|
|
|
The following messages are produced by the ENF/SNMP Monitor component.
Reason:
An SNMP session could not be created. This includes opening a socket and resolving the target host as specified in the ENF Event.
Action:
Verify the target host and examine any messages related to resolving the target host. This may involve DNR/DNS and IP issues. If you cannot resolve, contact CA Support.
Reason:
A send of the UDP packet containing the SNMP TRAP PDU failed.
Action:
The PDU was not properly built or the target host information was rejected by TCP/IP. Contact CA Support with the value of snmp_errno.
Reason:
An error occurred during the gethostname() function call when attempting to set the IPv4 address of the TCP/IP stack in the TRAP PDU.
Action:
The TCP/IP returned errno and errno_jr when the call failed. If the TCP/IP and TCPIP.DATA are operating correctly, contact CA Support with the values of errno and errno_jr.
Reason:
An error occurred during the gethostname() function call when the target host (host that receives the TRAP PDU) was not provided in the ENF Event.
Action:
The TCP/IP returned errno and errno_jr when the call failed. If the TCPIP and TCPIP.DATA are operating correctly, contact CA Support with the values of errno and errno_jr.
Reason:
An error occurred during the getaddrinfo() function call attempting to resolve the specified node name in order to set the IPv4 address. The message is indicated as an error, but the TRAP PDU is sent also. If the TCP/IP and TCPIP.DATA are operating correctly, contact CA Support.
Action:
The PDU was not properly built or the target host information was rejected by TCP/IP. Contact CA Support.
Reason:
The node name of the TCP/IP stack resolved to an IPv6 address that cannot be used in the SNMP V1 TRAP PDU (agent_addr field). Only IPv4 addresses are defined by the RFC.
Action:
A value of zero is returned and used as the IPv4 address. . The message is indicated as an error, but the TRAP PDU is sent also.
Reason:
The node name of the TCP/IP stack could not be resolved by getaddrinfo() into an IPv4 address to be used in the SNMP V1 TRAP PDU.
Action:
A value of zero is returned and used as the IPv4 address. The message is indicated as an error, but the TRAP PDU is sent also. If the TCP/IP and TCPIP.DATA are operating correctly, contact CA Support.
Reason:
An error occurred during the getaddrinfo() function call attempting to resolve the specified node name in order to determine the IP address of the target host (host that receives the TRAP PDU).
Action:
The TCP/IP set return code rc fails the call. A value of zero is returned and used as the IPv4 address. If the TCP/IP and TCPIP.DATA are operating correctly, contact CA Support.
Reason:
An error described by the string was found for the specified token on or near the specified line number.
Action:
Contact CA Support providing the string, token, and line number.
Reason:
An error described by the string was found on or near the specified line number.
Action:
Contact CA Support providing the string and line number.
Reason:
An attempt to abort a session failed.
Action:
Contact CA Support providing the reason why the session could not be aborted.
Reason:
A call to getaddrinfo() failed to resolve an IP address for the specified host name.
Action:
If the DNS/DNR is correctly configured, contact CA Support.
Reason:
Only IPv4 sockets can be opened, but the target host IP address resolved to an IPv6 address, which was not an IPv4-mapped IPv6 address.
Action:
If OMVS and TCP/IP are correctly configured, an IPv4 address must be available for the target host. For assistance, contact CA Support at http://ca.com/support.
During parsing, an ASN1 sequence symbol was encountered. The ASN1 sequence symbol is not supported.
Action:
Contact CA Support.
Reason:
Prior to sending the TRAP PDU, it was determined that the destination IP address is missing.
Action:
If other messages do not resolve this issue, contact CA Support.
Prior to sending the TRAP PDU, the call to build the packet indicated an error.
Action:
If other messages do not resolve this issue, contact CA Support.
While parsing the data passed in the ENF Event, too many variable arguments were detected.
Action:
Contact CA Support.
While parsing the data passed in the ENF Event, a variable type was specified but no value followed.
Action:
Contact CA Support.
Some previous specific error occurred.
Action:
Examine the output for a specific message relating to the construction of the variable list.
The CAICATD0001 environmental variable was set, but the value specifying the system defaults could not be resolved.
Action:
Contact CA Support with the value of rc.
The CAICATD0000 environmental variable was set, but the value specifying the Enterprise OID could not be resolved.
Action:
Contact CA Support with the value of rc.
An invalid OID/MIB number was detected.
Action:
Look up the code in the CATD_E_2xx series error messages. If the issue cannot be resolved from other messages, contact CA Support.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |