Did you logged in to iDRAC from host operating system. Ideally you should be seeing below log message when you log in to iDRAC from host operating system using iDRAC USB NIC interface
Successfully logged in using root, from 169.254.1.2 and GUI.
If you need to access iDRAC remotely using host IP address then you need to enable that feature in iSM with a port number. you can get more details on this configuration on below link (Refer section 3.1 Configuration using Linux Command line)
Can you share DRAC FW and iSM version used? You can also check whether you can see a network interface called "idrac" on Cent OS with IP address of 169.254.0.2. If this interface is available can you check whether you can ping 169.254.0.1 or launch iDRAC using IP 169.254.0.1 from Cent OS?
I just found there is a newer iSM version available here it says :
Fixes: Microsoft Windows and Linux operating systems -iSM (v3.4.0 or later) communication with iDRAC failure when iDRAC firmware is upgraded to 3.30.30.30 or later -iSM (v3.4.0 or later) communication with iDRAC failure when iDRAC firmware is downgraded from any recent version to a version less than 3.30.30.30
Looks like a conflict in IP for iDRAC and em1 port. Can you change iDRAC Virtual USB NIC IP to 192.168.1.1 and see whether it make iSM to work. You can run below command to change iDRAC USB NIC IP address
racadm set idrac.os-bmc.UsbNicIpAddress 169.254.1.1
I'm wondering whether that change could cause connection issues if it does my host will be angry also iSM throws an additional error
dsm_ism_srvmgrd[3338]: ISM0003 [iSM@674.10892.2 EventID="8196" EventCategory="Audit" EventSeverity="error" IsPastEvent="false" language="en-US"] The iDRAC Service Module is unable to discover iDRAC from the operating system of the server.
systemctl status ipmi.service shows it's active(exited) <== this doesn't look correct to me.
I didn't change anything yet however when i try to ping 169.254.1.1 i get
is that good news or bad news ? i'm just scared i'll screw up and i'll have to ask my host to fix the remote access controller.My goal is to get that web interface to work https://ip_here:1266/login.html
Can you run ifconfig command and check the ip address of idrac interface. I am suspecting issue is due to both iDRAC and em1 having same network address. I recommend to perform below steps to check with different ip address for iDRAC USB NIC
Uninstall iSM
Disable USB NIC on iDRAC
racadm set idrac.os-bmc.AdminState Disabled
Set USB NIC IP address to 169.254.1.1
racadm set idrac.os-bmc.UsbNicIpAddress 169.254.1.1
Enable USB NIC on iDRAC
racadm set idrac.os-bmc.AdminState Enabled
Check whether host got 169.254.1.2 ip address for idrac interface using ifconfig command on host
Check whether you can ping IP address / launch iDRAC from host using ip address 169.254.1.1
Can you change iDRAC USB NIC IP as I mentioned and check the behavior. I believe you are seeing the 6th issue mentioned in below link and solution recommended is reconfiguring the iDRAC USB NIC IP address.
I'll try that procedure you mentioned earlier.I have had a chat with my host and they said they use a webproxy to access that iDRAC interface so first i have to login to my customer account and there is a link to open it it is not accesible by the general public (there are good reasons for that)
I found in the docs that before you install the dcism package you have to install the OSC package collector using a command like rpm -ivh dcism-osc*.rpm is this true ?
DELL-Shine K
4 Operator
•
3K Posts
0
November 25th, 2020 05:00
Did you logged in to iDRAC from host operating system. Ideally you should be seeing below log message when you log in to iDRAC from host operating system using iDRAC USB NIC interface
Successfully logged in using root, from 169.254.1.2 and GUI.
If you need to access iDRAC remotely using host IP address then you need to enable that feature in iSM with a port number. you can get more details on this configuration on below link (Refer section 3.1 Configuration using Linux Command line)
https://downloads.dell.com/solutions/general-solution-resources/White%20Papers/iDRAC%20Service%20Module-iDRAC%20Access%20via%20Host%20OS.pdf
Note : Make sure firewall is disabled or allowing the port configured for iDRAC access via host operating system
DELL-Shine K
4 Operator
•
3K Posts
0
November 22nd, 2020 00:00
Can you share DRAC FW and iSM version used? You can also check whether you can see a network interface called "idrac" on Cent OS with IP address of 169.254.0.2. If this interface is available can you check whether you can ping 169.254.0.1 or launch iDRAC using IP 169.254.0.1 from Cent OS?
confuseduser43
3 Apprentice
•
591 Posts
0
November 22nd, 2020 04:00
Hello,
I just found there is a newer iSM version available here it says :
Fixes:
Microsoft Windows and Linux operating systems
-iSM (v3.4.0 or later) communication with iDRAC failure when iDRAC firmware is upgraded to 3.30.30.30 or later
-iSM (v3.4.0 or later) communication with iDRAC failure when iDRAC firmware is downgraded from any recent version to a version less than 3.30.30.30
Could that solve the issue ?
confuseduser43
3 Apprentice
•
591 Posts
0
November 22nd, 2020 04:00
Hello,
iDRAC Firmware version = 4.10.10.10
iSM version = 3.5.0
Regarding the other question i do see a network interface called idrac but it doesn't have ip address 169.254.0.2 it is listed as 169.254.0.0
I can ping 169.254.0.1 and 169.254.0.2 i have a feeling this is strange ....
DELL-Shine K
4 Operator
•
3K Posts
0
November 22nd, 2020 04:00
Looks like a conflict in IP for iDRAC and em1 port. Can you change iDRAC Virtual USB NIC IP to 192.168.1.1 and see whether it make iSM to work. You can run below command to change iDRAC USB NIC IP address
racadm set idrac.os-bmc.UsbNicIpAddress 169.254.1.1
confuseduser43
3 Apprentice
•
591 Posts
0
November 22nd, 2020 06:00
Hello,
I'm wondering whether that change could cause connection issues if it does my host will be angry also iSM throws an additional error
dsm_ism_srvmgrd[3338]: ISM0003 [iSM@674.10892.2 EventID="8196" EventCategory="Audit" EventSeverity="error" IsPastEvent="false" language="en-US"] The iDRAC Service Module is unable to discover iDRAC from the operating system of the server.
systemctl status ipmi.service shows it's active(exited) <== this doesn't look correct to me.
confuseduser43
3 Apprentice
•
591 Posts
0
November 22nd, 2020 07:00
Hello,
I didn't change anything yet however when i try to ping 169.254.1.1 i get
is that good news or bad news ? i'm just scared i'll screw up and i'll have to ask my host to fix the remote access controller.My goal is to get that web interface to work https://ip_here:1266/login.html
DELL-Shine K
4 Operator
•
3K Posts
0
November 22nd, 2020 08:00
Can you run ifconfig command and check the ip address of idrac interface. I am suspecting issue is due to both iDRAC and em1 having same network address. I recommend to perform below steps to check with different ip address for iDRAC USB NIC
racadm set idrac.os-bmc.AdminState Disabled
racadm set idrac.os-bmc.UsbNicIpAddress 169.254.1.1
racadm set idrac.os-bmc.AdminState Enabled
confuseduser43
3 Apprentice
•
591 Posts
0
November 22nd, 2020 09:00
Hello ,
No iDRAC and em1 interfaces both have a different address
I can ping 169.254.0.2 .Thinking about changing USB NIC IP address to 169.254.1.1.
confuseduser43
3 Apprentice
•
591 Posts
0
November 22nd, 2020 11:00
Hello,
Maybe i'm doing it wrong installing the iDRAC service module .The documentation here says :
Transverse to mounted volume (SMINST)
What does this mean exactely ? i just look at /dev/disk/by-label and then mount that to /root/iSM/ from there i run the installer sh ISM_Lx.sh.
English is not my mother language i do not understand what "Transverse" means.
DELL-Shine K
4 Operator
•
3K Posts
0
November 22nd, 2020 17:00
Your iSM installation steps looks correct
DELL-Shine K
4 Operator
•
3K Posts
0
November 22nd, 2020 17:00
From your netstat output both idrac and em1 have 169.254.0.0 route which can create issues while iSM try to communicate with iDRAC.
Can you run below 2 ping command and see whether it works.
ping 169.254.0.1
ping 169.254.0.1 -I idrac
I would recommend trying with 169.254.1.1 IP for USB NIC on iDRAC.
confuseduser43
3 Apprentice
•
591 Posts
0
November 22nd, 2020 18:00
Hello,
ping 169.254.0.1
ping 169.254.0.1 -I idrac
both ping commands work and reply .
DELL-Shine K
4 Operator
•
3K Posts
0
November 22nd, 2020 20:00
Can you change iDRAC USB NIC IP as I mentioned and check the behavior. I believe you are seeing the 6th issue mentioned in below link and solution recommended is reconfiguring the iDRAC USB NIC IP address.
https://www.dell.com/support/manuals/en-us/idrac-service-module-v3.4.1/ism_3.4.1_user_guide/frequently-asked-questions?guid=guid-55f53844-e393-497d-ad9e-dbb8bca0a639&lang=en-us
confuseduser43
3 Apprentice
•
591 Posts
0
November 23rd, 2020 01:00
Hello,
I'll try that procedure you mentioned earlier.I have had a chat with my host and they said they use a webproxy to access that iDRAC interface so first i have to login to my customer account and there is a link to open it it is not accesible by the general public (there are good reasons for that)
I found in the docs that before you install the dcism package you have to install the OSC package collector using a command like rpm -ivh dcism-osc*.rpm is this true ?