SPA2102 reboots approx. every 10 minutes

Unanswered Question
Mar 30th, 2009

Hi,

My brand new SPA2102 reboots approximately every 10 minutes.

I have recorded some log information, but I have a bit of a hard time making sense of it all.

Below is a part of the syslog I captured.

The reference domain, unref domain and last unref for domain messages keeps repeating every 5 seconds. Is that normal? gw1.fonet.dk is what I was told to put as proxy under the line config page.

Approximately every 10 minutes or so the router resets as showen at timestamp 2009-03-30 23:42:19. I can not figure out what reboot reason H0 is. Can anyone please help? Is my SPA2102 broken or is just a config issue.

Best regards.

Peter Karlsen

2009-03-30 23:41:36 Local3.Debug 192.168.0.1 RSE_DEBUG: reference domain:gw1.fonet.dk
2009-03-30 23:41:36 Local3.Debug 192.168.0.1 RSE_DEBUG: reference domain:gw1.fonet.dk
2009-03-30 23:41:41 Local3.Debug 192.168.0.1 RSE_DEBUG: unref domain, gw1.fonet.dk
2009-03-30 23:41:41 Local3.Debug 192.168.0.1 RSE_DEBUG: unref domain, gw1.fonet.dk
2009-03-30 23:41:41 Local3.Debug 192.168.0.1 RSE_DEBUG: last unref for domain gw1.fonet.dk
2009-03-30 23:41:51 Local3.Debug 192.168.0.1 RSE_DEBUG: reference domain:gw1.fonet.dk
2009-03-30 23:41:51 Local3.Debug 192.168.0.1 RSE_DEBUG: reference domain:gw1.fonet.dk
2009-03-30 23:41:56 Local3.Debug 192.168.0.1 RSE_DEBUG: unref domain, gw1.fonet.dk
2009-03-30 23:41:56 Local3.Debug 192.168.0.1 RSE_DEBUG: unref domain, gw1.fonet.dk
2009-03-30 23:41:56 Local3.Debug 192.168.0.1 RSE_DEBUG: last unref for domain gw1.fonet.dk
2009-03-30 23:42:19 Local3.Debug 192.168.0.1 RSE_DEBUG: reference domain:gw1.fonet.dk
2009-03-30 23:42:19 Local0.Info 192.168.0.1 System started:
ip@xxx.xxx.xxx.xxx, reboot reason:H0
2009-03-30 23:42:19 Local0.Info 192.168.0.1 System started:
ip@xxx.xxx.xxx.xxx, reboot reason:H0
2009-03-30 23:42:19 Local1.Debug 192.168.0.1 <009>gateway ip:<009>xxx.xxx.xxx.xxx
2009-03-30 23:42:19 Local1.Debug 192.168.0.1 <009>dns servers(2):<009>
2009-03-30 23:42:19 Local1.Debug 192.168.0.1 193.162.153.164
2009-03-30 23:42:19 Local1.Debug 192.168.0.1 194.239.134.83
2009-03-30 23:42:19 Local1.Debug 192.168.0.1 <010>
2009-03-30 23:42:19 Local0.Info 192.168.0.1 [0]Reg Addr Change(0) 0:0->818ee0fa:5060
2009-03-30 23:42:19 Local0.Info 192.168.0.1 [0]Reg Addr Change(0) 0:0->818ee0fa:5060
2009-03-30 23:42:19 Local3.Debug 192.168.0.1 RSE_DEBUG: reference domain:gw1.fonet.dk
2009-03-30 23:42:19 Local0.Info 192.168.0.1 [1]Reg Addr Change(0) 0:0->818ee0fa:5060
2009-03-30 23:42:19 Local0.Info 192.168.0.1 [1]Reg Addr Change(0) 0:0->818ee0fa:5060
2009-03-30 23:42:19 Local3.Debug 192.168.0.1 RSE_DEBUG: reference domain:gw1.fonet.dk
2009-03-30 23:42:19 Local3.Debug 192.168.0.1 RSE_DEBUG: reference domain:gw1.fonet.dk
2009-03-30 23:42:19 Local3.Debug 192.168.0.1 [0]RegOK. NextReg in 3570 (1)
2009-03-30 23:42:19 Local3.Debug 192.168.0.1 [1]RegOK. NextReg in 3570 (1)
2009-03-30 23:42:21 Local2.Debug 192.168.0.1 [0]Start tone 21(2)
2009-03-30 23:42:21 Local2.Debug 192.168.0.1 [1]Start tone 21(2)
2009-03-30 23:42:22 Local2.Debug 192.168.0.1 [0]Start tone 7(2)
2009-03-30 23:42:22 Local2.Debug 192.168.0.1 [1]Start tone 7(2)
2009-03-30 23:42:22 Local2.Debug 192.168.0.1 [0]Start tone 7(2)
2009-03-30 23:42:22 Local2.Debug 192.168.0.1 [1]Start tone 7(2)
2009-03-30 23:42:22 Local2.Debug 192.168.0.1 [0]Start tone 18(2)
2009-03-30 23:42:22 Local2.Debug 192.168.0.1 [1]Start tone 18(2)
2009-03-30 23:42:22 Local3.Debug 192.168.0.1 IDBG: st-0
2009-03-30 23:42:23 Local3.Debug 192.168.0.1 fs:10535:10535:65536
2009-03-30 23:42:23 Local3.Debug 192.168.0.1 fls:af:1:0


2009-03-30 23:42:23 Local3.Debug 192.168.0.1 fbr:1:3000:3000:169eb:0002:0003:3.3.6
2009-03-30 23:42:23 Local3.Debug 192.168.0.1 fhs:01:0
001:upg:app:0:3.3.6
2009-03-30 23:42:23 Local3.Debug 192.168.0.1 fhs:02:0
002:upg:app:1:3.3.6
2009-03-30 23:42:23 Local3.Debug 192.168.0.1 fhs:03:0
003:upg:app:2:3.3.6
2009-03-30 23:42:23 Local3.Debug 192.168.0.1 fhs:04:0:ffff:
2009-03-30 23:42:23 Local3.Debug 192.168.0.1 fhs:05:0
000:fp2:pidto:8388164
2009-03-30 23:42:23 Local3.Debug 192.168.0.1 fu:1:69fd, 0003 0001
2009-03-30 23:42:24 Local3.Debug 192.168.0.1 RSE_DEBUG: unref domain, gw1.fonet.dk
2009-03-30 23:42:24 Local3.Debug 192.168.0.1 RSE_DEBUG: unref domain, gw1.fonet.dk
2009-03-30 23:42:24 Local3.Debug 192.168.0.1 RSE_DEBUG: unref domain, gw1.fonet.dk
2009-03-30 23:42:24 Local3.Debug 192.168.0.1 RSE_DEBUG: unref domain, gw1.fonet.dk
2009-03-30 23:42:24 Local3.Debug 192.168.0.1 RSE_DEBUG: last unref for domain gw1.fonet.dk
2009-03-30 23:42:34 Local3.Debug 192.168.0.1 RSE_DEBUG: reference domain:gw1.fonet.dk
2009-03-30 23:42:34 Local0.Info 192.168.0.1 [0]Reg Addr Change(0) 0:0->818ee0fa:5060
2009-03-30 23:42:34 Local0.Info 192.168.0.1 [0]Reg Addr Change(0) 0:0->818ee0fa:5060
2009-03-30 23:42:34 Local3.Debug 192.168.0.1 RSE_DEBUG: reference domain:gw1.fonet.dk
2009-03-30 23:42:34 Local0.Info 192.168.0.1 [1]Reg Addr Change(0) 0:0->818ee0fa:5060
2009-03-30 23:42:34 Local0.Info 192.168.0.1 [1]Reg Addr Change(0) 0:0->818ee0fa:5060
2009-03-30 23:42:39 Local3.Debug 192.168.0.1 RSE_DEBUG: unref domain, gw1.fonet.dk
2009-03-30 23:42:39 Local3.Debug 192.168.0.1 RSE_DEBUG: unref domain, gw1.fonet.dk
2009-03-30 23:42:39 Local3.Debug 192.168.0.1 RSE_DEBUG: last unref for domain gw1.fonet.dk
2009-03-30 23:42:49 Local3.Debug 192.168.0.1 RSE_DEBUG: reference domain:gw1.fonet.dk
2009-03-30 23:42:49 Local3.Debug 192.168.0.1 RSE_DEBUG: reference domain:gw1.fonet.dk


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Patrick Born Tue, 03/31/2009 - 07:38

