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 |
|
HPE ServiceGuard Cluster Commands
This section includes the ServiceGuard clustering commands.
/usr/local/bin/sudo /usr/sbin/cmviewcl -v
Output:
CLUSTER STATUS
SomeClusterName up
NODE STATUS STATE
Node1 up running
Quorum_Server_Status:
NAME STATUS STATE
172.24.0.5 up running
Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up 0/2/2/1 lan3
PRIMARY up 0/1/1/1 lan1
PRIMARY up 0/2/2/0 lan2
PRIMARY up 0/1/1/0 lan0
STANDBY up 0/3/0/0/0/0/4/0/0/ lan7
STANDBY up 0/3/0/0/0/0/2/0/0/ lan5
STANDBY up 0/3/0/0/0/0/4/0/0/ lan6
STANDBY up 0/3/0/0/0/0/2/0/0/ lan4
PACKAGE STATUS STATE AUTO_RUN NODE
PackageName1 up running enabled Node1
Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Failover configured_node
Failback manual
Node_Switching_Parameters:
NODE_TYPE STATUS SWITCHING NAME
Primary up enabled Node1 (current)
PACKAGE STATUS STATE AUTO_RUN NODE
PackageName2 up running enabled Node1
Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Failover configured_node
Failback manual
Script_Parameters:
ITEM STATUS MAX_RESTARTS RESTARTS NAME
Subnet up 192.168.62.0
Subnet up 172.24.0.0
Node_Switching_Parameters:
NODE_TYPE STATUS SWITCHING NAME
Primary up enabled Node1 (current)
PACKAGE STATUS STATE AUTO_RUN NODE
PackageName3 up running enabled Node1
Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Failover configured_node
Failback manual
Node_Switching_Parameters:
NODE_TYPE STATUS SWITCHING NAME
Primary up enabled Node1 (current)
Mapping
Output of this command is used to fill in the attributes of the CIs:
CMD Output Attribute | CI Name | CI Attribute |
---|---|---|
SomeClusterName | Service Guard Cluster | Name |
PackageName1,..., PackageName3 |
SG Package | Name |
IP Address | SG Resource | Name |
Subnet value | Network | Name |
Node1 | Node | Name |
find /etc/cmcluster/ -name '*.cfg'
Output:
/etc/cmcluster/scripts/exampleapplicatie.cfg
/etc/cmcluster/package1/package1.cfg
/etc/cmcluster/package2/package2.cfg
/etc/cmcluster/package3/package3.cfg
Mapping:
This command is used to find package configuration files in the SG Cluster configuration directory.
find /etc/cmcluster/ -name '*.config'
Output:
/etc/cmcluster/scripts/exampleapplicatie.config
/etc/cmcluster/package1/package1.config
/etc/cmcluster/package2/package2.config
/etc/cmcluster/package3/package3.config
Mapping:
This command is used to find package configuration files in the SG Cluster configuration directory.
cat "/etc/cmcluster/package1/package.cfg" | grep -iE "PACKAGE_NAME|SCRIPT_LOG_FILE|RUN_SCRIPT|FS_DIRECTORY"
Output:
# "PACKAGE_NAME" is the name that is used to identify the package.
# Legal values for PACKAGE_NAME:
PACKAGE_NAME package1
# "RUN_SCRIPT" is the script that starts a package.
# Legal values for RUN_SCRIPT:
RUN_SCRIPT /etc/cmcluster/package1/package1.cntl
# "RUN_SCRIPT_TIMEOUT" is the number of seconds allowed for the package to start.
Mapping:
PACKAGE_NAME and RUN_SCRIPT variable values are used in further commands for discovery of IP and Mount Points, which are managed by this package.
cat "/etc/cmcluster/package1/package1.cntl.log" | grep -E "Mounting"
Output:
Jul 11 09:27:10 - Node "Node1":
Mounting /dev/vg1/lvol1 at /oracle/somename1
Jul 11 09:27:22 - Node "Node1":
Mounting /dev/vg1/lvol2 at /oracle/somename2
Jul 11 09:27:53 - Node "Node1":
Mounting /dev/vg1/lvol3 at /oracle/somename3
Mapping:
Discovered data for mount points will be used to link the RunningSoftware to the proper Clustered Service (actually a package). This linking approach relies on the running process path.
cat "/etc/cmcluster/package1/package1.cntl.log" | grep -E "Adding IP"
Output:
Jun 12 09:27:11 - Node "Node1":
Adding IP address 192.168.62.146 to subnet 192.168.62.0
Jun 12 09:27:11 - Node "Node1":
Adding IP address 172.24.10.142 to subnet 172.24.0.0
Mapping:
Discovered IP Address and Network will be reported as corresponding CIs. This is done because not all IP Resources might be present in the cmviewcl output.
ps -ef | grep "tnslsnr"
Output:
orauser 21926 1 0 Jun 9 ?
6:09 /oracle/somename1/applic/oracle/db/
10.2.0/instns1/bin/tnslsnr listener_name1 -inherit
Mapping:
From the fetched Oracle Listener process information ORACLE_HOME value, listener name and pid will be parsed out. ORACLE_HOME and listener name will be used in further discovery to get listener status and parse out Oracle DB SIDs.
/oracle/somename1/applic/oracle/db/10.2.0/instns1/bin/lsnrctl status listener_name1
Output:
LSNRCTL for HPUX: Version 10.2.0.5.0 -
Production on 20-JUL-2011 06:44:11
Copyright (c) 1991, 2010, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=oic6)))
STATUS of the LISTENER
------------------------
Alias listener_name1
Version TNSLSNR for HPUX: Version 10.2.0.5.0 -
Production Start Date 09-JUN-2011 21:56:34
Uptime 40 days 8 hr. 47 min. 36 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File
/oracle/somename1/applic/oracle/db/10.2.0/
instns1/network/admin/listener.ora
Listener Log File
/oracle/somename1/applic/oracle/db/10.2.0/
instns1/network/log/listener_name1.log
Listening Endpoints Summary...
DESCRIPTION=
ADDRESS=(PROTOCOL=ipc)(KEY=sid1)))
DESCRIPTION=
ADDRESS=(PROTOCOL=tcp)(HOST=192.168.80.24)(PORT=1521)))
DESCRIPTION=
ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROCsidas)))
Services Summary...
Service "PLSExtProcsid1" has 1 instance(s).
Instance "PLSExtProcdis1", status UNKNOWN,
has 1 handler(s) for this service...
Service "sid1.somedomain" has 1 instance(s).
Instance "sid1", status UNKNOWN,
has 1 handler(s) for this service...
The command completed successfully
Mapping:
Instance value will be parsed out and treated as SID; any instance name starting from PLSExtProc will be filtered out since this is RPC call service.
nice lsof -i 4 -a -P -n -p <Actual Pid>
or
nice pfiles 21926 2>&1 | awk "/S_IFSOCK|SOCK_STREAM|SOCK_DGRAM|port/ { print }"
Mapping:
Discovered IP and port information is used to set Application IP and Port on reported Running Software.
cat "/oracle/somename2/applic/oracle/oas/10.1.2/somename5/opmn/conf/opmn.xml"
Output:
......skip......
<ias-instance id="somename.somedomain">
<environment>
<variable id="TMP" value="/tmp"/>
<variable id="LD_LIBRARY_PATH" value="/usr/lib"/>
<variable id="LD_PRELOAD" value="libloghost.so.1"/>
......skip......
Mapping:
The Oracle iAS CI name is taken from value of ias-instance in the following order: parameter name, parameter id, Default Server.
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 cms-doc@microfocus.com.
Help Topic ID:
Product:
Topic Title:
Feedback: