Routine Switch Management
The switch change management process allows for proactive maintenance for the SVLive service and reliability of the utilization data.
Switch Reconfiguration
If switches are reconfigured, the MLS will not be able to identify the correct switch and utilization data will not be collected for the workstations serviced by that switch. For more information on Rewire-up – Switch Reconfiguration, refer to Wire-up Maintenance.
Switch Not Linked to a Floor/Incorrect Switch Information Provided
Impact on Service
Serraview cannot link the utilization data to a floor or building.
Switch is retired or replaced
For information on Rewire-up – Switch is retired or replaced, refer to Wire-up Maintenance.
Re-cabling in the Communications room on a floor
For information on Rewire-up – Re-cabling, refer to Wire-up Maintenance.
Community String Changes
The client needs to maintain the same community string provided at time of implementation on all switches that MLS must scan. The community string must follow all required OIDs to be retrieved by SNMP polling. Any changes to the community string will need to be communicated before implementation as the
SVLive service will immediately be unavailable if switch scanning fails.
Impact on Service
A change to the name of community string being used by the MLS would cause all SVLive services to immediately become unavailable with data loss throughout the duration of the outage.
IP Address Changes
This happens when the switch was reconfigured with a different IP and not updated in Serraview, or an incorrect switch IP was imported to Serraview.
Impact on Service
The MLS will not be able to identify the correct switch and utilization data will not be collected for the workstations serviced by that switch. Until this is corrected user locations will not be accurate
The switch details need to be corrected in Serraview and the affected workstation re-wired up if any of the below changes has been made.