Page tree
Skip to end of metadata
Go to start of metadata

Use the mcrtcell command to create a new cell. You can run the mcrtcell command only on the local computer where you are creating the new cell.

Cell names

Cell names must be unique throughout the enterprise.

Warning

  • Cells with identical cell names on different computers within your enterprise will cause unexpected results.
  • Cell names must comprise only ASCII characters.

Cell names are case-sensitive for UNIX operating systems, but are not case-sensitive on Microsoft Windows.

The cell name cannot contain spaces or special characters. You can use any alphanumeric string and underscores (_) in a cell name, such as the following:

  • my_cell 
  • spike12 
  • oracle

Do not give a cell the same name as any item in the installationDirectory/pw/server/etc directory, such as the KB directory or the mcell.conf, mcell.dir, or mcell.trace files.

Using the mcrtcell command to add cells ensures that the cell names are unique.

Tip

When naming cells, adopt a naming convention for test and production cells that clearly identifies its purpose. For example, you could assign test cells names that use test as a prefix or suffix. A clear naming convention is important because in the console views, there is no way to distinguish test and production cells other than by the cell name.

mcrtcell actions

The mcrtcell command performs the following actions:

  • Determines whether an entry exists in the mcell.dir file that matches the cell being created
    If a matching entry exists, the creation fails. You can use the -fc option to force the creation of the cell. If you use the -fc option alone, only the cell configuration and Knowledge Base files are re-created. If you use the -fc option with the -ba or the -bm option, the cell's service (Windows) or boot script (UNIX) also is re-created. If only the service or boot script needs to be re-created, you can use the -fb option with the -ba or the -bm option. 
  • Creates the etc\CellName directory, which contains a Knowledge Base copied from the etc\default\kb directory 
  • Creates a services entry on Microsoft Windows if you specify the -ba or -bm option with the -r, -r1, or -r2 option 
  • Creates boot scripts on UNIX if the -ba or the -bm option is specified with the -r, -r1, or -r2 option 
  • Adds an entry to the local mcell.dir file 
  • When the-ba or -bm option is used without the -r, -r1, or -r2 option, an installation script specific to the new cell is created. This script is located in the installationDirectory/pw/server/etc/NewCellName directory and is named mcrtsvc_NewCellName.cmd on Windows and mcrtsvc_NewCellName.sh on UNIX. When invoked, the script creates the corresponding services entry on Windows or the boot files on UNIX.

UNIX boot files

If you run mdelcell CellName, all of these files are automatically removed.

Boot files created for UNIX when -ba or -bm are used

Platform

Boot file

Symbolic link (created for -ba only)

AIX

etc/rc.d/init.d/mc_cellName

  • /etc/rc.d/rc2.d/S98mc_cellname
  • /etc/rc.d/rc2.d/K02mc_cellname

HP-UX

/sbin/init.d/mc_cellName

  • /sbin/rc2.d/K99mc_cellName
  • /sbin/rc2.d/S99mc_cellName

UNIX or Linux

/etc/init.d/mc_cellname

  • etc/rc2.d/K99cellName
  • etc/rc2.d/S99 cellName

Linux

/etc/init.d/mc_cellname

  • /etc/rc.d/S99mc_cellName
  • /etc/rc.d/K99mc_cellName


* = 2, 3, 4, and 5 for a total of 8 symbolic links.

After you configure the cell, you must stop and restart it for the changes to take effect. For instructions, see Starting or stopping the cell.

mcrtcell syntax

