Follow this procedure to strip VN tags to support the encapsulation type expected by your traffic-analysis tools.
Note
In the examples that follow the configuration commands for this task, bold font is used to show the relationship between the items you configure and then bind. The example parameters and optional settings are only a partial set of those available. See the Extreme 9920 Software Command Reference, 21.1.0.0 for more information.device(config)#
The specified ACL and configured actions will be bound to a listener policy.
device(config)# ipv6 access-list acl2-ipv6 device(config-ipv6-acl)# seq 9 permit ipv6 any any count
Note
A listener policy supports only one of each of each ACL type: IP, IPv6, MAC .device(config)# listener-policy lp-11 43 device(config-listener-policy)# match ipv6 access-list acl2-ipv6 device(config-listener-policy)# strip vn-tag device(config-listener-policy)# description "LP for vn tag strippin ipv6"
Note
An egress can be associated with only one listener policy.device(config)# egress e7 device(config-egress)# set listener-policy lp-11 43 device(config-egress)# precedence 1 interface ethernet 2/14
device(config)# egress-group eg_9 device(config-egress-group)# description e-group_9 device(config-egress-group)# set egress e7
Note
A route-map policy supports only one match-ACL per layer.device(config)# route-map R4 10 device(config-route-map)# match ipv6 access-list acl2-ipv6 device(config-route-map)# set egress-group eg_9 device(config-route-map)# forward-action permit
Note
An ingress group can be associated with only one route map.device(config)# ingress-group TAP_TRAFFIC_2 device(config-ingress-group)# set route-map R4
Note
In the following example, traffic is coming in on slot/port-number 2/3.interface ethernet 1/3 description From_TAP set ingress-group TAP_TRAFFIC_2 no shutdown
Note
In the following example, traffic is leaving on slot/port-number 2/14.interface ethernet 2/14 description To_Tool no shutdown