Send netdisco-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/netdisco-users
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of netdisco-users digest..."
Today's Topics:
1. Switch bootcode reporting in snmp-info (Les Begnaud)
2. Re: Switch bootcode reporting in snmp-info (Oliver Gorwits)
--- Begin Message ---
I'm looking for permission to do a PR for EdgeSwitch firmware version
reporting. I don't know if this would be against some kind of standard, but I'd
like to merge the firmware and bootcode versions in the firmware string.
Example:
(es-ljb-testbed-1) #show version bootloader
Querying Active and Backup Software, please wait ....
Running Version................................ 1.1.0.5102011
Active Version................................. 1.1.0.5102011
Backup Version................................. 1.1.0.5102011
(es-ljb-testbed-1) #show sysinfo
System Description............................. EdgeSwitch 48-Port 500W,
1.8.1.5145168, Linux 3.6.5-1b505fb7, 1.1.0.5102011
System Name.................................... es-ljb-testbed-1
I would like to report this switch's version as:
1.8.1.5145168-b1.1.0.5102011
Anyone see a potential issue with that? Would the length be ok? If not we could
shorten it and probably be fine to either
1.8.1.5145168-b1.1.0
Or even
1.8.1.5X-b1.1.0
Thoughts? I think it's probably important to include something from the 4th
section in the firmware version as those can change sometimes
Les Begnaud
Systems Engineer (Sys Lord)
337.205.4652
[email protected]
--- End Message ---
--- Begin Message ---
Seems a good idea to me - thanks! There's no constraint on content or
length of the 'os_ver' field of the device table.
Rather than patch in Netdisco, you could also patch the os_ver() method in
SNMP::Info for this device class to return the text string you want...
Netdisco would never know.
regards
Oliver.
On Mon, 22 Jul 2019 at 21:43, Les Begnaud <[email protected]>
wrote:
> I’m looking for permission to do a PR for EdgeSwitch firmware version
> reporting. I don’t know if this would be against some kind of standard, but
> I’d like to merge the firmware and bootcode versions in the firmware
> string. Example:
>
>
>
> (es-ljb-testbed-1) #show version bootloader
>
>
>
> Querying Active and Backup Software, please wait ....
>
>
>
> Running Version................................ 1.1.0.5102011
>
> Active Version................................. 1.1.0.5102011
>
> Backup Version................................. 1.1.0.5102011
>
>
>
> (es-ljb-testbed-1) #show sysinfo
>
>
>
> System Description............................. EdgeSwitch 48-Port 500W,
> 1.8.1.5145168, Linux 3.6.5-1b505fb7, 1.1.0.5102011
>
> System Name.................................... es-ljb-testbed-1
>
>
>
> I would like to report this switch’s version as:
>
>
>
> 1.8.1.5145168-b1.1.0.5102011
>
>
>
> Anyone see a potential issue with that? Would the length be ok? If not we
> could shorten it and probably be fine to either
>
>
>
> 1.8.1.5145168-b1.1.0
>
>
>
> Or even
>
>
>
> 1.8.1.5X-b1.1.0
>
>
>
> Thoughts? I think it’s probably important to include something from the 4
> th section in the firmware version as those can change sometimes
>
>
>
> Les Begnaud
> Systems Engineer (Sys Lord)
>
> *337.205.4652* <337.205.4652>
> *[email protected]* <[email protected]>
> _______________________________________________
> Netdisco mailing list
> [email protected]
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
