HA Cluster Management W/O using Netbios

Thanks for the post Jason.

HA cluster seems to be showing up ok in my tree...inventory too.

What protocol are you using in your discovery wizard (snmp?)

Does the Dell troubleshooting tool (on your desktop) return the OMSA version in the result set?

Thanks,

Rob

Rob,

Thanks for looking at this. Yes I'm using SNMP and DNS for discovery.

When I use the Dell troubleshooting tool to discovery the SNMP the following occurs.

If I query the name that OME has which is the Cluster Share name resolves to MIB-II of the active node and OMSA version. If I query directly with the Server Name I get the same MIB-II of the device. It seems only to affect the Aside from that it dosent appear the troubleshooting tool differentiates from Netbios and DNS I get the same results outside of OME.

Ok, so name resolution and reverse also works.

Your discover prefs are set to DNS and you discovered via SNMP.

It all looks ok to me.  The only other similar thing I've seen is when a user had recent changes to his DNS environment.

He had to do a dnsflush.

http://en.community.dell.com/techcenter/systems-management/f/4494/p/19460854/20159385.aspx#20159385

(screenshot removed, need to insert a new one)

edit: new screen shot now inserted back in the post.

edit: third time is a charm! last edit to ss.

I think I may need to punt you over to open a ticket (800-945-3355).  I can't think of anything else.

Rob

Ok, I think you are saying that the TS tool _does_ display the OMSA version in the result set both when you use the DNS name and when you use the IP addr.

So it looks like this:

Server Administrator (Version) 6.5 ...or something like that.

What happens when you do a ping -a ipaddr from OME to MN?

What happens when you do a ping -a ipaddr from MN to OME?

Just checking some common stuff here...thx.

Rob

Rob,

Thanks for looking at this. Yes I'm using SNMP and DNS for discovery.

When I use the Dell troubleshooting tool to discovery the SNMP the following occurs.

If I query the name that OME has which is the Cluster Share name resolves to MIB-II of the active node and OMSA version. If I query directly with the Server Name I get the same MIB-II of the device. It seems only to affect the Aside from that it dosent appear the troubleshooting tool differentiates from Netbios and DNS I get the same results outside of OME.

When I perform the tasks you listed the results are accurate where DNS resolves to the correct IP. Even the Name Resolution tool in the TS resolves correctly... The console still when using DNS shows the innacurate name and essentially renames the Device from the accurate server name to the share name according to the Application Logs.

After this is done the server that is renamed ceases to be queriable via device search

So the only difference between your screen (which helped) is that your cluster is showing the cluster name and not the individual nodes. What's the designed goal?

My OME is as follows --

On Netbios

During DNS Discovery

After DNS Discovery Completion

Ok, the screen shots helped.  I'll check to see if this is something being reviewed in our current release under development.

thanks,

Rob