QinQ Mixed Mode on 5406 with Premium License

[A_Poignon]

I am trying to configure QinQ mixed mode. I am using a patch cable to connect the two switches for testing. After I get it working, these two switches will be on either end of a metro ethernet connection.

I have port A1 on TEST_CORE configured as a tagged member of S-VLAN 1151. A1 is connected with a patch cable to L1 on FMS-Core which is also a tagged member of S-VLAN 1151.

On TEST_CORE, A2 is an untagged member of S-VLAN 1151 and is configured as a qinq customer-port. Also on TEST_CORE, A3 is a tagged member of VLAN 310, which has an IP of 10.18.234.1. A2 and A3 are connected with a patch cable.

On FMS-Core, L2 is an untagged member of S-VLAN 1151 and is configured as a qinq customer-port. Also on FMS-Core, L3 is a tagged member of VLAN 310, which has an IP of 10.18.234.2. L2 and L3 are connected with a patch cable.

I am unable to ping 10.18.234.1 from FMS-Core, and I am unable to ping 10.18.234.2 from TEST_CORE.

The problem seems to be related to the loop from A2 to A3 and from L2 to L3. The Advanced Traffic Management Guide stated on page 8-8 that, "To tunnel customer frames through the provider network, you can externally connect a regular port to a customer-network port, eliminating the need for a separate S-VLAN bridge device to perform such operations."

I configured A18 on TEST_CORE and L18 on FMS-Core as untagged members of VLAN310. I connected Laptop1 with an IP 10.18.234.3 to A18, and Laptop2 with an IP 10.18.234.4 to L18. I am able to ping Laptop2 from Laptop1 and vice versa. This seems to tell me that QinQ is working.

I unplugged the patch cables from A2 to A3, L2 to L3 and A1 to L1. I Connected A3 to L3 with a patch cable and I was able to ping FMS-Core from TEST_CORE and vice versa. I was also able to ping our other networks from TEST_CORE. This tells me that routing is working properly.

I'm not sure what is needed to allow this configuration to work. Any help would be greatly appreciated.

[A_Poignon · Accepted solution]

HP Networking Support resolved this issue.

I had to use the ip-recv-mac-address <MAC ADDRESS> command in the VLAN 310 context to change the MAC Address of the VLAN.

The new MAC Address was higher than the switch's MAC Address pool.