Chapter 114 TCI (TCP/IP) Messages

The messages in this chapter are sent by the Transmission Control Protocol/Internet Protocol (TCP/IP) subsystem. The subsystem ID displayed by TCP/IP messages includes ZTCI as the subsystem name.




	NOTE: Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message that is not described in this chapter, see Chapter 15.

CAN'T MALLOC size BYTES FOR MBUFS

size

is the number of bytes of memory that the TCP/IP subsystem has tried to allocate to memory buffers (MBUFs).

Cause The internal memory allocation of MBUFs failed. An attempt was made to allocate memory to MBUFs, but the size specified was larger than the amount available.

Effect Data transfer might be slower or might fail when memory cannot be allocated for data structures.

Recovery Contact the Global Mission Critical Solution Center (GMCSC).

DEVICE READ ERROR errnum ON IOP iopname




	NOTE: This message is applicable to D-series RVUs only.

`errnum`	is the file-system error that has occurred.
`iopname`	is the name of the Tandem LAN Access Method (TLAM) port being accessed by the TCP/IP process for transmitting and receiving data when the READ operation failed.

Cause A READ operation to the TLAM I/O process (MLAM) failed.

Effect MLAM might close if too many failures or certain critical failures occur. If this error results in MLAM being closed, the TCP/IP process attempts to reopen MLAM at one-minute intervals.

Recovery The TCP/IP process automatically attempts to reopen the IOP when it is closed as a result of an error. If successful, operator intervention is not required. However, if the reopen fails, the operator must check the #IP port or #ARP port (for Ethernet) to verify that the problem is not at the port level. See Appendix B, for information on the specified error.

DEVICE WRITE ERROR errnum ON IOP iopname




	NOTE: This message is applicable to D-series RVUs only.

`errnum`	is the file-system error that has occurred.
`iopname`	is the name of the Multilan Access Method (MLAM) port being accessed by the TCP/IP process for transmitting and receiving data when the WRITE operation failed.

Cause A WRITE operation to the TLAM I/O process (MLAM) failed.

Effect MLAM might close if too many failures or certain critical failures occur. If this error results in MLAM being closed, the TCP/IP process attempts to reopen MLAM at one-minute intervals.

Recovery The TCP/IP process automatically attempts to reopen the input/output process (IOP) when it is closed as a result of an error. If successful, intervention is not required. However, if the reopen fails, check the #IP port or #ARP port (for Ethernet) to verify that the problem is not at the port level. See Appendix B, for information on the specified error.

ERROR errnum ON IOP iopname

`errnum`	is the file-system error that has occurred.
`iopname`	contains the name of the Multilan Access Method (MLAM) port being accessed by the TCP/IP process for transmitting and receiving data when the error occurred.

Cause An error occurred while the TCP/IP process was waiting for an I/O operation to complete on the MLAM. This error is returned only if the TCP/IP process called the AWAITIO procedure and the operator aborted a port while the TCP/IP process had the port opened.

Effect This can cause MLAM to be closed if too many failures or certain critical failures occur. If this error results in MLAM being closed, the TCP/IP process attempts to reopen MLAM at one-minute intervals.

Recovery The TCP/IP process automatically attempts to reopen the IOP when it is closed as a result of an error. If successful, intervention is not required. However, if the reopen fails, check the #IP port or the #ARP port (for Ethernet) to verify that the problem is not at the port level.

See Appendix B, for information on the specified error.

SUBNET subname IOP iopname CHANGED FROM old-state TO new-state BECAUSE OF cause

`subname`	is the name of the TCP/IP subnet that is the subject of this message.
`iopname`	is the name of the X25AM line and subdevice (for X.25 subnets) or, for D-series RVUs only, the TLAM line and port (for Ethernet and SNAP subnets) being accessed by the TCP/IP process for transmitting and receiving data when the summary state change occurred.
`old-state`	is the summary state of the object before the change took place.
`new-state`	is the summary state of the object after the change has taken place.
`cause`	is the reason the summary state has changed.

Cause A command or error occurred that affected the summary state of a TCP/IP subnet.

Effect The summary state of TCP/IP subnet subname changed from old-state to new-state.

Recovery If a command caused the summary-state change, no corrective action is needed. If the state changed for any other reason, note any other error messages returned and contact ythe Global Mission Critical Solution Center (GMCSC), providing all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

TCPIP NO LONGER OPERATIONAL cause

cause

is the reason that the TCP/IP process is no longer operational.

Cause The TCP/IP process detected an internal error from which it could not recover.

