SVLive2 Network Impact

Switch Scanner

The Serraview Switch Scanning Service uses SNMP to communicate with the network switches. SNMP utilizes UDP (User Datagram Protocol) as its communications protocol, generating very little additional network traffic and allowing the network to drop the request if there is congestion.

The Corporate Real Estate Team expects real-time updates of User Locations in the Locator web app. SVLive can be configured to help balance the requirement of real-time updates and the subsequent network impact, particularly on switches.

Quick Scans

The quick scan's interval is the time between the completion of the last scan results, for a given switch, and the start of the next scan. Results are sent to the SVLive cloud endpoint over a secure HTTPS connection.

More Scans, More Load

Scanning more frequently may improve the speed of Switch Scan results updating the cloud, in turn improving the speed of status changes being visible in the Locator web app. 

However, scanning more frequently will mean:

• More load on the client's switches.
• More outbound network traffic, from the Switch Scanner to the SVLive endpoints.

Scan results are also dependent on the performance of the actual Switch Hardware and Switch Operating System versions, to perform the scan and return the results to the Switch Scanner.

For example, a client might have an average scan time of around 24 seconds, but the maximum time for a particular switch in the environment is 9 minutes. Therefore, people on those switches will not be updated in less than 10 minutes no matter how aggressive you set the scanning interval.

Payload size

The size of the payload sent from the Switch Scanner to the SVLive cloud endpoint varies depending on the size of active ports. For example:

Presence Service Payload Size

The size of the payload sent from the Presence Service to the SVLive cloud endpoint varies depending on the number of WAPs visible to the user device. For example: