You can view events on a remote cell if you configure the remote cell so that it can be viewed in the operator console. BMC recommends that you do not add a second cell as a remote cell. For example, if you have multiple server deployments with one master and two child servers, do not add the cells as remote cells.
iadmin -ac name=
remoteCellName—Name of the remote cell that you want to display as defined in the mcell.dir file
key—Encryption key of the cell; the default is mc
hostName—Computer where the cell is located. Specify the computer name and the domain name.
portNumber—Port on which the remote cell is listening; the default is 1828
environmentType—Type of environment where the cell is used; must be either Production or Test
userGroupNames—Names of the user groups that can access the remote cell. To allow access to all user groups, enter an asterisk (*) . To specify only certain user groups, enter the group names separated by commas. If a user group contains spaces, enclose the entire entry for this group name with quotation marks.
iadmin -ac name=qa:key=mc:primaryHost=qa.company.com:primaryPort=1828:environment=Production:usergroups="BPPPM Administrators, Read Only"
If you are using the IPv6 address instead of the host name, ensure that the IPv6 address in enclosed in square parentheses . This applies to both the primary and the secondary hosts. For example,
iadmin -ac name=chas_cell3:
cell qa mc qa.company.com:1828