Set LAN Configuration Parameters 命令详情
更新时间：2025/06/26
在Gitcode上查看源码修订记录
| openUBMC版本号 | 修订日期 | 修订人 | 修订内容 |
|---|---|---|---|
| 25.06 | 2025/06/26 | pengqiang-gs | 初稿，新增命令详情 |
基本信息
功能说明
标准命令，通过 LAN 命令设置网络的配置。 This command is used for setting parameters such as the network addressing information required for IPMI LAN operation.
权限
BasicSetting
命令信息
请求信息
| 字节顺序 | 域取值说明 |
|---|---|
| 1 | [7:4] - reserved [3:0] - Channel number. |
| 2 | Parameter selector, per Table LAN Configuration Parameters |
| 3:2+N | Configuration parameter data, per Table LAN Configuration Parameters |
响应信息
| 字节顺序 | 域取值说明 |
|---|---|
| 1 | Completion Code. 80h = parameter not supported. 81h = attempt to set the ‘set in progress’ value (in parameter #0) when not in the ‘set complete’ state. (This completion code provides a way to recognize that another party has already ‘claimed’ the parameters) 82h = attempt to write read-only parameter 83h = attempt to read write-only parameter |
LAN Configuration Parameters
| Parameter | # | Parameter Data (non-volatile unless otherwise noted) |
|---|---|---|
| Set In Progress (volatile) | 0 | data 1 - This parameter is used to indicate when any of the following parameters are being updated, and when the updates are completed. The bit is primarily provided to alert software than some other software or utility is in the process of making changes to the data. An implementation can also elect to provide a ‘rollback’ feature that uses this information to decide whether to ‘roll back’ to the previous configuration information, or to accept the configuration change. If used, the roll back shall restore all parameters to their previous state. Otherwise, the change shall take effect when the write occurs. [7:2] - reserved [1:0] 00b = set complete. If a system reset or transition to powered down state occurs while ‘set in progress’ is active, the BMC will go to the ‘set complete’ state. If rollback is implemented, going directly to ‘set complete’ without first doing a ‘commit write’ will cause any pending write data to be discarded. 01b = set in progress. This flag indicates that some utility or other software is presently doing writes to parameter data. It is a notification flag only, it is not a resource lock. The BMC does not provide any interlock mechanism that would prevent other software from writing parameter data while. 10b = commit write (optional). This is only used if a rollback is implemented. The BMC will save the data that has been written since the last time the ‘set in progress’ and then go to the ‘set in progress’ state. An error completion code will be returned if this option is not supported. 11b = reserved |
| Authentication Type Support (Read Only) | 1 | This ‘read only’ field returns which possible Authentication Types (algorithms) can be enabled for the given channel. The following Authentication Type Enables parameter selects which Authentication Types are available when activating a session for a particular maximum privilege level. [7:6] -reserved [5:0] -Authentication type(s) enabled for this channel (bitfield): All bits: 1b = supported 0b = authentication type not available for use. [5] - OEM proprietary (per OEM identified by the IANA OEM ID in the RMCP Ping Response) [4] - straight password / key [3] - reserved [2] - MD5 [1] - MD2 [0] - none |
| Authentication Type Enables | 2 | This field is used to configure which Authentication Types are available for use when a remote console activates an IPMI messaging connection to the BMC for a given requested maximum privilege level. Once the session has been activated, the accepted authentication type will be the only one used for authenticated packets, regardless of the present operating privilege level, or the privilege level associated with the command. Depending on configuration of per-message and user-level authentication disables, unauthenticated packets (authentication type = none) may also be accepted. The BMC makes no attempt to check or ensure that stricter authentication types are associated with higher requested maximum privilege levels. E.g. it is possible to configure the BMC so activating a session with a maximum privilege level of ‘User’ requires MD5 while ‘Admin’ requires ‘none’. Note: An implementation that has fixed privilege and authentication type assignments, in which case this parameter can be implemented as Read Only. It is recommended that an implementation that implements a subset of the possible authentication types returns a CCh error completion code if an attempt is made to select an unsupported authentication type. byte 1: Authentication Types returned for maximum requested privilege = Callback level. [7:6] -reserved [5:0] -Authentication type(s) enabled for this channel (bitfield): All bits: 1b = authentication type enabled for use at given privilege level 0b = authentication type not available for use at given privilege level. [5] - OEM proprietary (per OEM identified by the IANA OEM ID in the RMCP Ping Response) [4] - straight password / key [3] - reserved [2] - MD5 [1] - MD2 [0] - none byte 2: Authentication Type(s) for maximum privilege = User level (format follows byte 1) byte 3: Authentication Type (s) for maximum privilege = Operator level (format follows byte 1) byte 4: Authentication Type (s) for maximum privilege = Administrator level (format follows byte 1) byte 5: Authentication Type (s) for maximum privilege = OEM level (format follows byte 1) |
| IP Address | 3 | data 1:4 - IP Address, MS-byte first. |
| IP Address Source | 4 | data 1 [7:4] -reserved [3:0] -address source 0h = unspecified 1h = static address (manually configured) 2h = address obtained by BMC running DHCP 3h = address loaded by BIOS or system software 4h = address obtained by BMC running other address assignment protocol |
| MAC Address (can be Read Only) | 5 | data 1:6 - MAC Address for messages transmitted from BMC. MS-byte first. An implementation can either allow this parameter to be settable, or it can be implemented as Read Only. |
| Subnet Mask | 6 | data 1:4 - Subnet Mask. MS-byte first |
| IPv4 Header Parameters | 7 | data 1 - Time-to-live. 1-based. (Default = 40h) Value for time-to-live parameter in IP Header for RMCP packets and PET Traps transmitted from this channel. data 2 [7:5] - Flags. Sets value of bit 1 in the Flags field in the IP Header for packets transmitted by this channel. (Default = 010b “don’t fragment”) [4:0] - reserved data 3 [7:5] - Precedence (Default = 000b) [4:1] - Type of Service (Default = 1000b, “minimize delay”) [0] - reserved |
| Primary RMCP Port Number (optional) | 8 | data 1:2 - Primary RMCP Port Number, LSByte first. Default = 26Fh (RMCP ‘Aux Bus Shunt’ port) |
| Secondary RMCP Port Number (optional) | 9 | data 1:2 - Secondary Port Number, LSByte first. Default = 298h (RMCP ‘Secure Aux Bus’ port) |
| BMC-generated ARP control (optional) | 10 | data 1 - BMC-generated ARP control. Note: the individual capabilities for BMC-generated ARP responses and BMC-generated Gratuitous ARPs are individually optional. The BMC should return an error completion code if an attempt is made to enable an unsupported capability. [7:2] - reserved [1] 1b = enable BMC-generated ARP responses 0b = disable BMC-generated ARP responses [0] 1b = enable BMC-generated Gratuitous ARPs 0b = disable BMC-generated Gratuitous ARPs |
| Gratuitous ARP interval (optional) | data 1 - Gratuitous ARP interval Gratuitous ARP interval in 500 millisecond increments. 0-based. Interval accuracy is +/- 10%. If this configuration parameter is not implemented, gratuitous ARPs shall be issued at a rate of once every 2 seconds. | |
| Default Gateway Address | 12 | data 1:4 - IP Address, MS-byte first. This is the address of the gateway (router) used when the BMC sends a message or alert to a party on a different subnet than the one the BMC is on. |
| Default Gateway MAC Address | 13 | data 1:6 - MAC Address. MS-byte first. |
| Backup Gateway Address | 14 | data 1:4 - IP Address, MS-byte first. This is the address of an alternate gateway (router) that can be selected when a sending a LAN Alert. |
| Backup Gateway MAC Address | 15 | data 1:6 - MAC Address. MS-byte first. |
| Community String | 16 | data 1:18 - Community String. Default = ‘public’. Used to fill in the ‘Community String’ field in a PET Trap. This string may optionally be used to hold a vendor-specific string that is used to provide the network name identity of the system that generated the event. Printable ASCII string-. If a full 18 non-null characters are provided, the last character does not need to be a null. 18 characters must be written when setting this parameter, and 18 will be returned when this parameter is read. The null character, and any following characters, will be ignored when the Community String parameter is placed into the PET. The BMC will return whatever characters were written. I.e. it will not set bytes following the null to any particular value. |
| Number of Destinations (Read Only) | 17 | data 1 - Number of LAN Alert Destinations supported on this channel. (Read Only). At least one set of non-volatile destination information is required if LAN alerting is supported. Additional non-volatile destination parameters can optionally be provided for supporting an alert ‘call down’ list policy. A maximum of fifteen (1h to Fh) non-volatile destinations are supported in this specification. Destination 0 is always present as a volatile destination that is used with the Alert Immediate command. [7:4] - reserved. [3:0] - Number LAN Destinations. A count of 0h indicates LAN Alerting is not supported. |
| Destination Type (volatile / non-volatile) | 18 | Sets the type of LAN Alert associated with the given destination. This parameter is not present if the Number of Destinations parameter is 0. data 1 - Set Selector = Destination selector, 0 based. [7:4] -reserved [3:0] -Destination selector. Destination 0 is always present as a volatile destination that is used with the Alert Immediate command. data 2 - Destination Type [7] - Alert Acknowledge. 0b = Unacknowledged. Alert is assumed successful if transmission occurs without error. This value is also used with Callback numbers. 1b = Acknowledged. Alert is assumed successful only if acknowledged is returned. Note, some alert types, such as Dial Page, do not support an acknowledge. [6:3] -reserved [2:0] -Destination Type 000b = PET Trap destination 001b - 101b = reserved 110b = OEM 1 111b = OEM 2 data 3 - Alert Acknowledge Timeout / Retry Interval, in seconds, 0-based (i.e. minimum timeout = 1 second). This value sets the timeout waiting for an acknowledge, or the time between automatic retries depending on whether the alert is acknowledge or not. Recommended factory default = 3 seconds. Value is ignored if alert type does not support acknowledge, or if the Alert Acknowledge bit (above) is 0b. data 4 - Retries [7:4] - reserved [3] - reserved [2:0] - Number of times to retry alert to given destination. 0 = no retries (alert is only sent once). If the alert is acknowledged (Alert Acknowlege bit = 1b) the alert will only be retried if a timeout occurs waiting for the acknowledge. Otherwise, this value selects the number of times an unacknowledged alert will be sent out. The timeout interval or time between retries is set by the Alert Acknowledge Timeout / Retry Interval value (byte 3 of this parameter). |
| Destination Addresses | 19 | Sets/Gets the list of IP addresses that a LAN alert can be sent to. This parameter is not present if the Number of Destinations parameter is 0. data 1 - Set Selector = Destination Selector. [7:4] -reserved [3:0] -Destination selector. Destination 0 is always present as a volatile destination that is used with the Alert Immediate command. data 2 - Address Format [7:4] - Address Format. 0h = IPv4 IP Address followed by DIX Ethernet/802.3 MAC Address 1h = IPv6 IP Address [3:0] - reserved For Address Format = 0h: data 3 - Gateway selector [7:1] - reserved [0] 0b = use default gateway first, then backup gateway (Note: older implementations (errata 4 or earlier) may only send to the default gateway.) 1b = use backup gateway data 4:7 - Alerting IP Address (MS-byte first) data 8:13 - Alerting MAC Address (MS-byte first) For Address Format = 1h: data 3:18 - Alerting IPv6 Address (MS-byte first) (Router MAC Address is obtained through Neighbor Discovery or using the addressing specified using static router configuration in the LAN Configuration Parameters) |
| 802.1q VLAN ID (12-bit) | 20 | data 1 [7:0] - Least significant 8-bits of the VLAN ID. 00h if VLAN ID not used. data 2 [7] - VLAN ID enable. 0b = disabled, 1b = enabled. If enabled, the BMC will only accept packets for this channel if they have 802.1q fields and their VLAN ID matches the VLAN ID value given in this parameter. [6:4] - reserved [3:0] - most significant four bits of the VLAN ID |
| 802.1q VLAN Priority | 21 | data 1 [7:3] - reserved [2:0] - Value for Priority field of 802.1q fields. Ignored when VLAN ID enable is 0b (disabled) - See 802.1q VLAN ID parameter, above. Setting is network dependent. By default, this should be set to 000b. |
| RMCP+ Messaging Cipher Suite Entry Support (Read Only) | 22 | This parameter provides a count of the number (16 max.) of Cipher Suites available to be enabled for use with IPMI Messaging on the given channel. Software can find out what security algorithms are associated with given Cipher Suite ID by using the Get Channel Cipher Suites command. In addition, there are Cipher Suite IDs assigned for standard Cipher Suites (see Table 22-19, Cipher Suite IDs) data 1 [7:5] - reserved [4:0] - Cipher Suite Entry count. Number of Cipher Suite entries, 1-based, 10h max. |
| RMCP+ Messaging Cipher Suite Entries (Read Only) | 23 | This parameter contains zero to sixteen (16) bytes of Cipher Suite IDs for Cipher Suites that can be used for establishing an IPMI messaging session with the BMC. The number of Cipher Suites that are supported is given in the preceding parameter. data 1 - Reserved data 2 - Cipher Suite ID entry A. data 3 - Cipher Suite ID entry B. ... data 17 - Cipher Suite ID entry P. |
| RMCP+ Messaging Cipher Suite Privilege Levels | 24 | This parameter allows the configuration of which privilege levels are associated with each Cipher Suite. The total number of nibbles supported (zero to sixteen) matches the number of fixed Cipher Suite IDs. data 1 - Reserved data 2 - Maximum Privilege Level for 1st and 2nd Cipher Suites [7:4] - Maximum Privilege Level for 2nd Cipher Suite [3:0] - Maximum Privilege Level for 1st Cipher Suite 0h = Unspecified (given Cipher Suite is unused) 1h = Callback level 2h = User level 3h = Operator level 4h = Administrator level 5h = OEM Proprietary level data 3 - Maximum Privilege Level for 3rd and 4th Cipher Suites data 4 - Maximum Privilege Level for 5th and 6th Cipher Suites … data 9 - Maximum Privilege Level for 15th and 16th Cipher Suites |
| Destination Address VLAN TAGs (can be READ ONLY) | 25 | Sets/Gets the VLAN IDs (if any) addresses that a LAN alert can be sent to. This parameter is not present if the Number of Destinations parameter is 0, or if the implementation does not support the use of VLAN IDs for alerts. Otherwise, the number of VLAN TAG entries matches the number of Alert Destinations. An implementation may only be able to send alerts using the same VLAN TAG configuration as specified by parameters 20 and 21, in which case this parameter is allowed to be READ ONLY, where data 3-4 reflects the settings of parameters 20 and 21, and data 2 [7:4] indicates that VLAN TAGs are being used for alerts. If the implementation does support configurable VLAN TAGs for alert destinations, it must support configuring unique TAG information for all destinations on the given channel. data 1 - Set Selector = Destination Selector. [7:4] -reserved [3:0] -Destination selector. Destination 0 is always present as a volatile destination that is used with the Alert Immediate command. data 2 - Address Format [7:4] - Address Format. 0h = VLAN ID not used with this destination 1h = 802.1q VLAN TAG [3:0] - reserved For Address Format = 1h: data 3-4 - VLAN TAG [7:0] - VLAN ID, least-significant byte [11:8] - VLAN ID, most-significant nibble [12] - CFI (Canonical Format Indicator. Set to 0b) [15:13] - User priority (000b, typical) |
| Bad Password Threshold (optional) | 26 | Sets/Gets the Bad Password Threshold. If implemented and non-zero, this value determines the number of sequential bad passwords that will be allowed to be entered for the identified user before the user is automatically disabled from access on the channel. For example, a value of 3 indicates that 3 sequential attempts are allowed for the given username on the particular channel. If the password for the third attempt is not correct, the user will be disabled for the channel. If this value is zero (00h) then there is no limit on bad passwords. The effect of the disable is the same as if a Set User Access command were used to remove the user's access from the channel. Bad password attempts are tracked according to individual username on a per channel basis. (Thus, a given username may be disabled on one channel, but still enabled on another) Bad password attempts are not counted if integrity check or other session parameters, such as session ID, sequence number, etc. are invalid. That is, bad password attempts are not counted if there are any other errors that would have caused the login attempt to be rejected even if the password was valid. The count of bad password attempts is retained as long as the BMC remains powered and is not reinitialized. Counting automatically starts over (is reset) under any one of the following conditions: a) a valid password is received on any of the allowed attempts b) the Attempt Count Reset Interval expires c) the user is re-enabled using the Set User Access command d) the user is automatically re-enabled when the User Lockout Interval expires. e) the Bad Threshold number parameter value is re-written or changed The Set User Access command is used to re-enable the user for the Channel. data 1 [7:1] - reserved [0] 0b = do not generate an event message when the user is disabled. 1b = generate a Session Audit sensor "Invalid password disable" event message. data 2 [7:0] - Bad Password Threshold number. data 3:4 [15:0] - Attempt Count Reset Interval. The interval, in tens of seconds, for which the accumulated count of bad password attempts is retained before being automatically reset to zero. The interval starts with the most recent bad password attempt for the given username on the channel. This interval is allowed to reset if a BMC power cycles or re-initialization occurs while the interval is being counted. 0000h = Attempt Count Reset Interval is disabled. The count of bad password attempts is retained as long as the BMC remains powered and is not reinitialized. data 5:6 [15:0] - User Lockout Interval. The interval, in tens of seconds, that the user will remain disabled after being disabled because the Bad Password Threshold number was reached. The user is automatically re-enabled when the interval expires. Note that this requires the BMC implementation to track that the user was disabled because of a Bad Password Threshold. This interval is allowed to be restarted if a BMC power cycle or re-initialization occurs while the interval is being counted. Note that this requires an internal non-volatile setting to be maintained that tracks when a particular user has been temporarily disabled due to the Bad Password Threshold. This is required to distinguish a user that was disabled automatically from a user that is intentionally disabled using the Set User Access command. 0000h = User Lockout Interval is disabled. If a user was automatically disabled due to the Bad Password threshold, the user will remain disabled until re-enabled via the Set User Access command. |
| IPv6/IPv4 Support (read only) | 50 | This parameter is Mandatory if IPv6 addressing is supported. This parameter and the following parameters, up to and including the “IPv6 Neighbor Discovery / SLAAC Timing Configuration” parameter should not be supported if the implementation does not support IPv6 addressing per this specification. data 1 – [2] -1b = Implementation supports IPv6 Destination Addresses for LAN Alerting. [1] -1b = Implementation can be configured to use both IPv4 and IPv6 addresses simultaneously. [0] -1b = Implementation can be configured to use IPv6 addresses only. |
| IPv6/IPv4 Addressing enables | 51 | This parameter is Mandatory if IPv6 addressing is supported. data 1 – The following values can be set according the capabilities specified in parameter 50. 00h = IPv6 addressing disabled. 01h = Enable IPv6 addressing only. IPv4 addressing is disabled. 02h = Enable IPv6 and IPv4 addressing simultaneously. |
| IPv6 Header Static Traffic Class | 52 | This parameter is Mandatory if IPv6 addressing is supported. Recommended Default = 0. data 1 – Traffic Class This field determines the Traffic Class used by the BMC when transmitting Alert packets using IPv6 addressing. Otherwise, the BMC uses the traffic class value from the remote console. Refer to [RFC2460] and [RFC2474] for additional information. |
| IPv6 Header Static Hop Limit | 53 | This parameter is Mandatory if IPv6 addressing is supported. Default = 64. data 1 – Static Hop Limit This parameter is used under two circumstances: 1. If the router returns ‘unspecified’ (00h) as the hop limit. 2. When a static router configuration is used, the BMC does not pay attention to the Router Advertisement messages and uses this value for the Hop Limit instead. |
| IPv6 Header Flow Label [OPTIONAL] | 54 | data 1:3 – Flow Label, 20-bits, right justified, MS Byte first. Default = 0. If this configuration parameter is not supported, the Flow Label shall be set to 0 per [RFC2460]. Bits [23:20] = reserved – set to 0b |
| IPv6 Status (read only) | 55 | Provides the number of IPv6 addresses that are supported and configurable for use by the BMC for IPMI. This parameter is Mandatory if IPv6 addressing is supported. data 1: - Static address max Maximum number of static IPv6 addresses for establishing connections to the BMC. Note: in some implementations this may exceed the number of simultaneous sessions supported on the channel. 0 indicates that static address configuration is not available. data 2: - Dynamic address max Maximum number of Dynamic (SLAAC/ DHCPv6) IPv6 addresses that can be obtained for establishing connections to the BMC. Note: in some implementations this may exceed the number of simultaneous sessions supported on the channel. 0 = Dynamic addressing is not supported by the BMC. data 3: - [7:2] - reserved [1] -1b = SLAAC addressing is supported by the BMC [0] - 1b = DHCPv6 addressing is supported by the BMC (optional) |
| IPv6 Static Addresses | 56 | This parameter is Mandatory if IPv6 addressing is supported. data 1 - Set Selector = Address selector, 0 based. BMC shall provide at least one IPv6 Static Address entry if static address configuration is supported. For the case of 0 Static addresses, only selector 0 is allowed, data[2:19] are reserved, data 20 = “disabled”. data 2 - Address source/type [7]- enable=1/disable=0 [6:4] - reserved [3:0]- source/type 0h = Static All other = reserved data 3:18 - IPv6 Address, MS-byte first. data 19 - Address Prefix Length data 20 - Address Status (Read-only parameter. Writes to this location are ignored.) 00h = Active (in-use) 01h = Disabled 02h = Pending (currently undergoing DAD [duplicate address detection], optional) 03h = Failed (duplicate address found, optional) 04h = Deprecated (preferred timer has expired, optional) 05h = Invalid (validity timer has expired, optional) All other = reserved |
| IPv6 DHCPv6 Static DUID storage length (read only) | 57 | This parameter is Mandatory if IPv6 addressing is supported. data 1 – The maximum number of 16-byte blocks that can be used for storing each DUID via the IPv6 DHCPv6 Static DUIDs parameter. 1-based. Returns 0 if IPv6 Static Address configuration is not supported. Per [RFC3315] the first two bytes hold a DUID Type Number. The following bytes hold the DUID data. Depending on the Type, the DUID data can be up to 128 octets long (not including the 2-byte type code) – though most forms are significantly shorter. As of this writing, DUID Type 2 (Vendor-assigned unique ID based on Enterprise Number is the one Type that has a vendor-specific length and could be 128 octets long). It is recommended that the implementation supports at least 3 blocks per DUID. |
| IPv6 DHCPv6 Static DUIDs | 58 | DUIDs (DHCP Unique Identifiers). Per [RFC3315], each DHCP client and server has a DUID. This parameter provides storage for each DUID that identifies a particular IPv6 Interface Association (IA). This parameter is Mandatory if IPv6 addressing is supported. data 1 - Set Selector = DUID selector, 0 based. Each set selector matches with the corresponding Set Selector for the IPv6 Static Addresses parameter. This parameter is Mandatory if IPv6 addressing is supported. If IPv6 Static Address configuration is not supported, only selector 0 and block 0 is allowed and nothing is returned for data 3-18. data 2 - Block Selector, 0-based Selects which 16-byte block of DUID data to write for the DUID storage from the given Set Selector. data 3-18 - DUID data for given block. The first byte of block 0 is the overall length of the following DUID data (1-based). The remaining DUID data is formatted and stored in network byte order (MS-bytes first) per [RFC3315], starting with the DUID Type field. Notes: Per [RFC3315]: “A client must associate at least one distinct IA with each of its network interfaces for which it is to request the assignment of IPv6 addresses from a DHCP server. The client uses the IAs assigned to an interface to obtain configuration information from a server for that interface. Each IA must be associated with exactly one interface.” Consequently, the Set Selector for the DUID effectively becomes bound to a particular IA, and since the Set Selector for the DUID and the Set Selector for the IPv6 Address correspond to one another, the Set Selector for the IPv6 address is also associated with the IA. In effect, the Set Selector value becomes the handle for a particular IA. Depending on DUID Type, a given MAC address MAY have more than one DUID (and IPv6 Address) associated with it. The Type 3 DUID just uses the link layer address directly (MAC address) and therefore would not support more than one DUID for the MAC address. Other DUID Types do not have that restriction. |
| IPv6 Dynamic (SLAAC/DHCPv6) Address (read only) | 59 | This parameter is Mandatory if IPv6 addressing is supported. data 1 - Set Selector = Address selector, 0 based. BMC shall provide at least one entry in the array. For the case of 0 SLAAC and DHCPv6 addresses, only selector 0 is allowed, data[2:20] are reserved, data 21 = “disabled”. Mandatory if IPv6 addressing is supported. data 2 - Address source/type [7:4] - reserved [3:0]- source/type 0 – Reserved 1 – SLAAC (StateLess Address Auto Configuration) 2 – DHCPv6 (optional) Other - reserved data 3-18 - IPv6 Address, MS-byte first. data 19 - Address Prefix Length data 20 - Address Status 0 – Active (in-use) 1 – Disabled 2 – Pending (currently undergoing DAD, optional) 3 – Failed (duplicate address found, optional) 4 – Deprecated (preferred timer has expired, optional) 5 – Invalid (validity timer has expired, optional) other – reserved |
| IPv6 DHCPv6 Dynamic DUID storage length (read only) | 60 | This parameter is Mandatory if IPv6 addressing is supported. data 1 – The maximum number of 16-byte blocks that can be used for storing each DUID via the IPv6 DHCPv6 Static DUIDs parameter. 1-based. Returns 0 if IPv6 Static Address configuration is not supported. Per [RFC3315] the DUID can be up to 128 octets long – though most forms are significantly shorter. As of this writing, DUID Type 2 (Vendor-assigned unique ID based on Enterprise Number) is the format which has a vendor-specific length and could be lengthy It is recommended that the implementation supports at least 3 blocks per DUID |
| IPv6 DHCPv6 Dynamic DUIDs | 61 | This parameter is Mandatory if IPv6 addressing is supported. DUIDs (DHCP Unique Identifiers). Per [RFC3315], each DHCP client and server has a DUID. Although DHCPv6 is not used for address assignment when IPv6 static addresses are enabled, DHCPv6 may be used for discovery, configuration, or other purposes. Therefore, this configuration parameter provides a mechanism for setting and returning a DUID that is associated with each IPv6 Static Address that is supported. The Set Selector for the Dynamic DUIDs Type parameter matches the set selector for the corresponding IPv6 Static address. . If IPv6 Dynamic Address configuration is not supported, only selector 0 and block 0 is allowed and nothing is returned for data 3-18. data 1 - Set Selector = DUID selector, 0 based. Each set selector matches with the corresponding Set Selector for the IPv6 Dynamic Addresses parameter. This parameter is Mandatory if IPv6 addressing is supported. If IPv6 Dynamic Address configuration is not supported, only selector 0 is allowed and the type shall be returned as ‘0’ (not supported). data 2 - Block Selector (0-based) Selects which 16-byte block of DUID data to write for the DUID storage from the given Set Selector. data 3-18 - DUID data for given block. The first byte of block 0 is the overall length of the following DUID data (1-based). The remaining DUID data is formatted and stored in network byte order (MS-bytes first) per [RFC3315], starting with the DUID Type field. Notes: Refer to the notes for the IPv6 DHCPv6 Static DUIDs parameter, above, for more information. |
| IPv6 DHCPv6 Timing Configuration Support (read only) | 62 | This parameter is Mandatory if IPv6 addressing is supported. data1 [7:2] - reserved [1:0] 00b = DHCPv6 timing configuration per IPMI is not supported. 01b = ‘Global’ - Timing configuration applies across all interfaces (IAs) that use dynamic addressing and have DHCPv6 is enabled. 10b = ‘Per interface’ - Timing is configurable for each interface and used when DHCPv6 is enabled for the given interface (IA). 11b = reserved |
| IPv6 DHCPv6 Timing & Configuration (optional, recommended) | 63 | This parameter is Mandatory if DHCPv6 timing configuration is supported as indicated by the IPv6 DHCPv6 Timing Configuration Support parameter, above. If DHCPv6 Dynamic Address configuration is not supported, this parameter should not be implemented. This parameter is used to configure the default timing values for DHCPv6. These values are used when the BMC is initially powered up or reinitialized, and after DHCPv6 address configuration becomes enabled or is re-enabled. Note that some of these parameters may be superseded by values received from the DHCP server. See DHCPv6 Timing Parameters. The DHCPv6 Timing configuration can be ‘global’, where a single set of timing parameters applies to all DHCPv6 transactions for all supported interfaces on the channel that are using DCHPv6 for IPv6 address assignment on the channel or ‘per interface’ in which case only one set of timing parameters needs to be supported. The IPv6 DHCPv6 Timing Configuration Support parameter lets software know what is supported by the implementation. data 1 - Set Selector = IPv6 interface (IA) selector, 0 based. If ‘global’ the Set Selector is always 0. If ‘per interface’, each set selector matches with the corresponding Set Selector for the IPv6 Dynamic Addresses parameter. data 2 - Block Selector (0-based) Selects which 16-byte block of timing parameter data is accessed for the given Set Selector. See DHCPv6 Timing Parameters, for the specification of the data content in each block. |
| IPv6 Router Address Configuration Control | 64 | This parameter is Mandatory if IPv6 addressing is supported. Router discovery is part of support for SLAAC and DHCPv6 addressing (dynamic addressing). This parameter controls whether automated router discovery occurs when static addresses are used for the BMC. It also enables the use of static router addresses. data 1 – [7:2] - reserved [1] - 1b = enable dynamic router address configuration via router advertisement messages. Router solicitation messages are sent with timing and behavior as specified in [RFC4861]. The router solicitation timing values from the IPv6 Neighbor Discovery / SLAAC Timing Configuration parameter (below) are used if that parameter is implemented. [0] - 1b = enable static router address. If static and dynamic router addressing are enabled, the BMC shall attempt to use the static router address and prefix first. |
| IPv6 Static Router 1 IP Address | 65 | This parameter is Mandatory if IPv6 addressing is supported. data 1:16 - IPv6 Router IP Address (Used when static address is selected in the IPv6 IP Address Source configuration parameter). 16 bytes of IPv6 address, MS-byte first. |
| IPv6 Static Router 1 MAC Address | 66 | This parameter is Mandatory if IPv6 addressing is supported. data 1:6 – Router MAC Address. MS-byte first. |
| IPv6 Static Router 1 Prefix Length | 67 | This parameter is Mandatory if IPv6 addressing is supported. data 1 – Prefix length. Only used with static addressing. Used to determine whether an address is ‘on link’ (can be accessed directly) or ‘off link’ (must go to the corresponding Static Gateway address). The upper bits of the first address entry in the IPv6 Static Addresses parameter are used for the prefix value. Prefix length should be from 0 to 128 as per [RFC4861]. |
| IPv6 Static Router 1 Prefix Value | 68 | This parameter is Mandatory if IPv6 addressing is supported data1:16 – Prefix value. MS-byte first. |
| IPv6 Static Router 2 IP Address | 69 | This parameter is Mandatory if IPv6 addressing is supported. data 1:16 - IPv6 Static Router Address (Used when static address is selected in the IPv6 IP Address Source configuration parameter). 16 bytes of valid IPv6 address, MS-byte first. |
| IPv6 Static Router 2 MAC Address | 70 | This parameter is Mandatory if IPv6 addressing is supported. data 1:6 - MAC Address. MS-byte first. |
| IPv6 Static Router 2 Prefix Length | 71 | This parameter is Mandatory if IPv6 addressing is supported. data 1 – Prefix length. Only used with static addressing. Used to determine whether an address is ‘on link’ (can be accessed directly) or ‘off link’ (must go to the corresponding Static Gateway address). The upper bits of the first address entry in the IPv6 Static Addresses parameter are used for the prefix value. Prefix length should be from 0 to 128 as per [RFC4861]. |
| IPv6 Static Router 2 Prefix Value | 72 | This parameter is Mandatory if IPv6 addressing is supported. data1:16 – Prefix value. MS-byte first. |
| Number of Dynamic Router Info Sets (read-only) | 73 | This parameter is Mandatory if IPv6 dynamic addressing is supported. data1- Number of dynamic Router Address information entries. If a router returns multiple prefixes, there will be a one set of entries (prefix, router ip address, and router mac address) for each prefix. Entries are handled in a FIFO manner. That is, once all entries are used, the BMC replaces older sets with newer ones in the order that they are received if the new information doesn’t match an entry that’s already on the list. Set to 0 if dynamic Router Address information entries are not supported. Otherwise, the required minimum = 2. Recommended: 4 entries, min. This allows the BMC to track two router addresses and two prefixes per router address. Note that per [RFC4861] “a host MUST retain at least two router addresses and SHOULD retain more.” The implementation should provide one info set for each router address + prefix it supports. |
| IPv6 Dynamic Router Info IP Address (read-only) | 74 | This parameter is Mandatory if Number of Dynamic Router Info Sets is non-zero. data1 - set selector (0-based) data 2:17- IPv6 Router IP Address (Used when static address is selected in the IPv6 IP Address Source configuration parameter). 16 bytes of valid IPv6 address, MS-byte first. Set to 0000_0000h if the corresponding IPv6 Dynamic Router Info Prefix Length = FFh. |
| IPv6 Dynamic Router Info MAC Address (read-only) | 75 | This parameter is Mandatory if Number of Dynamic Router Info Sets is non-zero. data 1 - set selector (0-based) data 2:7 - MAC Address. MS-byte first. Set to 00_0000h if the corresponding IPv6 Dynamic Router Info Prefix Length = FFh. |
| IPv6 Dynamic Router Info Prefix Length (read-only) | 76 | This parameter is Mandatory if Number of Dynamic Router Info Sets is non-zero. data1 - set selector (0-based) data 2 – Prefix length. Used with dynamic router address configuration. Used to determine whether an address is ‘on link’ (can be accessed directly) or ‘off link’ (must go to the corresponding Dynamic Router address). The upper bits of the first address entry in the IPv6 Static Addresses parameter are used for the prefix value. Prefix length should be from 0 to 128 as per [RFC4861]. FFh = Dynamic address is unspecified. The corresponding IPv6 Dynamic Router Info IP Address and MAC Address fields should be ignored. |
| IPv6 Dynamic Router Info Prefix Value (read-only) | 77 | This parameter is Mandatory if Number of Dynamic Router Info Sets is non-zero. data1- set selector (0-based) data 2:17 – Prefix value. Set to all 0s if the corresponding IPv6 Dynamic Router Info Prefix Length = FFh. |
| IPv6 Dynamic Router Received Hop Limit (read only) [optional, recommended] | 78 | This parameter is optional (recommended). This value is obtained from the router as part of a Router Advertisement message. The BMC returns the most recently received information that it has received, regardless of the router that sent the advertisement. data 1 – Hop Limit |
| IPv6 Neighbor Discovery / SLAAC Timing Configuration Support (read only) | 79 | This parameter is Mandatory if IPv6 static router address configuration is supported. data1: [7:2] - reserved [1:0] 00b = IPv6 Neighbor Discovery / SLAAC timing configuration per IPMI is not supported. 01b = ‘Global’ - Timing configuration applies across all interfaces (IAs) that have IPv6 dynamic addressing enabled. 10b = ‘Per interface’ - Timing is configurable for each interface and used when IPv6 dynamic addressing is enabled for the given interface (IA). 11b = reserved |
| IPv6 Neighbor Discovery / SLAAC Timing Configuration | 80 | This parameter is Mandatory if Neighbor Discovery / SLAAC Timing configuration is supported. If it is not supported, this parameter is not implemented. This parameter is used to configure the default timing values for IPv6 Neighbor Discovery / SLAAC. These values are used when the BMC is initially powered up or reinitialized, and after IPv6 dynamic addressing becomes enabled or is re-enabled for the interface(s). Note that some of these parameters may be superseded by values received from the router. See Section 23.2b, Neighbor Discovery / SLAAC Timing Parameters, for more information. The Neighbor Discovery / SLAAC Timing configuration can be ‘global’, where a single set of timing parameters applies to all Neighbor Discovery / SLAAC transactions for all supported interfaces on the channel that are using Neighbor Discovery / SLAAC for IPv6 address assignment on the channel or ‘per interface’ in which case only one set of timing parameters needs to be supported. The IPv6 Neighbor Discovery / SLAAC Timing Configuration Support parameter lets software know what is supported by the implementation. data 1: - Set Selector = IPv6 interface (IA) selector, 0 based. If ‘global’ the Set Selector is always 0. If ‘per interface’, each set selector matches with the corresponding Set Selector for the IPv6 Dynamic Addresses parameter. data 2: - Block Selector (0-based) Selects which 16-byte block of timing parameter data is accessed for the given Set Selector. See Table Neighbor Discovery / SLAAC Timing Parameters for the specification of the data content in each block. |
| OEM Parameters | 192:255 | This range is available for special OEM configuration parameters. The OEM is identified according to the Manufacturer ID field returned by the Get Device ID command. |
命令样例
样例1：
- 请求：
- 响应：