Nortel Networks 5399 Manual De Usuario
Nortel Networks 5399 Access Switch Hardware Installation Guide
Chapter 2
Installing the Model 5399 Remote Access Concentrator Module
2-30
Image name: <invalid or uninitialized> Default:
“oper.64.enet”
Enter Image name::oper.64.enet
Image name: “oper.64.enet”
TFTP load directory:
Enter TFTP load directory::/annex
TFTP Dump path/filename: <uninitialized> Default :
“dump.134.117.6.34”
Enter TFTP Dump path/filename::/annex/mydumpfile
Using current TFTP Dump path/filename.
monitor::
“oper.64.enet”
Enter Image name::oper.64.enet
Image name: “oper.64.enet”
TFTP load directory:
Enter TFTP load directory::/annex
TFTP Dump path/filename: <uninitialized> Default :
“dump.134.117.6.34”
Enter TFTP Dump path/filename::/annex/mydumpfile
Using current TFTP Dump path/filename.
monitor::
3.
Issue the following commands to prepare the tftp dump file.
touch /tftpboot/annex/mydumpfile
chmod 622 /tftpboot/annex/mydumpfile
4.
Enter the boot command.
The boot command display looks similar to this:
Enter boot file name[oper.64.enet]::
Waiting for Config Block Info...
Requesting boot file ”oper.64.enet”.
Unanswered requests shown as ’?’,transmission errors
as ’*’.
Unanswered requests shown as ’?’,transmission errors
as ’*’.
Requesting boot from 192.9.200.88 via Ethernet...
Booting BFS file using open delay of 8?
Booting TFTP file using open delay of 8
Booting TFTP file from 192.9.200.88
Header received OK. Received data blocks shown as ’.’.
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . EOF
Booting BFS file using open delay of 8?
Booting TFTP file using open delay of 8
Booting TFTP file from 192.9.200.88
Header received OK. Received data blocks shown as ’.’.
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . EOF
Once the Remote Access Concentrator is booted, Monitor Mode is no
longer operational. The Remote Access Concentrator is up and running
longer operational. The Remote Access Concentrator is up and running
,
and the following message is displayed:
Console monitor ready; Press CR to start.