IBMC Advanced Command Reference 05
IBMC Advanced Command Reference 05
Issue 05
Date 2024-09-25
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: https://www.huawei.com
Email: support@huawei.com
Overview
This document describes the parameters used by iBMC advanced users,
development personnel, and production personnel.
Note
Commands described in this document can be used only by advanced users, R&D
personnel, and production personnel. Otherwise, the user shall bear full
responsibility for any consequences.
Change History
Issue Release Date Description
Contents
2.13 coninfo....................................................................................................................................................................................21
2.14 cp.............................................................................................................................................................................................. 22
2.15 crc32........................................................................................................................................................................................ 22
2.16 datafs_cp............................................................................................................................................................................... 23
2.17 datafs_reset.......................................................................................................................................................................... 23
2.18 datafs_up............................................................................................................................................................................... 23
2.19 ddr_test.................................................................................................................................................................................. 24
2.20 dt.............................................................................................................................................................................................. 24
2.21 dts............................................................................................................................................................................................ 25
2.22 echo......................................................................................................................................................................................... 25
2.23 editenv.................................................................................................................................................................................... 26
2.24 erase........................................................................................................................................................................................ 26
2.25 exit........................................................................................................................................................................................... 27
2.26 false......................................................................................................................................................................................... 27
2.27 flinfo........................................................................................................................................................................................ 28
2.28 fsinfo....................................................................................................................................................................................... 28
2.29 fsload...................................................................................................................................................................................... 29
2.30 go............................................................................................................................................................................................. 29
2.31 help.......................................................................................................................................................................................... 30
2.32 hiddr_test...............................................................................................................................................................................30
2.33 iminfo......................................................................................................................................................................................30
2.34 itest.......................................................................................................................................................................................... 31
2.35 loadb....................................................................................................................................................................................... 31
2.36 loads........................................................................................................................................................................................ 32
2.37 loady....................................................................................................................................................................................... 32
2.38 loop......................................................................................................................................................................................... 33
2.39 ls............................................................................................................................................................................................... 33
2.40 lswread................................................................................................................................................................................... 34
2.41 lswwrite.................................................................................................................................................................................. 34
2.42 md............................................................................................................................................................................................ 34
2.43 mm.......................................................................................................................................................................................... 35
2.44 mtdparts................................................................................................................................................................................ 35
2.45 mtest....................................................................................................................................................................................... 36
2.46 mw........................................................................................................................................................................................... 36
2.47 nfs............................................................................................................................................................................................ 37
2.48 nm............................................................................................................................................................................................ 37
2.49 passwd.................................................................................................................................................................................... 37
2.50 phyread.................................................................................................................................................................................. 38
2.51 phywrite................................................................................................................................................................................. 38
2.52 ping......................................................................................................................................................................................... 38
2.53 printenv.................................................................................................................................................................................. 39
2.54 protect.................................................................................................................................................................................... 39
2.55 rarpboot................................................................................................................................................................................. 41
2.56 reboot..................................................................................................................................................................................... 41
2.57 reset......................................................................................................................................................................................... 41
2.58 rootfs_cp................................................................................................................................................................................ 42
2.59 rootfs_up................................................................................................................................................................................ 42
2.60 run........................................................................................................................................................................................... 43
2.61 saveenv...................................................................................................................................................................................43
2.62 setenv..................................................................................................................................................................................... 44
2.63 sleep........................................................................................................................................................................................ 44
2.64 spi_test................................................................................................................................................................................... 45
2.65 test........................................................................................................................................................................................... 45
2.66 tftpboot.................................................................................................................................................................................. 45
2.67 true.......................................................................................................................................................................................... 46
2.68 Uboot_cp0............................................................................................................................................................................. 46
2.69 uboot0_up............................................................................................................................................................................. 47
2.70 uboot_cp1.............................................................................................................................................................................. 47
2.71 uboot1_up............................................................................................................................................................................. 48
2.72 version.................................................................................................................................................................................... 48
2.73 flashdata_burning.............................................................................................................................................................. 48
3 KVM Integration.................................................................................................................... 50
3.1 Software Environment Requirements............................................................................................................................ 50
3.2 Web Integration.................................................................................................................................................................... 51
3.2.1 Logging In to the KVM Using a URL Without Encryption................................................................................... 51
3.2.2 Logging In to the KVM Using a URL in Encryption Mode...................................................................................53
3.2.3 Connecting to the Web Home Page or KVM Using a Token..............................................................................55
3.3 Notes......................................................................................................................................................................................... 57
Command Format
maint_debug_cli
Parameter Description
None
Examples
# Access the debugging mode interface.
*************************************************************************
Debug Shell
Copyright(C) 2013-2018
*************************************************************************
~
~
~
%
Format
help
Parameters
None
Example
# The debug interface has been displayed.
% help
Usage: help
Get all command help information.
Usage: bye
Quit maintain debug command line interface.
Usage: attach <module name>
Attach certain module to debug.
Usage: i2cread <i2c device name>
Read value from i2c device.
Usage: regread
Read value in cpld.
Usage: getprop [-hw] <obj name>.<prop name>
Get prop value of a specified obj.
Usage: lsobj <class name>
List all objects specified class.
Usage: lsprop <obj name>
List all props of specified obj.
Usage: i2cdevicelist
List i2c device name.
Usage: lsmod
Command Format
bye
Parameter Description
None
Examples
# Run the following command on the debugging interface.
% bye
Byebye. See you next time.
Format
lsmod
Parameters
None
Example
# The debug interface has been displayed.
% lsmod
Payload FileManage MaintDebug StorageMgnt PcieSwitch NetConfig Dft ipmi_app DDNS kvm_vmm
diagnose CpuMem BIOS User Snmp Led BMC PowerMgnt card_manage Harddisk UPGRADE
sensor_alarm HwScan FruData cooling_app dfm
%
Command Format
attach <module name>
Parameter Description
Parameter Description
Examples
# Run the following command on the debugging interface.
% lsmod
Payload FileManage MaintDebug snmp0 web1 web0 Dft NetConfig ipmi_app kvm_vmm CpuMem
diagnose FruData Led PowerMgnt Snmp BIOS sensor_alarm HwScan BMC card_manage Harddisk
DDNS UPGRADE User Lcd cooling_app dfm
% attach Payload
Success
%
NOTE
Logs of the mass level can only be printed on the console and cannot be recorded in files.
Command Format
dlogtype <local | file>
Parameter Description
Parameter Description
Examples
# On the debugging mode interface, specific module attached.
% dlogtype local
Success
%
Command Format
dloglevel <error | info | debug | mass>
Parameter Description
Parameter Description
Examples
# On the debugging mode interface, specific module attached.
% dloglevel info
Success
%
NOTE
After the debugging is complete, restore the debugging log level to error and save the
setting again. For details, see 1.7 Modify the Debugging Log Output Level and this
chapter.
Command Format
save
Parameter Description
None
Examples
# Run the following command on the debugging interface.
% dloglevel info
Success
% save
Success
Command Format
regread
Parameter Description
None
Examples
# Run the following command on the debugging interface.
regread
[00000000] 0x0A 0x55 0x00 0x00 0x0F 0x02 0x0F 0x00 0x00 0x00 0x0F 0x00 0x01 0x00 0x00 0x00
[00000010] 0x80 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
......
Command Format
i2cdevicelist
Parameter Description
None
Examples
# Run the following command on the debugging interface.
% i2cdevicelist
lm75_inlet_temp
lm75_outlet_temp1
lm75_outlet_temp2
lm75_mezz-2
lm75_raid_temp-6
eeprom0
EepromChip-2
EepromChip-6
EepromChip-9
EepromChip-10
onepower0
Command Format
i2cread <i2c device name>
Parameter Description
Parameter Description
Examples
# Run the following command on the debugging interface.
% i2cread lm75_inlet_temp
[00000000] 0x19 0xA0 0x19 0x19 0xA0 0x19 0xA0
Command Format
trace <enable | disable | all >
trace <ch=xx> [dest=xx src=xx netfn=xx cmd=xx]
Parameter Description
Parameter Description
Examples
# On the debugging mode interface, IPMI module connected.
% trace all
Success
% T(0003136690) Recv-->>>(CH-RMCP ) [ 20 18 C8 81 00 38 8E 04 B5 ]
T(0003136690) <<<--Send(CH-RMCP ) [ 81 1C 63 20 00 38 00 01 80 04 03 00 00 00 00 20 ]
T(0003136890) Recv-->>>(CH-RMCP ) [ 20 18 C8 81 04 3B 04 3C ]
T(0003136890) <<<--Send(CH-RMCP ) [ 81 1C 63 20 04 3B 00 04 9D ]
Command Format
lsobj <class name>
Parameter Description
Parameter Description
Examples
# Run the following command on the debugging interface.
% lsobj Eth
Eth2
Eth2vlan4090
Eth2vlan4092
Eth2vlan4093
Eth2Float
Eth3
Eth3vlan4090
Eth3vlan4092
Eth3vlan4093
Eth3Float
Command Format
getprop [-hw] <obj name>.<prop name>
Parameter Description
Parameter Description
Examples
# Run the following command on the debugging interface.
% getprop BMC.CpldVersion
3.04
Command Format
gmacstats <ethname>
Parameter Description
ethname: network port name
Examples
# Run the following command on the debugging interface.
% gmacstats eth2
eth2 statistics:
rx_desc_l3_wrong_head_cnt: 0
rx_desc_l3_csum_err_cnt: 0
rx_desc_l3_len_err_cnt: 0
rx_desc_l3_zero_ttl_cnt: 0
rx_desc_l3_rsvd_cnt: 0
rx_desc_l4_wrong_head_cnt: 0
rx_desc_l4_len_err_cnt: 0
rx_desc_l4_csum_err_cnt: 0
rx_desc_l4_zero_port_num_cnt: 0
rx_desc_l4_rsvd_cnt: 0
rx_desc_frag_cnt: 0
rx_desc_ip_ver_err_cnt: 0
rx_desc_ipv4_pkt_cnt: 71579173
rx_desc_ipv6_pkt_cnt: 19954372
rx_desc_no_ip_pkt_cnt: 19577999
rx_desc_ip_pkt_cnt: 199158
rx_desc_tcp_pkt_cnt: 71288453
rx_desc_udp_pkt_cnt: 467935
rx_desc_vlan_pkt_cnt: 91533542
rx_desc_icmp_pkt_cnt: 152345
rx_desc_arp_pkt_cnt: 14066
rx_desc_rarp_pkt_cnt: 0
rx_desc_multicast_pkt_cnt: 555736
rx_desc_broadcast_pkt_cnt: 326849
rx_desc_ipsec_pkt_cnt: 0
rx_desc_ip_opt_pkt_cnt: 46813
rx_desc_key_match_cnt: 91533545
rx_octets_total_ok_cnt: 2818686246
rx_uc_pkts_cnt: 90650960
rx_mc_pkts_cnt: 555736
rx_bc_pkts_cnt: 326849
rx_vlan_pkt_cnt: 91533542
rx_fw_ctrl_frame_cnt: 0
rx_octets_bad_cnt: 0
rx_octets_total_filt_cnt: 0
rx_filt_pkt_cnt: 0
rx_framsize_64: 20612628
rx_framsize_65_127: 70096873
rx_framsize_128_255: 307307
rx_framsize_256_511: 516722
rx_framsize_512_1023: 11
rx_framsize_1024_1518: 4
rx_framsize_bt_1518: 0
rx_fcs_error_cnt: 0
rx_data_error_cnt: 0
rx_align_error_cnt: 0
rx_frame_long_err_cnt: 0
rx_frame_very_long_err_cnt: 0
rx_frame_runt_err_cnt: 0
rx_frame_short_err_cnt: 0
rx_overrun_cnt: 0
rx_rbuff_rq_err_cnt: 0
tx_octets_total_ok_cnt: 2158081039
tx_uc_pkts_cnt: 125640095
tx_mc_pkts_cnt: 30686
tx_bc_pkts_cnt: 116910
tx_vlan_pkt_cnt: 125787663
tx_fw_ctrl_frame_cnt: 0
tx_octets_bad_cnt: 0
tx_framsize_64: 63505930
tx_framsize_65_127: 12197218
tx_framsize_128_255: 4525114
tx_framsize_256_511: 41019065
tx_framsize_512_1023: 4534071
tx_framsize_1024_1518: 6293
tx_framsize_bt_1518: 0
tx_fcs_error_cnt: 0
tx_underrun_err_cnt: 0
tx_add_cs_fail_cnt: 0
tx_buffrl_err_cnt: 0
tx_we_err_cnt: 0
rx_overrun_drop_cnt: 0
tx_excessive_drop_cnt: 0
tx_overrun_drop_cnt: 0
Print detailed statistics of gmac chip successfully.
Command Format
lsprop <obj name>
Parameter Description
obj name: object name.
Examples
# Run the following command on the debugging interface.
% lsprop PMEServiceConfig
SystemResourceMonitorEnable=0
SerialLoopbackDetectEnable=0
JavaVideoEnable=0
SnmpdEnable=0
DataAcquisitionSupport=0
iBMAOnBoardEnable=0
CustomSNMPOID=null
PSFirmwareUpgradeEnable=0
WEBEnable=1
SSDPEnable=1
WOLConfigEnable=0
SPServiceOSEnable=0
KerberosSupport=0
X86Enable=0
PowerCappingSupport=0
HTTPSEnable=1
EnergySavingSupport=0
PSUEnable=1
BoardInfoCollectStatus=0
VirtualUmsEnable=0
PowerActiveStandbyEnable=0
RTCEnable=1
PowerDeepSleepEnable=0
ARMEnable=0
CoolingEnable=1
SSHEnable=1
IPMILanEnable=1
HTTPEnable=1
BlackBoxSupport=0
JavaKVMEnable=0
PartitionEnable=0
BoardInfoCollectEnable=0
TrapEnable=1
SSDPCtrlPtEnable=0
VNCEnable=0
KVMEnable=0
SystemLockDownSupport=0
NetConfigEnable=1
RedfishEnable=1
Command Function
This command is used to query data of a specific SMC object.
Command Format
smcread <smcobj> <isBitAccess> <offset> <length> [mask]
Parameter Description
smcobj: SMC object name, which can be queried by running the lsobj command,
for example: lsobj SMC.
isBitAccess: The value 1 indicates a bit operation, and the value 0 indicates a
block operation. Other characters are invalid.
offset: Indicate the required operation code in hexadecimal format. Specify
document query through SMC command word. The offset consists of Function,
Command, MS, RW, and Parametert, each value are connected by colons (:), for
example, 0:4:0:1:0.
length: Length of the data to be read or written. The maximum access length is
255.
mask: If a bit operation is performed, mask is used. The value must be a
hexadecimal number, for example, 0xff.
Examples
# Run the following command on the debugging interface.
% smcread ExpBrdSMC 0 0:6:0:1:0 5
0x00 0x00 0x10 0x01 0x16
Enter and run U-Boot commands at the command-line prompt. By running dozens
of common U-Boot commands, R&D engineers can debug the development board,
boot the Linux kernel, and erase the flash memory to implement system
deployment. Under the U-Boot, running help displays all U-Boot commands. Brief
command and parameter descriptions are provided after each command. This
section describes command functions and parameters based on help information.
The default U_Boot password can be obtained from the product nameplate. You
can change the password using the passwd command. Change the default
password upon the first login. For security purposes, change the password
periodically. For details, see the description of the passwd command.
Only iBMC 1710 supports the U-Boot command. iBMC chip type, which can be
obtained by running the ipmcget -d version command.
2.1 ?
2.2 appfs_cp
2.3 appfs_up
2.4 base
2.5 bdinfo
2.6 boot
2.7 bootd
2.8 bootm
2.9 bootp
2.10 cfgfs_cp
2.11 cfgfs_up
2.12 cmp
2.13 coninfo
2.14 cp
2.15 crc32
2.16 datafs_cp
2.17 datafs_reset
2.18 datafs_up
2.19 ddr_test
2.20 dt
2.21 dts
2.22 echo
2.23 editenv
2.24 erase
2.25 exit
2.26 false
2.27 flinfo
2.28 fsinfo
2.29 fsload
2.30 go
2.31 help
2.32 hiddr_test
2.33 iminfo
2.34 itest
2.35 loadb
2.36 loads
2.37 loady
2.38 loop
2.39 ls
2.40 lswread
2.41 lswwrite
2.42 md
2.43 mm
2.44 mtdparts
2.45 mtest
2.46 mw
2.47 nfs
2.48 nm
2.49 passwd
2.50 phyread
2.51 phywrite
2.52 ping
2.53 printenv
2.54 protect
2.55 rarpboot
2.56 reboot
2.57 reset
2.58 rootfs_cp
2.59 rootfs_up
2.60 run
2.61 saveenv
2.62 setenv
2.63 sleep
2.64 spi_test
2.65 test
2.66 tftpboot
2.67 true
2.68 Uboot_cp0
2.69 uboot0_up
2.70 uboot_cp1
2.71 uboot1_up
2.72 version
2.73 flashdata_burning
2.1 ?
Function
Similar to the help command, this command is used to display help information.
Format
None
Parameters
None
2.2 appfs_cp
Function
This command is used to copy the appfs file to the flash memory.
Format
Hi1710_UBOOT> help appfs_cp
Usage:
Parameters
None
2.3 appfs_up
Function
This command is used to upgrade the APP file system.
Format
Hi1710_UBOOT> help appfs_up
Usage:
Parameters
appfile indicates the name of the file system to be written into the flash memory.
2.4 base
Function
This command is used to display the offset address for the memory command.
The base off command is used to set the offset address for the memory
command.
Format
Hi1710_UBOOT> help base
Usage:
base
base off
Parameters
[off] indicates the offset address.
2.5 bdinfo
Function
This command is used to query the board structure.
Format
Hi1710_UBOOT> help bdinfo
Usage:
bdinfo
Parameters
None
2.6 boot
Function
This command is used to boot the images in the flash memory.
Format
Hi1710_UBOOT> help boot
Usage:
boot
Parameters
None
2.7 bootd
Function
Similar to the boot command, this command is used to boot the images in the
flash memory.
Format
Hi1710_UBOOT> help bootd
Usage:
bootd
Parameters
None
2.8 bootm
Function
This command is used to boot application images stored in memories. The
memories include the RAM and the flash memory that can permanently store
data.
Format
Hi1710_UBOOT> help bootm
bootm - boot application image from memory
Usage:
bootm [addr [arg ...]]
- boot application image stored in memory
passing arguments 'arg ...'; when booting a Linux kernel,
'arg' can be the address of an initrd image
Parameters
addr indicates the address for application images in U-boot format.
arg is used for booting the Linux kernel and indicates the storage address for the
RAMDISK image in U-boot format. The arg parameter can be transferred to the
Linux kernel. The bootargs environment variable is transferred to the kernel by
default.
2.9 bootp
Function
This command is used to request the DHCP server to allocate an IP address and
download a specified file to the memory over the Trivial File Transfer Protocol
(TFTP).
Format
Hi1710_UBOOT> help bootp
bootp - boot image via network using BOOTP/TFTP protocol
Usage:
Parameters
loadAddress indicates the memory address for storing the file to be downloaded.
hostIPaddr indicates the IP address of the host which provides the downloading -
service for the client.
bootfilename indicates the name of the file to be downloaded. This should be
provided on the host.
2.10 cfgfs_cp
Function
This command is used to copy the cfgfs file to the flash memory.
Format
Hi1710_UBOOT> help cfgfs_cp
cfgfs_cp - cfgfs_cp -copy cfgfs to flash
Usage:
cfgfs_cp cfgfs_cp -copy cfgfs to flash
Parameters
None
2.11 cfgfs_up
Function
This command is used to upgrade the CFG file system.
Format
Hi1710_UBOOT> help cfgfs_up
cfgfs_up - cfgfs_up -update data file system
Usage:
cfgfs_up update cfg file system to flash
Parameters
cfgfile indicates the name of the file system to be written into the flash memory.
2.12 cmp
Function
This command is used to compare the contents in two memories.
Format
Hi1710_UBOOT> help cmp
Usage:
Parameters
addr1 indicates the start address for the first memory.
count indicates the amount of data to be compared. The units of cp.b, cp.w, and
cp.l are byte, word, and long word respectively. Note that there is no space in
cmp.b.
2.13 coninfo
Function
This command is used to display console configurations.
Format
Hi1710_UBOOT> help coninfo
Usage:
coninfo
Parameters
None
2.14 cp
Function
This command is used to copy data blocks in the memory or in the flash memory.
Format
Hi1710_UBOOT> help cp
cp - memory copy
Usage:
cp [.b, .w, .l] source target count
Parameters
source indicates the start address for the data blocks to be copied.
target indicates the address to which data blocks are copied. If this address is
located in the flash memory, the function for writing to the flash memory is
called. Therefore, the U-boot writes to the flash memory by running the cp
command. The area of the flash memory must be erased before this area is
written.
count indicates the amount of data to be copied. The units of cp.b, cp.w, and cp.l
are byte, word, and long word respectively.
2.15 crc32
Function
This command is used to calculate the checksum of the stored data.
Format
Hi1710_UBOOT> help crc32
crc32 - checksum calculation
Usage:
crc32 address count [addr]
- compute CRC32 checksum [save at addr]
Parameters
address indicates the address for the data to be checked.
count indicates the number of bytes to be checked.
2.16 datafs_cp
Function
This command is used to copy the datafs file to the flash memory.
Format
Hi1710_UBOOT> help datafs_cp
Usage:
Parameters
None
2.17 datafs_reset
Function
This command is used to reset the datafs.
Format
Hi1710_UBOOT> help datafs_reset
Usage:
datafs_reset
Parameters
None
2.18 datafs_up
Function
This command is used to upgrade the data file system.
Format
Hi1710_UBOOT> help datafs_up
Usage:
Parameters
datafile indicates the name of the file system to be written into the flash memory.
2.19 ddr_test
Function
This command is used to check the memory through the memory self-check
module of the CPU. WR, march-6n, and 9-step checkerboard are available for
memory self-check.
Format
ddr_test <ADDR> <LEN> <ALGO>
Parameters
● ADDR indicates the start address for the memory self-check.
● LEN indicates the range for the memory self-check.
● ALGO indicates the algorithm to be used. The values specific to the supported
algorithms are as follows:
● 0: WR
● 1: March-6n
● 2: 9 step checkerboard
NOTE
The memory address segment (ranging from 0x87400000 to 0x87a00000) used by the U-
boot cannot be tested. Otherwise, the U-boot will be suspended.
2.20 dt
Function
This command is used to perform memory self-check on software. The algorithm
is 3-step checkerboard.
Format
dt <start_addr> <ramsize>
Parameters
start_addr indicates the start address for the memory self-check.
NOTE
Memory self-check has been completed before Huawei Hi1710 is powered on. The memory
self-check range involved in this command does not cover the memory that the U-boot
occupies (because the U-boot has been running) or the reserved memory shared with the
x86 system.
2.21 dts
Function
This command is used to write a value to a specified physical address and display
the value. This command is used only for a test.
Format
dts < test_addr> < test_value>
Parameters
test_addr indicates the physical address where a value is to be written.
2.22 echo
Function
This command is used to display parameters.
Format
Hi1710_UBOOT> help echo
Usage:
echo [args..]
Parameters
[args..] indicates the parameter to be displayed.
2.23 editenv
Function
This command is used to edit environment variables.
Format
editenv <env>
Parameters
env indicates the environment variable to be edited.
2.24 erase
Function
This command is used to erase specified blocks in the flash memory.
Format
Hi1710_UBOOT> help erase
erase - erase FLASH memory
Usage:
erase start end
- erase FLASH from addr 'start' to addr 'end'
erase start +len
- erase FLASH from addr 'start' to the end of sect w/addr 'start'+'len'-1
erase N:SF[-SL]
- erase sectors SF-SL in FLASH bank # N
erase bank N
- erase FLASH bank # N
erase <part-id>
- erase partition
erase all
- erase all FLASH banks
Parameters
If a block is to be erased based on the start and end addresses, the start
parameter indicates the start address for the block, and the end parameter
indicates the end address for the block. If a block to be erased based on the bank
ID and sector ID, N indicates the flash memory bank ID, SF indicates the ID of the
start sector to be erased, and SL indicates the ID of the end sector to be erased. To
erase all the blocks in flash bank N, run erase bank N. To erase all the blocks in a
flash memory, run erase all.
2.25 exit
Function
This command is used to exit the U-boot script and is used only in a script.
Format
Hi1710_UBOOT> help exit
Usage:
exit
Parameters
None
2.26 false
Function
This command is used to write the U-boot script, and the returned value is always
false.
Format
Hi1710_UBOOT> help false
Usage:
Parameters
None
2.27 flinfo
Function
This command is used to display the information about one or all flash memory
banks.
Format
Hi1710_UBOOT> help flinfo
Usage:
flinfo
flinfo N
Parameters
None
2.28 fsinfo
Function
This command is used to display file system information.
Format
Hi1710_UBOOT> help fsinfo
Usage:
fsinfo
Parameters
None
2.29 fsload
Function
This command is used to search for a binary file at a specified address and load it
to the memory.
Format
Hi1710_UBOOT> help fsload
fsload - load binary file from a filesystem image
Usage:
fsload [ off ] [ filename ]
- load binary file from flash bank
with offset 'off'
Parameters
[off] indicates the specified address, and [filename] indicates the file to be
searched.
2.30 go
Function
This command is used to run an application.
Format
Hi1710_UBOOT> help go
go - start application at address 'addr'
Usage:
go addr [arg ...]
- start application at address 'addr'
passing 'arg' as arguments
Parameters
addr indicates the entry address for the application to be executed.
[arg ...] is optional and indicates the parameter to be transferred to the
application.
2.31 help
Function
This command is used to query help information.
Format
Hi1710_UBOOT> help help
Usage:
help
Parameters
The optional parameter command indicates the command whose help
information will be displayed.
2.32 hiddr_test
Function
This command is used to report the last memory self-check result.
Format
hiddr_test
Parameters
None
2.33 iminfo
Function
This command is used to display header information about application images.
Image check (covering the serial number, header, and checksum) is involved in this
function.
Format
Hi1710_UBOOT> help iminfo
iminfo - print header information for application image
Usage:
iminfo addr [addr ...]
- print header information for application image starting at
address 'addr' in memory; this includes verification of the
image contents (magic number, header and payload checksums)
Parameters
addr indicates the start address for a specified image.
[addr ...] is optional and indicates the addresses for other images.
2.34 itest
Function
This command is used to compare two values by byte, word, and long word.
Format
Hi1710_UBOOT> help itest
itest - return true/false on integer compare
Usage:
itest [.b, .w, .l, .s] [*]value1 <op> [*]value2
Parameters
value1 and value2 indicate the values to be compared, and op indicates the
comparison operator.
2.35 loadb
Function
This command is used to load a binary file over the serial cable.
Format
Hi1710_UBOOT> help loadb
loadb - load binary file over serial line (kermit mode)
Usage:
- load binary file over serial line with offset 'off' and baudrate 'baud'
Parameters
The optional parameters [off] and [baud] indicate the offset address and baud
rate respectively.
2.36 loads
Function
This command is used to load an S-Record file over the serial cable.
Format
Hi1710_UBOOT> help loads
Usage:
loads [ off ]
Parameters
The optional parameters [off] and [baud] indicate the offset address and baud
rate respectively.
2.37 loady
Function
This command is used to load a binary file over the serial cable.
Format
Hi1710_UBOOT> help loady
Usage:
- load binary file over serial line with offset 'off' and baudrate 'baud'
Parameters
The optional parameters [off] and [baud] indicate the offset address and baud
rate respectively.
2.38 loop
Function
This command is used to conduct the loopback test on a group of addresses.
Format
Hi1710_UBOOT> help loop
Usage:
Parameters
The address parameter indicates the test address.
2.39 ls
Function
This command is used to list the files in the current directory.
Format
Hi1710_UBOOT> help ls
Usage:
ls [ directory ]
Parameters
The optional parameter directory indicates the directory to be queried.
2.40 lswread
Function
This command is used to read a value from a register on the Marvell-provided
LAN switch (LSW).
Format
lswread <mdio_addr> <dev_addr> <reg_addr>
Parameters
mdio_addr indicates the LSW address on the MDIO bus.
dev_addr indicates the address of a device on the LSW.
reg_addr indicates the register offset on a device of the LSW.
2.41 lswwrite
Function
This command is used to write a value into a register on the Marvell-provided
LSW.
Format
lswwrite <mdio_addr> <dev_addr> <reg_addr> <val>
Parameters
mdio_addr indicates the LSW address on the MDIO bus.
dev_addr indicates the address of a device on the LSW.
reg_addr indicates the register offset on a device of the LSW.
val indicates the value to be written.
2.42 md
Function
This command is used to display memory information by byte, word, and long
word.
Format
Hi1710_UBOOT> help md
md - memory display
Usage:
Parameters
The address parameter indicates the start address.
2.43 mm
Function
This command is used to modify the memory by byte, word, and long word. The
usage of .b, .w, and .l is the same as that of the cp command.
Format
Hi1710_UBOOT> help mm
Usage:
Parameters
The address parameter indicates the address for the memory to be modified.
2.44 mtdparts
Function
This command is used to display partition information.
Format
mtdparts
Parameters
None
2.45 mtest
Function
This command is used to conduct read and write tests on the RAM.
Format
Hi1710_UBOOT> help mtest
Usage:
Parameters
The start parameter indicates the test start identifier, and the end parameter
indicates the test end identifier.
2.46 mw
Function
This command is used to write to the memory by byte, word, and long word. The
usage of .b, .w, and .l is the same as that of the cp command.
Format
Hi1710_UBOOT> help mw
Usage:
Parameters
address is the address for the memory to be written.
2.47 nfs
Function
This command is used to start images over the Network File System (NFS)
protocol.
Format
Hi1710_UBOOT> help nfs
nfs - boot image via network using NFS protocol
Usage:
nfs [loadAddress] [[hostIPaddr:]bootfilename]
Parameters
loadAddress is optional and indicates the host address.
host ip addr:bootfilename indicates the host IP address.
2.48 nm
Function
This command is used to modify the memory by byte, word, and long word.
Format
Hi1710_UBOOT> help nm
nm - memory modify (constant address)
Usage:
nm [.b, .w, .l] address
Parameters
The address parameter indicates the address for the memory to be read and then
modified.
2.49 passwd
Function
This command is used to change the U-boot login password.
Format
Passwd
Parameters
None
2.50 phyread
Function
This command is used to read a value from a PHY register.
Format
phyread <phy_addr> <reg_addr>
Parameters
phy_addr indicates the PHY address on the MDIO bus.
2.51 phywrite
Function
This command is used to write a value into a PHY register.
Format
phywrite <phy_addr> <reg_addr> <val>
Parameters
phy_addr indicates the PHY address on the MDIO bus.
2.52 ping
Function
This command is used to send an Internet Control Message Protocol (ICMP)
request to the network host.
Format
Hi1710_UBOOT> help ping
ping - send ICMP ECHO_REQUEST to network host
Usage:
ping pingAddress
Parameters
The pingAddress parameter indicates the destination host address.
2.53 printenv
Function
This command is to display all or specified environment variables.
Format
Hi1710_UBOOT> help printenv
printenv - print environment variables
Usage:
printenv
- print values of all environment variables
printenv name ...
- print value of environment variable 'name'
Parameters
None
2.54 protect
Function
This command is used to enable or disable write protection for the flash memory.
Format
Hi1710_UBOOT> help protect
protect - enable or disable FLASH write protection
Usage:
protect on N:SF[-SL]
protect on bank N
protect on <part-id>
- protect partition
protect on all
- make FLASH from addr 'start' to end of sect w/addr 'start'+'len'-1 wrtable
Parameters
The on parameter indicates that write protection is enabled, and the off
parameter indicates that write protection is disabled.
The parameters N, SF, and SL are used to specify the write protection range of the
flash memory. Their usage is the same as that of the erase command.
2.55 rarpboot
Function
This command is used to mirror files over TFTP, that is, download a specified file
to a specified address and then run it.
Format
Hi1710_UBOOT> help rarpboot
Usage:
Parameters
loadAddress indicates the memory address for storing the file to be downloaded.
2.56 reboot
Function
This command is used to reboot the U-boot.
Format
Hi1710_UBOOT> help reboot
Usage:
reboot
Parameters
None
2.57 reset
Function
This command is used to reset the U-boot.
Format
Hi1710_UBOOT> help reset
Usage:
reset
Parameters
None
2.58 rootfs_cp
Function
This command is used to copy the rootfs file to the flash memory.
Format
Hi1710_UBOOT> help rootfs_cp
Usage:
Parameters
None
2.59 rootfs_up
Function
This command is used to upgrade the root file system.
Format
Hi1710_UBOOT> help rootfs_up
Usage:
Parameters
rootfsfile indicates the name of the rootfs file to be loaded onto the flash
memory.
2.60 run
Function
This command is used to run the commands in environment variables. The var
parameter can be followed by several environment variables.
Format
Hi1710_UBOOT> help run
Usage:
Parameters
The var parameter can be an environment variable name.
2.61 saveenv
Function
This command is used to save environment variables to the flash memory.
Format
Hi1710_UBOOT> help saveenv
Usage:
saveenv
Parameters
None
2.62 setenv
Function
This command is used to set environment variables.
Format
Hi1710_UBOOT> help setenv
Usage:
setenv name
Parameters
name indicates the name of the environment variable to be set.
value indicates the value to be specified. If the value parameter is not specified,
the corresponding environment variable is deleted.
2.63 sleep
Function
This command is used to delay execution by several seconds.
Format
Hi1710_UBOOT> help sleep
Usage:
sleep N
Parameters
N indicates the delay time in second and it is a decimal number.
2.64 spi_test
Function
This command is used to send the 0x5a5a data over the SPI bus.
Format
Hi1710_UBOOT> help spi_test
Usage:
spi_test spi_test
Parameters
None
2.65 test
Function
This command is used to start a test, such as running scripts.
Format
Hi1710_UBOOT> help test
Usage:
test [args..]
Parameters
The [args..] parameter indicates the variable to be tested.
2.66 tftpboot
Function
This command is used to download binary files over TFTP. The environment
variables, such as serverip and ipaddr, must be set before this command is
executed.
Format
Hi1710_UBOOT> help tftpboot
tftpboot - boot image via network using TFTP protocol
Usage:
tftpboot [loadAddress] [[hostIPaddr:]bootfilename]
Parameters
loadAddress indicates the memory address for storing the file to be downloaded.
hostIPaddr indicates the IP address of the host which provides TFTP service for
the client.
bootfilename indicates the name of the file to be downloaded. The file must be
in a directory of the TFTP server.
2.67 true
Function
This command is used to write the U-boot script, and the returned value is always
true.
Format
Hi1710_UBOOT> help true
true - do nothing, successfully
Usage:
true - No additional help available.
Parameters
None
2.68 Uboot_cp0
Function
The command is used to copy the U-boot file to the flash memory.
Format
Hi1710_UBOOT> help uboot_cp0
uboot_cp0 - uboot_cp -copy uboot to flash
Usage:
Parameters
None
2.69 uboot0_up
Function
This command is used to upgrade the U-boot.
Format
Hi1710_UBOOT> help uboot0_up
Usage:
Parameters
None
2.70 uboot_cp1
Function
The command is used to copy the U-boot file to the flash memory.
Format
Hi1710_UBOOT> help uboot_cp1
Usage:
Parameters
None
2.71 uboot1_up
Function
This command is used to upgrade the U-boot.
Format
Hi1710_UBOOT> help uboot1_up
uboot1_up - uboot_up -update uboot
Usage:
uboot1_up update uboot to flash
Parameters
None
2.72 version
Function
This command is used to query the U-boot version.
Format
Hi1710_UBOOT> help version
version - display u-boot version
Usage:
version
Parameters
None
2.73 flashdata_burning
Function
This command is used to burn flash data for upgrading the iBMC.
Format
Hi1710_UBOOT> flashdata_burning
Parameters
None
3 KVM Integration
The KVM function is integrated in the URL. To ensure the system proper running,
perform corresponding steps to complete the development in a proper running
environment.
3.1 Software Environment Requirements
3.2 Web Integration
3.3 Notes
OS Windows XP 32-bit
Mac OS X v10.7
Parameter description:
-I lan: accessing through the network. -I lanplus: encrypted; lan: non-encrypted.
-U root: the local BMC user name. Set this parameter based on the actual
situation.
-P Huawei12#$: BMC user password. Set this parameter based on the actual
situation.
raw 0x30 0x93 0xdb 0x07 0x00 0x04 0x00 0x0 0x0 0x0 0x3 0x72 0x6f 0x6f 0x74
0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0: The information in red is
divided into three parts.
Part 1: 0x0 0x0 0x0 0x3 before the red part is the identifier, which is in little-
endian format and is used for communication between the KVM and the console.
The identifier is valid for 2 minutes and becomes invalid immediately after
verification.
Part 2: The last 16 bytes 0x72 0x6f 0x6f 0x74 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
0x0 0x0 0x0 0x0 indicate the user name.
Part 3: The last byte indicates whether to open the KVM in shared mode or
exclusive mode.
Second command:
ipmitool -I lanplus -H 192.168.2.100 -U root -P Huawei12#$ raw 0x30 0x94 0xdb 0x07 0x00 0x21 0x06 0x00
0x00 0x37 0x00 0x24 0x00 0x00 0x00 0x03 0x06 0xBD 0x43 0x29 0x77 0x3F 0xC3 0x34 0x36 0x75 0x96
0x4B 0x67 0xEE 0x72 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83
0x83 0x72 0x6f 0x6f 0x74 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
-U root: the local BMC user name. Set this parameter based on the actual
situation.
-P root: the BMC root user password. Set this parameter based on the actual
situation.
raw 0x30 0x94 0xdb 0x07 0x00 0x21 0x06 0x00 0x00 0x37 0x00 0x24 0x00 0x00
0x00 0x03 0x06 0xBD 0x43 0x29 0x77 0x3F 0xC3 0x34 0x36 0x75 0x96 0x4B 0x67
0xEE 0x72 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83
0x83 0x83 0x83 0x83 0x72 0x6f 0x6f 0x74 0x00 0x00 0x00 0x00 0x00 0x00 0x00
0x00 0x00 0x00 0x00 0x00 0x00
The information that is not in red is the header information (generally, you do not
need to modify it). The information in red is divided into four parts.
Part 1: 0x00 0x00 0x00 0x03 before the red part is the identifier in little-endian
format. The validity period of the identifier is 2 minutes. The identifier becomes
invalid after one login.
0x06 0xBD 0x43 0x29 0x77 0x3F 0xC3 0x34 0x36 0x75 0x96 0x4B 0x67 0xEE 0x72
0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83
0x83 0x83
are used when the encryption mode is enabled. In the non-encryption state, they
are invalid and can be set to any value.
Part 3: The last 16 bytes of the encrypted field are the user name.
0x72 0x6f 0x6f 0x74 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
0x00
Part 4: The last byte indicates whether to open the KVM in shared mode or
exclusive mode.
Step 3 Call the corresponding Uniform Resource Locator (URL). URL format:
https:// 192.168.2.100/remote_access.asp?authParam=3&lp=en
Parameter description:
192.168.2.100: the IP address of the BMC to be accessed. Set this parameter based
on the actual situation.
authParam: the identifier set by using the IPMITool. authParam= 3, the value 3 is
a decimal number converted from 0x00 0x00 0x00 0x03.
lp: current language, which can be Chinese or English, Chinese parameter value
----End
Only the administrator can set KVM encryption. You can set the encryption mode
on the BMC WebUI or by using the IPMITool. Run the following command to
enable the encryption mode:
ipmitool -I lanplus -U root -P Huawei12#$ -H 192.168.2.100 raw 0x30 0x94 0xdb 0x07 0x00 0x21 0x02
0x00 0x00 0x01 0x01
-U root: the local BMC user name. Set this parameter based on the actual
situation.
-P Huawei12#$: BMC user password. Set this parameter based on the actual
situation.
The information that is not in red is the header information (generally, you do not
need to modify it). The information in red is the encryption state of the KVM.
0x00: non-encrypted
0x01: encrypted
Step 2 To prevent unauthorized users from connecting to the BMC through the local KVM
console and using the KVM function, the BMC needs to confirm the user identity
based on the user ID. You can use the IPMITool to set the identifier.
ipmitool -I lanplus -H 192.168.2.100 -U root -P Huawei12#$ raw 0x30 0x94 0xdb 0x07 0x00 0x21 0x06 0x00
0x00 0x37 0x00 0x24 0x00 0x00 0x00 0x03 0x06 0xBD 0x43 0x29 0x77 0x3F 0xC3 0x34 0x36 0x75 0x96
0x4B 0x67 0xEE 0x72 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83
0x83 0x72 0x6f 0x6f 0x74 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
-U root: the local BMC user name. Set this parameter based on the actual
situation.
-P root: the BMC root user password. Set this parameter based on the actual
situation.
raw 0x30 0x94 0xdb 0x07 0x00 0x21 0x06 0x00 0x00 0x37 0x00 0x24 0x00 0x00
0x00 0x03 0x06 0xBD 0x43 0x29 0x77 0x3F 0xC3 0x34 0x36 0x75 0x96 0x4B 0x67
0xEE 0x72 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83
0x83 0x83 0x83 0x83 0x72 0x6f 0x6f 0x74 0x00 0x00 0x00 0x00 0x00 0x00 0x00
0x00 0x00 0x00 0x00 0x00 0x00
The information that is not in red is the header information (generally, you do not
need to modify it). The information in red is divided into three parts.
Part 1: The 0x00 0x00 0x00 0x03 0x06 0xBD 0x43 0x29 0x77 0x3F 0xC3 0x34
0x36 0x75 0x96 0x4B 0x67 0xEE 0x72 0x83 0x83 0x83 0x83 0x83 0x83 0x83
0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 before the red part is the
identification ID. The validity period of the identifier is 2 minutes. The identifier
becomes invalid after one login.
Part 3: The last byte indicates whether to open the KVM in shared mode or
exclusive mode.
This port is used for communication between the KVM and the console. The
validity period of the identifier is 2 minutes. The identifier becomes invalid after
one login.
Step 3 Call the corresponding Uniform Resource Locator (URL). URL format:
https://192.168.2.100/remote_access.asp?
authParam=0000000306BD4329773FC3343675964B67EE728383838383838383838
383838383838383&lp=en
The parameters in red in the URL can be modified. The parameters in the
command are described as follows:
192.168.2.100: BMC IP address. Set this parameter based on the actual situation.
authParam: the identifier set by using the IPMITool. Parameters following
authParam=0000000306BD4329773FC3343675964B67EE7283838383838383838
38383838383838383 are converted from 0x00 0x00 0x00 0x03 0x06 0xBD 0x43
0x29 0x77 0x3F 0xC3 0x34 0x36 0x75 0x96 0x4B 0x67 0xEE 0x72 0x83 0x83 0x83
0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83 0x83.
Note: The ID can only be entered in hexadecimal format.
lp: current language, which can be Chinese or English, Chinese parameter value
Note: lp=cn indicates Chinese and lp=en indicates English.
----End
function Execution
Token response
Respo {ret:val, token:val}
nse
The number of online users (Web/ The web login page is displayed, and a
KVM) reaches the maximum. message "The maximum number of
sessions has been reached." is
displayed.
The token is invalid, the user does not The WebUI login page is displayed,
have the permission, or other errors and the message "Login failed. Try
occur. again." is displayed.
3.3 Notes
1. The KVM integration function applies to Huawei servers that support the KVM
function.
2. Customers may use different Huawei servers and versions, some of which may
not support this calling method, resulting in compatibility issues.
3. Considering the version mapping of JAR packages, do not cache JAR packages
locally during integration. Instead, you need to download JAR packages from
the server BMC each time you open the remote console (the JAR packages are
automatically downloaded when you open the remote_access.asp page).