Customize Guide For NE80E V600R003C00 Version Upgrade

HUAWEI NetEngine40E/80E Universal
Service Router
V600R003C00
Cusmoize Guide
Date
11-04-2013
CONTENTS
1- Check list Before You Start.
2- Backup for old software files.
3- Deleting Unnecessary Files.
4- Upgrade Procedure.
5- Verifying the Upgrade.
6- Rollback procedures.
7- Verifying the Rollback.
8- Special topics for special Cases.
1- Check list 1 Before Starting :

We have use the below check after and before the
action .
- First we will takes screen shots for the router alarms
- Second run the below list of commands:
display interface brief main | i Gig
display interface brief main | i Tun
display interface brief main | i Pos
display ospf peer
display bgp vpnv4 all peer
display interface --- > to check the power after and before
display bfd session all
display alarm all
display device
display device pic-status
display memory-usage
display cpu-usage
display health
dir
dir slave#cfcard:
display current-configuration
display version
display device pic-status
display interface
display startup
display patch-information
display paf all
display switchover state
display device
display ip interface brief
display health
display ip routing-table statistics
display bgp vpnv4 all peer
display bgp vpnv4 all routing-table statistics
display mpls ldp peer
display mpls ldp session all
display assert 10
display exception 10
display deadloop 10
2- Backup for old software files:

We need to take a backup from the old files and the
configuration files.
Step 1 Before backup save the configuration file, or compare configuration to make sure
backup file same with running configuration.
Step 2 Log in to the FTP server from the PC that functions as an FTP client.
1.
Choose Start > Run. Enter cmd and then press Enter.
2.
Enter ftp ( O&M IP ).

C:\Documents and Settings\Administrator> ftp ( O&M IP ).
Connected to ( O&M IP )..
220 FTP service ready.
3.
Enter the user name ftpuser and the password huawei. The ftp> prompt is displayed
on the FTP client.
User ( O&M IP ).:(none)): Username
331 Password required for Password.
Password:
230 User logged in.
Step 3 Set the file transfer mode to binary and the directory where the Software files are for
example to c:\ for the FTP client.
ftp> binary
200 Type set to I.
ftp> lcd c:\
Local directory now C:\
Step 4 At the ftp> prompt, run the get remote-filename [ local-filename ] command to download
files from the FTP server, and then save the files in the c:\ directory.
For example, download confile.cfg, paf.txt, license.txt, V600R001C00SPC200B206.cc,
and the GTL license file and save them in the root directory.
ftp> get config.cfg confilebackup.cfg
200 Port command okay.
150 Opening BINARY mode data connection for config.cfg.
226 Transfer complete.
ftp: 4545 bytes received in 0.01Seconds 303.00Kbytes/sec.
ftp> get paf-v6r1.txt pafbackup.txt

150 Opening BINARY mode data connection for paf-v6r1.txt.
ftp> get license-v6r1.txt licensebackup.txt
150 Opening BINARY mode data connection for license-v6r1.txt.
ftp> get v600r001c00spc200b206.cc v600r001c00spc200b206backup.cc
150 Opening BINARY mode data connection for v600r001c00spc200b206.cc.
ftp> get gtl.dat gtlbackup.dat
150 Opening BINARY mode data connection for gtl.dat.
ftp: 1705 bytes received in 0.01Seconds 113.67Kbytes/sec
----End
3 -Deleting Unnecessary Files

Note the following issues when deleting files:
Do not delete the private-data.txt file because it is a system file.
Delete $_patchstate_a.backup.
Verify that system software (.cc), configuration files (.cfg or .zip), GTL license file
(.dat), PAF file (.txt), and license file (.txt) are not used before deleting them.
If remaining space on the CF cards is insufficient for storing target system software, run
the following commands in the user view to delete the unnecessary files from the CF cards
on both MPUs.
<HUAWEI> delete cfcard:/$_patchstate_a.backup
Info: Deleting file cfcard:/$_patchstate_a.backup...succeeded.
<HUAWEI> delete slave#cfcard:/$_patchstate_a.backup
Info: Deleting file slave#cfcard:/$_patchstate_a.backup...succeeded.
Run the following command to restore the dumped file in the recycle bin.
<HUAWEI> undelete cfcard:/$_patchstate_a.backup
%Undeleted file cfcard:/$_patchstate_a.backup.
Run the following commands to delete unnecessary files permanently.

<HUAWEI>
<HUAWEI>
<HUAWEI>
<HUAWEI>
reset
reset
reset
reset
recycle-bin
recycle-bin
recycle-bin
recycle-bin
cfcard:/
cfcard2:/
slave#cfcard:/
slave#cfcard2:
4- Upgrade Procedure :
Step 1 Log in to the FTP server from the PC that functions as an FTP client.
1.
Save the files to be uploaded in the specified directory (for example, c:\) on the PC.
Choose Start > Run on the PC. Enter cmd and press Enter.
2.
Enter ftp (O&M IP).

Enter Error! Hyperlink reference not valid..C:\Documents and
Settings\Administrator>ftp (O&M IP)
Connected to (O&M IP)
220 FTP service ready.
3.
Enter the user name and the password ,The ftp> prompt is displayed on the FTP
client.
User ((O&M IP).:(none)): username
331 Password required for password.
Password:****
230 User logged in.
ftp>
Step 2 Set the file transfer mode to binary and the directory to c:\temp on the PC.
ftp> binary
200 Type set to I.
ftp> lcd c:\
Local directory now C:\
Step 3 At the ftp> prompt, run the put local-filename [ remote-filename ] command to upload the
specified files on the PC.
.
ftp> put V6R3C00-NE-X3.CC V6R3C00-NE-X3.CC
150 Opening BINARY mode data connection for V6R3C00-NE-X3.CC
ftp: 263098112 bytes sent in 743.13Seconds 354.04Kbytes/sec.
Step 4 Copy files to the CF card on the slave MPU and view uploaded files.
Run the copy source-filename destination-filename command to copy system software,
paf.txt, license.txt, and the GTL license file from the master MPU's CF card to the slave
MPU's CF card.
<HUAWEI> copy cfcard:/V6R3C00-NE-X3.CC slave#cfcard:/V6R3C00-NE-X3.CC
Warning: File cfcard:/ V6R3C00-NE-X3.CC will be copied to slave#cfcard:/
V6R3C00-NE-X3.CC. Continue? [Y/N]:y
100% completed.
.
After the preceding operations, run the dir command to view the uploaded files and verify
that the files have been uploaded or downloaded completely.
After uploading or downloading files, verify their completeness. If a file is incomplete due to
insufficient storage space, delete unnecessary files from the CF card and upload or download the file
again. For information about how to delete unnecessary files from a CF card, see "3 -Deleting
Unnecessary Files."
<HUAWEI> dir cfcard:
Directory of cfcard:/
Idx
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
Attr
drwdrwdrw-rwdrw-rw-rwdrw-rw-rw-rw-rw-rw-rw-rwdrwdrw-
Size(Byte)
284,588,262
86,731
1,851
3,336
246,057,216
5,009
14,721
123,151
120,325
14,592
-
Date
Sep 02
Sep 02
Apr 26
Jan 25
Jan 25
Jan 25
Jan 25
Jan 25
Jan 25
Jan 25
Jan 25
Jan 25
Jan 25
Jan 25
Jan 25
Jan 25
Jan 25
2008
2008
2000
2011
2011
2011
2011
2011
2011
2011
2011
2011
2011
2011
2011
2011
2011
1,000,176 KB total (497,963 KB free)
Time(LMT)
17:50:12
17:50:12
12:00:04
21:29:18
11:21:32
21:03:42
21:16:46
19:09:22
19:09:14
18:52:26
20:58:36
21:03:58
21:09:00
21:15:42
21:15:50
11:20:52
11:09:46
FileName
bam
bambak
bak
V6R3C00-NE-X3.cc
pmdata
paf-v6r1.txt
gtl.dat
log
$_patchstate_reboot
v600r001c00spc200b206.cc
vrpcfg.cfg
license-v6r1.txt
$_patchstate_a.backup
paf-ne.txt
license-ne.txt
bill
mplstpoam
<HUAWEI> dir slave#cfcard:/

Directory of slave#cfcard:/
Idx Attr
Size(Byte) Date
0 -rw123,151 Jan 25
1 -rw5,009 Jan 25
2 drw- Jan 25
3 drw- Jan 25
4 -rw14,592 Jan 25
5 -rw1,851 Jan 25
6 -rw284,588,262 Jan 25
7 -rw14,400 Jan 25
v6r1c00spc200b206_patch001.pat
8 -rw246,057,216 Jan 25
9 -rw120,325 Jan 25
10 drw- Jan 25
11 -rw3,336 Jan 25
2011
2011
2010
2011
2011
2011
2011
2011
Time(LMT)
21:10:06
21:19:16
11:29:06
11:09:30
21:18:34
21:18:56
21:42:54
21:41:24
FileName
$_patchstate_a.backup
vrpcfg.cfg
dhcp
mplstpoam
license-ne.txt
gtl.dat
V6R3C00-NE-X3.cc
2011
2011
2011
2011
19:05:54
21:18:14
11:22:36
21:36:14
v600r001c00spc200b206.cc
paf-ne.txt
bill
$_patchstate_reboot
1,000,107 KB total (496,253 KB free)
Step 5 Check whether a patch is running.

If no patch is running, go to the next step. If a patch is running, uninstall the patch to
ensure that no patch runs next time the system reboots.
V600R002 is used as a source version here.
No patch is running in the system.

If the following command output is displayed, go to the next step.
<HUAWEI> display patch-information
Info: No patch exists.
************************************************************************
*
The cold patch information, as follows:
*
************************************************************************
Patches are running in the system.

<HUAWEI> display patch-information
Service pack Version:V600R001C00SPH001
Pack file name
:cfcard:/v6r1c00spc200b206_patch001.pat
----------The patch information of slot 9---------Total Patch Unit
: 1
Running Patch Unit
: 1 - 1
Active Patch Unit
:
Deactive Patch Unit
:
----------The patch information of slot 10---------Total Patch Unit
: 1
Running Patch Unit
: 1 - 1
Active Patch Unit
:
Deactive Patch Unit
:
----------The patch information of slot 8---------This slot does not need patch
If the preceding command output is displayed, patches are running in the system.
Perform the following operations under the guidance of Huawei technical support
personnel:
1.
Delete patch files from MPUs and LPUs.

<HUAWEI> patch delete all
2.
Delete both the current patch configurations and the patch configuration for the next
startup.
<HUAWEI> reset patch-configure
<HUAWEI> reset patch-configure next-startup
Step 6 Specify system software, and the configuration file for the next startup.
Do specify system software before specifying the PAF and license files; otherwise, the system
may use the default PAF and license files during startup.
The system loads PAF and license files contained in system software by default. Although userdefined PAF and license files are specified for the next start up, the startup paf default
command and the startup license default command can specify the default files for the next
startup. In V300R002 or earlier, PAF and license files saved in the CF card can only be loaded.
If dual MPUs are installed on an NE40E/80E, the configuration file must have been stored in CF
cards on both MPUs before being loaded; the PAF file, license file, and system software on the
master MPU must be the same as those on the slave MPU. Any inconsistency will cause trouble
in restarting the NE40E/80E.
Specify the system software to be loaded to both MPUs for the next startup.
<HUAWEI> startup system-software V6R3C00-NE-X3.CC
Info: Succeeded in setting the software for booting system.
<HUAWEI> startup system-software V6R3C00-NE-X3.CC slave-board
Info: Succeeded in setting the software for booting system.
Info: Succeeded in setting main board resource file for system.
(Optional) Specify the startup configuration file for the NE40E/80E. If no configuration
file is specified, the configuration file for the source version is used during the next
startup.
<HUAWEI> startup saved-configuration vrpcfg.cfg
Info: Succeeded in setting the configuration for booting system.
After completing the preceding operations, run the display startup command to verify
that files to be loaded for the next startup have been specified successfully.
If a V600R001 or V600R002 sub-version is to be upgraded to a later sub-version, run the check

startup crc next command to perform a CRC check before restarting the system. The CRC
check lasts about 5 minutes. If an error occurs, delete target system software and re-upload it.
If V300R003 is to be upgraded to V600R003C00, verify that the number of uploaded bytes is the
same as the target system software size. This means that system software is uploaded completely.
After a source version is upgraded to V600R003C00, run the check system-software

cfcard:/v600r003c00spc001.cc command to verify the integrity of the target system software. If
the check fails, re-upload the target system software. The system software named
v600r003c00spc001.cc is saved in the CF card.
<HUAWEI> display startup

MainBoard:
Configured startup system software:
Startup system software:
Next startup system software:
cfcard:/v600r001c00spc200b206.cc
cfcard:/V6R3C00-NE-X3.cc
Startup saved-configuration file:

Next startup saved-configuration file:
Startup paf file:
Next startup paf file:
Startup license file:
Next startup license file:
Startup patch package:
Next startup patch package:
SlaveBoard:
Startup paf file:
cfcard:/vrpcfg.cfg
cfcard:/vrpcfg.cfg
cfcard:/paf-v6r1.txt
cfcard:/paf-ne.txt
cfcard:/license-v6r1.txt
cfcard:/license-ne.txt
NULL
NULL
cfcard:/vrpcfg.cfg
cfcard:/vrpcfg.cfg
cfcard:/paf-v6r1.txt
cfcard:/paf-ne.txt
cfcard:/license-v6r1.txt
NULL
NULL
Step 7 Save configurations.

