cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1412
Views
15
Helpful
4
Replies

CSPC Collector bandwidth usage

aadrian
Level 1
Level 1

I know the CSPC Collector uses SNMP polling to gather network hardware information during its discovery stage. I’m trying to find how much the actual bandwidth usage the collector uses in that process or in other words what is the load the collector puts on the infrastructure? 

1 Accepted Solution

Accepted Solutions

Lynden Price
Cisco Employee
Cisco Employee

Hi Adrian,

There are a few different scenarios for how the collector does its discovery.

Strictly in terms of bandwidth, the collector produces very little traffic during discovery. The discovery phase only polls a few general MIBs for the purposes of categorizing the device. This device categorization determines what MIBs will be used on the device during the inventory.

Doing a discovery by a known IP address produces very little network traffic. The collector makes its request directly to the requested IP, receives it, and then doesn’t poll the device again. There is no ongoing polling required.

More specifically:

percent_usage = (elements * packet_size * 8bits_per_Byte)/(network_bandwidth*polling interval)

The discovery uses 24 elements at most. Assuming a 100 Mbps Ethernet connection:

percent_usage = (24*1500*8)/(100,000,000*1) = 0.00288

The means the discovery is using 0.00288 of the available bandwidth and only for that one instance of polling.

Doing a discovery by protocol however, is a different story. The collector makes its request for basic information from the seed IP address and then also polls a table on the device to try and learn about other devices on the network. It then reaches out to these devices and does the same, splintering out through the network according to the number of hops specified in the discovery.

The difference in bandwidth in these two scenarios is very small, but the difference in device impact (CPU usage, etc.) is huge. For example, if you do a routing table discovery on a core network device, the potentially enormous routing table could cause the CPU usage to spike, or disrupt traffic passing through the device. These kinds of discoveries should be scheduled off peak hours.

Cheers,

Lynden

View solution in original post

4 Replies 4

Lynden Price
Cisco Employee
Cisco Employee

Hi Adrian,

Thank you for your question. Please give me a little time to draft an appropriate response.

Thank you,

Lynden

Lynden Price
Cisco Employee
Cisco Employee

Hi Adrian,

There are a few different scenarios for how the collector does its discovery.

Strictly in terms of bandwidth, the collector produces very little traffic during discovery. The discovery phase only polls a few general MIBs for the purposes of categorizing the device. This device categorization determines what MIBs will be used on the device during the inventory.

Doing a discovery by a known IP address produces very little network traffic. The collector makes its request directly to the requested IP, receives it, and then doesn’t poll the device again. There is no ongoing polling required.

More specifically:

percent_usage = (elements * packet_size * 8bits_per_Byte)/(network_bandwidth*polling interval)

The discovery uses 24 elements at most. Assuming a 100 Mbps Ethernet connection:

percent_usage = (24*1500*8)/(100,000,000*1) = 0.00288

The means the discovery is using 0.00288 of the available bandwidth and only for that one instance of polling.

Doing a discovery by protocol however, is a different story. The collector makes its request for basic information from the seed IP address and then also polls a table on the device to try and learn about other devices on the network. It then reaches out to these devices and does the same, splintering out through the network according to the number of hops specified in the discovery.

The difference in bandwidth in these two scenarios is very small, but the difference in device impact (CPU usage, etc.) is huge. For example, if you do a routing table discovery on a core network device, the potentially enormous routing table could cause the CPU usage to spike, or disrupt traffic passing through the device. These kinds of discoveries should be scheduled off peak hours.

Cheers,

Lynden

Thanks for the post!

Question: what protocols can be involved in the "protocol discovery" you mentioned? And where is this CPU load experienced- I am assuming it's on all the routers part of the discovery. Is there a way calculate or estimate this CPU load?

 

Thanks!

aadrian
Level 1
Level 1

You're the man Lynden!! Tks

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: