Managing Cluster Resources of The M2000 HA System: About This Chapter

M2000
HA System Administrator Guide (S10)
3 Managing Cluster Resources of the M2000 HA System
Managing Cluster Resources of the M2000

HA System
About This Chapter

This chapter describes how to manage the cluster resources of the M2000 HA system.
3.1 Introduction to Cluster Resources of the M2000 HA System
This describes the cluster resources of the M2000 HA system. The resources consist of working
principles of the Sun Cluster, resource planning of the M2000 HA system, and automatic
switching of active and standby nodes.
3.2 Switching Over Active and Standby Nodes
This lists the conditions for switching over active and standby nodes and describes how to switch
over the active and standby nodes.
3.3 Registering the Sybase
This describes how to register the Sybase. After the Sybase is registered in the Sun Cluster, the
Sun Cluster monitors the operating status of the Sybase in real time. After the Sybase is
registered, modify the file /opt/SUNWscsyb/bin/sybase_stop_servers on both node 1 and node
2. After the Sybase is registered in the Sun Cluster, the file needs to be modified only on node
1.
3.4 Registering the M2000 Server Application
This describes how to register the M2000 server application. After the M2000 server application
is registered on the Cluster, the M2000 server application is managed by the Cluster as the
resource. The operation is performed only on node 1.
3.5 Managing Cluster Resources
This describes how to manage the cluster resource of the M2000 HA system. The process for
managing the cluster resource involves starting and stopping the Cluster monitoring resources,
the M2000 system service, and the Sybase.
Issue 06 (2008-03-18)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd
3-1
M2000
3.1 Introduction to Cluster Resources of the M2000 HA

System
This describes the cluster resources of the M2000 HA system. The resources consist of working
principles of the Sun Cluster, resource planning of the M2000 HA system, and automatic
switching of active and standby nodes.
3.1.1 Work Principle of the Sun Cluster
This describes the working principle of the Sun Cluster and defines the switch mechanism,
resource group, and resource. For details, refer to the user manual of the Sun Cluster.
3.1.2 Resource Planning for the M2000 HA System
This describes the resource planning for the M2000 HA system. The resources consist of the
Cluster, resource group, and detailed resource planning.
3.1.3 Automatic Switchover Conditions of Active and Standby Nodes
This describes the resource monitoring mechanism, principle of switching active or standby
nodes, and automatic switching conditions for the M2000 HA system.
3.1.1 Work Principle of the Sun Cluster

This describes the working principle of the Sun Cluster and defines the switch mechanism,
resource group, and resource. For details, refer to the user manual of the Sun Cluster.
Introduction to the Sun Cluster

The Sun Cluster promotes the Solaris operating environment to a cluster operating system. As
a collection of loose coupling computing nodes, the cluster provides a single customer view for
network services or applications such as database, web service, and file service. The cluster
supports the applications with high availability and flexibility.
Switching Mechanism
The cluster can automatically relocate the applications from a faulty active node to a specified
standby node, and thus the Sun Cluster features high availability.
If the active node, that is, the node running services, is faulty, the Cluster restarts the services
on the same node. If the restart fails, the service is switched to the other node automatically.
There may be a temporary interruption during the switchover and you may need to reconnect
the two nodes after the switchover. The physical server that provides the applications and data,
however, is visible.
Resource
Resource is the instance of the resource type defined in the cluster range. The same resource
type may contain many resources and each resource has a name and an attribute group. In this
case, instances of the basic applications can run on the cluster.
Resource Group
A resource group is a group of resources that are associated with each other. These resources
depend on each other.
3-2

Issue 06 (2008-03-18)
M2000
3.1.2 Resource Planning for the M2000 HA System

This describes the resource planning for the M2000 HA system. The resources consist of the
Cluster, resource group, and detailed resource planning.
Table 3-1 lists the factory settings of the Sun Cluster in the M2000 HA system.
Table 3-1 Factory settings of the Sun Cluster
Item
Name
Description
Cluster
osscluster
The Cluster name is unique in

