Endothermal
Programmer
I'm having trouble tracking down a problem I am having with a new VLAN I am setting up on an old network.
As quick of background info as I can give.
I have a Passport 1600 layer 3 switch, connected via fibre to a 460- 24T PWR switch (sw1). I have three VLANS 1,5,19 all working nominally on sw1. I then have a wireless bridge that connects two buildings plugged into port 6 on sw1. In the second building I have the receiving end of the bridge plugged into port 24 of a second 460-24T PWR (sw2). VLAN 19 is not functioning correctly on SW2, however VLAN 1 and VLAN5 is working correctly.
VLAN 1 192.168.1.x/24 untagged fully working
VLAN 5 192.168.5.x/24 tagged fully working* two tagged devices
VLAN 19 192.168.19.x/24 tagged not working correctly on SW2 only
I have a device plugged into sw2 and I have made it a memeber of VLAN 1 and VLAN 19 I have set the port to untag all and PVID is set to 1. I have the IP address set to 192.168.19.246 dv1. if add my laptop (ip 192.168.19.66) to sw2 and ping dv1 I get a response. If I try pinging a device in VLAN 1 I get no response. If I trying pinging dv1 from vlan 1 no response.
So it sounds like inter vlan communication is not working properly so I try the exact same setup on sw1 and everything works as expected.
I suspected the bridge but not quite sure it's the bridge, from the bridge device itself, a Cisco 1300ap I can ping dv1 no problem but if I try to ping dv1 from sw1 or sw2 using the management interface it fails. I assume I should be able to ping a device connected to a switch from the switch itself
I should note that all the switches are running very old versions of the firmware.
sw1 is running firmware v3.0.6.08
sw2 is running firmware v3.1.0.04
so they are quite old especially version 3.0, which has very limited controls especially when dealing with VLANS.
So here is my questions:
1) should I be able to ping the device plugged into the switch from the switch itself?
2) The bridge is plugged into port 6 on sw1 and it is set to untagged access, my only other option is Tagged Trunk, when I set the port to that all communication with sw2 is cut off
As quick of background info as I can give.
I have a Passport 1600 layer 3 switch, connected via fibre to a 460- 24T PWR switch (sw1). I have three VLANS 1,5,19 all working nominally on sw1. I then have a wireless bridge that connects two buildings plugged into port 6 on sw1. In the second building I have the receiving end of the bridge plugged into port 24 of a second 460-24T PWR (sw2). VLAN 19 is not functioning correctly on SW2, however VLAN 1 and VLAN5 is working correctly.
VLAN 1 192.168.1.x/24 untagged fully working
VLAN 5 192.168.5.x/24 tagged fully working* two tagged devices
VLAN 19 192.168.19.x/24 tagged not working correctly on SW2 only
I have a device plugged into sw2 and I have made it a memeber of VLAN 1 and VLAN 19 I have set the port to untag all and PVID is set to 1. I have the IP address set to 192.168.19.246 dv1. if add my laptop (ip 192.168.19.66) to sw2 and ping dv1 I get a response. If I try pinging a device in VLAN 1 I get no response. If I trying pinging dv1 from vlan 1 no response.
So it sounds like inter vlan communication is not working properly so I try the exact same setup on sw1 and everything works as expected.
I suspected the bridge but not quite sure it's the bridge, from the bridge device itself, a Cisco 1300ap I can ping dv1 no problem but if I try to ping dv1 from sw1 or sw2 using the management interface it fails. I assume I should be able to ping a device connected to a switch from the switch itself
I should note that all the switches are running very old versions of the firmware.
sw1 is running firmware v3.0.6.08
sw2 is running firmware v3.1.0.04
so they are quite old especially version 3.0, which has very limited controls especially when dealing with VLANS.
So here is my questions:
1) should I be able to ping the device plugged into the switch from the switch itself?
2) The bridge is plugged into port 6 on sw1 and it is set to untagged access, my only other option is Tagged Trunk, when I set the port to that all communication with sw2 is cut off