3com 3031 Instruccion De Instalación

Descargar
Página de 1122
1060
C
HAPTER
 76: DCC C
ONFIGURATION
[3Com] debugging dialer packet
[3Com] info-center enable
Outputting debugging information and diagnose the process for the 
failure of the interconnection between DCC and the remote end 
In this section, the debugging information that may be outputted when DCC 
cannot reach the remote end will be displayed and explained. The user can solve 
the problems with the solutions recommended in this section.
DCC
Receive CALL_DISC_IND
The debugging information is probably output because:
The physical connection between the local and remote ends is broken, phone 
cable is not securely connected to the router, or the quality of phone line is not 
good.
PPP authentication is not correctly configured, so the PPP authentication is 
failed.
Remote DCC authentication is failed, because name in the commands 
dialer 
user 
and 
dialer route
 configured for DCC is inconsistent with name 
configured for PPP authentication, and the 
dialer route
 at the remote end 
does not contain the local network address.
The remote end disconnects the connection because the remote DCC 
idle-timeout timer has timed out.
Solution:
If PPP configuration is incorrect or name configurations are inconsistent, 
implement the configuration as shown in the above example.
If it is the problem of the network address, apply the following measures in the 
configuration of the remote end: Add the dialer route corresponding to the 
network address of the local router on the remote router. Alternatively, remove 
all the dialer routes configured at the remote end, and use the dial number.
DCC
link negotiation Down on interface ***
The link is probably disconnected because PPP negotiation is failed due to a wrong 
PPP configuration. To solve the problem, refer to the previous example to make 
the configuration.
DCC
NAME authentication ERROR,
 
failed
The debugging information is probably outputted because name configured in the 
commands 
dialer user 
and 
dialer route
 is inconsistent with that configured 
in PPP authentication. The connection is disconnected since the local DCC 
authentication has been failed. To solve the problem, refer to the previous example 
to make the configuration.
DCC
peeraddr matching  error on interface ***
shutdown link
The debugging information is probably outputted because the local dialer route 
does not contain the remote network address. To solve the problem, add the dialer 
route corresponding to the remote network address on the local router or use the 
dial number after removing all the dialer routes configured on the local router.