0

New Release: VMware PowerCLI 6.5.4

New Release: VMware PowerCLI 6.5.4

New Release: VMware PowerCLI 6.5.4

It feels just like yesterday that we released PowerCLI 6.5.3. Shockingly, it was less than a month ago when we released the brand-new module to help manage and automate your NSX-T environments. Yet, we’re back with another brand-new module to manage VMware Cloud on AWS environments as well as a bunch of new and updated […] The post New Release: VMware PowerCLI 6.5.4 appeared first on VMware PowerCLI Blog .


VMware Social Media Advocacy

0

Getting Started with vCloud Director 9.0 API –…

Getting Started with vCloud Director 9.0 API – Part 1

Getting Started with vCloud Director 9.0 API –…

Recently, VMware released vCloud Director 9.0 for Service Providers. I refer you to this vCloud Director 9.0 What’s New White Paper, this explains all the goodness packed into this latest release. As the title suggests – in this post I’m going to cover the vCloud Director 9.0 for Service Providers vCloud API. There are a…


VMware Social Media Advocacy

0

Installing NSX Manager GUEST INTROSPECTION NSX Data Security

Guest introspection is a service that is deployed from NSX Manager to offload security functions. Guest Introspection installs a new vib and a service virtual machine on each host in the cluster. Guest Introspection is required for NSX Data Security, Activity Monitoring, and several third-party security solutions.

System Requirements for NSX

To install Guest Introspection First need to login into the vSphere web client and browse to Networking & Security.
on the left hand side click on Installation. Click the green plus symbol to add a new service deployment.

After this select Guest introspection

 

Select Storage and Network

Create IP Pool for the VM which NSX install for AV purpose.

 

 

Now select the IP Pool and click next

After that it will appear here in last tab

If you closely monitor vCenter task then it will start installing VM

In NSX manager you can see status.

Now your Guest Introspection is ready.

 

You can check this in vCenter under Newly created resource pool > ESX Agent.
This resource pool is auto created by NSX manager for these VM’s only.

 

If this VM giving you error or warning like Failed then just click on Resolve and it will delete the VM and create new VM.

0

VPN Configuration to VMware Cloud on AWS using…

VPN Configuration to VMware Cloud on AWS using pfSense

VPN Configuration to VMware Cloud on AWS using…

Provisioning a new SDDC on VMware Cloud on AWS (VMC) is not an operation that I perform on a regular basis. Usually, one of the first tasks after a new SDDC deployment is setting up a VPN connection between your on-premises datacenter and your VMC environment. Given this is not a frequent activity, I always forget the […]


VMware Social Media Advocacy

0

Configuring IPsec VPN within VMware NSX Edge

This article shows you how to create an IPsec VPN between a NSX Edge Gateway with a vCloud Director/NSX Manager and a remote Client site.

First you need basic details from client so that you can configure IPSec VPN from your end.Like you need Phase 1 and Phase 2 Details. (This document related to NSX Edge 6.3.2)

 

Image Credit VMware

Note: NSX Edge supports Main Mode for Phase 1 and Quick Mode for Phase 2.

Phase 1 Parameters

Phase 1 sets up mutual authentication of the peers, negotiates cryptographic parameters, and creates session keys. The Phase 1 parameters used by NSX Edge are:

  • Main mode
  • TripleDES / AES [Configurable]
  • SHA-1
  • MODP group 2 (1024 bits)
  • pre-shared secret [Configurable]
  • SA lifetime of 28800 seconds (eight hours) with no kbytes rekeying
  • ISAKMP aggressive mode disabled

In 6.3.2 you Can see basic details or you can say this is mixed mode like Phase 1 and Phase 2 they don’t have different tabs or options.

 

Here are details which you have to fill while configuring IPSec VPN for client.

Note: If you are doing this from HTML5 Console then in “Peer Subnets” You have to provide IP range from Increasing to Decreasing order like (192.168.11.0/24 and after that 192.168.10.0/24).

 

I was trying to update this tab from vCloud Director Web and i was not able to do so i changed this from vCenter > NSX manager > Edge settings.

Client side settings must match with your Edge settings.

If your Client have old router (Cisco) then you have to ask them to do settings with supported parameter and these parameters are:

1. SHA1
2. Diffie-Hellman Group – DH5 or DH2 (Old router can only support this IOS 12.4)
3. Encryption Algorithm – AES256

NSX Edge to Cisco

  • proposal: encrypt 3des-cbc, sha, psk, group5(group2)

After setup you can export Settings from Edge and share it with Client Network Team so that they can run it in their router and do the same setup which you have done in your Edge gateway.

Go to vCenter > NSX Manager > NSX Edges > Search your Edge and double click > Manage (R.H.S) > VPN Tab > IPSec VPN and from here you can download script for Cisco router.

 

You can copy and send it to client IT team.

Note: It will copy Shared key also so before sending to Client IT team remove that.

After this check the Tunnel status.

Go to vCenter > NSX Manager > NSX Edges > Search your Edge and double click > Manage (R.H.S) > VPN Tab > IPSec VPN

 

I was getting below Error so need to check your DH2 or DH14 settings.

  • If the Cisco device does not accept any of the parameters the NSX Edge sent in step one, the Cisco device sends the message with flag NO_PROPOSAL_CHOSEN and terminates the negotiation.
0

Upgrade VMware vCloud Director for Service Providers v8.20 to v9.0.0

Now before starting this activity need to take backup for few VMs like. You can check my last blog regarding same.

Here is the link https://www.dtechinspiration.com/upgrade-vmware-vcloud-director-for-service-providers-v8-1-0-to-v8-20/

Now starting activity

 

Steps to upgrade

We are running only one vCD cell server. Here is the process:

  1. Restrict access to vCD and display a maintenance message for the duration of the upgrade.

 

0

Upgrade VMware vCloud Director for Service Providers v8.1.0 to v8.20

Today we are upgrading our vCloud Director from 8.10 to 8.20.

Now before starting this activity need to take backup for few VMs like.

  • Take Snapshot of vCloud Director VM
  • Take Snapshot of vCenter VM
  • Take Snapshot of NSX VM
  • Do the FTP backup for NSX VM
  • Take vCloud Database backup
  • Take vCenter Database backup
  • Login into vmware website and download the upgrade bin file from there
  • Copy it on vCloud Director Server using winscp software to copy this in tmp folder

 

Steps to upgrade

We are running only one vCD cell server. Here is the process:

  1. Restrict access to vCD and display a maintenance message for the duration of the upgrade.

2017-09-27 15_34_30-mRemoteNG - confCons.xml - vCenter-Cloud-D2017-09-27 15_34_48-Service Unavailable

 

2. Quiesce vCD cell servers from the Cell Management Tool.

  • cd /opt/vmware/vcloud-director/bin/
    ./cell-management-tool -u username -p password cell –status
    ./cell-management-tool -u username -p password cell –quiesce true
    ./cell-management-tool -u username -p password cell –maintenance true

3. Upgrade the vCD software on all cell servers (If you have). Do not restart vCD services until the database is upgraded.

Log in to the target server as root.

  • Go to cd /tmp folder make this vCloud file as executable
  • chmod u+x vmware-vCloud-director-distribution-8.20.0-5515092.bin

After that run this command ./vmware-vCloud-director-distribution-8.20.0-5515092.bin

If the installer detects a version of vCloud Director installed on this server that is equal to or later than
the version in the installation file it displays an error message and exits. Otherwise, it prompts you to
confirm that you are ready to proceed to upgrade this server.

 

2017-09-27 15_36_17-mRemoteNG - confCons.xml - vCenter-Cloud-D2017-09-27 15_36_23-mRemoteNG - confCons.xml - vCenter-Cloud-D2017-09-27 15_36_41-mRemoteNG - confCons.xml - vCenter-Cloud-D2017-09-27 15_36_53-mRemoteNG - confCons.xml - vCenter-Cloud-D

 

Upgrade the vCD database.

Note: Make Sure you have Database backup before upgrading Schema for database.

image

 

Go to this location: cd /opt/vmware/vCloud-director/bin/

type ./upgrade

2017-09-27 15_39_54-mRemoteNG - confCons.xml - vCenter-Cloud-D2017-09-27 15_40_24-mRemoteNG - confCons.xml - vCenter-Cloud-D

 

