Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Smarts NCM: 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. (335566)

Last Updated: 5/29/2020Categories: TroubleshootingTotal Views: 3741Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

An explanation of why a Cisco IOS Switch gets discovered as a Cisco IOS Router.

On discovery you notice that your new newly discovered Cisco Switches are showing up as Cisco Routers.. (See the screen shot below):

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.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - NCM

Take Our Survey

Support Assistant