Installation guide

20-5
Messages 300 – 399
Local -323- Telnet listener failed to get a socket
Explanation: The access server was unable to enable the Telnet listener due to memory
problems.
Local -324- Telnet listener failed to bind socket
Explanation: The software could not bind the socket (in a TCP system call) for one of the
following reasons:
• The access server does not have an Internet address defined. This message is always
generated for listener 23 upon factory initialization.
• You attempted to SET TELNET LISTENER CONNECTION ENABLE or CLEAR
TELNET LISTENER within several minutes of the listener having been in use and
disconnected. A timer on the listener prevents reenabling for several minutes following
a disconnection.
Local -325- Telnet listener failed to listen on socket
Explanation: The access server was unable to enable the Telnet listener because the
access server Internet address has not been set.
Action: Set the Internet address. See the section Ve ri fy Internet Address (Chapter 3).
Step Action
1 If every port on your access server is only intended for Telnet use, enter the
following command:
Local> CHANGE SERVER NODE LIMIT 1
2 This command prevents the access server memory from being filled with LAT
service node information.
3 Verify access server memory usage. See the section Verify Access Server Memory
Usage
(Chapter 2).
Step Action
1 If this message is generated after initialization, you should use the
DEFINE/SET/CHANGE command with the Internet address, DISABLE the listener,
and ENABLE the listener.
2 You should wait for several minutes and attempt to ENABLE the listener.