The following messages are produced by the CAIENF/SNMP component.
Reason:
Unable to load the requested SAPI DLL.
Action:
Check that the eTrust library contains the members that are needed.
Reason:
Abnormal condition detected by UNIX System Services.
Action:
Investigate the cause of the signal.
Reason:
Informational.
Action:
No action is required.
Reason:
Informational.
Action:
No action is required.
Reason:
Informational.
Action:
No action is required.
Reason:
Informational.
Action:
No action is required.
Reason:
The security API library does not contain needed DLLs.
Action:
Check that the library in use is correct.
Reason:
The initialization routine has failed.
Action:
Record the error code and contact CA Support.
Reason:
The getaddrinfo function failed to return a known host.
Action:
Check your network host names and connections.
Reason:
Routing to the hostname was unsuccessful.
Action:
Check the network connections.
Reason:
Informational.
Action:
No action is required.
Reason:
Informational. Neither CA ACF2, CA Top Secret, nor RACF was specified.
Action:
No action is required. Processing continues.
Reason:
Informational.
Action:
No action is required.
Reason:
Informational.
Action:
No action is required. Processing continues without SAPI.
Reason:
Unable to create a new SAPI message.
Action:
Processing continues. The error indicated by the RC (security doc describes RC) should be corrected in order for this new message to succeed in the future.
Reason:
Syntax error in SAPIDATA strings.
Action:
Correct the error and resubmit.
Reason:
Message submission failed.
Action:
Examine the security API RC and the remote rc.
Reason:
Message removal failed.
Action:
Examine the security API RC for the failure reason.
Reason:
Adding string item failed.
Action:
Examine the security API RC for the failure reason.
Reason:
Adding integer item failed.
Action:
Examine the security API RC for the failure reason.
Reason:
The security API library was not found or was not APF authorized. Processing continues without SAPI support.
Action:
Authorize the library if SAPI support is needed. If not, no action is required.
Reason:
The IP address for target node of SNMP packet send is not constructed correctly.
Action:
Correct the IP address.
Reason:
The TCPIP stack specified by the IP_STACK=xxxx parm in the environment variables for ENFSNMPM is either not valid or not active.
Action:
Correct the IP_STACK parm to point to a valid, or active TCPIP and restart ENFSNMPM. ENFSNMPM will use the default stack.
Reason:
ENFSNMPM encountered error ###### attempting SETIBMOPT for the TCPIP stack specified in the IP_STACK= variable.
Action:
Correct the IP_STACK parm to point to a valid or active TCPIP, then restart ENFSNMPM. ENFSNMPM will use the default stack.
Reason:
ENFSNMPM encountered an error attempting SETIBMOPT for the TCPIP stack specified in the IP_STACK= variable.
Action:
Correct the IP_STACK parm to point to a valid or active TCPIP and restart ENFSNMPM. ENFSNMPM will use the default stack.
Reason:
Routing to the fixed port number was unsuccessful.
Action:
Check the port number usage.
Reason:
Informational.
Action:
No action is required.
Reason:
Error from call to gethostname(). The errno is decimal and errno2 is hexadecimal.
Action:
SAPI processing continues.
Reason:
Name ‘name’ is the hostname provided. The rc is in decimal.
Action:
SAPI processing continues.
Reason:
The number of variables comprising the variable bindings exceeds the maximum allowed.
Action:
The trap is not sent.
Reason:
A variable binding specified a type but no value.
Action:
The trap is not sent.
Reason:
Error from call to gethostname(). The errno is decimal and errno2 is hexadecimal.
Action:
The agent-addr field in the trap is set to zero.
Reason:
Node ‘name’ is an IPv6 address but the agent-addr field is defined to be an IPv4 address.
Action:
The agent-addr field in the trap is set to zero.
Reason:
Name ‘name’ is the hostname provided. The rc is in decimal.
Action:
The agent-addr field in the trap is set to zero.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |