NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
apack
Jun 22, 2011Aspirant
GSM7328FS 7.3.1.7 losing L3 vlan interfaces?
Hello all, and thank you all for the help you've provided me in the past just by searching / reading your posts, especially advantagecom. I have a star topology with a GSM7328FS at the core feeding 2...
apack
Aug 12, 2011Aspirant
Since yesterday I have installed our backup GSM7328FS with FW 8.0.3.25 and connected it to the existing (FW 7.3.1.7) GSM7328FS on port 24 on both switches.
The new switch was factory defaulted, brought up and configured from console. I changed the l3 vlan 10 IP address on the old switch, and set the new switch to that same gateway IP. It is doing better, but still has issues.
All this switch is doing is providing the l3 gateway address for vlan 10, which about 400 machines use. I am showing about 3mb/s down and 1mb/s up on the internet router upstream from this switch. My pings (from a machine plugged in port 23 of the new GSM7328FS) to the l3 interface are inconsistent, ranging from 1ms to 100's and dropouts. The ping from the same machine through to www.yahoo.com range from 8ms to 30's and 40's but do not drop out.
show process CPU has indicated an average CPU utilization of 14% over 5 minutes on the switch.
This switch is factory default plus vlan 10 l2 and l3 setup with two ports (1/0/23, 1/0/24) setup for untagged vlan 10 pvid 10 and one port (1/0/21) setup for port mirroring 1/0/24 (uplink to old switch).
If someone has some ideas or questions about the config, please let me know.
The old core switch has hardly stable on l3, but had been relatively trouble free for almost two months. Wednesday night we started changing downstream switches from untagged vlan 10 uplinks to the core to tagged, and that is when this all started. I could go back and untag all those downstream switches, but we really need this config to work to be able to properly trunk wireless to our APs.
The new switch was factory defaulted, brought up and configured from console. I changed the l3 vlan 10 IP address on the old switch, and set the new switch to that same gateway IP. It is doing better, but still has issues.
All this switch is doing is providing the l3 gateway address for vlan 10, which about 400 machines use. I am showing about 3mb/s down and 1mb/s up on the internet router upstream from this switch. My pings (from a machine plugged in port 23 of the new GSM7328FS) to the l3 interface are inconsistent, ranging from 1ms to 100's and dropouts. The ping from the same machine through to www.yahoo.com range from 8ms to 30's and 40's but do not drop out.
show process CPU has indicated an average CPU utilization of 14% over 5 minutes on the switch.
This switch is factory default plus vlan 10 l2 and l3 setup with two ports (1/0/23, 1/0/24) setup for untagged vlan 10 pvid 10 and one port (1/0/21) setup for port mirroring 1/0/24 (uplink to old switch).
If someone has some ideas or questions about the config, please let me know.
The old core switch has hardly stable on l3, but had been relatively trouble free for almost two months. Wednesday night we started changing downstream switches from untagged vlan 10 uplinks to the core to tagged, and that is when this all started. I could go back and untag all those downstream switches, but we really need this config to work to be able to properly trunk wireless to our APs.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!