Effect The TCP/IP process no longer exists.

Recovery Restart the TCP/IP process using the RUN command with SAVEABEND ON. Contact the Global Mission Critical Solution Center (GMCSC), providing all relevant information as follows:

The saveabend file for HP to analyze
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

ARP: DUPLICATE IP ADDRESS ip-addr FROM ETHERNET ADDRESS enet-addr

`ip-addr`	is the duplicate IP address.
`enet-addr`	is the Ethernet address of the other machine that is broadcasting a duplicate internet (IP) address.

Cause The Address Resolution Protocol (ARP) module of the TCP/IP process has detected that another machine on the network is broadcasting the same IP address.

Effect If this were to continue, each of the two machines might get packets intended for the other and would function improperly.

Recovery Determine which machine is broadcasting incorrectly and reassign a unique IP address to it.

ARP: ETHERNET BROADCAST ADDRESS (FF.FF.FF.FF.FF.FF) USED BY IP ADDRESS ip-addr

ip-addr

is the internet (IP) address of the machine using the broadcast address as its Ethernet address.

Cause The Address Resolution Protocol (ARP) module of the TCP/IP process has detected that another machine on the Ethernet LAN is using the broadcast address FF.FF.FF.FF.FF.FF as its Ethernet address.

Effect This causes all packets sent to the broadcast address to be received by all machines on the Ethernet LAN. Performance of all machines is adversely affected. In addition, some implementations of TCP/IP might try to forward the packets back over the Ethernet LAN, flooding the LAN and crashing most machines on the LAN.

Recovery Determine which machine is using the broadcast address as its Ethernet address and fix the machine. Note that you cannot reassign an Ethernet address.

NUMBER OF X25AM DEVICES AVAILABLE num-devices

num-devices

is the number of X25AM subdevices opened by the TCP/IP process.

Cause Either the operator has opened all the subdevices added to X25AM, or X25AM does not let the operator access subdevices.

Effect The TCP/IP process cannot open any more X25AM subdevices.

Recovery If the number of subdevices opened is less than the number that have been added to X25AM, then the operator should check X25AM to determine why these devices cannot be accessed. If the number of subdevices opened is equal to the number that have been added to X25AM, then this message is informational only; no corrective action is needed.

CONNECTION ESTABLISHED WITH ip-addr

ip-addr

is the internet (IP) address of a remote TCP/IP host with which a connection is established.

Cause An X.25 connection was established to a remote TCP/IP host located at address ip-addr.

Effect An X.25 connection was established with a remote TCP/IP process.

Recovery Informational message only; no corrective action is needed.

CONNECTION WITH ip-addr TIMED OUT

ip-addr

is the internet (IP) address of the remote TCP/IP host with which the connection timed out.

Cause An X.25 connection to the remote host located at address ip-addr timed out.

Effect An X.25 connection to a remote host was deleted. If no free devices were available, at least one device is now available for new connections.

Recovery Informational message only; no corrective action is needed.

NO DEVICES AVAILABLE TO MAKE CONNECTION TO HOST ip-addr

ip-addr

is the internet (IP) address of a remote TCP/IP host for which no devices are available for connection.

Cause The X.25 connection to the remote host located at address ip-addr could not be established because no free devices were available. All the connections that have been established are active.

Effect None

Recovery An X.25 connection to a remote host cannot be established until an existing connection times out.

SYNTAX ERROR ON LINE line-num FILE filename

`line-num`	is the number of the line where the syntax error occurred.
`filename`	contains the name of the file where the syntax error occurred.

Cause The IP-to-X.25 address file, filename, contains a syntax error on line line‑num.

Effect The line containing the error is not executed.

Recovery Correct the syntax error and restart the process.

CONFIGURATION FILE filename ACCESS ERROR

filename

is a configuration file that cannot be accessed for the Simple Mail Transfer Protocol (SMTP) or the domain name server.

Cause The configuration file, filename, is secured incorrectly. This error is generated by either the SMTP or the domain name server.

Effect The SMTP or domain name server exits and the TCP/IP process terminates.

Recovery Secure the file so that it can be read by the person starting the TCP/IP process, and restart the process that detected the error.

SYNTAX ERROR IN FILE filename LINE line-num

`filename`	contains the name of the file where the syntax error occurred.
`line-num`	contains the number of the line where the syntax error occurred.

Cause The Simple Mail Transfer Protocol (SMTP) or the domain name server received a syntax error on line line-num of configuration file filename.

Effect The line containing the error is ignored.

