Cisco Catalyst concatenating switch stacks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
We're bringing in our network gear info primarily using Cisco Catalyst Connector, however it's creating switch stacks as one CI instead of multiple (it also misses the relationships, so we will be using Discovery) and is just concatenating Serial numbers and models. I believe the data is stored this way in CC as well, but I'm not familiar with the tool and if it's typical for it to look that way. Discovery is scanning the switches properly and creating multiple CIs for a stack, and relating them to each other, but then CC isn't detecting those CIs for itself and updating them. Is there anyway to get CC and Discovery to play nice with the CIs? Ideally we'd have Discovery scan and create them, and Catalyst would update the other non-discoverable information, but if it's not looking at switch stacks properly, we have problems.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @michellewol
Refer these links , if helps : Cisco Stacked Switch Discovery issues
Discovery of Cisco Stacked Switches - New York
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Not quite the same issue, I've attached a screenshot for an example. These 3 CIs represent a stack of 2 switches. The top CI, created by Cisco Catalyst (Discovery Source - Other Automated), and is making 1 CI of 2 switches, and just concatenating the serial numbers and models into the one field on one CI. The other 2 CIs, are created by Discovery, and are correctly created and related as master and member. Neither source will update the other, as they don't recognize the CI, and it's now a duplicate in the CMDB in a weird way. We want the format of Discovery, but we want CC to be able to recognize it and utilize it from a future ITSM perspective.