Failed to deploy edge appliance vse-XXXX-0. The name ‘vse-XXXX-0’ already exists”

Posted on 12-07-2017 by Manish Jha

This post is very similar to issue described in my last post. The only difference in last issue and this was I was not able to redeploy edge gateway to get rid of stubborn Org Networks whereas in previous case Edge redeploy fixed the issue quite comfortably.

Let me start with a little bit background of how was this issue discovered and what challenges I faced. I was working investigating a failed deprovision issue when this issue was discovered. Deprovision tasks in our environment are fully automated and we have some portal where these tasks arrives and there is a Resume button which when clicked, kicks the deprovision process.

When the Resume button is clicked that portal initiates API calls to vCD and start deleting stuffs. It starts with deleting vApps, vApp Templates and then proceed to Org Network deletion and then the edge gateway and at last deletes the Org vDC and Org.… Read More

VIX_E_PROGRAM_NOT_STARTED was returned by VIX API

Posted on 11-07-2017 by Manish Jha

Today while working on one production issue, I came across one incident where I was unable to delete one of the Org Network in vCloud Director.

I observed following errors in vCD UI for the Org network deletion failure:

On checking vcloud-container.debug.log I observed similar log entries as seen in vCD UI

This was entirely new error for me so I started googling this around and unfortunately did not found helpful article.

So I started my troubleshooting from edge level. I Found that the edge gateway in vCloud Director was complaining about edge backing VM’s was not reachable.

At vCenter level I found both the edge backing VM’s were intact and was running. I tried performing a force sync on edge gateway from vCenter Web-Client but the operation failed.

At this point I could have sneaked into vsm.log (or show manager log follow) on NSX manager to see what went wrong, but I decided not to waste time into reading logs and went ahead for Edge Gateway redeploy.… Read More

PyNSXv-Powerful tool for NSX Automation

Posted on 05-07-2017 by Manish Jha

Like last post of NSX series, this post is also focused on exploring a new tool which helps automatic NSX stuffs in your infrastructure. I first came across this tool when I was watching a VMworld 2016 Session titled NET7514 – PowerNSX and PyNSXv, but never got chance to play around this tool.

Now since I am exploring NSX automation these days, I decided to deploy the tool, in lab and use it.

This post will be focused on just installation/configuration part and some examples on how to use this tool.

So what is PyNSXv?

PyNSXv is a high python based library that exposes ready to use work-flows and a CLI tool that can be used to control and automate NSXv in your infrastructure.

It an opensource tool and is not supported by VMware and before using this in production, it is recommended to test it thoroughly in lab deployments. … Read More

Exploring PowerNSX in Lab

Posted on 29-06-2017 by Manish Jha

These days I am busy exploring NSX Rest API in my lab and during the process I came to know about a cool tool named PowerNSX and decided to dedicate a blog on this to give respect to creator of this tool.

What is PowerNSX

PowerNSX is a PowerShell module that abstracts the NSX API to a set of easily used PowerShell functions. PowerNSX enables NSX administrators to drive their infrastructure programmatically.

PowerNSX add additional functionality to extend the capabilities of NSX along with exposing the existing Update, Remove and Get operations for all key NSX functions beyond the native UI or API.

PowerNSX have been developed by Nick Bradford. PowerNSX is available for download on GitHub and can be downloaded as the branch or zipfile.

Note: VMware does not support this module, and PowerNSX comes with no warranties express or implied. It is advisable to test this in Lab before using in a production environment.… Read More

Retrieving NSX Manager System Info Using Rest API

Posted on 27-06-2017 by Manish Jha

In this post we will explore how NSX manager system info can be retrieved via Rest API. NSX manager appliance home page is itself very descriptive and provides all system info.

In this post we will learn how the same system info can be explored via API calls. Let’s get started.

Query NSX Manager Information

Below API query will provide you info like what is the major and minor version of NSX appliance you are running along with patch number and build number

# Fetch Global Info
# METHOD: GET
# API CALL: https://NSX-MGR-IP/api/1.0/appliance-management/global/info

# Fetch Global Info

# METHOD: GET

