Tag-Stripping

Encapsulation header tags are stripped to prepare the packets for downstream analytic and other monitoring tools.

Header-tag stripping at egress is applied on only the first L2 header of the received packet.

You can configure a listener policy to define the actions to be performed on packet header tags and bind it to an egress policy. A listener policy supports the following header-modification and traffic actions.

You can create multiple listener-policy stanzas, but they do not have to be used in unique 1:1 configurations. In the following example, two listener policies (lp-1 and lp-2) are used to manage three traffic types. The listener-policy, lp-1 has two entries to manage 802.1BR and VN-TAG traffics.
Table 1. Managing traffic types in a listener-policy
Example 1 Example 2 Example 3 
listener-policy lp-1 10
match ip access-list v4_someacl1
strip br-tag

listener-policy lp-1 20
match ip access-list v4_someacl2
strip vn-tag

listener-policy lp-2 10
match ip access-list v4_someacl1
strip vn-tag

The following table lists the minimum requirements that must be configured for each policy type.

Table 2. Minimum policy configuration requirements
Ingress policy (packet flow) Egress policy (packet prep for analysis tools)
Match ACL Match ACL
Route-map with a valid match statement referencing a created ACL. A designated interface or multiple interfaces.
Note the following when configuring an ingress or egress policy:
9037169-00 Rev AA