- Notes, cautions, and warnings
- iDRAC9 Release Notes
- Revision History
- Product description
- New features
- Resolved Issues
- Known issues
- Limitations
- Environmental and system requirements
- Installation and upgrade considerations
- Where to get help
iDRAC9 Version 6.10.00.00 Release Notes
Networking and IO
- During a DPU (Smart NIC) firmware update, SUP0516 message about firmware update is logged in Lifecycle (LC) Logs before the system restart log (SYS1000). The actual firmware update is applied at Post while the host system is powering on.
- Firmware version for DPU cards on iDRAC Overview page (Network Devices section) may vary with the version that is displayed on the Firmware Inventory page. Use the version that is displayed on the Firmware Inventory page.
- iDRAC may display some unsupported attributes such as PCIeOfflineOnlineFQDDList, SerialNumber, PermanentMACAddress, CSP Mode and DPUOSDeploymentTaskState for DPUs when GET is performed on the iDRAC attribute registry. These attributes are expected to be removed from the iDRAC code in an upcoming release.
- iDRAC IPv6 auto-generated addresses change to stable-privacy assigned addressing when iDRAC is upgraded to firmware version 5.10.00.00 (or later) from any previous iDRAC versions.
- In a SCP import job for enabling NPAR on a network port, if all partitions are not required then ensure that you apply the SCP import twice. Once to enable the NPAR on the port and the second time to disable the partitions that are not required.
- For partition enabled COMMs adapter, a PR6 Lifecycle Log message may be displayed as partition-1 even though the values are configured as other than first partition.
- When auto negotiation is disabled while iDRAC is in Shared LOM mode, the speed and duplex values shown in the GUI and RACADM output may not accurately show the actual speed and duplex on the link.
- In systems with network adapters without internal temperature sensors, for some adapters the NIC temperature sensors metric value is reported as 0.
- After iDRAC is upgraded to versions 4.xx or later for the first time, there may be a change in network settings option including IPv4 and IPv6. Reconfigure the network settings to resolve this.
- If the network is not configured and you try to perform a network operation in LC, a warning message is displayed. When you go to the network settings page from this message, the left navigation panel on network settings page may not be displayed.
- If a network operation fails for a valid address, try configuring the network settings again. If the issue persists, restart the system and retry the operation.
- Fibre-channel NIC cards with dual or four ports are displayed as a single port card in LC. However, all ports are updated when a firmware update is performed.
- If SMBv2 share fails in Lifecycle GUI, ensure that:
- The Digitally sign communications option is disabled.
- Permissions to access the folder or file is granted.
- folder/file name does not have a space.
- Share contains fewer files and folders.
- While iDRAC is initializing, all communications with iDRAC may fail. For any service requests, wait until the initialization process is complete.
- In iDRAC, if there is no link that is detected in the selected iDRAC port then the iDRAC IP is displayed as 0.0.0.0.
- FRU objects or properties for Network adapters that are embedded on the motherboard are not available through any of the iDRAC interfaces.
- The iDRAC feature “Topology LLDP” is not supported on 1 GbE controllers and on selected 10 GbE controllers (Intel X520, QLogic 578xx).
- Mellanox network adapters that are used in PowerEdge MX740c and MX840c servers must be updated to version 14.23.10.20 or later, before updating the iDRAC firmware to version 4.xx or later.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\