Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: nsp: extreme

Q-in-Q

 

 

nsp extreme RSS feed   Index | Next | Previous | View Threaded


alchemyx at uznam

Aug 9, 2012, 2:13 PM

Post #1 of 2 (1481 views)
Permalink
Q-in-Q

Hello,

Currently we are trying to make Q-in-Q between x480-24x and Cisco
Catalyst 3550.

We have on Cisco side VLAN 500, which has VLAN 101 inside. VLAN 500 has
IP 192.168.254.1 and VLAN 101 has 192.168.255.1. Just for testing
purposes. On Extreme side VLAN 545, and 101 inside. IP for 500 is
192.168.254.2 and for 101 is 192.168.255.2.

We had to change EtherType to 0x8100 on Extreme and we can ping
192.168.254.1 and .2 back and forth (VLAN 500/545). But no luck with
VLAN 101.

We are using some kind of weird technique of looping back to ourselves,
so for example on Cisco it looks like this:

interface GigabitEthernet0/10
description TPIX - QinQ in
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 101
switchport mode trunk
end
!
interface GigabitEthernet0/11
description TPSA - MetroEthernet
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 500
switchport mode trunk
no cdp enable
end
!
interface GigabitEthernet0/12
description EDGE - TPSA MetroEthernet
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,101
switchport mode trunk
end

So on Gi 0/11 we receive data from Extreme switch, on Gi 0/12 we sent
out VLAN 101 to another switch which has L3, BGP and so on. Gi0/9 and Gi
0/10 are loopbed back together. It worked that way previously (but we
had Cisco on other end). No configuration of Extreme. We are receiving
data from Cisco on port 2. We have loop between ports 23 and 24. VLAN
101 has IP added, but we can ping it. Configuration follows:

create vlan "TESTOWY"
configure vlan TESTOWY tag 101
configure vlan TESTOWY add ports 24 untagged
create vman "tpix"
configure vman tpix tag 545
configure vman tpix add ports 2 tagged
configure vman tpix add ports 23 untagged
configure vlan tpix ipaddress 192.168.254.2 255.255.255.0
configure vlan TESTOWY ipaddress 192.168.255.2 255.255.255.0

What are we doing wrong? Probably misunderstanding some concepts (we are
new to Extremes). Any clues will help!

--
Michał Margula, alchemyx [at] uznam, http://alchemyx.uznam.net.pl/
"W życiu piękne są tylko chwile" [Ryszard Riedel]
_______________________________________________
extreme-nsp mailing list
extreme-nsp [at] puck
https://puck.nether.net/mailman/listinfo/extreme-nsp


alchemyx at uznam

Aug 9, 2012, 2:50 PM

Post #2 of 2 (1401 views)
Permalink
Re: Q-in-Q [In reply to]

W dniu 09.08.2012 23:13, Michał Margula pisze:
> create vlan "TESTOWY"
> configure vlan TESTOWY tag 101
> configure vlan TESTOWY add ports 24 untagged
> create vman "tpix"
> configure vman tpix tag 545
> configure vman tpix add ports 2 tagged
> configure vman tpix add ports 23 untagged
> configure vlan tpix ipaddress 192.168.254.2 255.255.255.0
> configure vlan TESTOWY ipaddress 192.168.255.2 255.255.255.0
>
> What are we doing wrong? Probably misunderstanding some concepts (we are
> new to Extremes). Any clues will help!
>

That our dirty trick is causing this:

08/09/2012 23:13:54.68 <Warn:IPMC.Warning> Our own packet received. Mac
address of the received packet is [0:4:96:51:81:88],there could be
physical loop in the network

Which may be a root cause of everything. Is it possible to disable that?
Or is there any way to accomplish that QinQ setup?

Thanks

--
Michał Margula, alchemyx [at] uznam, http://alchemyx.uznam.net.pl/
"W życiu piękne są tylko chwile" [Ryszard Riedel]
_______________________________________________
extreme-nsp mailing list
extreme-nsp [at] puck
https://puck.nether.net/mailman/listinfo/extreme-nsp

nsp extreme RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.