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. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

WRVS4400N V2 Not addressable after 24 hours running

I recently installed a WRVS400N V2 to run a large residential network with approximately 120 devices (90 wired into 3 main switches and about 20 wireless devices).  The router won't allow me to login (address 192.168.1.254) to the web GUI after running for about 24 hours.  I have the wireless AP turned off as I use my own unifi network. I used DHCP reservation for approcimately 35 devices (I think there was a limit of 50) and used about 50 static IP from 192.168.1.2 through 192.168.1.110.  I have my DHCP pool start at 192.168.1.130 through 192.168.1.252.  I have insured that there are no overlapping static IP address by making an excel spreadsheet with all my devices by MAC address.

After about 24 hours all my devices with a DHCP reservation drop off line and are not addressable.  All my static IP devices (set manually wirthin the device itself) continue to function without issue.  The router itself is not addressable at 192.168.1.254 after running for about 24 hours.  The router runs in a well ventilated closet with other networking gear and doesn't feel overly hot/warm.  To my knwledge the V2 router allows he use of the address 192.1768.1.2 which is assigned to a device by static DHCP reservaion.  I'm not sure what may be the issue. 

Is this router designed to handle a network this size?  Could it be an issue where I am maxing out the router CPU?  Any suggestions on looking at the router logs/config to see what the issue may be?  Any suggestions?

1 REPLY
New Member

WRVS4400N V2 Not addressable after 24 hours running

As an update, I am on the latest firmware.  I created a syslog server and was able to see what the router reported before locking up:

I see this repeatedy:

0-order allocation failed (gfp=0x1d2/0)

0-order allocation failed (gfp=0x1d2/0)

0-order allocation failed (gfp=0x1d2/0)

0-order allocation failed (gfp=0x1d2/0)

306
Views
0
Helpful
1
Replies