Cisco Stacked switches?

[Alex Macdonel]

We're currently trying to quickly populate our asset records through discovery and we hit a snag when it comes to Cisco stacked switches; discovery only finds the primary switch but we'd like to discover all members of the stack.

I found on share the following post - Custom Probe/Sensor - Cisco Stacked Switches (member info) but it assumes you know how discovery works and I haven't been able to make it work, the error message I got is: No sensors defined

How do you deal with stacked switches? were you able to make the shared probe/sensor work? and if you did, how?

Thanks!

[A Westervelt]

That's the correct OID for the Catalyst 29XXs.

It might be the OID is inactive or SNMP did not retrieve the value when scanning the switch.

[Ryan Zulli]

Agreed - I would recommending installing a MIB Browser on your MID Server host (I like iReasoning), and loading the Cisco Stack MIB. This will tell you if anything about the stack members is returned.

let me know if this helps!

[Ankush13]

I was trying to post this on the share but it seems there is a character limit there. I have found some things that I wish to share:
1. moduleSerialNumberString has been deprecated and replaced by entPhysicalSerialNum per Cisco website. (not a big deal!)
2. If I modify probe to probe entPhysicalSerialNum, the sensor code at the moment will create cmdb entries for all the serial numbers it finds. Interesting thing to note here is that it will have serial numbers of everything(stack switches, power supplies, fans, etc...).   So an entry of a fan serial number(say) and it being shown as a member of stack becomes be an undesired state.

From a logical sense, I hope that when switches are stacked, they are of same make,model and might have same serial number prefix. But this is highly assumptious of me. I know that different vendor switches can be stacked in which case world will not be the same.

[Amit Sharma4]

Hi Ryan

This works fine for me and thanks for making this available. But I see one issue in my discovery.

Issue: This code does not update the CIs which are already existing in CMDB i.e. no update in down and upstream relationship. If I delete the existing CIs ad rediscover, then it creates the down and upstream relationships.

Any pointer for this?

Thanks

Amit

[ralvarez]

Hi Ryan,

I'm having the same issue here, would you mind sharing again your customization for the Cisco Stack?

Thank you in advance,
Roberto