Switch Scanning
SNMP traps is not supported as the server only supports one-way traffic from the server to the switch.
MLS switch scanning requires an SNMP read only community string. The string is configured on the switches at the time of implementation and it is communicated to the Serraview Implementation team to set up on the MLS. MLS can be configured to use only one community string at a time, hence all switches to be scanned need to have the same community string for MLS to scan.
The SNMP OIDs used by switch querying are:
|
OidvtpVlanEntry = 1.3.6.1.4.1.9.9.46.1.3.1.1; |
If there is an ACL to restrict SNMP access to certain clients, then MLS would need to be added to the access control list.
The Client provides switch details (name, IP Address, building it services, floor(s) it services) at the time of implementation and provide them to the Serraview Implementation team to import, so the MLS knows which switches to scan.
The format of the Switch Import is described in the Switch Import and the Client can send the Switch Import file to the Serraview Support Team, use the File Upload's category Other and include a comment.
The location details required are the floors that the switch services, not its physical location. For example, a switch might be physically placed on level 2 but services wall ports on level 4 and 5.
Only endpoint switches servicing workstations/meeting rooms/wall ports should be included in the list; distribution switches and router switches are to be excluded.
Below is a sample switch information table showing all the required information.
|
Switch Name |
Switch IP |
Building |
Servicing Floor |
Servicing Additional Floors |
|---|---|---|---|---|
|
NSYSR058 |
10.90.0.45 |
385 Bourke St, Melbourne |
22 |
|
|
NSYSR103 |
10.90.11.22 |
385 Bourke St, Melbourne |
23 |
24 |
|
NAWPR058 |
10.28.28.17 |
415 Collins St, Melbourne |
3 |
4,5 |