<HUAWEI> save
The current configuration will be written to the device.
Are you sure to continue?[Y/N]y
Now saving the current configuration to the slot 4 ..
Save the configuration successfully.
Step 8 Reboot the NE40E/80E.
Some commands and functions may change because the configuration file changes after the
reboot.
The reboot fast command is used to restart an NE40E/80E without a message displayed to ask
you whether or not to save configurations.
<HUAWEI> reboot
mpu 5:
Next startup system software: cfcard:/V6R3C00-NE-X3.cc
Paf: V600R003C00
License: V600R003C00
Next startup saved-configuration file: cfcard:/vrpcfg.cfg
The Other Mpu is the same with Mpu 5
Info: The system is now comparing the configuration, please wait.
Warning: Inactive configuration may be lost. Whether to save them to
configuration file for the next startup:cfcard:/vrpcfg.cfg?[Y/N]:y
System will reboot! Continue?[Y/N]:y
Step 9 After the restart, run the display startup command to verify that the NE40E/80E is running
target system software.
During the upgrade, if a board is loading system software, the board's RUN indicator blinks twice
every second; after the board registers successfully, its RUN indicator blinks once every second.
Before proceeding to the next step, determine whether the board registers successfully by observing
its RUN indicator.
In versions later than V300R003C02B608, if the system is configured to use the default PAF and
license files, the display startup command displays "Next startup license file:
default" and
"Startup license file:
default."
<HUAWEI> display startup
MainBoard:
Startup paf file:
SlaveBoard:
Startup paf file:
cfcard:/vrpcfg.cfg
cfcard:/vrpcfg.cfg
cfcard:/paf-ne.txt
cfcard:/paf-ne.txt
NULL
NULL
cfcard:/vrpcfg.cfg
cfcard:/vrpcfg.cfg
cfcard:/paf-ne.txt
cfcard:/paf-ne.txt
NULL
NULL
5- Verifying the Upgrade
Verifying the System Software Version

After the upgrade, run the display version and display startup commands in any view to
check the NE40E/80E system software version. The display in bold is the current
NE40E/80E system software version. Check whether the system software is the target
version. If the version is not the target version, review the upgrade steps to determine the
cause of the problem and then perform the version upgrade again.
<HUAWEI> display version
Huawei Versatile Routing Platform Software
VRP (R) software, Version 5.90 (NE40E&80E V600R003C00)
Copyright (C) 2000-2011 Huawei Technologies Co., Ltd.
HUAWEI NE40E-X3 uptime is 0 day, 0 hour, 16 minutes
NE40E-X3 version information:
---- More ---<HUAWEI> display startup
MainBoard:
cfcard:/vrpcfg.cfg
cfcard:/vrpcfg.cfg
Startup paf file:
cfcard:/paf-ne.txt
cfcard:/paf-ne.txt
NULL
NULL
SlaveBoard:
cfcard:/vrpcfg.cfg
cfcard:/vrpcfg.cfg
Startup paf file:
cfcard:/paf-ne.txt
cfcard:/paf-ne.txt
NULL
NULL
Verifying that Boards Successfully

Register
Run the display device command in any view to check the registration status of boards.
Status should be Normal.
<HUAWEI> display device
NE40E-X3's Device status:
Slot #
Type
Online
Register
Status
Primary
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1
2
3
4
5
6
7
9
10
LPU
LPU
LPU
MPU
MPU
CLK
CLK
PWR
FAN
Present
Present
Present
Present
Present
Present
Present
Present
Present
Registered
Registered
Registered
Registered
NA
Registered
Registered
Registered
Registered
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
Normal
NA
NA
NA
Slave
Master
Slave
Master
NA
NA
Verifying the Version Consistency on

Components
If there are version inconsistencies after the upgrade, perform a manual upgrade by
following the instructions in Error: Reference source not found"Error: Reference source
not found."
Run the check version startup command in the user view to check the software upgrade
result.
If the upgrade succeeded, the display is as follows:
<HUAWEI> check version startup
Info:Software version match ok!
This display indicates that the software version of each component on the NE40E/80E is
the same as the current system software version. A detailed list for each component is not
displayed.
If the upgrade failed, the display is as follows:
Slot#
Type Content
CurVer ExactVer State
Upgrade Suggestion
10
FAN MonitorBus Software 1.6
1.7
Incompatible
Must
In this example, the display indicates that the version of the MonitorBus of the LPU in slot
6 does not match the current system software version. You must upgrade the MonitorBus
of the LPU.
If there are inconsistencies like the one shown in the preceding display, you must perform
a manual upgrade to correct the problem. For detailed instructions, see section Error:
Reference source not found"Error: Reference source not found."
Verifying Device Status

Run the display health and display alarm commands in the user view to check device
operating status. Make sure that all boards (MPUs and LPUs) are functioning properly.
<HUAWEI> display health
Slot
CPU Usage Memory Usage(Used/Total)
--------------------------------------------------------5 MPU(Master)
9%
24% 438MB/1825MB
1 LPU
18%
39% 322MB/823MB
2 LPU
20%
39% 322MB/807MB
3 LPU
8%
42% 358MB/840MB
4 MPU(Slave)
7%
21% 394MB/1825MB
<HUAWEI> display alarm all

---------------------------------------------------------------------------NO alarm
Keep a detailed record of the operating status of each board for use as a troubleshooting
reference.
Checking Whether RUN Indicators on Boards Are

Working Properly
RUN indicators on a board panel can identify working status of the board based on their
blinking intervals. Blinking intervals of RUN indicators on different boards are as follows:
Blinking intervals of RUN indicators on a main control board
Main Control
Board
Blinking
Intervals of
RUN
Indicators
on the MPU
of
the
NE40E/NE80
E)
Blinking
Intervals
of
RUN
Indicators on
the MPUD of
the NE40E-X3
Blinking Intervals
of RUN Indicators
on
the
MPUC/SRUC of the
NE40E-X8/NE40EX16
Non-file loading
phase before main
control
board
registration
2s
1s
1s
File loading phase

