All Linux servers are "Unclassified"

Thank you for your answer, i did try the T-Shooting tool and with the credentials i set, i get status "Connected". But in the console, the server is showing as unclussified.

Maybe the rabbit hole is deeper then i thought.. :)

Please let me know.

Thank you.

Thanks for the question.

I hope your discovery range only checked the SSH box and not SNMP or any of the others :)

There _might_ be a Troubleshooting Tool SSH test, I can't recall for sure.  This tool is installed on your OME desktop.

It should be able to classify it just via SSH...I think we use dmidcode to do this.  Other folks use SNMP + OMSA for LInux.

Hope this helps.

Rob

does your box have dmidecode?  I would guess most distros do, but please confirm.

Yes, only ssh is checked and filled with correct credentials.

Ok, and sorry to ask again, but can you confirm that SNMP is _not_ checked in your discovery wizard?  Only SSH right?

Yes, the boxes have dmidecode installed, and it works.. just tested.

Hi,

Can you also confirm the flavor of Linux server which you have?

Also, can you check that firewall is not enabled for the SSH port and on the OME machine as well?

Also,

Can you confirm that the discovery task in using root user or some other user?

And can you try running this dmidecode command on the linux server and see what is the output?

dmidecode -t1 | grep PowerEdge –c                       

we are using ssh on daily basis, so ssh firewall is i believe out of question, but firewall setup on aOME machine.. what should i be looking for..? OME is running on Windows VM.

Thank you.

Although, is it only linux discovery which is not working or none of the discovery tasks are getting classified properly? If it is only SSH discovery of linux servers, then it is highly doubtful that it can be a firewall problem.

Can you confirm the flavour of linux, if it is a SLES, you may need to check the sshd_config file and the value of "PasswordAuthenticalion" needs to be made YES. By default it is NO.

Also after these changes are made on the target Linux systems, please delete the devices in OME console (Manage->Devices) and re-discover the targets.

Thanks,
Raj Shresta

Here is a snippet from OME user guide that can potentially help you:

Question: Why are SUSE Linux Enterprise and Red Hat Enterprise Linux based-servers not displayed in the Server category after I have discovered it using SSH protocol?

Answer: The OpenManage Essentials SSH plugin uses sshlib2. sshlib2 fails to authenticate Linux servers which have disabled the Authentication by password option. To enable the option:
1. Open the file /etc/ssh/sshd_config in edit mode and search for the key PasswordAuthentication.
2. Set the value to yes and save the file.
3. Restart the sshd service /etc/init.d/sshd restart.The servers are now displayed under the Server category in the Device tree.

Thanks,
Raj Shresta

Hi,\

I did try to set the password authentification and delete/rediscover the item, but the only think i get is the hostname and NIC. To be honest, im a bit dissapointed. Do you know what else i can try..?

The same is happening with Windoiws servers (WMI)..

Thank you.

Let us drill down to one server, since you tried making password authentication YES, i am assuming the flavor of linux is SLES. Also, to confirm, did you restart the ssh services on the linux target after making the password authentication change on the linux server. The command would be service sshd restart.

Once the ssh services restart, can you check the results of these verification points:

• Are you able to connect through TT?
• What is the output of this command:

dmidecode -t1 | grep PowerEdge –c

• Are you trying discovery through root user or any other user? 
• On deleting and rediscovering that individual device, where does the device classify in the device tree?
• What is the SMBIOS version on the linux server? You can check that by running any of the dmidecode commands eg: 

  dmidecode -t 1

  The output will be something like:

  # dmidecode 2.11
  SMBIOS 2.7 present.

For WMI discovery, are you able to connect to the windows server using troubleshooting tool through WMI?

Hi,  we have RHEL 6 64x.

1. dmidecode -t1 | grep PowerEdge –c

output: grep: –c: No such file or directory

2. yes, im using root for auth..

3. All discovered devices ended up in "Unknown"

4. dmidecode -t 1

output: # dmidecode 2.11
SMBIOS 2.4 present.

5. Yes, thru t-shooting tool im able to connect to windows servers via WMI.