Login
| Title | Size | Downloads |
|---|---|---|
| H3C S5120-SI Series Ethernet Switches Command Reference-Release 1101-6W105-Device Management Commands.pdf | 134.31 KB |
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 28-Device Management Commands | 134.31 KB |
Device Management Commands
boot-loader
Syntax
boot-loader file file-url { main | backup }
View
User view
Default Level
2: System level
Parameters
file file-url: Specifies a file name, a string of 1 to 63 characters, If you enter a relative path here, the system automatically converts it to an absolute path. The absolute path should contain no more than 63 characters; otherwise, the command cannot be successfully executed. The file name is in the format of [drive:/]file-name, where
l The items in square brackets [ ] are optional.
l drive specifies the storage medium of the file. The value is the name of the storage medium. If a device has only one storage medium, you can execute this command without providing this argument.
l file-name specifies the filename, which is usually suffixed by .bin. Suffixes vary with devices.
main: Specifies a file as a main boot file. A main boot file is used to boot a device.
backup: Specifies a file as a backup boot file. A backup boot file is used to boot a device only when a main boot file is unavailable.
Description
Use the boot-loader command to specify a boot file for the next boot.
Related commands: display boot-loader.
Examples
# Specify the main boot file for the next device boot as test.bin. (The output of this command varies with devices.)
<Sysname> boot-loader file test.bin main
This command will set the boot file. Continue? [Y/N]:y
The specified file will be used as the main boot file at the next reboot on sl
ot 1!
bootrom
Syntax
bootrom update file file-url
View
User view
Default Level
2: System level
Parameters
update file file-url: Upgrades Boot ROM, where file-url is a string of 1 to 63 characters and represents name of the file to be upgraded. See boot-loader.
Description
Use the bootrom command to upgrade the Boot ROM program on a device(s).
Examples
# Read the Boot ROM program.
<Sysname> bootrom update file a.btm
This command will update bootrom file, Continue? [Y/N]:y
Now updating bootrom, please wait...
BootRom file updating finished!
bootrom-update security-check enable
Syntax
bootrom-update security-check enable
undo bootrom-update security-check enable
View
System view
Default Level
2: System level
Parameters
None
Description
Use the bootrom-update security-check enable command to enable the validity check function.
Use the undo bootrom-update security-check enable command to disable the validity check function.
By default, the validity check function is enabled at the time of upgrading Boot ROM.
After the validity check function is enabled, the device will strictly check whether the Boot ROM upgrade files are valid and can match the hardware.
Examples
# Enable the validity check function when upgrading Boot ROM.
<Sysname> system-view
[Sysname] bootrom-update security-check enable
display boot-loader
Syntax
display boot-loader
View
Any view
Default Level
2: System level
Parameters
None
Description
Use the display boot-loader command to display information of the boot file.
Related commands: boot-loader.
Examples
# Display the file adopted for the current and next boot of the device. (The output of this command varies with devices.)
<Sysname> display boot-loader
The current boot app is: flash:/test.bin
The main boot app is: flash:/test.bin
The backup boot app is: flash:/test.bin
Table 1-1 display boot-loader command output description
|
Field |
Description |
|
The current boot app is |
Boot file used for the device for the current device boot |
|
The main boot app is |
Main boot file used for the next device boot of the device |
|
The backup boot app is |
Backup boot file used for the next device boot of the device |
display cpu-usage
Syntax
display cpu-usage [ number [ offset ] [ verbose ] [ from-device ] ]
View
Any view
Default Level
1: Monitor level
Parameters
entry-number: Number of entries to be displayed, in the range of 1 to 60.
offset: Offset between the serial number of the first CPU usage statistics record to be displayed and that of the last CPU usage record to be displayed. It is in the range of 0 to 59. For example, the idx of the latest statistics record is 12, if the offset is set to 3, the system will display the statistics records from the one with the idx of 9. idx represents the serial number of the period for the statistics, and its value ranges from 0 to 60 cyclically. The system makes CPU usage statistics periodically; after each period, the system records the average CPU usage during this period, and the idx value is added by 1 automatically.
verbose: Specifies to display detailed information of CPU usage statistics. If this keyword is not provided, the system displays the brief information of the CPU usage statistics; if this keyword is provided, the system displays the average CPU usage statistics for each task in the specified period.
from-device: Displays external storage media such as flash and hard disk. The device currently does not support the from-device keyword.
Description
Use the display cpu-usage command to display the CPU usage statistics.
The system takes statistics of CPU usage at intervals (usually every 60 seconds) and saves the statistical results in the history record area. The maximum number of records that can be saved depends on the device model. display cpu-usage entry-number indicates the system displays entry-number records from the newest (last) record. display cpu-usage entry-number offset indicates the system displays number records from the last but offset record.
Equivalent to the display cpu-usage 1 0 verbose command, the display cpu-usage command displays detailed information of the last CPU usage statistics record.
Examples
# Display information of the current CPU usage statistics.
<Sysname> display cpu-usage
Unit CPU usage:
1% in last 5 seconds
1% in last 1 minute
1% in last 5 minutes
# Display the last fifth and sixth records of the CPU usage statistics history.
<Sysname> display cpu-usage 2 4
===== CPU usage info (no: 0 idx: 58) =====
CPU Usage Stat. Cycle: 60 (Second)
CPU Usage : 3%
CPU Usage Stat. Time : 2006-07-10 10:56:55
CPU Usage Stat. Tick : 0x1d9d(CPU Tick High) 0x3a659a70(CPU Tick Low)
Actual Stat. Cycle : 0x0(CPU Tick High) 0x95030517(CPU Tick Low)
===== CPU usage info (no: 1 idx: 57) =====
CPU Usage Stat. Cycle: 60 (Second)
CPU Usage : 3%
CPU Usage Stat. Time : 2006-07-10 10:55:55
CPU Usage Stat. Tick : 0x1d9c(CPU Tick High) 0xa50e5351(CPU Tick Low)
Actual Stat. Cycle : 0x0(CPU Tick High) 0x950906af(CPU Tick Low)
Table 1-2 display cpu-usage command output description
|
Field |
Description |
|
Unit CPU usage |
CPU usage statistics |
|
1% in last 5 seconds |
After the device boots, the system calculates and records the average CPU usage in every five seconds. This field displays the average CPU usage in the last five seconds. |
|
1% in last 1 minute |
After the device boots, the system calculates and records the average CPU usage in every one minute. This field displays the average CPU usage in the last minute. |
|
1% in last 5 minutes |
After the device boots, the system calculates and records the average CPU usage in every five minutes. This field displays the average CPU usage in the last five minutes. |
|
CPU usage info (no: idx:) |
Information of CPU usage records (no: The (no+1)th record is currently displayed. no numbers from 0, a smaller number equals a newer record. idx: index of the current record in the history record table). If only the information of the current record is displayed, no and idx are not displayed. |
|
CPU Usage Stat. Cycle |
CPU usage measurement interval, in seconds. For example, if the value is 41, it indicates that the average CPU usage during the last 41 seconds is calculated. The value range of this field is 1 to 60. |
|
CPU Usage |
Average CPU usage in a measurement interval, in percentage |
|
CPU Usage Stat. Time |
CPU usage statistics time in seconds, that is, the system time when the command is executed |
|
CPU Usage Stat. Tick |
System runtime in ticks, represented by a 64-bit hexadecimal. CPU Tick High represents the most significant 32 bits and the CPU Tick Low the least significant 32 bits. |
|
Actual Stat. Cycle |
Actual CPU usage measurement interval in ticks, represented by a 64-bit hexadecimal. CPU Tick High represents the most significant 32 bits and the CPU Tick Low the least significant 32 bits. Owing to the precision of less than one second, the actual measurement periods of different CPU usage records may differ slightly. |
display cpu-usage history
Syntax
display cpu-usage history [ task task-id ]
View
Any view
Default Level
1: Monitor level
Parameters
task task-id: Displays the history statistics of the CPU usage of the specified task, where task-id represents the task number. If the task-id argument is not provided, the system displays the history statistics of the CPU usage of the entire system (the CPU usage of the entire system is the sum of CPU usages of all tasks).
Description
Use the display cpu-usage history command to display the history statistics of the CPU usage in a chart.
If no argument is provided, the system displays the CPU usage of the whole system.
The system takes statistics of the CPU usage at an interval and saves the statistical results in the history record area. You can use the display cpu-usage history command to display the CPU usage statistics records in the last 60 minutes. The statistical results are displayed through geographical coordinates. In the output information:
l Latitude indicates the CPU usage, which is displayed based on the step. For example, if the step of the CPU usage is 5%, then the actual statistics value 53% is displayed as 55%, and actual statistics value 52% is displayed as 50%.
l Longitude indicates the time.
l Consecutive pond marks (#) indicate the CPU usage at a certain moment. The value of the latitude corresponding to the # mark on the top of a moment is the CPU usage at this moment.
Examples
# Display the CPU usage statistics of the whole system.
<Sysname> display cpu-usage history
100%|
95%|
90%|
85%|
80%|
75%|
70%|
65%|
60%|
55%|
50%|
45%|
40%|
35%|
30%|
25%|
20%|
15%| #
10%| ### #
5%| ########
------------------------------------------------------------
10 20 30 40 50 60 (minutes)
cpu-usage last 60 minutes(SYSTEM)
The above output information indicates the CPU usage of the whole system in the last 60 minutes: 5% in the twelfth minute, 10% in the thirteenth minute, 15% in the fourteenth minute, 10% in the fifteenth minute, 5% in the sixteenth and seventeenth minute, 10% in the eighteenth minute, 5% in the nineteenth minute, and 2% or lower than 2% at other times.
# Display the CPU usage statistics of task 6.
<Sysname> display cpu-usage history task 6
100%|
95%|
90%|
85%|
80%|
75%|
70%|
65%|
60%|
55%|
50%|
45%|
40%|
35%|
30%|
25%|
20%|
15%|
10%|
5%| #
------------------------------------------------------------
10 20 30 40 50 60 (minutes)
cpu-usage last 60 minutes(T03M)
The above output information indicates the CPU usage of task 6 (with the task name T03M) in the last 60 minutes: 5% in the twentieth minute, and 2% or lower than 2% at other times.
display device
Syntax
display device [verbose ]
View
Any view
Default Level
2: System level
Parameters
verbose: Displays detailed information.
Description
Use the display device command to display information about the device.
Examples
# Display information of the device. (The output of this command varies with devices.)
<Sysname> display device
SubSNo PortNum PCBVer FPGAVer CPLDVer BootRomVer AddrLM Type State
0 52 Ver.B NULL 001 119 IVL LS51LTSS Normal
Table 1-3 display device command output description
|
Field |
Description |
|
SubSNo |
Number of the slot in which the subcard resides |
|
PortNum |
Maximum number of ports that a subcard supports |
|
AddrLM |
Address learning mode |
|
Brd Status |
Card status, which can be the following values: l Absent: No card is in the slot. l Fault: Error occurred, and the card cannot start normally. l Normal: The card is an interface card and functions normally. |
display device manuinfo
Syntax
display device manuinfo
View
Any view
Default Level
3: Manage level
Parameters
None
Description
Use the display device manuinfo command to display electrical label information about the device.
Electrical label information is also called permanent configuration data or archive information, which is written to the storage medium of the device during debugging or test of a device. The information includes name of the device serial number, and vendor name. This command displays part of the electrical label information of the device.
Examples
# Display electrical label information. (The output of this command varies with devices.)
DEVICE_NAME : S5120-28P-SI
DEVICE_SERIAL_NUMBER : DPPMWWB123456
MAC_ADDRESS : 000F-E26A-58EA
MANUFACTURING_DATE : 2007-11-10
VENDOR_NAME : H3C
Table 1-4 display device manuinfo command output description
|
Field |
Description |
|
DEVICE_NAME |
Device name |
|
DEVICE_SERIAL_NUMBER |
Device serial number |
|
MAC_ADDRESS |
MAC address of the device |
|
MANUFACTURING_DATE |
Manufacturing date of the device |
|
VENDOR_NAME |
Vendor name |
display environment
Syntax
display environment
View
Any view
Default Level
1: Monitor level
Parameters
None
Description
Use the display environment command to display the temperature information, including the current temperature and temperature thresholds.
Examples
# Display the temperature information of the device.
<Sysname> display environment
System temperature information (degree centigrade):
-------------------------------------------------------------------------------
Sensor Temperature LowerLimit WarningLimit AlarmLimit ShutdownLimit
hotspot 1 45 NA 85 95 NA
display fan
Syntax
display fan [ fan-id ]
View
Any view
Default Level
1: Monitor level
Parameters
fan-id: Displays the operating state of the specified fan, where fan-id represents the built-in fan number.
Description
Use the display fan command to display the operating state of built-in fans.
Examples
# Display the operating state of all fans in a device.
<Sysname> display fan
Fan 1 State: Normal
display memory
Syntax
display memory
View
Any view
Default Level
1: Monitor level
Parameters
None
Description
Use the display memory command to display the usage of the memory of a device.
Examples
# Display the usage of the memory of a device.
<Sysname> display memory
System Total Memory(bytes): 83947760
Total Used Memory(bytes): 24881784
Used Rate: 16%
Table 1-5 display memory command output description
|
Field |
Description |
|
System Total Memory(bytes) |
Total size of the system memory (in bytes) |
|
Total Used Memory(bytes) |
Size of the memory used (in bytes) |
|
Used Rate |
Percentage of the memory used to the total memory |
display power
Syntax
display power [ power-id ]
View
Any view
Default Level
1: Monitor level
Parameters
None
Description
Use the display power command to display the PSU information of a device.
Examples
# Display the PSU information of the device.
<Sysname> display power
Power 0 State: Normal
Table 1-6 display power command output description
|
Field |
Description |
|
Power |
PSU number |
|
State |
PSU state: l Normal l Absent l Fault |
display reboot-type
Syntax
display reboot-type
View
Any view
Default Level
2: System level
Parameters
None
Description
Use the display reboot-type command to display the reboot mode of the device.
Examples
# Display the reboot mode of the device.
<Sysname> display reboot-type
The rebooting type this time is: Cold
The above information indicates that the last reboot mode of the device is Cold boot (cold boot is to restart a device by powering it on). (The display of Warm represents a warm boot, which means to restart a device by using the commands like reboot).
display schedule job
Syntax
display schedule job
View
Any view
Default Level
1: Monitor level
Parameters
None
Description
Use the display schedule job command to display the detailed configurations of the scheduled automatic execution function.
Examples
# Display the detailed configurations of the current scheduled automatic execution function.
<Sysname> display schedule job
Specified command: execute 1.bat
Specified view: system view
Executed time: at 12:00 10/31/2007 (in 0 hours and 16 minutes)
If you modify the system time within 16 minutes, the configurations of scheduled automatic execution of the batch file will become invalid, and then when you execute the display schedule job command again, the system displays nothing.
display schedule reboot
Syntax
display schedule reboot
View
Any view
Default Level
3: Manage level
Parameters
None
Description
Use the display schedule reboot command to display the device reboot time set by the user.
Related commands: schedule reboot at and schedule reboot delay.
Examples
# Display the reboot time of a device.
<Sysname> display schedule reboot
System will reboot at 16:00:00 03/10/2006 (in 2 hours and 5 minutes).
The above information indicates the system will reboot at 16:00:00 on March 10, 2006 (in two hours and five minutes).
display system-failure
Syntax
display system-failure
View
Any view
Default Level
3: Manage level
Parameters
None
Description
Use the display system-failure command to display the exception handling method.
Related commands: system-failure.
Examples
# Display the exception handling method.
<Sysname> display system-failure
System failure handling method: reboot
display transceiver alarm
Syntax
display transceiver alarm interface [ interface-type interface-number ]
View
Any view
Default Level
2: System level
Parameters
interface [ interface-type interface-number ]: Displays the current alarm information of the pluggable transceiver plugged in the specified interface. interface-type interface-number represents interface type and interface number. If it is not specified, the command displays the current alarm information of the pluggable transceiver in all the interfaces.
Description
Use the display transceiver alarm command to display the current alarm information of a single or all transceivers.
If no error occurs, None is displayed.
Table 1-7 shows the alarm information that may occur for the four types of commonly used transceivers.
Table 1-7 display transceiver alarm command output description
|
Field |
Remarks |
|
GBIC/SFP |
|
|
RX loss of signal |
Incoming (RX) signal is lost. |
|
RX power high |
Incoming (RX) power level is high. |
|
RX power low |
Incoming (RX) power level is low. |
|
TX fault |
Transmit (TX) fault |
|
TX bias high |
TX bias current is high. |
|
TX bias low |
TX bias current is low. |
|
TX power high |
TX power is high. |
|
TX power low |
TX power is low. |
|
Temp high |
Temperature is high. |
|
Temp low |
Temperature is low. |
|
Voltage high |
Voltage is high. |
|
Voltage low |
Voltage is low. |
|
Transceiver info I/O error |
Transceiver information read and write error |
|
Transceiver info checksum error |
Transceiver information checksum error |
|
Transceiver type and port configuration mismatch |
Transceiver type does not match port configuration. |
|
Transceiver type not supported by port hardware |
Transceiver type is not supported on the port. |
|
XFP |
|
|
RX loss of signal |
Incoming (RX) signal is lost. |
|
RX not ready |
RX is not ready |
|
RX CDR loss of lock |
RX clock cannot be recovered. |
|
RX power high |
RX power is high. |
|
RX power low |
RX power is low. |
|
TX not ready |
TX is not ready. |
|
TX fault |
TX fault |
|
TX CDR loss of lock |
TX clock cannot be recovered. |
|
TX bias high |
TX bias current is high. |
|
TX bias low |
TX bias current is low. |
|
TX power high |
TX power is high. |
|
TX power low |
TX power is low. |
|
Module not ready |
Module is not ready. |
|
APD supply fault |
APD (Avalanche Photo Diode) supply fault |
|
TEC fault |
TEC (Thermoelectric Cooler) fault |
|
Wavelength unlocked |
Wavelength of optical signal exceeds the manufacturer’s tolerance. |
|
Temp high |
Temperature is high. |
|
Temp low |
Temperature is low. |
|
Voltage high |
Voltage is high. |
|
Voltage low |
Voltage is low. |
|
Transceiver info I/O error |
Transceiver information read and write error |
|
Transceiver info checksum error |
Transceiver information checksum error |
|
Transceiver type and port configuration mismatch |
Transceiver type does not match port configuration. |
|
Transceiver type not supported by port hardware |
Transceiver type is not supported on the port. |
|
XENPAK |
|
|
WIS local fault |
WIS (WAN Interface Sublayer) local fault |
|
Receive optical power fault |
Receive optical power fault |
|
PMA/PMD receiver local fault |
PMA/PMD (Physical Medium Attachment/Physical Medium Dependent) receiver local fault |
|
PCS receive local fault |
PCS (Physical Coding Sublayer) receiver local fault |
|
PHY XS receive local fault |
PHY XS (PHY Extended Sublayer) receive local fault |
|
RX power high |
RX power is high. |
|
RX power low |
RX power is low. |
|
Laser bias current fault |
Laser bias current fault |
|
Laser temperature fault |
Laser temperature fault |
|
Laser output power fault |
Laser output power fault |
|
TX fault |
TX fault |
|
PMA/PMD receiver local fault |
PMA/PMD receiver local fault |
|
PCS receive local fault |
PCS receive local fault |
|
PHY XS receive local fault |
PHY XS receive local fault |
|
TX bias high |
TX bias current is high. |
|
TX bias low |
TX bias current is low. |
|
TX power high |
TX power is high. |
|
TX power low |
TX power is low. |
|
Temp high |
Temperature is high. |
|
Temp low |
Temperature is low. |
|
Transceiver info I/O error |
Transceiver information read and write error |
|
Transceiver info checksum error |
Transceiver information checksum error |
|
Transceiver type and port configuration mismatch |
Transceiver type does not match port configuration. |
|
Transceiver type not supported by port hardware |
Transceiver type is not supported on the port. |
Examples
# Display the alarm information of the pluggable transceiver plugged in interface GigabitEthernet1/0/25. (The output of this command varies with devices.)
<Sysname> display transceiver alarm interface GigabitEthernet1/0/25
GigabitEthernet1/0/25 transceiver current alarm information:
RX loss of signal
RX power low
Table 1-8 display transceiver alarm command output description
|
Field |
Description |
|
transceiver current alarm information |
Current alarm information of the transceiver |
|
RX loss of signal |
Incoming (RX) signal is lost. |
|
RX power low |
Incoming (RX) power level is low. |
display transceiver diagnosis
Syntax
display transceiver diagnosis interface [ interface-type interface-number ]
View
Any view
Default Level
2: System level
Parameters
interface [ interface-type interface-number ]: Displays the currently measured value of digital diagnosis parameters of the H3C customized anti-spoofing pluggable optical transceiver plugged in the specified interface. interface-type interface-number represents interface type and interface number. If it is not specified, the command displays the currently measured value of digital diagnosis parameters of H3C customized anti-spoofing pluggable optical transceivers in all the interfaces.
Description
Use the display transceiver diagnosis command to display the currently measured value of digital diagnosis parameters of H3C customized anti-spoofing pluggable optical transceivers.
Examples
# Display the currently measured value of the digital diagnosis parameters of the H3C customized anti-spoofing pluggable optical transceiver plugged in interface GigabitEthernet1/0/25. (The output of this command varies with devices.)
<Sysname> display transceiver diagnosis interface GigabitEthernet1/0/25
GigabitEthernet1/0/25 transceiver diagnostic information:
Current diagnostic parameters:
Temp(°C) Voltage(V) Bias(mA) RX power(dBM) TX power(dBM)
36 3.31 6.13 -35.64 -5.19
Table 1-9 display transceiver diagnosis command output description
|
Field |
Description |
|
transceiver diagnostic information |
Digital diagnosis information of the transceiver plugged in the interface |
|
Current diagnostic parameters |
Current diagnostic parameters |
|
Temp.(°C) |
Digital diagnosis parameter-temperature, in °C, with the precision to 1°C. |
|
Voltage(V) |
Digital diagnosis parameter-voltage, in V, with the precision to 0.01 V. |
|
Bias(mA) |
Digital diagnosis parameter-bias current, in mA, with the precision to 0.01 mA. |
|
RX power(dBM) |
Digital diagnosis parameter-RX power, in dBM, with the precision to 0.01 dBM. |
|
TX power(dBM) |
Digital diagnosis parameter-TX power, in dBM, with the precision to 0.01 dBM. |
display transceiver
Syntax
display transceiver interface [ interface-type interface-number ]
View
Any view
Default Level
2: System level
Parameters
interface [ interface-type interface-number ]: Displays main parameters of the pluggable transceiver plugged in the specified interface. interface-type interface-number represents interface type and interface number. If it is not specified, the command displays main parameters of the pluggable transceiver(s) in all the interfaces.
Description
Use the display transceiver command to display main parameters of a single or all pluggable transceivers.
Examples
# Display main parameters of the pluggable transceiver plugged in interface GigabitEthernet1/0/25. (The output of this command varies with devices.)
<Sysname> display transceiver interface GigabitEthernet1/0/25
GigabitEthernet1/0/25 transceiver information:
Transceiver Type : 1000_BASE_SX_SFP
Connector Type : LC
Wavelength(nm) : 850
Transfer Distance(m) : 550(50um),270(62.5um)
Digital Diagnostic Monitoring : YES
Vendor Name : H3C
Ordering Name : SFP-GE-SX-MM850
Table 1-10 display transceiver command output description
|
Field |
Description |
|
transceiver information |
Pluggable transceiver information |
|
Transceiver Type |
Pluggable transceiver type |
|
Connector Type |
Type of the connectors of the transceiver: l Optical connectors, including SC (SC connector, developed by NTT) and LC (LC connector, 1.25 mm/RJ-45 optical connector developed by Lucent). l Other connectors, including RJ-45 and CX 4. |
|
Wavelength(nm) |
l Optical transceiver: central wavelength of the laser sent, in nm. If the transceiver supports multiple wavelengths, every two wavelength values are separated by a comma. l Electrical transceiver: displayed as N/A. |
|
Transfer distance(xx) |
Transfer distance, with xx representing km for single-mode transceivers and m for other transceivers. If the transceiver supports multiple transfer medium, every two values of the transfer distance are separated by a comma. The corresponding transfer medium is included in the bracket following the transfer distance value. The following are the transfer media: l 9 um: 9/125 um single-mode fiber l 50 um: 50/125 um multi-mode fiber l 62.5 um: 62.5/125 um multi-mode fiber l TP: Twisted pair l CX4: CX4 cable |
|
Digital Diagnostic Monitoring |
Whether the digital diagnosis function is supported, where: l YES: supported l NO: not supported |
|
Vendor Name |
Vendor name or name of the vendor who customizes the transceiver: l H3C customized anti-spoofing transceiver: H3C is displayed. l Other transceivers: The vendor name is displayed. |
|
Ordering Name |
Pluggable transceiver model |
display transceiver manuinfo
Syntax
display transceiver manuinfo interface [ interface-type interface-number ]
View
Any view
Default Level
2: System level
Parameters
interface [ interface-type interface-number ]: Displays part of the electrical label information of the H3C customized anti-spoofing pluggable transceiver plugged in the specified interface. interface-type interface-number represents interface type and interface number. If it is not specified, the command displays part of the electrical label information of the H3C customized anti-spoofing pluggable transceiver(s) in all the interfaces.
Description
Use the display transceiver manuinfo command to display part of the electrical label information of a single or all H3C customized anti-spoofing pluggable transceivers.
Examples
# Display the electrical label information of the H3C customized anti-spoofing pluggable transceiver plugged in interface GigabitEthernet1/0/25. (The output of this command varies with devices.)
<Sysname> display transceiver manuinfo interface GigabitEthernet1/0/25
GigabitEthernet1/0/25 transceiver manufacture information:
Manu. Serial Number : 213410A0000054000251
Manufacturing Date : 2006-09-01
Vendor Name : H3C
Table 1-11 display transceiver manuinfo command output description
|
Field |
Description |
|
Manu. Serial Number |
Serial number generated during debugging and testing of the customized transceivers |
|
Manufacturing Date |
Debugging and testing date. The date takes the value of the system clock of the computer that performs debugging and testing. |
|
Vendor Name |
Name of the vendor who customizes the transceiver, that is, H3C. |
reboot
Syntax
reboot
View
User view
Default Level
2: System level
Parameters
None
Description
Use the reboot command to reboot the device.
l Device reboot may result in the interruption of the ongoing services. Use these commands with caution.
l If a main boot file fails or does not exist, the device cannot be rebooted with the reboot command. In this case, you can re-specify a main boot file to reboot the device, or you can power off the device, then power it on and the system automatically uses the backup boot file to restart the device.
l If you are performing file operations when the device is to be rebooted, the system does not execute the command for the sake of security.
Examples
# If the current configuration does not change, reboot the device.
<Sysname> reboot
Start to check configuration with next startup configuration file, please wait.........DONE!
This command will reboot the device. Continue? [Y/N]:y
Now rebooting, please wait...
# If the current configuration changes, reboot the device.
<Sysname> reboot
Start to check configuration with next startup configuration file, please wait.........DONE!
This command will reboot the device. Current configuration will be lost in next startup if you continue. Continue? [Y/N]:y
Now rebooting, please wait...
reset unused porttag
Syntax
reset unused porttag
View
User view
Default Level
1: Monitor level
Parameters
None
Description
Use the reset unused porttag command to clear the 16-bit index saved but not used in the current system.
Examples
# Clear the 16-bit index saved but not used in the current system.
<Sysname> reset unused porttag
Current operation will delete all unused port tag(s). Continue? [Y/N]:y
<Sysname>
schedule job
Syntax
schedule job { at time1 [ date ] | delay time2 } view view command
undo schedule job
View
User view
Default Level
3: Manage level
Parameters
at time1 [ date ]: Specifies the execution time of a specified command.
l time1: Execution time of the command, in the format of hh:mm (hour/minute). The hh value ranges from 0 to 23, and the mm value ranges from 0 to 59.
l date: Execution date of the command, in the format of MM/DD/YYYY (month/day/year) or YYYY/MM/DD (year/month/day). The YYYY value ranges from 2000 to 2035, the MM value ranges from 1 to 12, and the DD value range depends on a specific month.
delay time2: Specifies the execution waiting time of a specified command. time2 represents the waiting time, which can be in the following format:
l hh:mm (hour/minute): The hh value ranges from 0 to 720, and the mm value ranges from 0 to 59. The value of hh:mm cannot exceed 720:00.
l mm (minute): It ranges from 0 to 432000, with 0 indicating that a command is executed immediately without any delay.
view view: Specifies the view in which a command is executed. view represents the view name, and it takes the following values at present:
l shell, represents user view.
l system, represents system view.
command: The command string to be automatically executed at the scheduled time.
Description
Use the schedule job command to automatically execute a specified command at the scheduled time.
Use the undo schedule job command to remove the configuration.
Note the following:
l If you provide both the time1 and date arguments, the execution time must be a future time.
l If you only provide the time1 argument, when time1 is earlier than the current system time, the specified command is executed at time1 of the next day; when time1 is later than the current system time, the specified command is executed at time1 of the current day.
l No matter whether you use the at or delay keyword, the difference between the execution time of a command and the current system time cannot exceed 720 hours (namely, 30 days).
l At present, you can specify only user view and system view. To automatically execute the specified commands in other views or automatically execute multiple commands at a time, you can configure the system to automatically execute a batch file at a specified time (note that you must provide a complete file path for the system to execute the batch file.).
l The system does not check the view and command arguments. Therefore, ensure the correctness of the command argument (including the correct format of command and the correct relationship between the command and view arguments.).
l After the specified automatic execution time is reached, the system executes the specified commands without displaying any information except system information such as log, trap and debug.
l When the system is executing the specified command, you do not need to input any information. If there is information for you to confirm, the system automatically inputs Y or Yes; if certain characters need to be input, the system automatically inputs a default character string, and inputs an empty character string when there is no default character string.
l For the commands used to switch user interfaces, such as telnet, ftp, and ssh2, the commands used to switch views, such as system-view, quit and interface ethernet, and the commands used to modify status of the user that is executing commands, such as super, the operation interface, command view and status of the current user are not changed after the automatic execution function is performed.
l If you modify the system time after the automatic execution function is configured, the scheduled automatic execution configuration turns invalid automatically.
l Only the latest configuration takes effect if you execute the schedule job command repeatedly.
Examples
# Configure that the device will execute the batch file 1.bat in system view in 60 minutes (supposing that the current time is 11:43).
<Sysname> schedule job delay 60 view system execute 1.bat
Info: Command execute 1.bat in system view will be executed at 12:43 10/31/2007 (in 1 hours and 0 minutes).
# Configure that the device will execute the batch file 1.bat in system view at 12:00 in the current day (supposing that the current time is 11:43).
<Sysname> schedule job at 12:00 view system execute 1.bat
Info: Command execute 1.bat in system view will be executed at 12:00 10/31/2007 (in 0 hours and 16 minutes).
schedule reboot at
Syntax
schedule reboot at hh:mm [ date ]
undo schedule reboot
View
User view
Default Level
3: Manage level
Parameters
hh:mm: Reboot time of a device, in the format of hh:mm (hours:minutes). The value of the hh argument ranges from 0 to 23, and the value of the mm argument ranges from 0 to 59.
date: Reboot date of a device, in the format mm/dd/yyyy (month/day/year) or in the format yyyy/mm/dd (year/month/day) The yyyy value ranges from 2000 to 2035, the mm value ranges from 1 to 12, and the dd value depends on a specific month.
Description
Use the schedule reboot at command to enable the scheduled reboot function and specify a specific reboot time and date.
By default, the scheduled reboot function is disabled.
There are two cases if no specific reboot date is specified:
l When the specified reboot time is later than the current time, the device will be rebooted at the reboot time of the current day.
l When the specified reboot time is earlier than the current time, the device will be rebooted at the reboot time the next day.
l If you are performing file operations when the device is to be rebooted, the system does not execute the command for the sake of security.
Note that:
l The precision of the device timer is 1 minute. One minute before the reboot time, the device will prompt “REBOOT IN ONE MINUTE” and will be rebooted in one minute.
l The difference between the reboot date and the current date cannot exceed 30 x 24 hours (namely, 30 days).
l After you execute the above command, the device will prompt you to confirm the configuration. You must enter Y or y to make the configuration take effect. The original configuration will be overwritten at the same time.
l If a date (month/day/year or year/month/day) later than the current date is specified for the schedule reboot at command, the device will be rebooted at the reboot time.
l If you use the clock command after the schedule reboot at command to adjust the system time, the reboot time set by the schedule reboot at command will become invalid.
This command reboots the device in a future time, thus resulting in service interruption. Please use it with caution.
Examples
# Configure the device to reboot at 12:00 AM (supposing that the current time is 11:43).
<Sysname> schedule reboot at 12:00
Reboot system at 12:00 06/06/2006(in 0 hour(s) and 16 minute(s))
confirm? [Y/N]:
# If you have used the terminal logging command to enable the log display function on the terminal before setting a reboot time, the system will automatically display related log information after you enter <y>. By default, the log display function is enabled.
<Sysname>
%Jun 6 11:43:11:629 2006 Sysname CMD/4/REBOOT:
vty0(192.168.1.54): Set schedule reboot parameters at 11:43:11 06/06/2006, and system will reboot at 12:00 06/06/2006.
schedule reboot delay
Syntax
schedule reboot delay { hh:mm | mm }
undo schedule reboot
View
User view
Default Level
3: Manage level
Parameters
hh:mm: Device reboot wait time, in the format of hh:mm (hours:minutes). The value of the hh argument ranges from 0 to 720, and the value of the mm argument ranges from 0 to 59, and the value of the hh:mm argument cannot exceed 720:00.
mm: Device reboot wait time in minutes, in the range of 0 to 43,200.
Description
Use the schedule reboot delay command to enable the scheduled reboot function and set a reboot wait time.
By default, the scheduled reboot function is disabled.
Note that:
l The reboot wait time can be in the format of hh:mm (hours:minutes) or mm (absolute minutes). The absolute minutes cannot exceed 30 x 24 x 60 minutes, namely, 30 days.
l The precision of the device timer is 1 minute. One minute before the reboot time, the device will prompt “REBOOT IN ONE MINUTE” and will be rebooted in one minute.
l After you execute the above command, the device will prompt you to confirm the configuration. You must enter <Y> or <y> to make the configuration take effect. The original configuration will be overwritten at the same time.
l If you use the clock command after the schedule reboot delay command to adjust the system time, the reboot wait time set by the schedule reboot delay command will become invalid.
l If you are performing file operations when the device is to be rebooted, the system does not execute the command for the sake of security.
This command reboots the device after the specified delay time, thus resulting in service interruption. Please use it with caution.
Examples
# Configure the device to reboot in 88 minutes (supposing the current time is 11:48).
<Sysname> schedule reboot delay 88
Reboot system at 13:16 06/06/2006(in 1 hour(s) and 28 minute(s)). confirm? [Y/N]:
# If you have used the terminal logging command to enable the log display function on the terminal before setting a reboot time, the system will automatically display related log information after you enter y. By default, the log display function is enabled on the terminal.
<Sysname>
%Jun 6 11:48:44:860 2006 Sysname CMD/4/REBOOT:
vty0(192.168.1.54): Set schedule reboot parameters at 11:48:44 06/06/2006, and system will reboot at 13:16 06/06/2006.
system-failure
Syntax
system-failure { maintain | reboot }
undo system-failure
View
System view
Default Level
3: Manage level
Parameters
maintain: Specifies that when the system detects any software abnormality, it maintains the current situation, and does not take any measure to recover itself.
reboot: Specifies that when the system detects any software abnormality, it recovers itself through automatic reboot.
Description
Use the system-failure command to configure the exception handling method.
By default, the system adopts the reboot method to handle exceptions.
Examples
# Set the exception handling method to reboot.
<Sysname> system-view
[Sysname] system-failure reboot