How to add a static route between 2 vlans on a netgear switch

We have a netgear managed switch that unfortunately I did not set up.  It has 2 vlans on it: 192.169.101.0 and 201.0   The switches ip address is 101.253.  I am trying to see the network on the 201 side, specifically 201.201.  I cannot for the life of me figure out how to set up a static route to enable this.  Does anyone have any ideas?
cvonrabeAsked:
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.

from_expCommented:
hi
does you switch have ip interfaces in both vlans?
if yes, then you have to configure all your workstations to have default gw to your switch, and your switch should be configured with default gateway to your firewall(the firewall you have additional static route to one (not directly connected) network located on the switch), so your switch will do the routing job between vlans and to the firewall.

Btw, I suppose you have typo in your networks and in a real live you have 192.168, not 192.169..
0
cvonrabeAuthor Commented:
Basically the vlans are set up on the switch.  The firewall is the dhcp server for the 101 subnet and our voip system provides the ip addresses on the 201 side.  I just need to be able to get to the 201 side from the 101 side.  This is how it looks right now:

101.189 (my workstatation) -> 101.254 (the firewall) -> 101.253 (the switch) -> dies after that

I just need to know how to set up the route on the switch to hit the 201 side.  the address of the switch on that side is 192.168.201.253. When I try to create the route it asks for the network address and the next hop address.  This is what I am confused about and do not know what to put in.  

P.S. I did mean 192.168, not 169
0
from_expCommented:
does your switch has ip address set in 201 subnet?
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

cvonrabeAuthor Commented:
yes.  both in the 101 and 201
0
from_expCommented:
ok
I would say you don't need any route on the switch, because it already knows about it's own subnets.
so my assumption is that you need route to 101 subnet from 201st.
let's have an example


A(workstation)-->B(firewall) -->C(switch)-->D(PBX)

A has:
ip: 192.168.101.189/24
gw to 192.168.101.254

B:
ip: 192.168.101.254/24 (local side)
ip: x.x.x.1/24 (wan side)
default to: x.x.x.254 (route to internet)
route: 192.168.201.0/24 via 192.168.101.253 (so firewall should know that 201st subnet is behind the switch), possibly you already has that route because after fw you see switch's ip in the trace)

C:
ip: 192.168.101.253/24 (vlan 1)
ip: 192.168.201.253/24 (vlan 2)
default to 192.168.101.254 (if needed)

D:
ip 192.168.201.100/24
default to 192.168.201.253 (unless you don't have default to somewhere else. If you have, then you have to add only a route to 101.0/24 subnet via 192.168.201.253)

that's all.




0
cvonrabeAuthor Commented:
OK I think I kind of understand.  These are the routes I have in the switch right now.  It is still not working.  Do you think these routes are correct?  Thanks for all of your help, your information above is all correct.


Total Number of Routes         5
Network Address       Subnet Mask       Protocol       Next Hop Slot/Port       Next Hop IP Address
0.0.0.0       0.0.0.0       Default       2/1       192.168.101.254
192.168.101.0       255.255.255.0       Local       2/1       192.168.101.253
192.168.101.0       255.255.255.0       Static       2/2       192.168.201.0
192.168.201.0       255.255.255.0       Local       2/2       192.168.201.253
192.168.201.0       255.255.255.0       Static       2/1       192.168.101.0
0
from_expCommented:
hi!
static routes should be deleted here, because you can see switch itself has local routes to the same subnets
0
cvonrabeAuthor Commented:
So what you are saying is that the routes that were initially in were sufficient?
0
from_expCommented:
absolutely sufficient!
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.