Reboot your workstation, and add the Microsoft
TCP/IP driver in your network control panel.
SECTION 1.6 LAUNCHING THE TFTP SERVER
For Windows 3.1 and Windows NT 3.51 open the "MaxLink Pro" Program
manager group, and double click on the TFTP application.
For Windows 95/NT, click on the Start menu, Programs, MaxLink Pro for
95/NT, and finally on TFTP.
SECTION 1.7 CREATING A HOME DIRECTORY FOR THE TFTP SERVER
In the root directory of the "c" drive create a directory/folder named
"TFTP". Any configuration files that you tsave from your router will
be stored in the tftp directory. Any binary upgrade files that you
wish to load into your router will need to be placed into this directory
to be recognized by the TFTP server.
SECTION 1.8 ENABLING THE TFTP SERVER
In the TFTP window open the "settings" menu and then select "server".
Select the check box "Server on", this will enable the TFTP server.
To select the public directory or "default directory" for the TFTP
server enter "c:\tftp" in the top or first field of the Server Settings
window. Close the server settings window. You will see two things
in the TFTP window. 1) In the lower right hand corner you will see
it say "server: on" and 2) you will see a line of text that says
"current date-time-server c:\tftp"
Your TFTP server is now ready to transfer the file to the pipeline/max
SECTION 1.9 - SAVING CONFIG BEFORE PROCEEDING WITH UPGRADE!
It is recommended that you perform a "tsave" command to save your
configuration on the TFTP server before loading the code. Although it
is unlikely that your configuration will be lost, this will allow you to
recover easily if the configuration is lost or damaged. Keep in mind
that this saved configuration file has all passwords, and should be
moved from the TFTP directory into a secure location after the upgrade
procedure is complete.
SECTION 1.10 - OBTAINING FULL ACCESS SECURITY.
In order to get into debug mode, you must be logged into a security
profile that has "Field Service" set to yes. If you have enabled
security on your Pipeline/Max, then you will need to log into the
"Full Access" security profile. To get into "Full Access", hit
Control-D, and then "P" for password Scroll down to "Full Access",
and hit enter, enter your password when prompted.
SECTION 1.11 - GETTING INTO DEBUG MODE
TFTP is executed as a command in the "debug" mode. To enter debug, hit
Control-D, and then "D" for Diagnostic mode. If you are on software
previous to 5.0A, you must enter debug with the "ESC [ ESC =" key
sequence. This key sequence must be entered in less than one second.
SECTION 1.12 - SAVING CONFIGURATION TO A TFTP SERVER
The first step is to save your configuration to the TFTP server. If
your TFTP server is UNIX based, you may need to go into TFTP server's
home directory and perform a "touch" command to create the file, for
example "touch router1.cfg".
To save your configuration, type tsave [host] [filename].
For Example: tsave 192.168.100.1 router1.cfg
Next, you will need to perform the actual TFTP code load.
SECTION 1.13 - UPGRADING FROM 4.6C OR PREVIOUS TO 5.0A AND ABOVE
If you are upgrading from software 4.6C or previous to version 5.0A or
later, it is recommended that you perform the TFTP upgrade in three
steps as follows:
- Step #1 - TFTP Load version 4.6Ci18 and NVRAMCLEAR.
- Step #2 - TFTP Load version 5.0A and then NVRAMCLEAR.
- Step #3 - TFTP Load version 5.0AXX and then NVRAMCLEAR.
This is due to the changes in flash memory management that have taken
place in 5.0A. Failure to adhere to this procedure may cause your
Pipeline/Max lose or corrupt its configuration, and possibly render
the unit unusable.
SECTION 1.14 - LOADING "FAT" BINARIES.
It is recommended that you be on version 5.0A in order to load any "FAT"
binary in the 5.0AXX tree. A FAT binary is any code image that is
larger than 450K for the pipeline series, or 960K for the Max series.
FAT Binaries may only be loaded via TFTP, and cannot be loaded through
the serial console port.
If you are local to the router (i.e. connected via the serial console
cable, you can upgrade directly to any version (except a "FAT" binary)
of software as long as you perform and FCLEAR, AND NVRAMCLEAR after TFTP
Loading the new code. This will wipe out the configuration completely,
and allow only console access to the router. You can reenter the IP
address (and default gateway if necessary), and then TRESTORE your
configuration from a TFTP server, or manually reconfigure the router.
SECTION 1.15 - TLOADCODE PROCEDURE.
To load the binary code image, type TLOADCODE [host] [filename].
For Example: tload 192.168.100.1 b.p75
The last step is to perform an NVRAMCLEAR. This will initialize the
Non-Volatile RAM where the active configuration data is stored. Don't
worry, this WILL NOT cause you to lose your configuration. In fact, if
you don't perform the NVRAMCLEAR, it is possible that your configuration
will become corrupted, or lost completely. Since the TLOADCODE command
automatically performs an FSAVE, your configuration is stored in flash,
and automatically restored after performing the NVRAMCLEAR.
NOTE: The Pipeline/Max will reboot TWICE after performing a software
upgrade, it will take a Pipeline approximately one to two minutes, and
a Max two to five minutes to boot up after performing the upgrade and
NVRAMCLEAR.
The TLOAD command will automatically perform an FSAVE and save your
active configuration to flash, then load the code image across the
network. During the transfer of the file, a series of dots is printed
to indicate progress. Each dot represents 512 bytes of data.
Upon rebooting, the router will perform a CRC check on the new operating
system, and if it passes, it will be copied into the primary flash
partition, and the router will reboot using the new code. If the code
does not pass the CRC checksum, then the code will be discarded and the
router will reboot with the original software, and configuration.
The TLOADCODE command does NOT automatically reboot the box after the
code load is complete. This must be done manually by typing
"NVRAMCLEAR" at the debug prompt. You MUST perform an NVRAMCLEAR after
the TLOADCODE, or you will risk corrupting the non-volatile RAM
configuration data. The NVRAMCLEAR procedure will ensure that your
configuration is properly restored after loading the new operating
system.
SECTION 1.16 - TFTP DEBUG COMMAND REFRENCE.
TSAVE - saves your configuration to a TFTP server
Usage: TSAVE [host] [filename]
For Example: tsave 192.168.100.1 router1.cfg
TRESTORE - restores configuration from a TFTP server
Usage: TRESTORE [host] [file]
For Example: trestore 192.168.100.1 router1.cfg
FSAVE - saves your configuration to FLASH memory in router
Usage: FSAVE
This command saves the configuration profile to flash in the same text
format used in the "System->Sys Diag->Save Cfg" menu command and the
"tsave" TFTP command. Once saved to flash, this configuration may be
restored at any time using the "FRESTORE" command.
FRESTORE - restores configuration from Flash memory in router
Usage: FRESTORE
This command restores the configuration previously stored via the
"fsave" command.
NOTE: It is necessary to reset the box after an FRESTORE, because some
profiles which are copied from Flash to NVRAM will otherwise not be
properly initialized.
TLOADCODE - loads binary code image from TFTP server.
Usage: TLOADCODE [host] [filename]
For Example: tsave 192.168.100.1 b.p75
This command loads the binary software image into flash using the TFTP
protocol. If the DNS server is configured in the Ethernet, Mod Config,
DNS menu, then a DNS name may be used instead of the numerical IP
address.
SECTION 2.0 - UPGRADING SOFTWARE VIA SERIAL CONSOLE PORT
SECTION 2.1 - EXPLANATION OF THE SERIAL CONSOLE UPGRADE PROCEDURE.
Ascend uses the XModem file-transfer protocol to upgrade system software
in the field. You can reprogram the Pipeline's/Max's Flash-EEPROM by
uploading new system software using a PC/Macintosh and a communications
software package which supports the XModem-1K protocol.
SECTION 2.2 - HARDWARE & SOFTWARE REQUIRED TO UPGRADE VIA CONSOLE.
In order to field upgrade your Pipeline/Max, you must have the
following equipment and software:
- a. An IBM compatible PC or Macintosh.
- b. A serial port on the PC/Mac capable of connecting
to The Pipeline's/Max's Console port.
- c. A Straight through serial cable.
- d. Data communications software for your PC/Mac with
XModem CRC/1K support, such as Procomm Plus, HyperTerminal,
or ZTerm for the Macintosh.
SECTION 2.3 - CAUTION: USING WINDOWS BASED TERMINAL EMULATORS.
CAUTION: If you use a Windows based terminal emulator such as Windows
terminal, or HyperTerminal, make sure that you disable any screen
savers, or other processes that could interrupt the file transfer.
Failure to do so will cause the software upload to halt, and may render
the Pipeline/Max unusable!
SECTION 2.4 - WARNING: CONFIG WILL BE ERASED DURING UPGRADE.
WARNING: This upgrade deletes all call profiles, line profiles,
Ethernet configurations and the system profile from Pipeline's/Max's
memory. You should use the Pipeline's/Max's Save Config feature to save
and later restore the configurations.
SECTION 2.5 - SAVING CONFIG VIA THE CONSOLE
To save your configuration via the console, you will need a terminal
emulator capable of capturing screen output to an ASCII text file.
From the Main Edit Menu, go into System, Sys Diag, and Click on Save
Cfg. You should see the screen clear and a line stating "Ready to
download - type any key to start..." should appear.
At this point, you should start capturing text in your terminal
emulator. For example, in Hyperterminal, click on the Transfer menu,
and then on Capture Text. Enter the path and filename that you would
like to save your configuration to, and click the Start button. Hit
enter to start downloading your configuration file.
When finished, you will se a line stating "Download complete - type
any key to return to menu...". At this point, you will need to stop
capturing text in your terminal emulator. Do not hit any keys until
you have turned off the capture function, or you will have gibberish
at the end of your configuration file. In Hyperterminal, click on the
Transfer menu, and then on Capture Text, and finally on Stop. You may
want to open your configuration file in a text editor to make sure
that it was saved properly, and that there is nothing after the
"END DOWNLOAD" line.
SECTION 2.6 - SERIAL CONSOLE PORT UPGRADE PROCESS
To upload new software into your Pipeline/Max, follow these steps:
2.6.1 - Start up the PC communications software package. You should set
up the software to communicate with Pipeline/Max as you would for normal
use of Pipeline's/Max's serial console interface (9600 bps, N, 8, 1, NO
FLOW CONTROL).
2.6.2 - Make certain that the communications software is configured for
XModem-1K. This functionality is sometimes specified as XModem-1K,
XModem-CRC, or simply XModem.
2.6.3 - Verify that you can communicate with the Pipeline's/Max's
Monitor Screen. You should see the Control Monitor on the Screen.
If the screen is blank, try typing CTRL-L. If you still cannot see
the Control Monitor, try power cycling the Pipeline/Max.
2.6.4 - Once you are communicating with the Pipeline/Max, invoke the
firmware upload mode. With your fingers positioned over the ESC and
left bracket ([) keys, type in rapid succession ESC [ ESC -. That's
four keystrokes in less than one second. If you type the four
keystrokes too slowly, they will not be recognized by Pipeline/Max and
you will have to retype them. In summary, the four keystrokes are
escape, left bracket, escape, minus. If you are unable to get into
firmware upload mode, make sure that the security profile you are logged
into has "Field Service" set to yes.
2.6.5 - The Pipeline/Max will then begin transmitting a series of XModem
control characters, which appear on the screen as a simple string of
CKs. This protocol will time-out within approximately 1 minute, so
return to step 2.5.4 if necessary.
2.6.6 - Start the XModem upload process from your communications
program. Specify the file to upload based on your Pipeline/Max model.
(See a list of Filenames in Section 3.0 - File naming Conventions.)
2.6.7 - Your communications program should start the upload process.
It is normal behavior to see between one and twenty bad blocks recorded
at the beginning of the file transfer as the Pipeline/Max synchs up to
the terminal software.
2.6.8 - The upload process takes approximately 5 minutes for the Max,
and 3 minutes for pipelines at a data rate of 38400 bps. The upload
will take approximately 10 minutes for the Max, or 3 minutes for
pipelines at 9600 bps.
2.6.9 - After the upload process is complete, the Pipeline/Max will
reset and initiate its power-on self tests. At this point, Pipeline/Max
should be running the new software. Check in the 00-100 Sys Options
status window to verify the current version.
2.6.10 - If an XModem failure occurs during the upload process, the
Pipeline/Max will redisplay the CKs. You should retry the upload
process, beginning with step 2.5.4.
2.6.11 - If the upload fails during the transfer, try downloading a
fresh copy of the binary image from Ascend's ftp server and re-uploading
the code to the pipeline. If you still have problems, contact Ascend
technical support for assistance.
SECTION 2.7 - COMM PORT MAY REVERT TO 9600 BPS
NOTE: When you load a new software release, the Pipeline/Max returns to
its factory default state and the communications port may revert to the
factory default baud rate (9600 bps, N, 8, 1, No Flow Control).
SECTION 2.8 - NVRAMCLEAR BEFORE RESTORING CONFIGURATION!
CAUTION: Before reloading your configuration, you must perform an
NVRAMCLEAR!
If you are running Software 5.0A or higher, hit Control-D, and then "D"
for Diagnostics. If you are running Software previous to 5.0A,
with your hands positioned over the ESC and left bracket ([) keys,
type in rapid succession ESC [ ESC =. That's four keystrokes in
less than one second.
If you type the four keystrokes too slowly, they will not be recognized
by Pipeline/Max and you will have to retype them. In summary, the four
keystrokes are escape, left bracket, escape, equals. If you are unable
to get into debug mode, make sure that the security profile you are
logged into has "Field Service" set to yes.
Once in debug, enter the command "NVRAMCLEAR" (type help for
information). The system will reset and you should proceed with
restoring your configuration file.
SECTION 2.9 - RESTORING CONFIG VIA THE CONSOLE
Before you restore your configuration file back into your Pipeline/Max,
make sure that you perform an NVRAMCLEAR! To restore your configuration
go into System, Sys Diag, Restore Config. Hit enter on the Restore
Config menu, and you should see a prompt stating "Waiting for upload
data...". At this point, you are ready to send your configuration file
as ASCII text. In Hyperterminal, go to the Transfer menu, and click on
Send Text File (not the Send File command which is used to send BINARY
files). Locate your configuration file and click on the Open button.
After your configuration has finished restoring, hit Control-C, and then
enter to return to the console. It is highly recommended that you
reboot your router after restoring the configuration.
SECTION 2.10 - RESTORING CONFIGURATION WITH HYPERTERMINAL.
Since the Pipeline/Max does not have any flow control on the console
port, you must pace any text that you send to it. If you are running
Windows 95 or NT and Hyperterminal, using the following procedure will
ensure that your configuration is restored properly.
- From the File menu, Open Properties.
- In the Properties screen, click on the Settings Tab, and hit the
ASCII Setup button.
- Under Line Delay, enter 100 milliseconds.
SECTION 2.11 - CONFIGURATIONS NOT GUARANTEED TO RESTORE 100%.
WARNING: There is no guarantee that 100% of the configuration will be
restored in this manner. From release to release, as features change and
new features are added, so do the inherent data-structures. For this
reason it is recommended that you go through an integrity check of
samples of your profiles. If you have many profiles and passwords,
you may wish to consider using TFTP save to save your config
SECTION 2.12 - PASSWORDS ARE NOT SAVED DURING CONSOLE UPGRADE.
NOTE: Passwords are not saved for security reasons. AFTER UPGRADING,
YOU WILL HAVE TO REENTER YOUR SEND, RECEIVE, TELNET, AND SECURITY
PROFILE PASSWORDS. If you edit your saved configuration file, and enter
passwords in the appropriate fields (replacing the *SECURE*), these
passwords WILL be restored into the Pipeline/Max. If you do choose to
edit your configuration file, make sure to save it as TEXT ONLY, or you
will not be able to load it into your Pipeline/Max.
SECTION 3.0 - OBTAINING SOFTWARE UPGRADE FILES
SECTION 3.1 - FILE LOCATIONS ON THE FTP SITE
All software upgrades are available for download from Ascend's FTP site
at ftp.ascend.com.
For MAX Software go to:
ftp://ftp.ascend.com/pub/Software-Releases/Max/
For Pipeline Software go to:
ftp://ftp.ascend.com/pub/Software-Releases/Pipeline/
The most current Patch release is always available in the "Current"
directory. If you need an incremental release, or wish to revert back
to a previous version of software, simply go into the Incremental, or
Patch directory, and search for the desired version.
SECTION 3.2 - DETERMINING WHICH FILE TO LOAD
Incremental Releases - An Incremental Release encompasses all new
feature enhancements and bug fixes made since the last full release.
Since these releases have not been fully regression tested (only sanity
checked) they are not as stable as the patch releases. Incremental
Releases are usually released by Wednesday of each week for all product
lines.
Patch Releases - A Patch Release contains only bug fixes made since the
last full release which will not affect the stability of the release.
Patch Releases may not be released on a regular interval.
What does this mean?
If you have a customer needing a fix made in both the patch and the
incremental release, and stability is what you want, then use the Patch
Release. If there is a new feature the customer desires or if they have
a problem fixed in the Incremental Release that a Patch Release does not
address, then they should use the Incremental Release.
SECTION 3.3 - DOWNLOAD PROCEDURES
There are several areas within the Service & Support sections for
downloading files, primarily binary images for a specific model of an
Ascend product located on the Ascend FTP site. All of our files are
named following the DOS "8.3" convention (eight-character name.three
character extension). If you attempt to open the files by clicking on
them, your browser may not recognize these files as binary and may
display them on your screen as a display of unreadable characters and
symbols. Instead, download the file to a local disk or directory.
To do this from a PC or UNIX platform:
- Place the cursor over the highlighted name of the file you
wish to download.
- Press the right mouse.
- Choose the Save Link As option and indicate a location where
the image should reside.
On the MAC platform:
- Place the cursor over the highlighted name of the file you
wish to download.
- Press and hold the mouse key down for a moment.
- Choose the Save Link As... option and indicate a location
where the image should reside.
SECTION 4.0 - SOFTWARE FILE NAMING CONVENTIONS
DATE: 12-10-97
File name changes:
We have changed the naming convention as follows:
Platforms (extension)
===============
m60 Max 600x
m40 Max 400x
m16 Max 1600
m18 Max 1800
m20 Max 2000
m2 Max 200
p40 Pipeline 400
p13 Pipeline 130
p75 Pipeline 75
p50 Pipeline 50
p25 Pipeline 25
p15 Pipeline 15
mb MultiBand Plus
vsx MultiBand VSX
File Type
==========
r Restricted Load
f Full Extended Load
Restricted loads are loads that are truncated for compatibility with
older versions that only know hot to load "thin" loads. They contain
only enough functionality to run TLOADCODE over IP. These loads are
to be used as an intermideiate step when an upgrade to a full
extended load is required.
Full loads are complete extended loads that contain the full
functionality.
Network Interfaces
==============
t T1
e E1
b ISDN BRI
52 Switched 56 2 wire
54 Switched 56 4 wire
l DSL
Features
========
i IP only (OSPF - no IPX, ARA)
p IPX only
a Appletalk Routing
x X.25
o Modem outdial w/ no R2 (E1 m40 loads only)
h PHS
c Remote Access
v Voice over IP
1 Old hardware (e.g., b1.p50)
2 New hardware (e.g., b2.p75) use for p50/p75 with serial numbers
722XXXX and above, except models number P75-1UBRI-O, and P75-1SBRI-O.
n Nortel
m V34 Modem-12 modem support only
k K56Flex Modem Support only (8, 12, or 16 modems per card)
A list of the files released is included below along with the old filename:
Old Name New Name Old Name New Name
-------- -------- -------- --------
mp1e1.bin e.m16 mp1e1bri.bin eb.m16
mp1t1.bin t.m16 mp1t1bri.bin tb.m16
m2bri.bin b.m2
m18bri.bin b.m18 m18briip.bin bi.m18
m18bxip.bin bix.m18
m20e1.bin e.m20 m20t1.bin t.m20
mhpe1.bin e.m40 mhpe1bim.bin ebim.m40
mhpe1bimo.bin ebimo.m40 mhpe1bip.bin ebi.m40
mhpe1bipo.bin ebio.m40 mhpe1bm.bin ebm.m40
mhpe1bmo.bin ebmo.m40 mhpe1bri.bin eb.m40
mhpe1brio.bin ebo.m40 mhpe1brx.bin ebx.m40
mhpe1brxo.bin ebox.m40 mhpe1bxi.bin ebix.m40
mhpe1bximo.bin ebimox.m40 mhpe1bxipo.bin ebiox.m40
mhpe1bxm.bin ebmx.m40 mhpe1ip.bin ei.m40
mhpe1ipm.bin eim.m40 mhpe1ipmo.bin eimo.m40
mhpe1ipo.bin eio.m40 mhpe1m.bin em.m40
mhpe1mo.bin emo.m40 mhpe1o.bin eo.m40
mhpt1.bin t.m40 mhpt1bim.bin tbim.m40
mhpt1bip.bin tbi.m40 mhpt1bm.bin tbm.m40
mhpt1bri.bin tb.m40 mhpt1brx.bin tbx.m40
mhpt1bxi.bin tbix.m40 mhpt1bxm.bin tbmx.m40
mhpt1ip.bin ti.m40 mhpt1ipm.bin tim.m40
mhpt1m.bin tm.m40
p25ip.bin i.p25 p25ipx.bin p.p25
p50bria.bin ba.p50 p50brib.bin b.p50
p50brina.bin ban.p50 p50brinb.bin bn.p50
p50s562.bin 52.p50 p50s564.bin 54.p50
sosbri.bin b.p40 sose1.bin e.p40
soss562.bin 52.P40 soss564.bin 54.p40
sost1.bin t.p40
