MSPs: Get the facts you need to protect your clients.
The 2017 Webroot Threat Report provides a uniquely insightful global view into the analysis and discoveries made by the Webroot® Threat Intelligence Platform to provide insights on key trends and risks as seen by our users.
Solved
Cisco 3550 smi routing
Posted on 2004-09-25
Hello
Looking for some configuration tips on a couple of 3550 smi switches. I currently have production PLC and PC devices on the switches and am looking to segment them into 2 networks but they need to talk between a single server. I have been looking at Ciscos configurations and was wondering if anyone can tell me if I have to put an IP address at each interface or just the vlan them interface belongs to? Any other tips would be appreciated. since the switches are smi they only support static and rip routing? 1 switch is running Version 12.1(13)EA1a and the other is Version 12.1(12c)EA1. In total I have 6 of the 3550 on this lan but only need to segment and route between the 2. Thanks in advance.
JF
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
3-
3
2
8 Comments
If you sick with the standard image you will need another layer 3 device to perfrom intervlan routing. This could be another L3 switch or a router. Connecting a router to a switch to perform this function is called "router on a stick". This can be done with or without trunks.
http://www.cisco.com/en/US/products/hw/switches/ps679/products_configuration_guide_chapter09186a008007d1b7.html#39627
provides configuration examples for intervlan routing with a layer 2 switch.
Beware that router on a stick can be a performance bottleneck. L3 switching with the enhanced image will provide the best performance.
If you upgade to the enhanced image you can do layer 3 switching:
http://www.cisco.com/warp/public/473/howto_L3_intervlanrouting.html
http://www.cisco.com/en/US/products/hw/switches/ps679/products_configuration_guide_chapter09186a008007d1b7.html#39627
provides configuration examples for intervlan routing with a layer 2 switch.
Beware that router on a stick can be a performance bottleneck. L3 switching with the enhanced image will provide the best performance.
If you upgade to the enhanced image you can do layer 3 switching:
http://www.cisco.com/warp/public/473/howto_L3_intervlanrouting.html
The SMI version of the 3550 provides multilayer switching. You do NOT need an external router for inter-vlan routing.
To route between VLAN's, simply create the VLAN's:
en
conf t
vlan 2
Next, assign IP addresses to the VLAN interfaces (SVI):
en
conf t
int vlan1
ip address 192.168.1.1 255.255.255.0
no shut
int vlan 2
ip address 192.168.2.1 255.255.255.0
no shut
You need to also enable "IP routing" as it is disabled by default:
en
conf t
ip routing
You should at that point be routing between the two VLAN's/Subnets. Make sure the default gateway on the end systems is configured for the appropriate VLAN interface IP address.
To route between VLAN's, simply create the VLAN's:
en
conf t
vlan 2
Next, assign IP addresses to the VLAN interfaces (SVI):
en
conf t
int vlan1
ip address 192.168.1.1 255.255.255.0
no shut
int vlan 2
ip address 192.168.2.1 255.255.255.0
no shut
You need to also enable "IP routing" as it is disabled by default:
en
conf t
ip routing
You should at that point be routing between the two VLAN's/Subnets. Make sure the default gateway on the end systems is configured for the appropriate VLAN interface IP address.
I stand corrected. The SMI version added intervlan routing starting with 12.1(11)EA1:
http://www.cisco.com/en/US/tech/tk389/tk815/technologies_configuration_example09186a008019e74e.shtml
Give JFrederick29 the points!
http://www.cisco.com/en/US/tech/tk389/tk815/technologies_configuration_example09186a008019e74e.shtml
Give JFrederick29 the points!
Is it necessary to turn on IP routing on all switches on Lan or just the 2 switches where my Vlan 4 needs to talk to Vlan 1.
Also, I do not understand the default gatewey. Devices on Vlan 1 have the router for gateway. Do I change all devices on this vlan to point to vlan IP address for gateway. And does Vlan 4 devices use Vlan 4 ip address as gateway? Thanks in advance
Also, I do not understand the default gatewey. Devices on Vlan 1 have the router for gateway. Do I change all devices on this vlan to point to vlan IP address for gateway. And does Vlan 4 devices use Vlan 4 ip address as gateway? Thanks in advance
You can leave the VLAN 1 devices using the router for the gateway but the router will need a static route to the VLAN 4 subnet using the 3550 as the next hop. The VLAN 4 devices should use the VLAN 4 interface IP address as their default gateway.
Jfrederick29
Thanks for the help. Everything seams to be working well for the 3550 I enabled IP routing on but I was curious, I have
another 3550 that will have ports on Vlan 4, will I need to enable routing on this switch as well or will the first 3550 handle all intervlan routing for Vlan 4 no matter what switch traffic is coming from, I did put the static route in the router to point to vlan 4.
Thanks for the help. Everything seams to be working well for the 3550 I enabled IP routing on but I was curious, I have
another 3550 that will have ports on Vlan 4, will I need to enable routing on this switch as well or will the first 3550 handle all intervlan routing for Vlan 4 no matter what switch traffic is coming from, I did put the static route in the router to point to vlan 4.
Featured Post
We know how difficult it can be to evaluate Wi-Fi vendors, so we created this helpful Wi-Fi Buyer's Guide to help you find the Wi-Fi vendor that's right for your business! Download the guide and get started on our checklist today!
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Make the most of your online learning experience.
This article explains the fundamentals of industrial networking which ultimately is the backbone network which is providing communications for process devices like robots and other not so interesting stuff.
NetCrunch network monitor is a highly extensive platform for network monitoring and alert generation. In this video you'll see a live demo of NetCrunch with most notable features explained in a walk-through manner. You'll also get to know the philos…
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …
Suggested Courses
Course of the Month8 days, 14 hours left to enroll
604 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.