Configuring vNET High Availability (HA)

---

vNET HA provides high availability for switch access through a vNET manager. The vNET manager is a zone, typically with one IP interface, which allows a vNET administrator to log into and administer a vNET using the CLI or a REST API.

Netvisor ONE provides HA functionality by allowing you to create multiple vNET managers. Netvisor ONE enables access to the vNET managers when you add either standard or VRRP VIP interfaces to the vNET managers.

Without vNET HA, vNET administrators have only a single point of access where the vNET manager zone runs on a particular switch. If that switch fails, the administrator cannot log into the fabric and administer the vNET.

This feature provides the following:

 

• Create or delete a vNET manager zone.
• The vnet-manager-interface command  accepts VRRP interfaces. This allows you to create VRRP interfaces on vNET manager zones
• The vnet-create command  provides an option to not create a vNET manager zone when creating a vNET.
• Copy and paste SSH host keys used on different vNET managers. This is needed when using a VRRP VIP to access the vNET managers to avoid SSH host key violations if the VIP fails over to the standby vNET manager. Install these keys on the client machine used to connect to the vNET managers.

Creating a vNET Manager Zone

To create additional vNET manager zones, use the vnet-manager-create command.

CLI (network-admin@Leaf1) > vnet-manager-create name name-string vnet vnet-name [disable|enable][location fabric-node name][storage-pool storage-pool name]

 

 

Deleting a vNET Manager Zone

 

To delete a vNET manager zone, use the vnet-manager-delete command.

 

CLI (network-admin@Leaf1) > vnet-manager-delete name name-string

 

Specify the name of service configuration.

 

Copying and Pasting SSH Keys

 

To output SSH host keys to copy and paste to ~/.ssh/known_hosts file of the client host, use the vnet-manager-ssh-host-key-show command. 

This allows you to SSH to any vNET manager zone and avoid issues with invalid key hosts.

 

CLI (network-admin@Leaf1) > vnet-manager-ssh-host-key-show [vnet vnet name]

 

 

vNET Manager Command Options

 

This feature uses a new option [no-]create-vnet-mgr which controls whether to create a vNET manager. 

The default behavior is creating a vNET manager as this is the current behavior of creating a vNET manager as part of vnet-create.

CLI (network-admin@Leaf1) > no-create-vnet-mgr

 

 

VRRP Interfaces Option

 

This feature now accepts options for VRRP interfaces. This allows you to create VRRP interfaces on vNET manager zones.

CLI (network-admin@Leaf1) > vnet-manager-interface-add vnet-manager-name name-string [vrrp-id 0,,255][vrrp-primary vrrp-primary-string][vrrp-priority 0..254][vrrp-adv-int 300..40950]