SCOM Adapter Configuration for vCOPs

Summary:
I wanted to test the SCOM adapter in vCOPs to see what data I could get and see how it could be used.  Unfortunately, the VMware video demonstrating it's installation did not work for me without some tweaks.

Config:
vCOPs 5.7.1 (vApp)
SCOM Adapter Build 1036195

 Installing the Adapter:

  1. Log into your vCOPs admin page (Usually https://vcopsServer/admin)
  2. Select the Update tab and upload the 'pak' file

  3. Accept the EULA, wait.
    • Pretty much the same as updating vCOPs @ this point.
  4. Once completed, you need to log into the custom UI (https://vcopServer/custom) as an admin.
    • If you setup LDAP and made your account an admin, you're good.  Otherwise, you can login as the same admin account as the admin page.
  5. Once in the custom UI screen, hover over admin and select 'support'

  6. Select the 'Info' tab, click the gear to start the 'describe' process.

  7. Once the process is completed you should see the SCOM adapter available in the adapters info table.

  8. Congrats, the adapter is now installed.  Next we need to configure it to pull data.
    • If it's not there, you may need to restart vCOPs services.
SCOM Adapter PreReqs:
  1. SQL Account w/ dataread role access to the SCOM database.
    1. Windows account "MAY" work, but there may be a syntax problem.  I still need to test this more.

Configure Adapter Instance:
  1. At this point, watching the video would probably be easier than me typing it out w/ screenshots.
  2. If it works, GREAT!  If not, follow these next steps.
  3. SSH into the UI VM.
  4. Use VI to edit the scom.properties file.
    1. vi $ALIVE_BASE/user/plugins/inbound/msscom_adapter3/conf/scom.properties
    2. Click here if you need info on how to use VI.
  5. The line you need to change is jdbcDriver=jtds to jdbcDriver=sqljdbc
  6. Save your changes and now SSH into the Analytics VM and start @ step 4.
  7. Once done, try configuring the adapter again.  Hopefully this solves your problem.  It certainly solved mine.

Comments

Anonymous said…
Have you had any luck testing Windows Authentication with your SCOM adapter. When using the vAPP for vCOP there seems to still be an issue with Windows Authentication. VMware's recommendation was to put the SCOM adapter on a Windows box or just Authenticate with SQL
February 26, 2014 at 5:48 PM
Zsoldier said…
Haven't revisited this. It may be a combination of driver and username formatting.
February 26, 2014 at 7:26 PM
Anonymous said…
Hi, i tried to install vcops with SCOM, but i have the next error, " Failed to collect data from SCOM: invalid object name "managedEntityGenericView" "i hope that you can help me.
TKS.
April 21, 2014 at 5:24 PM
Post a Comment

Popular posts from this blog

NSX-T: Release associated invalid node ID from certificate

Image
Summary: Basically had an expiring certificate registered in NSX-T that was associated to a node_id that is no longer valid.  Long story short, there wasn't anything obvious in API to delete or disassociate a certificate from a node_id for 3.2.2.  Not sure how things got in this state, but annotating for future reference.  This may change in future revisions, so always check API for latest. Details: Effectively had a stale node associated w/ a certificate that was expiring.  Could not delete certificate until that node was disassociated from the certificate. To get certificate details and associated node_id's, you can use the following curl call (UI works too): curl -k -X GET -H "Content-Type: application/json" -u admin https://<manager ip>/api/v1/trust-management/certificates/<cert UUID> Above will return something like this: Below must be run from one of the manager nodes via elevation to root: ONLY RUN THIS IF YOU ARE ABSOLUTELY SURE OF WHAT YOU ARE DO...
Read more

NSX-T: vCenter and NSX-T Inventory out of Sync (Hosts in vSphere not showing up in NSX-T)

Image
Summary: NSX-T loses synch w/ vCenter inventory, but statuses don't appear to show an issue.  Basically, you add a host to a vCenter cluster, NSX-T bits should start to automatically installing on new host.  Assuming you've created a Transport Node Profile and associated w/ the cluster.  The problem is that NSX-T doesn't see the new host and its link to the compute manager (vCenter) looks fine. Looks fine, Y U NO WORK!? So what's going on here?  This appears to affect NSX-T 2.5 and 2.5.1.  Cause is unknown. Workaround: Restart the cm-inventory service on each NSX-T mgmt/controller node using API or CLI. Details: If you were to query the status of the cm-inventory via API or CLI, you could query all 3 manager/controller nodes and get a status of running.  Even if the primary node associated w/ the VIP, if configured, is not necessarily in charge of inventory.  So you could restart the cm-inventory service till you are blue in the face ...
Read more

MacOS: AnyConnect VPN client was unable to successfully verify the IP forwarding table modifications.

Image
The VPN client was unable to successfully verify the IP forwarding table modification.  A VPN connection will not be established. Summary: I started running into issue utilizing Cisco AnyConnect on my Mac basically complaining about not able to overwrite IP forwarding tables.  This was on 4.6.x.  Since my VPN endpoints were not providing me w/ an updated client and w/ no access to Cisco Anyconnect downloads, my only option was to try openconnect.  It was totally worth it, here is why and how to set it up. PreReqs: Homebrew Installing OpenConnect: Launch MacOS Terminal brew install openconnect Getting VPN IP's/DNS Endpoints from AnyConnect: The information is typically located in your profile xml files located here: /opt/cisco/anyconnect/profile/somethingsomething.xml In the xml file, you are looking for "<HostAddress>typicallyaDNSName.com</HostAddress>" entry.  These are your VPN endpoints that you would need to pass to openconnec...
Read more