Hello. Today we'll talk about OpenManage Integration for VMware vCenter
and how to troubleshoot management compliance issues.
In order to check if any of our servers are having problems identifying information to OMIVV, we can
click on the 'Compliance and Deployment' section and scroll down to 'Management Compliance'.
So you can see there are no services listed in this view,
which means that all my servers that are tied into OMIVV are compliant.
For this example I will trigger an error on the host so that we can troubleshoot
WBEM and WSMAN issues. When hosts are not compliant this is the view that we will get
under 'Management and Compliance'. All my servers will be listed there
within a status of 'Unknown' for anything that may not be enabled, or that OMIVV cannot detect.
The first step that we can take to fix compliance on any of these hosts is to click on the 'Fix
Compliance' button available on this section. The 'Fix Compliance' button will bring up a wizard
that will allow you to fix the WBEM configuration and SNMP tabs for any of the hosts. Anything that
needs to be fixed will be listed on this view. Any host that is compliant with all of the sections
will not show up on this list. So you have the option of performing the actions of
one or more hosts. As an example, if any of the iDRAC firmware was not compliant,
for example the minimum requirement is 2.52.52 for iDRAC 7 and 8, it would also
give you an option to update the iDRAC firmware on this section.
So in this case I'm going to click on all my hosts, click 'Next', it will provide me a summary
of the changes that will need to take place. Once those are confirmed you can click on 'Finish',
and then the wizard will attempt to fix those issues. The wizard may take
a few seconds to several minutes depending on what needs to be fixed on each of the hosts.
If the wizard completes the changes successfully
none of the hosts will show up in this view, which means that those hosts are compliant. At
this point if there were any errors on any of the hosts they will still show up on this view.
Another way to confirm is if you click on 'Logs' you'll see a summary of all the actions that took
place, including setting up the trap destinations and if WBEM needed to be enabled it would also
be listed here. So in the case that you were troubleshooting whether a host had WBEM enabled
or not you can do a filter search, and it will tell you any of the steps that it completed. So
in this case for this host with this IP address, WBEM was disabled, OMIVV set it to enabled.
Once it obtained and gathered the information from the host it set it back to a disabled state.
For troubleshooting purposes you can actually log into the host via SSH and enable WBEM if needed.
In this case I am going to log into one of the ESXi hosts and provide an example of
what can be done in regards to WBEM. In the case that WBEM was set to disabled
and the OMIVV appliance was unable to get any of the information
you can check the status by running this command, which is 'esxcli system wbem get'
If the service was disabled you could rerun that same command, delete the 'get' portion,
perform a '--enable' and then set the value to 'true'.
Oh, in this case it seems that I forgot the actual
action, which is 'set'. So 'wbem set --enable' and then 'true'.
Next we can restart the watchdog service just in case that there were any issues with that service.
It provides management services for ESXi. In this case I'm going to trigger a restart.
And if in case there were any issues with WSMAN you could also run a command for WSMAN which is
'/etc/init.d/wsman' and then 'start'.
In this case OpenWSMAN is already running, so there are no actions taking place. At this
point we could go back to OMIVV and attempt to fix compliance again by rerunning that wizard,
or we can go into the 'Job' section and go down to 'Host Inventory'.
Click on your connection profile and then click on 'Run Now'. At this point it would
run the inventory on all the host, and it will reach out to ESXi, the iDRAC and obtain
the information that it needs in order to obtain the inventory information for those hosts. So at
this point we're done with this presentation, thank you for your time, and have a good day.