Get Lsw Info Parameters
更新时间： 2026/08/06
在Gitcode上查看源码Get Lsw Info Parameters
Change History
| openUBMC Version | Revision Date | Description |
|---|---|---|
| 25.06 | 2025/06/26 | Initial draft: add command details |
Basic Information
Function Description
Obtains LSW parameters.
Privilege
Command Information
Request Information
| Byte | Data Field |
|---|---|
| NetFn | 30h |
| CMD | 93h |
| 1:3 | Manufacturer ID, LS Byte first. The length is fixed to three bytes. For example, if the vendor ID is 2011 and the corresponding hexadecimal value is 0x0007DB, the first byte is DBh, the second byte is 07h, and the third byte is 00h. |
| 4 | Sub command, subcommand = 60h |
| 5 | Parameter selector |
| 6:N | Configuration parameter data For details, see Table 1. |
Response Information
| Byte | Data Field |
|---|---|
| 1 | Completion Code |
| 2:4 | Manufacturer ID, LS Byte first. The length is fixed to three bytes. For example, if the vendor ID is 2011 and the corresponding hexadecimal value is 0x0007DB, the first byte is DBh, the second byte is 07h, and the third byte is 00h. |
| 5:N | Reponse data For details, see Table 1. |
Reference Information
Table 1 Lsw Info Parameters Table
| Parameter | # | Parameter Data |
|---|---|---|
| Get Node Status (Read Only) | 01h | Slot ID of the data1-Slot Id--Lsw node The response data is as follows: data[5]: node status. 0x5A indicates that the node is valid, and 0xff indicates that the node is invalid. |
| Get Port Statistics (Read Only) | 02h | data[1-32]: Port Name (port name, 32 bytes. If the name contains less than 32 bytes, fill 00h.) The response data is as follows: data[33]: number of statistical items data[34-36]: reserved data[37-164]: Every eight bytes form a statistical item. rx_octets_total: total number of bytes received by a specified switch port rx_pkt_unicast: indicates the total number of unicast packets received on a specified switch port. rx_pkt_multicast: indicates the total number of multicast packets received on the specified switch port. rx_pkt_broadcast: indicates the total number of broadcast packets received on a specified switch port. tx_octets_total: specifies the total number of bytes sent by the switch port. tx_pkt_unicast: indicates the total number of unicast packets sent by a specified switch port. tx_pkt_multicast: indicates the total number of multicast packets sent by a specified switch port. tx_pkt_broadcast: indicates the total number of broadcast packets sent by a specified switch port. rx_mac_drop_cnt: specifies the total number of discarded packets at the MAC layer received by the specified switch port. rx_adpt_s2p_drop_cnt: indicates the number of lost S2P packets on the specified switch port. rx_swb_dpi_drop_cnt: indicates the number of packets discarded by DPI on a specified switch port. tx_adpt_p2s_drop_cnt: indicates the number of P2S lost packets on the specified switch port. tx_pkt_err_all: specifies the total number of error packets on the specified switch port. tx_mac_drop_cnt: indicates the number of discarded packets at the MAC layer sent from a specified switch port. rx_pkt_symbol_err: This parameter indicates the number of error packets on the specified switch port. rx_pkt_fcs_err: indicates the number of FCS error packets on a specified switch port. |
| Get Work Port Info (Read Only) | 03h | data[1-32]: Port Name (port name, 32 bytes. If the name contains less than 32 bytes, fill 00h.) The response data is as follows: data[33]: number of statistical items data[34-36]: reserved data[37-60]: Every eight bytes form a statistical item. The statistical items are as follows: Port duplex information Port auto-negotiation information Indicates the working rate of a port. The value is a character string. If no byte is used, 0x00 is used for padding. |
| Get Node Online Status (Read Only) | 04h | data[1-4]: max_slot_num: maximum number of slots in the current subrack The response data is as follows: Compute node response: data[5]: mesh card installation status. 0x00 indicates that the mesh card is not installed, and 0x01 indicates that the mesh card is installed. Response of the management module center: data[5-(5+max_slot_num)], indicating the installation status of each node. 0x00 indicates that the node is not installed, and 0x01 indicates that the node is installed. |
| Get MESH multiple path operation (Read Only) | 05h | data[1-4]: type. 1: control node; 2: controlled node; 3: relay node. data[5-8]: indicates the mode. The value 0 indicates that the regeneration is configured. The value 1 indicates that the regeneration is pre-restored. The value 2 indicates that the regeneration is restored. The value 3 indicates that the regeneration is available. The value 4 indicates that the regeneration information is synchronized. data[9-12]: slot ID of the controller node data[13-16]: slot ID of the relay node data[17-20]: slot ID of the controlled node data[21-24]: whether trunk information is obtained from the chip. 1: yes; 0: no. The response data is as follows: data[5]: return value of the request operation. The value 0 indicates success, and the value 1 indicates failure. |
| Get Port Link Status (Read Only) | 06h | data[1-4]: Port Index The response data is as follows: data[5-6]: port link status. 0: link down; 1: link up. |
| Get multiple path link status (Read Only) | 07h | data[1]: slot ID of the local node data[2]: type. The value 1 indicates that link information is sent between BMCs. The value 2 indicates that link information is sent between the iBMA and BMC. The value 3 indicates iBMA heartbeat information. type=1: data[3-10]: Each byte indicates the Mesh link detection result of the node in the corresponding slot. 00 indicates that the Mesh link is normal, 01 indicates that the Mesh link is disconnected, 02 indicates that the number of lost packets exceeds the threshold, and 04 indicates that the number of error packets exceeds the threshold. type=2: data[3-18]: Every two bytes indicate the Mesh link detection result of the node in the corresponding slot. 00 indicates that the Mesh link is normal, 01 indicates that the Mesh link is disconnected, 02 indicates that the number of lost packets exceeds the threshold, and 04 indicates that the number of error packets exceeds the threshold. type=3: data[3]: iBMA heartbeat information. The value 0 indicates offline, and the value 1 indicates online. The response data is as follows: data[5]: return value of the operation. The value 0 indicates success, and the value 1 indicates failure. data[6]: iBMA heartbeat status of the local node |
| Get Backplane Type (Read Only) | 08h | The response data is as follows: data[5]: backplane type. The value 1 indicates 4U, and the value 2 indicates 8U. |
| Get Node Lsw Status (Read Only) | 09h | data[1]: node slot ID The response data is as follows: data[5]: indicates whether the node Lsw is valid. 0x5A indicates that the node Lsw is valid, and 0xff indicates that the node Lsw is invalid. |
| Get All Node Status (Read Only) | 0Ah | data[1-2]: max_slot_num: maximum number of slots in the current subrack The response data is as follows: Data[5-(5+max_slot_num)]: status of each node. 0x5A indicates that the node is valid, and 0xff indicates that the node is invalid. |
| Get ITF Port Config Mode (Read Only) | 0Bh | The response data is as follows: data[5]: ITF port configuration mode. Description of FC host port modes 0x1: Two 100GE ports form a trunk group, and eight 25GE ports do not form a trunk group. 0x2: Eight 25GE ports form two trunk groups, and each trunk group has four 25GE ports. Two 100GE ports do not form a trunk group. 0x3: 400GE large-bandwidth mode. In this mode, eight 25GE ports form two trunk groups, and each trunk group has four 25GE ports. Two 100GE ports do not form a trunk group. 0x4: 400GE high-bandwidth VLAN full-pass mode. Eight 25GE ports form two trunk groups, and each trunk group has four 25GE ports. Two 100GE ports do not form a trunk group. |
| Get Mesh Health Status (Read Only) | 0Ch | The response data is as follows: Compute node response: data[5]: Mesh card health status. 0x0 indicates that the Mesh card is normal. Other values indicate that the Mesh card is faulty. |
| Get Mesh Type (Read Only) | 0Dh | data[1]: slot ID of the peer board The response data is as follows: data[5]: indicates the type of the mesh card in the peer slot. 0x0: The type of the peer mesh card fails to be obtained. 0x1: No mesh card is available at the peer end. 0x2: The peer mesh card is type 1 (SD6603). 0x3: The peer mesh card is type 2 (SD6605). |
Command Example
Obtain the valid status of an LSW node.
Request:
bash
[root@localhost ~]# ipmicmd -k "0f 00 30 93 DB 07 00 60 01 25" smi 0
00 DB 07 00 5AResponse:
text
[root@localhost ~]# ipmitool raw 0x30 0x95 0xDB 0x07 0x00 0X60 0x0D 0x02
00 Db 07 00 01 01