Hello Aronne
VLAN mapping allows you to translate VLAN IDs on one switch to a VLAN ID on another switch. That way, you can refer to the same VLAN with different VLAN IDs on different switches. This is helpful, particularly in a Metro Ethernet scenario, where the ISP is asked to send specific VLAN IDs across its infrastructure. If the customer VLAN ID numbers are already in use in the ISP’s infrastructure, then these are translated for transmission over the ISP, and are typically re-translated to their original values when they reach the remote customer site.
For clarity, let’s call your original VLAN IDs the Customer VLAN IDs (C-VLAN IDs), and the mapped VLAN IDs we’ll call Service Provider VLAN IDs (S-VLAN IDs).
Now in your case you are not “translating back” to the original C-VLAN IDs at the remote site, you are simply mapping one VLAN ID to another. I don’t have a definitive answer for you as to why you are unable to ping your gateway, but I do have the following comments that you can explore during your troubleshooting to resolve the issue:
- On the trunk port of the Switch_for_remap switch, you must have both customer and service provider VLAN IDs allowed on the trunk. You should, therefore, also include 3332 and 3333 in your allowed list. (I know you’re testing only VLAN 3331 for the time being in your post, but this should be done for completeness.)
- When mapping, you should only map your C-VLAN IDs to your S-VLAN IDs. You should not be mapping the opposite direction as well. So you must remove the last three mapping commands.
Other than that, at first glance, everything looks OK. Try these out and continue your troubleshooting. The following documentation may also be helpful for you:
Let us know how you get along!
I hope this has been helpful!
Laz