Recovery Correct the syntax error and restart the process that detected the error.

LISTNER: ERROR new-proc-err STARTING NEW-PROCESS FILE filename

`new-proc-err`	indicates the NEWPROCESS or PROCESS_CREATE_ error that has occurred.
`filename`	contains the name of server that could not be started.

Cause The LISTNER process’s attempt to start a new server failed.

Effect The server is not started, and the user initiating the request is notified.

Recovery See Appendix C, or Appendix D, for a description of error new-proc-err. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. Correct the error in filename and restart the LISTNER process.

SMTP: TRANSFER UOW REQUEST xfer-uow ERROR xfer-err, DETAIL detail

`xfer-uow`	identifies the unit of work that could not be processed.
`xfer-err`	is the Transfer error code.
`detail`	reports any additional error information.

Cause The Simple Mail Transfer Protocol (SMTP) received an error during a Transfer request.

Effect The transfer is incomplete.

Recovery See the Transfer Programming Guide for recovery information and for information on the three Transfer variables shown in the message.

ERROR IN PARAMETER SPECIFIED IN FILE filename LINE line-num

`filename`	contains the name of the file where the parameter error occurred.
`line-num`	contains the number of the line where the parameter error occurred.

Cause The Simple Mail Transfer Protocol (SMTP) or the domain name server received a parameter error on line line-num of configuration file filename.

Effect The line containing the error is ignored.

Recovery Correct the parameter error and restart the process that detected the error.

Error in Address/Name specified in file filename line line-num

`filename`	contains the name of the file where the parameter error occurred.
`line-num`	contains the number of the line where the parameter error occurred.

Cause A configuration file contains a parameter error. This message is generated by SMTP or the Domain Name Server.

Effect The line containing the parameter error is not executed.

Recovery Correct the syntax error and restart the process that detected the error.

Error errnum in socket operation socket-function

`errnum`	contains the number of the error that has occurred.
`socket-function`	identifies the socket operation that was being performed when the error occurred.

Cause An error occurred in a Tandem application during a socket operation.

Effect The application stops abnormally (an abend occurs).

Recovery Contact the Global Mission Critical Solution Center (GMCSC), providing all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable.

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Error in protocol specified in file filename line line-num

`filename`	contains the name of the file where the parameter error occurred.
`line-num`	contains the number of the line where the parameter error occurred.

Cause A configuration file contains a parameter error. This message is generated by SMTP or the Domain Name Server.

Effect The line containing the parameter error is ignored.

Recovery Correct the syntax error and restart the process that detected the error.

Open of $Receive failed in the TCP/IP process, err errnum

errnum

is the file-system error that occurred. See Appendix B, for information on the specified error.

Cause The TCP/IP process could not open $RECEIVE.

Effect The TCP/IP process stops.

Recovery Restart the TCP/IP process.

inIT_buf: SSINIT failed err errnum

errnum

is the file-system error that occurred. See Appendix B, for information on the specified error.

Cause There is an SCF-interface related problem.

Effect None

Recovery Determine the problem in the SCF interface, correct it, and reissue the SCF command.

en unit-num: can't handle af proto-num

`unit-num`	contains the unit number of the interface being used.
`proto-num`	contains the protocol number.

Cause The wrong protocol was used. The protocol number specified is not supported. The subsystem supports only AF_INET.

Effect The error EAFNOSUPPORT is generated.

Recovery The application must reissue the request using the valid protocol number.

in_cksum: out of mbufs..

Cause TCP/IP could not get enough buffer space for the request.

Effect The TCP/IP statistics buffer for bad checksum is incremented.

Recovery The TCP/IP protocol handles the recovery; no user recovery action is necessary.

SCPTRACE-STOP error errnum

errnum

is the file-system error that occurred. See Appendix B, for information on the specified error.

Cause A TCP/IP call to DSM_TRACE_ failed. This might happen if a STOP command is issued for a trace that is already in the STOPPED state.

Effect There is a problem in stopping the trace.

Recovery Recovery depends on the trace collector. If the reason for the trace failure can be corrected, the operation may be retried.

sn_init_buf: SSINIT Failed err errnum

errnum

is the file-system error that has occurred. See Appendix B, for information on the specified error.

Cause There is an SCF-interface related problem.

Effect None

Recovery Determine the problem in the SCF interface, correct it, and reissue the SCF command.

allocating new cluster mbufs PANIC

Cause TCP/IP could not allocate buffer space for processing the request.

Effect TCP/IP stops abnormally (an abend occurs).

