srp521 stops arp-ing

Sage Major · ‎01-25-2012

We have been using firmware 1.1.19 We now have about 50 in the field. Almost daily we are having 1 or more devices which are no longer responding. I can do a shutdown the interface on the other side but it still does not not come up. I have upgraded a few to 1.1.24 in the last two days but this seems to be related to the uptime of the the device.

Even though the remote device shows a up/up the mas address table does not show any connection.

Is there any kind of known bug that would be causing this?

Andrew Hickman · ‎01-25-2012

Hi Sage,

Thanks for the feedback. Can you tell me what type of service / modem these devices are connected to please?

If I understand correctly, you are not seeing ARPs or a MAC table entry for the WAN interface and that while this condition occurs, you can't access the internet, but can access the device from the LAN side?

If this is the case, the next time this happens, could you please grab a debug file from the Admin > Remote Debug page and send it to us - either directly to me, or via the SBSC.

Regards,

Andy

Sage Major · ‎01-25-2012

They are all plugged into either adtran 832T units or in one instance the Wan side of another spr521.

We also have used adtran ta-900 routers as well as Cisco wrv210 routers which do not experience this issue so I believe it to be related to the cisco not the 832T.

I do not know if I can access it from the lan side, these are customer prem equipment and the customer reboots the units to get access back. The rest is correct. Next time I see one down I will collect debug info.

Sage Major · ‎01-26-2012

It happened to another customer today

I went out to the site and found the following

The router would not give out an ip address on DHCP.

With a static ip set I could not ping the ip of the inside interface.

When I pushed the wps button the light did not come on.

When I plug in a cable I see the link lights come on both on the lan and wan side.

I can see the wireless ssid but could not connect

After a reboot everything worked, I could connect via wireless and lan.

Andrew Hickman · ‎01-26-2012

Thanks Sage,

We've had the odd report of crashes like this - you seem to be suffering more than most.

Can you send me a backup file from one of the sites that has seen this problem please? Please send it directly to me and include the password, so that I restore to one of my devices and get access (feel free to temporarily change the password to something you are ok shareing before creating the backup).

In addition, can you please also provide an copy of the XML configuration file (http://SRP_address/admin/config.xml&xuser=admin&xpassword=)

Have you seen this issue on any sites running the latest code yet? If so, please collect the backup and config from that site.

Many thanks

Andy

Andrew Hickman · ‎01-30-2012

Hi Sage,

Have you seen any repeat of this issue with units running 1.1.24 yet?

Many thanks

Andy

Sage Major · ‎01-30-2012

I have not yet had one, but we only have upgraded about 5 or so of them.

I sent you the text config. How do I send you the file?

Sage Major · ‎01-30-2012

We just had another one on 1.1.19 go down. The ones which stop working all seem to have been up for more than 2 months so if we are going to see an issue with a 1.1.24 I would not expect to see it for quite a while.

Andrew Hickman · ‎01-31-2012

Hi Sage,

Can I suggest that you upgrade to 1.1.24 throughout - there were many improvements in this release over 1.1.19 and I'd like to ensure that we aren't chasing ghosts in 1.1.19.

If you'd rather not visit each SRP individually to upgrade them, you could use the XML provisioning interface to have them upgrade themselves. To do this, you'll need to place the 1.1.24 image on an HTTP or TFTP server visible to all of the devices, then apply the following XML configuration:

http://[server_address]:[port]/[path]/[filename]

You can use CURL to push this XML file directly to the SRP, or you can save the XML file to a file server and use the SRP resync URL to collect it. For information on these processes, please see:

https://supportforums.cisco.com/docs/DOC-16131

Hope that helps,

Andy

Sage Major · ‎01-31-2012

I can not get it to work

curl -d upgrade.xml "http://remote_ip:8080/admin/config.xml/xuser=admin&xpassword=test"

upgrade.xml

tftp://69.28.108.9/cisco/SRP520_1.01.24.bin

With this I get

The server could not verify that you are authorized to access the requested URL

However if I access

http://remote_ip:8080/admin/config.xml/xuser=admin&xpassword=test in a web browser I get the full xml file.

originally I thought it was because my password had $ and ! in it so I changed it to test and I still get the error using Curl

This is being done from a linux box.

Andrew Hickman · ‎01-31-2012

Hi Sage,

It should be an '&' before xuser, not an '/'.

Andy

Andrew Hickman · ‎01-31-2012

....also, don't forget to prepend the config file name with an "@".

eg:

curl -d @upgrade.xml "http://remote_ip:8080/admin/config.xml&xuser=admin&xpassword=test"

Sage Major · ‎01-31-2012

Also If I just do the resync with only will I wipe out my current config

upgrade.xml

tftp://69.28.108.9/cisco/SRP520_1.01.24.bin

Andrew Hickman · ‎01-31-2012

No, XML configurations are additive, so you just change the parameters you need, the rest will be left as is.

Andy

Sage Major · ‎02-13-2012

Andrew

I had one running 1.1.24 go down today. It was my test router so I was able to confirm that I could not access it from either side. and could not connect to wireless.

This was the first one I upgraded to 1.1.24 when you first suggested it.