WAN Failover with RV320 not working

[j.spiess]

Hello!
We have a brand new RV320 with the latest firmware in our network. Setup is with 2 WAN connection. Primary is a static IP connection. Secondary is a PPPoE conection. When ISP Service at WAN1 is OK, we have no problem, but now our primary ISP connection failed (ping fails, Ethernet connection is up though) and the secondary connection does not kick in. It seems that WAN2 is connected for a very short time and the disconnected again - which leaves us without internet service. I now manually switched the primary WAN interface to WAN2 and that works - but that is nit the automatic solution this product should provide. Please advice on what to do...

Sample Log Entries (after a reboot):

2013-10-15, 03:48:10	System Log	gateway : System is up
2013-10-15, 03:48:19	Network Log	WAN connection is up : 212.186.xxx.xxx/255.255.255.248 gw 212.186.xxx.xxx on eth1
2013-10-15, 03:48:19	System Log	WAN2=95.143.xxx.xxx WAN2 MASK=255.255.255.255 WAN2_GATEWAY=77.220.xxx.xx WAN2_DNS1=92.63.xxx.xxx WAN2_DNS2=93.185.xxx.xxx mtu=0
2013-10-15, 03:48:25	Network Log	WAN connection is up : 95.143.xx.xxx/255.255.255.255 gw 77.220.xxx.xx on ppp2
2013-10-15, 03:48:32	System Log	Terminating on signal 15
2013-10-15, 03:48:32	System Log	Connect time 0.3 minutes.
2013-10-15, 03:48:32	System Log	Sent 28919 bytes, received 15614 bytes.
2013-10-15, 03:48:32	System Log	Connection terminated.
2013-10-15, 03:48:32	Network Log	WAN connection is down
2013-10-15, 03:48:32	System Log	Exit.

Best regards,

Philipp.

[jeffrrod]

Dear Jean-Philipp,

Thank you for reaching the Small Business Support Community.

I suggest you to uncheck the "network service detection" setting under System Management -> Dual WAN -> WAN2 (edit)

If the problem persists then try unchecking the same setting on WAN1 as well.  Please give that a try and let me know, I'll be looking forward to hear from you.

Kind regards,

Jeffrey Rodriguez S. .:|:.:|:.
Cisco Customer Support Engineer

*Please rate the Post so other will know when an answer has been found.

[j.spiess]

Hello!

We just another Failure on WAN1 ISP side. Again no automatic switching - I unchecked NSD on WAN 2. See log below:

2013-10-28, 14:18:54	Network Log	NSD FAIL WAN[1]
2013-10-28, 14:18:59	System Log	WAN2=95.143.xx.xxx WAN2 MASK=255.255.255.255 WAN2_GATEWAY=77.220.xxx.xxx WAN2_DNS1=92.63.xxx.xxx WAN2_DNS2=93.185.xxx.xx mtu=1460
2013-10-28, 14:18:59	Network Log	WAN connection is up : 95.143.xx.xxx/255.255.255.255 gw 77.220.xx.xxx on ppp2
2013-10-28, 14:19:04	Network Log	NSD SUCCESS WAN[1]
2013-10-28, 14:19:05	System Log	Terminating on signal 15
2013-10-28, 14:19:05	System Log	Connect time 0.1 minutes.
2013-10-28, 14:19:05	System Log	Sent 24797 bytes, received 18123 bytes.
2013-10-28, 14:19:05	System Log	Connection terminated.
2013-10-28, 14:19:06	System Log	Exit.
2013-10-28, 14:19:06	Network Log	WAN connection is down

Again same symptom... router switches to WAN2 for a very short period and then goes back to WAN1 for what evere reason...

When I disable NSD on WAN1 and WAN2, nothing at all happens, the router not even tries to switch over to WAN2...

Best regards,

Jean-Philipp SPIESS.

[mhsherman]

I have the same problem.   WAN1 150MB Cable; WAN2 is 6MB ADSL.  I want to use fall over, but when I test it, it does not fall over.  The WAN2 status shows all zeros on the IPv4 even though I can see it  is fully up.

[j.spiess]

Hello!

I just want everybody know, that the problem was finaly solved after a remote session with cisco support.

