Inventory Cisco Stacked Switches

This is a bit larger issue that also we had. There are also other issues with stacked switches and CMDB in current setup. For example if the active device in stack changes then the serial number of the stacked switch changes in SL1 and in CMDB also.

The underlying issue is that device sync can only sync, well.. devices. So you first have to create a devices for each physical stacked device and of course one device for the "stack", because at least in our ServiceNow we have not been able to send relationship between switch and switch (maybe that is our issue, IRE), and of course as the active device can change in stack so that needs to be separate vs those physical switches

Then our DAs also gather serial numbers, firmware etc from all stack members, enough data that our CMDB people are happy.

And this does not end here, you also have to create device classes for the stacks and edit current ones, because those devices are easily saying they are stacks, because they are stackable, even though there is only one device in that "stack". Those stack device classes need to be "intelligent enough" to understand if it is standalone switch or actual stack, this is pretty important because fixing it afterwards is pretty work intensive (still fixing those).

We have created these stack PPs for Cisco, HPE/Aruba and Juniper devices, including physical and virtual stacks.