sgmgr(1m) [hpux man page]
sgmgr(1M) sgmgr(1M) NAME
sgmgr - Serviceguard Manager SYNOPSIS
filename ] | COMserver username password cluster_name ...]] COMserver2 Remarks Serviceguard Manager is the graphical user interface for Serviceguard or Serviceguard Extension for RAC software, Version A.11.12 or later, Serviceguard products are not included in the standard HP-UX operating system. DESCRIPTION
The command starts Serviceguard Manager, the graphical user interface for Serviceguard clusters. Serviceguard Manager can be installed on HP-UX, Linux, or Windows. Serviceguard Manager can be used to view saved data files of a single cluster, or to see running clusters. To see the "live" cluster map, Serviceguard Manager connects to a Serviceguard node on the same subnet as those clusters, specifically to a part of Serviceguard called the Cluster Object Manager (COM). Options supports the options listed below. No options are required. If any option is not specified, the user will be prompted to supply it after the interface opens. Open a previously saved or example object data file. The file will have the .sgm extension. It can display only one cluster. This option cannot be used with any other options. Specify the Serviceguard node that will be the server. This node's COM will query cluster objects running on its subnets, and will report their status and configuration. Servers with Serviceguard Version A.11.12 or later can monitor clusters. Servers with Ser- viceguard Version A.11.14 or later can also perform administrative actions. Servers with Version A.11.16 or later can also configure clusters. To specify multiple sessions, repeat the -s option. The user login name for the COMserver node. Valid only if COMserver is specified. The user password on the COMserver node. Valid only if username is specified. In creating the map, the COMserver will include the cluster where it is a member. In creating the map, the COMserver will report information about the specified cluster_name(s). Specify clusters with the following cluster software installed: MC/Serviceguard Version A.10.10 or later, MC/LockManager Version A.11.02 or later, Serviceguard OPS or Extension for RAC Version A.11.08 or later, and all versions of MetroClusters and ContinentalClusters. To see several clusters, repeat the -c option. If you specify this unused nodes option all COMservers will report information about nodes that have Serviceguard installed, but are not currently configured in any cluster. To connect to another COMserver for another session, repeat the -s options. AUTHOR
was developed by HP. SEE ALSO
See documents at http://docs.hp.com/hpux/ha including: Managing Serviceguard. Configuring OPS Clusters with Serviceguard OPS Edition. Using Serviceguard Extension for Real Application Cluster (RAC). Series 700 or 800 Works with Optional Serviceguard or Serviceguard Extension for RAC Software sgmgr(1M)
Check Out this Related Man Page
cmmigratepkg(1m) cmmigratepkg(1m) NAME
cmmigratepkg - Migrate Serviceguard legacy Package to a Module Package. SYNOPSIS
cmmigratepkg -p package_name [-x extern_script] [-e] [-s] -o output_filename DESCRIPTION
cmmigratepkg is used to generate a modular package configuration file from a configured legacy package. cmmigratepkg expects the package to be a configured legacy package. The package can be up or down and the cluster can be on-line or off-line. The utility reads the control script of the package, so the package's control script must be located on the node where the command is run. cmmigratepkg can migrate packages created by Serviceguard version A.11.09 through A.11.18. The control script's customer-defined area is any code between "#START CUSTOMER DEFINED FUNCTIONS" and "#END CUSTOMER DEFINED FUNCTION. If the customer-defined area has code that needs to be migrated to the modular package then cmmigratepkg can create an external script by inserting the shell code from the control script into the external_script file. The external script is generated from the external template found in $SGCONF/examples/external_script.template. (See chapter 4 of the Managing Serviceguard manual for more information about the tem- plate.) The external_script_name is the full pathname and file name of the file. The extexternal scriptfile must be copied to each node where the package can run and make sure that the permissions are set to 744, and owned by root. Non-Serviceguard variables defined in the legacy package control script can be converted to user defined parameters called PEV, parameter environment variable. The PEV is defined in the package configuration file and has a prefix of "PEV_". See description under the -e option. The cmmigratepkg displays informational message about the variables which it cannot convert because they are non-Serviceguard variables. If these non-Serviceguard variables are used and defined in the customer defined area then there is no need to convert them to PEV. If they are defined in another location in the control script, and the values should be part of the package, they can be converted to PEV using the -e option. The PEV are defined in the new package configuration file. If non-Serviceguard functions are defined in the legacy package control script, cmmigratepkg lists the non-Serviceguard functions to STD- OUT. These functions are not converted. You must determine if the functions are called and how you want to migrate them to the modular package. You can put them into the new external script file. cmmigratepkg converts legacy failover packages that are configured with: Services, File Systems, Volume groups, Dependencies, EMS Resources, and User Defined Roles to modular packages. cmmigratepkg generates the modular package configuration file in lowercase. The package configuration file has no comments about the pack- age attributes. If the user wants to see comments regarding the package attributes, they can generate a temporary package configuration file using cmmakepkg -v. The following control script parameters are obsolete and the cmmigratepkg gives a warning about them not be able to convert: RAIDSTART, RAIDSTOP, RAIDTAB, MD, GFS, DATA_REP, and DTC_NAME. Note: that cmmigratepkg will not convert CVM3.5 packages or CFS packages. If you are converting packages please see the White paper for more details aboutconverting legacy packages. Options cmmigratepkg supports the following options: -p package_name Name of an existing configured legacy package to convert. -x external_script Name of the external script file to create. -e Generate PEV's from non Serviceguard parameters. All non Serviceguard parameters found in the package control script are con- verted to PEVs. "PEV_" is prepended to the original name. For example, package_root="/srv/colossus", is written as PEV_pack- age_root="/srv/colossus" in the output_file. -s This option comments out service attributes in the output_file. A warning is displayed when the option is used and the package has services defined. When using this option the user should review the output file. -o output_file Name of the output file for the converted package configuration. RETURN VALUE
cmmigratepkg returns the following values: 0 Successful completed. >0 Command failed. EXAMPLES
Converts pkgA writing out new package configuration file. cmmigratepkg -p pkgA -o /etc/cmcluster/pkg/pkgA/pkgA.conf Converts pkgA and also generates an external script. cmmigratepkg -p pkgA -x /etc/cmcluster/pkg/pkgA/external.sh -o /etc/cmcluster/pkg/pkgA/pkgA.conf" AUTHOR
cmmigratepkg was developed by HP. SEE ALSO
cmmakepkg(1m), cmgetconf(1m) Migration White Paper. Requires Optional Serviceguard Software cmmigratepkg(1m)