Hidden VPLEX Script – VPlexadmin

Last week during the VPLEX Design and Deploy class I spent A LOT of time using the vplexcli tool and getting to know all of the contexts (post coming on vplexcli contexts).  A question came up during the course of how you can convert a VPLEX local cluster into a VPLEX Metro cluster WITHOUT having to do a re-install. The short answer? VPlexadmin.

Within vplexcli there is a command called script.  Script allows you to import and unimport scripts into vplexcli.

Using the script command we’ll import VPlexadmin into vplexcli (VPlexadmin is case sensitive)

Now that we’ve imported it you will now see a need Global command in vplexcli called VPlexadmin

 

 

Now that we can see this new command in vplexcli, lets see what we can do with it.  By typing VPlexadmin and pressing enter or VPlexadmin -h will produce the same results

 

 

There are a lot of commands part of VPlexadmin and to be honest, I don’t know what all of them do.  I will briefly go over a few of them.

VPlexadmin add-remote-cluster-routes

As you can see from the description, this command is used to add a route to a remote management server.  In order to run VPLEX Metro, management servers from both clusters need to be connected to each other through a VPN connection.  This is one of the steps you will need to perform when converting a VPLEX Local configuration to a VPLEX Metro configuration.

Once you configure the remote route(s) to the management server you then would need to configure the certificates and configure the VPN.  Use the following command to automate that process

VPlexadmin configure-certificates-and-vpn

This command may also be useful should you get an error for the management servers when running a NDU health-check.

As you look through the list of the different commands associated with VPlexadmin you see there are some set commands that will allow you to change enclosure IDs and the WWN seed of an engine.  You shouldn’t have any reason to do this, but in case you are going to use the VPlexadmin set-wwn-seed –engine <engine>  be aware that this will in-turn change the WWNs for all of your ports (FE, BE and WAN).  Doing this will cause you to lose connectivity to all ports (fibre channel ports) unless you update your zone configurations prior to the change with the new WWNs.

I can’t speak to whether using VPlexadmin is supported, so proceed with caution!

 

Comments 1

  1. Need some advise , we will be implementing Vplex metro across 2 sites , we have L2 stretched across sites and IP WAN for both ISL Vplex clusters will be used ( FC not stretched). We would want to use VMSC using distributed volumes and ESXi hosts in a single DRS-HA cluster . What would be recommendations and any advise to get this done.

Leave a Reply to rambosuri Cancel reply

Your email address will not be published. Required fields are marked *

*