Hi,
Thanks for the testing and setting it up.
As told, I run the temporary environment on an HP 3500-24G switch, wich with the latest firmware also supports QinQ / BGP etc... I Thought, let me share these 'strange' settings with you. Because, when setting it up on the same switch with a looped cable as descibed above, you need to change the Layer3 MAC address on the VLAN that crosses QinQ.
Article here: http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=mmr_kc-0131185&sp4ts.oid=3437443
Extra changes to be made:
Within VLAN200 (Customer VLAN) I added:
ip-recv-mac-address 223344-223344
On the Customer QinQ port (on wich the looped cable is connected, I added the commands:
unknown-vlans disable
qinq port-type customer-network
untagged svlan 1000
On the Serviceprovider QinQ port (on wich the uplink to MS Azure is connected) I added the commands:
unknown-vlans disable
QinQ port-type Provider-network (which is default and not visible)
tagged svlan 1000
And so QinQ with a Looped cable on the same switch works on a HP3500 switch also, with above adjustments.
In the weekend of the 25th of March, I'll be migrating the customer, and the 5800's will be connected and configured. So fingers crossed that I don't need an L3 MAC RECV command (which doens't excists on the comware switches, but possibly could be replaced by the IP Source Binding <IP> <MAC> command?)
But overall conclusion for this post is, that it is NOT POSSIBLE to add an S-VLAN tag to an C-VLAN on the same switch WITHOUT using a looped cable construction.
Case closed!
Joep