Configure the NSX Controller instances for the ROBO cluster to forward log information to vRealize Log Insight in the ROBO by using the NSX REST API. You can use a REST client, such as the RESTClient add-on for Firefox, to enable log forwarding.

Prerequisites

On a Windows host that has access to your data center, install a REST client, such as the RESTClient add-on for Firefox or Postman add-on for Chrome.

Procedure

  1. Log into the Windows machine that has access to the ROBO data center.
  2. In a Firefox browser, go to chrome://restclient/content/restclient.html .
  3. Specify the request headers for requests to the NSX Manager. 
    1. From the Authentication drop-down menu, select Basic Authentication
    2. In the Basic Authorization dialog box, enter the following credentials, select Remember me and click Okay.

      Authentication Attribute

      Value

      Username

      admin

      Password

      nycnsx_admin_password

      The Authorization:Basic XXX header appears in the Headers pane.

    3. From the Headers drop-down menu, select Custom Header
    4. In the Request Header dialog box, enter the following header details and click Okay.

      Request Header Attribute

      Value

      Name

      Content-Type

      Value

      application/xml

      The Content-Type:application/xml header appears in the Headers pane.

  4. Contact the NSX Manager to retrieve the IDs of the associated NSX Controllers.
    1. In the Request pane, from the Method drop-down menu, select GET.
    2. In the URL text box, enter the following URL, and click Send.

      NSX Manager

      URL

      NSX Manager for the ROBO cluster

      https://nyc01nsxm01.rainpole.local/api/2.0/vdn/controller

      The RESTClient sends a query to the NSX Manager about the installed NSX controllers.

    3. After the NSX Manager sends a response back, click the Response Body (Preview) tab under Response.

      The response body contains a root <controllers> XML element that groups the details about the three controllers that form the controller cluster. 

    4. Within the <controllers> element, locate the <controller> element for each controller and write down the content of the id element. 

      Controller IDs have the controller-id format where id represents the sequence number of the controller in the cluster, for example, controller-2.





  5. For each NSX Controller, send a request to configure vRealize Log Insight as a remote syslog server.
    1. In the Request pane, from the Method drop-down menu, select POST, and in the URL text box, enter the following URL.

      NSX Manager

      NSX Controller in the Controller Cluster

      POST URL

      NSX Manager for the ROBO cluster

      NSX Controller 1

      https://nyc01nsxm01.rainpole.local/api/2.0/vdn/controller/controller-1/syslog

      NSX Controller 2

      https://nyc01nsxm01.rainpole.local/api/2.0/vdn/controller/controller-2/syslog

      NSX Controller 3

      https://nyc01nsxm01.rainpole.local/api/2.0/vdn/controller/controller-3/syslog

    2. In the Request pane, paste the following request body in the Body text box and click Send.
      <controllerSyslogServer>
         <syslogServer>nyc01vrli01-cluster01.rainpole.local</syslogServer>
         <port>514</port>
         <protocol>UDP</protocol>
         <level>INFO</level>
      </controllerSyslogServer> 
    3. Repeat the steps for the next NSX Controller.

  6. Verify the syslog configuration on each NSX Controller. 
    1. In the Request pane, from the Method drop-down menu, select GET, and in the URL text box, enter the controller-specific syslog URL from 5.
    2. After the NSX Manager sends a response back, click the Response Body (Preview) tab under Response

      The response body contains a root <controllerSyslogServer> element that represents the settings for the remote syslog server on the NSX Controller.

    3. Verify that the value of the <syslogServer> element is nyc01vrli01-cluster01.rainpole.local.

    4. Repeat the steps for the next NSX Controller.