Hello. On this video, we will learn about the open manage integration for BMW appliance and how to fix echoes with compliance errors. When one of our host is added to own my UB, the appliance runs a series of prerequisite checks. If one or more of this test fails, the host will be listed in the complaint staff or maybe we provide a wizard interface to attempt to fix these issues. In most cases, it is able to address any underlying problems and allow the host to act successfully.
The actions that o my checks for are WBM for communication with the ESX I host seor to collect system inventory from the A RS and MP trap actions to monitor the system's events and that the host meets the minimum required framework for the address. And that is part of the connection profile. In this case, the host is still showing with an error taking a look at the log. So we can see that the entry states that the SNNP alert destination is full on the IR. In order to fix this issue, we will need to go into the IR and ensure that we have an available SN MP trap destination space.
Since we're only going to use this host for my B I will blank out all the entries under the alerts tab. However, if a customer is using other SN MP monitoring applications such as open manage, enterprise support assist or open manage essentials, we will only need to ensure that we have an available slot for OIBB. The customer can then choose to keep the other entries. Once we do this, we can run the fix complaints. Wizard inside or maybe one more time.
What we're expecting to see is that once the wizard finishes the host disappears from the compliance list. As you can see, the host has disappeared from that non compliance list. And finally, we can check the address and we will see that the SN MP destination for IB is listed there in the form of its IP address.
Thank you for watching this video. This is Miguel.
