PRIMECLUSTER Installation and Administration Guide4.5

6.11.2 Notes on Configuration

Do not use reserved words for userApplication names and Resource names

If you use a reserved word for a userApplication or Resource name, RMS cannot be configured properly.

Do not use the following reserved words in addition to numbers and types of characters limited in this manual.

<List of reserved words>

Reserved words written in C

 auto|break|case|char|const|continue|

 default|do|double|else|enum|extern|float|

 for|goto|if|int|long|main|register|return|short|

 signed|sizeof|static|struct|switch|typedef|

 union|unsigned|void|volatile|while

Reserved words written in C++

 and|and_eq|bitand|bitor|compl|not|or|or_eq|xor|xor_eq|

 asm|catch|class|delete|friend|inline|new|operator|private|

 protected|public|template|try|this|virtual|throw

Reserved words within RMS

 ADMIN|ADMIN_MODIFY|CONTRACT_MODIFY|ENV|ENVL|INIT_NODE|Offline|

 Faulted|Online|Standby|Warning|SysNode|andOp|

 assert|commdNode|contractMod|controller|env|envl|gResource|node|

 object|orOp|userApp|userApplication|ScalableCtrl

 abstract|attach|attribute|begin|class|consume|copy|cpp|declare|

 delay|delete|error|extends|extern|hidden|implements|include|

 interface|java|left|lookahead|lr|message|modify|nonassoc|node|

 nosplit|notree|package|prec|private|public|reductor|repeat|right|

 select|show|simple|skip|state|tree|trigger|type|used|virtual|wait|link

Register all Resources created by the userApplication Configuration Wizard to userApplication

When setting a cluster application, if Resource that does not belong to userApplication exists, RMS does not run. After registering all created Resources to userApplication, check that the icon of the config does not turn red.

Before using the userApplication Configuration Wizard, calculate the necessary heap memory size

If the size is more than 64 MB after the calculation, take the following actions:

• If the necessary heap memory size is 65 to 1024 MB

  Set the necessary heap memory size to Java VM used in the Web-Based Admin View client.

  However, Web-Based Admin View may not be connected when the heap memory size that was specified at Java VM startup were not secured after specifying the necessary heap memory size. In this case, take the action of "If the necessary heap memory size is more than 1024 MB" to reduce the necessary heap memory size.

  The maximum value of the heap memory size that can be connected to Web-Based Admin View depends on the memory volume that is installed in a client, and also depends on the memory status.

• If the necessary heap memory size is more than 1024 MB

  If multiple resources with the same Resource type exist in a single userApplication, take the following action to reduce the necessary heap memory size to less than 1024 MB. If the resource is not described in the following action, no action is required. If the necessary heap memory size is more than 64 MB after taking the action, set the necessary heap memory size to Java VM that is used by the Web-Based Admin View client.

  • Gds resource

    Register only one Gds resource to a single userApplication.
    When creating a Gds resource on the Select Disk Class screen, add all the disk classes to be registered in a single userApplication from Available disk class to create a Gds resource.
    For details, see "6.7.1.3 Creating Gds Resources."

  • Gls resource

    Register only on Gls resource to a single userApplication.
    When creating a Gls resource on the Select takeover IP address screen, add all the takeover IP addresses to be registered in a single userApplication from Available takeover IP address to create a Gls resource.

  • Line switching unit resource (unavailable in the Oracle Solaris 11 environment)

    Register only one line switching unit resource to a single userApplication.
    When creating a line switching unit resource on the Set up Resource screen, add all the line switching unit resources to be registered in a single userApplication by adding resources from AdditionalResource to create a line switching unit resource.
    For details, see "6.7.1.8 Creating Line Switching Unit Resources."

  • Procedure resource of Netcompo product

    Assign a startup order to all resources for each Netcompo product to be registered in a single userApplication. The order is optional.
    Assign a startup order on the Associate resources screen, This screen is displayed by pressing the SubApplication button on the "Confirm registration" screen when creating a resource of Netcompo product.
    Below is the setting example.

    If there are five procedure resources of Netcompo product

    Procedure resource name of Netcompo product	Procedure resource name of Netcompo product set to SubApplication
    netcompo0	Not set
    netcompo1	netcompo0
    netcompo2	netcompo1
    netcompo3	netcompo2
    netcompo4	netcompo3

    For details, see "6.7.1.6 Creating Procedure Resources."

    Note

    When the startup order is assigned to a procedure resource of Netcompo product, add the processing time of each procedure resource of Netcompo product to the startup time of userApplication.

The necessary heap memory size is calculated with the following procedure:

