• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2854
  • Last Modified:

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 / 24
VLAN ID 20 / 24
VLAN ID 30 / 24
Routing between these VLANs works fine.

To enable routing to an external network / 24 and to the Internet I did configure port 1 as interface / 24 on the switch. In addition I did configure a Netgear VPN router (FVX538) with LAN IPs /24 and / 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, SM, Interface: Port 1, Next Hop IP
I've added the following route on the VPN router FVX538:
Network address, SM, Interface: LAN, Gateway IP

When I connect a computer to VLAN 20 (IP: it will be able to ping successfully addresses in the Internet as well in the / 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 on the FSM7328S stack from computers in the / 24 subnet.

If I ping to for example (this is the routing interface in VLAN 20) from IP, 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!
1 Solution
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: UNKN[280142736]: dot1s_sm.c(1351) 43042 %% dot1sPrxMachine(): Rcvd BPDU in Discard State on port 1

The subnet / 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 / 24 the problem was solved. Now communication in both directions does work as expected.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now