- Notes, cautions, and warnings
- Release summary
- Compatibility
- New and enhanced features
- Fixes
- Important notes
- Known issues — To be fixed in future releases
- Storage devices not found in iDRAC
- Hot-plugged PCIe SSDs not detected
- NIC or FC device slot listed in hardware inventory even when disabled in BIOS
- <Keyboard_Mouse_USB_reset_warning> button in Virtual Console with Java plug-in
- Firmware update job name in Tasks Redfish API showing as "Firmware Update"
- Foreign Preview not found & not able to clear the foreign config on storage controller in iDRAC
- GracefulRestart performs ForcefulRestart in Redfish API
- Get operation not displaying model or serial number for PCIe devices
- IP address missing in iDRAC
- Unable to set Power cap values in Lockdown mode
- Incorrect firmware version displayed after the update
- iDRAC not detecting Virtual disks in eHBA Mode
- Legacy attribute System.Embedded.1#Diagnostics.1#OSAppCollectionTime displays incorrect time
- iDRAC Direct Port accessible even after the port is turned off
- Getting an error while downloading DUP using Redfish interface
- Updates through Redfish Simple Update Transfer Protocol failing
- PERC FRU not displayed using IPMITool FRU commands
- Getting partial screen on online video player
- Disk assignment not reflected in iDRAC GUI even after waiting for about 3-5 minutes
- Unsupported RAID level displayed
- SEL not reporting drive events
- SEL logs in the setup menu and LC logs in the iDRAC GUI not matching
- MaxReadingRange and MinReadingRange for Readingvolts attributes displayed incorrectly
- iDRAC DUP update fails on SLES when the secure boot is enabled
- CPLD update repeats three times
- AC recovery power-on settings not working after installing NVDIMMs
- Boot mode error during OS deployment
- Header error while using Powershell for Redfish requests
- Port 5353 blocked by iDRAC internal firewall and appears as Open|Filtered
- Limitations
- Updating iDRAC firmware
- Lifecycle Controller Remote Services — client tools
- Resources and support
- Contacting Dell EMC
iDRAC9 with Lifecycle Controller Version 3.34.34.34 Release Notes
Port 5353 blocked by iDRAC internal firewall and appears as Open|Filtered
- Description
- When node initiated discovery or Group Manager is enabled, iDRAC uses mDNS to communicate through port 5353. However, when both are disabled, port 5353 is blocked by iDRAC's internal firewall and appears as Open|Filtered port in the port scans.
- Workaround
- Group Manager and node initiated discovery need to be turned off in order to disable mDNS.
- Systems affected
- All systems supported by this release.
- Tracking number
- N/A
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: <>()\