1. Calculate the total number of nodes, applications, and resources displayed on the userApplication Configuration Wizard screen.

   1. Create the following table for each userApplication.
      Input the number of each resource to be embedded to userApplication to "Number of resources" in the table below. If there is no resource, input 0.

      Number of resources	Factors of formula	Resource type
      		Cmdline Controller Nwcl NetWorker Nwst NetWorker Nwsv NetWorker Procedure(Application) Procedure(BasicApplication) Symfoware Oracle Procedure(SystemState3) Procedure(SystemState2) FNA1_FSUNvcph FNA2_FSUNvcp FNALAN_FSUNlndfc BCLine_FSUNbcdr Ims Patrol SH_SWLine Gls Ipaddress Fsystem Gds

      Note

      If the startup priority has been set to resources of the same type such as Cmdline or Procedure, the resources become the parent-child relationship. Therefore, modify the table.

      Example: when setting the startup priority to the following Procedure(BasicApplication) to be called sequentially from the top

      IS_INTERSTAGE
      OTS_RMP_INTERSTAGE
      ES_INTERSTAGE

      Number of resources	Coefficient of formula	Resource type
      		Cmdline Controller Nwcl NetWorker Nwst NetWorker Nwsv NetWorker Procedure(Application) Procedure(BasicApplication) <- ES_INTERSTAGE Procedure(BasicApplication) <- OTS_RMP_INTERSTAGE Procedure(BasicApplication) <- IS_INTERSTAGE Symfoware Oracle Procedure(SystemState3) Procedure(SystemState2) FNA1_FSUNvcph FNA2_FSUNvcp FNALAN_FSUNlndfc BCLine_FSUNbcdr Ims Patrol SH_SWLine Gls Ipaddress Fsystem Gds

   2. Delete the line if the number of resources is 0 from the table created in step a.
      Next, input the coefficient of formula to each line like R0, R1, R2, .... sequentially from the first line.

   3. Calculate the total number of resources to be displayed for each application.
      It is calculated using the following formula.

      The total number of resources for each application = Node * ( 1 + R0 + R0*R1 + R0*R1*R2 + ... )

      Node         : Number of nodes
      R0,R1,R2,... : Number of resources corresponding to the coefficient of formula in the table

   4. The total number of resources to be displayed are calculated by adding the number of applications to the total number of resources that was calculated for each application.

      The total number of resources to be displayed = the total number of resources calculated for each application +
                                 Node * The number of applications

2. Calculate the necessary memory volume.

   Calculate the necessary memory volume from the total number of resources that was calculated in step 1 using the following formula.

   The necessary memory volume [MB] = 0.111 [MB] * Total number of resources [Number] + 9.0 [MB]

   Example: when the total number of resources calculated in step 1 is 1620

   The necessary memory volume [MB] = 0.111 * 1620 + 9.0 = 188.82 [MB]

Set the necessary heap memory size for JavaVM of a client using the following procedure:

1. Right-click the shortcut of the Java application (PRIMECLUSTER Web-Based Admin View Startup) and open the properties.

2. Edit "Target" of the "Shortcut" tab to specify the "-Xmx" option right after the "javaw" command.

   To set the "-Xmx" option, specify the maximum size of Java heap memory in bytes.

   The specified value must be more than 2 MB. The default value is 64 MB.

   Example of specifying the maximum Java heap memory size (when setting 189 Mbyte):

   -Xmx189m

   Example of setting "Target" parameter of the shortcut tab (set as follows without line break):

   "C:\Users\[User name]\AppData\Local\Programs\PRIMECLUSTER Web-Based Admin View Startup\bin\javaw.exe"
   -Xmx189m -jar "WVStartup.jar" "10.20.30.40" "8081"

Example

Example for calculating heap memory size

Below explains the examples of embedding resources when there are two nodes (uAp_0) and when there are two userApplications (uAp_1).

uAP_0
  Cmdline                     4 [Number]
  Procedure(Application)      8 [Number]
  Procedure(BasicApplication) 8 [Number]
  Fsystem                     2 [Number]

uAP_1
  Cmdline                     1 [Number]
  Procedure(Application)      1 [Number]

1. Create a table.

   uAP_0

   Number of resources	Factors of formula	Resource type
   4 0 0 0 0 8 8 0 0 0 0 0 0 0 0 0 0 0 0 0 2 0		Cmdline Controller Nwcl NetWorker Nwst NetWorker Nwsv NetWorker Procedure(Application) Procedure(BasicApplication) Symfoware Oracle Procedure(SystemState3) Procedure(SystemState2) FNA1_FSUNvcph FNA2_FSUNvcp FNALAN_FSUNlndfc BCLine_FSUNbcdr Ims Patrol SH_SWLine Gls Ipaddress Fsystem Gds

   uAP_1

   Number of resources	Factors of formula	Resource type
   1 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0		Cmdline Controller Nwcl NetWorker Nwst NetWorker Nwsv NetWorker Procedure(Application) Procedure(BasicApplication) Symfoware Oracle Procedure(SystemState3) Procedure(SystemState2) FNA1_FSUNvcph FNA2_FSUNvcp FNALAN_FSUNlndfc BCLine_FSUNbcdr Ims Patrol SH_SWLine Gls Ipaddress Fsystem Gds

2. Delete the lines if the number of resources is 0 from the table created in example 1.

   uAP_0

   Number of resources	Factors of formula	Resource type
   4 8 8 2	R0 R1 R2 R3	Cmdline Procedure(Application) Procedure(BasicApplication) Fsystem

   uAP_1

   Number of resources	Factors of formula	Resource type
   1 1	R0 R1	Cmdline Procedure(Application)

3. Assign each coefficient to each formula.

   uAp_0
   2(node) * ( 1 + 4(Cmdline) 
                 + 4(Cmdline) * 8(Proc)
                 + 4(Cmdline) * 8(Proc) * 8(Proc)
                 + 4(Cmdline) * 8(Proc) * 8(Proc) * 2(Fsystem) )
   = 1610
   
   uAp_1
   2(node) * ( 1 + 1(Cmdline)
                 + 1(Cmdline) * 1(Proc)
   = 6

4. Calculate the total number of resources.
   

   1610 (Number of resources for uAp_0)
   +
   6    (Number of resources for uAp_1)
   +
   4    (Number of resources for userApplication)
        (It is four because two applications exist in two nodes)
   = 1620