before
main
control
board
registration
0.12s
0.06s
0.06s
After main control

board registration
1s
1s
1s
Table 1.1.1.I.9.1.1.1 Blinking intervals of RUN indicators on an LPU

LPU
Blinking Intervals
of RUN Indicators
on
the
LPUA/LPUG/LPUH
Blinking
Intervals
of
RUN Indicators
on the LPUF10/20/40
Blinking
Intervals of
RUN
Indicators
on
the
LPU41/101
Non-file loading
phase
before
LPU registration
2s
Constantly off
Constantly off
File
loading
phase
before
LPU registration
0.5s
0.5s
0.12s
After
LPU
registration
1s
1s
1s
Table 1.1.1.I.9.1.1.2 Blinking intervals of RUN indicators on an SFU

SFU
Blinking Intervals of RUN Indicators on the

SFU
Non-file loading phase

before SFU registration
2s
BootROM loading phase

Constantly on
Other file loading phase

0.5s
After SFU registration
1s
If a board fails to register, it will cycle in the following process until it registers successfully: nonfile loading phase before registration, file loading phase before registration, and registering phase.
Verifying Configurations
Run the display current-configuration command to check the NE40E/80E configurations
after the NE40E/80E starts up. Run the compare configuration command in the user view
to compare the new configuration file with the saved configuration file. This allows you to
check whether any configurations have been lost or changed.
The following display shows that no configuration has been lost:
<HUAWEI> compare configuration
Info:The current configuration is the same as the next startup configuration
file.
The following display shows that some configurations have been lost:
<HUAWEI> compare configuration
Warning: The current configuration is not the same as the next startup
configura
tion file.
====== Current configuration line 16 ======
efm enable
#
clock source bits0 ssm unk
clock source bits1 ssm unk
clock source ptp ssm unk
#
snmp-agent trap type base-trap
====== Configuration file line 16 ======
efm enable
#
snmp-agent trap type base-trap
#
slot 2
iphc aging-time 20
#
diffserv domain default
diffserv domain 5p3dbas
Verifying Services
Two methods are available for verifying whether services are normal.
Check whether services are running properly before running the save command.
Compare data entries from the upgraded routing table, FIB table, MAC table and
other tables with pre-upgrade entries from the same tables to determine if any data
has been lost. Check whether the traffic volumes of services are the same before and
after the upgrade.
Contact network management personnel from the customer to check whether services
are running properly.
6- Rollback procedures
Scenarios and Method of

Version Rollback
If the NE40E/80E functions properly after the system software upgrade, use
command lines to perform version rollback.
If the NE40E/80E does not function properly after the system software upgrade, use
the BootROM to perform version rollback in the special topics part.
Performing Version Rollback Using Command Lines

If the NE40E/80E can reboot, but some services cannot be properly processed after the
upgrade, perform version rollback using command lines.
The method for version rollback using command lines is the same as that for upgrading the
system software using command lines.
PAF file, license file, and patch file are stored on the CF card, you do not need to upload
these files again. We only need to set the old system software and configuration file to be
used for the next startup, and then run the reboot command in the user view.
And be noted If we are rolling back the system to a source version earlier than
V300R003, we must change the names of the target PAF and license files to paf.txt
and license.txt and copy these two files to the CF card of the master MPU as well as to
the slave MPU if there is one.
7- Verifying the Rollback

The method and the check list for Verifying the Rollback is the same as that for upgrading
the system software.
8- Special topics for special Cases

I- Performing Version Rollback Using BootROM
Upgrade Procedure
Step 1 Connect the Console interface of the MPU to be upgraded on an NE40E/80E and the COM
interface of a PC, and configure the HyperTerminal.
Step 2 Powering on and powering off the NE40E/80E. The HyperTerminal interface displays the
following information:
*************************************************************
*
Copyright 2000-2009 Huawei Tech. Co., Ltd.
*
*************************************************************
Board Name ....................................... CR52MPUA
SDRAM Size .......................................
Enable the instruction cache .....................
Disable the data cache ...........................
Disable the ECC...................................
The SDRAM testing ................................
The SDRAM ECC initializing .......................
2048MB
pass!
pass!
pass!
pass!
pass!
Now begin to initialize system

Mpu reset other board ............................
Cache library initializing........................
Exception vectors initializing....................
The host bridge initializing......................
Page table initializing...........................
CPU initializing..................................
Console device initializing.......................
PCI scanning......................................
L2 cache initializing.............................
Wind kernel configuration initializing............
MMU initializing..................................
Instruction cache initializing....................
Data cache initializing...........................
System clock initializing.........................
I/O and file system initializing..................
TTY devices creating and initializing.............
pass!
pass!
pass!
pass!
pass!
pass!
pass!
pass!
pass!
pass!
pass!
pass!
pass!
pass!
pass!
pass!
Standard input/output/error device setting........