# API CALL: https://NSX-MGR-IP/api/1.0/appliance-management/global/info

Example: curl -k -u “vcadmin@corp.local” -X GET https://nsxmgr-01a.corp.local/api/1.0/appliance-management/global/info | tidy -xml -indent -quiet

<?xml version="1.0" encoding="utf-8"?>
<globalInfo>
  <currentLoggedInUser>admin</currentLoggedInUser>
  <versionInfo>
    <majorVersion>6</majorVersion>
    <minorVersion>3</minorVersion>
    <patchVersion>5</patchVersion>
    <buildNumber>7119875</buildNumber>
  </versionInfo>
</globalInfo>

<?xml version="1.0" encoding="utf-8"?>

Managing NSX Manager Network Settings via Rest API

Posted on 25-06-2017 by Manish Jha

In this post we will learn how can we configure some of the network settings like DNS/Syslog and NTP configurations in NSX manager via Rest API.

We can do all this from NSX manager GUI also but if you are thinking about automating NSX manager deployment, then these Rest API knowledge can be pretty handy for configuring the appliance post its deployment.

Lets get started.

Query Network Settings

Below API query will give you an overview of NSX Manager IP settings, Hostname, DNS settings and domain name

# curl -k -u “admin:adminpwd” -X GET https://nsxmgr.alex.local/api/1.0/appliance-management/system/network/ | xmllint –format –

<?xml version="1.0" encoding="UTF-8"?>
<network>
 <hostName>nsxmgr</hostName>
 <domainName>alex.local</domainName>
 <networkIPv4AddressDto>
 <ipv4Address>192.168.109.6</ipv4Address>
 <ipv4NetMask>255.255.255.0</ipv4NetMask>
 <ipv4Gateway>192.168.109.1</ipv4Gateway>
 </networkIPv4AddressDto>
 <dns>
 <ipv4Address>192.168.109.2</ipv4Address>
 <domainList>alex.local</domainList>
 </dns>
</network>

<?xml version="1.0" encoding="UTF-8"?>

<hostName>nsxmgr</hostName>

<domainName>alex.

NSX Certificate Management Using Rest API

Posted on 22-06-2017 by Manish Jha

In this post We will learn how to view generate self-signed certificate for NSX and replace the certificates after getting them signed from CA. We will be doing this via Rest API.

I wrote a post in past on how to replace SSL certs for NSX from GUI. In this post I am trying to achieve the same via Rest API

Following are the API queries which you need to execute in order to generate and replace certs.

Generate CSR Certificate

# curl -k -u “admin:passwd” -d @csr.xml -X PUT https://nsxmgr.alex.local/api/1.0/appliance-management/certificatemanager/csr/nsx

<?xml version="1.0" encoding="UTF-8"?>
<csr>
 <algorithm>RSA</algorithm>
 <keySize>4096</keySize>
 <subjectDto>
 <commonName>nsxmgr.alex.local</commonName>
 <organizationUnit>Cloud</organizationUnit>
 <organizationName>Alex.Co</organizationName>
 <localityName>Bangalore</localityName>
 <stateName>Karnataka</stateName>
 <countryCode>IN</countryCode>
 </subjectDto>
</csr>

<?xml version="1.0" encoding="UTF-8"?>

<csr>

<commonName>nsxmgr.

Enable Disable HA on Edge GW via NSX Rest API

Posted on 22-06-2017 by Manish Jha

In this post I will be demonstrating how to enable and disable high availability on NSX edge gateway using Rest API.

If you are new to NSX and do not know what edge gateway high availability means then I would recommend to read this Blog by Gabe Rosas.

We can enable disable high availability on edge gateway from vSphere Web Client by navigating to Home > Networking & Security > NSX Edges > Selecting Edge > Manage > HA Configuration

Enabling HA on edge gateway will create a new vse vm in vCenter and both VM start exchanging heartbeat and exchanging other configuration etc.

Now we will see how to achieve this via NSX Rest API.

Step 1: Query HA Status

# curl -k -u “admin:passwd” -X GET https://nsxmgr.alex.local/api/4.0/edges/edge-2/highavailability/config | xmllint –format –

