Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

RVS4000 VLAN feature buggy?

Hello,

I bought a RVS4000 Router last week. I configured two VLAN's (beside of the default one), VLAN ID 120 and VLAN ID 130. I configured an IP in the LAN section for both of them (192.168.120.1 and 192.168.130.1).

I then configured port 1-3 to be in VLAN ID 120 (Untagged) and port 4 to be the Trunk (VLAN ID 120 Tagged and VLAN ID 130 Tagged). The port 4 I connected a Cisco SLM224G. There I configured these two VLAN's too, and configured the uplink port as Trunk as well. The two network seem to be properly switched: I have access to 130 Hosts directly on the VLAN ID 130, and the other VLAN ID 120, I have access on all hosts connected to that VLAN ID as well (both, on the switch and the three ports on the router). On Layer 3, the RVS4000 is configured to route between the VLAN's. But I cant ping hosts on the other network! I configured the Router to be the default gateway... I think the source of that problem is the next one:

I can't ping from the Routers Maintainance Page to a host connected on Port 1-3 of the Switch (which is configured as VLAN ID 120 untagged). I reseted the router, and tested this simple use case again: Created two VLAN's, defined Port 2 to be in one of them, setted the IP's properly (192.168.120.1 for the Router on that VLAN), but stil, I cant ping from the Router to Host on that VLAN (Router=>192.168.120.10)! The other way around works (Host=>192.168.120.1)

The Routers Configuration:

WAN: PPPoE (works)

LAN: VLAN ID 1: 192.168.1.1 no DHCP

        VLAN ID 120: 192.168.120.1 no DHCP

        VLAN ID 130: 192.168.130.1 no DHCP

No DMZ:

Routing: Inter VLAN Routing: Enabled

L2 Switch: VLAN ID 1/120/130

Port 1: Untagged, 120untagged

Port 2: Untagged, 120untagged => Server connected

Port 3: Untagged, 120untagged

Port 4: Trunk, 1 untagged, 120tagged, 130tagged

Wiresharks shows me no ARP requests on that interface too... The product seems not to work porperly when I configure a port to be in a VLAN untagged, and try to ping to a host connected to that interface.

I have Firmware 3.1.0.0 (Website says 3.0.5.0 is the newest...??)

Bye

falstaff

Everyone's tags (4)
7 REPLIES
New Member

RVS4000 VLAN feature buggy?

Hi,

I know this is an old post but I am having the exact same problem and would like to know what the solution was.

Is there a solution? I have even upgraded to the most recent firmware version and it didn't cure this.

Cheers,

rw

New Member

RVS4000 VLAN feature buggy?

Hi Rob,

In the end I gave up using the VLAN feature. So I did not found a solution for that product...

Cheers,

falstaff

New Member

Re: RVS4000 VLAN feature buggy?

Thank you for the reply.

I really appreciate it.

Cheers!

--

Rob White

falstaff84 created the

discussion

"Re: RVS4000 VLAN feature buggy?"

To view the discussion, visit:

https://supportforums.cisco.com/message/3467654#3467654

Gold

Re: RVS4000 VLAN feature buggy?

Rob,

I set this up in our lab and found that it worked perfectly. See the following post:

https://supportforums.cisco.com/thread/2110576?tstart=0

One thing that I think that I did differently than falstaff84 is on the PC in VLAN 2 with DHCP off I set the Default Gateway to 192.168.1.1, the default IP of the router. He mentions 192.168.120.1 in his post. Did you change the Default Gateway on your devices in VLANs other than 1? I did not try using a DHCP server other than the RVS4000, although I did test with static IPs. Please test by following the steps in the post I referenced above. If it does not work properly there may be an issue with your router.

New Member

Re: RVS4000 VLAN feature buggy?

Hi,

I reset my router to the default settings and copied the steps exactly

outlined by the correct answer in the thread:

https://supportforums.cisco.com/thread/2110576

The computer hooked up to VLAN 2 has no internet access and cannot ping

the computer on VLAN1 with inter-VLAN routing turned on. The computer in

VLAN1 has internet access but cannot ping the computer in VLAN2 with

inter-VLAN routing enabled.

What firmware version did you get it working with?

Thanks,

--

Rob White

mpyhala created the

discussion

"Re: RVS4000 VLAN feature buggy?"

To view the discussion, visit:

https://supportforums.cisco.com/message/3469165#3469165

Gold

Re: RVS4000 VLAN feature buggy?

Hi Rob,

Hardware version 2 and firmware version 2.0.2.7. Did the computer on VLAN 2 get a valid IP address from the router? Open the Command Prompt and type ipconfig /all. Press enter and see what the IP, Gateway and DNS servers are. Mine had 192.168.2.100, GW 192.168.1.1, ISP DNS servers.

New Member

Re: RVS4000 VLAN feature buggy?

Hi,

I too have firmware V2.0.2.7 and I do receive a valid IP address:

IP Address: 192.168.2.100

Subnet Mask: 255.255.255.0

Default Gateway: 192.168.2.1

I do notice that the default gateway is not 192.168.1.1, but that is what

the router has assigned through DHCP, and going around to each device on

the network and changing the default gateway manually is out of the

question.

Thanks,

--

Rob White

mpyhala created the

discussion

"Re: RVS4000 VLAN feature buggy?"

To view the discussion, visit:

https://supportforums.cisco.com/message/3469354#3469354

4513
Views
0
Helpful
7
Replies
CreatePlease to create content