Exception show routines initializing..............
Exception handling installing.....................
Log task initializing.............................
WDT starting......................................
MUX devices initializing..........................
pass!
pass!
pass!
pass!
pass!
pass!
Now begin to test key chips

The serial port testing .......................... pass!
The bridge register testing ...................... pass!
The bridge internal sram(256K Bytes) testing ..... pass!
The epld1 testing ................................ pass!
The main boot ROM and backup boot ROM comparing .. pass!
The boot ROM testing ............................. pass!
Press CTRL+T to start sdram full test in 1 seconds!
The slot ID testing .............................. pass!
Starting...
ncompressing type 2 ......one!
I2c Init Create Sem OK
CLOCK_REALTIME(yyyy/mm/dd - hh:mm:ss) is: 2011/01/25 - 19:08:17
Start file system check...
pFd->pVolDesc->devHdr.name = cfcard:.
pVolDesc->devHdr.name = cfcard:.
cfcard:/ - Volume is OK
****************************************************
*
*
*
8090 boot ROM, Ver 366.00
*
*
*
****************************************************
Creation date: Aug 16 2009, 20:05:44
CPU
CPU
CPU
BUS
type
L2 Cache
Core Frequency
Frequency
:
:
:
:
MPC7447A
512KB
1GHz
133MHz
Press Ctrl+B to enter Main Menu... 3
Step 3 Press Ctrl+B within 3 seconds after the prompt of Press Ctrl+B to enter Main Menu... 3
is displayed.
password:
Step 4 Enter a password and enter the main menu.

The default password is 8090. The password can be changed by selectin g 6. Modify boot ROM
password in the main menu.
Main
Menu(bootload ver: 216.00)
1. Boot with default mode

2. Boot from CFcard
3. Enter serial submenu
4. Enter ethernet submenu
5. Set boot file and path
6. Modify boot ROM password
7. List file in CFcard
8. Chkdsk CFcard
9. Set patch mode
10. Set version back signal
11. Reboot
Enter your choice(1-11):4
Step 5 Select 4. Enter ethernet submenu to enter the Ethernet interface submenu.
Ethernet
1.
2.
3.
4.
Submenu
Download file to SDRAM through ethernet interface and boot

Download file to CFcard through ethernet interface
Modify ethernet interface boot parameters
Return to main menu
Be sure to select 3 to modify boot parameters before downloading!

Enter your choice(1-4): 3
Step 6 Select 3. Modify ethernet interface boot parameters to set boot parameters.
Note: two protocols for download, tftp & ftp.
You can modify the flags following the menu.
tftp--0x80, ftp--0x0.
'.' = clear field;
'-' = go to previous field;
^D = quit
boot device
: mgi0 \\The value of this parameter can be mgi0 or mgi2.
If the file fails to be loaded when the parameter is set to mgi0, set the
parameter to mgi2.
\\Set the parameter to motetsec0 for an MPUC
or SRUC.
processor number
: 2 \\If the preceding parameter is set to mgi0, this
parameter must be set to 2; if the preceding parameter is set to mgi2, this
parameter must be set to 0.
\\Set the parameter to 0 for an MPUC or SRUC.
host name
: host \\This parameter does not need to be set.
file name
: V6R3C00-NE-X3.CC \\The parameter is the name of system
software on the server.
inet on ethernet (e) : 1.1.1.100:FFFFFF00 \\IP address and mask set for the
local device so that the local device can communicate with the FTP server.
inet on backplane (b): \\A backup interface connected to the FTP server. This
parameter does not need to be set.
host inet (h)
: 1.1.1.2 \\IP address of the FTP server.
gateway inet (g)

\\This parameter indicates the gateway used to communicate
with the FTP server. This parameter does not need to be set.
user (u)
: 8090 \\FTP user name that must be the name of a user on
the FTP server.
ftp password (pw) (blank = use rsh): 8090 \\FTP user password.
flags (f)
: 0x0
\\This parameter specifies whether to upgrade the
system software by means of FTP or TFTP. FTP (0x80) is used by default. To use
TFTP, enter 0x80.
target name (tn) \\This parameter does not need to be set.
startup script (s) \\This parameter does not need to be set.
other (o)
:
\\This parameter does not need to be set.
Ethernet
Submenu
1. Download file to SDRAM through ethernet interface and boot

2. Download file to CFcard through ethernet interface
3. Modify ethernet interface boot parameters
4. Return to main menu
The configuration is now completed. The system returns to the Ethernet interface
submenu.
Step 7 Select 4. Return to main menu. The system returns to the main menu.
Main
1. Boot with default mode

