Pvc State Is Down When Atm Interface State Is Up; Ping Failure After Pppoa Configuration - HP MSR Router Series Wan Access Configuration Manual

Hide thumbs Also See for MSR Router Series:
Table of Contents

Advertisement

Solution
If IPoA is used, make sure the IP protocol address mapping is configured correctly. If the interfaces
of two routers are connected back-to-back, the local PVC mapped to the remote IP address must
have the same VPI/VCI value as the remote PVC mapped to the local IP address.
If two routers are connected back-to-back, make sure at least one of interfaces uses internal
transmission clock (master). If the routers are connected to the ATM network, the transmission clock
must be set to line clock (slave).
Verify that the ATM interfaces of the two sides are of the same type. For example, both sides use
multi-mode fiber interfaces, single-mode fiber interfaces, or multi-mode fiber interfaces but
connected using single-mode fiber. If a multi-mode fiber interface and a single-mode fiber interface
are directly connected, they can communicate in most cases, but sometimes with frequent packet
dropping and CRC errors.
If the two ends use PPPoA, make sure their IP addresses and authentication parameters are correctly
configured.
If the output from the ping command shows that only small packets can pass, check the MTU
settings of both router interfaces.

PVC state is down when ATM interface state is up

Symptom
The state of the ATM interface is up, but the PVC state is down.
Solution
Determine if this fault results from enabling OAM F5 Loopback cell transmission and retransmission
detection or OAM continuity check. When two routers are connected, the VPI/VCI values of the PVCs on
the two routers must be the same. If OAM F5 cell transmission and retransmission detection or OAM
continuity check is enabled, and the VPI/VCI values of the two directly connected nodes are not the same,
the local PVC state cannot change to up.

Ping failure after PPPoA configuration

Symptom
The PVC state is up, but after applications like PPPoA are configured, the remote node cannot be pinged.
Solution
Make sure the remote node supports the same application as configured on the local node. For example,
if the local node uses PPPoA, the remote node must also use PPPoA.
If the remote node supports the same application configured on the local node, make sure the two sides
use the same type of AAL5 encapsulation protocol. For example, if one side uses aal5snap and the other
uses aal5mux, they cannot communicate. You can enable ATM packet debugging to get some clues
about possible causes of the ping failure.
152

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents