VMware vCOPs and vCNS Adapter – Better together

Yesterday VMware has made GA announcement of vCNS Management pack of vCOPs. We were using it internally even before GA though. So, I thought I will take up this opportunity to show what is the adapter is all about and how does it work and how you can make it to work.

The main purpose to build this adapter was to provide operational visibility into the core components of the vCNS with the use of vCOPs. So, one thing I can confirm you that, this adapter utilizes vShield API heavily to get the statistics and other details of Edge devices or even the plain vCNS product itself.

When vCOPs starts the discovery process, this adapter sends a vCNS API request to the vCNS to get the list of available Edge devices. For communicating with vCNS, this adapter firstly send an API request.

Collection of the statistics and status of the services happens by querying the Edge devices. For collection, each of the edges will be queried with vCNS API calls and the informations is converted into the metrics one can see in the UI. The API response provides all the values collected on the vCNS side.

What are the services it can monitor for their status and statistics?

  • Each connected interface of the Edge device
  • vShield Firewall
  • IPSec VPN
  • SSL VPN
  • Load Balancer

Where can you download this? Its the same place where you can get other management packs.

How do you deploy this adapter. Its the same way you add any other vCOPs adapter today.

  1. Login to your vCOPs Admin interface
  2. Go to the Update Tab
  3. Click on Browse and choose the adapter .pak file
  4. Click on Update
  5. Click on OK to confirm
  6. You will be asked to accept the terms and conditions, click on the check box and click on OK.
  7. Once you are done with the installation, you need to add the adapter instance in the Advanced Dashboard.
  8. Login to the vCOPs Advanced Dashboard.
  9. Select Environment -> Configuration -> Adapter Instances
  10. Select vCenter Operations Standard Server from the Collector drop down and select MP for vCNS as Adapter kind and click on the Add New Adapter Instance button.
    AdapterInstance1
  11. Specify a Adapter Instance name, VSM URL. Other things are optional.
  12. Click on Add in the Credential section.
  13. Specify a Instance name, VSM Username and Password. Other things are optional.
  14. Click on OK.
  15. On the final screen, click on Test and it should be successful. Click on OK to finish.

AdapterInstanceFinal

Once you are done, you will see a vCNS section in the Dashboards menu. Choose any of those and you will be presented with some precious custom dashboards.

These are the Dashboards you will be presented there.

  • vCNS Alerts
  • vCNS IPSec Stats
  • vCNS Load Balancer Stats
  • vCNS Service Status
  • vCNS SSLVPN & Firewall Stats
  • vCNS Overview
  • vCNS All Metrics Selector

These are couple of screen shots of the dashboards from my Lab.

vCNS Overview

vCNSOverview

vCNS All Metrics Selector

AllMetrics

 

4 thoughts on “VMware vCOPs and vCNS Adapter – Better together

  1. Hi,
    interested to install this, I get this error on vCOPs 5.8.1. Advanced Edition. Tried using both IE11 and Firefox 27.0.1 same issue at the end of the upload. Reboot of the vCOPs vApp same issue present.

    “vCenter Operations Manager is unable to display the EULA and cannot proceed. Please contact Technical Support for assistance.”

    Any help would be appreciated.
    cheers
    Ross

    • Hi,

      OK figured it out, the subtle difference is selecting the TRY button and downloading a zip file not the tgz. It then proceeds to show the EULA and install.
      cheers
      Ross

  2. Pingback: VMware vCOPs and vCNS Adapter – Better together (Stretch Cloud) | NMS Test

  3. Hi,
    have you configured the adapter to work with vCloud Director? If so, do you have an example of the vCD DB Connection String that worked ?

    I note that the VMware provided documentation with the adapter is also missing these examples and also does not define the necessary network ports that must be open between the vCNS and the vCOPs appliances. Only a problem when they are setup on different vlans of course, and that is exactly what you would do in the real world for added security.

    cheers
    Ross

Leave a Reply