Configuring sqlserver Resources
3. Select online - NETNUMENCLUSTER1
4. Start Sqlserver database on NETNUMENCLUSTER1.
5. Mount the NM installation path N:\ NETNUMEN on NETNUMENCLUSTER1. Then, start configuring NM server.
To configure NM server, perform the following steps:
1. Initialize NM server database.
Run
N:\NETNUMEN\ums-svr\docs\dbscript\install-db\uep\install.bat to initialize NetNumen N31 NM server database.
2. Perform system configurations on NM server.
For detailed configurations, refer to the Figure 230 section.
This section just introduces settings, which have influence on NM server startup, including:
f NM server startup parameter i. Run
N:\NETNUMEN\ums-svr\output\tools\configcenter\bin\ run.bat to start NM configuration center tool, as shown in Figure 230.
FI G U R E 2 3 0 −NE TNU M E N N M CO N F I G U R A T I O N CE N T E R
ii. Set database IP address connected to NM server. Here, the IP is the floating IP and Sqlserver database, 10.40.88.14. Select test connection and optimization configuration.
iii. Test connection: Test whether it is possible to connect Steps
Chapter 4 VCS4.3 for Windows
iv. Optimization configuration: Optimize the database automatically (mainly for SQL Server database), including set backup mode to be Simple, cleaning database log and compressing log.
Note: Switch Sqlserver database over to NETNUMENCLUSTER2.
Start NM configuration center. Select optimization configuration to optimize Sql server database attributes on NETNUMENCLUSTER2.
f Server multiple IP addresses setting
For dual systems, the server has multiple IP addresses. It is required to perform the below settings:
Modify the following parameters in the ‘\ums-svr\netnumen\ip\dsl\dsl-base.par\conf\IPMS_param.xml’
file.
<FTP_PARAMETERS
FTPIPAddress="localhost" />
Change FTPIPAddress="localhost to be the NM IP address with which NE can use ftp.
END OF STEPS
It is successful to start NM server on both computers.
Normally, it is successful to start NM server on NETNUMENCLUSTER1. Close the NM server. Uninstall N:\NETNUMEN from NETNUMENCLUSTER1. Mount N:\NETNUMEN to NETNUMENCLUSTER2. It is also successful to start NM server on NETNUMENCLUSTER2.
Add NM server resources in VCS.
Select Start Æ Programs Æ VERITAS Æ VERITAS Cluster Manager Æ Java Console to open VCS management interface as shown in Figure 223.
NM server-related resources contain:
NM server resource group (nms-grp)
Disk group resource (VMDg)
Share disk resource (MountV) Result
Follow-up Action
Prerequisite
Resources
i. Right click on zte-clu as shown in Figure 226. Select Add Service Group. Add Service Group window appears as shown in Figure 231.
FI G U R E 2 3 1 −AD D SE R V I C E GR O U P
ii. Input nms-grp in the Service Group name text box.
Select NETNUMENCLUSTER1 and NETNUMENCLUSTER2.
Check Startup. Click OK. NM resource group (nms-grp) is created as shown in Figure 232.
FI G U R E 2 3 2 −CR E A T I N G N M RE S O U R C E GR O U P (N M S-G R P)
Chapter 4 VCS4.3 for Windows
group nms-grp (AutoStartList = { NETNUMENCLUSTER1, NETNUMENCLUSTER2})
AutoStartList decides on which system nms-grp runs in priority when both systems are restarted. In this instance, nms-grp runs on NETNUMENCLUSTER1 in priority. The setting is contrary to AutoStartList for sqlserver-grp resource, ensuring that sqlserver database and NM server run on different systems by default.
The value for AutoStart is true.
It indicates that when the system is started, nms-grp enabled automatically.
2. Add VMDg resource to nms-grp.
Right click on nms-grp in Creating NM Resource Group (nms-grp) interface as shown in Figure 232. Select Add Resource. Add Resource window appears as shown in Figure 233.
FI G U R E 2 3 3 − AD D RE S O U R C E
Select VMDg for Resource Type. Input nms-grp-VMDg in Resource Name. Set the value of DiskGroupName to be nms-dskgrp. Set the value of DGGuid. Select Critical and Enabled. Then, click OK.
DGGuid is the unique ID of disk group in disk array. It is Related
Information
FI G U R E 2 3 4 −RU N N I N G
ii. Click OK to open the dos window. Execute the vmgetdrive command in dos window. The VMDriveInfo.txt file is created under the directory (here, it is d:) as shown in Figure 235.
FI G U R E 2 3 5 −CR E A T I N G V M DR I V EIN F O.T X T FI L E
iii. Open the d:\ VMDriveInfo.txt file as shown in Figure 236.
Chapter 4 VCS4.3 for Windows
FI G U R E 2 3 6 − D: \ V M DR I V EIN F O.T X T
iv. Find the DiskGroup GUID value corresponding to DiskGroup Name = nms-dskgrp disk group. Copy it to nms-grp-VMDg resource as DGGuid value.
Result: The nms-grp-VMDg resource is shown in Figure 237.
FI G U R E 2 3 7 − N M S-G R P- V M DG RE S O U R C E
3. Add share disk resource (MountV).
i. Right click on nms-grp in the nms-grp-VMDg Resource interface as shown in Figure 237.
ii. Select Add Resource. Select MountV for source type.
Input nms-grp-MountV for resource name.
iii. Input share disk information of NM program as follows:
f MountPath = "N:"
f VolumeName = nms-data
f VMDGResName = nms-grp-VMDg
f ForceUnmount = ALL
f AutoFSClean = 1 iv. Click OK.
Result: nms-grp-MountV resource is added as shown in Figure 238, nms-grp-MountV resource is in blue, indicating normal running.
FI G U R E 2 3 8 − N M S-G R P- MO U N TV RE S O U R C E
4. Add network interface card resource
Both NM programme and Sqlserver database share the same network interface card. The network interface card resource is added in sqlserver resource group. It is required to create a Related
Information
Chapter 4 VCS4.3 for Windows
i. Right click on nms-grp in the nms-grp-VMDg Resource interface as shown in Figure 237.
ii. Select Add Resource.
iii. Select Proxy for resource type. The resource name is proxy NIC. Select Enable. Edit TargetResName to be grp-NIC, the NIC resource name in sqlserver-grp.
iv. Click OK.
Result: Adding proxy_NIC resource is complete as shown in Figure 239, proxy_NIC resource is in blue, indicating normal running.
FI G U R E 2 3 9 − P R O X Y_ N I C RE S O U R C E
5. Add virtual IP resource.
This IP resides on the computer which provides NM service.
Whatever NM server runs, there is only one IP address.
i. Right click on nms-grp the nms-grp-VMDg Resource interface as shown in Figure 237.
ii. Select Add Resource.
iii. Select IP for resource type.
iv. Input nms_IP for resource name. Property settings for nms_IP are the same as those of sqlserver-grp-IP of sqlserver-grp resource group. For subnet mask and MAC address, refer to sqlserver-grp-IP property setting.
Modify IP to be 10.40.88.44, the virtual IP of NM server.
Select Enabled.
Properties for IP nms-IP are:
Related Information
Result: Adding nms_IP resource is complete.
6. Add NM program resource.
To implement VCS monitoring and management on NM program, it is required to add NM server to VCS resource group as program resource.
Make preparations below:
i. Configure required parameters. Ensure it is possible to start NM system manually.
ii. Copy N:\NETNUMEN\ums-svr\output\tools\cluster to C:\cluster\cluster. Copy N:\NETNUMEN\ums-svr\output\jdk-windows to C:\cluster\jdk-windows.
iii. Modify NM-related scripts. Modify moni_win.bat and offline_win.vbs under N:\NETNUMEN\ums-svr\output\tools\cluster\ as needed.
For moni_win.bat, modify two paths. Copy jdk-windows to C:\Cluster\jdk-windows. moni_win.bat is under C:\Cluster\cluster. The absolute path for moni_win.bat is:
set JDK_HOME=C:\cluster\jdk-windows set MONI_HOME=C:\cluster\cluster
For offline_win.vbs, modify NM platform startup absolute path to be executable path. For instance, the NM programme is in N:\NETNUMEN\ums-svr. Modify the path to be:
if ps.executablepath = "N:\NETNUMEN\jdk-windows\bin\java.exe" then
Script for moni_win.bat is:
@echo on
rem ---
rem monitor ums Script on cluster for Win32
rem
Chapter 4 VCS4.3 for Windows Script for offline_win.vbs is
for each ps in getobject _
("winmgmts:\\.\root\cimv2:win32_process").instances_
If ps.name = "java.exe" Then
if ps.executablepath = "N:\NETNUMEN\jdk-windows\bin\java.exe" then
wscript.echo ps.terminate end if
End If
'wscript.echo
ps.handle&vbtab&ps.name&vbtab&ps.executablepath Next
iv. Set NM configuration file
For parameters in NM configuration file of ums-
svr\platform\psl\ext-service\console\conf\maincontroller.xml, it is recommended to set them to be 1. In this way, the console interface may pop up, for viewing NM status conveniently.
<! – Whether the console has interface or not. The parameter is set to be an integer. 1 – With interface, 0 – Without interface>
<client-type>1</client-type>
Run ums-svr\bin\ console.bat to start the console with interface manually. Select Start automatically while starting the console, as shown in Figure 240. Then, close console. When VCS starts console, console will start NM
FI G U R E 2 4 0 −U M S N MPL A T F O R M SE R V E R CO N S O L E
v. Copy NM-related scripts to dual systems.
Perform operations below on both systems.
Create a cluster directory in C:\.
Copy N:\NETNUMEN\ums-svr\tools\cluster to C:\cluster\cluster.
Copy N:\NETNUMEN\ums-svr\jdk-windows to C:\cluster\jdk-windows.
vi. Add NM resource.
Right click on nms-grp in the nms-grp-VMDg Resource interface as shown in Figure 237. Select Add Resource to add NM resource. Select Process for resource type.
Input NETNUMEN for resource name as shown in Figure 241.
FI G U R E 2 4 1 −AD D N MRE S O U R C E
Chapter 4 VCS4.3 for Windows
InteractWithDesktop: Set InteractWithDesktop to be True.
StartProgram: Set StartProgram to be absolute path of NM starting file, for instance, N:\NETNUMEN\ums-svr\bin\console.bat.
StopProgram: Set StopProgram. The stop script is VBS file. It is required to set command line: cscript /H:Cscript /NOLOGO C:\cluster\cluster\offline_win.vbs.
MonitorProgram: Set MonitorProgram. Monitor programme monitors the absolute path of NM monitor script. Here, it is C:\cluster\cluster\ moni_win.bat.
Select Process Æ show all attribute Æ restartlimit.
Set the restart limit to be 3. Start the current system for three times. If it still fails, switch over to another system as shown in Figure 242.
FI G U R E 2 4 2 − SE T RE S T A R TLI M I T T O B E 3
Result: The configured NM program resource is shown in Figure 243.
FI G U R E 2 4 3 −N M PR O G R A M M E RE S O U R C E
Add relationship.
Select nms-grp. Select the Resource tab. Click link to add relations between resources. This relationship chart is very important. VCS decides starting and exiting sequence according to the chart as shown in Figure 244.
FI G U R E 2 4 4 −AD D I N G RE L A T I O N S H I P
Test nms-grp, including two items below:
Make sure all resource settings are available after resources are added in nms-grp. If the resource is grey, select it. Right Follow-up
Action
Chapter 4 VCS4.3 for Windows
system can run on NETNUMENCLUSTER1 (or NETNUMENCLUSTER2). Select nm-grp resource. Right click on it. Select switch to - NETNUMENCLUSTER2 (NETNUMENCLUSTER1). The NM system can switch to another system.
END OF STEPS
NetNumen N31 NM group resources (nms-grp) configuration is complete.
Establish relationship between sqlserver-grp and nms-grp.
To establish the relationship sqlserver-grp and nms-grp, ensuring that NM server can start normally after NM-related resources are started.
To establish relationship between sqlserver-grp and nms-grp, perform the following steps:
1. Select cluster: zte-clu in VCS management interface. Select the Service Group tab as shown in Figure 245.
FI G U R E 2 4 5 − SE R V I C E GR O U P
2. Click link. Link Service Groups window appears as shown