As part of the iDRAC configuration, it is not recommended to change or amend the IP. Though, I've spoken to one of the iSM support team and have reviewed the commands that you have entered, and it seems to be the only way to divert the IP to another namespace.
With that, you stating about your goal to get the hostname and osversion "in there", are you referring to iDRAC? Is iDRAC now able to display the information that you're looking for?
By the way, what version of iSM have you installed? What OS are you running? Are all of the server firmware and BIOS updated?
> With that, you stating about your goal to get the hostname and osversion "in there", are you referring to iDRAC? Is iDRAC now able to display the information that you're looking for?
yes! With my "hacks" I am able to get the osname and version in the iDRAC, but it is very hackish. My desire is that I can just package a docker container, or run the setup.sh -x -a of iSM, and have it just work "out of the box" That would mean the guys packaging iSM have to work a bit though... Right now I am also evaluating doing it through ipmi (https://github.com/openbmc/ipmitool/blob/master/contrib/exchange-bmc-os-info.init.redhat, as shared on https://www.dell.com/support/kbdoc/fr-fr/000148573/set-os-information-in-idrac-via-ipmi) which is much less intrusive (we don't need to install anything on the server!) but also does not have the nice lifecycle log export to OS. The ultimate goal would be to package it as docker container, deployed with openstack tripleo when we deploy new servers (since that's what we do ultimately)... I think at least, the netns makes sense as that way we are not exposing the iDRAC network to the rest of the processes, only to the iSM.
> By the way, what version of iSM have you installed? What OS are you running? Are all of the server firmware and BIOS updated?
OM-iSM-Dell-Web-LX-360-2249_A00.tar.gz, latest RHEL7.9, latest firmwares and BIOS (2.10.0) and DRAC (4.40) at of today
We also synchronize all these firmwares with DRM, but unfortunately this OM-iSM-Dell-Web-LX-360-2249_A00.tar.gz does not seem part of the catalog.
Thanks for letting us know if the steps you taken, works (not fully but acceptable?).
As I said, it's not recommended to change the iSM IP as it communicating with iDRAC. I may not have proper documentation for reference to provide a good solution for your intensions, but it's good to know now you're on a workaround.
hi. The steps I have taken (installing an exchange-bmc-os-info package to set-up os name and version in the iDRAC through ipmitool) are working.
However iSM is unusable. I cannot roll this on any production (or even local dev) server. We've been running without iSM for years, we will probably continue this way.
I take good note that it is not wise to change the iSM IP and will not do that.
DELL-Joey C
Moderator
•
4.1K Posts
1
February 9th, 2021 22:00
Hi,
As part of the iDRAC configuration, it is not recommended to change or amend the IP. Though, I've spoken to one of the iSM support team and have reviewed the commands that you have entered, and it seems to be the only way to divert the IP to another namespace.
With that, you stating about your goal to get the hostname and osversion "in there", are you referring to iDRAC? Is iDRAC now able to display the information that you're looking for?
By the way, what version of iSM have you installed? What OS are you running? Are all of the server firmware and BIOS updated?
frigo_
1 Rookie
•
22 Posts
0
February 10th, 2021 02:00
Hi!
> With that, you stating about your goal to get the hostname and osversion "in there", are you referring to iDRAC? Is iDRAC now able to display the information that you're looking for?
yes! With my "hacks" I am able to get the osname and version in the iDRAC, but it is very hackish. My desire is that I can just package a docker container, or run the setup.sh -x -a of iSM, and have it just work "out of the box" That would mean the guys packaging iSM have to work a bit though... Right now I am also evaluating doing it through ipmi (https://github.com/openbmc/ipmitool/blob/master/contrib/exchange-bmc-os-info.init.redhat, as shared on https://www.dell.com/support/kbdoc/fr-fr/000148573/set-os-information-in-idrac-via-ipmi) which is much less intrusive (we don't need to install anything on the server!) but also does not have the nice lifecycle log export to OS. The ultimate goal would be to package it as docker container, deployed with openstack tripleo when we deploy new servers (since that's what we do ultimately)... I think at least, the netns makes sense as that way we are not exposing the iDRAC network to the rest of the processes, only to the iSM.
> By the way, what version of iSM have you installed? What OS are you running? Are all of the server firmware and BIOS updated?
OM-iSM-Dell-Web-LX-360-2249_A00.tar.gz, latest RHEL7.9, latest firmwares and BIOS (2.10.0) and DRAC (4.40) at of today
We also synchronize all these firmwares with DRM, but unfortunately this OM-iSM-Dell-Web-LX-360-2249_A00.tar.gz does not seem part of the catalog.
DELL-Joey C
Moderator
•
4.1K Posts
0
February 10th, 2021 19:00
Hi,
Thanks for letting us know if the steps you taken, works (not fully but acceptable?).
As I said, it's not recommended to change the iSM IP as it communicating with iDRAC. I may not have proper documentation for reference to provide a good solution for your intensions, but it's good to know now you're on a workaround.
frigo_
1 Rookie
•
22 Posts
0
February 11th, 2021 03:00
hi. The steps I have taken (installing an exchange-bmc-os-info package to set-up os name and version in the iDRAC through ipmitool) are working.
However iSM is unusable. I cannot roll this on any production (or even local dev) server. We've been running without iSM for years, we will probably continue this way.
I take good note that it is not wise to change the iSM IP and will not do that.
Cheers!