<?xml version="1.0" encoding="UTF-8"?>
<highAvailability>
 <version>3</version>
 <enabled>false</enabled>
 <declareDeadTime>15</declareDeadTime>
 <logging>
 <enable>false</enable>
 <logLevel>info</logLevel>
 </logging>
 <security>
 <enabled>false</enabled>
 </security>
</highAvailability>

Redeploy NSX Edge Gateway Using Rest API

Posted on 21-06-2017 by Manish Jha

In this post I will demonstrate how to redeploy edge gateway in vCloud Director using Rest API

Disclaimer: This is not any fancy post and I am going to perform very simple task here. Most of you may be already aware of this. This post is for those who are new to API and also a reference post for me for future.

Lets get started.

We have to follow below steps for redeploying an edge gateway using API calls

Step 1: Generate Auth Token

# curl -sik -H “Accept:application/*+xml;version=5.6” -u “admin@system” -X POST https://vcd-b.alex.local/api/sessions | grep auth
Enter host password for user ‘admin@system’:

x-vcloud-authorization: 3fc8a5425f804c9d94eeff04e0272ed7

Step 2: Get Org UUID

# curl -sik -H “Accept:application/*+xml;version=5.6” -H “x-vcloud-authorization:3fc8a5425f804c9d94eeff04e0272ed7” -X GET https://vcd-a.alex.local/api/org/

<Org href="https://vcd-a.alex.local/api/org/58d92de4-4aa5-4a14-9b39-28e1de5e9809" name="Production" type="application/vnd.vmware.vcloud.org+xml"/>

1	<Org href="https://vcd-a.alex.local/api/org/58d92de4-4aa5-4a14-9b39-28e1de5e9809" name="Production" type="application/vnd.vmware.vcloud.org+xml"/>

Step 3: Get vDC UUID

# curl -sik -H “Accept:application/*+xml;version=5.6” -H “x-vcloud-authorization:3fc8a5425f804c9d94eeff04e0272ed7” -X GET https://vcd-a.alex.local/api/org/58d92de4-4aa5-4a14-9b39-28e1de5e9809… Read More

Troubleshooting Failed Org Network Creation in vCloud Director

Posted on 08-04-2017 by Manish Jha

Today while working in my lab, I observed that while creating a new VDC in vCD was failing because org network failed to create.

On navigating to Org VDC list and clicking on error, it read the error load and clear that org vdc network can’t be created.

On navigating to Org VDC Networks section and clicking on error, I was able to identify what has caused the network creation failure.

The error stack was reading as below:

[ 114db22d-fc14-4c87-9030-36d2316aff8b ] Cannot deploy organization VDC network (f1514426-647e-4a03-a5a9-fafa4d73bb58)
com.vmware.vcloud.api.presentation.service.InternalServerErrorException: Cannot create network "dvs.VCDVSRouted-NW-9ab02973-9ded-4c4b-8826-4a52bdf2d6cf" from VXLAN network pool "urn:uuid:5c9de104-0f40-4cec-898f-985ee1fce1d6". Make sure vShield Manager infrastructure is properly configured and there are segment IDs available.

- com.vmware.vcloud.api.presentation.service.InternalServerErrorException: Cannot create network "dvs.VCDVSRouted-NW-9ab02973-9ded-4c4b-8826-4a52bdf2d6cf" from VXLAN network pool "urn:uuid:5c9de104-0f40-4cec-898f-985ee1fce1d6". Make sure vShield Manager infrastructure is properly configured and there are segment IDs available.

- Cannot create network "dvs.VCDVSRouted-NW-9ab02973-9ded-4c4b-8826-4a52bdf2d6cf" from VXLAN network pool "urn:uuid:5c9de104-0f40-4cec-898f-985ee1fce1d6". Make sure vShield Manager infrastructure is properly configured and there are segment IDs available.

Spread the Love

Spread the Love

Spread the Love

Spread the Love

Spread the Love

Spread the Love

Spread the Love

Spread the Love

Spread the Love

Spread the Love