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

High CPU usage on Juniper EX4300 virtual chassis

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • Professional Edition
    • Poller
    • None
    • Juniper virtual chassis: 2x EX4300-32F and 2x EX4300-48T

    Description

      After update Juniper virtual chassis 2x EX4300-32F and 2x EX4300-48T from Junos  14.1X53-D30.3 to 21.4R3.15

      Attachments

        1. 19.debug
          3.35 MB
        2. discovery.txt
          7 kB
        3. ex4300-vc.mngmt.pardubice.cmnet.cz.poller
          3.29 MB
        4. ex4300-vc.mngmt.pardubice.cmnet.cz.snmpwalk
          9.53 MB
        5. poller.txt
          7 kB
        6. Screenshot 2024-01-26 at 7.43.19.png
          Screenshot 2024-01-26 at 7.43.19.png
          974 kB

        Activity

          [OBS-4724] High CPU usage on Juniper EX4300 virtual chassis

          yep, you can make poller debug with this device_id (but this not make sense for issue, since you revert firmware version):

          ./poller.php -d -r -h 19

          landy Mike Stupalov added a comment - yep, you can make poller debug with this device_id (but this not make sense for issue, since you revert firmware version): ./poller.php -d -r -h 19
          Svoboda Ondrej added a comment -

          mysql> SELECT `device_id` FROM `devices` WHERE `disabled` = 0 AND `hostname` LIKE 'ex4300-vc.mngmt.pardubice.cmnet.cz' AND `poller_id` = '0' ORDER BY `device_id` ASC;
          -----------
          | device_id |
          -----------
          |        19 |
          -----------
          1 row in set (0.00 sec)

          Svoboda Ondrej added a comment - mysql> SELECT `device_id` FROM `devices` WHERE `disabled` = 0 AND `hostname` LIKE 'ex4300-vc.mngmt.pardubice.cmnet.cz' AND `poller_id` = '0' ORDER BY `device_id` ASC; ----------- | device_id | ----------- |        19 | ----------- 1 row in set (0.00 sec)

          Please go to page: device -> performance data
          and make screenshot of page.

          landy Mike Stupalov added a comment - Please go to page: device -> performance data and make screenshot of page.

          still not:

          #####  Starting polling run at 2024-01-19 18:52:26  #####
           
           
          SQL[SELECT `device_id` FROM `devices` WHERE `disabled` = 0 AND `hostname` LIKE 'ex4300-vc.mngmt.pardubice.cmnet.cz' AND `poller_id` = '0' ORDER BY `device_id` ASC]
          SQL RUNTIME[0.00211287s]
          WARNING: 0 devices polled. Did you specify a device that does not exist?
          poller.php: ex4300-vc.mngmt.pardubice.cmnet.cz - 0 devices polled in 0.1531 secs
          #####  Completed polling run at 2024-01-19 18:52:26  #####

          show me device page in observium.

          landy Mike Stupalov added a comment - still not: ##### Starting polling run at 2024-01-19 18:52:26 #####     SQL[SELECT `device_id` FROM `devices` WHERE `disabled` = 0 AND `hostname` LIKE 'ex4300-vc.mngmt.pardubice.cmnet.cz' AND `poller_id` = '0' ORDER BY `device_id` ASC] SQL RUNTIME[0.00211287s] WARNING: 0 devices polled. Did you specify a device that does not exist? poller.php: ex4300-vc.mngmt.pardubice.cmnet.cz - 0 devices polled in 0.1531 secs ##### Completed polling run at 2024-01-19 18:52:26 ##### show me device page in observium.
          Svoboda Ondrej added a comment -

          Is that ok now?

          I had to rollback to Junos 14, if it doesn't mind.

          Svoboda Ondrej added a comment - Is that ok now? I had to rollback to Junos 14, if it doesn't mind.

          Attached poller/discovery is incorrect. You should use exactly same hostname for device as stored in observium or device_id. You always can see device_id in device page url.

          landy Mike Stupalov added a comment - Attached poller/discovery is incorrect. You should use exactly same hostname for device as stored in observium or device_id. You always can see device_id in device page url.

          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 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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:
            5 Start watching this issue

            Dates

              Created:
              Updated: