R2511-HP MSR Router Series Terminal Access Configuration Guide(V5)
78
software inbound) commands on the asynchronous serial interface to prevent detection of the
dsr/dtr signals. This allows the asynchronous interface to automatically enter the up state, and
prevents detection of hardware flow control signals by adopting software flow control or no flow
control.
When a 5-wire asynchronous serial interface cable is used, flow control signal lines are absent.
This means that you must use the flow-control none or flow-control software inbound command on
the asynchronous interface, to prevent detection of hardware flow control signals by adopting
software flow control or no flow control instead.
When an 8-wire asynchronous serial interface cable is used, all the required signal lines are
available. Therefore, you do not need to configure the above-mentioned commands on the
asynchronous interface.
Check whether the router and Unix server can ping each other
1. If yes
The WAN line between the router and the Unix server functions well, and the criterion is satisfied
for the router to establish a TCP connection to the server. For more information, see "Check
whether the main ttyd proc
ess and its child processes are present."
2. If not
Check the configuration of the WAN interface of the router, the WAN line provided by the ISP,
and the router related parameters on the router and server.
Check whether the main ttyd process and its child processes are present
Use the process management function provided by the ttyd administration program or the ps –ef | grep
ttyd command to check whether the main ttyd process and its child processes are present.
1. The ttyd main process does not exist.
The ttyd program is not running. Run the program as follows:
# /etc/ttyd
If you do not specify any parameters for the command, the default configuration file /etc/ttyd.conf
is used. To specify another configuration file, you must enter a file name in the following format:
# /etc/ttyd /etc/ttyd9020.conf
2. The main ttyd process exits but none of its child processes exist.
The ttyd program has been started, but no TCP connection has been established between the
router and the Unix server. First, verify that the connection modes set on the router and the FEP are
the same, for example, both in the TTY one-to-one mode. Then, check whether it is because the
terminal authentication failed or opening the pseudo terminal failed. For more information, see
"Verify the configuration of the router and the ttyd c
onfiguration of the server are correct and
consistent "or Prompts on terminals.
3. T
he main ttyd process and its child processes exist.
The ttyd program has been started, and a TCP connection has been established between the router
and the Unix server. For more information, see "Check whether the router has established a TCP
conn
ection with the Unix server."
Verify the configuration of the router and the ttyd configuration of the server are correct and consistent
• Verify that the router configuration is correct.
• Verify that the configuration file ttyd.conf on the Unix server is correct.
• Verify that either the TTY one-to-one or TTY many-to-one mode is configured on both sides.
• Verify that port numbers configured on both sides are consistent.










