PAP2T reboots every morning, reason H633a08fe

[CraigBosCisco]

Greetings, forum.

I recently installed a PAP2T in my home, connected to Callcentric. It is working fine for us, except for one thing.

I've noticed that every morning it reboots with reason H633a08fe.  Its running software 5.1.6(LS) and its hardware version is 0.3.5.  Each reboot is about a minute and a half after a DHCP Renew, and it is happening about (but not exactly) every 24 hours.

Here is a typical reboot as listed in the Syslog:

2011-02-06 08:23:30    Local7.Debug    192.168.1.15    DHCP renew, lease time: 86400 seconds
2011-02-06 08:25:02    Local7.Debug    192.168.1.15    System started: ip@192.168.1.15, reboot reason:H633a08fe
2011-02-06 08:25:02    Local7.Debug    192.168.1.15    System started: ip@192.168.1.15, reboot reason:H633a08fe
2011-02-06 08:25:02    Local7.Debug    192.168.1.15    DHCP lease time: 86400 seconds
2011-02-06 08:25:02    Local7.Debug    192.168.1.15        subnet mask:    255.255.255.0
2011-02-06 08:25:02    Local7.Debug    192.168.1.15        gateway ip:    192.168.1.1
2011-02-06 08:25:02    Local7.Debug    192.168.1.15        dns servers:   
2011-02-06 08:25:02    Local7.Debug    192.168.1.15    192.168.1.1

Interestingly, the 86400 second lease time is 24 hours.

The reboot reason is not on the reboot reason list (https://supportforums.cisco.com/docs/DOC-9889).

Any ideas on what is causing this and how to stop it?

Thanks for any information or assistance.

/cb

[CraigBosCisco]

Update on this.

I've contacted Cisco support and they have authorized a factory return.  No complaints there.

But I have purchased and commissioned a second PAP2T (so I have a hot spare).  The second PAP2T behaves exactly the same as the first -- reboots every 24 hours with the same reason code.

So now I don't think this is a hardware failure.  It must be something in the firmware, configuration, or something like that.  I don't think I will bother to send the hardware back to the factory...

Still looking for any info.

Thanks.

[Andrey Cassemiro]

Hi Craig,

Could you send us a copy from your configuration(hiding personal information)?

Thanks,

Regards.

[CraigBosCisco]

Yes I would be happy to post the configuration.  Can you point me instructions on how to do this, particularly the part about removing personal information?

I have a .zip file with all the configuration web pages captured, but the personal info is still there.  I tried editing the HTML, but it is very messy, 225KB of dense HTML times 9 files.  And the MS Word WYSIWYG editor just made a mess also.

Thanks for your response.

[Andrey Cassemiro]

Hi Crag,

Remove your personal information (only user and password) save the settings and later save the page as a MHT file.

Regards.

Andrey Cassemiro.

[CraigBosCisco]

OK, here it is.  Firefox doesn't have an option to save as .mht, but this should still work.

Thanks for taking a look.

/cb

[CraigBosCisco]

UPDATE:

On advice in another forum, last night I made two changes to try to work around the problem.  I turned the box vertical to provide better airflow and cooling through the vents, and I disabled DHCP, assigning a static IP address and netmask.  The PAP2T has now exceeded 24 hours of uptime for the first time that I know of.  I'm going to let it keep running to see how long it lasts.

Gut feel says it was DHCP that was crashing the PAP2T.  But I sure would like to know what reboot reason H633a08fe means.

[radomir.tomis]

I can confirm that "reboot reason:H633a08fe" is caused by blocked DHCP renewal packets.

See:

   crash("c:/RCS/burgundy/net/src/dhcp.c", "", 0x08fe, "drn");

at:

  http://www.broadbandreports.com/forum/remark,25545321

In our case, the DHCP renewal reply packets were blocked by our firewall (/var/log/messages: "dhcpd: send_packet: Operation not permitted")