System Update is sending an incorrect URL during update

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

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

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

...and just to follow up to my earlier reply, you are not using IPv6 addresses, right?

Thanks,

Rob

Rob - Is there a roadmap for ipv6 in OME? We are starting to roll out ipv6 in our network.

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

Disabling IPV6 fixed the issue.

Thanks for the help!

- Simon

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

Hi Rob,

We will be using both.

DRAC IPs might stay completely on ipv4 but server IPs will be a mix.

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

Hi D....

The only other thing I can think of is if your loopback adapter is bound to the NIC.

We toss out loopback and IPV6.  So if those get tossed out and we are left with nothing, that's why we've figured it was one of those two things.

We may need the support guys to run some diagnostics to determine what IP address might be bound to the NIC.  Perhaps their is something else we need to be accounting for when building up this ip address.

If you can open a ticket it might help us get more info (800-945-3355).

Thanks,

Rob

Hi Rob,

Which options do I select to get to the right department  (800-945-3355)?

I spin up a brand new R2 system, immediately disabled ipv6 and fully updated then installed OME but observed the same behavior. 

I refuse to believe that a registry hack or non-standard network configuration is required for OME 2.0 to be properly installed on a vanilla system. That's a bug and I wish Dell addressed this issue or at least expose that setting so it can be manually set. 

Thanks again for your help.

D

Hi D.

Yeah, fair enough.  The issue is that we have a few folks seeing this behavior, but they've all been fixed by disabling IPv6 or loopback.  So we kind of understand that behavior and how to address that.  So now that does not seem to help you, so there might be something in your environment that we've not tested for...something unique that other folks may not have.  Hence the support call to see if we can get a bit more info on your environment.

I think if you call in and get to pro support, it should be where you give them the service tag of your one of your servers.  That's what most folks seem to do to get to the right place.

Thanks!

Rob

I'm was having the exact same issue on my system with a fresh install.   I tried everything on this post but nothing worked.

DNS is working properly on the system.

I then put the system hostname and IP address in the Windows hosts file.   This resolved the issue.

I'm not sure why Dell OME can't pick up the hostname or do DNS resolution on the hostname but having the hostname and IP address in the hosts file resolved the issue for me.

Thanks G2BSupport,

Would you please post your hosts file (without your real hostnames and IPs). I'm still getting the same error.

Thank you,

D