(OMi) Support Tip: How to test CI Resolver from command line

You can make use of the "opr-jmxClient" tool to easily test the CI Resolver from the command line. This tool is available on both DPS and GW servers in the following location:

Windows:
<HPBSM>\opr\support\opr-jmxClient.bat

Linux:
/opt/HP/BSM/opr/support/opr-jmxClient.sh


The following JMX methods are available to test the CI Resolver:

resolveHost:

opr-jmxClient -system <DPS_host>:29622 -user <user> -password <password> -bean "opr.ciresolver:name=CiResolverMBean" -method resolveHost -a opr -a <host_to_resolve_FQDN> 

E.g.:

C:\HPBSM\opr\support>opr-jmxClient.bat -system dps1.omi.local:29622 -user admin -password admin -bean "opr.ciresolver:name=CiResolverMBean" -method resolveHost -a opr -a testnode.omi.local
RMI URL = 'service:jmx:rmi://dps1.omi.local:29622/jndi/rmi://dps1.omi.local:29622/jmxrmi'
Result:

Resolution Result
HintCount: 1
matchedHintCount: 1
Ci Id: nt:418a0431a5bd4fd09c7e0ce2e2cc946f
Success: true
Ambiguous: false
Missing Monitor CI: false
Event Host: __nohost__
Host Context: null
Types List: []
Hints List: []
Result Message: [Host CI found by hint "testnode.omi.local"]
Result List: []


resolveHint:

opr-jmxClient -system <DPS_host>:29622 -user <user> -password <password> -bean "opr.ciresolver:name=CiResolverMBean" -method resolveHint -a opr -a <resolve_hint> -a <preferred_ETI>

E.g.:
C:\HPBSM\opr\support>opr-jmxClient.bat -system dps1.omi.local:29622 -user admin -password admin -bean "opr.ciresolver:name=CiResolverMBean" -method resolveHint -a opr -a testnode -a ""
RMI URL = 'service:jmx:rmi://dps1.omi.local:29622/jndi/rmi://dps1.omi.local:29622/jmxrmi'
Result:

Resolution Result
HintCount: 1
matchedHintCount: 1
Ci Id: nt:418a0431a5bd4fd09c7e0ce2e2cc946f
Success: true
Ambiguous: false
Missing Monitor CI: false
Event Host: __nohost__
Host Context: __nohost__
Types List: []
Hints List: [testnode]
Result Message: [Success: Hint "testnode" resolved.]
Result List: [{ testnode, id =418a0431a5bd4fd09c7e0ce2e2cc946f (nt): 30 }]

If CI Resolver cannot find the CI, you might need to check if there are any missing attributes in the CI or  whether the CI Hint from the event is correct. If you're still having issues with CI Resolution, you can also try to reload the CI Resolver cache:

opr-jmxClient -system <DPS_host>:29622 -user <user> -password <password> -bean "opr.ciresolver:name=CiResolverMBean" -method reloadCache -a opr