Machine ID Match (MID) test

This test checks whether the MID that the Agent reported matches that recorded in the Model Repository (SA data repository).

You can receive four possible errors from the Machine ID (MID) Communication Test:

• MID – OK
• MID – Untested
• MID – Unexpected error
• MID – MID mismatch

MID – OK

No troubleshooting necessary.

MID – Untested

This result is returned when a functional area cannot be tested, because of a previous failure that prevents further testing. For example, if the Agent cannot reach the Model Repository, then no other tests are possible.

What can I do if a test is not run during an MID test?

First resolve all tests that failed, and then run the Communication Test again.

MID – Unexpected error

This result indicates that the test encountered an unexpected condition.

What can I do if I get an unexpected error during an MID test?

First resolve all tests that failed, and then run the Communication Test again. If the unexpected error recurs, check to see if any additional details in the error message indicate the problem. If the error cannot be resolved, contact Hewlett Packard Enterprise Customer Support.

MID – MID mismatch

This result indicates that the MID that the Agent reported does not match the recorded MID in the Model Repository for that Agent. The likely cause is that the Command Engine is running the test against the wrong Agent.

What can I do if the MID is mismatched during an MID test?

To troubleshoot this error:

Check the Network Settings tab for the server in the SA Client to see if NAT is in use for this server. If it is, make sure that static, 1-to-1 NAT is being used. Server Automation requires that all managed servers be reachable on a distinct, consistent IP address, so configurations that assign addresses dynamically or use port-based translation are not supported.

If the Agent is installed on a cluster, check that each node in the cluster has a unique IP address at which it can be reached. You might have to add static routes to the server to ensure that connections made from that server to the SA core use the unique IP. If NAT is not in use, you can alternately mark the correct interface as the “primary” interface from the Network node under the Inventory panel in server browser, via SA Client.

The IP address might have changed recently. If this is the case, stop and restart the Agent. For these instructions, see Restarting a Server Agent.