mcrtcell [-h|?] [-z] [-q] [-v] [-c <ConfigFile>] [-l <HomeLocation>]
-n <NewCell> -@ <host1>[</port1>][,<host2>[/<port2>]][#<key>]
{-aa|-ae|-as|-ap} [-s <SourceCell>] {-bn|-bm|-ba} {-fc|-fb} [-d
<ServiceDisplayName>] {-r|-r1|-r2}

If you do not specify the -aa, -ae, -as, or -ap option, you create a cell with an empty Knowledge Base, and the cell does not respond to requests.

When -ba or -bm is used with accompanying -r, -r1, or -r2 options, the installation script for the new cell's service or boot script is generated underinstallationDirectory/pw/server/etc/NewCell.

The following table lists the command-specific options for mcrtcell. For a list of common command options that apply to all CLI commands, see Event management common command options.

mcrtcell options

Option

Description

-n NewCell

Specifies the name for the cell being created. For information about cell naming conventions, see Cell names.

-@ host1[/port1][,host2[/port2]][#key]

New cell host name with optional port and encryption key
Optionally, you can define a secondary host name and port for the new cell. If you do not specify a port, the default is 1828. If you do not specify an encryption key,  "mc" is taken as the default encryption key.

-aa

Creates a cell that has the Admin Knowledge Base and configuration

-ae

Creates a cell that has the Event Management Knowledge Base and configuration

-as

Creates a cell that has the Service Impact Management Knowledge Base and configuration

-ap

Creates a cell that has the ProactiveNet Operations Manager Knowledge Base and configuration

-s SourceCell

Specifies the cell (SourceCell) from which to copy a Knowledge Base

-bm

On Windows, configures a service for the cell with a Manual startup type. On UNIX, creates the boot script to start the cell after the UNIX server on which it resides is rebooted.

-bn

Configures the cell so that it must be manually restarted after the host is rebooted. No service or boot script is created.

-ba

On Windows, configures a service for the cell with an Automatic startup type. On UNIX, creates the boot script to start the cell after the UNIX server on which it resides is rebooted. Also creates the symbolic links to the boot script required for autorestart on system boot.

-fc

Forces a re-creation of the configuration and knowledge base files of the cell, but does not re-create the service or boot script, unless the -bm or -ba option is used.

Note

You can use this option whether or not NewCell exists.

-fb

If NewCell already exists, forces a re-creation of the service (Windows) or boot script (UNIX) of the cell, but not the configuration and Knowledge Base files.

Note

NewCell must exist to use this option. Also, this option must be used in conjunction with -ba or -bm.

-d

(Windows only) Specifies a display name for the service

Note

If a ServiceDisplayName is not supplied, and -bm or -ba is specified, the display name will be the same as the service name.
If -d is used on UNIX, a syntax error will occur.

-r

Immediately sets up cell for restart at reboots as a non-high-availability cell (requires Administrator/root privileges)

-r1

Immediately set up cell for restart at reboots as a high-availability cell on the primary server

-r2

Immediately set up cell for restart at reboots as a high-availability cell on the secondary server

mcrtcell examples

The following example creates cell newcell by copying the configuration and Knowledge Base files from the existing cell, othercell. The service (Windows) or boot script (UNIX) is set up during this mcrtcell invocation. If you use this command, the cell service must be started manually (as specified by the -bm option).

Example of mcrtcell where the configuration and Knowledge Base are copied from an existing cell

mcrtcell -n <newcell> -@ houper.bmc.com/8501#mc -s <othercell> -bm -r

The following example re-creates the service or boot script for an existing cell, mycell, without touching the cell's existing configuration and Knowledge Base files. If you use this command, the cell service will be started automatically.

Example of mcrtcell where the service and boot script are re-created for an existing cell

mcrtcell -n <mycell> -fb -ba -r

The following example for Windows re-creates only the service for existing cell mycell by giving it "BMC Cell mycell", as the display name.

Example of mcrtcell where the service is created for an existing cell and a display name is specified

mcrtcell -n <mycell> -fb -ba -r -d "BMC Cell <mycell>"

The following example re-creates only the service or boot script for existing cell mycell. If the mcell.dir entry for mycell does not match the @ information provided, it also updates the mcell.dir entry with the new @ details.

Example of mcrtcell where the service or boot script is created and the mcell.dir entry for the cell is updated if necessary

mcrtcell -n <mycel>l -@ houper.bmc.com/8502 -fb -ba -r


The following example re-creates the configuration and Knowledge Base files for cell testcell. It creates the installation scripts installationDirectory/pw/server/etc/testcell/mcrtsvc_testcell.cmd (Windows) or installationDirectory/pw/server/etc/testcell/mcrtsvc_testcell.sh (UNIX). The service or boot script will not be created at the time of this mcrtcell invocation, but will be created or re-created after running the installation script. The installation script for this cell does not take any arguments. 

Example of mcrtcell where installation scripts are created so that the configuration and Knowledge Base files for the cell are re-created after the installation script is executed

mcrtcell -n <testcell> -as -@ houper.bmc.com/8503#mc -fc -bm

The following example re-creates the configuration and Knowledge Base files for cell testcell. It does not create or re-create the service or boot script. 

Example of mcrtcell where only the Knowledge Base and configuration files are re-created

mcrtcell -n <testcell> -ae -@ houper.bmc.com/8503#mc -fc

The following example re-creates the configuration and Knowledge Base files for cell testcell. It also creates or re-creates the service or boot script. 

Example of mcrtcell where the Knowledge Base files, configuration files, and the service (Windows) or boot script (UNIX) are re-created

mcrtcell -n <testcell> -as -@ houper.bmc.com/8503#mc -fc -ba -r

The following example creates a high-availability cell, hacell, on the primary server, eagle.bmc.com. The mcell.conf file for hacell on the primary server must be edited manually so that CellDuplicateMode=1. The service or boot script is created during this mcrtcell invocation. The service or boot script explicitly will refer to hacell on the primary server as hacell#1.

Note

This mcrtcell invocation must run on the primary server (for example, eagle.bmc.com).

Example of mcrtcell where a high-availability cell is created on the primary server when mcrtcell is invoked

mcrtcell -as -n <hacell> -@ eagle.bmc.com/8501,hawk.bmc.com/8501 -ba -r1


The following example creates a high-availability cell, hacell, on the secondary server, hawk.bmc.com. The mcell.conf file for hacell on the secondary server must be edited manually so that CellDuplicateMode=2. The service or boot script is created during this mcrtcell invocation. The service or boot script explicitly will refer to hacell on the secondary server as hacell#2.

Note

This mcrtcell invocation must run on the secondary server (for example, hawk.bmc.com).

Example of mcrtcell where a high-availability cell is created on the secondary server when mcrtcell is invoked

mcrtcell -as -n <hacell> -@ eagle.bmc.com/8501,hawk.bmc.com/8501 -ba -r2


The following example creates a high-availability cell, hacell, on the primary server, eagle.bmc.com. The mcell.conf file for hacell on the primary server must be edited manually so that CellDuplicateMode=1. The installation scripts installationDirectory/pw/server/etc/hacell/mcrtsvc_hacell.cmd or installationDirectory/pw/server /etc/hacell/mcrtsvc_hacell.sh are created. The Administrator or root user runs that installation script to set up the service or boot script, giving it one of the following arguments:

  • (Windows) installationDirectory/pw/server/etc/hacell/mcrtsvc_hacell.cmd 1 
  • (UNIX) installationDirectory/pw/server/etc/hacell/mcrtsvc_hacell.sh 1
    After the installation script is run, the service or boot script is created, referring to hacell on the primary server as hacell#1.

    Example of mcrtcell where the service or boot script for a high-availability cell is created on the primary server when an installation script is run

    mcrtcell -as -n <hacell> -@ eagle.bmc.com/8501,hawk.bmc.com/8501 -ba


    The following example creates a high-availability cell, hacell, on the secondary server, hawk.bmc.com. The mcell.conf file for hacell on the primary server must be edited manually so that CellDuplicateMode=2. The installation scripts installationDirectory/pw/server/etc/hacell/mcrtsvc_hacell.cmd or installationDirectory/pw/server/etc/hacell/mcrtsvc_hacell.sh are created. The Administrator or root user runs that installation script to set up the service or boot script, giving it one of the following arguments:

  • (Windows) installationDirectory/pw/server/etc/hacell/mcrtsvc_hacell.cmd 2 
  • (UNIX) installationDirectory/pw/server/etc/hacell/mcrtsvc_hacell.sh 2
    After the installation script is run, the service or boot script is created, referring to hacell on the secondary server as hacell#2. 

    Example of mcrtcell where the service or boot script for a high-availability cell is created on the secondary server when an installation script is run

    mcrtcell -as -n <hacell> -@ eagle.bmc.com/8501,hawk.bmc.com/8501 -ba

mcrtcell return codes

The following table lists the command-specific return codes for mcrtcell. For a list of common return codes that apply to all CLI commands, see Event management return codes.

mcrtcell return codes

Code

Description

31

No MCELL_HOME environment variable is defined

32

Cell name already exists in mcell.dir

33

Cell directory to be created already exists

35

Unable to open/access/read mcell.dir file

36

Unable to create new directory

37

Cannot get OS (uname command failed)

38

Unable to remove cell entry from mcell.dir file

39

Bad or missing cell name

40

Working directory is inside a directory to be removed

41

Bad port

42

Bad host name

43

Bad or invalid service display name

44

Bad usage

45

Bad cell details (invalid hosts, ports, and/or encryption key)

46

Source cell does not exist

47

Cell name not found in mcell.dir file

48

Cell directory not found

49

Immediate setup of service or boot script failed

50

Error while reading/parsing the mcell.dir file

51

Error during file or directory copy operation