Improve company productivity with a Business Account.Sign Up

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 6273
  • Last Modified:

Routing between VLAN's using Cisco SMB SG-300-28


I've purchased a Cisco SMB SG300-28 switch in hopes it can be used to create the following setup. The switch is currently in Layer3 mode.

I have 2 devisions in my company. One is for IT services, the other for hosted services, data backup and the like. I'd like to keep these separated logically via VLAN's on the switch.

Devision1 - VLAN 10 (IT Services)
- Office Desktops, Printers, Scanners, People work here
- Switch and server rack are in another room. Port 2 will connect to an unmanaged "dumb" switch in my actual office via a long CAT6. 3-6 will be empty unless i need them for something down the road in the office.
- Ports 2-6 on my switch.

Devision2 VLAN 20 (Hosted Services)
- Servers, Email Hosting, FTP, Other Stuff, Only servers here.
- Ports 7-20 on my switch.

- 2 QNAP NAS each using LACP
- iSCSI for VMWare
- Ports 21-24

Router runs an Open-Source platform called Untangle. It's being used for NAT / Port Forwards and VPN. DHCP and DNS is controlled by the domain controller. If i need to use a big-boy router i can switch to RouterOS by Microtik.

My office ( must be able to talk with both the servers and the SAN. I thought this would involve a static route, but that hasn't seemed to work.

How would i set this up?

What is involved to allow communication between VLAN's?

Does the communication go through the router and then to the other VLAN? Will Untangle even work for this? (It does NOT support VLAN's in any way. It strips the tags)

I'll need DHCP in my office. What would provide it?
(All workstations are Mac's and not networked in a domain. Simply dont need it for what goes on.)

Unfortunately i am not familiar with this level of networking. I mostly deal with software, Exchange, AD, GP, etc. I hope that my questions have been clear and my situation described correctly.

I sincerely thank those who reply in advance.
  • 3
1 Solution
Robert Sutton JrSenior Network ManagerCommented:
Is 'Ip routing' enabled on the device?
Can you post the config of the switch?
VCSLIAuthor Commented:
The 300 series of their SMB switches does not have Cisco iOS on it. It runs some other thing which no one seems to like :P.

I am not sure how i'd export the config or know how to tell if the switch even has this feature.
VCSLIAuthor Commented:
Marius GunnerudSenior Systems EngineerCommented:
Most of the 300 switches support basic Layer 3 capabilities. That would say that they only support static routes and NO routing protocols.  If I remember correctly they can support up to 16 static routes.

That being said, if you enable ip routing (Layer 3) on the switch and configure IP addresses on the VLAN interfaces, and given that all networks/vlans connect to the 300 switch, you should not need to configure any static routes as the switch is directly connected to all the networks and knows where to send the traffic. The only time you would need to configure static routes is if, for example, you had a different network hanging off of the Officy Stuff switch which is not directly connected to the 300 switch. then you would need to configure a static route pointing to Officy Stuff switch as the next hop.

Keep in mind it is not enough just to have the VLAN configured on the 300 switch, you also need to configure IP addresses on those VLAN interfaces. Also you will need a default route pointing to the Untangle Router so that traffic can reach the internet.
VCSLIAuthor Commented:
Your answer was correct. Excuse the delay. Thank you!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now