Upgrade verification tasks

The upgrade verification tasks allow you to prepare for an uninterrupted VxBlock Central upgrade process. Perform the verification tasks before and after you upgrade VxBlock Central. These tasks include verifying the VM versions, ensuring the services are up and running, and checking the connection between the MSM VM for SLIB and the MSP VM.

About this task

Note: During the version verification process, the package version is displayed instead of the release version. The supported versions are:
  • Package version: 5.1.0
  • VxBlock Central release version: 2.1

Procedure

  1. Use Putty (or any similar application) to get a SSH session for the VMs.
  2. Log in to CLI using the root username and password.
  3. For the Core VM, type the following command to verify the version, service status, discovery completion status, and the results of the last five discovery cycles: echo "Checking the version information" ; getFMagentInfo ; echo -e "\nChecking the services in CORE VM" ; vision status ; echo -e "\nChecking the discovery completion status and showing the last 5 successful cycle completion result" ; cat /opt/vce/fm/logs/FMAgent.log | grep -i "current status" | grep -i "100%" | tail -5
  4. For the MSM VM, type the following command to verify the version, service status, credential manager CLI service status, validation of the credentials, and connection with the Cassandra database : echo -e "\nChecking the version installed" ; visionver ; echo -e "\nChecking the services in MSM VM" ; vision status ; echo -e "\n" ;/opt/vce/credential-management/bin/credential-manager-cli status ; echo -e "\n" ; /opt/vce/credential-management/bin/credential-manager-cli validate ; echo -e "\nChecking the connection to Cassandra DB" ; /opt/vce/multivbmgmt/install/getConnectInfo.sh -e "select * from systeminfo.appinfo"
  5. Type the following command to verify the connection of Core VM with MSM VM: /opt/vce/multivbmgmt/install/listSlibNodes.sh
  6. For the MSP VM, type the following command to verify the version, service status, communication between MSM VM and MSP VM (check for the number of RabbitMQ connections), and the MSP VM configuration file has the MSM VM hostname listed and display on the screen: echo -e "\nChecking the version installed" ; visionver ; echo -e "\nChecking the status of the services in MSP VM" ; vision status ; echo -e "\nChecking if we have rabbitmq connections between MSM and MSP VM" ; count=$(netstat -ntp | grep -i ":5672" | wc -l); if [[ $count != 4 ]]; then echo "$count is INCORRECT, check rabbitmq on MSM"; else echo "$count is CORRECT"; fi ; echo -e "\nChecking if MSM hostname is listed correctly in the MSP configuration file" ; echo -e "PARAMETER remote.vce.amqp.rabbitHostnames is set to $(cat /opt/vce/msp/conf/msp-common.properties | grep -i "remote.vce.amqp.rabbitHostnames" | cut -d '=' -f2)"
    Note: The count of RabbitMQ connections must be equal to four. If not, then no connection is established.