Error messages
Error messages provide information about problems that occur while running the probe. You can use the information that they contain to resolve such problems.
The following table describes the error messages specific to this probe. For information about generic error messages, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide (SC14-7608).
Error |
Description |
Action |
|---|---|---|
| Could not init the buffer | The probe could not initialize the buffer on startup. |
Check the value specified for the NlmConfigGlobal EntryLimit property. |
| Error either the value is empty or nrc is not SUCCESS | Either the probe could not send a GET request to the IEMS server or it failed to extract the OID from the GET reply from the IEMS server. |
Check that the IEMS server is running correctly and received the GET request. |
Error when parsing the oid %s Expected varbind from get! |
The probe encountered a problem while parsing the event. |
Check that the IEMS server is running correctly. |
ExtractGenericGenband Alarm: NSProbeEventCreate failed GenerateIncrResynch Alert: NSProbeEventCreate failed Not enough memory |
The probe has received more alarms than it can store in the buffer file. |
Check the value specified by the TrapQueueMax property. Make more memory available. |
Exception value returned when attempting to do a GETNEXT: errorcode Invalid response to SNMP GETNEXT command |
The probe is attempting to get the active alarm index. The errorcode value will contain the system's error code. |
Check that the IEMS server is running correctly. |
ExtractGenericGenband Alarm 0: Error in issuing get req: errorcode ExtractGenericGenband Alarm 1: Failure when attempting to do SNMP GET ExtractGenericGenband Alarm 2: Error in issuing get req: errorcode |
The probe is attempting to get the varbinds of resynchronized alarms. Theerrorcode value will contain the system's error code. |
Check that the IEMS server is running correctly. |
GenerateResynchAlert: Failure when attempting to do SNMP GET GenerateResynchAlert: Error in issuing get req: %s GenbandIncremental Resynch: Error in issuing get req: ErrorcodeA seq_num: ErrorcodeB |
The probe is sending PDU messages to the IEMS system requesting a trap OID for an alarm resynchronization operation. The ErrorcodeA and ErrorcodeB values will contain system error codes. |
Check that the IEMS server is running correctly. |
| NSProbeEventSetElement (ReqId): errorcode | The probe failed to set an event token value. The errorcode value will contain the system's error code. |
Make more memory available. |
| Unable to create SNMP pdu | The probe failed to process the alarms. |
Check that Genband IEMS is running correctly. |
| Unable to open snmp session | The probe failed to connect to the Genband IEMS server. |
Check that Genband IEMS is running correctly. Check the values specified for
the following properties:
|
Unable to parse oid %s Unrecognized ASN1 type |
The probe cannot parse the alarm; this is probably because the alarm is not in a format that the probe can understand. |
Check that the Genband IEMS server is running correctly. Check the setting of the GenbandCVMVersion property matches the Genband IEMS version. Check the details in this file: $OMNIHOME/probes/arch/mttrapd.conf. |
| Unable to extract oid | When the probe started, it could not retrieve the existing alarms. |
Check that the Genband IEMS server is running currently. |
| Unexpected trap oid stored in nlmLogVariableTable discarding %s | The incoming data stream may be corrupt. |
Check that the ObjectServer is running correctly. |
| Warning: OID not increasing: %s >= %s\n | The probe is not receiving alarms from the Genband IEMS server. |
Check that the IEMS server is running correctly. |