3com 3031 Instruccion De Instalación

[3Com] ping 111.1.1.2

  PING 111.1.1.2: 56  data bytes, press CTRL_C to break

    Reply from 111.1.1.2: bytes=56 Sequence=1 ttl=255 time=29 ms

    Reply from 111.1.1.2: bytes=56 Sequence=2 ttl=255 time=31 ms

    Reply from 111.1.1.2: bytes=56 Sequence=3 ttl=255 time=29 ms

    Reply from 111.1.1.2: bytes=56 Sequence=4 ttl=255 time=30 ms

    Reply from 111.1.1.2: bytes=56 Sequence=5 ttl=255 time=30 ms

  --- 111.1.1.2 ping statistics ---

    5 packet(s) transmitted

    5 packet(s) received

    0.00% packet loss

round-trip min/avg/max = 29/29/31 ms

Note that the MP link must bind to MP-group directly, No alternative such as using 
Virtual-Template as a medium exists.

Fault 1: Link never turns into up state.

Problem solving: This problem may arise because of the PPP authentication 
failure due to the incorrect configuration of PPP authentication parameters.

Enable the debugging of PPP, and you will see the information describing that LCP 
went up upon a successful LCP negotiation but went down after the PAP or CHAP 
negotiation.

Fault 2: Physical link failed in going up.

Problem solving: Execute the 

command to view the current interface statuses, including:

■

“serial number is administratively down, line protocol is down”, which 
indicates that the interface has been shut down by the administrator. 

■

“serial number is down, line protocol is down”, which indicates that the 
interface is not active or the physical layer has not gone up yet. 

■

“Virtual-template number is down, line protocol is spoofing up”, which 
indicates that this interface is a Dialer interface and the call establishment 
attempt has failed.

■

”serial number is up, line protocol is up”, which indicates that the link 
negotiation, i.e., the LCP negotiation on this interface has succeeded.

■

”serial number is up, line protocol is down”, which indicates that this interface 
is active, but link negotiation has failed.