VCM5034 - Troubleshooting w/ Log Insight and vCOPs @ Cox Communications Extras!

We unfortunately did not demo the vCOPs integration w/ Log Insight.  I did record those videos though so I figure I would share them here.  No audio, but just videos.

Here we are demonstrating the 'context' awareness menu where you can select an object in vCOPs, in this case a VM, and jump into Log Insight w/ a pre-populated query.  It's only context aware from the aspect of object selection, meaning, the VM and the host it's running on, but imagine the integration possibilities.

This second video just shows how you can make custom queries and just by aspect of those entries showing up, send an associated alarm to vCOPs for tracking/notification purposes.  The video shows you the idea of finding 'cloned vm' entries and having log insight insert those as a specific type of alert in vCOPs.  The video is poorly edited and is meant to show you the 'concept':


Anyway, feel free to post comments here.  I'm always monitoring and willing to answer questions.  Hope you enjoyed our session and got something out of it.


Comments

RightMac said…
Why didn't you get to demo?
August 30, 2013 at 7:24 AM
RightMac said…
Why weren't you able to demo?
August 30, 2013 at 7:24 AM
Zsoldier said…
We were more focused on the 'how' rather than the ancillary functions.
August 30, 2013 at 9:58 AM
Kimberly Horte said…
Hey Chris,

My name is Kimberly Horte. I saw your account on LinkedIn and I wanted to reach out to you about a couple of career opportunities I have. One is a Virtualization Engineer position, but I also have a Deployment Engineer position that is just stellar! I know it's kind of weird to reach out to you via your blog about this, but I ran out of inmail credits! Please e-mail me back at kimberly@smart-tek.net. Have a great day!
September 6, 2013 at 9:07 AM
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