Interface Configuration
7750 SR Interface Configuration Guide Page 257
Configuring G.8031 Protected Ethernet Tunnels
Ethernet tunnel configuration can include at most two paths. Other considerations include:
• A path contains one member port and one control-tag (backbone VLAN ID/BVID)
• If the operator wants to replace an existing member port or a control-tag, the whole path
needs to be shutdown first. The alternate path will be activated as a result keeping the
traffic interruption to a minimum. Then the whole path must be deleted and re-created. To
replace an existing member port or control tag, the whole path needs to be shutdown first.
The alternate path will be activated as a result keeping traffic interruption to a minimum.
Then the whole path must be deleted, the alternate path precedence modified to primary
before re-creating the new path.
• The Ethernet tunnel will inherit the configuration from the first member port. The
following port-level configuration needs to be the same between member ports of an
Ethernet tunnel:
→ config>port>ethernet>access>{ingress|egress}>queue-group
→ config>port>ethernet>egress-scheduler-policy
→ config>port>access>egress>pool
→ config>port>ethernet>dot1q-etype
→ config>port>ethernet>qinq-etype
→ config>port>ethernet>pbb-etype
→ config>port>ethernet> mtu
• The operator can update these port parameters only if the port is the sole member of an
Ethernet tunnel. This means that in the example below, the operator needs to remove port
1/1/4 and port 1/1/5 before being allowed to modify 1/1/1 for the above parameters.
CLI Syntax: eth-tunnel 1
path 1
member 1/1/1
path 2
member 1/1/4
eth-tunnel 2
path 1
member 1/1/1
path 2
member 1/1/5
The following example displays eth-tunnel configuration output:
port 1/1/1
ethernet
encap-type dot1q
port 2/2/2
ethernet
To Next Page
Loading...
