RVS4000 and VLANs

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by doubleH, Oct 16, 2007.

  1. doubleH

    doubleH LI Guru Member


    Just looking into a RVS4000 to see if it can do what I want it to do and am looking for some input. I currently have a Procurve 1800-24 layer 2 internal switch. I would like to create VLANs on my internal switch and then use the RVS4000 as the router so that the VLANS on the 1800-24 can route to each other as well as get on the internet. Is this possible?

    Does the RVS4000 support assigning IP addresses to VLANs?

    If the RVS4000 doesn't do this I would be open to other suggestions.

  2. Solinga

    Solinga LI Guru Member

    Limited VLAN capabilities

    Hi doubleH,

    I tried a few things with a PowerConnect 2716 (Dell layer 2) switch. Here is what I experienced:

    The RSV4000 should support up to 4 VLANS beside default VLAN 1. With my beta firmware 1.13 its actually 4 VLANS including VLAN 1 and with previous firmware it is reported that max VLAN ID can 4, even if I never verified it. In any case, you are restricted to 4 VLANs.

    When you set up the VLANs (in my case 1, 20, 30, 40) it depends on the sequence you set them up which subnet is assigned to them.

    VLAN 1 has
    2nd VLAN has regardless of VLAN ID
    3rd VLAN has regardless of VLAN ID
    4th VLAN has regardless of VLAN ID

    There is a DHCP server running for each subnet but it's not guaranteed that you get an IP from the the VLAN-subnet the DHCP client is attached to. I had an web server attached to 4th VLAN but it got an IP from the 2nd VLAN. It's a bit confusing.

    Fixed IP assigments (IP to MAC) to avoid lease termination only works in VLAN 1 subnet, settings for other subnets are taken but ignored.

    Inter-VLAN routing can be generally switched on and of but it seems to work only in one direction. PCs attched to VLAN 1 find and work with PC from other VLANs but not vice versa. Sometimes you first need to ping the other PCs to get it working. Entries in the routing table between VLANs are to my knowledge ignored but I didn't spend much time on it.

    I've set up 4 trunk lines with my switch, trunk ports tagged (with exception of VLAN 1 because my Dell switch does not allow tagged ports on VLAN 1, I did not use the 'trunk' option for the RSV4000 ports because it was not clear to me how it works. All other ports on the Dell were untagged but had corresponding VLAN IDs assigned. So far it worked fine, all attached PCs had access to the internet via WAN port.

    DMZ server or port settings for HTTP of FTP only works in VALN 1 because the RSV4000 masks are predefined for 192.168.1.x IP settings. So each DMZ server or PCs with open ports need to belong to this subnet.

    That's more or less all I can tell you.
  3. doubleH

    doubleH LI Guru Member

    thank you very much for your reply. so it sounds like it can do what i was looking for, but it just doesn't do it well which is the general theme on any discussion on this device. what a shame because on paper it looks awesome.

    in the mean time i have since been looking at FreeSCO and will be persuing that option.

    thanks again!
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice