SPECTRUM fails to compile PAM MIB file with HTTP Error

Products

• CA Privileged Access Manager - Cloakware Password Authority (PA)
• CA Privileged Access Manager (PAM)
• CA Spectrum

Issue/Introduction

Why does Spectrum fail to import/compile PAM's MIB file?
Why does it throw HTTP error?

Environment

PAM versions below 3.2.4

Resolution

The reason why Spectrum throws HTTP Error is because there is a problem in the PAM's MIB file.
The top section of the MIB file will include certain standard MIB files.
Then whatever is not available in the referenced MIB files must be declared in the PAM's MIB file itself.

IMPORTS     MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP         FROM SNMPv2-CONF     Integer32, MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY,     OBJECT-TYPE         FROM SNMPv2-SMI     DisplayString, TEXTUAL-CONVENTION         FROM SNMPv2-TC     TEXTUAL-CONVENTION, DateAndTime         FROM SNMPv2-TC     ;

Then the PAM's MIB file need to explain the identity of this PAM product and its vendor.
In the below section, "Xceedium, Inc" is the vendor and the vendor code is 10449.

xceedium MODULE-IDENTITY     LAST-UPDATED  "201609280344Z" -- September 28, 2016     ORGANIZATION         "Xceedium, Inc."     CONTACT-INFO         "Postal: Xceedium, Inc.          2214 Rock Hill Road, Suite 100          Herndon, VA 20170          Web site: http://www.xceedium.com/"     DESCRIPTION         "Xceedium generic MIB"     ::= { 1 3 6 1 4 1 10449 }

After this there are declaration of OID and its alarms and notifications.
Starting from OID "1.3.6.1.4.1.10449.5xx" as well as "1.3.6.1.4.1.10449.6xx" there are OBJECTS that are not defined but referenced.

gkAlarmStartup NOTIFICATION-TYPE     OBJECTS {    AlarmID,         AlarmName,         AlarmTime,         AlarmSeverity,         AlarmObject,         AlarmProbableCause,         AlarmInformation }     STATUS        current     DESCRIPTION         "Xsuite is starting up."     ::= { xceediumNotifications 500 }

As you can see above, there are "AlarmID", "AlarmName" and so on that are not defined anywhere in the IMPORT'ed MIB files nor in the PAM's MIB file itself.
This causes the Spectrum to fail.

But some other 3rd party MIB tools may compile or import just fine depending on how relax they are or fail if they are strict.

Starting from PAM 3.2.4, a new MIB file is released.

gkAlarmStartup NOTIFICATION-TYPE     OBJECTS {    gkAlarmId,         gkAlarmName,         gkAlarmEventTime,         gkAlarmPerceivedSeverity,         gkAlarmObject,         gkAlarmProbableCause,         gkAlarmInformation }     STATUS        current     DESCRIPTION         "Xsuite is starting up."     ::= { xceediumNotifications 500 }

gkAlarmId OBJECT-TYPE         SYNTAX      Integer32 (0..2147483647)         MAX-ACCESS  read-only         STATUS      current         DESCRIPTION                 "This object uniquely identifies an entry in the                  Alarm Table. It increases every time a new alarm                  occurs. Due to cleared alarms the index will not be                  contiguous. When the maximum is reached of                  Integer32, the value of this object rolls over to 1.                  The actor must use 'alarmEventTime' to sort on                  chronological order.                    The alarmId object is read-only even though it                  is used as index in the Alarm Table. The reason is                  that this facilities a convenient way to extract                  the corresponding value from a notification where                  the object is included."     ::= { xceediumNotifications 404 }

As you can see above, the OID "1.3.6.1.4.1.10449.500" references different OBJECTS and also you can find that they are defined.

Upgrade to PAM 3.2.4 or above and use the new MIB file.