I presume you've tried Emergency Treatment #1: Reboot?
It probably won't help, but it shouldn't hurt.
>dialup-networking for most of our users) that the port master reboots
>right away
>with that PANIC System Exception IP:33333333 followed by 6 registries
>numbers.
Can you do a 'set debug 0x51' and see what is happening when they connect
with PPP?
>What could be causing this?? All we did is shut it down, and move a few
Truthfully I haven't seen this one. It could be something in the ComOS
got corrupted. How - no idea. Power surge on start up. Cosmic rays. *shrug*
Or it could be something weird in the config.
It is nigh-impossible to say.
>find anything for "PANIC" error messages that would help explain. Is
They are very low level engineering reports. I don't even have the magic
decoder. Basically, PANIC is a bad thing to see.
I'd try rebooting. Go over the config with a fine tooth comb. And if
that fails, try upgrading the ComOS - even if it means reloading the same
revision (I'd use 3.3.3 though). And if that fails, wipe FLASH with
'set register 0xffff 0x0f63' and reload ComOS and reconfigure.
It *that* fails you'll probably end up with an RMA, so you'll need to
talk to support.
Please don't rely on me for this. My great-grandmother died this morning
and I'm leaving tomorrow for the funeral and probably won't be back until
Wednesday.
-MZ
-- Livingston Enterprises - Chair, Department of Interstitial Affairs Phone: 800-458-9966 510-426-0770 FAX: 510-426-8951 megazone@livingston.com For support requests: support@livingston.com <http://www.livingston.com/> Snail mail: 6920 Koll Center Parkway #220, Pleasanton, CA 94566