Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Search for | Example | Results |
---|---|---|
A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Search for | Operator | Example |
---|---|---|
Two or more words in the same topic |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
Upgrading a multimaster mesh
When upgrading a multimaster mesh, the following steps must be performed:
- Make sure that all CORD patches are uninstalled
- Check the transaction status
- Shutdown services on the Secondary cores
- Upgrade the Primary Core
- Upgrade the Secondary Cores
Checking transaction status
Before starting to upgrade a multimaster mesh, make sure that there are no transactions that are not sent or received and that there are no conflicts. See the Viewing the State of the Multimaster Mesh - SA Client section in the SA 10.50 Administration Guide.
If conflicts exist, these must be resolved before starting the upgrade. See the Resolving Mesh Conflicts - SA Client section in the SA 10.50 Administration Guide for more details.
Shutting down the services on the secondary cores
Before starting the upgrade procedure of your cores, you must stop the services on all the secondary cores in the mesh, so as to avoid new running jobs to create conflicts.
Method 1: Shut down using the opsware-sas service
Run the following commands for each secondary core that is part of the mesh:
-
Shut down all Secondary Core services by issuing the following command as a user with root privileges on each Secondary Core host:
/etc/init.d/opsware-sas stop
-
Start the Management and Core Gateways on the Secondary Core host by issuing the following command:
/etc/init.d/opsware-sas start opswgw-mgw opswgw-cgws
Method 2: Shut down using the Management Console
You can also use the Management Console to stop the services. You need to invoke the following command once on each of the Secondary cores that is part of the mesh. On the Infrastructure host of each core, invoke the Management Console using the installation media:
<distro>/opsware_installer/hpsa_mgmt_console.sh –c <path_to_CDF_file>
where <distro>
is the full path to the distribution media. For example:
/<mountpoint>/hpsa-primary/disk001
Select the Shutdown service option in the utility menu and follow the instructions.
For more details, see the SA Management console section in the SA 10.50 Install Guide.
Upgrading the Primary Core of a multimaster mesh
Once the steps described above have been performed, you may start to upgrade the Primary Core of the mesh.
The services must be running on the Primary core, but must be stopped on the Secondary cores, as described in the previous step.
The upgrade process is the same as listed in Upgrading a single-host Core or Upgrading a single Core with distributed components sections described above, depending on the core layout. Refer to the corresponding section for the complete procedure.
Upgrading the Secondary Core of a multimaster mesh
Important Start the upgrade process on the secondary cores only after the Primary core upgrade is successfully complete.
You can upgrade the Secondary Cores in a mesh one at a time or upgrade multiple Secondary Cores concurrently. After each Secondary Core has been upgraded, its services will be restarted and can remain running while you upgrade the other Secondary Cores.
The upgrade process is the same as listed in Upgrading a single-host Core or Upgrading a single Core with distributed components sections described above, depending on the core layout. Refer to the corresponding section for the complete procedure.
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to hpe_sa_docs@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: