Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

OpenNMS does not show the proper CPU fan speed on JA2500 appliance

0

0

Article ID: KB30476 KB Last Updated: 09 Jul 2015Version: 1.0
Summary:

CPU fan speed monitoring of the JA2500 in OpenNMS is not correct.

Symptoms:

The speed of the CPU fan in the JA2500 hardware is shown wrong in the JA2500. This is shown properly for the JA1500, even though the SNMP config remains the same.

Cause:

The root cause of this issue is that the wrong OID is monitored. The JA2500 has a different fan index compared to the JA1500.

Solution:

Monitor a fan with an index of 3 or 4. The workaround for this issue is as follows:

  1. Back up the following configuration files under /home/admin:

    /etc/snmp/snmpd.conf
    /opt/opennms/etc/events/JuniperEvents/space-platform/mib-jnx-space-platform.xml
  2. Modify the /etc/snmp/snmpd.conf file on all nodes. Look for the following lines and remove them:

    monitor -S -r 60 -I "CPU fan trigger" lmFanSensorsValue.2 < 1000
    monitor -S -r 60 -I "CPU fan clear" lmFanSensorsValue.2 >= 1000

    Add the following lines instead:

    monitor -S -r 60 -I "CPU fan3 trigger" lmFanSensorsValue.3 < 1000
    monitor -S -r 60 -I "CPU fan3 clear" lmFanSensorsValue.3 >= 1000
    monitor -S -r 60 -I "CPU fan4 trigger" lmFanSensorsValue.4 < 1000
    monitor -S -r 60 -I "CPU fan4 clear" lmFanSensorsValue.4 >= 1000

    Save the file and restart snmpd.

  3. Replace the XML file at the location /opt/opennms/etc/events/JuniperEvents/space-platform/mib-jnx-space-platform.xml with the following XML file:
    library/CUSTOMERSERVICE/GLOBAL_JTAC/Palani/mib-jnx-space-platform.xml 
    (the md5sum of this file is 1b866acccfe6b85447402b02002792a1) 

    Copy the XML file to all the space nodes. Ensure that the ownership and permission for this file are correctly set to opennms:opennms and 640, respectively.

  4. Restart OpenNMS on the VIP node.

    #su opennms
    $/etc/init.d/opennms restart
    $exit
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search