The LCC and iDrac IP's should NEVER be the same.  If they are you will not be able to use the iDrac remote virtual console to access the LCC as they will be in conflict. You can however use the same IP for the LCC that you would use for your OS, as the two would never be active at the same time.  Pretty much, the only time you need an IP on the LCC would be to use it to download firmware updates from Dell's FTP server. That said, if you are using clustering or some other technology that monitors your server OS by IP, you would be better serviced by using a unique IP for the LCC.  This way those other technologies will not see the LCC (when active) and think that it is really seeing your OS (which would be inactive at that moment). Also, if your server has a separate NIC available for the iDrac, I would recommend using it instead of sharing one of the LOMs. I have over 50 servers configured with the LCC & OS on the same IP and have not run into any issues. Dave
We currently have the Windows IP and the iDrac IP setup for all our servers.  We then used the lifecycle Controller to do some firmware updates which needed yet another IP address. I really don't want to have to set aside 3 IP addresses for every server so what are our options?  Does the Lifecycle IP only get used if you actually log into the Lifecycle contoller?  If so, can I just use the same IP on all my servers as long as I'm never trying to use two at once?  Maybe I can just turn the IP off when I'm not using it... Just looking for options. Thanks!
Lifecycle Controller IP. Is it always active?