What's new

Cisco SB RV082 + switches with vlan tag feature

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

rgilja

New Around Here
Hi guys,

I have a small lab datacenter at home, with 1 iSCSI server and 3 VMware ESXi 5.1 hosts. I run some windows servers and a few linux servers.

And a couple of years ago I bought a Cisco SB RV082 Dual VPN Router and a Netgear smart switch to be able to have more segmentantion and managability on my network and VMs. I was really happy with the Cisco router, because of the stability and functionality.

But after a while I wanted to learn VLAN and vlan tagging, and found out that I wanted to create interfaces for the different vlans. I installed the pfSense open source firewall, to be able to create these VLANs with tagging from the firewall and across switches/esxi hosts. The pfSense was installed as a VM on one of the vSphere hosts, and that became a headache if something happened to the host. So I've decided to switch back to the Cisco SB RV082.


So here's my question:

Is it possible to still have all these VLANs I've created on the switches, and on the ESXi Hosts when I swap to the Cisco router? Even if the Cisco only support port based VLAN, this should not be a problem? Because of the Multiple subnet feature? These VLANs will have Internet access and should not have access to each other. Only the primary network/management network should have access to the vlans.

Let's say my primary network is 192.168.1.X and I have 5 vlans with IP 192.168.2.X, ..3.X, ..4.X etc. To be able to use these VLANs across all the devices, do I need to assign each VLAN on the Cisco to a specific port? Meaning that I will have 5 cables from the Cisco to the switch?

I will probably have a domain controller with DHCP and DNS on a few of the VLANs I create. So DHCP for the different VLANs will be created like that, and will not be required from the firewall (which RV082 does not support?)


In my head, this text/topic makes sense. But I'm not entirely sure if you guys understand what I mean or want to accomplish here. So do not hesitate to ask :)


Thanks in advance.
 
That appears to be the case. You simply have 5 cables from the RV082 going to 5 ports on the switch. The only main difference is that you assign these ports (on the switch) as access ports (Untagged with PVID) rather than trunk ports (Tagged).

AFAIK, the RV series won't do DHCP/ DNS on the additional interfaces but you can assign multiple subnets (may need firmware update if you haven't done so in a while). You'll need a DHCP server on each of these 'VLAN' subnets to assign IP addresses (Win server perhaps?).
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top