Why is a Cisco switch, or router, discovered under the wrong device class? How to troubleshoot a cisco router being discovered as a switch or visa versa.
book
Article ID: 331013
calendar_today
Updated On:
Products
VMware Smart Assurance
Issue/Introduction
On discovery you notice that your new newly discovered Cisco Switches are showing up as Cisco Routers as seen below:
Environment
NCM 10.X
Resolution
There can be several reasons that cause this situation.
Scenario 1: The Cisco IOS Switch Device Class or SNMP mechanism is disable under the Global Managed Device Classes
.
Scenario 2: Only using SSH for discovery and since Router is the first driver on the discovery list it tries and it works to complete the discovery, but fails to detect as a Cisco Switch. An option to try is to remove all of the Devices in the Global Managed Device Class list by clicking on Manage List and just adding Cisco IOS Switch. Then complete a discovery. (see below)
Scenario 3: Verify and make sure the Model information, SysOID information and driver number package match correctly in inside the Cisco.Models file located in the $VOYENCE_HOME/custompackage/Cisco directory. Correct the driver package number if needed, remember this is a global setting for this class. ( 1=Router, 2=Switch) (See the screen shot below)
The last thing to check is the Object IP Forwarding, you will need to gather a Walk of the device.
SNMP discovery is looking for the OID ipForwarding {.1.3.6.1.2.1.4.1.0}
.1.3.6.1.2.1.4.1.0: 1 (Forwarding) Will be discovers as Router
.1.3.6.1.2.1.4.1.0: 2 (Not Forwarding) Will be discovers as Switch
If NCM is discovering the device using SNMP, its detecting use the Object IP Forwarding (most common) and if its not correct and try to work around the issue please contact the OEM to correct or provide work around.