Routing problem on FSM7328S

This is the first time I'm configuring a L3 switch, so please excuse if this might be a stupid question for you:

I'm using 2 stacked Netgear FSM7328S switches. I've configured 3 different VLANs:
VLAN ID 10   192.168.1.0 / 24
VLAN ID 20   192.168.2.0 / 24
VLAN ID 30   192.168.3.0 / 24
Routing between these VLANs works fine.

To enable routing to an external network 10.1.2.0 / 24 and to the Internet I did configure port 1 as interface 192.168.5.254 / 24 on the switch. In addition I did configure a Netgear VPN router (FVX538) with LAN IPs 192.168.5.253 /24 and 10.1.2.254 / 24 and I did use a patch cable for connection between the VPN router and port 1 on the switch.

I've added the following default route on the FSM7328S stack:
Network address 0.0.0.0, SM 0.0.0.0, Interface: Port 1, Next Hop IP 192.168.5.253
I've added the following route on the VPN router FVX538:
Network address 192.168.0.0, SM 255.255.0.0, Interface: LAN, Gateway IP 192.168.5.254

When I connect a computer to VLAN 20 (IP: 192.168.2.50) it will be able to ping successfully addresses in the Internet as well in the 10.2.2.0 / 24 subnet. In this direction all seems to work fine. But I'm neither able to ping IP addresses in the VLANs nor the gateway IP 192.168.5.254 on the FSM7328S stack from computers in the 10.2.2.0 / 24 subnet.

If I ping to 192.168.2.254 for example (this is the routing interface in VLAN 20) from IP 10.1.2.51, then my computer in the VLAN will lose connection to the switch. After some minutes connection will be restored. I can restore connection manually if I unplug the cable of this computer on the FSM7328S and re-connect it into another switch port.

Does anybody know what might be the reason for this behaviour?

Thanks in advance!
ghana
LVL 11
ghanaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ghanaAuthor Commented:
OK, I found the reason myself:It was caused by Spanning Tree Protocol and another switch.

In the log of the switch stack I found the following entries, that appeared every 2 seconds:
0.0.0.0-1 UNKN[280142736]: dot1s_sm.c(1351) 43042 %% dot1sPrxMachine(): Rcvd BPDU in Discard State on port 1

The subnet 10.1.2.0 / 24 does contain another single FSM7328s switch. This switch tried to communicate with the switch stack via spanning tree protocol. When I disabled the spanning tree on the single switch in subnet 10.1.2.0. / 24 the problem was solved. Now communication in both directions does work as expected.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Switches / Hubs

From novice to tech pro — start learning today.