Upgrade the Monitor in Non-HA Mode
Be sure to review Upgrade Overview before starting this procedure!
This section provides details on upgrading your CloudCenter deployment in Non-HA mode.
For each CloudCenter deployment that needs to be upgraded, verify the following prerequisites:
Backup your database and applications before you begin this process.
You should have already completed the following procedures:
Review the information provided in the Upgrade Overview section and validate the following requirements for the release to which you are upgrading:
- Is an upgrade path available?
- Is the core_upgrade.bin file required?
Ensure that a version file (/usr/local/osmosix/etc/version) exists in both Monitors to be upgraded.
Verify that the version file contains the correct version number (for example, if your current CloudCenter release version is 4.7.2, ensure that the corresponding version value is 4.7.2).
See the corresponding release notes for release-specific information on the CloudCenter version to which you are upgrading. For example, the CloudCenter 4.8.0 Release Notes.
Backup the exploded war files to a backup folder (the following example uses /mnt, you can change this directory as applicable)
SSH into the VM instance designated for this component by using the key pair that you used to launch the VM.
Along with the key pair, you may need to use your login credentials for sudo or root access based on your environment.
Download the following required files for this component from software.cisco.com:
Run the following commands:
For example: ./core_upgrade.bin centos7 amazon monitor
<ostype> = centos6, centos7, rhel6, rhel7 (Ubuntu12.04 is not recommended for a new install)
<cloudtype> = amazon, azureclassic, azurepack, azurerm, google, opsource, openstack, softlayer, vmware, vcd
Run the following command from your download folder.
Post Upgrade Tasks
Verify Your Upgrade – Ensure that the version file (/usr/local/osmosix/etc/version) reflects the new release.
Reboot the Monitor server.
- Configure the Properties in the Monitor Wizard.
Install Monitor Using Appliances (Required)
The Elasticsearch, Logstash, and Kibana, collectively referred to as the ELK stack, are installed by default when you install the Health Monitor. To be able to Download Log Files, be sure to install this component!
Configure Monitor Wizard Properties
The Monitor is a required CloudCenter component!
Invoke the wizard as a root user (see Virtual Appliance Process > Cloud-Specific Setup Details for a sample setup).
Configure the properties for the Monitor instance.
Write this down for future reference!Write down the Field details in a printed version of thesection for later use.
Wizard Menu Field Notes CCM_Info Monitor ID
A unique (alphanumeric) identifier used for the health check instance.
CCM Hostname/URL (Required)
- CCM_IP or
- CCM_SA_IP or
Monitor User The User ID configured on the CCM server to enable health check for cloud regions.
- To perform a health check on all activated cloud regions, set this value as 2 (2 is the CloudCenter’s root administrator’s User ID).
- To perform a health check on specific cloud regions, create and activate a new user with those specific regions and use that user’s User ID as value for this property. To get the User ID, use the v1 User Management APIs.
ELK_Login ELK User The default Username for the ELK/Monitor host is logreader. ELK Password The default ELK Password is re@d0nly (zero between d and n) (change this password after the initial login – see Download Log Files for additional context). Config_Certs Certs Zip Path Provide the path for the certs.zip file. The default path is /tmp/certs.zip.
Verify your changes and Exit the Monitor configuration wizard.
Select Yes, to restart the Tomcat service for the changes to take effect.
You have successfully configured the Monitor instance! You can now proceed to thesection and install the CloudCenter components for each Cloud.
Verify that you have configured the ELK stack and Monitor details in theand the servers.
- No labels