Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
4261
Views
0
Helpful
2
Replies

Problem with PAP2T-NA (won't boot)

qwer130461
Level 1
Level 1

‎08-14-2009 06:38 AM - edited ‎03-21-2019 09:18 AM

Hi,

I was a happy user of a PAP2T-NA with the latest FW version. Everything has been working perfectly until today when tried to change some configuration. I did quite a number of changes all of which worked fine.

At some point after hitting Save the unit died with the following odd behavior:

1.Power LED is ON with RED

2.Ethernet LED is ON with GREEN

3.IVR is dead on both lines

Now I disconnect the Ethernet connection. After several minutes (5?) the unit comes up with:

1.Power LED blinking 1-long 2-short, which according to a Cisco doc means LAN disconnected

2.IVR works

I tried different things with IVR, including reset to factory default, setting up IP, netmask, default gateway. The unit accepts the configuration parameters, then all LEDs go GREEN, then the unit reboots and we're back at the beginning (RED Power, Green LAN).

I set up a syslog server which shows:

08-14-2009    16:20:05    Local7.Debug    192.168.1.111    -- FLASH-R[0001317e:32] ffff0000ffffffff
08-14-2009    16:20:05    Local7.Debug    192.168.1.111    -- FLASH-R[0001317e:32] ffff0000ffffffff
08-14-2009    16:20:05    Local7.Debug    192.168.1.111    -- FLASH-R[0001317e:32] ffff0000ffffffff
08-14-2009    16:20:05    Local7.Debug    192.168.1.111    -- FLASH-R[0001317e:32] ffff0000ffffffff
08-14-2009    16:20:05    Local7.Debug    192.168.1.111    -- FLASH-R[0001317e:0] ffff0000ffffffff
08-14-2009    16:20:05    Local7.Debug    192.168.1.111    -- FLASH-R[0001317e:0] ffff0000ffffffff
08-14-2009    16:20:05    Local7.Debug    192.168.1.111    -- FLASH-R[0001317e:0] ffff0000ffffffff
08-14-2009    16:20:05    Local7.Debug    192.168.1.111    -- FLASH-R[0001317e:0] ffff0000ffffffff
08-14-2009    16:20:02    Local7.Debug    192.168.1.111    [1]Reg Addr Change(0) 0:0->ae81ec07:5060
08-14-2009    16:20:02    Local7.Debug    192.168.1.111    [1]Reg Addr Change(0) 0:0->ae81ec07:5060
08-14-2009    16:20:02    Local7.Debug    192.168.1.111    [0]Reg Addr Change(0) 0:0->c0a80101:5070
08-14-2009    16:20:02    Local7.Debug    192.168.1.111    [0]Reg Addr Change(0) 0:0->c0a80101:5070
08-14-2009    16:20:02    Local7.Debug    192.168.1.111    DHCP lease time: 86400 seconds
08-14-2009    16:20:02    Local7.Debug    192.168.1.111    System started: ip@192.168.1.111, reboot reason:H633a03b0
08-14-2009    16:20:02    Local7.Debug    192.168.1.111    System started: ip@192.168.1.111, reboot reason:H633a03b0

I tried to update the FW and also to do a recovery - both didn't work.

If I set up a DHCP server to provide an IP, the unit pulls successfully its IP, but fails to boot.

Any ideas?

Thx,

D

0 Helpful
2 Replies 2

qwer130461
Level 1
Level 1

‎08-15-2009 02:41 AM

Additional info:

Turns out there's an initial window when the unit is fully functional:

1.It manages to register with service providers

2.I manage to access it through the Web interface and see the data.

After that short window the unit crashes.

I tried to disconnect it from the 'Net, but that didn't extend the window.

I managed to set the debug level to 99, and when doing a Save on configuration the unit spat out:

08-15-2009     12:15:46     Local3.Debug     192.168.1.111     Aug 15 12:17:05 000F18603559 fu:1:321d, 03e4 05a8 0001
08-15-2009 12:15:46 Local1.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, giving up (0x001eaa01: curr = 0x00, targ = 0x5d)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001eaa01: curr = 0x00, targ = 0x5d)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001eaa01: curr = 0x00, targ = 0x5d)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001eaa01: curr = 0x00, targ = 0x5d)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001eaa01: curr = 0x00, targ = 0x5d)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001eaa01: curr = 0x00, targ = 0x5d)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001eaa01: curr = 0x00, targ = 0x5d)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001eaa01: curr = 0x00, targ = 0x5d)
08-15-2009 12:15:46 Local1.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, giving up (0x001eaa00: curr = 0x00, targ = 0x17)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001eaa00: curr = 0x00, targ = 0x17)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001eaa00: curr = 0x00, targ = 0x17)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001eaa00: curr = 0x00, targ = 0x17)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001eaa00: curr = 0x00, targ = 0x17)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001eaa00: curr = 0x00, targ = 0x17)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001eaa00: curr = 0x00, targ = 0x17)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001eaa00: curr = 0x00, targ = 0x17)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001eaa00: curr = 0x00, targ = 0x17)
08-15-2009 12:15:46 Local1.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, giving up (0x001ea9e1: curr = 0x00, targ = 0x3f)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001ea9e1: curr = 0x00, targ = 0x3f)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001ea9e1: curr = 0x00, targ = 0x3f)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001ea9e1: curr = 0x00, targ = 0x3f)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001ea9e1: curr = 0x00, targ = 0x3f)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001ea9e1: curr = 0x00, targ = 0x3f)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001ea9e1: curr = 0x00, targ = 0x3f)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001ea9e1: curr = 0x00, targ = 0x3f)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001ea9e1: curr = 0x00, targ = 0x3f)
08-15-2009 12:15:46 Local1.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, giving up (0x001ea9e0: curr = 0x00, targ = 0x31)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001ea9e0: curr = 0x00, targ = 0x31)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001ea9e0: curr = 0x00, targ = 0x31)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001ea9e0: curr = 0x00, targ = 0x31)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001ea9e0: curr = 0x00, targ = 0x31)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001ea9e0: curr = 0x00, targ = 0x31)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001ea9e0: curr = 0x00, targ = 0x31)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001ea9e0: curr = 0x00, targ = 0x31)
08-15-2009 12:15:46 Local1.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, giving up (0x001e3201: curr = 0x00, targ = 0x5d)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001e3201: curr = 0x00, targ = 0x5d)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001e3201: curr = 0x00, targ = 0x5d)
08-15-2009 12:15:46 Local2.Debug 192.168.1.111 Aug 15 12:17:05 000F18603559 flash: byte write hardware failure, retrying (0x001e3201: curr = 0x00, targ = 0x5d)

This seems to point to a faulty flash and explains why Factory Reset didn't help.

Any ideas?

Thx,

D

0 Helpful

wichilds
Level 4
Level 4
In response to qwer130461

‎08-20-2009 02:57 AM

D,

I hate to say it but it looks as though you need a new device. If it is a flash error, then the only way to fix it is buy a new one or get this one replaced via rma. You can explore the rma option with the small business support center at 1-866-606-1866. If this unit was provided to you via an ITSP, then you would need to go to them for replacement options.

Good luck,

Bill

0 Helpful
Customers Also Viewed These Support Documents