False alarm. It turns out that we have a new breaker in the house which is tripping when power tools are plugged in.
Unfortunately, that breaker serves a part of the basement that I don't (yet) have a UPS for, and that's where the ATT device lives. This modem has a backup battery in it, so after power loss it cycles very quickly and it doesn't report that it went down - the battery onboard doesn't keep the stupid thing lit as far as ethernet or DSL functionality, but does keep the modem itself from fully crashing.
Thus, the bogus uptime report I'm seeing.
-------------------------------------------------------------------------------
I have FTTN X2 in Oakland, serviced by an NVG599 modem.
For three days running I've had the internet drop offline in the morning, Monday around 10:30 and yesterday and today around 8:30 am. Monday I shrugged, pulled the plug on the ATT hardware, and everything came back up fine.
Yesterday, the issue raised its head first with the IP phone going offline; I rebooted the phone's modem, it took a long time to reregister, and while it did that I noticed that there had been a hiccup in internet service.
This morning the phone was OK but the internet went down. It looks as if there's a soft reset happening and also a mention of a filter being applied, then reverted.
Here are the logs from the ATT device from this morning's blink. We did not lose power in the house here.
Ethernet ports 1 and 4 being down is normal. Port 2 feeds my router and port 3 feeds the telephone. System uptime is reported as several days, so the device isn't being completely restarted by this event.
Does anyone have any insight into this?
2017-08-09T08:24:19-07:00 L3 sdb[330]: ELAN: Port lan-2 (eth1) is DOWN
2017-08-09T08:24:19-07:00 L5 sdb[330]: Apply Filter
2017-08-09T08:24:19-07:00 L3 sdb[330]: ELAN: Port wl_hd (eth4) is DOWN
2017-08-09T08:24:19-07:00 L3 wlcfg_rpcd[2912]: Received SIGTERM, calling shutdown
2017-08-09T08:24:21-07:00 L3 sdb[330]: HPNA: powering off hpna
2017-08-09T08:24:21-07:00 L3 sdb[330]: ENSW:(enport_status_update) enswitch in power down mode
2017-08-09T08:24:21-07:00 L5 sdb[330]: HPNA: Link down
2017-08-09T08:24:21-07:00 L3 sdb[330]: Wi-Fi: Number of clients associated on 2.4GHz radio 0
2017-08-09T08:24:21-07:00 L4 mcp[2529]: mcp: processing STOP signal
2017-08-09T08:24:21-07:00 L3 sdb[330]: ELAN: Port hpna (eth5) is DOWN
2017-08-09T08:24:23-07:00 L3 sdb[330]: ENSW:(enport_status_update) enswitch in power down mode
2017-08-09T08:24:24-07:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-08-09T08:25:10-07:00 L5 mcp[3929]: mcp: mcfwd_upstream_if already set to: 18
2017-08-09T08:25:15-07:00 L3 sdb[330]: ELAN: Port hpna is UP. (eth5) speed 200 duplex full
2017-08-09T08:25:19-07:00 L4 sdb[330]: PWRMGMT: Restoring database settings
2017-08-09T08:25:21-07:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 1000 duplex full
2017-08-09T08:25:21-07:00 L3 sdb[330]: ELAN: Port wl_hd is UP. (eth4) speed 1000 duplex full
2017-08-09T08:25:21-07:00 L3 sdb[330]: ELAN: Port lan-2 is UP. (eth1) speed 100 duplex full
2017-08-09T08:25:21-07:00 L3 wlcfg_rpcd[523]: MAC of the 802.11ac interface is 10:05:b1:df:e8:53
2017-08-09T08:25:22-07:00 L5 sdb[330]: HPNA: Link down
2017-08-09T08:25:22-07:00 L3 sdb[330]: ELAN: Port hpna (eth5) is DOWN
2017-08-09T08:25:25-07:00 L3 battctl[1718]: BATTERY: charger is on
2017-08-09T08:25:26-07:00 L3 sdb[330]: ELAN: Port hpna is UP. (eth5) speed 10 duplex full
2017-08-09T08:25:37-07:00 L5 sdb[330]: Revert Filter
Part of why this is noticeable is that the gear behind the ATT router is not handling having the ATT device's changes gracefully. Yesterday's loss of the phone was noticeable, though - I might have had another phone loss today, but needed to get the dogs out just as the blink happened.
I did call Sonic yesterday to find out if there had been a systemwide issue noted, and there had not. The person I spoke with agreed that posting the info here might be a good way to get more eyes on this.
Unfortunately, that breaker serves a part of the basement that I don't (yet) have a UPS for, and that's where the ATT device lives. This modem has a backup battery in it, so after power loss it cycles very quickly and it doesn't report that it went down - the battery onboard doesn't keep the stupid thing lit as far as ethernet or DSL functionality, but does keep the modem itself from fully crashing.
Thus, the bogus uptime report I'm seeing.
-------------------------------------------------------------------------------
I have FTTN X2 in Oakland, serviced by an NVG599 modem.
For three days running I've had the internet drop offline in the morning, Monday around 10:30 and yesterday and today around 8:30 am. Monday I shrugged, pulled the plug on the ATT hardware, and everything came back up fine.
Yesterday, the issue raised its head first with the IP phone going offline; I rebooted the phone's modem, it took a long time to reregister, and while it did that I noticed that there had been a hiccup in internet service.
This morning the phone was OK but the internet went down. It looks as if there's a soft reset happening and also a mention of a filter being applied, then reverted.
Here are the logs from the ATT device from this morning's blink. We did not lose power in the house here.
Ethernet ports 1 and 4 being down is normal. Port 2 feeds my router and port 3 feeds the telephone. System uptime is reported as several days, so the device isn't being completely restarted by this event.
Does anyone have any insight into this?
2017-08-09T08:24:19-07:00 L3 sdb[330]: ELAN: Port lan-2 (eth1) is DOWN
2017-08-09T08:24:19-07:00 L5 sdb[330]: Apply Filter
2017-08-09T08:24:19-07:00 L3 sdb[330]: ELAN: Port wl_hd (eth4) is DOWN
2017-08-09T08:24:19-07:00 L3 wlcfg_rpcd[2912]: Received SIGTERM, calling shutdown
2017-08-09T08:24:21-07:00 L3 sdb[330]: HPNA: powering off hpna
2017-08-09T08:24:21-07:00 L3 sdb[330]: ENSW:(enport_status_update) enswitch in power down mode
2017-08-09T08:24:21-07:00 L5 sdb[330]: HPNA: Link down
2017-08-09T08:24:21-07:00 L3 sdb[330]: Wi-Fi: Number of clients associated on 2.4GHz radio 0
2017-08-09T08:24:21-07:00 L4 mcp[2529]: mcp: processing STOP signal
2017-08-09T08:24:21-07:00 L3 sdb[330]: ELAN: Port hpna (eth5) is DOWN
2017-08-09T08:24:23-07:00 L3 sdb[330]: ENSW:(enport_status_update) enswitch in power down mode
2017-08-09T08:24:24-07:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-08-09T08:25:10-07:00 L5 mcp[3929]: mcp: mcfwd_upstream_if already set to: 18
2017-08-09T08:25:15-07:00 L3 sdb[330]: ELAN: Port hpna is UP. (eth5) speed 200 duplex full
2017-08-09T08:25:19-07:00 L4 sdb[330]: PWRMGMT: Restoring database settings
2017-08-09T08:25:21-07:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 1000 duplex full
2017-08-09T08:25:21-07:00 L3 sdb[330]: ELAN: Port wl_hd is UP. (eth4) speed 1000 duplex full
2017-08-09T08:25:21-07:00 L3 sdb[330]: ELAN: Port lan-2 is UP. (eth1) speed 100 duplex full
2017-08-09T08:25:21-07:00 L3 wlcfg_rpcd[523]: MAC of the 802.11ac interface is 10:05:b1:df:e8:53
2017-08-09T08:25:22-07:00 L5 sdb[330]: HPNA: Link down
2017-08-09T08:25:22-07:00 L3 sdb[330]: ELAN: Port hpna (eth5) is DOWN
2017-08-09T08:25:25-07:00 L3 battctl[1718]: BATTERY: charger is on
2017-08-09T08:25:26-07:00 L3 sdb[330]: ELAN: Port hpna is UP. (eth5) speed 10 duplex full
2017-08-09T08:25:37-07:00 L5 sdb[330]: Revert Filter
Part of why this is noticeable is that the gear behind the ATT router is not handling having the ATT device's changes gracefully. Yesterday's loss of the phone was noticeable, though - I might have had another phone loss today, but needed to get the dogs out just as the blink happened.
I did call Sonic yesterday to find out if there had been a systemwide issue noted, and there had not. The person I spoke with agreed that posting the info here might be a good way to get more eyes on this.
