Sunday, September 24, 2017

Configuring a Syslog Server for NSX Controller

If you configure a syslog server for NSX controllers, NSX Manager sends all audit logs and system events to the syslog server. Syslog data is useful for troubleshooting and reviewing data logged during installation and configuration. The only supported method on configuring the syslog server on the NSX controllers is through the NSX API. VMware recommends using UDP as the protocol for syslog.

Procedure



  1. To enable syslog on NSX Controller, use the following NSX API. It adds controller syslog exporter and configures a syslog exporter on the specified controller node.
    Request
    POST https://<nsxmgr-ip>/api/2.0/vdn/controller/{controller-id}/syslog
    Request Body:
    <controllerSyslogServer>
    <syslogServer>10.135.14.236</syslogServer>
    <port>514</port>
    <protocol>UDP</protocol>
    <level>INFO</level>
    </controllerSyslogServer>
  2. You can query the controller syslog exporter and retrieve details about the configured syslog exporter on the specified controller node using the following NSX API.
    Request
    GET https://<nsxmgr-ip>/api/2.0/vdn/controller/{controller-id}/syslog
    Response Body:
    <?xml version="1.0" encoding="UTF-8"?>
    <controllerSyslogServer>
    <syslogServer>10.135.14.236</syslogServer>
    <port>514</port>
    <protocol>UDP</protocol>
    <level>INFO</level>
    </controllerSyslogServer>
  3. If not required, you can delete controller syslog exporter on the specified controller node using the following NSX API.
    Request
    DELETE https://<nsxmgr-ip>/api/2.0/vdn/controller/{controller-id}/syslog
For more details about NSX API

https://docs.vmware.com/en/VMware-NSX-for-vSphere/6.3/nsx_63_api.pdf

Saturday, July 29, 2017

Manual Installation of NSX VIBs on ESXi Host

In this article I am going to demonstrate how to manually install NSX VIBs to ESXi host.

First of all we need to know the exact location of VIB files on NSX manager, once you know the vSphere version you are using, post that hit the URL to know the VIB location for that vsphere version.

https://<NSX-IP-Address>/bin/vdn/nwfabric.properties

In this out put you will see the PATH for VIBs as per vSphere version.

Out come of above URL will be something similar to :
================================================================
# 5.1 VDN EAM Info VDN_VIB_PATH.1=/bin/vdn/vibs-6.2.0/5.1-2107743/vxlan.zip VDN_VIB_VERSION.1=2107743 VDN_HOST_PRODUCT_LINE.1=embeddedEsx VDN_HOST_VERSION.1=5.1.*
# 5.5 VDN EAM Info VDN_VIB_PATH.2=/bin/vdn/vibs-6.2.0/5.5-2983935/vxlan.zip VDN_VIB_VERSION.2=2983935 VDN_HOST_PRODUCT_LINE.2=embeddedEsx VDN_HOST_VERSION.2=5.5.*
# 6.0 VDN EAM Info VDN_VIB_PATH.3=/bin/vdn/vibs-6.2.0/6.0-2984108/vxlan.zip VDN_VIB_VERSION.3=2984108 VDN_HOST_PRODUCT_LINE.3=embeddedEsx VDN_HOST_VERSION.3=6.0.*
# Single Version associated with all the VIBs pointed by above VDN_VIB_PATH(s) VDN_VIB_VERSION=6.2.0
# Legacy vib location. Used by code to discover avaialble legacy vibs. LEGACY_VDN_VIB_PATH_FS=/common/em/components/vdn/vibs/legacy/ LEGACY_VDN_VIB_PATH_WEB_ROOT=/bin/vdn/vibs/legacy/
==============================================================
In my example I am using vSphere 6.0 so see in above outcome I highlighted the path for NSX VIBs for vSphere 6.0

Then I need to open the URL


https://<NSX-IP-Address>/bin/vdn/vibs-6.2.0/6.0-2984108/vxlan.zip

This will download the vxlan.zip file to your system, now you can upload the same to one of your ESXi Datastore. So that you can install the same using esxcli.

Connect esxi using SSH and then run the command 
esxcli software vib install -d "Complete path of vxlan.zip file"




Thursday, May 18, 2017

Top Free Courses from VMware (eLearning)

While you are preparing for VMWare products and want to explore more, use below link to start exploring.

https://mylearn.vmware.com/portals/www/mL.cfm?menu=topfreecourses


Saturday, May 13, 2017

Setting the Logging Level of NSX Components

You can set the logging level for each NSX component.
The supported levels vary by component, as shown here.

nsxmgr> set
  hardware-gateway  Show Logical Switch Commands
  PACKAGE-NAME      Set log level
  controller        Show Logical Switch Commands
  host              Show Logical Switch Commands

nsxmgr> set hardware-gateway agent 10.1.1.1 logging-level
  ERROR
  WARN
  INFO
  DEBUG
  TRACE

nsxmgr-01a> set <package-name> logging-level
  OFF
  FATAL
  ERROR
  WARN
  INFO
  DEBUG
  TRACE

nsxmgr> set controller 192.168.110.31
  java-domain    Set controller node log level
  native-domain  Set controller node log level

nsxmgr> set controller 192.168.110.31 java-domain logging-level
  OFF
  FATAL
  ERROR
  WARN
  INFO
  DEBUG
  TRACE

nsxmgr> set controller 192.168.110.31 native-domain logging-level
  ERROR
  WARN
  INFO
  DEBUG
  TRACE

nsxmgr> set host host-28
  netcpa  Set host node log level by module
  vdl2    Set host node log level by module
  vdr     Set host node log level by module

nsxmgr> set host host-28 netcpa logging-level
  FATAL
  ERROR
  WARN
  INFO
  DEBUG

nsxmgr> set host host-28 vdl2 logging-level
  ERROR
  INFO
  DEBUG
  TRACE

nsxmgr> set host host-28 vdr logging-level
  OFF
  ERROR
  INFO

More details:-  http://bit.ly/2qcj9na