- For individual users
- Instant access to solutions
- Ask your tech questions
- Start your 30-day Free Trial
Main Topics
Browse All TopicsThis 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
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: ghanaPosted on 2007-03-24 at 10:04:12ID: 18785647
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.