OME 2.2: Inventory unclassified WSMAN

Similar Questions

• OME does not receive details of the inventory and the State for some devices

  OME does not receive the details of the inventory and the State for some servers.

  For example when looking at one of our PowerEdge R620s is all that presents itself:

  

  iDRAC firmware and LCC is updated (version 2.21.21.21 is installed.)

  I reset the iDRAC, and that did not help.  I have no problem with most of the other R620s in the same range of discovery.

  I deleted the object to OME and re-discovered twice over the past week it but did not help.

  Things seem ok when I use the troubleshooting tool:

  

  Anyone has any info on what may be going on here or how to fix this?

  Thank you

  Hello

  Thanks for the details in the post.

  Wanted to check what version of OME use you - OME 2.1?

  If so, this behavior with ws - man discovery could potentially due to expiry of certificate on this device. You can launch the iDRAC user interface and confirm the certificate information.

  2.1 the OME, the WS - Man communication component is updated. The most recent component does not communicate with the device if that device has been exceeded in the certificate.

  Sslresetcfg running via racadm will reset the certificate. For details and solution, see same threadhttp://en.community.dell.com/techcenter/systems-management/f/4494/t/19653767 .

  Let us know if that helps.

  Thank you
  Vijay

• OMSA on CentOS 5.7 - OME inventory

  Hello community,

  We use the OMSA on a CentOS Distribution 5.7 7.4. In OMSA all indicators are green. Now, I did an inventory of the system to the point 1.3 of OME. But the State of health of the system is grey (?). What can I do to get a status of green circuit. I have already configured snmp, but it does not work.

  Thanks in advance

  André

  Hi and thanks for the post.

  It is important to note that OMSA is ok on the managed node, it is not because you have configured entirely OMSA SNMP instrumentation.  Be sure to check this part of the guide of the OMSA user or the first installation steps in the tutorial of OME.  There could also be a white paper or video on it on the www.delltechcenter.com/ome page.

  Thank you

  Rob

• OME 2.0.1.2222 will add 13 gen servers for inventory

  Since a wile racking 13th generation of Dell in our data centers, we started and I noticed that most of them is not discovered by MOE.

  They are in the same network as the 'old' (gen 12) that have been discovered, with the same settings, the same username/password, enabled IPMI, SNMP enabled etc.

  On all these hosts that I see in the lifecycle sign on the next line, repeat several times "properly connected using root, xxx.xxx.xxx.xxx and WS - Man."

  iDRAC8 firmware version is 2.10.10.10

  Please hit me with some ideas

  Stef

  Hi Stef,

  A few questions:

  • Can confirm what protocol you are using to perform the discovery?
  • Are you able to connect to servers using this Protocol through the troubleshooting tool?
  • The required ports are open on these new servers as required by MOE for communication between server and OME?
  • Also, is there a specific IP range where you are not able to discover servers?

• OME firewall ports

  Hi all

  Can someone tell me if not secured such as HTTP and TELNET protocols are required for OME? Or they are just for the legacy support?

  I would prefer to use HTTPS and SSH to my deployment if possible.

  Any help would be appreciated!

  See you soon,.

  Ben Loveday

  Hi Ben,

  The discovery/inventory of servers (iDRAC/host operating system) works with wsman (idrac), snmp (with agent OMSA), wmi (windows OMSA agentless), ssh (linux agentless OMSA).

  There is a very limited use of the HTTP protocol in case you have a few switches Dell networking, in this case based only URL http application launch.

  OME 2.1 - User Guide (https://topics-cdn.dell.com/pdf/dell-openmanage-essentials-v2.1_User's%20Guide_en-us.pdf )

• OME 1.3: update R910 5.5 ESXi host through iDrac fails

  OME 1.3 fees deployed on a Server R2 Windows Server 2012. OME server is in the same subnet as the iDRAC.

  OMSA agent for ESXi 5.5 deployed, but not relevant since the updates of the system OME uses iDRAC for ESXi hosts.

  The R910 was discovered and inventoried by WS - MAN on iDRAC and OMSA bot successfully.

  Trying to make an update of the system. I find the server in noncompliant systems, select it, select all 4 applicable updates.

  I apply and provide the login of the iDRAC.

  The task fails with errors below:

  -J' tried with the online catalogue Dell as well as a local Manager of Repositry

  -J' noticed that the 4 updates all point to pacaages in. EXE format. Since the deployment through iDRAC they shouldn't be. BIN files?

  Results:
  Download the packages.
  The call of method InstallFromUri to download packages to the iDRAC

  Error occurred: A security error occurred
  Username and password are not valid or

  The component that is being updated is not valid. Re-run the inventory in order to determine the correct component, and then try again

  Error occurred: A security error occurred
  Username and password are not valid or

  The component that is being updated is not valid. Re-run the inventory in order to determine the correct component, and then try again

  Error occurred: A security error occurred
  Username and password are not valid or

  The component that is being updated is not valid. Re-run the inventory in order to determine the correct component, and then try again

  Error occurred: A security error occurred
  Username and password are not valid or

  The component that is being updated is not valid. Re-run the inventory in order to determine the correct component, and then try again
  Check the following: entered credentials are valid, iDRAC is accessible from the host OME and iDRAC is in good condition. IDRAC was unable to download all the packages.
  The task of software update failed.

  Hi Roger,

  Two questions:

  • What is the version of your R910 iDRAC6?
  • If you run the following command, then what is the result you get?

  WinRM e cimv2/root/dcim/DCIM_LifecycleJob - u: - p: - r: https: / //wsman:443 - SkipCNCheck - SkipCACheck - SkipRevocationCheck - auth: base - encoding: utf-8

  • Is it possible to restart your server? If so, can you check if CSIOR is enabled on the server and are you able to see running system services?

  You can get information about CSIOR on this link:

  http://en.community.Dell.com/TechCenter/systems-management/f/4494/p/19515744/20413397.aspx#20413397

• OpenManage Version Essentials 2.0 Firmware gather and pilot inventory

  Ive installed 2.0

  I have 2 inventory servers via "iDRAC (server out of band)" "WS - MAN".

  now, I'm trying to collect the inventory FW so I can test the upgrade of the drac fw.

  No matter what I do "error at least select a server.

  but the servers are not displayed... If I create a new group and add them to the group,

  Group is visible in the window "create F/W and pilot inventory task" but when I check the box and try to finish, he says always "error at least select a server.

  

  I am sure that this particular task is required for in-band system updates.

  Looks like you are using out of band (iDRAC/WSMan).

  In this case, I think you're all ready to go.  You discovered via WSMan, now just go on manage | Updates system and you should be able to see your report compliance and update from there.  You have no need for this task, that you try to create.

  Can you let me know if go to the update of the portal page system works for you?

  Kind regards

  Rob

  delltechcenter.com/OME

• OME 2.0.1 and Brocade M5424 fc switches

  Hello

  I have problem with OME discovery/inventory abd Brocade M5424.   4 M5424 brocades are defined as 2 M1000e chassis access gateways, problem is this discovery/inventory OME found as a fibre channel switch with 4 ip addresses.

  Inventory and discovery works well with all the other components of these 2 chassis, only fc switches I have this problem.

  M5424 have unique host names, single ip addr. and snmp is defined.  OME same troubleshooting tool gives me the correct result when the connection on these switches CF test.

  Anyone with the same problem?  Mode gateway may be the source of this problem?

  Thanks for any help

  Martin

  
  

• Where the das value the FQDN in OME Alert Message comes from

  If I place an alert Action to OME, OME provids the details of the alert Message to the script that I defined. In the alert Message, there are several types of information, such as Service number, alert and FULL domain name.

  Now, at one customer site OME reports for appliance name and domain FULL of different values. I was wondering where the FQDN value is taken. It is something of DNS or has he just iDRAC? If it comes to the iDRAC, I can configure it? Is this something I can configue on OME or iDRAC?

  OME performs a reverse DNS lookup.

  This is a list of name resolution that OME crosses top down

  1. If the inventoried by OMSA server then the FQDN DNS name servers
  2. iDRAC name DNS (Reverse DNS lookup)
  3. iDRAC (iDRAC host name parameter) host name
  4. IP address

  If you let the iDRAC registers in the system DNS enable this check mark.

  

• OME identifier does not PE 2970

  Hello

  OME2.1 is to discover our PE2970s but is not identifying as 2970's. The model appears as N/A under all devices.

  Serial No., DRAC IP and same Windows Server name are picked upwards, but not a model.

  Is there a way to help the OME to pick this up? :). I use only protocol WS - MAN to discover the details via the DRAC.

  In addition, m605 / m905 do not seem to be picked up at all by MEO. Should it?

  THX,

  John Bradshaw

  Hi John,.

  The simple rule I use is this:

  -For 12 and 13G using WSMan to iDRAC for discovery

  -To the pre - 12G (for example PE2950), use OMSA SNMP or WMI + OMSA (IP, iDRAC no host)

  Hope that helps!

  Rob