a enterprise.
Resource group
oss_rg
Refer to the resource group of

the system.
Resource
ossdg_rs
Refer to the resource name of

the disk array.
sybase_rs
Refer to the resource name of

the Sybase.
ossapp_rs
Refer to the application

resource name of the
M2000 .
3.1.3 Automatic Switchover Conditions of Active and Standby

Nodes
M2000 Resource Monitoring Mechanism and Switchover Principle

The M2000 uses the monitoring mechanism of the Cluster to monitor the daemon process. This
ensures the system security of the M2000. In the event of a serious fault, the M2000 can quickly
detect the fault and automatically restart the applications.
The monitoring script monitors the ServiceManager and start_service of the M2000. The two
daemon processes monitor other M2000 services. In addition, the two daemon processes are
responsible for automatic restart in the event of a system fault.
The Cluster of the HA system runs the monitoring script at regular intervals. The interval is the
attribute value of Thorough_probe_interval of the M2000 resource ossapp_rs. The default
value is 60. If the script returns a message stating that the services are normal, the monitoring
continues. If the script returns a message stating that the services are not normal, the system
invokes the script stop_OMC.sh and stops the M2000 services. When the services are stopped,
the monitoring also stops. When the stopped services need to be restarted, the system invokes
the script start_OMC.sh to start the M2000 services and records the time at that point. After
the interval of Thorough_probe_interval, the system starts the next phase of monitoring.
If the services ServiceManager and start_service are restarted successfully, the Cluster regards
the M2000 as normal and thus continues the monitoring.
Issue 06 (2008-03-18)

3-3
M2000
If the services fail to restart, the system tries to restart the services for the times as specified by
Retry_count of ossapp_rs. The default value is 2. After retry attempts are over, the system
measure the time between the restart time of the system and the beginning of the next monitoring
process after the interval Thorough_probe_interval. If the monitoring script returns a message
stating that the system is normal, the system performs the switchover and switches the resource
from the active node to the standby node.
M2000 Switching Conditions

The Cluster switches the Sybase, M2000 server application, and disk array resources to the other
server in the following cases:
l
CPU faults
Memory faults
Disk access faults
Main board faults
Disconnection between the host Ethernet adapter and the LAN switch
Operating system faults
Database faults
3.2 Switching Over Active and Standby Nodes

This lists the conditions for switching over active and standby nodes and describes how to switch
over the active and standby nodes.
3.2.1 Automatic Switchover Conditions of Active and Standby Nodes
3.2.2 Manually Switching Over Active and Standby Nodes
This describes how to switch over active and standby nodes.
3.2.1 Automatic Switchover Conditions of Active and Standby

Nodes
M2000 Resource Monitoring Mechanism and Switchover Principle

The M2000 uses the monitoring mechanism of the Cluster to monitor the daemon process. This
ensures the system security of the M2000. In the event of a serious fault, the M2000 can quickly
detect the fault and automatically restart the applications.
The monitoring script monitors the ServiceManager and start_service of the M2000. The two
daemon processes monitor other M2000 services. In addition, the two daemon processes are
responsible for automatic restart in the event of a system fault.
The Cluster of the HA system runs the monitoring script at regular intervals. The interval is the
attribute value of Thorough_probe_interval of the M2000 resource ossapp_rs. The default
value is 60. If the script returns a message stating that the services are normal, the monitoring
3-4

Issue 06 (2008-03-18)
M2000
continues. If the script returns a message stating that the services are not normal, the system
invokes the script stop_OMC.sh and stops the M2000 services. When the services are stopped,
the monitoring also stops. When the stopped services need to be restarted, the system invokes
the script start_OMC.sh to start the M2000 services and records the time at that point. After
the interval of Thorough_probe_interval, the system starts the next phase of monitoring.
If the services ServiceManager and start_service are restarted successfully, the Cluster regards
the M2000 as normal and thus continues the monitoring.
If the services fail to restart, the system tries to restart the services for the times as specified by
Retry_count of ossapp_rs. The default value is 2. After retry attempts are over, the system
measure the time between the restart time of the system and the beginning of the next monitoring
process after the interval Thorough_probe_interval. If the monitoring script returns a message
stating that the system is normal, the system performs the switchover and switches the resource
from the active node to the standby node.
M2000 Switching Conditions

