UNSOLVED
S
simonclausen
3 Posts
0
55983
September 27th, 2014 01:00
System Update is sending an incorrect URL during update
HI,
After upgrading to OME 2 from OME 1.3 I have an issue where OME sends an incorrect/incomplete URL to the iDRAC during an update, which of course causes the update to fail:
"The URI given to the iDRAC to download from: http://:1278/install_packages/Packages/Lifecycle-Controller_Application_C19M0_WN64_1.4.2.12_A00.EXE"
I've come across this thread with a similar issue, but no solution was published in it: http://en.community.dell.com/techcenter/systems-management/f/4494/t/19543102
How and where does OME generate this URL? I can't find anything in registry to tinker with. The host running OME only has one NIC and one IP. Both a wildcard binding in IIS and a binding to the one IP has no influence on the problem.
- Simon
simonclausen
3 Posts
1523
0
Posted September 30th, 2014 01:00
Hi,
The solution suggestions in that thread do not apply to this scenario. The server it not multi homed.
It does have full DNS resolution.
The problem appeared after an upgrade to OME 2.0. The System Update functionality worked as intended in version 1.3.
- Simon
DELL-Rob C
4 Apprentice
•
2843 Posts
1523
0
Posted September 30th, 2014 07:00
Hi Simon,
Ok, it looks like we'll need to have the support guys collect some logs and take a closer look. Can you open a ticket (800-945-3355 for North America, or use your server support number for your region).
Thanks,
Rob
DELL-Rob C
4 Apprentice
•
2843 Posts
1523
0
Posted September 30th, 2014 08:00
...and just to follow up to my earlier reply, you are not using IPv6 addresses, right?
Thanks,
Rob
cameronredux
2 Intern
•
615 Posts
1523
0
Posted September 30th, 2014 12:00
Rob - Is there a roadmap for ipv6 in OME? We are starting to roll out ipv6 in our network.
DELL-Rob C
4 Apprentice
•
2843 Posts
1523
0
Posted September 30th, 2014 12:00
Hey that is great news Simon. Thanks for the update.
I'll see if we can get a new FAQ item published quickly and dig a bit more on our side.
But good you are moving forward.
Thanks,
Rob
simonclausen
3 Posts
1523
0
Posted September 30th, 2014 12:00
Disabling IPV6 fixed the issue.
Thanks for the help!
- Simon
DELL-Rob C
4 Apprentice
•
2843 Posts
1523
0
Posted October 1st, 2014 15:00
Cameron,
I don't know for sure but will try to find out.
When you roll out, will you disable v4 addressing?
Will you enter an v6 address for discovery, etc.?
Just trying to think about the touch points in our product.
Thx
Rob
cameronredux
2 Intern
•
615 Posts
1523
0
Posted October 1st, 2014 16:00
Hi Rob,
We will be using both.
DRAC IPs might stay completely on ipv4 but server IPs will be a mix.
dimitar.delchev
3 Posts
910
0
Posted October 9th, 2014 18:00
I'm on a fresh install of OME 2.0 and observing the same behavior. OME sending an address with empty hostname to the drac.
Disabling IPV6 did not fix it for me (disabled in the registry and rebooted).
The OME host's DNS resolves correctly.
OME server is NOT multi-homed.
Would be nice if Dell posted a method to rule out/validate/isolate the root cause of this problem since it appears that there are several possible ones.
I have read all posts on the subject and tried all suggested fixes but am still having the issue.
Rob, seems like you are tackling this problem so your feedback would be greatly appreciated.
Thank you,
D
DELL-Rob C
4 Apprentice
•
2843 Posts
1520
0
Posted September 29th, 2014 09:00
Hi Simon thanks for the post.
There are a few suggestions in the other thread you reference.
The 'missing' ip address is supposed to be a valid ip address for your OME server. OME builds up this URL and sends it to the iDRAC. Typically, we get a list of valid ip addresses and filter out IPv6 and loopback.
Also, some folks that have seen this problem realize the problem is that the OME server is resolving to the loop back address (127.0.0.1) and that was the cause...
Do you have full DNS name resolution for the OME server?
Thanks,
Rob