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

Errors when importing NS.chassis.mib

0

0

Article ID: KB13364 KB Last Updated: 18 Feb 2009Version: 3.0
Summary:
Import of NS.chassis.mib into some SNMP/MIB management tools can fail due to errors in MIB files.
Symptoms:
This article applies to 6.1.0 and 6.2.0 ScreenOS MIBs.

1. For SNMPv1 ScreenOS MIBs:
The import of SNMPv1 NS.chassis.mib can fail. This failure occurs due to an error in the following line of NS.chassis.mib file:
-- LAST-UPDATED “200705080000Z" -- May 8, 2007 by mxk <<<<<<<The line number is 7 in the mib file
The string (May 8, 2007 by mxk) behind the second pair of adjacent hyphens causes a syntax error in the import.

Note: Incase, you are using HPOV-NNM (Network Node Manager) snmp tool, then you have to make some additional changes in SNMPv1 NS.chassis.mib for the import to be successful. Please, refer to the below “Solution” section for “SNMPv1 Netscreen MIBs”.

2. For SNMPv2 ScreenOS MIBs:
The import of NS.chassis.mib can fail due to wrong definition in mib file NS-SMI.mib. The error is in the following line of the SNMPv2 NS-SMI.mib file:
netscreenChasis OBJECT IDENTIFIER ::= { netscreen 21 } <<<<<<<The line number is 87 in the mib file
The character "s" is missing from the word “Chasis”.
Solution:
Work-arounds:

1. For SNMPv1 ScreenOS MIBs:
The original line in the SNMPv1 NS.chassis.mib is
-- LAST-UPDATED "200705080000Z" -- May 8, 2007 by mxk
The solution is to modify the above line as
-- LAST-UPDATED "200705080000Z"
-- May 8, 2007 by mxk
Or deleting the string (May 8, 2007 by mxk), so that the line in MIB file appears like this
-- LAST-UPDATED "200705080000Z" --


Note: Incase, you are using HPOV-NNM (Network Node Manager) snmp tool, then you have to make the additional changes in SNMPv1 NS.chassis.mib for the import to be successful. The changes are listed below as a and b.

a. The original line in the SNMPv1 NS.chassis.mib is

nsTemperatureCur INTEGER, <<<<<<<The line number is 175 in the mib file


The solution is removing the comma after the INTEGER so that the above line appears as

nsTemperatureCur INTEGER

b. The original line in the SNMPv1 NS.chassis.mib is

nsSlotSN DisplayString, <<<<<<<The line number is 237 in the mib file


The solution is removing the comma after the DisplayString so that the above line appears as

nsSlotSN DisplayString


2. For SNMPv2 ScreenOS MIBs:
The original line in the SNMPv2 NS-SMI.mib is
netscreenChasis OBJECT IDENTIFIER ::= { netscreen 21 }
The solution is to change netscreenChasis to netscreenChassis in the above line, so that the line in MIB file appears like this:
netscreenChassis OBJECT IDENTIFIER ::= { netscreen 21 }
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