What can I do to make sure Stacked Switch, Stack mode attribute is being discovered correctly?

[Cathlene Burk]

We have recently upgraded to San Diego, and I have been working to figure out why we have very few CIs for Master Stacked Switch.  I go in and find that the name of the Switch, and the Stack mode has been changed through discovery in the past two days. The number of Stack Switch Master CI records is going down rapidly, and at the same time, I am seeing duplicates appearing for the slave CIs.

Name is changed to SWITCHNAME-SerialNumber, and Stack Mode flips between Master and Slave, ending with the CI being updated as Slave instead of Master.

Is there something I can do to make sure this doesn't happen, Our Network Team has asked that we only make Master Switches available for changes instead of using slave records, since the impact is on the Master if any of the slave CIs are to be modified.

The network Team has told me that they are no longer able to pull information on Slave switches, and that once they resolve that it should fix our issue, however, we are pulling CIs for all the Slaves, but also renaming and changing Masters to Slaves.

Is anyone else seeing this behavior?

[Mahak2]

Hello,

Can you please check this article:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1117145

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0750531

Let me know if this resolves your issue.

Thanks.

Mark my response as helpful and correct as applicable.

[Will O]

We had seen the same issue within our environment and told it is no longer occurring after a later upgrade to San Diego.  Anyone else follow the KB above to resolve and clean up the existing problem records?

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1117145

[Mahak2]

Hello,

Any update on this?

Thanks

[David77]

Also looking for a follow-up. I opened a case w ServiceNow and they closed with this note:
------------------------
PRB1536015 - the PRB is fixed as in the pattern it does not populate incorrect serial numbers anymore.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1117145
There is also a script to fix some of the data but it can't completely fix all bad data. Manual action is required.

----------------------------------

We've got almost 100 switches with this issue, and to manually remediate takes about 10 minutes per switch!