• The firmware version of incorrect declaration OME

  OME - 2.1 version

  After you run inventories using SNMP and WMI, most of our M610 blades is displayed as in need of various Broadcom and SAS6IR updated firmware, but when running updates on the server, we find the latest firmwares are already installed.  OME inventory shows that an update is required, but running OMSA and SUU on the servers watch the latest firmware is installed.  We have a mixture of servers on our network will worms PE1950 and different generations after that, all reports very well. The DUP is the same in the OME that SUU.

  Screenshot of SUU and OME below showing the difference. Search the forums or Google can't find someone with the same problem.  Any thoughts anyone?

  Thank you
  Justin

  Suu running on the server:

  MOE:

  Hi Pupul,

  Having travelled the beaches of discovery and exclusions, it was quite a complete mess so I removed all machines, deleted the inclusive ranges and exclusions and re-inventoried and all seems to be good at the moment and all versions correctly reported.  It will look again tomorrow, but for now, I would say everything is good!

  Thank you

  Justin

• OME v2.0 - ws - man to DRAC, General questions

  Hello

  I'm currently testing a number of things within my organization for OME. We have installed v2.0. I managed to use SNMP to enter a few servers for MOE, displaying information on material etc. However I cant seem to get DRAC using ws - man. Are there recommended references to use?

  On the DRAC and servers, if the hostname of a server is specified within the drac will create 2 entries separate devices? (one for the server, one for the drac) or it will merge the two?

  Thank you

  Hi and thanks for the post.

  If you have 12G or 13 G Dell servers, it is probably easier to simply discover the IP address of the iDRAC via WSMan (disable SNMP from the wiz of disc).

  If you _do_ discover the _and_ IP address band iDRAC (via WSMan) via SNMP + OMSA, it should merge the data in an entry.  But for the sake of simplicity, it is sometimes easier to do how I mentioned above.

  Just be sure to hit all the checkboxes on the page of the wizard for the discovery of WSMan.  If you still have problems, you can try the WSMan test on the Dell troubleshooting tool.

  Kind regards

  Rob

  delltechcenter.com/OME

