Binding An Ac To A Cross-Connect; Configuring Pw Redundancy - HP 10500 Series Configuration Manual

Step
4. Configure an LDP PW and
enter PW view.

Binding an AC to a cross-connect

This task is mutually exclusive with Ethernet link aggregation. If a Layer 2 Ethernet interface has been
added to a link aggregation group, you cannot bind a service instance on the interface to a
cross-connect, and vice versa.
On the HP 10500 series, an AC is a service instance on a Layer 2 Ethernet interface.
After you bind a service instance on a Layer 2 Ethernet interface to a cross-connect, packets that are
received from the Layer 2 Ethernet interface and meet the match criteria of the service instance are
forwarded to the PW or another AC bound to the cross-connect. A service instance can match all packets,
tagged packets, or untagged packets.
To bind a service instance to a cross-connect:
Step
1. Enter system view.
2. Enter cross-connect group
view.
3. Enter cross-connect view.
4. Bind the service instance on
the Layer 2 Ethernet interface
to the cross-connect.

Configuring PW redundancy

This task includes the following configurations:
Create a backup PW for the primary PW.
•
Specify whether to switch traffic from the backup PW to the primary PW when the primary PW
•
recovers, and specify the wait time for the switchover.
Manually perform a PW switchover.
•
Command
peer ip-address pw-id pw-id
[ pw-class class-name |
tunnel-policy tunnel-policy-name ] *
Command
system-view
xconnect-group group-name
connection connection-name
ac interface interface-type
interface-number service-instance
instance-id [ access-mode
{ ethernet | vlan } ]
233
Remarks
By default, no LDP PW is
configured.
If the specified peer PE is not
directly connected, the local PE
automatically sends a targeted
hello to create an LDP session to the
peer PE and then exchanges the
PW ID FEC and PW label mapping
with the peer.
Remarks
N/A
N/A
N/A
By default, no service instance is
bound to the cross-connect.