Operation Manual – Device Management
H3C S9500 Series Routing Switches Table of Contents
i
Table of Contents
Chapter 1 Device Management....................................................................................................1-1
1.1 Device Management Overview..........................................................................................1-1
1.2 Configuring Device Management......................................................................................1-1
1.2.1 Rebooting a Device.................................................................................................1-1
1.2.2 Specifying a Boot ROM File for the Next Device Boot............................................1-2
1.2.3 Upgrading Boot ROM..............................................................................................1-3
1.2.4 Configuring a Detection Interval..............................................................................1-3
1.2.5 Configuring Temperature Alarm Thresholds for a Board........................................1-4
1.2.6 Configuring the Load Mode for the Active Main Board and Standby Main Board...........1-4
1.2.7 Clearing the 16-bit Interface Indexes Not Used in the Current System..................1-5
1.3 Displaying and Maintaining Device Management Configuration.......................................1-6
1.4 Device Management Configuration Example (Remote Upgrade).....................................1-6
Operation Manual – Device Management
H3C S9500 Series Routing Switches Chapter 1 Device Management
1-1
Chapter 1 Device Management
Note:
File names in this document comply with the following rules:
z Path + file name (namely, a full file name): File on a specified path. A full file name
consists of 1 to 135 characters.
z “File name” (namely, only a file name without a path): File on the current working
path. The file name without a path consists of 1 to 91 characters.
When configuring device management, go to these sections for information you are
interested in:
z Device Management Overview
z Configuring Device Management
z Displaying and Maintaining Device Management Configuration
z Device Management Configuration Example
1.1 Device Management Overview
Through the device management function, you can view the current working state of a
device, configure running parameters, and perform daily device maintenance and
management.
Currently, the following device management functions are available:
z Rebooting a device
z Rebooting a device at a specified time
z Specifying a Boot ROM file for the next device reboot
z Upgrading a Boot ROM file
z Configuring temperature alarm thresholds for a board
z Clearing the 16-bit Interface Indexes Not Used in the Current System
1.2 Configuring Device Management
1.2.1 Rebooting a Device
In some cases, you need to reboot the device; for example, after upgrading the Boot
ROM, you can reboot the device to make it take effect. This operation is equal to
powering on the device after powering it off. It is mainly used to reboot a device in
remote maintenance, without performing hardware reboot of the device. You can set a
Operation Manual – Device Management
H3C S9500 Series Routing Switches Chapter 1 Device Management
1-2
time at which the device can automatically reboot. You can also set a delay so that the
device can automatically reboot in the delay.
Follow these steps to reboot a device:
To do… Use the command… Remarks
Reboot a board or the
whole system
reboot [ slot slot-number ]
Optional
Available in user view.
Enable the scheduled
reboot function and specify
a specific reboot time and
date
schedule reboot at
hh:mm [ date ]
Enable the scheduled
reboot function and specify
a reboot waiting time
schedule reboot delay
{ hh:mm | mm }
Optional
The scheduled reboot
function is disabled by
default.
Available in user view.
Caution:
z The precision of the rebooting timer is 1 minute. One minute before the rebooting
time, the device will prompt a specific reboot time and date and will reboot one
minute after this reboot time.
z The execution of the schedule reboot at, and schedule reboot delay commands
can reboot a device. As a result, the ongoing services will be interrupted. Be careful
to use these commands.
z The execution of the reboot command may reboot the whole system, resulting in
the interruption of the ongoing services. Be careful to use the command. For the
details of the reboot command, refer to Device Management Commands.
z If a primary boot file fails or does not exist, the device cannot be rebooted with this
command. In this case, you can re-specify a primary boot file to reboot the device, or
you can power off the device then power it on and the system automatically uses the
secondary boot file to restart the device.
z If you are performing file operations when the device is to be rebooted, the system
removes the reboot operation for the sake of security.
1.2.2 Specifying a Boot ROM File for the Next Device Boot
A Boot ROM file is an application file used to boot the device. When multiple Boot ROM
files are available on the storage device, you can specify a file for the next device boot
by executing the following command.
Operation Manual – Device Management
H3C S9500 Series Routing Switches Chapter 1 Device Management
1-3
Follow these steps to specify a file for the next device boot:
To do… Use the command… Remarks
Specify a Boot ROM file
on a board
boot-loader file file-url
slot slot-number { main |
backup }
Required
Available in user view.
Caution:
The file for the next device boot must be saved under the root directory of the device
(for a device supporting storage device partition, the file must be saved on the first
partition). You can copy or move a file to change the path of it to the root directory.
1.2.3 Upgrading Boot ROM
During the operation of the device, you can use Boot ROM in the storage device to
upgrade those that are running on the device.
Follow these steps to upgrade Boot ROM:
To do… Use the command… Remarks
Upgrade the Boot ROM
program on a board(s)
bootrom update file
file-url slot
slot-number-list
Required
Available in user view
Note:
Restart the device to validate the upgraded Boot ROM.
1.2.4 Configuring a Detection Interval
When detecting an exception on a port, the operation, administration and maintenance
(OAM) module will automatically shut down the port. The device will detect the status of
the port when a detection interval elapses. If the port is still shut down, the device will
recover it.
If you change the detection interval at t to T1, the interval from t to the time when the
previous detection starts is T.
z If T1<T, the interface which is down will be brought up immediately at t;
z If T1>=T, the interface which is down will be brought up after T1-T time.
Operation Manual – Device Management
H3C S9500 Series Routing Switches Chapter 1 Device Management
1-4
Follow these steps to configure a detection interval:
To do… Use the command… Remarks
Enter system view
system-view
—
Configure a detection
interval
shutdown-interval time
Optional
30 seconds by default.
1.2.5 Configuring Temperature Alarm Thresholds for a Board
You can set temperature alarm thresholds for a board by using the following command.
When the temperature of a board exceeds the threshold, the device will generate alarm
signals.
Follow these steps to configure temperature alarm thresholds for a board:
To do… Use the command… Remarks
Enter system view
system-view
—
Configure temperature
alarm thresholds for a
board
temperature-limit
slot-number lower-value
upper-value
Optional
The lower value is 10 and
the upper level is 70 by
default.
1.2.6 Configuring the Load Mode for the Active Main Board and Standby Main
Board
Two load modes are available between active main board (AMB) and standby main
board (SMB) of a device: load sharing (BALANCE) and active/standby mode (SINGLE).
You can use the xbar command to configure the load mode for a board.
Follow these steps to configure the load mode for the AMB and SMB:
To do… Use the command… Remarks
Enter system view
system-view
—
Configure the load mode
for the AMB and SMB
xbar { load-balance |
load-single }
Optional
The AMB and SMB work
in the active/standby
mode by default.
Operation Manual – Device Management
H3C S9500 Series Routing Switches Chapter 1 Device Management
1-5
Caution:
Only when both the AMB and the SMB are in the slot can the load sharing mode be
valid; otherwise, even if the load sharing mode is configured the active board will
automatically switch to the active/standby mode.
1.2.7 Clearing the 16-bit Interface Indexes Not Used in the Current System
In practical networks, the network management software requires the device to provide
a uniform, stable 16-bit interface index. That is, a one-to-one relationship should be
kept between the interface name and the interface index in the same device.
For the purpose of the stability of an interface index, the system will save the 16-bit
interface index when a board or logical interface is removed.
If you repeatedly insert and remove different subboards or interface boards to create or
delete a large amount of logical interface, the interface indexes will be used up, which
will result in interface creation failures. To avoid such a case, you can clear all 16bit
interface indexes saved but not used in the current system in user view.
After the above operation,
z For a re-created interface, the new interface index may not be consistent with the
original one.
z For existing interfaces, their interface indexes remain unchanged.
Follow the step below to clear the 16bit interface indexes not used in the current
system:
To do… Use the command… Remarks
Clear the 16-bit interface indexes saved
but not used in the current system
reset unused porttag
Required
Caution:
A confirmation is required when you execute this command. If you fail to make a
confirmation within 30 seconds or enter “N” to cancel the operation, the command will
not be executed.
Operation Manual – Device Management
H3C S9500 Series Routing Switches Chapter 1 Device Management
1-6
1.3 Displaying and Maintaining Device Management
Configuration
To do… Use the command… Remarks
Display the Boot ROM file
used for the next boot
display boot-loader [ slot
slot-number ]
Available in any
view
Display the statistics of
the CPU usage
display cpu-usage [ number
[ [ offset ] [ verbose ] [ slave |
slot slot-number ]
[ from-device ] ] | slave | slot
slot-number ]
Available in any
view
Display information about
a specified device on the
switch
display device [ cf-card]
[ [ shelf shelf-number ] [ frame
frame-number ] [ slot
slot-number [ subslot
subslot-number ] ] | verbose ]
Available in any
view
Display manufacture
information of the device
display device manuinfo [ slot
slot-number ]
Available in any
view
Display the temperature
information of devices
display environment
Available in any
view
Display the operating
state of fans in a device
display fan [ fan-id ]
Available in any
view
Display the usage of the
memory of a device
display memory [ slave | slot
slot-number ]
Available in any
view
Display the power state of
a device
display power [ power-id ]
Available in any
view
Display the reboot time of
a device
display schedule reboot
Available in any
view
Display the load mode of
the current AMB and SMB
display xbar
Available in any
view
1.4 Device Management Configuration Example (Remote
Upgrade)
I. Network requirements
z Switch A serves as the FTP Client. The aaa.app program and the boot.app
program are both saved under the aaa directory of the FTP Server.
z The IP address of Vlan-interface 2 on Switch A is 1.1.1.1/24, the IP address of the
FTP Server is 2.2.2.2/24, and the IP address of User is 3.3.3.3/24.
z A route exists between the FTP server, Switch A and User.
Operation Manual – Device Management
H3C S9500 Series Routing Switches Chapter 1 Device Management
1-7
z User can log in to Switch A via Telnet to perform operations on Switch A (that is,
download the application program from FTP Server and remotely upgrade Switch
A through command lines).
II. Network diagram
FTP Client
FTP Server
User
Telnet
Switch A
Vlan-interface2
1.1.1.1/24
2.2.2.2/24
Internet
3.3.3.3/24
Figure 1-1 Network diagram for remote upgrade
III. Configuration procedure
1) Configure the IP address of each device and a route between FTP server and
Switch A, Switch A and User.
Configure the IP address of each device as shown in
Figure 1-1.
Configure a route between FTP server and Switch A, Switch A and User. The
configuration procedure is omitted here.
2) Configure the username and password on the FTP server.
# Set the FTP username to aaa and password to hello and configure the user to have
access to the aaa directory. The configuration procedure is omitted here.
3) Telnet from User to Switch A.
Perform the operation as needed. The procedure is omitted.
4) Configuration on Switch A
Caution:
If the size of the Flash on the device is not large enough, delete the original application
programs from the Flash before downloading.
Operation Manual – Device Management
H3C S9500 Series Routing Switches Chapter 1 Device Management
1-8
# Enter the following command in user view to log in to FTP Server after telnetting to
Switch A.
<Sysname> ftp 2.2.2.2
Trying ...
Press CTRL+K to abort
Connected.
220 WFTPD 2.0 service (by Texas Imperial Software) ready for new user
User(none): aaa
331 Give me your password, please
Password:
230 Logged in successfully
[ftp]
# Download the aaa.app and boot.app programs on FTP Server to the Flash of Switch
A.
[ftp] get aaa.app
[ftp] get boot.app
# Terminate the FTP connection and return to user view.
[ftp] quit
<Sysname>
# Upgrade the Boot ROM file of the SRPU.
<Sysname> bootrom update file boot.app slot 0
# Specify the application program for the next boot on SRPU 0.
<Sysname> boot-loader file aaa.app slot 0 main
# Reboot the device. The application program is upgraded now.
<Sysname> reboot
/