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 Netcool/OMNIbus error messages, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide.

Table 1. Error messages
Error	Description	Action
`Error: ipv6_address is not a valid address for Protocol protocol`	The IP address specified for the BindAddress property was not in IPv4 format and not valid for the specified protocol.	Check the value specified for the BindAddress property; if the Protocol property is set to TCP, UDP, ALL, or ANY, this IP address must be specified in IPv4 format.
`Error: ipv4_address is not a valid address for Protocol protocol`	The IP address specified for the BindAddress property was not in IPv6 format and not valid for the specified protocol.	Check the value specified for the BindAddress property; if the Protocol property is set to TCPV6, UDPV6, or ALLIPV6, this IP address must be specified in IPv6 format.
`Error: Unknown authentication protocol`	A user entry in the configuration file contains an unrecognized value for the authentication protocol	The preface to the message includes the line number in the configuration file that caused the error. Check that user entry to ensure that the authentication protocol is one of the supported types and that the protocol is specified in upper case.
`Failed to parse SNMP PDU, Version unrecognised!!!PDU command was invalid`	The probe failed to process the traps.	Check that the device is running correctly.
`get_enginetime() got less-than-zero engineID_len`	An incoming inform did not contain an engine ID. The user entry in the configuration file does not provide a default one to use.	Ensure that the SNMP agent includes an engine ID in its informs. Or add a default engine ID to the user record in the configuration file.
`IP token[ip_value] not usable in the Protocol setting [protocol], no insertion to the table`.	The probe has received a trap from a host using an IP protocol other than that specified by the Protocol property.	Change the setting of the Protocol property to match the traps that the probe is receiving. For further details refer to the Writing resolved host names and discarded host names to flat files.
`Line line_number: Probe's IP-Hostname pairs has reached the limit as configured in HostnameTableSize property. The current and all subsequent entries in the file will not be parsed.`	The internal table that the probe uses to hold IP-host name details has reached the maximum size specified by the HostnameTableSize property. So the current entry and all subsequent entries will not be parsed.	This message is for your information only. No action is required, but you may need to increase the value set for the HostnameTableSize property.
`Line line_number: Hostname token exceeds max length hostname_lentgh, the string is truncated.`	A host name retrieved following a DNS query exceeds 255 characters. The probe will truncate the host name, and only write the first 255 characters to the internal table.	This message is for your information only. No action is required.
`Cached IP-hostname list is full. No instantaneous and periodic hostname resolution to be done on IP[%s]`	The internal table that the probe uses to hold IP-host name details has reached the maximum size specified by the HostnameTableSize property. So the new IP address of the trap received by the probe cannot be written to the table.	This message is for your information only. No action is required.
`Line line_number IP tokenip_address not usable in the Protocol setting protocl_id.`	The probe received a trap from a node whose IP address does not match the format expected by the probe.	Check the value specified the Protocol property.
`Missing input to SNMPSET or SNMPGET request`	One or more arguments are missing from the nco_http command line when managing the SNMP agent through the probe's HTTP/ HTTPS interface.	Check the command and make sure it contains all of the required arguments as defined in Sending commands using nco_http.
`plaintextscopedPDU parsing returned NULL - Possible rootcause: decrypted text is incorrect in format.`	The privacy password in a trap or inform is incorrect.	Check that the password is correctly specified in the configuration file and that the SNMP agent is specifying the password correctly.
`Property ActiveHostnameDuration [%d] is not within valid range (%d - %d) mins. Default to value [%d]`	The ActiveHostnameDuration property has been set to an invalid value in the properties file. The probe is using the default value of 30 minutes instead.	Set ActiveHostnameDuration to a value between 5 and 10080 minutes.
`Property RefreshHostnameInterval [%d] is not within valid range (%d - %d) mins. Default to value [%d]`	The RefreshHostnameInterval property has been set to an invalid value in the properties file. The probe is using the default value of 60 minutes instead.	Set RefreshHostnameInterval to a value between 15 and 10080 minutes.
`Property HostnameTableSize [%d] is not within valid range (%d - %d). Default to value [%d`	The HostnameTableSize property has been set to an invalid value in the properties file. The probe is using the default value of 20000 entries instead.	Set HostnameTableSize to a value between 50 and 50000 entries.
`protocol not known`	An invalid protocol has been specified.	Check the value specified for the Protocol property.
`scopedPDU desperate parsing still returned NULL`	A trap or inform received from the SNMP agent contains an error in the specified authentication protocol, privacy type, authentication password, privacy password, or engine ID.	A subsequent message contains further indication of the reason for the error. Use that to determine the cause and to take corrective action.
`search_enginetime_list() error.`	An inform contained an unrecognized engine ID.	Ensure that the SNMP agent specifies the correct engine ID.
`UDP snmp_open: Unknown host (Address already in use)Failed to open UDP sessionUnable to get hold of session link pointer`	As another process is running on the port specified, it is not available for this session.	Specify a different port either using the command line, or using the Port property in the properties file.
`TRAP_FLOOD: IP=[ip_address] has [number_of_traps] entries in the queue. Dropping and discarding.`	The probe has dropped the host IP addressed identified in the message and marked it as blocked.	The number of traps queued for the IP address exceeded the maximum allowed.
`TRAP_FLOOD: IP=[ip_address] has sent [number_of_traps] traps in the last [number_of_seconds] seconds, rate = [traps_per_second] so remains banned.`	The probe is continuing to block the host identified in the message.	The probe checked the blocked host to determine whether the number of traps received by the host has slowed, but found that it has not.
`TRAP_FLOOD: IP=[ip_address] has only sent [number_of_traps] traps in the last [number_of_seconds] seconds, rate = [traps_per_second] so is being allowed again. )`	The probe is unblocking the host identified in the message.	The probe checked the blocked host to determine whether the number of traps received by the host has slowed. As the number has slowed, the probe is no longer blocking the host.
`TRAP_FLOOD: IP=[ip_address] ban ending, enabling.`	The probe has now marked the host identified in the message as no longer blocked.	The probe unblocked the host.
`TRAP_FLOOD_REPORT_START at [time] with [number_of_traps] traps in the queue.`	Indicates the start of the periodic Trap Flood Report.	This messages is for information only. No action is required.
`TRAP_FLOOD_REPORT_HOST: ip=[ip_address] status=[DROP] since [number_of_seconds] seconds. inqueue=[number_of_traps] nosdrop=[number_of_traps _dropped]`	Indicates that the specified host is blocked.	This messages is for information only. No action is required.
`TRAP_FLOOD_REPORT_HOST: ip=[ip_address] status=[ACCEPT] inqueue=[number_of_traps] nosdrop=[number_of_traps _dropped]`	Indicates that the previously blocked host is now unblocked.	This messages is for information only. No action is required.
`TRAP_FLOOD_REPORT_END at [time]`	Indicates the end of the periodic Trap Flood Report.	This messages is for information only. No action is required.
`TrapStat is disabled.`	The TrapStat property is set to `0`.	If you want to use the trap flood monitoring functionality, set the TrapStat property to `1`. Otherwise, leave the TrapStat property set to `0`.