Updating the serial number before it's run through IRE

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-27-2024 01:12 PM
I have an issue with Juniper routers where their routing engines use the same serial number as the chassis. This is resulting in the same CI flipping names (router-re0 and router-re1) and IPs.
One option that was brought up was to update the serial number through a pattern extension. I was able to accomplish this and appended the serial number with either -re0 or -re1.
However, it is still updating the same CI rather than creating a new one. It seems I would have to do this around step 8 in the discovery section.
Thoughts/Questions
- would creating a custom step in an OOB pattern affect future updates?
- would this be the right place to create this step? (I see it's populating the ip router SN here, but from the cmdb_ci_serial_number table which means it's already been written in the database. )
- has anyone had to deal with anything similar to this 🙂
Thanks!!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2024 06:28 AM
Hi @David Casper ,
Yes creating a custom step in OOB discovery pattern impact you in future release or upgrades of ServiceNow Instances.
I have not seen that type of issue but you can refer the below Docs, which may help you.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0750386
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.
Thanks
AJ
Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/
ServiceNow Community Rising Star 2024