OME 3.1: configuration inventory and compliance baselines
Hey,
I am having a hard time figuring out how to create and actually run a compliance baseline.
I've 1) created a deployment baseline from reference device 2) a compliance template based on the deployment baseline and 3) a compliance baseline based on that.
Configuration inventory and Configuration compliance tabs on a specific server are empty.
Apparently OME is lacking the servers' configuration inventory. Indeed, looking at "Monitoring - Jobs" at 01:00 AM a Configuration inventory job failed with the error: SYS045 --> Unable to copy the Server Configuration Profile to the network share.
What network share is it talking about??? Of course I've looked at OME User's Guide but to no avail.
Note: We do have iDrac Enterprise and OME Server configuration licenses installed alright.
The share in question here is the internal share carried by OpenManage Enterprise to copy the information from iDRAC. You will need to make sure that all the necessary ports required to run Configuration Inventory are enabled between iDRAC and appliance. Please look at the details in this link:
Well it's in the same subnet so it wasn't a network issue.
I don't know what fixed it, maybe the problem was not having configured an online repository yet at all. Also, maybe inventory of servers wasn't entirely complete. One should take care to "Run inventory" with config inventory if in doubt.
That part of the setup is really not straightforward but now it's working.
In general, OME (3.x) is quite a nice tool, it's a shame that it took until the year 2019 for something similar to exist.
I ran into this problem recently as well. Our OME instance was on another subnet from the rest of our iDRACs. We verified there was no network traffic being blocked between the two networks. After much troubleshooting, I built up a new instance of OME and it started working.
It looks like there was maybe some corruption going on with our original OME instance.
schwinger04
3 Posts
4057
0
Posted January 15th, 2019 13:00
I ran into the same issue as well.