Table of Contents
Advertisement
Step
Binding an AC to a cross-connect
This task is mutually exclusive with Ethernet link aggregation. If a Layer 3 interface has been added
to a link aggregation group, you cannot bind the interface to a cross-connect, and vice versa.
After you bind a Layer 3 interface to a cross-connect, packets received from the Layer 3 interface are
forwarded through the PW or another AC bound to the cross-connect.
To bind a Layer 3 interface to a non-BGP cross-connect:
Step
1.
Enter system view.
2.
Enter cross-connect group
view.
3.
Enter cross-connect view.
4.
Bind the Layer 3 interface to
the cross-connect.
To bind a Layer 3 interface to a BGP cross-connect:
Step
1.
Enter system view.
2.
Enter cross-connect group
view.
3.
Enter auto-discovery
cross-connect group view.
4.
Enter site view.
5.
Enter auto-discovery
cross-connect view.
6.
Bind the Layer 3 interface to
the BGP 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
class-name ]
Command
system-view
xconnect-group group-name
connection connection-name
ac interface interface-type
interface-number
Command
system-view
xconnect-group group-name
auto-discovery bgp
site site-id [ range range-value ]
[ default-offset
default-offset-value ]
connection remote-site-id
remote-site-id
ac interface interface-type
interface-number
419
Remarks
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.
Remarks
N/A
N/A
N/A
By default, no Layer 3 interface is
bound to the cross-connect.
Remarks
N/A
N/A
N/A
N/A
N/A
By default, no Layer 3 interface is
bound to the BGP cross-connect.
Advertisement
Table of Contents
