iSM is not required for this IP to work. can you check iDRAC username and password used in redfishtool command. You can also try with iDRAC root user or create a new user in iDRAC and try. 401 error code typically come when wrong credential is used.
Can you give more details on GUI is not displaying right? Are you not able to get iDRAC login screen when try to launch 169.254.1.1 from ubuntu browser?
@ION_Vince , If you need to run redfish command locally from the server then you can use "OS to iDRAC Pass-through" USB NIC feature on iDRAC. Once you enable this feature you will see an new network interface on host (default IP will be 169.254.0.2). Once this feature is enabled you can run redfish commands from the host by using 169.254.0.1 as iDRAC IP. You can get more details on this feature from below links.
This just brought me slightly further... but has not enabled me to do as desired.
I also found that iSM had to be on the server for the usb-nic to show in ifconfig
OM-iSM-Dell-Web-LX-351-1949_A00.tar.gz was placed and run and os data shows in iDrac web interface now.
But the problem of getting the data locally seems to remain.
~$ redfishtool -r 169.254.1.2 -u -p Systems list redfishtool: Transport: Response Error: status_code: 404 -- Not Found redfishtool: getCollection: Error getting service root, aborting
So it seems now that the idrac webserver is responding to the request but not locally as desired.
What am I missing here ? I tried curl against same ip and got same 404... Seems that redfish is not where expected ? I am using idrac express but got same results when used trial version of enterprise.
{"@odata.context":"/redfish/v1/$metadata#ChassisCollection.ChassisCollection","@odata.id":"/redfish/v1/Chassis/","@odata.type":"#ChassisCollection.ChassisCollection","Description":"Collection of Chassis","Members":[{"@odata.id":"/redfish/v1/Chassis/System.Embedded.1"},{"@odata.id":"/redfish/v1/Chassis/Enclosure.Internal.0-1:RAID.Integrated.1-1"}],"Members@odata.count":2,"Name":"Chassis Collection"}
From Local Machine:
ping works fine:
~$ ping 169.254.1.2 PING 169.254.1.2 (169.254.1.2) 56(84) bytes of data. 64 bytes from 169.254.1.2: icmp_seq=1 ttl=64 time=0.026 ms 64 bytes from 169.254.1.2: icmp_seq=2 ttl=64 time=0.048 ms
It is working when I tried it on my server. Can you let me know the iDRAC firmware version and server model? Can you also try launching iDRAC GUI from the server operating system using 169.254.1.1 IP?
using express license, but enterprise was same result.
ISM: 3.5.1 -- OM-iSM-Dell-Web-LX-351-1949_A00.tar
using cli web browser seems to connect but not really display right. If I was going to guess maybe this is something with the ism ?
looks as though all enabled...
OpenManage || iDRAC Service Module
#################################################
Available feature options:
[x] 1. Watchdog Instrumentation Service [x] 2. LifeCycle Log Information [x] 3. Operating System Information [x] 4. iDRAC access via Host OS [x] a. Access via GUI, WS-man, Redfish, Remote Racadm [x] b. In-band SNMP Traps [x] c. Access via SNMP Get [x] 5. iDRAC SSO Launcher [x] a. Read only [ ] b. Administrator [x] 6. Chipset SATA HDD S.M.A.R.T monitoring 7. iDRAC Hard Reset 8. Support Assist 9. Full Power Cycle [x] 10. All Features
Enter the number to select/deselect a feature ( multiple feature selection should be comma separated) ( to select sub-features, please use 4.a,4.b, etc.) Enter i to install the selected features. Enter q to quit.
Enter : i
Enter a valid port number for iDRAC access via Host OS or Enter to take default port number: 1266
Do you want the services started?
Press ('y' for yes | 'Enter' to exit): y Checking for iSM communication with iDRAC... Waiting... ############### [100%] iSM communication with iDRAC is established successfully.
well I think I am going to call this closed.. I created a new idrac user test with pw test and it worked... Not sure why root was not working, same settings or even less, but not worried about it to try and sort that
DELL-Shine K
4 Operator
•
3K Posts
1
October 19th, 2020 06:00
iSM is not required for this IP to work. can you check iDRAC username and password used in redfishtool command. You can also try with iDRAC root user or create a new user in iDRAC and try. 401 error code typically come when wrong credential is used.
Can you give more details on GUI is not displaying right? Are you not able to get iDRAC login screen when try to launch 169.254.1.1 from ubuntu browser?
DELL-Shine K
4 Operator
•
3K Posts
0
October 16th, 2020 21:00
@ION_Vince , If you need to run redfish command locally from the server then you can use "OS to iDRAC Pass-through" USB NIC feature on iDRAC. Once you enable this feature you will see an new network interface on host (default IP will be 169.254.0.2). Once this feature is enabled you can run redfish commands from the host by using 169.254.0.1 as iDRAC IP. You can get more details on this feature from below links.
iDRAC9 : https://www.dell.com/support/manuals/en-us/idrac9-lifecycle-controller-v4.x-series/idrac9_4.00.00.00_ug_new/enabling-or-disabling-os-to-idrac-pass-through?guid=guid-25fc6820-9a01-4739-87c3-d2036b9adf80&lang=en-us
iDRAC8: https://www.dell.com/support/manuals/en-us/idrac8-lifecycle-controller-v2.75.75.75/idrac8_2.75.75.75_ug/enabling-or-disabling-os-to-idrac-pass-through?guid=guid-e44413c7-969c-4c76-91f2-f6d9076a57b7&lang=en-us
DELL-Shine K
4 Operator
•
3K Posts
0
October 18th, 2020 09:00
As host got ip address of 169.254.1.2, iDRAC ip will be 169.254.1.1 Can you run Redfish command with 169.254.1.1 as iDRAC IP.
ION_Vince
1 Rookie
•
5 Posts
0
October 18th, 2020 09:00
@DELL-Shine K
Thanks for your response.. however.
This just brought me slightly further... but has not enabled me to do as desired.
I also found that iSM had to be on the server for the usb-nic to show in ifconfig
OM-iSM-Dell-Web-LX-351-1949_A00.tar.gz was placed and run and os data shows in iDrac web interface now.
But the problem of getting the data locally seems to remain.
~$ redfishtool -r 169.254.1.2 -u -p Systems list
redfishtool: Transport: Response Error: status_code: 404 -- Not Found
redfishtool: getCollection: Error getting service root, aborting
So it seems now that the idrac webserver is responding to the request but not locally as desired.
What am I missing here ? I tried curl against same ip and got same 404... Seems that redfish is not where expected ? I am using idrac express but got same results when used trial version of enterprise.
Seems this should not be impossible...
from othermachine: https://192.168.100.2/redfish/v1/Chassis
{"@odata.context":"/redfish/v1/$metadata#ChassisCollection.ChassisCollection","@odata.id":"/redfish/v1/Chassis/","@odata.type":"#ChassisCollection.ChassisCollection","Description":"Collection of Chassis","Members":[{"@odata.id":"/redfish/v1/Chassis/System.Embedded.1"},{"@odata.id":"/redfish/v1/Chassis/Enclosure.Internal.0-1:RAID.Integrated.1-1"}],"Members@odata.count":2,"Name":"Chassis Collection"}From Local Machine:
ping works fine:
~$ ping 169.254.1.2
PING 169.254.1.2 (169.254.1.2) 56(84) bytes of data.
64 bytes from 169.254.1.2: icmp_seq=1 ttl=64 time=0.026 ms
64 bytes from 169.254.1.2: icmp_seq=2 ttl=64 time=0.048 ms
~$ ifconfig
eno1: flags=4163 mtu 1500
inet 10.0.0.250 netmask 255.255.255.0 broadcast 10.0.0.255
inet6 fe80::2eea:7fff:fe5a:30cb prefixlen 64 scopeid 0x20
inet6 2601:186:4500:f700:2eea:7fff:fe5a:30cb prefixlen 64 scopeid 0x0
ether 2c:ea:7f:5a:30:cb txqueuelen 1000 (Ethernet)
RX packets 41814 bytes 6721812 (6.7 MB)
RX errors 0 dropped 1 overruns 0 frame 0
TX packets 963 bytes 90552 (90.5 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 17
eno2: flags=4163 mtu 1500
inet 192.168.100.1 netmask 255.255.255.0 broadcast 192.168.100.255
inet6 fe80::2eea:7fff:fe5a:30cc prefixlen 64 scopeid 0x20
ether 2c:ea:7f:5a:30:cc txqueuelen 1000 (Ethernet)
RX packets 13483 bytes 3629968 (3.6 MB)
RX errors 0 dropped 2 overruns 0 frame 0
TX packets 12350 bytes 5672497 (5.6 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 18
idrac: flags=4163 mtu 1500
inet 169.254.1.2 netmask 255.255.0.0 broadcast 169.254.255.255
inet6 fe80::2eea:7fff:fe5a:30c8 prefixlen 64 scopeid 0x20
inet6 fde1:53ba:e9a0:de11:2eea:7fff:fe5a:30c8 prefixlen 64 scopeid 0x0
inet6 fde1:53ba:e9a0:de11:c93c:ca08:b993:b1dc prefixlen 64 scopeid 0x0
ether 2c:ea:7f:5a:30:c8 txqueuelen 1000 (Ethernet)
RX packets 3749 bytes 285279 (285.2 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4374 bytes 360647 (360.6 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73 mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 68 bytes 6476 (6.4 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 68 bytes 6476 (6.4 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
ION_Vince
1 Rookie
•
5 Posts
0
October 18th, 2020 11:00
Different error, now 401
~$ redfishtool -r 169.254.1.1 -u -p Chassis
redfishtool: Transport: Response Error: status_code: 401 -- Unauthorized
DELL-Shine K
4 Operator
•
3K Posts
0
October 18th, 2020 22:00
It is working when I tried it on my server. Can you let me know the iDRAC firmware version and server model? Can you also try launching iDRAC GUI from the server operating system using 169.254.1.1 IP?
ION_Vince
1 Rookie
•
5 Posts
0
October 19th, 2020 05:00
@DELL-Shine K thanks for the help.
Server: PowerEdge R440
Ubuntu: 18.04.4 LTS (Bionic Beaver) Kernel 4.15.0-121-generic (x86_64)
using express license, but enterprise was same result.
ISM: 3.5.1 -- OM-iSM-Dell-Web-LX-351-1949_A00.tar
using cli web browser seems to connect but not really display right. If I was going to guess maybe this is something with the ism ?
looks as though all enabled...
OpenManage || iDRAC Service Module
#################################################
Available feature options:
[x] 1. Watchdog Instrumentation Service
[x] 2. LifeCycle Log Information
[x] 3. Operating System Information
[x] 4. iDRAC access via Host OS
[x] a. Access via GUI, WS-man, Redfish, Remote Racadm
[x] b. In-band SNMP Traps
[x] c. Access via SNMP Get
[x] 5. iDRAC SSO Launcher
[x] a. Read only
[ ] b. Administrator
[x] 6. Chipset SATA HDD S.M.A.R.T monitoring
7. iDRAC Hard Reset
8. Support Assist
9. Full Power Cycle
[x] 10. All Features
Enter the number to select/deselect a feature
( multiple feature selection should be comma separated)
( to select sub-features, please use 4.a,4.b, etc.)
Enter i to install the selected features.
Enter q to quit.
Enter : i
Enter a valid port number for iDRAC access via Host OS or Enter to take default port number: 1266
Do you want the services started?
Press ('y' for yes | 'Enter' to exit): y
Checking for iSM communication with iDRAC...
Waiting... ############### [100%]
iSM communication with iDRAC is established successfully.
ION_Vince
1 Rookie
•
5 Posts
0
October 19th, 2020 10:00
well I think I am going to call this closed.. I created a new idrac user test with pw test and it worked... Not sure why root was not working, same settings or even less, but not worried about it to try and sort that
thanks @DELL-Shine K