Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Verified Answer
  • Replies replies
    2
  • Subscribers subscribers
    164
  • Views views
    165
  • Users 0 members are here
Related
Options

Mismatched Server Realms after adding vCenter servers with fakevCenter

Sharp_2

We have added vCenter servers using the fakevCenter tool in support/bin and since doing so, we always have the error when running diagnostics.

Mismatched Server Realms (Finds any servers whose Realm doesn't match its Realm RoleClass.) : Servers with mismatched Realm relationships:  [138670001, 176730001, 146100001]

Has anyone figured out a way to get the diagnostics to ignore these? When we run the cli diagnostics it errors out part way through as well:

/opt/opsware/oi_util/bin/run_all_probes.sh run

Mismatched Server Realms (Finds any servers whose Realm doesn't match its Realm RoleClass.) : Servers with mismatched Realm relationships: [138670001, 176730001, 146100001]
--------------------------
(Local execution failed - exit code 1)

[Summary]
1 of 1 hosts are valid Opsware core systems.
4 of 7 validation probes passed.
[root@mysaserver ~]#

Thanks,

/A

  • Verified Answer

    +1

    Problem solved. Seem when I ran the ./fakeVCenter --ip 10.10.10.20 I neglected to include the --realmid and it defaulted to one of the realms under the primary core. We have 3 listed - Core1, Core1-agents and Core1-mm. It assigned the vCenters to Core1-agents instead of Core1.

    So I removed the virtualization servers, deactivated, deleted and waited 20 minutes.Ran garbage collection manually for good measure.

    Next I added the vCenters back using ./fakeVCenter --ip 10.10.10.20 --realmid 40001 and now there are no more errors running diagnostics. From the man page:

    .B \-\-ip <vcenter_ip>
    This mandatory argument is the IP address of a vCenter
    .TP
    .B \-\-realmid <id>
    Option argument of the realm to create the device in, if not supplied
    the Realm of the facilty where the script is executed is computed.
    .SH USAGE
    This example will integrate a vCenter at 192.168.1.35, first mock the server.

    # fakeVCenter --ip 192.168.1.35

  • 0   in reply to 

    Make sure you are using at least OPSWtools-2.0.40 there was a bug that created realm mismatch errors.
    This switch is handy to correct data created by prior version --fixIntegrity
    Or just delete them, use the latest version of the tools, and create them again.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.