Last weekend I replaced a dying Adtran(yeah, I know) "coreswitch" with a Netgear M4300 to allow 10G links to our other Adtran switches and satellite offices. Everything went well until I tried to create a static route between two VLANs.
We use VL200 with a 172.16.1.x/24 for our phones and they connect to the controller no problem. The issue with this are the hand full of workstations on VL1(192.168.1.x/24) that need to use the software to connect to the controller.
The old Adtran made it bloody simple to make a route between the two VLANs but after 4 techs and 7+ hours on the phone Netgear can't figure out a solution to do the same on their switch. A static route in windows for 172.16.1.0 255.255.255.0 192.168.1.2 allows connection, but the stupid Netgear will NOT allow me to route between the VLANs on itself.
Does anyone have experience with the Netgear GUI or CLI that help me set this route up? Every time I try it throws an error and I bought this switch specifically so we did not have to make a route upstream on the router(as the phones have a separate router/ISP and shouldn't need to hit the main router for any reason).
The phone controller is not VLAN aware and both 1 and 200 are being sent untagged already.
No comments:
Post a Comment