Contents
-
Fabric Interconnect
-
Upgrade FI-UCSM From 3.2(3b) to 4.0(1c)
- Prerequisites for Upgrade to Cisco UCS Manager Release 4.0
- Required Order of Steps for Auto Install
- Creating an All Configuration Backup File
- Disabling Smart Call Home
- Verifying the Operability of a Fabric Interconnect
- Verifying the High Availability Status and Roles of a Cluster Configuration
- Configuring the Default Maintenance Policy
- Disabling the Management Interface
- Verifying the Status of an I/O Module
- Verifying the Status of a Server
- Verifying the Ethernet Data Path
- Verifying the Data Path for Fibre Channel End-Host Mode
- Downloading Firmware Images to the Fabric Interconnect from a Remote Location
- Displaying the Firmware Package Download Status
- Displaying All Available Packages on the Fabric Interconnect
- Checking the Available Space on a Fabric Interconnect
- Upgrade the Infrastructure Firmware with Auto Install
- Acknowledging the Reboot of the Primary Fabric Interconnect
- Viewing the Status of the FSM During An Infrastructure Firmware Upgrade
- Confirm that upgrade is complete
- Troubleshooting
-
Upgrade FI-UCSM From 3.2(3b) to 4.0(1c)
Fabric Interconnect
Upgrade FI-UCSM From 3.2(3b) to 4.0(1c)
Cisco strongly recommends that you use Auto Install to upgrade a Cisco UCS domain.
Prerequisites for Upgrade to Cisco UCS Manager Release 4.0
- Scenarios for Firmware Upgrade to Cisco UCS Manager Release 4.0
Upgrading the Infrastructure software bundle (A bundle) directly to Cisco UCS Manager Release 4.0(x) is supported from Release 3.1(1) and later releases. While upgrading from releases earlier than Release 3.1(1), you must upgrade to Release 3.1(x) or 3.2(x) first for A, B, and C bundles, and then upgrade to Release 4.0(x).
- Cisco UCS Manager Release 3.1 and later releases do not support key rings that have modulus size less than 2048 bits.
- Before upgrading to Cisco UCS Manager Release 4.0, ensure that the key ring in use has a modulus size of 2048 bits or more by doing the following:
UCS-A# scope security UCS-A /security # scope keyring keyring-name UCS-A /security/keyring # show detail
Required Order of Steps for Auto Install
If you want to upgrade all components in a Cisco UCS domain to the same package version, you must run the stages of Auto Install in the following order:
- Install Infrastructure Firmware Install Server Firmware
This order enables you to schedule the server firmware upgrades during a different maintenance window than the infrastructure firmware upgrade.
Creating an All Configuration Backup File
This procedure assumes that you do not have an existing backup operation for an All Configuration backup file.
- Step 1 UCS-A# scope system
Enters system mode.
- Step 2 UCS-A /system # create backup URL all-configuration enabled
ftp:// username@hostname / path
scp:// username@hostname / path
sftp:// username@hostname / path
tftp:// hostname : port-num / path- Step 3 UCS-A /system # commit-buffer
Commits the transaction.
Disabling Smart Call Home
BGY-NEW-HX-B /system # scope monitoring
BGY-NEW-HX-B /monitoring # scope callhome
BGY-NEW-HX-B /monitoring/callhome # disable
BGY-NEW-HX-B /monitoring/callhome #
BGY-NEW-HX-B /monitoring/callhome # commit-buffer
BGY-NEW-HX-B /monitoring/callhome # show detail
Callhome:
Admin State: Off
Throttling State: On
Contact Information:
Customer Contact Email:
From Email:
Reply To Email:
Phone Contact e.g., +1-011-408-555-1212:
Street Address:
Contract Id:
Customer Id:
Site Id:
Switch Priority: Debugging
SMTP Server Address:
SMTP Server Port: 25
Current Task:
Verifying the Operability of a Fabric Interconnect
BGY-NEW-HX-B# scope fabric-interconnect a
BGY-NEW-HX-B /fabric-interconnect # show
Fabric Interconnect:
ID OOB IP Addr OOB Gateway OOB Netmask OOB IPv6 Address OOB IPv6 Gateway Prefix Operability
---- --------------- --------------- --------------- ---------------- ---------------- ------ -----------
A 10.254.253.77 10.254.253.254 255.255.255.0 :: :: 64 Operable
BGY-NEW-HX-B /fabric-interconnect # exit
BGY-NEW-HX-B# scope fabric-interconnect b
BGY-NEW-HX-B /fabric-interconnect # show
Fabric Interconnect:
ID OOB IP Addr OOB Gateway OOB Netmask OOB IPv6 Address OOB IPv6 Gateway Prefix Operability
---- --------------- --------------- --------------- ---------------- ---------------- ------ -----------
B 10.254.253.78 10.254.253.254 255.255.255.0 :: :: 64 Operable
Verifying the High Availability Status and Roles of a Cluster Configuration
BGY-NEW-HX-B# show cluster state Cluster Id: 0xaded5a7ccf6611e7-0xb59400defb68c3a1 B: UP, PRIMARY A: UP, SUBORDINATE HA READY
Configuring the Default Maintenance Policy
BGY-NEW-HX-B# scope org /
BGY-NEW-HX-B /org # scope maint-policy default
BGY-NEW-HX-B /org/maint-policy # set reboot-policy user-ack
BGY-NEW-HX-B /org/maint-policy* # commit-buffer
BGY-NEW-HX-B /org/maint-policy # show
Maintenance Policy:
Name Schedule
---------- --------
default
BGY-NEW-HX-B /org/maint-policy # show detail
Maintenance Policy:
Name: default
Schedule:
Description:
Policy Owner: Local
Reboot Policy: User Ack
Config Trigger: None
Soft Shutdown Timer: 150 Secs
BGY-NEW-HX-B /org/maint-policy #
Disabling the Management Interface
BGY-NEW-HX-B# scope monitoring BGY-NEW-HX-B /monitoring # set mgmt-if-mon-policy admin-state enabled BGY-NEW-HX-B /monitoring # commit-buffer BGY-NEW-HX-B /monitoring #
Verifying the Status of an I/O Module
Not have
Verifying the Status of a Server
OK as bellow
BGY-NEW-HX-B# scope server 1
BGY-NEW-HX-B /server # show status
Server Slot Status Availability Overall Status Discovery
------- ------------------------- ------------ --------------------- ---------
1 N/A Available Unassociated Complete
BGY-NEW-HX-B /server # show status detail
Server 1:
Conn Path: A,B
Conn Status: A,B
Managing Instance: B
Availability: Available
Admin State: In Service
Overall Status: Unassociated
Oper Qualifier: N/A
Discovery: Complete
Current Task:
Check Point: Discovered
BGY-NEW-HX-B /server # show adapter status
Server 1:
Overall Status
--------------
N/AFailed discovered as bellow
BGY-NEW-HX-B# scope server 2
BGY-NEW-HX-B /server # show sta
stats status
BGY-NEW-HX-B /server # show status
Server Slot Status Availability Overall Status Discovery
------- ------------------------- ------------ --------------------- ---------
2 N/A Unavailable Discovery In Progress
BGY-NEW-HX-B /server # show status detail
Server 2:
Conn Path: A
Conn Status: A
Managing Instance: A
Availability: Unavailable
Admin State: In Service
Overall Status: Restart
Oper Qualifier: N/A
Discovery: In Progress
Current Task: Preparing to check hardware configuration server sys/rack-unit-2(FSM-STAGE:sam:dme:ComputePhysicalHardreset:PreSanitize)
Check Point: Shallow Checkpoint
Verifying the Ethernet Data Path
BGY-NEW-HX-B# connect nxos b Cisco Nexus Operating System (NX-OS) Software TAC support: http://www.cisco.com/tac Copyright (c) 2002-2016, Cisco Systems, Inc. All rights reserved. The copyrights to certain works contained in this software are owned by other third parties and used and distributed under license. Certain components of this software are licensed under the GNU General Public License (GPL) version 2.0 or the GNU Lesser General Public License (LGPL) Version 2.1. A copy of each such license is available at http://www.opensource.org/licenses/gpl-2.0.php and http://www.opensource.org/licenses/lgpl-2.1.php BGY-NEW-HX-B(nxos)# BGY-NEW-HX-B(nxos)# show interface brief | grep -v down -------------------------------------------------------------------------------- Ethernet VLAN Type Mode Status Reason Speed Port Interface Ch # -------------------------------------------------------------------------------- Eth1/1 1 eth vntag up none 10G(D) -- Eth1/2 1 eth vntag up none 10G(D) -- Eth1/3 1 eth vntag up none 10G(D) -- Eth1/4 1 eth vntag up none 10G(D) -- Eth1/5 1 eth vntag up none 10G(D) -- Eth1/6 1 eth vntag up none 10G(D) -- Eth1/7 1 eth vntag up none 10G(D) -- Eth1/8 1 eth vntag up none 10G(D) -- -------------------------------------------------------------------------------- Port VRF Status IP Address Speed MTU -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- Vethernet VLAN Type Mode Status Reason Speed -------------------------------------------------------------------------------- Veth32769 1 virt trunk up none auto Veth32770 1 virt trunk up none auto Veth32771 1 virt trunk up none auto Veth32772 1 virt trunk up none auto Veth32773 1 virt trunk up none auto Veth32774 1 virt trunk up none auto Veth32775 1 virt trunk up none auto Veth32776 1 virt trunk up none auto ------------------------------------------------------------------------------- Interface Secondary VLAN(Type) Status Reason ------------------------------------------------------------------------------- BGY-NEW-HX-B(nxos)# show interface brief | grep -v down | wc -l 33 BGY-NEW-HX-B(nxos)# show platform fwm info hw-stm HW STM Contents dleft loc - bucket_type:line:bucket_number misc - learn_type:ecc:valid:fcf cdce format - ig:ul:switch_id:subswitch_id:end_node_id:pbp_idx:local_id VLAN MAC Address Port loc misc cdce ------+----------------+--------------+--------+-------+-------------------- 1.4043 380e.4d16.94e7 Eth1/4 1:51:0 0:0:1:0 2.a.bc.0.0.6 (e:0) 1.4044 380e.4d16.bd45 vif56 1:190:0 0:0:1:0 6.a.bc.0.0.8 (e:1) 1.4044 380e.4d16.9505 vif52 1:815:0 0:0:1:0 6.a.bc.0.0.6 (e:1) vsan1 0efc.00ff.fc4d sup-eth1 1:1221:0 0:0:1:1 2.0.0.0.0.3 (e:0) 1.4043 3890.a5bd.3a31 Eth1/6 1:1421:0 0:0:1:0 2.a.bc.0.0.b (e:0) 1.4044 3890.a5bd.3a4f vif55 1:1529:0 0:0:1:0 6.a.bc.0.0.b (e:1) 1.4043 380e.4d16.8f21 Eth1/2 1:1532:0 0:0:1:0 2.a.bc.0.0.7 (e:0) 1.4044 500f.809f.c294 vif51 1:1597:0 0:0:1:0 6.a.bc.0.0.9 (e:1) 1.4043 380e.4d16.bd27 Eth1/3 1:1931:0 0:0:1:0 2.a.bc.0.0.8 (e:0) 1.4043 500f.809f.c036 Eth1/7 1:2624:0 0:0:1:0 2.a.bc.0.0.a (e:0) 1.4044 380e.4d16.8f3f vif69 1:2659:0 0:0:1:0 6.a.bc.0.0.7 (e:1) 1.4043 380e.4d16.9547 Eth1/1 1:3266:0 0:0:1:0 2.a.bc.0.0.5 (e:0) 1.4044 380e.4d16.9565 vif68 1:3268:0 0:0:1:0 6.a.bc.0.0.5 (e:1) 1.4044 500f.809f.c054 vif53 1:3445:0 0:0:1:0 6.a.bc.0.0.a (e:1) 1.4043 500f.809f.be56 Eth1/8 1:3690:0 0:0:1:0 2.a.bc.0.0.c (e:0) 1.4044 500f.809f.be74 vif54 1:3692:0 0:0:1:0 6.a.bc.0.0.c (e:1) 1.4043 500f.809f.c276 Eth1/5 1:3950:0 0:0:1:0 2.a.bc.0.0.9 (e:0) 14.1 0efc.00ff.fc4d sup-eth1 1:3951:0 0:0:1:0 2.a.bc.0.0.3 (e:0) in-0 00de.fb68.c400 convert-err 3:0:1016 0:0:1:0 2.a.bc.0.0.0 (e:0) 14.407 0efc.0068.c400 convert-err 3:0:1017 0:0:1:0 2.a.bc.0.0.0 (e:0) in-0 ffff.ffff.ffff midx 8189 3:0:1018 0:0:1:0 1.0.0.0.1f.fd (e:0) in-0 0100.5e00.0000 midx 8189 3:0:1019 0:0:1:0 1.0.0.0.1f.fd (e:0) in-0 0100.5e00.0000 midx 8191 3:0:1020 0:0:1:0 1.0.0.0.1f.ff (e:0) in-0 0100.0000.0000 midx 8190 3:0:1021 0:0:1:0 1.0.0.0.1f.fe (e:0) DA hit 36569 miss 50651 SA ig_miss 27085 eg_miss 371035 Total addresses: 24 (unreserved entries -104) BGY-NEW-HX-B(nxos)# show platform fwm info hw-stm | grep '1.' | wc -l 26
Verifying the Data Path for Fibre Channel End-Host Mode
BGY-NEW-HX-B(nxos)# show npv flogi-table No flogi sessions found.
Downloading Firmware Images to the Fabric Interconnect from a Remote Location
UCS-A# scope firmware UCS-A /firmware # download image scp://user1@192.168.10.10/images/ucs-k9-bundle.1.0.0.988.bin OR download image usbB:/username/ucs-k9-bundle-b-series.3.0.1a.B.bin UCS-A /firmware # show download-task
Displaying the Firmware Package Download Status
BGY-NEW-HX-B# scope firmware
BGY-NEW-HX-B /firmware # show download-task
Download task:
File Name Protocol Server Userid State
--------- -------- ------------------------------------- --------------- -----
ucs-catalog.3.2.2b.T.bin
Local local Downloaded
ucs-k9-bundle-b-series.3.2.2b.B.bin
Local local Downloaded
ucs-k9-bundle-c-series.3.2.2b.C.bin
Local local Downloaded
ucs-k9-bundle-infra.3.2.2b.A.bin
Local local Downloaded
BGY-NEW-HX-B /firmware # show image
Displaying All Available Packages on the Fabric Interconnect
BGY-NEW-HX-B /firmware # show package
Name Version
--------------------------------------------- -------
ucs-catalog.3.2.2b.T.bin 3.2(2b)T
ucs-k9-bundle-b-series.3.1.2e.B.bin 3.1(2e)B
ucs-k9-bundle-b-series.3.2.2b.B.bin 3.2(2b)B
ucs-k9-bundle-c-series.3.1.2e.C.bin 3.1(2e)C
ucs-k9-bundle-c-series.3.2.2b.C.bin 3.2(2b)C
ucs-k9-bundle-infra.3.1.2e.A.bin 3.1(2e)A
ucs-k9-bundle-infra.3.2.2b.A.bin 3.2(2b)A
BGY-NEW-HX-B /firmware # show package ucs-k9-bundle-c-series.3.2.2b.C.bin expand
Package ucs-k9-bundle-c-series.3.2.2b.C.bin:
Images:
ucs-3260.3.0.3e.bin
ucs-adaptor-pcie-ucsc-pcie-x710ta4.800031CA-1.810.8.bin
ucs-c-amd-video-7150x2.015.049.000.016.007518_113-8747CA-102.bin
ucs-c-emulex-pci-lpe31002.11.2.156.27.bin
ucs-c-fusion-io-pfio1000mp.8.9.9.118194.bin
ucs-c-fusion-io-pfio1000mps.8.9.9.118194.bin
ucs-c-fusion-io-pfio1205m.7.1.17.bin
Checking the Available Space on a Fabric Interconnect
BGY-NEW-HX-B /fabric-interconnect # show storage
Storage on local flash drive of fabric interconnect:
Partition Size (MBytes) Used Percentage
---------------- ---------------- ---------------
bootflash 16329 37
opt 3877 2
spare 5744 5
usbdrive Nothing Empty
var_sysmgr 2000 4
var_tmp 600 1
volatile 240 Empty
workspace 3852 1
Upgrade the Infrastructure Firmware with Auto Install
If your Cisco UCS domain does not use an NTP server to set the time, make sure that the clocks on the primary and secondary fabric interconnects are in sync. You can do this by configuring an NTP server in Cisco UCS Manager or by syncing the time manually.
BGY-NEW-HX-A# show clock Thu Nov 23 09:38:34 UTC 2017 BGY-NEW-HX-A# BGY-NEW-HX-B# show clock Thu Nov 23 09:38:32 UTC 2017 BGY-NEW-HX-B#
BGY-NEW-HX-B /firmware # show package Name Version --------------------------------------------- ------- ucs-catalog.3.2.2b.T.bin 3.2(2b)T ucs-k9-bundle-b-series.3.1.2e.B.bin 3.1(2e)B ucs-k9-bundle-b-series.3.2.2b.B.bin 3.2(2b)B ucs-k9-bundle-c-series.3.1.2e.C.bin 3.1(2e)C ucs-k9-bundle-c-series.3.2.2b.C.bin 3.2(2b)C ucs-k9-bundle-infra.3.1.2e.A.bin 3.1(2e)A ucs-k9-bundle-infra.3.2.2b.A.bin 3.2(2b)A BGY-NEW-HX-B /firmware # BGY-NEW-HX-B /firmware # scope firmware BGY-NEW-HX-B /firmware # scope auto-install BGY-NEW-HX-B /firmware/auto-install # install infra infra-vers 3.2(2b)A This operation upgrades firmware on UCS Infrastructure Components (UCS manager, Fabric Interconnects and IOMs). Here is the checklist of things that are recommended before starting Auto-Install (1) Review current critical/major faults (2) Initiate a configuration backup (3) Check if Management Interface Monitoring Policy is enabled (4) Check if there is a pending Fabric Interconnect Reboot activitiy (5) Ensure NTP is configured (6) Check if any hardware (fabric interconnects, io-modules, servers or adapters) is unsupported in the target release Do you want to proceed? (yes/no): Triggering Install-Infra with: Infrastructure Pack Version: 3.2(2b)A
Acknowledging the Reboot of the Primary Fabric Interconnect
Caution
To upgrade with minimal disruption, you must confirm the following:
Ensure that all the IOMs that are attached to the Fabric Interconnect are up before you acknowledge the reboot of the Fabric Interconnect. If all IOMs are not up, all the servers connected to the Fabric Interconnect will immediately be re-discovered and cause a major disruption.
Ensure that both of the Fabric Interconnects and the service profiles are configured for failover.
Verify that the data path has been successfully restored from the secondary Fabric Interconnect before you acknowledge the reboot of the primary Fabric Interconnect. For more information, see Verification that the Data Path is Ready.
After you upgrade the infrastructure firmware, Install Infrastructure Firmware automatically reboots the secondary fabric interconnect in a cluster configuration. However, you must acknowledge the reboot of the primary fabric interconnect. If you do not acknowledge the reboot, Install Infrastructure Firmware waits indefinitely for that acknowledgment rather than completing the upgrade. BGY-NEW-HX-B# show cluster state Cluster Id: 0xaded5a7ccf6611e7-0xb59400defb68c3a1 B: UP, PRIMARY, (Management services: INIT IN PROGRESS) A: UP, SUBORDINATE HA NOT READY Management services: initialization in progress on local Fabric Interconnect
BGY-NEW-HX-A# scope firmware BGY-NEW-HX-A /firmware # scope auto-install BGY-NEW-HX-A /firmware/auto-install # acknowledge primary fabric-interconnect reboot BGY-NEW-HX-A /firmware/auto-install* # commit-buffer BGY-NEW-HX-A /firmware/auto-install # show cluster state Cluster Id: 0xaded5a7ccf6611e7-0xb59400defb68c3a1 A: UP, SUBORDINATE B: UP, PRIMARY HA READY BGY-NEW-HX-A /firmware/auto-install #
Viewing the Status of the FSM During An Infrastructure Firmware Upgrade
BGY-NEW-HX-A# scope firmware
BGY-NEW-HX-A /firmware # scope auto-install
BGY-NEW-HX-A /firmware/auto-install # show fsm status expand
FSM Status:
Affected Object: sys/fw-system/fsm
Current FSM: Deploy
Status: In Progress
Completion Time:
Progress (%): 90
FSM Stage:
Order Stage Name Status Try
------ ---------------------------------------- ------------ ---
1 DeployWaitForDeploy Success 0
2 DeployResolveDistributableNames Skip 0
3 DeployResolveDistributable Skip 0
4 DeployResolveImages Skip 0
5 DeployDownloadImages Skip 0
6 DeployCopyAllImagesToPeer Skip 0
7 DeployInternalBackup Skip 0
8 DeployPollInternalBackup Success 0
9 DeployActivateUCSM Skip 0
10 DeployPollActivateOfUCSM Success 0
11 DeployUpdateIOM Skip 0
12 DeployPollUpdateOfIOM Skip 0
13 DeployActivateIOM Skip 0
14 DeployPollActivateOfIOM Skip 0
15 DeployFabEvacOnRemoteFI Skip 0
16 DeployPollFabEvacOnRemoteFI Skip 0
17 DeployActivateRemoteFI Success 0
18 DeployPollActivateOfRemoteFI In Progress 1
19 DeployFabEvacOffRemoteFI Pending 0
20 DeployPollFabEvacOffRemoteFI Pending 0
21 DeployWaitForUserAck Pending 0
22 DeployPollWaitForUserAck Pending 0
23 DeployFailOverToRemoteFI Pending 0
24 DeployPollFailOverToRemoteFI Pending 0
25 DeployActivateLocalFI Pending 0
26 DeployPollActivateOfLocalFI Pending 0
27 DeployActivateUCSMServicePack Pending 0
28 DeployPollActivateOfUCSMServicePack Pending 020 minutes ago
BGY-NEW-HX-B /firmware/auto-install # show fsm status expand
FSM Status:
Affected Object: sys/fw-system/fsm
Current FSM: Deploy
Status: In Progress
Completion Time:
Progress (%): 90
FSM Stage:
Order Stage Name Status Try
------ ---------------------------------------- ------------ ---
1 DeployWaitForDeploy Success 0
2 DeployResolveDistributableNames Skip 0
3 DeployResolveDistributable Skip 0
4 DeployResolveImages Skip 0
5 DeployDownloadImages Skip 0
6 DeployCopyAllImagesToPeer Skip 0
7 DeployInternalBackup Skip 0
8 DeployPollInternalBackup Success 0
9 DeployActivateUCSM Skip 0
10 DeployPollActivateOfUCSM Success 0
11 DeployUpdateIOM Skip 0
12 DeployPollUpdateOfIOM Skip 0
13 DeployActivateIOM Skip 0
14 DeployPollActivateOfIOM Skip 0
15 DeployFabEvacOnRemoteFI Skip 0
16 DeployPollFabEvacOnRemoteFI Skip 0
17 DeployActivateRemoteFI Success 0
18 DeployPollActivateOfRemoteFI In Progress 4
19 DeployFabEvacOffRemoteFI Pending 0
20 DeployPollFabEvacOffRemoteFI Pending 0
21 DeployWaitForUserAck Pending 0
22 DeployPollWaitForUserAck Pending 0
23 DeployFailOverToRemoteFI Pending 0
24 DeployPollFailOverToRemoteFI Pending 0
25 DeployActivateLocalFI Pending 0
26 DeployPollActivateOfLocalFI Pending 0
27 DeployActivateUCSMServicePack Pending 0
28 DeployPollActivateOfUCSMServicePack Pending 0
BGY-NEW-HX-B /firmware/auto-install #
BGY-NEW-HX-B /firmware/auto-install # show fsm status expand detail | grep Prog
Status: In Progress
Progress (%): 98
Status: In Progress
BGY-NEW-HX-A /firmware/auto-install # show fsm status
FSM 1:
Remote Result: Not Applicable
Remote Error Code: None
Remote Error Description:
Status: Nop
Previous Status: Deploy Success
Timestamp: 2017-11-23T10:21:32.159
Try: 0
Progress (%): 100
Current Task:
Flags: 0
BGY-NEW-HX-A /firmware/auto-install # show cluster state
Cluster Id: 0xaded5a7ccf6611e7-0xb59400defb68c3a1
A: UP, PRIMARY
B: UP, SUBORDINATE
HA READY
BGY-NEW-HX-A /firmware/auto-install #
Confirm that upgrade is complete
Step 1 Log in to Cisco UCS Manager to ensure that the HX nodes have no pending server activities. From Server > Pending Activities tab check for all server activities. Step 2 Confirm that the HX nodes match the expected firmware version. In Cisco UCS Manager, from Equipment > Firmware Management > Installed Firmware tab, verify for the correct firmware version. Step 3 Log in to any controller VM through SSH. # ssh root@controller_vm_ip Step 4 Confirm the HyperFlex Data Platform version. # stcli cluster version Cluster version: 2.5(1c) Node HX02 version: 2.5(1c) Node HX05 version: 2.5(1c) Node HX01 version: 2.5(1c) Node HX03 version: 2.5(1c) Node HX04 version: 2.5(1c) Step 5 Verify that the HX storage cluster is online and healthy. # stcli cluster info|grep -i health Sample output: healthstate : healthy state: healthy storage cluster is healthy Step 6 Verify that the datastores are up and are mounted properly on the ESXi host. From the HX controller VMs: # stcli datastore list From the ESXi host: # esxcfg-nas -l Step 7 For each browser interface you use, empty the cache and reload the browser page to refresh the HX Connect content.
Troubleshooting
Force Subordinate to PRIMARY
connect local-mgmt cluster lead b 显示request failed local node is SUBORDINATE # USE following parameters: cluster force primary