Recovery The TCP/IP backup process continues operation. If there is no backup process, restart the TCP/IP process.

sched_socket: run_sock non-zero socket-num

socket-num

contains the current value of the run_sock variable.

Cause After scheduling all sockets, TCP/IP still had a socket left in a queue.

Effect TCP/IP stops abnormally (an abend occurs).

Recovery The TCP/IP backup process continues operation. If there is no backup process, restart the TCP/IP process.

TCP/IP process has no backup, err errnum

errnum

is the file-system error that occurred. See Appendix B, for information on the specified error.

Cause The processor in which the backup process was running has gone down.

Effect None

Recovery Informational message only; no corrective action is needed. TCP/IP will restart the backup process when the processor is reloaded.

Invalid backup CPU number for TCP/IP process, err errnum

errnum

is the file-system error that occurred. See Appendix B, for information on the specified error.

Cause An invalid backup processor number was specified in the RUN command.

Effect TCP/IP stops abnormally (an abend occurs).

Recovery Restart the TCP/IP process using a valid backup processor number.

Can not start TCP/IP backup process, err errnum

errnum

is the file-system error that occurred. See Appendix B, for information on the specified error.

Cause The TCP/IP process could not start its backup process.

Effect The TCP/IP process tries to restart its backup process, based on an ever-increasing delay with a maximum value of 10 minutes.

Recovery Informational message only; no corrective action is needed.

TCP/IP backup process abended, attempting recovery in time-count seconds.

time-count

contains the amount of time, in seconds, after which the TCP/IP process will attempt to restart its backup process.

Cause The TCP/IP backup process stopped abnormally (an abend occurred) due to an internal inconsistency.

Effect The TCP/IP process will attempt recovery.

Recovery Informational message only; no corrective action is needed.

TCP/IP backup process started

Cause The TCP/IP process successfully started its backup process.

Effect None

Recovery Informational message only; no corrective action is needed.

Connection Established with source-IPaddress Using Gateway gateway-ipaddress

`source-ipaddress`	contains the internet (IP) address of the source of the connection.
`gateway-ipaddress`	contains the internet (IP) address of the gateway being used for the connection.

Cause An X.25 connection was established to a remote TCP/IP host.

Effect None

Recovery Informational message only; no corrective action is needed.

CHECKPOINT FAILED Error errnum, attempting to restart backup process.

errnum

is the file-system error that occurred. See Appendix B, for information on the specified error.

Cause A TCP/IP process checkpoint failed.

Effect The backup process is no longer considered operational.

Recovery The TCP/IP process will attempt to restart the backup process.

No backup CPU specified for TCP/IP process.

Cause The TCP/IP process was started without specification of a backup processor.

Effect None

Recovery Informational message only; no corrective action is needed.

QIO Error errnum on IOP iopname

`errnum`	is the QIO-subsystem operator error that occurred.
`iopname`	is the name of the QIO process.

Cause A QIO driver error has occurred.

Effect None

Recovery Informational message only; no corrective action is needed. The TCP/IP process will close and attempt to reopen the I/O process once every second. If the TCP/IP process cannot be reopened, attempt to correct the QIO driver error and restart the TCP/IP process. See the SCF Reference Manual for QIO for information on the specified operator error.

Subnet subnet-name QIO Driver Mode On




	NOTE: This message is applicable for D-series RVUs only.

subnet-name

is the name of the subnet.

Cause The TCP/IP subnet has entered QIO direct mode to the controller.

Effect None

Recovery Informational message only; no corrective action is needed.

Subnet subnet-name QIO Driver Mode Off




	NOTE: This message is applicable for D-series RVUs only.

subnet-name

is the name of the subnet.

Cause The TCP/IP subnet has entered QIO nondirect mode to the controller.

Effect None

Recovery Informational message only; no corrective action is needed.

QIOLIMIT Value Invalid, Using 100

Cause The QIOLIMIT run-time parameter value specified is invalid.

Effect The TCP/IP process defaults to a value of 100.

Recovery Informational message only; no corrective action is needed.

Error error on LIF lif-name

Cause A LIF driver error has occurred.

Effect Provided for information only.

Recovery The TCP/IP process closes and attempts to reopen the LIF object.

COULD NOT CREATE QIO QUEUE for subnet <subnet-name>, error error.

Cause A QIO error has occurred.

Effect The add of a subnet has failed.

Recovery Correct the problem with the QIO subsystem and retry the operation.

LIF lif-name not in STARTED state in CPU x.

Cause A LIF interface state change has occurred.

