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.
Does the Lifecycle IP only get used if you actually log into the Lifecycle contoller?
No, the LCC initializes when the systems boots up. It continues running until the servers is powered down.
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?
That would result in an IP conflict. The LCC is a light-weight operating system that runs from the iDRAC. Even if it is not actively using the network it will still function similar to having an IP assigned to any interface that is online. If you want to limit the IP's that are used then you will need to either remove the network information when you are done using it or disable the network functionality on the LCC when you are not using it.
i am going to build production vmware 6.0 environment on Dell servers, Dell Power Edge 630. as my knowledge we manually install update for LCC and Bios, we assign IP only to IDRAC, does it matter or is that has any impact if we keep disable controller IPs or we don't assign any Ips to LCC white keeping its enable,?? i googled it but din't get satisfactory answers.
we assign IP only to IDRAC, does it matter or is that has any impact if we keep disable controller IPs or we don't assign any Ips to LCC white keeping its enable,??
I'm not sure what you are asking. You don't need to assign an IP address to the LCC for it to function. Some functionality requires network configuration.
my question was that do we required to assign IP to LLC to run server functionally well?? but i think you replied well and i got answer that it's optional to assign and not impact to the server functionality.
The LCC uses any of the LOM ports or any of the PCIe NIC ports. You can select which port in the network configuration of the LCC, but you cannot pick/choose the DRAC port. The chosen port is used to reach out to find the catalog with the latest firmwares for a server. The LCC defaults to ftp.dell.com, but can be changed in case you want to download all the files and such with Repository Manager and put them on a local FTP server to improve speed and save bandwidth.
To do connectivity, the LCC needs a (temporary) IP address while the LCC is running.
I usually use the same IP as the OS (management) IP as the LCC and the OS will never be up at the same time (they are mutually exclusive).
I am trying to config a Dell R530. first time trying IDRAC/LCC. I am a bit unclear on the network config.
It looks to me like the idrac and lcc IP is the same. when I f10 (LCC) I can drop down (in network settings) and choose a NIC (1-4 for my server). So, If I want to use IE to do some config, shouldn't the LOM in the idrac settings (F2/BIOS) match? for example if I have network cable in NIC1 then I should use LOM1?
I don't see why the two settings should be different. But can I then go ahead and install my OS (2012r2 server) and assign my server the same IP as I used for LCC/idrac?
Like I said, it's first time I work with these things
dgitter
2 Posts
4
September 16th, 2017 14:00
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
Daniel My
10 Elder
•
6.2K Posts
0
September 24th, 2015 18:00
Hello
No, the LCC initializes when the systems boots up. It continues running until the servers is powered down.
That would result in an IP conflict. The LCC is a light-weight operating system that runs from the iDRAC. Even if it is not actively using the network it will still function similar to having an IP assigned to any interface that is online. If you want to limit the IP's that are used then you will need to either remove the network information when you are done using it or disable the network functionality on the LCC when you are not using it.
Thanks
YT11
7 Posts
0
September 8th, 2016 08:00
Hi, Thanks for this info, just quick question,
i am going to build production vmware 6.0 environment on Dell servers, Dell Power Edge 630. as my knowledge we manually install update for LCC and Bios, we assign IP only to IDRAC, does it matter or is that has any impact if we keep disable controller IPs or we don't assign any Ips to LCC white keeping its enable,?? i googled it but din't get satisfactory answers.
Thanks
Daniel My
10 Elder
•
6.2K Posts
0
September 8th, 2016 11:00
I'm not sure what you are asking. You don't need to assign an IP address to the LCC for it to function. Some functionality requires network configuration.
Thanks
YT11
7 Posts
0
September 8th, 2016 13:00
Thanks Daniel,
my question was that do we required to assign IP to LLC to run server functionally well?? but i think you replied well and i got answer that it's optional to assign and not impact to the server functionality.
Thanks
Dev Mgr
4 Operator
•
9.3K Posts
1
November 16th, 2016 13:00
The LCC uses any of the LOM ports or any of the PCIe NIC ports. You can select which port in the network configuration of the LCC, but you cannot pick/choose the DRAC port. The chosen port is used to reach out to find the catalog with the latest firmwares for a server. The LCC defaults to ftp.dell.com, but can be changed in case you want to download all the files and such with Repository Manager and put them on a local FTP server to improve speed and save bandwidth.
To do connectivity, the LCC needs a (temporary) IP address while the LCC is running.
I usually use the same IP as the OS (management) IP as the LCC and the OS will never be up at the same time (they are mutually exclusive).
MCruzTCE
1 Message
0
April 28th, 2017 09:00
Hello
I am trying to config a Dell R530. first time trying IDRAC/LCC. I am a bit unclear on the network config.
It looks to me like the idrac and lcc IP is the same. when I f10 (LCC) I can drop down (in network settings) and choose a NIC (1-4 for my server). So, If I want to use IE to do some config, shouldn't the LOM in the idrac settings (F2/BIOS) match? for example if I have network cable in NIC1 then I should use LOM1?
I don't see why the two settings should be different. But can I then go ahead and install my OS (2012r2 server) and assign my server the same IP as I used for LCC/idrac?
Like I said, it's first time I work with these things
Thanks for your help