Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-4171

Cisco Catalyst "version changed" flapping

Details

    • Help
    • Resolution: Unresolved
    • Trivial
    • None
    • Professional Edition
    • Default
    • None

    Description

      For some of our Cisco Catalyst 3850 series switches, I'm seeing regular "version changed" flaps in the event log, but nothing has changed on the switches.

      Examples:

      2022-07-07 23:35:02 Version changed: 'Gibraltar 16.12.07' -> '16.12.7'

      2022-07-07 23:30:31 Version changed: 'Gibraltar 16.12.07' -> '16.12.7'

      2022-07-07 23:10:44 Version changed: '16.12.7' -> 'Gibraltar 16.12.07'

      2022-06-30 22:20:09 Version changed: 'Gibraltar 16.12.07' -> '16.12.7'

       

      Also seeing it for switches running 16.12.3a

       

      I don't think it's a problem pe se, it's just confusing (and possibly giving misleading info to managers regarding our sofware update progress). Do you have any idea what's causing it?

      Many thanks!

       

      Attachments

        Activity

          [OBS-4171] Cisco Catalyst "version changed" flapping
          adama Adam Armstrong added a comment -

          You'd need to run lots of debugged os poller runs to see catch the changes and see why 

          ./poller.php -n <device_id> -m os -d -r

          You'll need to capture the output when it changes

           

          adama Adam Armstrong added a comment - You'd need to run lots of debugged os poller runs to see catch the changes and see why  ./poller.php -n <device_id> -m os -d -r You'll need to capture the output when it changes  
          kingtrw Tom King added a comment -

          To clarify, the four lines I quoted as example were all for the same switch.

          kingtrw Tom King added a comment - To clarify, the four lines I quoted as example were all for the same switch.
          bot Observium Bot added a comment -

          General questions and device support can be discussed in our Discord channel, click here to join.

          Please make and attach additional information about the device:

          • full snmp dump from device: 

            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
            		 
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

            If device not support SNMP version 2c, replace -v2c with -v1.

          • If you have problems with discovery or poller processes, please do and attach these debugs: 

            ./discovery.php -d -h <device>
            		 
            ./poller.php -d -h <device>

          • additionally attach device and/or vendor specific MIB files

          This comment is added automatically.

          bot Observium Bot added a comment - General questions and device support can be discussed in our Discord channel, click here to join . Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files This comment is added automatically.

          People

            landy Mike Stupalov
            kingtrw Tom King
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: