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

High load on Juniper EX4500 routing engine after upgrade to JunOS 15.1R7.9

Details

    • Vendor Bug
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • Poller
    • None
    • Virtual chassis mixed mode:
      2x Juniper EX4500 switch
      3x Juniper EX4200 switch
      Junos 15.1R7.9

    Description

      Hello after update Junos from 12.3R12.4 to 15.1R7.9 on mixed virtual chassis consisted of Juniper EX4500 and EX4200 the is a very high load of the routing engine.

      According to https://supportportal.juniper.net/s/article/EX-Troubleshooting-and-resolving-high-CPU-utilization-on-EX4300?language=en_US I discovered that the process causing the problem is mib2d - which means SNMP.

       

      192.168.166.1.discovery

      Attachments

        1. 192.168.166.1.discovery
          1.94 MB
        2. 192.168.166.1.graph.png
          192.168.166.1.graph.png
          157 kB
        3. 192.168.166.1.poller
          3.45 MB
        4. 192.168.166.1.top
          5 kB

        Issue Links

          relates to

          Vendor Bug - This is vendor specific issue, not possible to be fixed inside our project. OBS-4012 Juniper EX4550 CPU utilisation increased after update to 22.2.11868

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. OBS-4311 Ex4200 Traffic Graphs missing after update

          • Major - Major loss of function.
          • Resolved

          Activity

            [OBS-4188] High load on Juniper EX4500 routing engine after upgrade to JunOS 15.1R7.9
            landy Mike Stupalov added a comment -

            nope, you are using stable channel. Switch to rolling:
            https://docs.observium.org/updating/#switch-between-rolling-and-stable-trains

            landy Mike Stupalov added a comment - nope, you are using stable channel. Switch to rolling: https://docs.observium.org/updating/#switch-between-rolling-and-stable-trains
            Svoboda Ondrej added a comment -

            I'm already on r12212:

            svn update
            Updating '.':
            At revision 12212.

            How do I force enable ports separate_walk option?

            I tried

            $config['polling']['selected_ports'] = true;

            but it did not work - the CPU utilization is still high

            Svoboda Ondrej added a comment - I'm already on r12212: svn update Updating '.': At revision 12212. How do I force enable ports separate_walk option? I tried $config ['polling'] ['selected_ports'] = true; but it did not work - the CPU utilization is still high
            landy Mike Stupalov added a comment -

            Should be fixed in r12212.

            You can force enable ports separate_walk option.
            This is trouble on JunOS: before 15.1R7.9 was faster polling with separate_walk, but after visa versa.

            landy Mike Stupalov added a comment - Should be fixed in r12212. You can force enable ports separate_walk option. This is trouble on JunOS: before 15.1R7.9 was faster polling with separate_walk, but after visa versa.
            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: