NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
WNDAP360 VLAN
Model: M5300-28G3 ProSafe 24-port Gigabit L3 with 10 Gigabit Stacking, 11.0.0.31, B1.0.0.5
I am trying to create a vlan (id 20) that passes through a couple of switches. I followed the instructions I found here but I can't ping between two laptops on either end.
My setup is as follows, I have one M5300-28G3 on the ground floor (stack id 2) and another in a server room (stack id 1) on a different floor. There are connected via a 10G-BaseT fibre cable. The pair of switches are in a stacked configuration with switch#2:port 26 uplinking to switch#1:port 25
On switch#1 I've added p23 as member of vlan#20, removed it from vlan#1 and set the port to access. I done something similar on switch#2. If I plug both units into the same switch, I have ping them but I can't ping across the trunk.
One question I have is how to interpret the vlan membership table. The UI displays Unit 1 and LAG and I'm not sure if I modify both port in each table. Below is a screenshot of switch#2's vlan membership of vlan#1
vlan#1
This the same view on vlan#20sw#2vlan20
That aside, I cannot see what I've missed. From my reading, the configuration should work. I've manually assigned IP addresses to the hosts at either end and verified they work on the same switch.
There is one detail that does not look right and that is in the PVID configuration. The uplink port (switch2:p26), seems to only support tagged vlan#1.
That doesn't look right to me but I cannot find a means to change it.
sw#2pvid-config
Any troubleshooting tips would be helpful.
Thanks,
Dermot
[ Apologies for the subject, I'm not sure where that subject came from ]
I think I may have resolved this. The problem looks to be because I did not assign both vlans to both trunkports. I'd assumed that by marking the port as 'T' it would accept and tag all traffic but you need to visit each vlan and set the trunkport for both vlans (1 & 20 in my case)
You end up with something like this
>show vlan 20 .. 1/0/24 Exclude Autodetect Untagged 1/0/25 Include Include Tagged 1/0/26 Exclude Autodetect Untagged ... >show vlan 1 .. 1/0/24 Include Include Untagged 1/0/25 Include Include Tagged 1/0/26 Include Include Untagged
Once I set the trunk port on both switches to trunk for both vlans, I could ping from one host to another.
Moreover, the original port I was using as an access port (port 23) refuses to cooperate despite the fact it does do cable tests successfully. I could not get any light or activity from it. This may be because port 25 - 28 are used as uplink and there is also a fibre module in the rear. Perhaps 23 is not available because of that.
Hope that helps someone in the future.Dermot
1 Reply
[ Apologies for the subject, I'm not sure where that subject came from ]
I think I may have resolved this. The problem looks to be because I did not assign both vlans to both trunkports. I'd assumed that by marking the port as 'T' it would accept and tag all traffic but you need to visit each vlan and set the trunkport for both vlans (1 & 20 in my case)
You end up with something like this
>show vlan 20 .. 1/0/24 Exclude Autodetect Untagged 1/0/25 Include Include Tagged 1/0/26 Exclude Autodetect Untagged ... >show vlan 1 .. 1/0/24 Include Include Untagged 1/0/25 Include Include Tagged 1/0/26 Include Include Untagged
Once I set the trunk port on both switches to trunk for both vlans, I could ping from one host to another.
Moreover, the original port I was using as an access port (port 23) refuses to cooperate despite the fact it does do cable tests successfully. I could not get any light or activity from it. This may be because port 25 - 28 are used as uplink and there is also a fibre module in the rear. Perhaps 23 is not available because of that.
Hope that helps someone in the future.Dermot
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
