| README.md (8cfa4c4400201459690c2ec6537df0f9c197f730) | README.md (b69209b498bf9b1c009c528e40280d13e68f8dbd) |
|---|---|
| 1### Sys Commands (0x32) 2 3There are and will be a variety of sys specific commands. 4 5#### Cablecheck - SubCommand 0x00 6 7The cablecheck command checks whether the BMC is seeing traffic between itself 8and the host's NIC. Sys specifies which if_name is expected to be connected. --- 37 unchanged lines hidden (view full) --- 46|0x01|Major|Major version 47|0x02|Minor|Minor Version 48|0x03|Sub 1|Third version number 49|0x04|Sub 2|Fourth version number 50 51**Per the above, if the version number doesn't fit in a byte it'll be cast to 52size.** 53 | 1### Sys Commands (0x32) 2 3There are and will be a variety of sys specific commands. 4 5#### Cablecheck - SubCommand 0x00 6 7The cablecheck command checks whether the BMC is seeing traffic between itself 8and the host's NIC. Sys specifies which if_name is expected to be connected. --- 37 unchanged lines hidden (view full) --- 46|0x01|Major|Major version 47|0x02|Minor|Minor Version 48|0x03|Sub 1|Third version number 49|0x04|Sub 2|Fourth version number 50 51**Per the above, if the version number doesn't fit in a byte it'll be cast to 52size.** 53 |
| 54#### GetNcsiEthDevice - SubCommand 0x02 | 54#### GetEthDevice - SubCommand 0x02 |
| 55 56The BMC itself must have hard-coded into the image, which ethernet device is 57connected to the host NIC. This is true also in the mapping of ethernet device | 55 56The BMC itself must have hard-coded into the image, which ethernet device is 57connected to the host NIC. This is true also in the mapping of ethernet device |
| 58to channel number. The channel number is used to configure the ethernet device | 58to channel number. Alternatively, you can pass a specific interface 59name for channel lookup. The channel number is used to configure the ethernet device |
| 59over IPMI, instead of the interface name. This is because we leverage the 60current IPMI command set to read and write the networking configuration. Sys 61can be programmed already to have this information in the board protobuf, 62however, this information -- can be read from the BMC over IPMI. 63 64Request 65 66|Byte(s) |Value |Data 67|--------|-------|---- 68|0x00|0x02|Subcommand | 60over IPMI, instead of the interface name. This is because we leverage the 61current IPMI command set to read and write the networking configuration. Sys 62can be programmed already to have this information in the board protobuf, 63however, this information -- can be read from the BMC over IPMI. 64 65Request 66 67|Byte(s) |Value |Data 68|--------|-------|---- 69|0x00|0x02|Subcommand |
| 70|0x01... |if_name| (optional) The interface name, not null-terminated |
|
| 69 70Response 71 72|Byte(s) |Value |Data 73|--------|-------|---- 74|0x00|0x02|Subcommand 75|0x01|Channel number|The IPMI channel number for use with the network configuration commands (such as reading the MAC or IP address of the BMC). 76|0x02|if_name length|The length of the if_name in bytes. --- 159 unchanged lines hidden --- | 71 72Response 73 74|Byte(s) |Value |Data 75|--------|-------|---- 76|0x00|0x02|Subcommand 77|0x01|Channel number|The IPMI channel number for use with the network configuration commands (such as reading the MAC or IP address of the BMC). 78|0x02|if_name length|The length of the if_name in bytes. --- 159 unchanged lines hidden --- |