OMSA on CentOS 5.7 - OME inventory

Similar Questions

• OMSA on CentOS/RHEL 7

  Hi all!

  I want to get the work of the OMSA on my old PowerEdge 2950 server. OMSA 7 works well with CentOS 6, it will be available on CentOS 7 too?

  Thank you.

  I know me:

  www.dell.com/.../DriversDetails

  It seems that the version 7.4.1 supports 12g (or earlier?) material and RHEL 7 dated November 21.

  Best,
  Martin

• CentOS 6.4 DELL OMSA error - PE 1950

  Hi all

  I managed to install the DELL OMSA on CentOS 6.4 [64 bit] on a Poweredge 1950 server without too much problem.

  PROBLEM:

  After installation, I have the following problem/error watch and need help where in the file 'invc ol' the following shall be published or how to solve the following...

  / opt/Dell/srvadmin/sbin/invcol:. / invcol: /lib/ld-linux.so.2: bad ELF interpreter: no such file or directory

  Your comments would be appreciated!

  Thank you

  -Hiphoptech

  Hi Hiphoptech,
  Try to install the binary 32 bits of libstdc ++ and zlib
  yum install compat-libstdc ++-33 - 3.2.3 - 69.el6.i686 zlib.i686

• 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

• 2.2 - ESXi - no State health of OME

  I try to get OpenManage Essentials 2.2 health of ESXi.

  A server ESXi 5.1 and OMSA 7.4 Health Watch
  Servers with 6 ESXi and 8.3 of the OMSA only show a grey question mark.

  I can find no documentation indicating which versions of ESXi and OMSA is compatible with 2.2 OME.

  I found that something was off with the OMSA package deployed via the Update Manager. It showed as being in line with the base line, but I re-uploaded VIB in the Nativity update repository, created a new base line and attached hosts. The hosts showed now also fort and OMSA installed OK.

  OME now see the health status.

  But, under Data Sources in the display of the device, the administrator of the server (storage management) and VMware ESXi have a triangle of yellow warning next to them. How will I know what is the reason for these warnings?
  