The Cluster switches the Sybase, M2000 server application, and disk array resources to the other
server in the following cases:
l
CPU faults
Memory faults
Disk access faults
Main board faults
Disconnection between the host Ethernet adapter and the LAN switch
Operating system faults
Database faults
3.2.2 Manually Switching Over Active and Standby Nodes

This describes how to switch over active and standby nodes.
Context
Take the switchover from osssvr-1 to osssvr-2 as an example to describe the procedures for
manual switchover.
Procedure
Step 1 Run the scstat command to check whether the system status is normal.
The online state means that the resource group is activated on the server.
# scstat
------------------------------------------------------------------- Cluster Nodes --
Cluster node:
Cluster node:
Node name
--------osssvr-1
osssvr-2
Status
-----Online
Online
------------------------------------------------------------------
Issue 06 (2008-03-18)

3-5
M2000
-- Cluster Transport Paths --
Transport path:
Transport path:
Endpoint
-------osssvr-1:bge3
osssvr-1:bge1
Endpoint
-------osssvr-2:bge3
osssvr-2:bge1
Status
-----Path online
Path online
------------------------------------------------------------------- Quorum Summary -Quorum votes possible:

Quorum votes needed:
Quorum votes present:
3
2
3
-- Quorum Votes by Node -Node Name

--------osssvr-1
osssvr-2
Node votes:
Node votes:
Present Possible Status

------- -------- -----1
1
Online
1
1
Online
-- Quorum Votes by Device --
Device votes:
Device Name
----------/dev/did/rdsk/d4s2
Present Possible Status

------- -------- -----1
1
Online
------------------------------------------------------------------- Device Group Servers --
Device group servers:
Device Group
-----------ossdg
Primary
------osssvr-1
Secondary
--------osssvr-2
-- Device Group Status --
Device group status:
Device Group
-----------ossdg
Status
-----Online
-- Multi-owner Device Groups -Device Group

------------
Online Status
-------------
------------------------------------------------------------------- Resource Groups and Resources -Group Name

---------Resources: oss_rg
Resources
--------osssvr_rs ossdg_rs sybase_rs ossapp_rs
-- Resource Groups -Group Name

---------Group: oss_rg
Group: oss_rg
3-6
Node Name
--------osssvr-1
osssvr-2

State
----Online
Offline
Issue 06 (2008-03-18)
M2000
-- Resources -Resource Name

------------Resource: osssvr_rs
- LogicalHostname online.
Resource: osssvr_rs
- LogicalHostname offline.
Resource: ossdg_rs
Resource: ossdg_rs
Resource: sybase_rs
Resource: sybase_rs
- Adaptive_server: STOPPED
Node Name
--------osssvr-1
State
----Online
Status Message
-------------Online
osssvr-2
Offline
Offline
osssvr-1
osssvr-2
Online
Offline
Online
Offline
Online
Offline
Online
Offline
Online
Offline
Online
Offline
osssvr-1
osssvr-2
backup_server: STOPPED
Resource: ossapp_rs
Resource: ossapp_rs
osssvr-1
osssvr-2
Step 2 Log in as user root to perform the switchover on the active or standby node.
# scswitch -S -h osssvr-1
Step 3 Check whether the switchover is successful.
# scstat
----End
3.3 Registering the Sybase

This describes how to register the Sybase. After the Sybase is registered in the Sun Cluster, the
Sun Cluster monitors the operating status of the Sybase in real time. After the Sybase is
registered, modify the file /opt/SUNWscsyb/bin/sybase_stop_servers on both node 1 and node
2. After the Sybase is registered in the Sun Cluster, the file needs to be modified only on node
1.
1.
3.3.1 Installing the Sybase Agent

This describes how to install the Sybase Agent on both node 1 and node 2.
2.
3.3.2 Modifying the File sybase_stop_servers in the Folder /opt/SUNWscsyb/bin

This is performed to add user information of sa in the file /opt/SUNWscsyb/bin/
sybase_stop_servers. The task ensures that the Cluster passes verification when the Cluster
starts the Sybase. You need to perform this operation on both Node1 and Node2.
3.
3.3.3 Registering the Sybase into the Cluster

This section describes how to register the Sybase on only node 1.
4.
3.3.4 Checking the Registration of the Sybase

This describes how to check the registration of the Sybase. After the Sybase is registered
in the Cluster, you must check the registration to ensure that the resource can be managed
by the Cluster. This operation is performed only on node 1.
5.
3.3.5 Activating sybase_rs

This describes how to activate sybase_rs. After the Sybase is registered and activated in
the Cluster, the Cluster monitors and manages the Sybase. This operation is performed only
on node 1.
3.3.1 Installing the Sybase Agent

This describes how to install the Sybase Agent on both node 1 and node 2.
Issue 06 (2008-03-18)

3-7
M2000
Prerequisite
l
You have logged in to node 1 and node 2 as user root.
You have unloaded the M2000 installation package to node 1.
Procedure
Step 1 Type the path of the Sybase Agent installation package.
l
To install the Sybase Agent installation package on node 1, run the following command:
# cd /opt/OMC/etc/dual
To install the Sybase Agent installation package on node 2, transfer the registration
package /opt/OMC/etc/dual/SUNWscsyb.tar.gz in bin mode from node 1 to the path /
tmp on node 2 through the FTP.
Run the command ftp IP address of node 1 on node 2 and log in to node 1 as user root. Run
the following commands:
ftp> lcd /tmp
ftp> cd /opt/OMC/etc/dual
ftp> bin
ftp> get SUNWscsyb.tar.gz
ftp> bye
After the files are transferred, run the following command to navigate to the installation
directory of node 2:
# cd /tmp
Step 2 Extract the package SUNWscsyb.tar.gz on node 1 and node 2.

# gunzip SUNWscsyb.tar.gz
# tar xvf SUNWscsyb.tar
# pkgadd -d .
Step 3 At the following prompt, press Enter.
The following packages are available:
1 SUNWscsyb
Sun Cluster HA Sybase data service
(sparc) 3.1.0,REV=2005.07.18.10.43
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:
Step 4 At the following prompt, press Enter:

Do you want to continue with the installation of <SUNWscsyb> [y,n,?]
The system prompts the following information after the installation of Sybase Agent.
Installation of <SUNWscsyb> was successful.
----End
3-8

Issue 06 (2008-03-18)
M2000
3.3.2 Modifying the File sybase_stop_servers in the Folder /opt/

SUNWscsyb/bin
This is performed to add user information of sa in the file /opt/SUNWscsyb/bin/
sybase_stop_servers. The task ensures that the Cluster passes verification when the Cluster
starts the Sybase. You need to perform this operation on both Node1 and Node2.
Prerequisite
You have logged in to Node1 and Node2 as root.
Procedure
Step 1 Open /opt/SUNWscsyb/bin/sybase_stop_servers and run the following commands:
# cd /opt/SUNWscsyb/bin
# TERM=vt100; export TERM
# vi sybase_stop_servers
Step 2 Find the following contents in two different places in the file.
${SYBASE}/${SYBASE_OCS}/bin/isql -Usa
-S${ADAPTIVE_SERVER_NAME}<<SVR_EOF
Step 3 Add the password of the sa user into the contents mentioned previously in the two different
places.
The modified contents is shown as follows:
${SYBASE}/${SYBASE_OCS}/bin/isql -Usa
-S${ADAPTIVE_SERVER_NAME} -Pemsems<<SVR_EOF
NOTE
The file sybase_stop_servers is read-only. To modify it, run wq! to write this file effectively, and then
exit.
Step 4 Modify the file right of sybase_stop_servers.