2. Boot from CFcard
3. Enter serial submenu
4. Enter ethernet submenu
5. Set boot file and path
6. Modify boot ROM password
7. List file in CFcard
8. Chkdsk CFcard
9. Set patch mode
10. Set version back signal
11. Reboot
Step 8 Select 5. Set boot file and path to specify the configuration file at the next startup.
Boot
1.
2.
3.
4.
5.
6.
7.
Files
Modify
Modify
Modify
Modify
Modify
Modify
Return
Submenu
the boot file

the paf file
the license file
the config file
the patch file
the patch states file
to main menu
Step 9 Select 1. Modify the boot file to change the configuration file at the next startup.
boot file is cfcard:/V300R003C02B697.cc, modify the file name if needed.
Please input correctly, e.g.: cfcard:/V200R001B019.cc cfcard:/ V6R3C00-NEX3.CC \\Enter the name of the loaded system software and an absolute path to
save the system software, and press Enter.
The file name you input is cfcard:/ V6R3C00-NE-X3.CC.
Are you sure? Yes or No(Y/N)y
Select 1 Modify the boot file again to check whether the file has been changed
successfully.
Boot
1.
2.
3.
4.
5.
6.
7.
Files
Modify
Modify
Modify
Modify
Modify
Modify
Return
Submenu
the boot file

the paf file
the license file
the config file
the patch file
to main menu

boot file is cfcard:/ V6R3C00-NE-X3.CC, modify the file name if needed.
Please input correctly, e.g.: cfcard:/V200R001B019.cc
The methods for specifying the PAF and license files and the configuration file are the same as that
for specifying the system software. It is not detailed here.
Step 10 Enter y and press Enter. After files have been successfully loaded, the system returns to the
boot files Submenu.
Setting ...
Read flag rec from nvram ......................OK!
Write descriptor to nvram ......................OK!
Done!
Clear version back signal...Done!
Boot
1.
2.
3.
4.
5.
6.
7.
Modify
Modify
Modify
Modify
Modify
Modify
Return
Files
Submenu
the boot file

the paf file
the license file
the config file
the patch file
to main menu
Step 11 Select 7. Return to main menu. The system returns to the main menu.
Main
1.
2.
3.
4.
5.
6.
Boot with default mode

Boot from CFcard
Enter serial submenu
Enter ethernet submenu
Set boot file and path
Modify boot ROM password
7.
8.
9.
10.
11.
List file in CFcard

Chkdsk CFcard
Set patch mode
Set version back signal
Reboot
Step 12 Upgrade the system software of the slave MPU.
Plug the console cable to the Console interface of the slave MPU and restart the
NE40E/80E. The upgrade process is the same as that used to upgrade the master MPU.
Step 13 Select 2. Boot from Cfcard to start the NE40E/80E from the CF card. The NE40E/80E
reboots using the newly loaded system software.
Booting from CFcard
Be sure the baudrate be 9600bps!
cfcard:/
- Volume is OK
The start file is cfcard:/ V6R3C00-NE-X3.CC

The config file is cfcard:/vrpcfg.cfg
The paf file is cfcard:/paf-ne.txt
The license file is cfcard:/license-ne.txt
CurrentBootFile's crc: 13102
Loading........................................................................
.
...............................................................................
.
...............................................................................
.
...............................................................................
.
........................................................................Done!
Took time : 12s
Clear version back signal...Done!
Update main boot ROM...
Writing data to boot ROM...
Took time: 6s
Success!Done!
Update bootload success!
System will reboot...
*************************************************************
*
*
*************************************************************
Board Name ....................................... CR52MPUA
SDRAM Size ....................................... 2048MB
Enable the instruction cache .....................

Disable the data cache ...........................
Disable the ECC...................................
The SDRAM testing ................................
The SDRAM ECC initializing .......................
pass!
pass!
pass!
pass!
pass!
Now begin to initialize system

Mpu reset other board ............................
Cache library initializing........................
Exception vectors initializing....................
The host bridge initializing......................
Page table initializing...........................
CPU initializing..................................
Console device initializing.......................
PCI scanning......................................
L2 cache initializing.............................
Wind kernel configuration initializing............
MMU initializing..................................
Instruction cache initializing....................
Data cache initializing...........................
System clock initializing.........................
I/O and file system initializing..................
TTY devices creating and initializing.............
Standard input/output/error device setting........
Exception show routines initializing..............
Exception handling installing.....................
Log task initializing.............................
WDT starting......................................
MUX devices initializing..........................
pass!
pass!
pass!
pass!
pass!
pass!
pass!
pass!
pass!
pass!
pass!
pass!
pass!
pass!
pass!
pass!
pass!
pass!
pass!
pass!
pass!
pass!
Now begin to test key chips