Effect Provided for information only.

Recovery The TCP/IP process closes and attempts to reopen the LIF object.

LIF lif-name Access down in CPU x.

Cause A LIF access state change has occurred.

Effect Provided for information only.

Recovery The TCP/IP process closes and attempts to reopen the LIF object.

Contains the text of the message being reported.

Cause Depends on the message text.

Effect Provided for information only.

Recovery No recovery necessary.

Primary TCP/IP Process switching to CPU x.

Cause The TCP/IP process is giving ownership to its backup process. An SCF PRIMARY command or a loss of all LAN access for all non-supported subnets causes this switch.

Effect The backup TCP/IP process takes over as the primary CPU.

Recovery The TCP/IP process attempts to reopen all active LAN interfaces.

TCP/IP Process stopped by operator.

Cause An SCF ABORT or STOP command has been issued.

Effect Provided for information only.

Recovery No recovery necessary.

Maximum CPU switches attempted, operator intervention may be required

Cause The TCP/IP process has switched CPUs six times trying to recover access to the LAN subsystem without success.

Effect Provided for information only.

Recovery Operator intervention may be required to solve the LAN access problems and the TCP/IP process may have to be moved to its backup CPU when LAN access problems are resolved.

Subnet subnet-name LIF filter register timeout.

Cause The TCP/IP process did not receive a response to a LIF filter register command within 10 seconds of issuing the command.

Effect The TCP/IP process attempts the command again.

Recovery The TCP/IP process attempts to complete this operation until successful or the subnet is stopped.

Configuration Error on Subnet subnet-name, LIF lif-name access not possible through current primary and/or backup process.

Cause The device (LIF) on which the subnet is configured is not accessible from the same CPUs as the TCP/IP process.

Effect The ADD of the subnet fails.

Recovery Select a device for the subnet that is configured in the same CPUs as the TCP/IP process; or stop and restart the TCP/IP process in the same CPUs as the device.

LIF lif-name access unavailable from cpu number.

Cause The current data path to the device is unavailable from the process’ primary CPU.

Effect If you are adding a subnet, the ADD fails. If this occurs during normal operations and if the LIF is accessible from the TCP/IP process’ backup CPU, the TCP/IP process attempts to switch CPUs.

Recovery When adding a subnet, select a device (LIF) that is configured and has the data path in the same CPU as the TCP/IP process. During normal operations this is provided for information only.

Deregister error on LIF lif-name.

Cause An error has occurred on a LIF De-Register command.

Effect Provided for information only.

Recovery The TCP/IP process attempts to reopen the LIF object.

Error error in sending to Agent in CPU nn

Cause An internal error has occurred that has caused a message system error on I/O to the Transport Agent.

Effect All open sockets using the Transport Agent are closed.

Recovery Use the DIVER command to stop the processor on which the Transport Agent is running and restart the processor.

Unable to allocate memory for Agent in CPU nn

Cause A data structure for the Transport Agent could not be allocated because QIO does not have enough memory.

Effect Applications running on the Transport Agent’s processor cannot open sockets.

Recovery Stop the TCP/IP process and use QIOMON to increase QIO memory, or create a socket at a later time when sufficient memory has been freed.

Unable to locate Agent by phandle, error n

n

is one of the following numbers:

Unable to decompose Transport Agent’s process handle
Unable to find Transport Agent’s process handle in internal tables
Process handle used by Transport Agent does not match stored process handle

Cause The Transport Agent could not be located by process handle for the reason associated with the number displayed.

Effect All open sockets using the Transport Agent are closed.

Recovery Use the DIVER command to stop the processor on which the Transport Agent is running and restart it.

Invalid aggregate message from Agent in CPU nn

nn

is the processor number of the Transport Agent that sent an invalid aggregate message.

Cause An internal error has caused the Transport Agent to send an invalid aggregate message.

Effect All open sockets using the Transport Agent are closed.

Recovery Use the DIVER command to stop the processor on which the Transport Agent is running and restart it.

Unable to allocate reply MD

Cause Unable to allocate an MD for a reply buffer.

Effect OSS sockets cannot be created.

Recovery Abort the TCP/IP process and reconfigure QIO for more memory.

Unknown device lif-name

Cause The TCP/IP process could not locate the LIF selected for a subnet.

Effect Provided for information only.

Recovery Retry the subnet ADD on a correct device.

Device dev-name returned a NULL MAC Address.

Cause The device selected for a subnet returned a NULL MAC address.

Effect Provided for information only.

Recovery Retry the subnet ADD once the problem with the device is corrected.