# chmod 500 sybase_stop_servers
# chown dbuser:staff sybase_stop_servers
----End
3.3.3 Registering the Sybase into the Cluster

This section describes how to register the Sybase on only node 1.
Prerequisite
l
You have logged in to node 1 as user root.
The Sybase registration scripts reg_syb.sh and AddHacheck.sql are copied to the
directory /opt/OMC/etc/dual on node 1.
The Sybase service is started.
Issue 06 (2008-03-18)

3-9
M2000
Procedure
Step 1 Run the following command to add the operation rights for reg_syb.sh:
# chmod a+x reg_syb.sh
Step 2 Run the registration script reg_syb.sh.
# bash
# ./reg_syb.sh SYB sa the password of the user sa
Step 3 At the following prompt, type the name of the resource according to Names for M2000 HA
System Cluster Components:
Please input Resource Group name [default:oss_rg]:
Please input Disk Group Resource name [default:ossdg_rs]:
Please input Sybase Resource name [default:sybase_rs]:
NOTE
In case of a failure, you can also run the following command, and then enter information as prompted.
# ./reg_syb.sh
Step 4 At the following prompt, type y to continue:

Are you sure to continue? [y/n]:
----End
3.3.4 Checking the Registration of the Sybase

This describes how to check the registration of the Sybase. After the Sybase is registered in the
Cluster, you must check the registration to ensure that the resource can be managed by the
Cluster. This operation is performed only on node 1.
Prerequisite
Procedure
Run the scstat -g command on node 1 to check the resource status.
# scstat -g
-- Resource Groups and Resources -Group Name
Resources
--------osssvr_rs ossdg_rs sybase_rs

Group: oss_rg
3-10
Node Name
--------osssvr-1
osssvr-2

State
----Online
Offline
Issue 06 (2008-03-18)
M2000

online.
Resource: osssvr_rs
Node Name
--------osssvr-1
State
Status Message
-----------------Online
Online - LogicalHostname
osssvr-2
Offline
Offline
Resource: ossdg_rs
Resource: ossdg_rs
osssvr-1
osssvr-2
Online
Offline
Online
Offline
Resource: sybase_rs
Resource: sybase_rs
osssvr-1
osssvr-2
Online
Offline
Online
Offline
If sybase_rs is displayed, you can infer that the M2000 is successfully registered in the
Cluster.
----End
3.3.5 Activating sybase_rs

This describes how to activate sybase_rs. After the Sybase is registered and activated in the
Cluster, the Cluster monitors and manages the Sybase. This operation is performed only on node
1.
Prerequisite
l
Stop the Sybase service. For details, refer to 3.5.7 Stopping the Sybase (HA).
Procedure
Step 1 Run the following command to start monitoring the Sybase by using the Sun Cluster:
# scswitch -e -j sybase_rs
The Cluster starts the Sybase.
Step 2 Run the following command to check whether the Sybase is started:
# scstat -g
Resources
--------osssvr_rs ossdg_rs sybase_rs

Group: oss_rg
Node Name
--------osssvr-1
osssvr-2
State
----Online
Offline

online.
Resource: osssvr_rs
Issue 06 (2008-03-18)
Node Name
--------osssvr-1
State
Status Message
-----------------Online
osssvr-2

Offline
Offline
3-11
M2000

