Best practices to shutdown Aria Operations for Networks Clustered deployments
search cancel

Best practices to shutdown Aria Operations for Networks Clustered deployments

book

Article ID: 314428

calendar_today

Updated On:

Products

VCF Operations for Networks

Issue/Introduction

This article offers detailed recommendations on how to effectively shutdown and take snapshots and restore Aria Operations for Networks Clustered deployment, specifically focusing on platform/collector nodes, during maintenance activities such as:

  • Correctly shutdown Aria Operations for Networks Clustered deployment for taking snapshots for upgrade
  • Correctly shutdown Aria Operations for Networks Clustered deployment for taking snapshots for applying GA Patches or Hot Patches on top of  current release deployments.
  • Correctly shutdown Aria Operations for Networks Clustered deployment for any customer datacenter maintenance activities apart from upgrades and applying GA/Hot patches.

This script helps ensuring the process is smooth and well-prepared and ready for above mentioned activities.

This script can be executed for Clustered deployments that have 3, 5, 7, 10 or 15 Platform Nodes.

This script attached in this KB is applicable for ALL Aria Operations for Networks deployments even those which are managed by Aria Suite Lifecycle (vRSLCM) until an issue with the shutdown logic in vRSLCM is released.

Environment

  • Aria Operations for Networks 6.13.0
  • Aria Operations for Networks 6.14.0
  • Aria Operations for Networks 6.14.1
  • VCF Operations for Networks 9.x

Resolution

Follow the below given sequence of steps needs to followed  as in order mentioned below:

  1. Download the Script :- Download the script  from the attachment section in this article to your local system.
  2. Copy the Script to Platform Node1 in a Clustered deployment :

    Once the script is downloaded, it needs to be transferred to platform 1.
    You can use the scp (Secure Copy Protocol) command or any other secure file transfer method to copy the script to the platform 1.

    For example, using scp:

    scp vrni-cluster-shutdown-script.sh support@<platform1-IP>:/home/support/


    After the password prompt, input the support user password to copy the file.
    Alternatively, WinSCP tool can be used to copy the file to Platform1 under location /home/support.
    Validate the downloaded script file against the below mentioned details and any one of the checksum values mentioned in below section.

    Filename, size and checksum values details:

    Filename: vrni-cluster-shutdown-script.sh
File size: 14.5 KB
Checksum Values:
MD5: EAD841F0AF75CEE0D2C4DFEBE19BDB24
SHA-1: E5E1FA7DECCA25FDA9188FAE5ED0B182DDA1966E
SHA-265: 257DF2738CC48DD3F880F2E725A681952F9D305AF36CE00868E944373A313C2F

    For checksum values use any one of the below commands :

    Type md5sum followed by the file name  
Press Enter
The md5sum of the file will be displayed

or 

Type sha1sum followed by the file name
Press Enter
The sha1sum sum of the file will be displayed

or 

Type sha256sum followed by the file name
Press Enter
The sha256sum sum of the file will be displayed

     

  3. Steps to take snapshot :

    Once the script is transferred to Platform1, execute the below mentioned steps:

    1. Manually shutdown collector nodes from vCenter using  Power > Shut down guest OS.
    2. Take a SSH/Putty session to Aria operations for Networks Platform Node1
    3. Login with username support
    4. Run ub which will change the prompt from support to ubuntu
    5. Run sudo mv /home/support/vrni-cluster-shutdown-script.sh /home/ubuntu/vrni-cluster-shutdown-script.sh
    6. Run sudo chown ubuntu:ubuntu vrni-cluster-shutdown-script.sh
    7. Run sudo chmod +x vrni-cluster-shutdown-script.sh
    8. Run below command to stop all the platforms.

      ./vrni-cluster-shutdown-script.sh shutdown 127.0.0.1 "/home/ubuntu/vrni-cluster-shutdown-script$(date +%s).log"

       

    9. Verify all the nodes are successfully powered off in vCenter GUI
    10. Take snapshots of the platforms and collector nodes.
    11. Power on all the platform nodes in the cluster, order should be 1 to N.
    12. Verify all the platform nodes are powered on in vCenter Console. If you see service such as NTP is NOT-IN-SYNC. Retrying in [1/36[ with [signal]. This is expected behavior as NTP service is masked when script was executed in step 7 above. No Action is needed to correct NTP, proceed to Step m.
    13. Run below command to start the services on all the platforms    

      ./vrni-cluster-shutdown-script.sh start-services 127.0.0.1 "/home/ubuntu/vrni-cluster-shutdown-script$(date +%s).log"

       

    14. After a few minutes, access the Aria Operations for Networks GUI and validate login is successful and also ensure no apparent issues are seen  GUI. 
    15. Power on the Collector VM from vCenter.
    16. Verify all the collector nodes are powered via vCenter GUI

  4. Steps to restore snapshots
    1. Power off all the nodes from vCenter GUI.
    2. Verify all the nodes in the deployment i.e. Platform(s) and collectors(s) are successfully powered off in vCenter UI
    3. Revert the snapshots of the platforms and collectors.
    4. Power on all the platform nodes in the cluster, order should be 1 to N.
    5. Verify all the platform nodes are powered on in vCenter UI
    6. Run below start the services on all the platforms nodes.

      ./vrni-cluster-shutdown-script.sh start-services 127.0.0.1 "/home/ubuntu/vrni-cluster-shutdown-script$(date +%s).log"

       

    7. After a few minutes, access the Aria Operations For Networks UI and validate login is successful. 
    8. Power on the Collector VM(s) on from vCenter GUI.
    9. Verify all the collector nodes are powered on in vCenter UI.

Now login to Aria Operations for Networks GUI and proceed with performing the upgrade/apply GA /Hot patches.

Additional Information

Important Notes:

  • For a Single platform environment, the script is NOT needed, just turn off the platform through vCenter via shutdown GuestOS and take a snapshot/backup.
  • To revert the snapshot, turn off the platform through vCenter via shutdown GuestOS and restore the snapshots.
  • To take collector(s) node snapshots, the script is not needed, just turn off the collector through vCenter via shutdown GuestOS and take snapshot.
  • To revert the snapshot, turn off the collector through vCenter via shutdown GuestOS and restore the snapshot/backup.
  • This attached script can be also used to take snapshot when performing a Cluster and Cluster expansion operations as well.


Additional Notes:

  • Log Files: The log file path is optional. If provided, the script will store the log file at the specified location for later review. If not, logging will be limited to the console during script execution.
  • Always ensure you are working with the correct Platform Node 1 IP and have SSH access configured properly.
  • Execute the script from Platform Node1.
  • Do not execute this script from collector node since running from collector node is blocked.

Attachments

vrni-cluster-shutdown-script.sh get_app
Powered by Wolken Software