Duplicate IP address with different ATM address.

Cause An ARP request has been received with the source IP address equal to the subnet’s but with a different source ATM address.

Effect Provided for information only.

Recovery The operator should determine which machine has the same address and reassign a unique IP address to it.

Duplicate ATM address with different IP address.

Cause An ARP request has been received with the source ATM address equal to the subnet’s but with a different source IP address.

Effect Provided for information only.

Recovery Determine why another system seems to have the same ATM address and take corrective action.

Registered to ARP server.

Cause An ATM subnet has registered to an ATM ARP server.

Effect Provided for information only.

Recovery None

ATM API Connect error to ARP server.

Cause An ATM subnet has had an error on an ATM API Connect call to an ATM ARP server.

Effect Provided for information only.

Recovery The TCP/IP process delays and retries establishing the connection to the ARP server. If more than one server has been configured, the TCP/IP process tries the next server on its list.

Timed out connecting to ARP server.

Cause The ATM ARP server is unavailable.

Effect Provided for information only.

Recovery The TCP/IP process retries establishing the connection to the ARP server. If more than one server has been configured, the TCP/IP process tries the next server on its list. If this error continues, the operator may need to check the status of the ATM subsystem or ATM ARP server.

Timed out registering to ARP server.

Cause The ATM ARP server failed to respond to a subnet’s ATM ARP register request.

Effect Provided for information only.

Recovery The subnet retries registering with the ATM ARP server. If this error continues, check the status of the ATM subsystem or ATM ARP server.

ATM API Connect error to ATM address.

Cause The ATM API returned an error on an ATM API Connect call.

Effect Provided for information only.

Recovery If this error continues, take action depending on the returned error.

ATM API Create endpoint error.

Cause The ATM API returned an error on an ATM API Create Endpoint call.

Effect Provided for information only.

Recovery If this error continues, take action depending on the returned error.

ATM API Set call options error.

Cause The ATM API returned an error on an ATM API Set Call Options call.

Effect Provided for information only.

Recovery If this error continues, take action depending on the returned error.

ATM API Accept call error.

Cause Problems with the ATM subsystem.

Effect Provided for information only.

Recovery If this error continues, take action depending on the returned error.

No memory for ATM address entry.

Cause Insufficient memory available for configuration.

Effect Provided for information only.

Recovery The operator may need to take corrective action to ensure enough memory is available in the processor running the TCP/IP process.

ATM API connect timed out.

Cause Destination ATM address is unavailable.

Effect Provided for information only.

Recovery If this error continues, take action depending on the returned error.

ATM API Set Call Options timed out.

Cause The ATM API subsystem failed to complete the command.

Effect Provided for information only.

Recovery If this error continues, take action depending on the returned error.

ATM API error on API Send.

Cause A problem with the ATM subsystem

Effect Provided for information only.

Recovery If this error continues, take action depending on the returned error.

ATM API Listen error.

Cause Problems with the ATM subsystem.

Effect Provided for information only.

Recovery If this error continues, take action depending on the returned error.

ATM API Bind PVC error.

Cause A problem with the ATM subsystem.

Effect Provided for information only.

Recovery If this error continues, take action depending on the returned error.

Filter register error.

Cause The Ethernet LIF rejected the filter registration.

Effect Provided for information only.

Recovery If this error continues, take action depending on the returned error.

Filter register timed out.

Cause The Ethernet adapter did not respond to a filter registration request.

Effect Provided for information only.

Recovery If this error continues, take action depending on the returned error.

Filter already in use.

Cause Another subnet was already added using the same IP address.

Effect Provided for information only.

Recovery Either select a different IP address or determine why another subnet is using the same address.

Default filter already in use.

Cause The default filter is already assigned to another subnet.

Effect Provided for information only.

Recovery Delete, then re-add the subnet with the GATEWAY option off.

Filter de-register error.

Cause The Ethernet adapter rejected the filter de-register.

Effect Provided for information only.

Recovery If this error continues, take action depending on the returned error.

Possible Denial-of-Service attack.

Cause The TCP/IP subsystem receives a flood of data segments destined for a non-existent connection from one or more IP addresses.

Effect This is a warning message.

Recovery If this error continues, the TCP/IP subsystem will generate an EMS message once every five minutes displaying up to three IP addresses, which are contributing to the flood. The TCP/IP trace will display the logical interface (LIF) and all the IP addresses from which the flood of data segments is arriving to a non-existent connection. Locate the network elements using these IP addresses and disconnect them from the network.