5610 and Netgear FVS338 going down?

[whiteEEnerd]

I have a system that has 5 remote FVS338s. The users are complaining that from time to time their remote phones will go down. I set everything up using the Avaya tech tip.

The only thing I can think of is static IPs? Right now they are all using DHCP to get their address. 3 of the 5 have the same router, and use the 192.168.1.X range. It could be possible that from time to time they will get a new IP address that matches the IP of one of the other users and kicks one or the other off. Does anyone know if this is the case? Has anyone ever had any trouble with DHCP?

Would doing anything with QOS help this issue?

The main IP Office is running 4.2(11) and the remote sites are all over the central US.

Thanks!

 

[tanderson3733]

Are you saying you have 3 different locations with the same 192.168.1.x subnet? Yes this will cause all kinds of problems. Each remote location should have a unique IP Subnet.

 

[whiteEEnerd]

I should specify that these remote locations are all single phone systems, using the VPN phone firmware.

I know that each should have a unique IP subnet when doing a full VPN, but is that necessary for client VPNs?

 

[tanderson3733]

OK that's different than 5 remote FSV338s. The Netgear should be assigning the VPN phones local addresses, which are used for communication with the IP Office. The IP Address the phones have on their physical network can pretty much be anything.

 

[tanderson3733]

Hit submit then remember the other half of the post...nice!

Anyway, it sounds more like Tunnel Lifetime expiring than DHCP lease. DHCP is designed to pretty much keep an active connection active, from both ends. With an 8 hour "lease duration" the client will usually check with the DHCP server every 4 hours to see if it's OK to keep using the same IP Address, and unless anything's changed the DHCP server usually permits it.

You can confirm the tunnel problem by checking it's status once the phone goes down...chances are the VPN won't be up to that phone.

 

[whiteEEnerd]

You are right in that the VPN is down on the phone when the phone goes down. The IKE lifetime is 28800 and the VPN lifetime is 3600. Do you think either of those need changed?

 

[tlpeter]

Always set the vpn life time as high as you can
This is your problem


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Implement IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[whiteEEnerd]

What number do you recommend? I was used those values because it is what Avaya used:

http://marketingtools.avaya.com/kno...edProjects/bulletins/techtips/184_techtip.htm

 

[tlpeter]

As high as possible
You could se tit for 24 hours ans set it at the middle of the night so the phone reboots in the middle of the night when it looses connection
After a while (when no connection) the phone automaticly reboots to try getting the connection back


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Implement IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[whiteEEnerd]

I will increase the time on the policies, thanks!

Is it necessary to have different IKE policies and VPN policies for each phone? Right now I do, meaning I have 5 VPN phones, so I have 5 VPN policies, and 5 IKE policies. Can they all be set to use the same one, or can that cause problems?

I am using the "Option 2" for the Avaya Tech Tip.

Thank You!