Problem
I have a single uplink (LAG) from my core to my QinQ provider Cisco switch. If I don't add QinQ to my replacement 8400 ArubaOS-CX cores, how can I service
multiple svlans with a single uplink from to customer vlans on an ArubaOS 3810M ?
Solution
Link ports
as shown in Topology with patch cable jumpers and configure the QinQ switch as below
Topology
Enable
qinq mixed-vlan mode and let switch reboot
Procurve-QinQ(config)#
qinq mixedvlan
tag-type
Configure qinq tag-type
<cr>
This
command will reboot the device. Any prior configuration
on this
config file will be erased and the device will boot up
with a
default configuration for the new qinq mode.
Do you want
to continue? [y/n] y
Disable
BPDU Throttling
no spanning-tree bpdu-throttle
Disable
gvrp on interfaces added to svlans
interface 1-3,10,12,14
unknown-vlans disable
Add ports
to svlan’s 150, 151, 152
svlan 150
tagged 1
untagged 10
svlan 151
tagged 2
untagged 12
svlan 152
tagged 3
untagged 14
Add the
interfaces to the trunk
trunk 47-48 trk1 lacp
Tell
interfaces what type of qinq port they are
interface 1-3,10,12,14
qinq port-type provider-network
interface 9,11,13,trk1
qinq port-type customer-network
Add Dot1q
VLANs and Ports
vlan 50
tagged 9,Trk1
no
ip address
vlan 51
tagged 11,Trk1
no
ip address
vlan 52
tagged 13,Trk1
no
ip address
I can now
ping across the svlan from Host to Core and back again
Hosts
to Core
Host1(config)#
show ip
-------------------- + ---------- -------------- --------------
VLAN50 |
Manual 10.0.50.254 255.255.255.0
Host1# ping
10.0.50.1
10.0.50.1
is alive, time = 1 ms
Host2(config)#
show ip
-------------------- + ---------- -------------- --------------
VLAN51 |
Manual 10.0.51.254 255.255.255.0
Host2# ping
10.0.51.1
10.0.51.1
is alive, time = 1 ms
Host3(config)#
show ip
-------------------- + ---------- -------------- --------------
VLAN52 |
Manual 10.0.52.254 255.255.255.0
Host3# ping
10.0.52.1
10.0.52.1
is alive, time = 1 ms
Core
to Hosts
Core(config)#
ping 10.0.50.254
10.0.50.254
is alive, time = 1 ms
Core(config)#
ping 10.0.51.254
10.0.51.254
is alive, time = 1 ms
Core(config)#
ping 10.0.52.254
10.0.52.254
is alive, time = 1 ms
No comments:
Post a Comment
Please add comments so I may update the material to accommodate platform modification to various commands. Also if you have some real-world caveats, do please share.