Re: (ASCEND) P 75 Reboot?

[Tim Basher <basher@ces.cwru.edu>]

> There was no power loss today, yet at 0645 this am, the router appeared
> to reboot.
...
> Upon looking at the unit's logs, it wiped all the stored data out -
> indicating to me that it either nvram cleared/reset/or power cycled.

Which stored data are you talking about?  The configuration (how did it
redial the ISP without the information)?

> Any thoughts on this?

First, try to verify that it really did reset.  This can be done in
a number of ways.  The first is to check the uptime reported in the
"00-100 Sys Option" window.
  example:
    Up: 10:01:33:04
The second is to enter the terminal server [System>Sys Diag>Term Serv or
"ctrl-d e"] and use the "show uptime" command.
  example:

     ** Ascend Pipeline Terminal Server **

     ascend% show uptime
     system uptime: up 10 days, 1 hours, 34 minutes, 4 seconds
     ascend%

If the system did reset, then the next thing to do is to check the system's
fatal error log.

Because there is no real-time clock in the P75, the log will not have any
timestamps.  Check for any "FATAL ERROR" messages.

  example log messages:
    OPERATOR RESET:  Index: 99  Load: b.p50 Revision: 5.1Ap1
          DEBUG Reset from unknown in security profile 1.

    SYSTEM IS UP:  Index: 100  Load: b.p50 Revision: 5.1Ap1

    FATAL ERROR:  Index: 40  Load: b.p50 Revision: 5.1Ap1
          Location: 0000000f 8020c9d8 8020a798 802073ac 80208718 800c0424

To get the log, you need to connect to the serial port of or telnet to your
Pipeline and enter Diagnostic mode.

You can enter Diagnostic mode in two different ways.

The first is to use a "DO" command.  You can select a "DO" command by
entering a ctrl-d (pressing the "control" key and "d" keys at the same
time) a console window.  You will want to select the "D=Diagnostics"
DO command.

The second is to enter the command "Esc [ Esc =" (where Esc represents
the Escape key) in less than three seconds.

Once you are in Diagnostic mode you will see a ">" prompt.

Enter the command "fatal-history" (which may be abbreviated to "fat")
and capture the output.

You can (optionally) clear the fatal-history using the "clr-history"
command after you view it.

You can exit from Diagnostic mode using the "quit" command.

Send the output to Ascend Customer Service via electronic mail to
support@ascend.com

Make sure you include your model numbers, part numbers and revisions,
software versions and a description of the problem sufficient to
reproduce it (if it seems related to a specific action).

You will then receive an email response indicating the ticket response
number assigned to your issue.  When you get back your ticket number,
which means that the information is now on hand with customer service
so call them at (800) 272-3634 between 6:00am and 6:00pm PST.  Make sure
you have your ticket number when you call.

Find out if the problem is a known problem.  If so, make sure you get
the "TR" number.  This is the number you will need to check the release
notes for, to find out if your problem has been fixed.

If the problem is not a known problem, ask them to contact you as soon
as they have a "TR" number.  If you don't hear back within 2 working days,
make sure you call again to follow up and get the "TR" number.

Always save your original ticket number.  If you want to avoid having to
give a lot of contact information each time you call, make sure you also
get your "Caller ID".  After that they will usually just ask you a few
questions to make sure your contact information is up to date (and that
you have the right number).

++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>