• Newbie Help - OME Setup - alert Email does not

  Hello

  I try to set up HOME in our Windows domain, but cannot work out why email alerts do not work. Here are the steps that I realized so far:

  • Installed OME v2.0.1.2222 on a server Dell PowerEdge R210 II running Windows Server R2 2012
  • Installed OMSA v8.1.0 on a server Dell PowerEdge R720xd running Windows Server R2 2012
  • The OMSA server, ensure that SNMP interrupts are enabled for all alert & under Alert Actions, enabled Alert on Console & broadcast Message. Platform event filter alert has also enabled
  • Compatible SNMP on both servers and set a unique name for the community & followed the instructions on section "Initial Setup" on the OME itself (what I need to enable ' send trap to authenticate on the server of the OMSA?)
  • On the OME server, configure settings for test purposes, set up to send alerts for all devices & categories & e-mail alert
  • Discovery of the network enabled on servers and made sure that network discovery & & Traps SNMP Service are defined as applications are allowed on the Windows Firewall
  • I sent an e-mail message to test from the server of the OMSA and it happens to the designated mailbox

  I can see alerts when I go on manage-> alerts on server for the server of OMSA OME, but no emails get releases by agencies.

  What Miss me?

  I'm having the same problem as you when I create an alert with the name action: "All issues" with another name works as it should.

  This probably has something to do with the fact that there is a view log of alerts with the same name.

  

• OME firewalls and ports configurations required

  I installed OME in a locked DMZ that is highly secure and has a number of different segments of network separated by firewalls... I installed OMSA on Windows physical server and ESXi 5.1 2012 hosts. I also have the physical hosts running Linux OS. OME can successfully connect to the iDRAC for each server, but not in OMSA

  Can you please indicate exactly what firewall ports must be opened to allow communications between OME and OMSA as well as between OME and iDRAC?

  Thank you

  Hi and thanks for the post.

  There should be a table in the user guide OME (online that came with the product, or at www.delltechcenter.com/ome.  The table is called:

  Support for protocols and Ports OpenManage Essentials

  And should highlight the ports you need.

  Thank you

  Rob

• Support DSA NX3300?

  Ladies and gentlemen,

  One of my clients recently installed NX3300.

  NX3300 use Windows Storage Server R2 2012 as an operating system,

  And the material is based on server r.620 EP.

  But I can not find NX3300 to the matrix of Support of OME. (NX3100, NX3500 is available)

  DSA supports the NX3300?

  I think that two method can affordable

  -Install OMSA

  -iDRAC discover via OME

  NX3300 is not officially supported by OME 2.1, so it is not supported by SupportAssist as well. I checked DSA 2.1 matrix and did not find this entry.

  Thank you

  Knockaert

• DRAC 4 - problem with password reset

  Hello

  My company bought used/refurbished Dell R200 server with DRAC 4/p card. Now, I'm trying configure/reset password for DRAC 4 (v1.75 A01 fw) to the server. Server running Win 2008 x 64 std.

  As a first step, that the seller forgot to put with ribbon cable card, so I had to do it myself after I got it... Back to story :) at the start, I have configured DRAC (Ctrl + D; set IP DNS & - I do not see 'reset password' option), I also configured BMC to tunnel IP too (I think that's not important).

  Then, after I got windows running nicely (WU, net. FW + soft base; I did while waiting for flat cable). Once I got the cable, I have configured the DRAC at boot time, and then I went to interface http and received the error of connection (for root and calvin). In the meantime, I had to grasp because victory could not find drivers for dell DRAC: (.)

  So I installed OMSA ManagedNode x 64 (v7.4.0.2) tools RDCA (Setup did not find my card too...). Now the server startup time tripled :/ (don't know what did OMSA / or make at startup...), but nice after starting web server interface OMSA works, I can see the status of the HDD, the sensors, the tensions - almost what I need, but nothing on the DRAC (BMC only).

  Started administrator cmd and typed:

  C:\Windows\System32>racadm racresetcfg
  ERROR: Cannot perform the requested operation

  And:
  C:\Windows\System32>racadm getsysinfo
  ERROR: Cannot perform the requested operation

  So now, I think that something is not ok, but what? DRAC is broken (said kindly) or soft cannot talk to the card...

  Can anyone provide some tips?

  Hello

  I did an extra test (before leaving the workstation) and OMSA CentOS Live image downloaded and tried running the racadm - same result then the card should be broken.

  Seller has decided to replace the card because "a very likely card is broken." So now I wait for the new card.

  If I remember, I'll post summary :)

  -Summary-

  I got more than 2 cards of seller. None of them worked, firmware update found card, updated at the latest but racadm wouldn't work: (.)

  I'm packing cards back to give their feedback to the seller, but I decided to check once more... If I put each a card server and I tried the OMSA Live CentOS run racadm getsysinfo [/ i].
  I don't know if I would be really happy but one of the DRACs replied :), so without hesitation, I run "racadm racresetcfg" and I had no errors (happy), so I waited a moment for card to reset, and then rerun the getsysinfo but there not as before, but now I can log in the web and I changed my password.

  I suspect editing card, but the PREV raid card works very well, there could be something offshore with this putting on drac PCI slot. Seller also admitted that he had specially the elevators in order to install the drac4 card.

  I consider this as solved :)

  PS. Sorry for my bad English.

• OME 2.2: Inventory unclassified WSMAN

  Our displays is an upgrade to 2.1 OME (where we also had the problem)
  We are using WSMAN to inventory our DRACs and they are marked as not classified

  Note: on a test OME 2.0 Server, using the same configuration everything works as expected.

  The troubleshooting tool works normal when selecting these options and WSMAN
  Jump CA control
  Skip CN Check

  Using winrm, there is no output and no error message?

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

  Which version is the lifecycle controller and BIOS on server 11G (iDRAC6)?
  What is the server model?

  Another thing you can try is to restart once iDRAC.

• 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

• Dell OMSA GUI reference works don't not with 6.4 CentOS 64 bit

  Hello

  I am trying to install the DELL OMSA on my Dell Poweredge 1950 with no luck setting the GUI part on the server, so I can use the link "https://localhost:1311" in all of our business network.

  The problem is that I've done the following to at least be able to use the CLI portion only:

  http://www.md3v.com/install-Dell-OpenManage-on-CentOS-6-4

  It is a very useful script that I found online to allow at least the installation works fine. I can't access the web interface, it continues to tell me Elinks or any external browser "unable to access".

  I also have openssl installed with wget and perl. I don't know what keeps me to get the portion of browser to work. Please help!

  Here are the currently used version of CentOS kernel:

  CentOS 2.6.32 - 358.el6.x86_64

  Thank you.

  Hello

  What version of OMSA are you using? Sometimes the older versions work better on the older hardware. What does
  

  srvadmin-services.sh status
  

  show? You may also want to try adding a non-root user to /opt/dell/srvadmin/etc/omarolemap
  

• 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 )

• 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.