Aria Operations for Networks post upgrade Health Checks
search cancel

Aria Operations for Networks post upgrade Health Checks

book

Article ID: 412763

calendar_today

Updated On:

Products

VCF Operations for Networks

Issue/Introduction

This outlines the Health Checks you can perform once you have successfully upgraded Aria Operations for Networks

Environment

Aria Operations for Networks 6.13.0
Aria Operations for Networks 6.14.0
Aria Operations for Networks 6.14.1

Resolution

Post successful upgrade for Aria Operations for Networks there are several items that can be checked to ensure all components have been upgraded and are healthy.  Once the upgrade has completed you need to wait for 1 hour to allow a few polling cycles to complete on the new version

 

  1. Log into the UI and go to Settings / Infrastructure and Support and ensure the proper new version is showing



  2. On the Infrastructure and Support page check the usage and capacity to ensure they have not been breached.



  3. Now check each Platform and Collector node to ensure they have been upgraded ( post upgrade this can be delayed 20-30 minutes).  On the Infrastructure and Settings page scroll to the bottom of the page where the Platform and Collector nodes are displayed and select each node and the new version should appear.

    Platform node
    Collector node

  4. SSH to Platform node1 to run the following commands:
    ub
    ./run_all.sh uptime  <-- This will display the uptime for all Platform nodes in the cluster
    ./run_all.sh df -h   <-- This will show the disk usage, if any directory is near 80% capacity take a screen shot, generate a new log bundle and open a support case
    ./run_all.sh sudo /home/ubuntu/check-service-health.sh -p -d <-- This will check all service on all the nodes, all services should be Running and Healthy and if they are not generate a new log bundle and open a Support case.
    sudo cat /home/ubuntu/build-target/deployment/patch.txt <-- This will show the nodes patch history and should include the latest upgrade and show complete and the date.
    

     

  5. Now we need to check the database to ensure the data has stabilized - SSH to Platform node1 as the Support user and run the following:
    ub
    fdbcli
    >status details  <-- this should show no moving data and Healthy
    >exit

     

  6. Check the nodes IOPS to ensure disk performance is good (This can be ran on both Platform and Collector nodes)  as the Support user on each node

    a) Read disk IOPS:
    ./run_all.sh 'file="/var/lib/ubuntu/fio-tmp"; fio --filename=$file --direct=1 --ioengine=libaio --bs=4K --name=bw-test --rw=randread --iodepth=4 --size=100M | grep -i IOPS; rm -f $file'

    b) Write disk IOPS: 

    ./run_all.sh 'file="/var/lib/ubuntu/fio-tmp"; fio --filename=$file --direct=1 --ioengine=libaio --bs=4K --name=bw-test --rw=randwrite --iodepth=4 --size=100M | grep -i IOPS; rm -f $file'

       
 If you have another upgrade to complete it is recommend to wait 24 hours before proceeding

Additional Information