IP address in IPARP table but unable to ping

[Rod_Robertson2]

Trying to set up vman across an ISP supplied network ( Cisco ) L2 connectivity . ICMP is not barred ..

The vman vlan has been given an IP address 192.168.200.200 ( A end )
192.168.200.100 ( B END ) with the Cisco ISP network in between

In the IPARP table (A end ) I can see an entry for the 192.168.200.100 address with the correct mac address of the remote Extreme switch ..

A end hardware X670-48X Vman termination

When I try to ping this address 192.168.200.100

# ping 192.168.200.100Ping(ICMP) 192.168.200.100: 4 packets, 8 data bytes, interval 1 second(s).
#

--- 192.168.200.100 ping statistics ---
4 packets transmitted, 0 packets received, 100% loss
round-trip min/avg/max = 0/0/0 ms

A end

configure vlan 4089 ipaddress 192.168.200.200 255.255.255.0

sh conf | include
vman configure vman ethertype 0x8100
create vman "4089"
configure vman 4089 tag 4089
configure vman 4089 add ports 1:48 tagged ( to ISP 10G)
configure vman 4089 add ports 1:47 untagged ( to X670-48T

B end

Hardware X670-48X using 10gig dat link to palo

configure vlan 4089 ipaddress 192.168.200.100 255.255.255.0
sh conf | include
vmanconfigure vman ethertype 0x8100
create vman "4089"
configure vman 4089 tag 4089
configure vman 4089 add ports 33 tagged ( to ISP 10G)
configure vman 4089 add ports 39 untagged ( Palo-Alto )

I have just upgraded both switches at the a end to SummitX-15.6.4.2-patch1-6.xos

[Rod_Robertson2]

I have just finished creating this with extreme hardware again in a lab environment , it works a treat.. just as before.

Has anyone have any configurations of using Extreme on the edge with cisco in the core returning to extreme on the edge..

Im going to search the internet now for any info ... even just to understand how cisco support this would be an advantage at this stage..

[EtherMAN]

First you have to make sure your ISP is allowing SVID tagging across their network and they are also supporting ethertype 0x8100 for the svid tagging. If they are transporting your svid (industry name for outer tag of QnQ or vman) or if they are just set up as an access port and aren't really doing a QnQ service. We need to know exactly how they have their part of this provisioned... Muti-tagging is very common today but things have to line up.

[Frank]

I wonder if JANET may have to adjust their MTU, because you're already handing them "q-in-q" traffic, and they (probably) add their q-in-q on top of that - so you're "q-in-q-in-q"-ing.

That being said, and because I looked at your drawing from the other post, why are you using a VMAN? Of course I'm now assuming (and I know how that usually goes) that you're in control of the VLANs on the Palo Alto and the VLANs that come in on the 670, which may not be true. But if it is, why not just tag all the VLANs all the way through your switches, tag them to the port where JANET plugs in, and let them handle the rest?

[Rod_Robertson2]

OK I have done this a one end ... SDC .. no access to the other so might have to be tomorrow..