The serial port testing .......................... pass!
The bridge register testing ...................... pass!
The bridge internal sram(256K Bytes) testing ..... pass!
Warning: The main boot ROM and backup boot ROM is different!
The boot ROM testing ............................. pass!
Press CTRL+T to start sdram full test in 1 seconds!
The slot ID testing .............................. pass!
Starting...
ncompressing..................one!
I2c Init Create Sem OK
CLOCK_REALTIME(yyyy/mm/dd - hh:mm:ss) is: 2011/01/25 - 19:32:17
Start file system check...
Copy boot ROM small system to flash...OK!

Copy boot ROM main system to flash...OK!
****************************************************
*
*
*
8090 boot ROM, Ver 317.00
*
*
*
****************************************************
Creation date: May 9 2009, 17:51:28
CPU
CPU
CPU
BUS
type
L2 Cache
Core Frequency
Frequency
:
:
:
:
MPC7447A
512KB
1GHz
133MHz
Press Ctrl+B to enter Main Menu... 3

Auto-booting...
Step 14 Verify that the NE40E/80E system software has been upgraded successfully.
Info:Software version match Ok!
Software version match Ok! indicates that the upgrade has succeeded. Otherwise,
upgrade the item manually.
Step 15 (Optional) If the channel check function has been disabled before the upgrade, run the
board-channel-check enable command to enable the channel check function to ensure that
the system software on the slave MPU can be upgraded successfully.
----End
II- For Upgrading the System Software Using the

BootROM
we will Refer to the rollback topic using the BootRom except the
transfer version files steps as the below:
1 Select 2. Download file to CFcard through ethernet interface to download the system
software to the CF card.
C address:0xa 0xb 0xc 0x0 0x9 0x0
Attached TCP/IP interface to mgi2.
Attaching network interface lo0... done.
boot device
unit number
: mgi\\Set the parameter to motetsec for an MPUC or SRUC.

: 2
processor number
: 0
host name
: host
file name
: V6R3C00-NE-X3.CC
inet on ethernet (e) : 1.1.1.100:FFFFFF00
host inet (h)
: 1.1.1.3
user (u)
: 8090
ftp password (pw)
: 8090
flags (f)
: 0x0
target name (tn)
:
Loading
...Done!
Writing to CFcard...Done!
Ethernet
1.
2.
3.
4.
Submenu
Download file to SDRAM through ethernet interface and boot

Download file to CFcard through ethernet interface
Modify ethernet interface boot parameters
Return to main menu

After the system software is loaded, the system returns to the Ethernet interface submenu

Customize Guide For NE80E V600R003C00 Version Upgrade

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Customize Guide For NE80E V600R003C00 Version Upgrade

Caricato da

Copyright:

Formati disponibili

HUAWEI NetEngine40E/80E Universal

1- Check list 1 Before Starting :

2- Backup for old software files:

Enter ftp ( O&M IP ).

ftp> get paf-v6r1.txt pafbackup.txt

3 -Deleting Unnecessary Files

Do not delete the private-data.txt file because it is a system file.

Run the following commands to delete unnecessary files permanently.

Enter ftp (O&M IP).

1,000,176 KB total (497,963 KB free)

<HUAWEI> dir slave#cfcard:/

1,000,107 KB total (496,253 KB free)

Step 5 Check whether a patch is running.

No patch is running in the system.

Patches are running in the system.

Delete patch files from MPUs and LPUs.

If a V600R001 or V600R002 sub-version is to be upgraded to a later sub-version, run the check

After a source version is upgraded to V600R003C00, run the check system-software

<HUAWEI> display startup

Startup saved-configuration file:

Step 7 Save configurations.

Step 8 Reboot the NE40E/80E.

5- Verifying the Upgrade

Verifying the System Software Version

Verifying that Boards Successfully

Verifying the Version Consistency on

Verifying Device Status

<HUAWEI> display alarm all

Checking Whether RUN Indicators on Boards Are

File loading phase

After main control

Table 1.1.1.I.9.1.1.1 Blinking intervals of RUN indicators on an LPU

Table 1.1.1.I.9.1.1.2 Blinking intervals of RUN indicators on an SFU

Blinking Intervals of RUN Indicators on the

Non-file loading phase

BootROM loading phase

Other file loading phase

After SFU registration

Scenarios and Method of

Performing Version Rollback Using Command Lines

7- Verifying the Rollback

8- Special topics for special Cases

Now begin to initialize system

Standard input/output/error device setting........

Now begin to test key chips

Press Ctrl+B to enter Main Menu... 3

Step 4 Enter a password and enter the main menu.

Menu(bootload ver: 216.00)

1. Boot with default mode

Download file to SDRAM through ethernet interface and boot

Be sure to select 3 to modify boot parameters before downloading!

'-' = go to previous field;

gateway inet (g)

1. Download file to SDRAM through ethernet interface and boot

Menu(bootload ver: 216.00)

1. Boot with default mode

the boot file

Enter your choice(1-7): 1

the boot file

Enter your choice(1-7): 1

the boot file

Enter your choice(1-7):7

Menu(bootload ver: 216.00)