Hi Dilip,

1. When you want to do system update via OMSA method, you can discover your server using SNMP or WMI protocol. You need to make sure the OMSA is installed on the target server and you need to provide the IP of the server, not the iDRAC
2. iDRAC6 and above support WSMAN protocol, so we have iDRAC update method for 11G and above servers. For 9G and 10G, you need to update them using the OMSA method. I did not understand the second part of your question: ICMP is a ping protocol, it is not used for discovery. You can discover iDRAC using WSMAN, IPMI and SNMP protocols but if you want to push updates, you need to discover the iDRAC using WSMAN protocol. Windows servers can be discovered using SNMP and WMI protocol and Linux using SNMP and SSH protocols. 
3. If you have discovered an iDRAC using SNMP or IPMI protocol, then you will not get the software inventory table populated, in that case you need to make sure that you discover and inventory the iDRAC using WSMAN. For a linux server, you need to make sure that the 'srvadmin-cm' rpm in installed.
4. You cannot update non-Dell servers using OME.

Hi Pupul,

Sorry it is SNMP not ICMP

Can we use both SNMP and WS-MAN for discovery in order to update via iDRAC and OMSA both ?

because hard-disk firmware you will not list under iDRAC update method i guess.

Regards

dilipnet

Yes,

You can use SNMP and WSMAN both. SNMP for server and WSMAN for iDRAC. When in system update page, you need to select the update method as OMSA method from the "Advanced Settings". Then you will be able to update by providing the server credentials. The white paper i pointed to, contains details about these.

Yes, you will not be able to update the physical disk using iDRAC update method. 

Hi Pupul,

I have a machine PowerEdge C2100 and I tried to discover the machine via ws-man and it was un-successfull

 though snmp as well. I tried to test it via troubleshooting tool no luck ?

1.82.53138 Firmware version

Is there any known / finding for this ?

Regards

dilipnet

Hi Dilip,

PowerEdge C series is not supported for system update. These servers can be discovered only using IPMI protocol.

Hi Pupul,

Thanks for the infomation

in that case if we have different set of server series ... and we do a one discovery with the full sub-net info how do we specify the authentication methods.. since we do not have segments C series on this range like wise ...

just select different method in one discovery "SNMP, WMI,ws-man,IPMI" ?

Regards

Dilip

Hi Dilip,

You do not have to divide discovery into segments. Enable all the protocols and then if you give all the IP range at once, then you will be able to discover your devices. OME establishes the available session with the device, if the required protocol is enabled in the discovery configuration.

One thing to try would be to keep OME and the iDRAC/server in the same domain. If it is already there, then the thing to try would be to get both, the OME server and the target signed by the same signing certificate authority.

Hello Pupul,

I guess the below command will work changing the iDRAC User and password locally on the given machine

DRAC 5 and 6 7:

racadm config -g cfgUserAdmin -o cfgUserAdminPassword -i 2 newpassword

How do we execute it remotely from OME server by specifying the iDRAC IP of the remote machine ?

Thanks

dilipnet

Hi Pupul,

Any ting that i can do to  fix the below issue "Security Alert: Certificate is invalid' ?

PS C:\Users\Administrator> racadm.exe -r 192.168.18.100 -u root -p calvin getsysinfo
Security Alert: Certificate is invalid - Certificate is not signed by Trusted Third Party
Continuing execution. Use -S option for racadm to stop execution on certificate-related errors

Thanks

dilipnet

Hi,

You can use the same command from remote tasks feature in OME. Just choose RACADM task when creating the task and provide the command and choose the target where you want to run the command. Do not use the word racadm when typing in the command in OME. There are sample tasks in OME which can help you in understanding how tasks are created and the white papers that i have been pointing to you, will be of great help for all the features in OME.