04-20-2021 02:52 PM
We are testing a Q-in-Q link to an internet service provider in our city. I have a few test VLANs at the remote site. The provider’s Q-in-Q tag is stripped on a Juniper ex4600 that connects to one of our VSP7254s. The remote site VLAN gateways are on the VSP7254. I can ping the layer 3 logical interface for each VLAN at the remote site. We also have an SPBM cloud so I’m trying to extend the remote VLANs to our main office (Site-A), but am not having success. I have created the VLANs and mapped them to i-sids on the 7254 and on the 4450 at Site-A. I created an untagged port for one of the test VLANs and connected an edge device to the port and assigned it an IP in one of the test VLANs. At this time I cannot even ping the gateway, but the 7254 does see the MACs. Any thoughts on what could be missing? Here is a basic diagram of the setup plus the out put of the MACs on the 7254.
Data-Center-1:1#sh vlan mac-address-entry 2997
===============================================================================
Vlan Fdb
===============================================================================
VLAN MAC SMLT
ID STATUS ADDRESS INTERFACE REMOTE TUNNEL
----------------------------------------------------------------------------------------------------
2997 learned c4:00:ad:fe:0f:83 Port-2/2 false VSP-4450
2997 self d4:78:56:96:b5:13 Port-cpp false -
2997 learned f0:64:26:5f:9c:83 Port-1/1 false -
Solved! Go to Solution.
04-20-2021 05:34 PM
None of those VSPs have a vIST configured ? If yes, the I-SIDs must be configured on both vIST peers.
04-20-2021 05:14 PM
-This is the link from the 4450 to my end device right? This is simply an untagged access port in vlan 2997. Not sure of the best command to confirm UNI type though.
I assume you configured a platform VLAN and assigned it to the port (CVLAN UNI), but you made sure the ISID numbers are the same for this VLAN 2997 on the VSP7254 and the VSP4450, correct?
IS-IS NNI links are up between the VSPs and you have done your fabric configuration properly, correct?
Roger
04-20-2021 04:57 PM
Also, just to be sure it isn’t the edge device, I confirmed that I can extend another site’s VLAN to it and it works. This site connects to our own fiber so no Q-in-Q, but again, it doesn’t seem like that should matter.
04-20-2021 04:46 PM
Hi Roger.
*the link between the EX4600 and the VSP7254 is tagged, correct?
-Yes, the link between ex4600 and VSP7254 is tagged.
* VLAN 2997 has a routing interface on the VSP7254 only and not on the VSP4450, correct?
-Yes, the 4450 does not have a layer 3 interface for that VLAN. I did have l3 interface for VLAN 2998 on both which definitely caused that VLAN (2998) to have issues until I fixed it.
*what UNI type are you using on the VSP4450? You are not using transparent UNI, right? (either CVLAN or Flex UNI should work).
-This is the link from the 4450 to my end device right? This is simply an untagged access port in vlan 2997. Not sure of the best command to confirm UNI type though.
* So the QinQ WAN part is not even comming into play in your initial test of pinging the VSP7254 routing interface from the VSP4450, correct?
-Mostly correct. I’m trying to ping the vlan 2997 routing interface on the vsp7254 from an edge device assigned to vlan 2997 that connects to the vsp4450. So, I believe there is no reason Q-in-Q should be a factor in this test, but thought I’d check since I’m fairly new to SPBM & brand new to Q-in-Q.
04-20-2021 04:16 PM
A couple of questions:
So the QinQ WAN part is not even comming into play in your initial test of pinging the VSP7254 routing interface from the VSP4450, correct?
Roger