Additional info that may or may not prove relevant: * Before changing the Auto-Rescan Duration, it had been running firmware 826. I fed it an upgrade to 832, which it took. It was after this that I experienced the first web server / management crash upon attempting to make a settings-change. We have other radios deployed with 832 and they have not behaved this way.
* I am told that when our on-site technician powercycled the radio after the web interface crashed out on him, it would not even establish an ethernet link for a good 20 minutes or so to his laptop. (I am not sure if he tried powercycling it multiple times.) Finally it linked up, but he was unable to get an IP address from it. * I should have mentioned that not only does it not respond to 192.168.254.251, but if I try to have a DHCP client get an IP from it, there is no response. It does seem like the unit is not completely initializing / booting up. Almost feels like there is some weird configuration corruption that is causing the bootup/initialization procedure to either get stuck or to bail out early. I did remove the panel antenna and take a look inside, and everything appears to be fine physically (as far as I can tell from a glance). Is there any way to force a config wipe during bootup? I don't see a depressable button on the PCB anywhere... -- Nathan -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Nathan Anderson Sent: Monday, December 19, 2016 4:46 PM To: [email protected] Subject: [Telrad] One-off CPE8K failure Does anybody know what it means when an 8K behaves this way?: 1) Powers on 2) All RF/signal LEDs are lit 3) Run LED is blinking 4) There is an ethernet link 5) Nothing else works (doesn't respond to 192.168.254.251 on LAN side, won't attach to network, etc.) Before these symptoms occurred, we did notice some already odd behavior by this particular unit. I had attempted to change the "Auto-Rescan Duration" value on the eNB Settings tab from 0 to 15. After clicking "Save & Apply", the CPE's web server crashed. So I SSH'd into the thing and issued a manual reboot. After it came back up on the network, I discovered it had forgotten all of its settings and reset to defaults. Logging in and attempting to reconfigure it (via uploading a standard configuration template file that we use for all CPE8Ks at Maintenance > Config Management > Restore Configuration) caused the web server to again crash out, but because I had not re-enabled SSH manually before doing so, I was unable to get into it remotely to reboot it a second time. (It was still attached to the network and passing data just fine, however, so the customer was not off-line). It sat that way until we sent a tech out to reboot it and check things out. He went in to enable SSH access, hit Save & Apply, and the web server *again* became unresponsive. But this time, after powercycling it, it came up into the vegetative state that it still remains in (described at the beginning). Anybody else seen anything like this? -- Nathan _______________________________________________ Telrad mailing list [email protected] http://lists.wispa.org/mailman/listinfo/telrad _______________________________________________ Telrad mailing list [email protected] http://lists.wispa.org/mailman/listinfo/telrad
