Can't Access VLANS on SF300-24 over QnQ?

bmanley · ‎01-27-2012

In our scenario setup is following:

Trunk from 3500 going into SF300-8 #1 QNQ
Trunk from SF300-8 #1 going into trunk SF300-8 #2
QNQ from SF300-08#2 going into Trunk SF300-24

All Vlans from Network 1 seem to be communicating properly between the 3550 and SF300-24 and is isolated from the Transport Network by QnQ. I am having one problem, I can not ping the SF300-24 or get to the management interface. I am able to access other devices on the SF300-24 Vlan1 from devices on the 3550 Vlan1 and vice versa. Any suggestions and/or comments?

3550 (Network 1) 174.16.1.3

Vlan 1 Management Vlan

Trunk Port 24

Vlan 1
Vlan 78
Vlan 21
Vlan 139

SF300-8 #1 (Transport Network) 192.168.1.253

QnQ Port 5

Vlan 2500 (UP)

Trunk Port 8

Vlan1 (UP)
Vlan 2500 (TP)

SF300-8 #2 (Transport Network) 192.168.1.252

QnQ Port 5

Vlan 2500 (UP)

Trunk Port 8

Vlan1 (UP)
Vlan 2500 (TP)

SF300-24 (Network 1) 174.16.1.8

Vlan1 Management Vlan

Trunk Port 12

Vlan 1 (UP)
Vlan 78 (TP)
Vlan 21 (TP)
Vlan 139 (TP)

Access Port 1

Vlan 1 (UP)

Access Port 2

Vlan 78 (UP)

Access Port 3

Vlan 21 (UP)

Access Port 4

Vlan 139 (UP)

bmanley · ‎01-31-2012

I am now able to PING the SF300-24, but network traffic is not working as desired.

When we have the Trunk ports of the Transport Switches connected by Ethernet Cable everything works as desired. When we put the Wireless Bridge in place we have issues. Devices on each side of the Customer switches get DHCP from their respective Vlans, some data flows, some does not. Able to get Internet from the correct Gateway, able to connect to Exchange, able to Ping Servers and devices back and forth. Not able to connect to network folders, SIP registrations, or GUI based devices. Again, this all works when the Wireless Bridge is removed and both transport switches are connected by Ethernet.

Any suggestions on what could be causing these problems?