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

Sunday, December 11, 2016

Why App Volumes

  • Dynamically deliver application in Real-Time.
  • Centrally Manage Application Lifecycle.
  • Reduce Infrastructure and Management Costs.
  • Persistence across Non-persistence Environments.
https://www.youtube.com/watch?v=SZ7OlCw7yMI
https://www.youtube.com/watch?v=IWxIrC6qzOI

App Volumes Components:- 
  • App Volumes Manager
  • App Volumes Agent
  • Provisioning VM
  • AppStack
  • Writebale Volume
https://www.youtube.com/watch?v=yL7Zx2IAEes

Sunday, November 20, 2016

VXLAN Overview

As its name indicates, VXLAN is designed to provide the same Ethernet Layer 2 network services as VLAN does today, but with greater extensibility and flexibility. Compared to VLAN, VXLAN offers the following benefits:

   Flexible placement of multitenant segments throughout the data center: It provides a solution to extend Layer 2 segments over the underlying shared network infrastructure so that tenant workload can be placed across physical pods in the data center.
   Higher scalability to address more Layer 2 segments: VLANs use a 12-bit VLAN ID to address Layer 2 segments, which results in limiting scalability of only 4094 VLANs. VXLAN uses a 24-bit segment ID known as the VXLAN network identifier (VNID), which enables up to 16 million VXLAN segments to coexist in the same administrative domain.
   Better utilization of available network paths in the underlying infrastructure: VLAN uses the Spanning Tree Protocol for loop prevention, which ends up not using half of the network links in a network by blocking redundant paths. In contrast, VXLAN packets are transferred through the underlying network based on its Layer 3 header and can take complete advantage of Layer 3 routing, equal-cost multipath (ECMP) routing, and link aggregation protocols to use all available paths.


Wednesday, June 8, 2016