Hi Peter,

While I'm researching reboot reason H0, can you please:

  1. confirm if your SPA2102 ever registers successfully
  2. verify if gw1.fonet.dk is the correct proxy for you to use
  3. verify that your configured DNS servers are resolving names properly
  4. use different DNS servers
  5. replace gw1.fonet.dk with 129.142.224.250 [what gw1.fonet.dk resolves to for me] and see if the SPA2102 registers and does not reboot

Regards,

Patrick

----------

Peter_Karlsen Tue, 03/31/2009 - 11:42

Hi Patrick,

Thank you for your input to finding the error.

This is what I found out.

1. In the status page of the router the lines are listed as registered.

2. I have looked at my VoIP suppliers webpage. gw1.fonet.dk should be the right proxy.

3. The DNS information comes from my ISP and works perfectly with my pc's connected to my network. I assume it works for the router as well.

4. I tried entering another DNS server. That didn't work.

5. When replacing gw1.fonet.dk with  129.142.224.250 all the reference domain, unref and last unref messages in the syslog dissapers. :-) And the lines list as registered.

Unfortunately the router still resets with the reason H0 approximately every 10 minutes.

Best regards

Peter Karlsen

Patrick Born Tue, 03/31/2009 - 12:34

Hi Peter,

I'm glad that you were able to get rid of the unref domain DNS error messages and that your lines are registered.

There appears to be a parameter that has been configured to do something every 10 minutes that is causing the device to reboot as a last resort.

Please do either A or B in order to discover the cause of the rebooting:

A.

  1. Enable syslog and debugging: https://www.myciscocommunity.com/docs/DOC-5405
  2. Save your devices configuration: https://www.myciscocommunity.com/docs/DOC-5101
  3. Send me the syslog output and the configuration files for analysis [paborn at Cisco.com]

Or:

B.

  1. Perform a factory reset of the device
  2. Change only the device's Proxy and Registration and Subscriber information
  3. Test

Regards,

Patrick

-----------

Patrick Born Wed, 04/01/2009 - 14:01

Hi Peter,

I received your syslog and configuration information.

Please update your SPA2102 from 3.3.6 to the current version 5.2.5, available from Cisco.com and repeat the steps from my previous post [factory reset etc]

Regards,

Patrick

-----------

Peter_Karlsen Tue, 04/21/2009 - 23:39

UPDATE:

After a lot of troubleshooting and mail correspondence with Patrick Born we resolved the problem.

The SPA2102 is primarily a phone adaptor with minimal router capability.

When the router is presented with heavy network load (e.g. when running a p2p client) the router tends to reset after some time.

The solution is to configure the SPA2102 to run in bridge mode and let a dedicated router handle the routing.

After I changed to bridge mode the SPA2102 haven't reset at all.

/Peter

Patrick Born Wed, 04/22/2009 - 06:24

Hi Peter,

Thanks for the update. I'm glad to read that the issue is resolved.

Regards,

Patrick

----------

Actions

This Discussion

Related Content