Why slave switches not getting discover?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-23-2024 11:15 PM
Hi Team,
I would like to ask for assistance in this matter. We have several CIs under IP Switch class stake true and having master and slave relationships. The CI's names and serial numbers differ, but the IP address remains the same.
During discovery for this type of IP switch, only the master CI is discovering and getting updated, but the slave CI is not getting any updates. This is causing the stale count to increase for this class of IP switch. How is this problem resolved?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-03-2024 01:36 AM
Hi @Raju kunde ,
Master switch is discovered because that is active and running, but Slave switch is acting as a child switch and that will be discovered once master switch is not running or down.
You can ask Network team to make the Slave switch as primary and trigger the discovery and check.
Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
Thank You
AJ - TechTrek with AJ
Linkedin:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
ServiceNow Community Rising Star 2024
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-04-2024 01:00 AM
Hi Ajay,
Thank you for response.
Here master ci is discovering correctly but child cis not getting updated.
And we have same ip address for slave ci's same as master.