It turned out to be a rather simple issue, that could have been easily avoided by proper interface design:

Although there are multiple Checkboxes to select targets for Network service detection, only one should be selected at a time, because if multiple are selected, the first target may be online while others are not. In that case Network Service detections stops at the first successful target and does not check the others, causing failover not to work.

I would suggest radio buttons in the next firmware version.

Best regards,

Jean-Philipp.

[Pavan Katti]

Hi Jean-Philipp,

I also facing the same issue of Auto failover between 2 WAN connection. Primary is a static IP connection. Secondary is a PPPoE conection.

Below are my doubts:

1) Smart Link Backup---WAN 1 should selected as primary or not, or i have to select Load Balane

2) In NSD, on both WAN interface setting we have to set remote host or only to the single WAN interface

Kindly update, if it is possible can u please share me the screenshots of same.

Also like to mention that in my auto failover test, I m 1st making WAN1 down and then testing whether traffic is shifted over WAN2 and then making WAN1 UP and test whether traffic is shifted back over WAN1.

As far as my autofailover testing on same router, I was able to failover from WAN1 to WAN2 but I was facing problem when I make

WAN1 UP, traffic was not shifting back to WAN1.

Regards

Pavan Katti

[radko.k]

Dear Jean-Philipp

We have two routers in the office

one V320 and one V320

move to new office and there we will have two ISP links one main and one for back up.

Could you tell me the best way to configure them routers for fail over in case one link fail and we need not interuption of the service.Thanks

Kindest Regards

Radko

[Pavan Katti]

Hello Radko

U can check my Discussion : Cisco RV320 fail over between WAN & USB Issue

Where I have documented & please rate & vote if you like my post.

Regards

Pavan

[radko.k]

Dear Jean-Phillip.

In my office we have RV325 router and 5 cisco48ports managed switches.

At present we strugle to distribute IP addresses to all users and create Vlans as we have one with range 07 to 149  not enough IP for users and IP Phones so IP start duplicate could you please help me with solution for that how to create one or two more Vlans and synchronize them with the 5 Cisco SG-200/50 Switches all we need configuration for one more vlan with same range /number of available IPs Thank you 

[svenberglund]

Thanks Jean-Philippe for sharing this important insight. I decided to add some thoughts to this thread even though it is old. This is where you end up googling "rv 325 failover not working" and I think many of us who had this problem made the same mistake as you. Namely we assume that there is a "and" condition implied between the different NSD options that you can check. When in reality it is an "or" condition. This is indeed not well documented by Cisco, not even hinted, and I absolutely suggest that it should be clarified. Perhaps examplified a little better in the manuals. For example on this page:

https://www.cisco.com/c/en/us/support/docs/smb/routers/cisco-rv-series-small-business-routers/smb4242-dual-wan-configuration-on-rv320-and-rv325-vpn-router-series.html

The example configuration that is depicted shows a combination of "default gateway" and "remote host", and moreover the remote host is specified as a internal ip (192.168 something). I believe this configuration makes absolutely no sense for 95% of the users since what we want to do is to test against some external (internet) high availability services. Most of us deploy this machine to ensure internet connectivity, not that our internal gateways or DSL modems or what not are alive. And by following the example above we are tricked to leave the "Default gateway" box ticked which ruins everything.

Although I do think it makes sense that you can combine two different external services in the NSD test.  For example in my configuration I have now put remote host: 8.8.8.8 and DNS lookup host: www.opendns.com. It seems to work, as long as one of them responds NSD is not failing. However it is a little awkward that I have to use different detection schemes (direct ping vs ping with dns lookup) in order to combine two services. IMHO It would be more logical if I can choose once and for all whether or not to include dns lookup in the NSD. In other words, the config would make more sense if I could list either multiple (at least two) IP addresses or multiple (2+) host names. 

[bibiii79]

This solved my issue, Thanks a lot, i did apply into my RV325 router , after uncheking the default gateway (in the WAN1, edit and WAN2 edit), and check in both:  remote host: 8.8.8.8 and Dns lookup: www.opendns.com solved the failoiver problem from WAN1 to WAN2!!!! ...... in the meantime i decided to go with Load Balance ... and increase the speed :) 

Thanks again!!!!