Hi Calvin,
The attached one works. I made 2 edits: 1) Added a comma between “TRAP-TYPE” and “enterprises” in the IMPORT Statement 2) Changed “nimsoft.sysadm” to “sysadm” on line 168, after “ENTERPRISE” in the NimBUSAlarm Trap Let me know if you have any problems with this one. Good luck. Rob Esdale CA Technologies Sr. Services Consultant Mobile: +1-603-553-2593 [email protected] <mailto:[email protected]> <mailto:> <http://www.ca.com/> From: Calvin Lane [mailto:[email protected]] Sent: Tuesday, August 03, 2010 4:29 PM To: spectrum Cc: spectrum Subject: Re: [spectrum] Errors compiling MIB Thanks Mark. Here it comes with the attachement. On Tue, Aug 3, 2010 at 3:54 PM, Mark Serencha <[email protected]> wrote: Hard to tell from raw text. Can you re-post as an attachment? I can’t promise that I will have time to check, but others might ;-) From: Calvin Lane [mailto:[email protected]] Sent: Tuesday, August 03, 2010 3:44 PM To: spectrum Subject: [spectrum] Errors compiling MIB Hello List, When trying to complile Nimsoft.mib, I get the following error messages: Could not parse the file NIMSOFT-MIB. The error occured at the line no: 12 ,column: 9. Could not parse the file NIMSOFT-MIB. The error occured at the line no: 168 ,column: 37. The identifier should not start or end with number or special character. Can someone tell me what is wrong with this MIB file. Thanks in advance. Calvin Lane _____________________________________________________ NIMSOFT-MIB DEFINITIONS ::= BEGIN -- NIMSOFT-MIB { iso org(3) dod(6) internet(1) 4 1 4055} -- NIMSOFT enterprise specific MIB -- HISTORY: -- 2010/05/11 added alarmSuppressionKey, alarmProbeId, alarmUserTag1, alarmUserTag2, alarmSource, alarmOrigin, alarmTime, alarmTimezoneOffset, alarmNimId, alarmRobot, alarmDomain -- added IMPORTS of enterprises and changed the refering MIB to SNMPv2-SMI (from RFC-1215) IMPORTS TRAP-TYPE enterprises FROM SNMPv2-SMI; nimsoft OBJECT IDENTIFIER ::= { enterprises 4055 } sysadm OBJECT IDENTIFIER ::= { nimsoft 1 } alarm OBJECT IDENTIFIER ::= { sysadm 1 } -- the Alarm group alarmSeverity OBJECT-TYPE SYNTAX INTEGER { unknown(0), information(1), warning(2), minor(3), major(4), critical(5) } ACCESS read-only STATUS mandatory DESCRIPTION "The alarmSeverity object type is used to describe the level of severity of the alarm." ::= { alarm 1 } alarmSubsys OBJECT-TYPE SYNTAX OCTET STRING ACCESS read-only STATUS mandatory DESCRIPTION "The alarmSubsys object type is used to describe the subsystem (i.e. the service) within the NimBUS Alarm Server where the alarm occured." ::= { alarm 2 } alarmDescr OBJECT-TYPE SYNTAX OCTET STRING ACCESS read-only STATUS mandatory DESCRIPTION "The alarmDescr object type is used to give a textual description of a NimBUS alarm." ::= { alarm 3 } alarmSuppressionKey OBJECT-TYPE SYNTAX OCTET STRING ACCESS read-only STATUS optional DESCRIPTION "The alarmSuppression object type is used to give a uniquie identifier of a NimBUS alarm." ::= { alarm 4 } alarmProbeId OBJECT-TYPE SYNTAX OCTET STRING ACCESS read-only STATUS optional DESCRIPTION "The alarmProbeId object type is used to identify the probe that issued the of a NimBUS alarm." ::= { alarm 5 } alarmUserTag1 OBJECT-TYPE SYNTAX OCTET STRING ACCESS read-only STATUS optional DESCRIPTION "The alarmUserTag1 object type is used for the custom User Tag 1 field of a NimBUS alarm." ::= { alarm 6 } alarmUserTag2 OBJECT-TYPE SYNTAX OCTET STRING ACCESS read-only STATUS optional DESCRIPTION "The alarmUserTag2 object type is used for the custom User Tag 2 field of a NimBUS alarm." ::= { alarm 7 } alarmSource OBJECT-TYPE SYNTAX OCTET STRING ACCESS read-only STATUS optional DESCRIPTION "The alarmSource object type is used to identify the source of a NimBUS alarm." ::= { alarm 8 } alarmOrigin OBJECT-TYPE SYNTAX OCTET STRING ACCESS read-only STATUS optional DESCRIPTION "The alarmOrigin object type is used to identify the origin of a NimBUS alarm." ::= { alarm 9 } alarmTime OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS optional DESCRIPTION "The alarmTime object type is used to identify the time of a NimBUS alarm." ::= { alarm 10 } alarmTimezoneOffset OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS optional DESCRIPTION "The alarmTimezoneOffset object type is used to identify the timezone offset of a NimBUS alarm." ::= { alarm 11 } alarmNimId OBJECT-TYPE SYNTAX OCTET STRING ACCESS read-only STATUS optional DESCRIPTION "The alarmNimId object type is used to identify a NimBUS alarm." ::= { alarm 12 } alarmRobot OBJECT-TYPE SYNTAX OCTET STRING ACCESS read-only STATUS optional DESCRIPTION "The alarmRobot object type is used to identify the Nimsoft Robot that issued a NimBUS alarm." ::= { alarm 13 } alarmDomain OBJECT-TYPE SYNTAX OCTET STRING ACCESS read-only STATUS optional DESCRIPTION "The alarmDomain object type is used to identify the Nimsoft Domain that issued a NimBUS alarm." ::= { alarm 14 } -- Enterprise-specific traps to be sent from NIMSOFT Servers -- The trap definitions are compliant with RFC 1155, -- RFC 1212, and RFC 1215 -- -- Depends on the snmpgtw probe. It can be configured to map severity levels to -- specific trap numbers. E.g. severity level = 1 maps to specific trap # 1 NimBUSAlarm TRAP-TYPE ENTERPRISE nimsoft.sysadm VARIABLES { sysDescr, alarmLevel, alarmSubsys, alarmDescr, alarmSuppressionKey, alarmProbeId, alarmUserTag1, alarmUserTag2, alarmSource, alarmOrigin, alarmTime, alarmTimezoneOffset, alarmNimId, alarmRobot, alarmDomain} DESCRIPTION "A NimBUS Alarm trap signifies that the sending SNMP application entity recognizes a NimBUS Alarm condition in its NimBUS Server" ::= 2 END ________________________________ * --To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected] * --To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected] --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
<<image001.png>>
NIMSOFT-Mib.MIB
Description: NIMSOFT-Mib.MIB
