Re: (ASCEND) Handy Hints For Upgrading Maxen

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

> Serial Downloads Won't
> Load, that is.  While one can get the restricted load (r*) into the Max
> and make it "like it" after only a few attempts, the extended load (f*)
> downloads without error, but fails with "CRC errors" when the Max attempts
> to "expand" it.  
> 
> Despite the fact that Ascend's web-based "Upgrade Instructions" document
> using a serial link as an upgrade tool, it simply "does not work" in the
> words of Ascend tech support.

I would recommend that all users follow the explicit instructions that are
now included in the release notes.

For example, the instuctions for the 7.0.0 release may be found on page 103
in the section titled "Upgrading system software".

The release notes say explicitly [page 104]:

  Extended load    6.0.0 or later MAX release denoted by an "f" preceding
                   the build name. You must use TFTP to upgrade to extended
                   loads.

You can find the release notes in the doc/ sub-directory that can be found
in the same directory you pick up the software.  For example, the release
notes for 6.1.7 are available from:
 ftp://ftp.ascend.com/pub/Software-Releases/Max/Release-6.1.X/6.1.7/doc/r617.pdf
See "Upgrading system software" on page 5.

Note to Ascend -
The standalone MAX Upgrade instructions are out of date, and do not even
mention the Restricted and Extended loads.
  ftp://ftp.ascend.com/pub/Software-Releases/Max/Upgrade-Instructions.txt
These instructions should be either kept up to date (or removed).

But even these instructions make it clear that some types of MAX software
loads require the use of TFTP.

  SECTION 1.14 - LOADING "FAT" BINARIES.
  ...
  FAT Binaries may only be loaded via TFTP, and cannot be loaded through
  the serial console port.

> The upgrade, once complete, erased all the options that had been provisioned
> on the Max, even "Data Call".

According to the people I have talked to at Ascend, the upgrade does not
erase the options.  The hash codes are stored in a different piece of
hardware (along with the serial number).  The problem is that the options
were never enabled in the hash code in older units.  The software did not
check the hash code and just provided the feature.  The newer software is
now checking the hash codes - which works fine in newer units which have
the correct hash code shipped from the factory - but breaks the operation
of older units, and require the new hash code.

Calling in advance to get the current hash codes is a good idea if you
know to expect it.  This has been greatly discussed on the Ascend Users
mailing list.

Note to Ascend -
The Release Notes do _not_ warn of this possible problem.  This does
cause problems for people and should be pointed out in advance in the
Release Notes for each release.  Many people are still running older
releases of software and this can be a source of frustration.

> After loading the hash codes sent by Ascend, the unit lost its configuration,
> and had to be reloaded from a saved copy.  Once again, this could be
> a serious problem in a case where the Max is a remote one, and connects
> back to the core location over a T-1 plugged into the Max itself.

The "update" command should not cause the unit to reset, so loading the
hash codes should not casue the unit to lose its configuration.  However,
with most software updates you need to follow the instructions carefully
because you typically need to do an "fsave" and "nvramclear" to get the
system to rebuild its configuration [read the release notes for details].
Otherwise you run the risk of corrupting the information in NVRAM and
losing your configuration.

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