
161
Step Command
Remarks
5.
Return to system view.
quit
N/A
6.
Enter Layer 2 Ethernet
interface view.
interface
interface-type
interface-number
N/A
7.
Create a service instance
and enter service instance
view.
service-instance
instance-id
By default, no service instance is
created.
8.
Configure a packet
matching rule for the
service instance.
encapsulation
{
s-vid
vlan-id
[
only-tagged
] |
port-based
|
tagged
}
By default, no packet matching rule
is configured for the service
instance.
9.
Create a primary static VC
and a backup static VC and
enter static-xpeer view
xconnect static-peer
peer-ip-address
pw-id
pw-id
[
access-mode
{
ethernet
|
vlan
} |
mtu
mtu-value
|
[
pw-class
class-name
]
[
backup-peer
ip-address
backup-pw-id
pw-id
[
backup-pw-class
class-name
|
revertive
[
wtr-time
wtr-time
] ]
* ] ] *
This command is available for
service instances with an ID in the
range of 1 to 4094.
To implement VC redundancy, use
the
backup-peer
keyword to create
a backup VC.
After this command is executed, the
VLAN ID, access mode, and MTU
configured for the service instance
cannot be changed. To modify
these parameters, you must use
the
undo xconnect static-peer
command to delete the VCs first.
10.
Configure the VC labels for
the primary VC.
static label local
local-vc
remote
remote-vc
By default, no VC labels are
configured for the primary VC.
11.
Configure the VC labels for
the backup VC.
static backup-label local
local-vc
remote
remote-vc
Optional.
By default, no VC labels are
configured for the backup VC.
You must perform this command if
you have specified the
backup-peer
keyword in the
xconnect static-peer
command.
12.
Return to the interface
view.
quit
N/A
13.
Switch traffic from the
active VC to the standby
VC.
xconnect static-peer
switchover
Optional.
14.
Display information about
one or all service instances
configured on the interface.
display service-instance
interface
interface-type
interface-number
[
service-instance
instance-id
]
[
|
{
begin
|
exclude
|
include
}
regular-expression
]
Available in any view.
Configuring Martini MPLS L2VPN
To configure Martini MPLS L2VPN, complete the following tasks:
1.
Configure the remote peer.
In Martini MPLS L2VPN implementation, VC labels must be exchanged between PEs. Because
two PEs might not be connected to each other directly, you must specify the peer PE as the
remote peer on each PE to establish a remote session between the two PEs and transfer VC
FECs and VC labels through the session.