- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-23-2018 01:41 PM
Hello Experts,
We see that, the Switch class CI gets created for vlans. In following list, cel-cs1 is the only physical switch, rest all are just interfaces, which shouldnt be classified as switch.
Please help..
Solved! Go to Solution.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-24-2018 06:10 AM
The reason why this is happening is because you discovery is currently setup to take DNS for the name instead of the name returned by the system. Look in your discovery properties page and you will see a setting which calls out setting SNMP is trusted host name source. As it stands right now when you discover those VLANs via their management IP it is resolving a different name and depending on how your identifiers are setup it probably isn't finding a match to the original one because the name is indeed different according to DNS.
If you check that option you should find that those will stop being discovered that way. I would also check to make sure that the serial number matches cause that should also of caused them to be identified together but more then likely it is because of the DNS entry and in most cases I turn off the DNS or NetBios is trusted name source because often DNS isn't setup properly at most organizations. Hope this helps.
EDIT: While this is most likely your issue I would definitely check your identifiers first and see what you have setup to identify on. If the issue is what I think it is and you are using the out of the box identifiers you shouldn't be getting duplicates if the serial number is coming back. Instead you would see 1 CI with a flip flopping name. Either way I think you will have to play with this setting called out here to make it use the system name instead of DNS but make sure you follow up on your CI Identification rules as well to understand what they are looking for (and confirm that the data is coming back from your device properly).

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-23-2018 02:30 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-23-2018 02:35 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-23-2018 06:20 PM
Is the correct sysobjectid in the OID table? Is the OID setup correctly to handle this type of switch?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-24-2018 06:10 AM
The reason why this is happening is because you discovery is currently setup to take DNS for the name instead of the name returned by the system. Look in your discovery properties page and you will see a setting which calls out setting SNMP is trusted host name source. As it stands right now when you discover those VLANs via their management IP it is resolving a different name and depending on how your identifiers are setup it probably isn't finding a match to the original one because the name is indeed different according to DNS.
If you check that option you should find that those will stop being discovered that way. I would also check to make sure that the serial number matches cause that should also of caused them to be identified together but more then likely it is because of the DNS entry and in most cases I turn off the DNS or NetBios is trusted name source because often DNS isn't setup properly at most organizations. Hope this helps.
EDIT: While this is most likely your issue I would definitely check your identifiers first and see what you have setup to identify on. If the issue is what I think it is and you are using the out of the box identifiers you shouldn't be getting duplicates if the serial number is coming back. Instead you would see 1 CI with a flip flopping name. Either way I think you will have to play with this setting called out here to make it use the system name instead of DNS but make sure you follow up on your CI Identification rules as well to understand what they are looking for (and confirm that the data is coming back from your device properly).