Step 1: Create l2pt profile in both the switches.
create l2pt profile <profile name>
Step 2: Create and define a protocol filter matching the l2 packets. By default, there are some protocol filters created and defined.
# show protocol filter ---> output truncated to show only the l2 protocols which are predefined.
Protocol Name Protocol Id Destination Field Field Field
Type Value Address Offset Value Mask
--------------------- ----- ------ ----------------- ------ ------ ------
cdp snap 0x2000 01:00:0c:cc:cc:cc
dtp snap 0x2004 01:00:0c:cc:cc:cc
edp snap 0x00bb 00:e0:2b:00:00:00
stp llc 0x4242 01:80:c2:00:00:00
vtp snap 0x2003 01:00:0c:cc:cc:cc
lacp etype 0x8809 01:80:c2:00:00:02 14 01 ff
lldp etype 0x88cc 01:80:c2:00:00:0e
pagp snap 0x0104 01:00:0c:cc:cc:cc
udld snap 0x0111 01:00:0c:cc:cc:cc
If you would like to tunnel any of the above L2 protocols between end points, you need not create a new filter.
if there is any specific L2 packet that you would like to tunnel across, you can create and define a new protocol filter.
create protocol filter <name>
configure protocol filter <name> add dest-mac <mac-address> <snap/llc/etype/field> <value>
Step 3: Add the protocol filters to the l2pt profile.
configure l2pt profile <profile name> add protocol filter <filter name>
Step 4: Map the l2pt profile to the VMAN or VLAN on the ingress ports for the l2 packets.
configure vlan <name> ports <port-list> l2pt profile <profile name>
configure vman <name> ports <port-list l2pt profile <profile name>
To verify if the traffic is tunneled, check the following command:
show vman <name> l2pt detail
show vlan <name> l2pt detail
The l2pt profile only needs to be added to the untagged vman port, the service/customer port.