• Hardware inventory to the iDRAC 6

  Hi all

  I use dell servers m610 (iDRAC6). We have built a tool to get hardware information of dell m610 using wsman via iDRAC 6. But when I got some information about hardware (Ram, CPU, HARD disk) using wsman, I had old infofmation. When I installed more RAM or connected several hard drives. I always have information on old hardware.

  + Example command. wsman list http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/root/dcim/DCIM_MemoryView h $IPADDRESS v - v - c dummy.cert 443 u $USERNAME $PASSWORD-j utf-8 Pei Pei - y basic.

  + management list http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/root/dcim/DCIM_SystemView h $IPADDRESS v - v - c dummy.cert 443 u $USERNAME $PASSWORD-j utf-8 Pei Pei - y basic

  I know an option of life cycle for the latest information on the hardware, is to allow to "collect system inventory on restart (CSIOR). But I have to restart the server for.

  Is there a way to get the latest information of hardware without restarting the server?

  Thank you very much

  nampnx

  Hi nampnx,

  You must enable CSIOR. This is a configuration of time. After that, whenever you add new hardware when the system boots, CSIOR will run for the POST. This will give you some info on iDRAC that new hardware has been added. Else iDRAC will not get to know the additional hardware.

  Kind regards

  Jean-Pierre

• Not sent to OME SNMP alerts

  Hello

  I have a small problem to configure my switch PowerConnect 5448 to talk to my open Server Management Essentials.

  I set up the snmp trap as in 'Making my environment Manageable.pdf.

  And by using troubleshooting utily of OME, I am able to communicate with the switch.

  The problem is that one of the fans is out of service and I don't have any information about this at OME.

  My question is, I have to implement something more (MIB,..) in OME or switch?

  In addition, the fan was out of use before you configure snmp interruptions... but I saw that OME see events of the month of other machines before they have been implemented...
  The show snmp output is:

  See the snmp console #.

  SNMP is enabled.

  Community community-access view name IP address string
  -------------------- ------------------ -------------- ------------
  dell_ome read only OME srv IP default
                                                                  
  Dell_Network_Manager read write DefaultSuper All
   
  Group Community-String name address IP Type
  ------------------ ------------ ------------------- ------
   
  Traps are enabled.
  The authentication failure trap is enabled.

  Notifications of the version 1, 2
  Udp target address community Type to the attempts of Version filter
  Name of the dry port
  ---------------- -------- ----------- ---------- ----- ------- ----- ---------
  OME srv IP trap dell_ome 2 162 0 0

  Notifications of version 3
  Udp security target address Type attempts username filter
  Name of the dry Port level
  [0mMore: , quit: q, one line:]
                                              
  ---------------- -------- ----------- -------- ----- ------- ----- ---------
  Console #.

  I have nothing under SNMP 3 and can't seem to enable it

  show the system - part fan:

  Power supply Status: OK
  1 table of fan: OK
  Fan 2 status: NOT OPERATIONAL
  Fan 3 Status: OK

  And OME comes to shows me that everything is 'green' on this switch.

  I searched Google and Dell times but can't seem to find more details, so I ask here if someone could help me :)

  Thank you!

  Best regards

  Liliana

  Hi and thanks for the question and good detail.

  So I guess the switch is displayed correctly in the OME devices tree and when you click on it you get a bit of inventory information, etc.  And you said that health currently appears green.

  OK, so if the alert happened in the past (before the implementation in OME), then you won't see in the alert console OME.  The thing that you might have seen, is if some type of device sends the same alert repeatedly.

  You confirm that you have changed the SNMP settings on the switch to run the SNMP alerts to the IP address of the server OME?  Your message makes it look like you have done this correctly, assuming that the IP address is correct.

  For some switches, just the Act of logging in the switch will generate an information alert.  Not sure about this model.  See you new alerts in OME this switch or you have a way to generate an alert of the switch as test by logging?

  BTW, OME has no support for v3 alerts, only v1/v2.

  Thank you

  Rob

• Critical error OME: systems are down

  Morning Dell.

  OME Dell performs a discovery and inventory every morning and every morning a couple of my systems are reported as "down", with no other information. It is sometimes several servers, other times it's just a server that is down repeatedly. It happens every morning when OME performs this check. Also, both of my KVM are supposed to be 'down', but I can connect to these servers remotely so I know they are on the rise. Any Suggestions? Is it a software update is necessary?

  I'm runing OME v 1.1.0.6063 and the hosts are R620s.

  Thanks in advance.

  Sorry, here's the fix - en.community.dell.com/.../20358671.aspx