08-16-2013 09:28 AM
Hey guys, having trouble getting routing to work across my vlans. Read this very helpful thread
https://supportforums.cisco.com/thread/2153236, but still have no luck.
Switch is in L3 mode
My firewall has internal ip of 192.168.63.254/255.255.0.0
DNS is 192.168.62.1
Vlan port settings:
| |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Interface | Mode | Administrative VLANs | Operational VLANs | LAG | |||||||||||
GE1 | Trunk | 200UP | 200UP | ||||||||||||
GE2 | Trunk | 200UP | 200UP | ||||||||||||
GE3 | Trunk | 200UP | 200UP | ||||||||||||
GE4 | Trunk | 200UP | 200UP | ||||||||||||
GE5 | Trunk | 1UP | 1UP | ||||||||||||
GE6 | Trunk | 1UP | 1UP | ||||||||||||
GE7 | Trunk | 1UP | 1UP | ||||||||||||
Interface | IP Address Type | IP Address | Mask | Status | |
---|---|---|---|---|---|
VLAN 200 | Static | 192.168.20.62 | 255.255.255.192 | Valid | |
VLAN 1 | DHCP | 192.168.61.2 | 255.255.252.0 | Valid |
Destination IP Prefix | Prefix Length | Route Type | Next Hop Router IP Address | Route Owner | Metric | Administrative distance | ||
---|---|---|---|---|---|---|---|---|
0.0.0.0 | 0 | Remote | 192.168.63.254 | Static | 2 | 1 | ||
192.168.20.0 | 26 | Local | 0.0.0.0 | Directly Connected | ||||
192.168.60.0 | 22 | Local | 0.0.0.0 | Directly Connected |
I have a windows8 host connected to port 1 of the sg300. It's configured with a static address of 192.168.20.20/255.255.255.192 with gateway of
192.168.20.62.
From the windows8 host, I can ping to 192.168.20.62, however, I cannot ping to 192.168.63.254 or 192.168.62.1.
Any help much appreciated!!!
08-16-2013 02:53 PM
Hi Jonathan, any reason you're suppernetting your router? You're using a /16 there and everything else is inside that scope... I'd recommend to normalize your addresses...
-Tom
Please mark answered for helpful posts
08-17-2013 01:44 PM
What would a better plan be? I will have 15x SG300-52s very soon, The goal was to limit broadcast scope to just the physical switch you're attached to.
08-17-2013 02:34 PM
Hi Jonathan, a pretty typical deployment would be to have a management vlan/subnet. For an argument purpose you can use vlan 1 as management and put it on a 255.255.255.224 mask if that is enough to permit the 15 switches and all of the other network devices.
Next you can either have the router support the network traffic with a normal trunk and vlans tag or you can have the switches handle the network load. If the router supports subinterfaces or network subnets, that is fine, otherwise you'd simply need a static route to point to the switch SVI to be able to route the desired subnets.
As an example-
Management is the /28 on vlan 1 - 192.168.1.1 - 192.168.1.31
Then you could create additional vlans basically as much as you want
vlan 2 - 192.168.2.1 /24
vlan 3 - 192.168.3.1 /24
etc
To implement the switch configuration is basic something like this-
config t
int vlan 1
ip address 192.168.1.2 /28
int vlan 2
ip address 192.168.2.1 /24
int vlan 3
ip address 192.68.3.1 /24
exit
ip default-gateway 192.168.1.1
Then your router, if it doesn't support the subnets you could use static routes
something like
ip route 192.168.2.0 255.255.255.0 192.168.1.2
ip route 192.168.3.0 255.255.255.0 192.168.1.2
This should normalize the network and separate network traffic and give enough space for a management vlan.
-Tom
Please mark answered for helpful posts
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide