Guest

Preview Tool

Cisco Bug: CSCvu92384 - post_install on cluster expansion failed while checking vMotion VlanID with existing vMotion VlanID

Last Modified

Jul 28, 2020

Products (1)

  • Cisco HyperFlex HX-Series

Known Affected Releases

4.0(2b)

Description (partial)

Symptom:
root@HyperFlex-Installer-4.0.2b:~# post_install
 
Select post_install workflow-
 
1. New/Existing Cluster
2. Expanded Cluster (for non-edge clusters)
3. Generate Certificate
 
Note:  Workflow No.3 is mandatory to have unique SSL certificate in the cluster.
        By Generating this certificate, it will replace your current certificate.
        If you're performing cluster expansion, then this option is not required.
 
Selection: 2
Expanded Cluster workflow selected
 
Logging in to controller xx.xx.xx.xx
HX CVM admin password:
Getting ESX hosts from HX cluster...
WARNING:root:Unable to fetch the deploymentMode from stcli. Will retry with fallback mechanism.
vCenter URL: xx.xx.xx.xx
Enter vCenter username (user@domain): administrator@vsphre.local
vCenter Password:
Found datacenter xxx
Found cluster xx-xx
 
post_install to be run for the following hosts:
hx4
 
 
Enter ESX root password:
 
Enter vSphere license key?  (y/n) n
 
Enable HA/DRS on cluster? (y/n) n
 
Disable SSH warning? (y/n) y
 
Add vmotion interfaces? (y/n) y
 
Existing cluster configuration for reference
--------------------------------------------
Netmask                Vlan-Id         IP-Address
--------------------------------------------
255.255.255.0          vmotion         xx.xx.xx.231
255.255.255.0          vmotion         xx.xx.xx.232
255.255.255.0          vmotion         xx.xx.xx.233
--------------------------------------------
 
 
Enter Expanded node configuration-
Netmask for vMotion: 255.255.255.0
VLAN ID: (0-4096) 3093
 
Expanded node configuration should match with existing cluster configuration. Kindly check the above reference information and retry.
 
Netmask for vMotion: 255.255.255.0
VLAN ID: (0-4096) 3093
 
Expanded node configuration should match with existing cluster configuration. Kindly check the above reference information and retry.

Conditions:
Existing cluster configuration for reference
--------------------------------------------
Netmask                Vlan-Id         IP-Address
--------------------------------------------
255.255.255.0          vmotion         xx.xx.xx.231
255.255.255.0          vmotion         xx.xx.xx.232
255.255.255.0          vmotion         xx.xx.xx.233
--------------------------------------------

The Vlan-Id for existing configuration is incorrect, instead of "vmotion" it should return 3093. Checked installer logs and it confirms the existing configuration has vMotion VLAN in 3093.
    "vMotion" : 3093,
    "vmNetwork" : [ {
      "name" : "vm-network-450-epic-450",
      "pgType" : "VM",
      "vlanid" : 450
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.