Panasonic NN46240-710 User Manual
Page 142
Attention! The text in this document has been recognized automatically. To view the original document, you can use the "Original mode".

4 MPLS L2VPN troubleshooting
Nortel Secure Router 8000 Series
_________ Troubleshooting - VPN
Code
Length
Description
0x02
4
Maximum number of concatenated ATM cells
0x03
Up to 82
Optional Interface Description string
0x04
4
CEP/TDM payload bytes
0x05
4
CEP options
0x06
4
Requested VLAN ID
0x07
6
CEP/TDM bit-rate
0x08
4
Frame-Relay DLCI Length
0x09
4
Fragmentation indicator
0x0A
4
FCS retention indicator
0x0B
4/8/12
TDM options
0x0C
4
Virtual Circuit Connectivity Verification (VCCV)
parameter
Items from 0x06 to 0x0C are extended in PWE3.
Currently, the Secure Router 8000 Series supports the MTU, Maximum ATM cell number,
Fragmentation and VCCV, but does not support the Request VLAN ID. You can set the same
VLAN ID for the AC interface at both ends to rectify the problem of not supporting the Request
VLAN ID.
When configuring interface parameters, note the following:
•
You must specify the same MTU for the Ethernet-type interface; otherwise, the PW cannot
be Up.
•
In ATM cell (0x0003 ATM transparent cell transport, 0x0009 ATM n-to-one VCC cell
transport and 0x000A ATM n-to-one VPC cell transport) mode, the maximum ATM cell
number must be sent to the peer in order to inform the peer how many cells it can handle at
a time. When the remote end encapsulates packets, this number must not increase.
Inconsistency of the cell number at both ends does not affect the status of a PW.
•
Fragmentation and ATM cell handling mode are consistent at both ends. The configuration
of fragmentation and ATM cell handling mode is optional. The local end only informs the
remote end whether it can perform reassembly; whether the remote fragments packets
depends on the packet size and its fragmentation capability. The fragmentation capability
does not affect the status of a PW, and it is not necessary to be the same.
•
VCCV processing is similar to ATM cell and fragmentation capability in terms of function.
The VCCV configuration is optional. VCCV informs the remote of its VCCV capability.
When performing VCCV, the peer chooses a path (CC) and a method (CV) according to
the configuration at both ends. VCCV does not a^ect the status of a PW, and does not need
to be consistent at both ends.
•
The Request VLAN ID informs the peer of its capability. During forwarding, the remote is
required to push a VLAN ID on its Layer 2 frame header. This configuration is optional. If
you use the Request VLAN ID, the VLAN ID can be different at both ends.
4-32
Nortel Networks Inc.
Issue 5.3 (30 March2009)