Binding an AC to a cross-connect
This task is mutually exclusive with Ethernet link aggregation. If an 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.
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 non-BGP cross-connect:
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. Bind the service instance on the Layer 2 Ethernet interface to the cross-connect. | ac interface interface-type interface-number service-instance instance-id [ access-mode { ethernet | vlan } ] | By default, no service instance is bound to the cross-connect. |
To bind a service instance to a BGP cross-connect:
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 group auto-discovery view. | auto-discovery bgp | N/A |
4. Enter site view. | site site-id [ range range-value ] [ default-offset default-offset-value ] | N/A |
5. Enter auto-discovery cross-connect view. | connection remote-site-id remote-site-id | N/A |
6. Bind the service instance on the Layer 2 Ethernet interface to the BGP cross-connect. | ac interface interface-type interface-number service-instance instance-id [ access-mode { ethernet | vlan } ] | By default, no service instance is bound to the BGP cross-connect. |