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

Juniper EX4550 CPU utilisation increased after update to 22.2.11868

Details

    • Vendor Bug
    • Resolution: Fixed
    • Critical
    • None
    • Enterprise Edition
    • Poller
    • None

    Description

      Hello,

      after update to Observium 22.2.11868 (stable) Juniper EX4550 switch virtual chassis CPU utilisation increased impossibly and graphs are not usable.

      We even tried to reboot the switch - no luck.

       

      Attachments

        1. ex4550.discovery
          454 kB
        2. ex4550.poller
          1.33 MB
        3. ex4550.snmpwalk
          600 kB
        4. Screenshot 2022-02-04 at 13.59.44.png
          Screenshot 2022-02-04 at 13.59.44.png
          177 kB
        5. Screenshot 2022-02-04 at 14.00.04.png
          Screenshot 2022-02-04 at 14.00.04.png
          115 kB

        Issue Links

          relates to

          Vendor Bug - This is vendor specific issue, not possible to be fixed inside our project. OBS-4188 High load on Juniper EX4500 routing engine after upgrade to JunOS 15.1R7.9

          • Major - Major loss of function.
          • Resolved

          Activity

            [OBS-4012] Juniper EX4550 CPU utilisation increased after update to 22.2.11868
            Svoboda Ondrej added a comment -

            Hello, thank you very much for the quick solution - it helped - the graphs are now ok.

             

            Svoboda Ondrej added a comment - Hello, thank you very much for the quick solution - it helped - the graphs are now ok.  
            landy Mike Stupalov added a comment -

            This is trouble with hardware/firmware on JunOS.

            Since firmware 15.1R5.5 (or around this version) Juniper "fixed" snmp stack for polling ports. And we disabled our hack with separate_walk feature for versions greater.

            In r11872 I increased this version to 15.1R7.9 for 4550. This should fix your issue..
            but I not sure about other versions and hw platforms.

            landy Mike Stupalov added a comment - This is trouble with hardware/firmware on JunOS. Since firmware 15.1R5.5 (or around this version) Juniper "fixed" snmp stack for polling ports. And we disabled our hack with separate_walk feature for versions greater. In r11872 I increased this version to 15.1R7.9 for 4550. This should fix your issue.. but I not sure about other versions and hw platforms.
            landy Mike Stupalov added a comment -

            Hi, sorry for delay.
            You can specify from which version you updated?

            landy Mike Stupalov added a comment - Hi, sorry for delay. You can specify from which version you updated?
            Svoboda Ondrej added a comment -

            ex4550.discovery

            Svoboda Ondrej added a comment - ex4550.discovery
            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
              Svoboda Ondrej
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: