334
Step Command
Remarks
8.
Create a local site and enter
site view.
site
site-id
[
range
range-value
]
[
default-offset
default-offset
]
By default, no local site is created.
9.
Create a cross-connect and
enter auto-discovery
cross-connect view.
connection
remote-site-id
remote-site-id
By default, no cross-connect is
created.
After you execute this command, a
PW to the specified remote site is
created and is bound to the
cross-connect.
10.
(Optional.) Reference a tunnel
policy.
tunnel-policy
tunnel-policy-name
By default, no tunnel policy is
referenced.
Configuring a remote CCC connection
To configure a remote CCC connection, perform the following configurations on the PE and P devices:
•
On the two PEs, use the
ccc
command to specify the incoming and outgoing labels.
•
On each P device between the two PEs, use the
static-lsp transit
command to configure a static LSP
for each direction of the CCC connection. For more information about the
static-lsp transit
command, see
MPLS Command References
.
Follow these guidelines when you configure a remote CCC connection:
•
The outgoing label specified on a device must be the same as the incoming label specified on the
next-hop device.
•
CCC connection settings such as the encapsulation type and control word feature must be
consistent on the two PEs. Otherwise, the PEs might fail to forward packets over the CCC
connection.
To configure a remote CCC connection:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter cross-connect
group view.
xconnect-group
group-name
N/A
3.
Enter cross-connect
view.
connection
connection-name
N/A
4.
Create a remote CCC
connection.
ccc in-label
in-label-value
out-label
out-label-value
{
nexthop
nexthop
|
out-interface
interface-type
interface-number
}
[
pw-class
class-name
]
By default, no remote CCC
connection is created.
Use the
out-interface
keyword to
specify the outgoing interface
only on a point-to-point link. On
other types of interfaces such as
Layer 3 Ethernet interface, VLAN
interface, and Layer 3 aggregate
interface, you must use the
nexthop
keyword to specify the IP
address of the next hop.