Users Guide
Unsupported features with IPv6 protocol
The features that are not supported when iSM is congured with IPv6 protocol and IPv4 conguration is not available on the USBNIC
interface are:
• InBand iDRAC Access
• iDRAC GUI Launcher
• iDRAC SSO Launcher
• idrac.local and drac.local
• Auto-update of iSM
Enhanced security between iSM and iDRAC
communication using TLS protocol
Starting iSM 3.4, the data communication between iSM and iDRAC happens through TLS protected USBNIC INET sockets. This ensures
protection of all the data that transports from iDRAC to iSM over USBNIC. iSM and iDRAC use self-signed certicates to control
Authentication. The self-signed certicates have 10 years of validity. Fresh self-signed certicates are generated while installing iSM every
time. Reinstall or upgrade iSM if the certicates expire.
NOTE: iSM reinstall (repair) does not work on Linux operating systems. It is mandatory to uninstall and then install iSM on Linux
operating systems.
NOTE: When iSM's TLS (client) certicate expires, then communication between iSM and iDRAC fails and an OS audit log is
generated indicating the same. This requires you to reinstall iSM on the Host OS.
Both iDRAC and the Host TLS versions should be 1.1 or above. Communication between iSM and iDRAC fails if the TLS protocol version
negotiation fails. If iSM with TLS capability is installed on an iDRAC rmware which does not support TLS communication over USBNIC, it
will work with the non-TLS channel as in the older versions of iSM.
NOTE
: iSM with TLS capability is supported on iDRAC rmware versions 3.30.30.30 and above.
NOTE: iSM without TLS capability does not function on a TLS-capable version of iDRAC rmware. For example: iSM 3.3 or older
which are not TLS-capable is not supported on iDRAC rmware 3.30.30.30 and later.
NOTE: If iSM 3.3.0 is installed on iDRAC 3.30.30.30 rmware, multiple events with ISM0050 are observed in LCLog.
iDRAC Service Module monitoring features 45