Configuring A Remote Ccc Connection - HP FlexNetwork 10500 Series Configuration Manual

Step
5. Configure route targets for
the cross-connect group.
6. (Optional.) Specify a PW
class for the auto-discovery
cross-connect group.
7. (Optional.) Set an MTU for
the PW.
8. Create a local site and enter
site view.
9. Create a cross-connect and
enter auto-discovery
cross-connect view.
10. (Optional.) Specify a tunnel
policy for the auto-discovery
cross-connect.

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 Reference.
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
1. Enter system view.
2. Enter cross-connect
group view.
3. Enter cross-connect view.
Command
vpn-target vpn-target&<1-8>
[ both | export-extcommunity |
import-extcommunity ]
pw-class class-name
mtu size
site site-id [ range range-value ]
[ default-offset default-offset ]
connection remote-site-id
remote-site-id
tunnel-policy tunnel-policy-name
Command
system-view
xconnect-group group-name
connection connection-name
335
Remarks
By default, no route targets are
configured for the cross-connect
group.
By default, no PW class is
specified.
The default MTU is 1500 bytes.
By default, no local sites exist.
By default, no cross-connects
exist.
After you execute this command,
a PW to the specified remote site
is created and is bound to the
cross-connect.
By default, no tunnel policy is
specified.
Remarks
N/A
N/A
N/A