After that it will ask you to restart vCD server press Y.

2017-09-27 15_41_09-mRemoteNG - confCons.xml - vCenter-Cloud-D2017-09-27 15_41_43-mRemoteNG - confCons.xml - vCenter-Cloud-D

 

Restart the vCD services on the cell servers.

2017-09-27 15_42_53-mRemoteNG - confCons.xml - vCenter-Cloud-D2017-09-27 15_41_43-mRemoteNG - confCons.xml - vCenter-Cloud-D

 

If you had the vCD web console open during the upgrade, log out to clear the browser cache.

2017-09-27 15_47_00-VMware vCloud Director

Errors during and After upgrade:

 

1. First thing after upgrade vCloud Director, vCD VM not getting IP address

To resolve this issue you have to make nic UP and Down for Centos or Linux

  • ifup eth0 and ifdown eth0
  • Also known error (Due Gratuitous ARP issue)

2. After that vCenter not connecting in vCloud Director.

We discovered the connection issue was due to vCenter using TLSv1 which we needed to enable on the vCD cell by running

  • /opt/vmware/vcloud-director/bin]# ./cell-management-tool ssl-protocols -d SSLv3,SSLv2Hello

and then restarting the cell services.

To perform this activity you have to follow below steps.

  • A. Login to the vCloud Director cell via SSH as root.
  • B. Change directory to where the cell-management-tool is located.
    ># cd /opt/vmware/vcloud-director/bin
  • C. Run the tool to verify the job count and active state (true):
    ># ./cell-management-tool -u administrator cell -t
    Please enter the administrator password:
    Job count = 2
    Is Active = true
  • D. Use the quiesce feature to ensure the cell takes no new jobs
    ># ./cell-management-tool -u administrator cell -q true
    Please enter the administrator password:
  • E. Run the tool to verify the job count and active state (false):
    ># ./cell-management-tool -u administrator cell -t
    Please enter the administrator password:
    Job count = 0
    Is Active = false
  • F. Shut down the cell once the Job count = 0 and Is Active = false:
    ># ./cell-management-tool -u administrator cell -s
    Please enter the administrator password:
  • G. Stop the vCloud Director services:
    ># service vmware-vcd stop
    Stopping vmware-vcd-watchdog:        [  OK  ]
    Stopping vmware-vcd-cell:                   [  OK  ]

3. Here you need to access your vCloud Director SQL database

and run these commands. (Run these command in one go)

  • update jobs set status = 3 where status = 1;
    update last_jobs set status = 3 where status = 1;
    delete from busy_object;
    delete from QRTZ_SCHEDULER_STATE;
    delete from QRTZ_FIRED_TRIGGERS;
    delete from QRTZ_PAUSED_TRIGGER_GRPS;
    delete from QRTZ_CALENDARS;
    delete from QRTZ_TRIGGER_LISTENERS;
    delete from QRTZ_BLOB_TRIGGERS;
    delete from QRTZ_CRON_TRIGGERS;
    delete from QRTZ_SIMPLE_TRIGGERS;
    delete from QRTZ_TRIGGERS;
    delete from QRTZ_JOB_LISTENERS;
    delete from QRTZ_JOB_DETAILS;
    delete from compute_resource_inv;
    delete from custom_field_manager_inv;
    delete from ccr_drs_vm_host_rule_inv;
    delete from cluster_compute_resource_inv;
    delete from datacenter_inv;
    delete from datacenter_network_inv;
    delete from datastore_inv;
    delete from dv_portgroup_inv;
    delete from dv_switch_inv;
    delete from folder_inv;
    delete from managed_server_inv;
    delete from managed_server_datastore_inv;
    delete from managed_server_network_inv;
    delete from network_inv;
    delete from resource_pool_inv;
    delete from storage_pod_inv;
    delete from task_inv;
    delete from task_activity_queue;
    delete from activity;
    delete from activity_parameters;
    delete from failed_cells;
    delete from lock_handle;
    delete from vm_inv;
    delete from property_map;

4. Start the vCloud Director services:
># service vmware-vcd start
Starting vmware-vcd-watchdog: [ OK ]
Starting vmware-vcd-cell: [ OK ]