Resource: ossdg_rs
Resource: ossdg_rs
osssvr-1
osssvr-2
Online
Offline
Online
Offline
Resource: sybase_rs
Resource: sybase_rs
osssvr-1
osssvr-2
Online
Offline
Online
Offline
In such a case, the Cluster ensures that the Sybase is started and that the Sybase can be switched
to the entire M2000 resource group. In the output, if the State of sybase_rs is Online on
node 1 (osssvr-1), you can infer that the Sybase is running.
If you do not want the Cluster to monitor the Sybase, run the following command to deactivate
the monitoring:
# scswitch -n -j sybase_rs
CAUTION
In Cluster-managed HA mode, sybase_rs is monitored by the Cluster. Do not use the isql
command to stop the Sybase server.
----End
3.4 Registering the M2000 Server Application

This describes how to register the M2000 server application. After the M2000 server application
is registered on the Cluster, the M2000 server application is managed by the Cluster as the
resource. The operation is performed only on node 1.
1.
3.4.1 Installing the M2000 Registration Package

This describes how to install the M2000 registration package on node 1 and node 2.
2.
3.4.2 Registering the M2000 Server Application into the Cluster

This describes how to register the M2000 server application in the Cluster only on node 1.
3.
3.4.3 Checking the Registration of the M2000 Server Application

This describes how to check the registration of the M2000 server application. After the
M2000 server application is registered in the Cluster, you must check the registration of
the M2000 application to ensure that the Cluster can manage the resource. This operation
is performed only on node 1.
4.
3.4.4 Activating M2000 Resources

This describes how to activate the M2000 resources. After the M2000 is registered in the
Cluster and is activated, the Cluster monitors and manages the M2000. This operation is
performed only on node 1.
3.4.1 Installing the M2000 Registration Package

This describes how to install the M2000 registration package on node 1 and node 2.
Prerequisite
3-12
You have logged in to node 1 and node 2 as user root.
The M2000 registration package is copied to the directory /opt/OMC/etc/dual on node 1.

Issue 06 (2008-03-18)
M2000
Procedure
Step 1 Type the path of the M2000 registration package.
l
To install the M2000 registration package on node 1, run the following command:
To install the M2000 registration package on node 2, transfer the registration package /opt/
OMC/etc/dual/M2kPkg.tar in bin mode from node 1 to the path /tmp on node 2 through
the FTP.
Run the command ftp IP address of node 1 on node 2 and log in to node 1 as user root. Run
the following commands:
ftp> lcd /tmp
ftp> cd /opt/OMC/etc/dual
ftp> bin
ftp> get M2kPkg.tar
ftp> bye
After the files are transferred, run the following command to go to the installation directory
of node 2.
# cd /tmp
Step 2 Extract the package M2kPkg.tar on node 1 and node 2.

# tar xvf M2kPkg.tar
# cd ./M2kPkg/HWM2000/pkg
# pkgadd -d .
At the following prompt: Select package(s) you wish to process (or 'all'
to process all packages). (default: all) [?,??,q]: during the
extraction, type all, and then press Enter to continue.
At the following prompt: Do you want to continue with the installation
of <HWM2000> [y,n,?] during the extraction, type y, and then press Enter to continue.
At the following prompt: Select package(s) you wish to process (or 'all'
to process all packages). (default: all) [?,??,q]: , type q, and then
press Enter to complete the extraction and exit.
----End
3.4.2 Registering the M2000 Server Application into the Cluster

This describes how to register the M2000 server application in the Cluster only on node 1.
Prerequisite
Procedure
Run the following command on node 1 to register the M2000 server application:
# scrgadm -a -t HW.M2000
Issue 06 (2008-03-18)

3-13
M2000
# scrgadm -a -j ossapp_rs -g oss_rg -t HW.M2000 -y Scalable=false -y

Resource_dependencies=sybase_rs
# scrgadm -c -j ossapp_rs -y STOP_TIMEOUT=900
If the system does not prompt anything, you can infer that the registration is successful.
----End
3.4.3 Checking the Registration of the M2000 Server Application

