Details

    • Vendor Bug
    • Resolution: Won't Fix
    • Minor
    • None
    • Enterprise Edition
    • Discovery

    Description

      Dell os10 bgp peers are showing incorrect uptimes. Eventlog is also flooded every 5min about BGP session flap even though there has been no flaps. It looks like that this started happening after upgrade from 22.4.11943 to 22.5.12060. DB schema was also upgraded from 462 to 467.

       

      Attachments

        1. discover526.txt
          305 kB
        2. poller526.txt
          426 kB
        3. Screenshot 2022-06-02 at 15.21.38.png
          Screenshot 2022-06-02 at 15.21.38.png
          141 kB
        4. Screenshot 2022-06-02 at 16.12.10.png
          Screenshot 2022-06-02 at 16.12.10.png
          208 kB

        Issue Links

          Activity

            [OBS-4134] BGP peers uptime 27 years

            Just polling bgp peers by DELLEMC-OS10-BGP4V2-MIB was added recently (in r11955).

            landy Mike Stupalov added a comment - Just polling bgp peers by DELLEMC-OS10-BGP4V2-MIB was added recently (in r11955).
            jsalo Jari Salo added a comment -

            Hmm, this is interesting. We've had these devices for a couple of years and only now this issue has surfaced. We do have some switches with newer software (10.5.2.7), but they behave exactly the same. However, only one of these devices (the one, where the debugs are from) is reporting bgp flaps all the time to eventlog.

            jsalo Jari Salo added a comment - Hmm, this is interesting. We've had these devices for a couple of years and only now this issue has surfaced. We do have some switches with newer software (10.5.2.7), but they behave exactly the same. However, only one of these devices (the one, where the debugs are from) is reporting bgp flaps all the time to eventlog.

            I really not know what this values should mean, this is exactly firmware issue..
            Probably on more recent firmwares this issue already fixed.
            (I see you use 10.5.2.0P1, but latest is 10.5.3.2)

            landy Mike Stupalov added a comment - I really not know what this values should mean, this is exactly firmware issue.. Probably on more recent firmwares this issue already fixed. (I see you use 10.5.2.0P1, but latest is 10.5.3.2)

            As I see device report this (incorrect) times in snmp:

            DELLEMC-OS10-BGP4V2-MIB::os10bgp4V2PeerFsmEstablishedTime

            os10bgp4V2PeerFsmEstablishedTime.1.1.4.10.10.11.1 = 879383700
            ...
            os10bgp4V2PeerFsmEstablishedTime.1.1.4.10.10.11.11 = 39597400

            DELLEMC-OS10-BGP4V2-MIB::os10bgp4V2PeerInUpdatesElapsedTime

            os10bgp4V2PeerInUpdatesElapsedTime.1.1.4.10.10.11.1 = 879579800
            ...
            os10bgp4V2PeerInUpdatesElapsedTime.1.1.4.10.10.11.11 = 39630400

            MIB description said that both this values should be in seconds unit.

            It seems as firmware issue, please write to Vendor support about this.

            landy Mike Stupalov added a comment - As I see device report this (incorrect) times in snmp: DELLEMC-OS10-BGP4V2-MIB::os10bgp4V2PeerFsmEstablishedTime os10bgp4V2PeerFsmEstablishedTime.1.1.4.10.10.11.1 = 879383700 ... os10bgp4V2PeerFsmEstablishedTime.1.1.4.10.10.11.11 = 39597400 DELLEMC-OS10-BGP4V2-MIB::os10bgp4V2PeerInUpdatesElapsedTime os10bgp4V2PeerInUpdatesElapsedTime.1.1.4.10.10.11.1 = 879579800 ... os10bgp4V2PeerInUpdatesElapsedTime.1.1.4.10.10.11.11 = 39630400 MIB description said that both this values should be in seconds unit. It seems as firmware issue, please write to Vendor support about this .
            jsalo Jari Salo added a comment -

            Requested discovery and poller debugs are attached to this issue.

             

             

            jsalo Jari Salo added a comment - Requested discovery and poller debugs are attached to this issue.    

            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
              jsalo Jari Salo
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: