
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-21-2022 03:14 PM
I wanted to populate the firmware version field for our network devices and ran across the following HI article.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0793931
Followed it and it worked for our Cisco devices. However we have other brands as well including Arista which is the next one I was trying to implement.
I'm no expert with regex so that is part of the reasoning for my post.
The Cisco regex, as you can see in the previous link, is: Cisco.*Version\s([^,]+),
The string...and it returns and populates the firmware version field with what's in bold.
Cisco NX-OS(tm) nxos.7.0.3.I4.7.bin, Software (nxos), Version 7.0(3)I4(7), RELEASE SOFTWARE Copyright (c) 2002-2013 by Cisco Systems, Inc. Compiled 6/28/2017 13:00:00
Fabric Stack Root
System OID: 1.3.6.1.4.1.9.12.3.1.3.1467
On to my Arista regex issue. The string for it is this...
Arista Networks EOS version 4.21.5.1F running on an Arista Networks DCS-7280SE-72
48 SFP+ +2 MPO 100Gb 1RU
System OID: 1.3.6.1.4.1.30065.1.3011.7280.3714.72
When I entered this regex, Arista.*version\s([^,]+)\s it returned what I put in bold. and entered '4.21.5.1F running on an Arista Networks' into the firmware version field. That's me just throwing a guess out there 🙂
Thanks in advance!!!
Solved! Go to Solution.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-22-2022 11:05 AM
Try Arista.*version\s([^\s]+) instead. This will only capture the version number.
Also have a look at https://regex101.com/. Its a great tool for writing and debugging regular expressions.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-21-2022 05:54 AM
Hi David,
I wasn't able to access the link in your firsts comment. Is your goal to show CI model firmware version? We are trying to figure out how to add the compliance parameters (what we consider to be compliant). If possible, please let me know if that makes sense and if you have any suggestions.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-01-2022 08:06 AM
Hey Thomas. What link are you referring to? I didn't see one in my original post.
My goal, which was accomplished, was to populate the firmware version for certain network CIs that were not automatically populating. To do this I had to update the 'SNMP - Classify' sensor. So I created a new one, disabled the OOB, and added the required code to capture the firmware version of the devices that were having issues.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-03-2025 02:24 PM
Hi Rishi,
I am also facing same issue and if the version is Version 7.0(3)I4(7), it updating using the following regix "Version\s([^,]+)," if the version data is different like example "Version 03.06.04.E", is not populating. Let me know in this how achieved. And also in this multiple versions how we can achieve in one discovery extension.