This describes how to check the registration of the M2000 server application. After the
M2000 server application is registered in the Cluster, you must check the registration of the
M2000 application to ensure that the Cluster can manage the resource. This operation is
performed only on node 1.
Prerequisite
Procedure
Run the following command on node 1 to check the resource status and to check whether the
M2000 is registered successfully in the Cluster:
# scstat -g
Resources

Group: oss_rg
Node Name
--------osssvr-1
osssvr-2
State
----Online
Offline

online.
Resource: osssvr_rs
Node Name
--------osssvr-1
State
Status Message
-----------------Online
osssvr-2
Offline
Offline
Resource: ossdg_rs
Resource: ossdg_rs
osssvr-1
osssvr-2
Online
Offline
Online
Offline
Resource: sybase_rs
Resource: sybase_rs
osssvr-1
osssvr-2
Online
Offline
Online
Offline
If ossapp_rs exists is displayed, you can infer that the M2000 is successfully registered
in the Cluster.
----End
3-14

Issue 06 (2008-03-18)
M2000
3.4.4 Activating M2000 Resources

This describes how to activate the M2000 resources. After the M2000 is registered in the Cluster
and is activated, the Cluster monitors and manages the M2000. This operation is performed only
on node 1.
Prerequisite
Procedure
Step 1 Run the following commands to check all the M2000 services:
# cd /opt/OMC
# . ./svc_profile.sh
# svc_ps
If certain services are running, run the following command to stop all the M2000 services:
# stop_svc
Step 2 Run the following command to start the monitoring of the M2000 server operation through the
Cluster:
# scswitch -e -j ossapp_rs
The Cluster starts the M2000 server.
Step 3 Run the following command to check whether the M2000 is started:
# scstat -g
Resources

Group: oss_rg
Node Name
--------osssvr-1
osssvr-2
State
----Online
Offline

online.
Resource: osssvr_rs
Issue 06 (2008-03-18)
Node Name
--------osssvr-1
State
Status Message
-----------------Online
osssvr-2
Offline
Offline
Resource: ossdg_rs
Resource: ossdg_rs
osssvr-1
osssvr-2
Online
Offline
Online
Offline
Resource: sybase_rs
Resource: sybase_rs
osssvr-1
osssvr-2
Online
Offline
Online
Offline

3-15
M2000

Resource: ossapp_rs
Resource: ossapp_rs
osssvr-1
osssvr-2
Online
Offline
Online
Offline
The Cluster monitors the real-time operational status of the M2000 and ensures that the
M2000 is started. In the output, if the State of ossapp_rs is Online on node 1
(osssvr-1), you can infer that M2000 services are running.
If you do not want the Cluster to monitor the M2000 server, run the following command to stop
the monitoring process:
# scswitch -n -j ossapp_rs
CAUTION
l
In the Cluster-managed HA mode, ossapp_rs is monitored by the Cluster. Do not run the
stop_svc command to stop the M2000 server.
After you register the Sybase software and M2000 resources with the Cluster, you must stop
the M2000 and Sybase monitoring before stopping the server.
# scshutdown -g0 -y
----End
3.5 Managing Cluster Resources

This describes how to manage the cluster resource of the M2000 HA system. The process for
managing the cluster resource involves starting and stopping the Cluster monitoring resources,
the M2000 system service, and the Sybase.
3.5.1 Viewing Configured Resources
This describes how to view the configured resources.
3.5.2 Starting Cluster Monitoring on Resources
This describes how to start Cluster monitoring on resources.
3.5.3 Stopping Cluster Monitoring on Resources
This describes how to stop Cluster monitoring on resources.
3.5.4 Starting M2000 Services (HA)
This describes how to run the start_svc command to start all the M2000 services. If some
services are already started, the system starts the rest of the services.
3.5.5 Stopping M2000 Services (HA)
This describes how to run the command stop_svc to stop all the M2000 services. After all the
M2000 services are stopped, NE performance data and alarm data cannot be processed. After
the M2000 services are resumed, the M2000 updates data with the NEs and processes the updated
data.
3.5.6 Starting the Sybase (HA)
This describes how to start the Sybase for the HA system.
3-16

Issue 06 (2008-03-18)
M2000
3.5.7 Stopping the Sybase (HA)

This describes how to stop the Sybase in the HA system.
3.5.1 Viewing Configured Resources

This describes how to view the configured resources.
Prerequisite
You have logged in to the server as user root.
Procedure
Run the scstat -g command to view the resources in the oss_rg resource group.
# scstat -g
The oss_rg resource group contains osssvr, ossdg_rs, sybase_rs, and ossapp_rs.
----End
3.5.2 Starting Cluster Monitoring on Resources

This describes how to start Cluster monitoring on resources.
Prerequisite
Procedure
If a resource is not monitored by the Cluster, run the following command to start the Cluster
monitoring on the resource.
# scswitch -e -j resource name
Run the following command to enable the Cluster monitoring on the Sybase:
Run the following command to enable the Cluster monitoring on the M2000:
# scswitch -e -j ossapp_rs
NOTE
After you run the scswitch -e -j command, the corresponding resource is started. For example, after you
run the scswitch -e -j ossapp_rs command, the M2000 server is started.
----End
3.5.3 Stopping Cluster Monitoring on Resources

This describes how to stop Cluster monitoring on resources.
Prerequisite
Issue 06 (2008-03-18)

3-17
M2000
Context
The Cluster monitors all the resources in the resource group. If a resource is faulty, the Cluster
attempts to restart the resource. The Cluster switches oss_rg to the standby node if the number
of restart attempts reaches the preset value.
Procedure
Stop Cluster monitoring on the resources.
# scswitch -n -j resource name
Run the following command to stop Cluster monitoring on the Sybase:
Run the following command to stop Cluster monitoring on the M2000:
NOTE
The scswitch -n -j command helps you stop a resource. For example, after you run the scswitch -n -j
sybase_rs command, the Sybase is stopped.
CAUTION
The stopped resource cannot restart automatically after the server restarts. In this situation, you
must start the resource manually.
----End
3.5.4 Starting M2000 Services (HA)

This describes how to run the start_svc command to start all the M2000 services. If some
services are already started, the system starts the rest of the services.
Prerequisite
You have logged in to the M2000 as user root.
Procedure
To start M2000 services, run the command # scswitch -e -j ossapp_rs.
NOTE
Before starting the M2000 server, ensure that the Sybase is started. If the Sybase is not started, refer
to 17.2.2 How to Start the Sybase (HA) to start the Sybase.
The HA system takes some time to start services. Wait for ten minutes after you run the command.
----End
3.5.5 Stopping M2000 Services (HA)

This describes how to run the command stop_svc to stop all the M2000 services. After all the
M2000 services are stopped, NE performance data and alarm data cannot be processed. After
3-18

Issue 06 (2008-03-18)
M2000
the M2000 services are resumed, the M2000 updates data with the NEs and processes the updated
data.
Prerequisite
You have logged in to the M2000 as user root.
Procedure
To stop M2000 services, run the command # scswitch -n -j ossapp_rs.
NOTE
The HA system takes some time to stop the services. Wait for ten minutes after you run the command. Run
the command svc_ps | wc to monitor the service stopping progress.
----End
3.5.6 Starting the Sybase (HA)

This describes how to start the Sybase for the HA system.
Prerequisite
Procedure
Run the following command to start the Sybase:
----End
3.5.7 Stopping the Sybase (HA)

This describes how to stop the Sybase in the HA system.
Prerequisite
You have logged into the server as user root.
Procedure
Run the following command to stop the Sybase:
----End
Issue 06 (2008-03-18)

3-19

Managing Cluster Resources of The M2000 HA System: About This Chapter

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Managing Cluster Resources of The M2000 HA System: About This Chapter

Transféré par

Droits d'auteur :

Formats disponibles

M2000

HA System Administrator Guide (S10)

3 Managing Cluster Resources of the M2000 HA System