Use this procedure to power on the
PowerFlex management node. This procedure is only applicable if a
PowerFlex management node (single non-HA node) is in use.
Steps
Log in to iDRAC and power on the
PowerFlex management node. Monitor the virtual console and wait for some time for the VMware ESXi server to appear.
Verify that the VMware vCenter VM is automatically powered on. If not, do the following:
Log in to VMware ESXi using the host client.
Click
Virtual Machines, select the management virtual machine, and click
Power on.
Power on the remaining VMs, starting with the three PowerFlex management virtual machines (MVMs):
Log in to
VMware vSphere Client.
From
vSphere Client > Shortcuts > Hosts and Clusters.
Right-click each of the management virtual machines and select
Power on.
Once the management virtual machines are powered on, power on the remaining VMs.
Log in to the nodes running
PowerFlex management platform processes (all three management virtual machines):
Run the following command to check the status of the rke2-server:
#systemctl status rke2-server Do the following depending on the rke2-server status:
Table 1. Status of the rke2-serverThe following table provides information about the status of the rke2-server.
Status of the rke2-server
Do the following
active
Go to the next step.
activating
Repeat the command to check the rke2-server status until active.
failed
Attempt to start the service by running the following command:
#systemctl start rke2-server
Once the rke2-server is running on all the three
PowerFlex management platform nodes, ensure that all nodes are in
ready state:
Log in to any of the PowerFlex nodes using SSH and run the following command:
#kubectl get nodes
If you see an error message, wait for a few minutes and try again. Once the nodes are in
ready state, go to the next step.
SSH into one of the PowerFlex management virtual machine primary nodes and run the following command to restore the cluster monitoring operator (CMO) database:
#alias k="kubectl -n $(kubectl get pods -A | grep -m 1 -E 'platform|pgo|helmrepo' | cut -d' ' -f1)"#kubectl config set-context default --namespace=$(kubectl get pods -A | grep -m 1 -E 'platform|pgo|helmrepo|docker' | cut -d' ' -f1)#kubectl -n powerflex patch $(kubectl -n powerflex get postgrescluster -o name) --type merge --patch '{"spec":{"shutdown":false}}
Verify the CMO database:
#echo $(kubectl get pods -l="postgres-operator.crunchydata.com/control-plane=pgo" --no-headers -o name && kubectl get pods -l="postgres-operator.crunchydata.com/instance" --no-headers -o name) | xargs kubectl get -o wide
Monitor the
PowerFlex management platform status:
Run the following command to identify the port number for the
PowerFlex management platform monitor utility:
#kubectl get services monitor-app -n powerflex -o jsonpath="{.spec.ports[0].nodePort}{\"\n\"}"
Wait for 20-30 minutes and check the overall health status of the
PowerFlex management platform.
Go to
http://<node IP>:port/
Where, the node IP address is a management IP address configured on any of the management virtual machines (not the Ingress or
PowerFlex management platform UI IP address).
Click
PFMP status and wait for all entries to turn green.
Contact Dell Technical Support if the
PowerFlex management platform status persists as red or the main UI is not accessible after 20-30 minutes.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\