Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP Systems Insight Manager Installation and Configuration Guide for Microsoft® Windows > Chapter 4 Initial setup

Setting up managed systems

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

Overview

Setting up managed systems involves installing the required Management Agents software and configuring the supported protocols to communicate with the HP Systems Insight Manager software. The following steps assume that HP Systems Insight Manager is installed on the CMS and the First Time Wizard has been completed.

NOTE: Discovery must be run before setting up managed systems. Configuring Automatic Discovery is part of the First Time Wizard.

To set up managed systems, you must perform two overall steps:

Installing required and optional managed system software

Managed systems must have the HP Version Control Agent (VCA) installed before you can use the Configure or Repair Agents feature to configure them.

Installing the ProLiant Support Pack on Windows systems for the first time

For Windows systems, install the latest ProLiant Support Pack with the preconfigured components to all managed systems using the HP Systems Insight Manager feature Initial ProLiant Support Pack Install.

When you are installing the ProLiant Support Pack for the first time, the Initial ProLiant Support Pack Install process enables you to install a ProLiant Support Pack to a Windows system because you do not have any HP Insight Management Agents, especially VCA, installed. This process also configures the system to use the trust certificate from HP Systems Insight Manager (HP SIM) and the setting to use the desired HP Version Control Repository Manager. After you have run the Initial ProLiant Support Pack Install tool, you can use the Install Software and Firmware tool to update systems.

The Install Software and Firmware feature in HP Systems Insight Manager requires that the HP Version Control Repository Manager be installed on servers containing a repository. Installing the VCRM is not part of this procedure. For more information regarding installing the VCRM, see the HP Version Control Installation Guide at http://h18013.www1.hp.com/products/servers/management/agents/documentation.html.

NOTE: You must have Windows administrator privileges on target systems to install a ProLiant Support Pack.The Install Software and Firmware and VCA features are only available after the Initial ProLiant Support Pack Install process has been run. For more information regarding ProLiant Support Packs, see the HP ProLiant Support Pack and Deployment Utilities User Guide at http://h18013.www1.hp.com/manage/psp.html.

To install a ProLiant Support Pack:

  1. Select Deploy->Deploy Drivers, Firmware and Agents->Initial ProLiant Support Pack Install. The Initial ProLiant Support Pack Install page appears.

  2. Select the target systems. To add targets, select a group from the dropdown list. The contents of the selected group appear and can be selected as targets, or choose the collection itself by selecting Select collection name itself.

  3. Click Next.

  4. On the Enter Windows login credentials page:

    1. In the User name field, enter the Windows administrator user name for the target system.

    2. In the Password field, enter the administrator password for the Windows user name entered above.

    3. In the Password (Verify) field, reenter the Windows administrator password exactly as it was entered in the Password field.

    4. In the Domain field, enter the System administrator's domain.

      Note: This field can be left blank if the system is not part of a domain.

  5. Click Next. The Select a Windows Support Pack page appears.

  6. Under Select a Version Control Repository, select a source repository system from which to retrieve the catalog.

    The following fields display:

    • Name. This field displays the name of the system.

    • Status. This field displays the status of the system.

    • Product Name. This field displays the name of the product.

    • Trusted?. This field indicates whether the system trust relationship has been configured. To configure a trust relationship, click configure.

    Note: This section displays systems that are authorized by the current user name. If the current user is not authorized to view the systems, a message appears, indicating that the user does not have authorization rights on the system.

  7. Under Select a Support Pack to Install, select a support pack to install. Click the expand tree icon icon to drill down and view the contents of the Version Control Repository that you selected.

    Note: To expand the System Software Baseline to display all contents, click the expand menu icon icon located in the upper-left corner of the Select a Support Pack to Install section. Click the collapse menu icon icon to collapse the listings.

  8. Select Install and initialize SSH (Secure Shell) if you want to install and configure OpenSSH on the target systems. This option is disabled by default.

  9. (Optional) Select Force downgrade or re-install the same version if you are installing a ProLiant Support Pack that is older than or the same as the version currently installed. This option is disabled by default.

  10. (Optional) If you do not want to reboot after the installation, clear the Reboot systems if necessary after successful install option, which is selected by default. However, the system must be rebooted for the new ProLiant Support Pack to be available.

  11. Click Next. The Configure Support Pack page appears.

    • If you select a ProLiant Support Pack 7.10, Configure a Support Pack appears. For example:

      Note: If you select a ProLiant Support Pack that is earlier than 7.10, the following example varies.

      To configure the 7.10 support pack:

      1. Click Configure Support Pack to set up the HP Version Control Agent in the selected Support Pack. The VCA Setup page appears.

        Note: If the VCA has already been configured, you can omit this step.

      2. In the Computer Name field, enter the name of the system where the VCRM is installed.

      3. In the Administrator Password field, enter the password associated with the login name specified.

      4. Click Save to save your settings. Click Cancel to discard your settings and close the VCA Setup page.

      5. Click Next. The Download Support Pack page appears.

      6. After the support pack is downloaded, click Schedule to create a scheduled task for the Initial ProLiant Support Pack Install to run, or click Run Now to run the task immediately.

      If you select a ProLiant Support Pack 7.20 or later, the following options display.

      • Click Configure System Management Homepage to set up the Support Pack to establish a trust relationship with System Management Homepage when it is installed on target systems.

        Note: If the Support Pack has already been configured, you can omit this step.

        Note: the trust relationship is established, click Last Update to update the status to trusted.

        To configure the System Management Homepage:

        1. From the Welcome to the Configuration Wizard for the HP System Management Homepage Component page, click Next. The Operating Systems Groups page appears.

        2. In the Group Name field, enter the name of an operating system group that you want to assign. For example, vcadmin.

        3. In the Operating Level field, select the appropriate level for the new group from the dropdown list.

          Note: The default Administrators Groups always have administrative access.

        4. Click Add to assign the group. The new group appears under the operating system group to which it was assigned.

          Note: You can add up to five entries per operating system group.

        5. Click Next. You can click Save to save your changes up to this point, or click Cancel to discard the changes and close the wizard.

        6. Select the appropriate settings to include:

          • Anonymous Access. Anonymous Access is disabled by default. Enabling Anonymous Access enables a user to access the System Management Homepage (SMH) without logging in. Select this option to allow anonymous access.

            Caution: HP does not recommend the use of anonymous access.

          • Local Access. Local Access is disabled by default. Enabling it means you can locally gain access to the System Management Homepage without being challenged for authentication. This means that any user with access to the local console is granted full access if Administrator is selected. If Anonymous is selected, any local user has access limited to unsecured pages without being challenged for a user name and password. Select this option to allow local access.

            Caution: HP does not recommend the use of local access unless your management server software enables it.

        7. Click Next. You can click Save to save your changes up to this point or click Cancel to discard the changes and close the wizard.

        8. Select the security required by your system. Some situations that require a higher level of security than others. Therefore, you are given the following security options:

          • Trust by Certificate. Sets the System Management Homepage (SMH) to accept configuration changes only from HP Systems Insight Manager servers with trusted certificates. This mode requires the submitted server to provide authentication by means of certificates. This mode is the strongest method of security because it requires certificate data and verifies the digital signature before allowing. If you do not want to enable any remote configuration changes, leave Trust by Certificate selected, and leave the list of trusted systems empty by avoiding importing any certificates.

            NOTE: HP strongly recommends using this option because it is more secure.

            To trust by certificate:

            1. Select Trust by Certificate, and click Next.

            2. In the Certificate Name field, click Browse to select the certificate file. After the certificate file is selected, the certificate data is displayed on the screen.

            3. Click Add. The certificate appears under Certificate Files. You can click Save to save your changes up to this point or click Cancel to discard the changes and close the wizard.

            4. Click Next. The IP Binding page appears.

          • Trust by Name. Sets the System Management Homepage to accept certain configuration changes only from servers with the HP Systems Insight Manager names designated in the Trust By Name field. The Trust By Name option is easy to configure. For example, you might use the trust by name option if you have a secure network with two separate groups of administrators in two separate divisions. It prevents one group from installing software to the wrong system. This option verifies only the HP Systems Insight Manager server name submitted.

            NOTE: HP strongly recommends using the Trust by Certificate option because the other options are less secure.

            The server name option must meet the following criteria:

            • Each server name must be less than 64 characters.

            • The overall length of the server name list is 1,024 characters.

            • The following special characters should not be included as part of the server name: ~ ' ! @ # $ % ^ & * ( ) + = \ ": ' < > ? , |

            • Semicolons are used to separate server names.

            To trust by name:

            1. Select Trust by Name, and click Next.

            2. In the Trusted Server Name field, enter the server name to be trusted.

            3. Click Add. The trusted system name appears under the Trusted Servers list. You can click Save to save your changes up to this point or click Cancel to discard the changes and close the wizard.

            4. Click Next. The IP Binding page appears.

          • Trust All. Sets the System Management Homepage to accept certain configuration changes from any system.

            NOTE: HP strongly recommends using the Trust by Certificate option because the other options are less secure.

            To trust all servers:

            1. Select Trust All. You can click Save to save your changes up to this point, or click Cancel to discard the changes and close the wizard.

            2. Click Next. The IP Binding page appears.

          IP Binding specifies from which IP addresses the System Management Homepage (SMH) accepts requests from and provides control over which nets and subnets requests are processed.

          Administrators can configure the System Management Homepage to only bind to addresses specified in the IP Binding page. A maximum of five subnet IP addresses and netmasks can be defined.

          An IP address on the server is bound if it matches one of the entered IP Binding addresses after the mask is applied.

          NOTE: The System Management Homepage always binds to 127.0.0.1. If IP Binding is enabled and no subnet/mask pairs are configured, then the System Management Homepage is only available to 127.0.0.1. If IP Binding is not enabled, you bind to all addresses.
        9. Configure IP Binding:

          1. Select IP Binding. The IP Binding page appears.

          2. Enter the IP address.

          3. Enter the netmask.

          4. Click Add. The IP binding configuration is saved and appears under the IP Binding List.

          5. Click Next. The IP Restricted Login page appears.

          The IP Restricted Login enables the System Management Homepage (SMH) to restrict login access based on the IP address of a system.

          You can set address restrictions at installation time, or it can be set by administrators from the IP Restricted Login page.

          • If an IP address is excluded, it is excluded even if it is also listed in the included box.

          • If there are IP addresses in the inclusion list, then only those IP addresses are allowed login access with the exception of localhost.

          • If no IP addresses are in the inclusion list, then log-in access is allowed to any IP addresses not in the exclusion list.

          Include or exclude IP addresses:

          1. In the From field, enter the IP addresses to include or exclude. You can enter an IP address range to be included or excluded by entering a beginning IP address in the From field and an ending IP address in the To field.

          2. From the Type field, select Include or Exclude.

          3. Click Add to add the IP address or IP address range to the Inclusion List or Exclusion List.

          4. Click Save. The HP System Management Homepage Login page for the System Management Homepage system appears. For more information about System Management Homepage, see the System Management Homepage Online Help at http://h18013.www1.hp.com/products/servers/management/agents/documentation.html.

    • Click Configure VCA to set up the HP Version Control Agent in the selected Support Pack.

      Note: If the VCA has already been configured, you can omit this step.

      To configure the VCA:

      1. In the Computer Name field, enter the name of the system on which the VCRM is installed.

      2. In the Login Account field, enter the login name used to connect to the VCRM on the system specified.

      3. In the Login Password field, enter the password associated with the login name specified.

      4. Click Save to save your settings. Click Cancel to discard your settings and close the VCA Setup page.

      5. Click Next.

  12. Back in HP Systems Insight Manager, click Next to start the ProLiant Support Pack download. The Download Support Pack page appears.

  13. After the support pack is downloaded, click Schedule to create a scheduled task for the Initial ProLiant Support Pack Install to run, or click Run Now to run the task immediately.

Installing the required software on an HP-UX system

  1. Understand the basic managed system software for HP-UX.

    For HPUX, the following software, shown with minimum recommended versions, is required for essential HP Systems Insight Manager functionality to operate. This software is installed by default as part of the latest HP-UX 11i v2 operating environments, but it might need to be installed or updated on HP-UX 11i v1 or older HP-UX 11i v2 systems.

    • T1471AA A.04.00 HP-UX Secure Shell

    • B8465BA A.02.00.07 HP WBEM Services for HP-UX

    This WBEM Services bundle contains basic system instrumentation displayed in the HP SIM Property Pages, as well as supporting collection and reporting by HP SIM Inventory functionality. To maximize the value of SIM for properties, inventory, and events, install the following available for HP-UX 11i v2 servers:

    • LVMProvider R11.23 CIM/WBEM Provider for LVM

    • WBEMP-LAN-00 B.11.23 LAN Provider for Ethernet/LAN Interfaces

    • SysFaultMgmt A.02.00 HP-UX System Fault Management

      System Management Homepage for HP-UX does not currently support the same level of functionality found in Windows and Linux servers. It is currently only required to support the latest version of Partition Manager.

    • SysMgmtWeb A.2.2 HP-UX Web Based System Management User Interfaces

    • Online Dialog bundle B6191AAE

    See http://www.hp.com/go/hpsim/providers for the latest WBEM Services bundle.

  2. Ensure the managed system software is installed.

    To verify that the minimum required software is installed, log in to the remote system, and run the following command:

    $ swlist –l bundle T1471AA B8465BA OpenSSL

    To verify that the optional providers and System Management Homepage are installed, run commands such as:

    $ swlist –l bundle LVMProvider WBEMP-LAN-00 SysMgmtWeb SysFaultMgmt OnlineDiag

  3. Acquire and install the managed system software if not previously installed.

    The SecureShell, WBEM and OpenSSL bundles are included on the HP-UX Operating Environment and Application Release media, as well as part of the HP Systems Insight Manager HP-UX depot downloaded from http://h18013.www1.hp.com/products/servers/management/hpsim/dl_hpux.html.

    For the WBEM providers, see http://h18013.www1.hp.com/products/servers/manamgement/hpsim/dl_hpux.html .

    After the depots containing the providers have been acquired, they can be installed from the managed system using commands such as:

    $ swinstall –s <depot_location> OpenSSL

    Note: B8465BA depends on OpenSSL, so this must be installed first.

    $ swinstall –s <depot_location> T1471AA

    $ swinstall –s <depot_location> B8465BA

    $ swinstall –s <depot_location> <names of WBEM providers being installed>

Configuring the Managed System Software

The HP Systems Insight Manager Configure or Repair Agents feature is a quick and easy way to configure managed systems.

Running the Configure or Repair Agents feature from the CMS

To run Configure or Repair Agents remotely against multiple systems simultaneously, you must have authorizations to run the Configure or Repair Agents tool.

You must have full CMS configuration privileges to modify the HP Systems Insight Manager community strings in the node security file. In addition, you must have administrator privileges for Windows systems HP-UX. you must enter root level user credentials for the target system.

Note: HP recommends that you use like operating systems to configure a managed system. For example, use a Linux-based CMS to run Configure or Repair Agents against Linux managed systems and HP-UX CMS to run Configure or Repair Agents against HP-UX managed systems. Windows systems can only be configured from a Windows CMS.

To configure agents remotely:

  1. Select Configure->Configure or Repair Agents from the menu.

    Note: The Verify Target Systems page appears if the targets are selected before selecting a tool.

  2. To add targets, select a group from the dropdown list. The contents of the selected group appear and can be selected as targets, or to select the collection itself, select Select Name of Collection itself.

  3. Click Apply.The targets appear in the Verify Target Systems section.

    Note: If the targets selected are not compatible with the tool, the Tool Launch OK? column provides a brief explanation for the problem. To remove a target, select the target, and then click Remove Targets.

  4. Select one of the following options:

    • Click Add Targets to add more targets to the Target System List.

    • To remove a target, select the target, and then click Remove Targets.

    • Click Next to specify tool parameters and to schedule the task.

  5. From the Enter login credentials page:

    1. In the User name field, enter the system administrator user name for the target systems.

    2. In the Password field, enter the system administrator password for the user name previously entered.

    3. In the Password (Verify) field, reenter the system administrator password exactly as it was entered from the enter login. These credentials must work on all target systems.

    4. For Windows managed systems only, in the Domain field, enter the Windows domain.

      Note: The credentials used in this step must work for all target systems that have been selected. HP recommends using domain administrator or root credentials.

  6. Click Next. Click Prev to return to the previous page. The Configure or Repair Settings page appears.

    The following options are available:

    • Configure SNMP. Select this option to configure SNMP settings.

      If this option is selected, the following steps must be considered:

      1. Select Set read community string.

        Note: If only HP-UX systems with default SNMP installation are being configured at this time, you may clear this option. HP-UX allows read by default (get-community-name is set to public by default on HP-UX systems).

        Note: If this option is selected, the Read Only community string is added to the target systems. If the target system is SUSE Linux or Microsoft Windows 2003, the managed nodes do not always allow SNMP communication between themselves and a remote host. This setting is modified to allow the instance of the HP Systems Insight Manager system to communicate SNMP with these target systems.

        Note: Repairing the SNMP settings adds a Read Write community string to the target system only if one does not currently exist. This community string is unique for each system, is composed of over 30 characters to include letters and numbers, and is only visible to the user with administrator privileges for that system. This Read Write community string is required by the Web Agent to perform certain threshold setting capabilities. This community string is only used locally on the target system and is not used by HP Systems Insight Manager over the network.

      2. Select Set traps to see this instance of HP Systems Insight Manager in the SNMP Trap Destination List of the target systems. This option allows the target systems to send SNMP traps to this instance of HP Systems Insight Manager.

    • Trust relationship: Set to "Trust by Certificate." Select this option to require systems to use the Trust by Certificate trust relationship with the System Management Homepage.

      For System Management Homepage on the target systems, this option sets the trust mode to Trust by Certificate and copies the HP Systems Insight Manager system certificate to the target system's trusted certificate directory, which enables HP Systems Insight Manager users to connect to the System Management Homepage using the certificate for authentication, rather then repeatedly entering login information.

    • Set administrator password for Insight Management Agents version 7.1 or earlier. Select this option to repair the administrator password on all Insight Management Agents installed on the target systems as applicable for Windows and Linux systems.

      Note: Deselect this option if you have Insight Management Agents 7.2 or later installed.

      Note: If the remote system is running HP-UX, this option is not executed on the remote system since it is not applicable on HP-UX systems. If only HP-UX target systems are being configured at this time, you can clear this option.

      If this option is selected, perform the following steps:

      1. In the Password field, reenter the new administrator password.

      2. In the Confirm Password field, re-enter the new administrator password exactly as you entered it previously.

    • Configure secure shell (SSH) access.

      Note SSH can be configured only if the SSH service is running on the managed systems.

      If this option is selected, you must select one of the following options:

    • Create subscriptions for WBEM events.

      Note: If this option is selected, the target system is configured to send WBEM indications or events to HP Systems Insight Manager.

      Note: Subscriptions for WBEM events can be created only if WBEM event providers are installed and running on the managed systems.

  7. Click Run Now, or click Schedule to run this task at a later time. Click Prev to return to the previous page. The Task Results page appears.

    Note: The Configure or Repair Agents tool can be used to update multiple target systems, the results can be seen on the stdout tab.

    Note:

    The Task Results page displays the following information:

    • Status. This field displays the details for each target system within a task instance.

    • Exit Code. This field represents the success or failure of an executable program. If the return value is zero or positive, the executable ran successfully. If a negative value is returned, the executable failed.

    • Target Name. This field displays the name/IP address of the target.

    • The stdout Tab. This tab displays the output text information.

    • The stderr Tab. This tab displays information if the executable experienced an error.

    • Files Copied Tab. This tab displays what files are in the process of being copied or have been copied to the target system.

    • View Printable Report. Reports can be printed for the currently selected target system or for all target systems associated with the task instance.

      To print a report:

      1. Click View Printable Report.

        An Options Message box appears, asking if you want to generate a report containing only the currently selected target system or all systems associated with the task instance.

      2. Select which report to print.

      3. Click OK to print the report, or click Cancel to return to the View Task Results page.

    If Management HTTP Server is installed on target systems, the login credentials are updated in the Management HTTP Server password file.

Setting up managed systems manually

Using HP Systems Insight Manager's Configure or Repair Agents is the easiest way to configure managed systems. The steps to manually configure Windows, , and managed systems are detailed below.

The following sections detail how to configure managed systems:

Setting up Windows managed systems manually

  1. Log in to the HP Systems Insight Manager on the Windows CMS with full CMS configuration privileges.

  2. Run the First Time Wizard if you have not already.

  3. Run discovery if you have not already.

  4. Preconfigure the System Management Homepage and version control components.

  5. Install the ProLiant or Integrity Support Packs on remote systems. Run the Initial ProLiant Support Pack Install to install the latest ProLiant Support Pack on Windows systems.

  6. Run the Configure or Repair Agents feature. For more information, see “Running the Configure or Repair Agents feature from the CMS”.

Setting up HP-UX managed systems manually

You can use the HP Systems Insight Manager Configure or Repair Agents tool to configure HP-UX managed systems simultaneously, or you can configure each managed system manually.

To configure an HP-UX system manually:

  1. Install SSH (bundle T1471AA) if not previously installed.

  2. Install WBEM (bundle B8465BA) if not previously installed.

  3. (Optional) Configure SNMP to send traps to the CMS.

  4. (Optional) Configure DMI on HP-UX 11.0 systems.

  5. On the CMS:

    1. Configure the SSH keys for this system.

    2. Configure the default WBEM user name and password if not previously done.

      Note: SSH and WBEM are installed on HP-UX 11.23 systems by default. For 11.11 systems, verify that they are installed with this command:

      swlist B8465BA T1471AA

    3. Subscribe to WBEM Indications/Events.

  6. On each managed system:

    1. Install SSH on the managed system if not previously installed.

      swinstall -s /directory/depot T1471AA where directory is the path to the depot file and depot is the name of the depot file. For example:

      swinstall -s /tmp/HPSIM_download.depot T1471AA

    2. Install WBEM on the managed system if not previously installed.

      swinstall -s /directory/depot B8465BA

      where directory is the path to the depot file and depot is the name of the depot file. For example:

      swinstall -s /tmp/HPSIM_download.depot B8465BA

    3. Configure SNMP to send traps to the CMS:

      1. Add the full host name or IP address of the CMS as a trapdest in the following file:

        /etc/SnmpAgent.d/snmpd.conf

        trap-dest: hostname_or_ip_address

      2. Stop the SNMP Master agent and all subagents with the command:

        /sbin/init.d/SnmpMaster stop

      3. Restart the SNMP Master agent and all subagents with the command:

        /usr/sbin/snmpd

    4. Configure DMI on the managed system by adding the DNS host name of the CMS.

      Note: DMI must only be configured for HP-UX 11.0.

      1. Stop the DMI daemon on the managed system:

        /sbin/init.d/Dmisp stop

      2. Edit /var/dmi/dmiMachines by adding the host name of the CMS to the end of this file. Save the file.

      3. Start the DMI daemon:

        /sbin/init.d/Dmisp start

    5. On the CMS, copy the SSH-generated public key from the CMS to the managed system using the mxagentconfig:

      Use one of the following commands:

      • mxagentconfig -a -n <hostname> -u root -f <file_with_root_password>

        or

      • mxagentconfig -a -n <hostname> -u root -p <root_password>

        Note: Using the -p option exposes the password through ps output, so use of the -f option (with a file only readable by root, and containing only the managed system root password) is highly recommended when using mxagentconfig -a. If the -p option is used, enclose the password in single quotes if the password has any special characters, such as & or $. For more information and options, see the mxagentconfig manpage with man mxagentconfig.

  7. Sign in to the HP Systems Insight Manager GUI. For assistance with this, see . Chapter 8 “Using the graphical user interface” Using the GUI, add the default WBEM user name and password to the Global Protocol Settings page.

    Note: An account for at least one of the WBEM user name and password combinations must exist on each managed system.

    Note: This step can be performed once for all the managed systems you are setting up.

    1. Select Options->Protocol Settings->Global Protocol Settings.

    2. In the Default WBEM settings section, ensure that the Enable WBEM checkbox is selected, and add the default WBEM user name, password, and confirmation password.

    3. Click OK.

    Note: An account for at least one of the WBEM user name and password combinations must exist on each managed system. If the user in the Global Protocol Settings does not exist on the managed node you can set per-system WBEM user names and passwords from the System Protocol Settings page.

  8. Using the GUI, add the default WBEM user name and password to the Global Protocol Settings page.

    Note: An account for at least one of the WBEM user name and password combinations must exist on the CMS.

    1. Select Options->Protocol Settings->Global Protocol Settings.

    2. In the Default WBEM settings section, ensure that the Enable WBEM checkbox is selected and add the default WBEM user name and password.

    3. Click OK.

  9. To subscribe to WBEM Indications/Events:

    Note: For more information about HP-UX WBEM events, go to the WBEM Event Subscriptions for HP-UX systems managed by HP SIM 5.0 white paper at http://h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html.

    1. From the managed system, be sure WBEM is already installed.

      Note: Subscribing to WBEM Indications/Events on managed systems is optional.

    2. Verify that SysFaultMgmt provider is installed:

      cimprovider –ls

      You should see EMSWrapperProviderModule.

    3. To subscribe to WBEM Events, you must have root access. If the Global Protocol Setting does not match the managed system or does not contain root access, the subscription for WBEM Indications fails. You can verify what access WBEM has by running the following command line:

      mxnodesecurity –l –p wbem –n <systemname>

      If the managed system does not have a root level user credential configured, you can add it for the individual system.

      Note: You can use the Configure or Repair Agents tool to perform this step without permanently recording a root password.

      1. To change the individual system:

        mxnodesecurity -a -p WBEM -c \

        <username:password> -n <systemname>

    4. From the CMS, run the WBEM Indications/Events command line:

      mxwbemsub -l -n <systemname>

      Your managed nodes are now ready to be managed by HP SIM

Configuring protocol settings

Configuring the protocol settings defines what systems are added to HP SIM using discovery.

To configure the protocol settings:

  1. Select Options->Protocol Settings->Global Protocol Settings. The Global Protocol Settings page appears.

  2. In the Default ping settings section, select Use the Internet Control Message Protocol (ICMP) for system reachability (ping) check or Use the TCP protocol for system reachability (ping) check port number 80. The Use the ICMP protocol for system reachability (ping) check option is the default and recommended setting.

    Select Use the TCP protocol for system reachable (ping) check. port number 80 if your company has disabled ICMP on the corporate network or the corporate policy mandates system firewall software to filter out ICMP requests. For example, Windows XP has this feature built in and can result in systems not being automatically discovered. This option enables you to run HP SIM and ping all available systems.

    Note: This option only applies to IP-based systems and is available for global, system-wide settings that are used when managing all systems in HP SIM. It is used by automatic discovery, hardware status polling, the ping tool, and any other tool that must verify system availability. This option is not available on a single-system basis.

    Note: If you select Use the TCP protocol for system reachable (ping) check. port number 80, even though HP SIM attempts a connection request to the current system, that system does not need any additional software running on it for this option to work. For example, HP does not require that a web server be running on port 80. Some networking systems might not respond to the TCP request, which is typically seen in low-end networking equipment. Manual additions can be made if it is necessary. However, this system displays as Critical if hardware status polling is run.

    Note: If you need to use a port other than port 80, you can change the NodeReachableTcpPort property in the globalsettings.props file located in C:\Program Files\HP\Systems Insight Manager\config\globalsettings.props for Windows and in /etc/opt/mx/config/globalsettings.props for HP-UX and Linux.

  3. Set the Default timeout and the Default retries. If some systems are managed over a WAN or satellite link, use a larger time-out (for example, five seconds) with at least one retry. For a LAN, a shorter time out can be used. This setting can be configured on a single-system basis.

  4. In the Default WBEM settings section, select Enable WBEM to allow Web-Based Enterprise Management (WBEM) requests to be sent. Enabled is the default setting. Enter as many default user names and passwords as needed. If your network includes storage systems, enter the user name and password of each SMI CIMOM in this section. The identification process attempts each of these user name and password pairs until a successful response is obtained. Future WBEM requests to that system use the user name and password that succeeded. For Windows-based systems, the user name should include the domain name, for example, domainname\username.

    Note: Order the name and password pairs such that root and administrator passwords are listed first and user and guest passwords are listed second. This order minimizes the search time.

  5. In the Default HTTP settings section, select Enable HTTP and HTTPS if it is necessary to allow web-based agents and other HTTP port scans to be identified. HP recommends leaving this option enabled for proper management and discovery of systems.

  6. In the Default SNMP settings section, select Enable SNMP, which is the system default, and set the Default time out and Default retries. If some systems are managed over a WAN or satellite link, use a larger time-out (for example, five seconds) with at least one retry. For a LAN, a shorter time out can be used. These settings can also be configured on a single-system basis.

  7. (Optional) Enter the Default write community string. This value is case-sensitive. Only a few tools need this option set. Community strings are case-sensitive.

  8. Enter the Read community string. This value is case-sensitive. Enter as many as needed. The identification process attempts communication to the system, using each of these communities in succession until a successful response is obtained. Future SNMP requests then use the community string that provided a successful response.

  9. (Optional) In the Default DMI settings section, select Enable DMI, to enable Desktop Management Interface (DMI) identification to run on systems. DMI is used to manage some older desktops, HP-UX 11.0 servers, and some third-party servers. If you do not need to manage these kinds of systems, DMI can be disabled to improve discovery performance.

    Note: DMI is not currently supported on Linux systems and is not shown in the user interface.

    Note: If DMI is disabled and some systems no longer have a correct system type or product name, re-enable DMI.

  10. Click OK to accept the settings.

Configuring and executing discovery

Discovery is the process that HP SIM uses to find and identify the systems on your network to populate the database with that information. A system must first be discovered to collect data and track system status. There are two basic ways to discover new systems:

  • Automatic discovery. The process that HP SIM uses to find and identify the systems on your network to populate the database with that information. A system must first be discovered to collect data and track system status.

  • Manual discovery. The process that enables you to bypass a full automatic discovery and add single and multiple systems to the database, create or import the HP SIM database Hosts file, and create or import a generic Hosts file.

Configuring and executing automatic discovery

  1. Select Options->Discovery. The Discovery page appears with the Automatic tab selected.

  2. In the For all automatic discoveries section, select Configure general settings. The General Settings section appears.

  3. Select Automatically discover a system when an event is received from it. This option allows systems to be discovered when a trap or some other supported event is received by HP Systems Insight Manager (HP SIM). It uses the discovery filters and IP address exclusion ranges for additional filtering of these events.

  4. Select Automatically discover a server blade when its Integrated Lights Out management processor is identified. This option adds servers that were indirectly discovered through its management processor. When these servers are discovered, they are listed with a Disabled state on the system table view page, and the only information displayed is the system serial number and the association to the iLO and the enclosure.

  5. Select Discover systems in an enclosure when Onboard Administrator is discovered. This option adds systems known by the Onboard Administrator even if they are not in the configured Discovery range.

  6. (Optional) In the Ping exclusion ranges, templates and/or hosts files field, specify the IP addresses, templates, or Hosts files containing IP addresses to exclude from the automatic discovery process. This field applies to both range pinging and event-based auto-discovery.

    Important: When discovering clusters, the ping inclusion range must include the IP addresses of the cluster and the cluster members.

  7. (Optional) Select Enable discovery filters.

  8. In the Discover the following system types: section, select the type of systems to be discovered.

    Important: When discovering clusters, you must include the server system type, so that the cluster members are not filtered out.

    Note: This option is available only when you select Enable discovery filters.

  9. In the Limit discovery to systems that meet the following criteria section, select from the following:

    • Any system that matches the above filter

    • All manageable systems (WBEM, SNMP, DMI, WMI, or HTTP support)

    • Manageable systems with HP agents only

    Note: This option is available only when you select Enable discovery filters.

  10. Click OK to save settings, or click Cancel to close the General Settings section without saving changes.

    If you click OK when discovery filters are enabled but have not selected any system types, the following error message appears:

    You must make at least one system type selection when enabling filters.

  11. Select the system automatic discovery , click run now, run at once or edit to schedule it for on going operations. if you would like to create other discovery tasks, click new.

Configuring and executing manual discovery

  1. Select Options->Discovery, and click the Manual tab. The System Information section appears.

  2. Select the System name radio button, and enter the system name,

    or

    select the IP address radio button, and enter the IP address.

  3. Click Add System to add the system to the database, if you have not entered the SNMP or WBEM credentials for this system previously, click More Settings, then click Add System. Or click More Settings to enter the following additional information:

    New Discovery Task
    New Discovery Task
    • Specify additional system properties to use only if Identification fails on this system. Includes:

      • System type

        Click the down arrow and select the appropriate System type.

      • System subtype

        Click the down arrow and select the appropriate System subtype. You can provide up to eight different system subtypes.

      • Product model

        This is a free form field and you can enter the system model number here.

    • WBEM Settings

      • User name

      • Password

        If you do not want to use the default global values for the WBEM user name and password, select Use Custom and enter custom values.

        If you are manually discovering a storage system, ensure that the user name and password of the SMI CIMOM are present in the global protocol settings, or enter them here as custom values. Select Options->Protocol Settings->Global Protocol Settings to view the global settings.

        For Windows-based systems, the user name should include the domain name, for example, domainname\username.

      • SNMP Settings

        If you do not want to use the default global values for the SNMP settings, select Use Custom and enter custom values.

        • Timeout (in seconds)

          The amount of time HP SIM waits for an SNMP response when it sends a request to the system. If a response is not received within the time interval, HP SIM might determine that the system does not support SNMP. Decreasing this value can result in increased network traffic because the number of attempts is accelerated. Use caution when changing this value. A value of three seconds usually works for a LAN. However, If systems are connected through a WAN, try a higher value, for example, 10 seconds.

        • Retries

          The number of additional times after the first attempt is made to communicate with a system before attempts stop.

        • Read-only community string and Write community string

          A community string sets up authentication that enables or prohibits communication between the managed system and the CMS. The community string of the CMS must match the community string of the managed system. Use the read-only community string to read variables. Use the write community string to modify variables. Although only one community is valid for a communication attempt, a system can belong to multiple communities. However, HP SIM only uses one community string when communicating to a system.

  4. If you clicked More Settings, click Add System to add the system immediately, or click Fewer Settings to return to the previous display. If you clicked Fewer Settings, click Add System to add the system to the database.

Adding users

Create a new user account to sign in to HP Systems Insight Manager (HP SIM). The account must be valid on the operating system (includes Active Directory on Windows) on the Central Management Server (CMS) and will be authenticated by the CMS. You must know the operating system user account name of the user you are adding, but you do not need to know the password.

To create a new user:

  1. Select Options->Security->Users and Authorizations->Users, and click New. The New User section appears.

  2. In the Login name (on central management server) field, enter the operating system login account name to be used to sign in to HP SIM. This field is required.

    Note: The user cannot sign in to HP SIM if the account is not a valid login. The account is not validated until the user tries to sign in to HP SIM.

  3. In the Domain (Windows domain for login name) field, enter the Windows domain name for the login name if the CMS is running a Windows operating system. If left blank, the system name of the CMS is used as the domain.

  4. (Optional) In the Full name field, enter the user's full name.

  5. (Optional) In the Phone number field, enter the user's phone number.

  6. (Optional) In the E-mail address field, enter the user's e-mail address.

  7. In the Copy all authorizations of this user or [template] field, select a template or login that already has the predefined authorizations that you want to assign to the login account you are creating.

  8. In the Central management server configuration rights section, select the level of authority to assign to the new user from the following options:

    • full, allowed to modify all Central Management Server settings. Allows the user total control of the database. Users can run discovery of systems and data collection define users and authorizations; set Cluster Monitor configuration; configure licensing and protocol settings; and create, modify, delete, and run reports, snapshot comparisons, tools, custom commands, events, automation tasks, and so on.

    • limited, allowed to create/modify/delete all reports and their own tools. Allows the user to create new reports, edit any reports, and delete any reports (including the predefined reports).

    • none, no configuration of Central Management Server allowed. Allows the user to view and run predefined reports on the CMS and all managed systems. However, the user has no configuration rights on the CMS or on the managed systems.

  9. Under the Login IP Address Restrictions section, in the Inclusion ranges field, enter the IP addresses of the systems that you want this user to be able to use as a client browsing into this CMS. If you list multiple IP addresses, separate them with a semicolon (;). Each range is a single IP address or two IP addresses separated by a dash (-). The IP addresses must be entered in the standard dotted form, for example, 15.1.54.133. Any spaces surrounding the semicolons or dashes are ignored. Spaces are not allowed within a single IP address in dotted form. Enter 0.0.0.0 to prevent a user from logging in through a remote system.

    Important: If browsing from the CMS, ensure all IP addresses of the CMS are properly included. If browsing to localhost, ensure the loopback address 127.0.0.1 is also included.

  10. In the Exclusion ranges field, enter the IP address of the systems that should be excluded from this user as clients browsing into this CMS. Use the same format in the previous step for Inclusion ranges.

    Note: Be sure to verify that your inclusion and exclusion ranges do not overlap.

  11. Under the Pager Information section, in the Phone number field, enter the pager phone number of the user associated with this user account if you are using a Windows operating system. If the Phone number field is left blank, the paging information is not saved.

  12. In the PIN number field, enter the PIN number associated with the pager phone number.

  13. In the Message length field, select how many characters can be accepted in the paging message from the dropdown list.

  14. In the Baud rate field, select the appropriate baud rate for the pager from the dropdown list.

  15. In the Data format field, select the appropriate data format for the pager from the dropdown list.

  16. Click OK to save and close the New User section. The new user account is created. Click Apply to save and keep the New User section open, or click Cancel to cancel the creation of this user.

User groups must exist in the operating system. For Windows, they must also exit in Active Directory. Members of the user groups in the operating system can sign in to HP Systems Insight Manager (HP SIM) and inherit the group's attributes for configuration rights, login IP address restrictions, and authorizations. When a group's configuration rights, login IP address restrictions, or authorizations are changed, this change is immediately reflected in all current members of the group.

To create a new user group:

  1. Select Options->Security->Users and Authorizations->Users, and click New Group. The New User Group section appears.

  2. In the Group name (on central management server) field, enter the operating system group name to be used for signing in to HP SIM. This field is required.

  3. In the Domain (Windows domain for login name) field, enter the Windows domain name for the group if the Central Management Server (CMS) is running a Windows operating system.

  4. In the Full name field, enter the full name for the group. This name appears in the table on the Users tab.

  5. In Copy all authorizations of this user or [template] dropdown list, select a template or login that already has the predefined authorizations that you want to assign to the group you are creating.

  6. In the Central management server configuration rights section, select the level of authority to assign to the new user group from the following options. Users that sign in to HP SIM as members of this group inherit these configuration rights.

    • full, allowed to modify all Central Management Server settings. Allows the user total control of the database. Users can run discovery of systems and data collection define users and authorizations; set Cluster Monitor configuration; configure licensing and protocol settings; and create, modify, delete, and run reports, snapshot comparisons, tools, custom commands, events, automation tasks, and so on.

    • limited, allowed to create/modify/delete all reports and their own tools. Allows the user to create new reports, edit any reports, and delete any reports (including the predefined reports).

    • none, no configuration of Central Management Server allowed. Allows the user to view and run predefined reports on the CMS and all managed systems. However, the user has no configuration rights on the CMS or on the managed systems.

  7. Under the Login IP Address Restrictions section, in the Inclusion ranges field, enter the IP addresses of the systems that you want members of this user group to be able to use as a client browsing into this CMS. If you list multiple IP addresses, separate them with a semicolon (;). Each range is a single IP address or two IP addresses separated by a dash (-). The IP addresses must be entered in the standard dotted form, for example, 15.1.54.133. Any spaces surrounding the semicolons or dashes are ignored. Spaces are not allowed within a single IP address in dotted form. Enter 0.0.0.0 to prevent a user from logging in through a remote system.

    Important: If browsing from the CMS, ensure all IP addresses of the CMS are properly included. If browsing to localhost, ensure the loopback address 127.0.0.1 is also included.

  8. In the Exclusion ranges field, enter the IP address of the systems that should be excluded from members of this user groups as clients browsing into this CMS. Use the same format in the previous step for Inclusion ranges.

    Note: Be sure to verify that your inclusion and exclusion ranges do not overlap.

  9. Click OK to save and close the New User Group section. Click Apply to save and keep the New User Group section open or click Cancel to cancel to close the New User Group section without saving the new group.

Configuring email settings

Configuring email settings enables users to send email notification of certain events.

To configure email settings:

  1. Access the Simple Mail Transfer Protocol (SMTP) host and CMS e-mail settings through the First Time Wizard, or choose Options->Events->Automatic Event Handling->Email Settings. The Email Settings page appears.

  2. Enter the SMTP host name. The SMTP host is the outgoing e-mail server that the CMS will use to send e-mail notifications.

  3. Enter the e-mail address that the management server will use when sending e-mail notifications in the Sender's e-mail address box.

  4. To authenticate your SMTP server, select Server Requires Authentication.

  5. Enter the account user name and password in the corresponding boxes.

  6. If you are using the First Time Wizard, click Next to go to the next step.

    Note If you did not enter a valid SMTP host, HP SIM notifies you that it will not be able to send e-mail notifications. Click OK if you do not want to enter e-mail settings now, or click Cancel and enter a valid SMTP host.

    If you are using the HP SIM GUI, click OK to save changes.

Configuring paging settings

Configuring paging settings enables users to receive pages to notify them of certain events.

To configure paging settings:

  1. Select Options->Events->Automatic Event Handling->Modem Settings. The Modem Settings page appears.

  2. From the COM port field, select the appropriate COM port. See your modem documentation for details.

  3. Click OK to save the setting.

Setting up automatic event handling

Automatic event handling enables you to define an action that HP SIM performs when an event is received. Automatic event handling can be set up to use the email and paging settings that you specified in the previous sections.

To set up automatic event handling with events and system attributes that you specify now:

  1. Select Options->Events->Automatic Event Handling->New Task. The Automatic Event Handling - New Task page appears.

  2. Select with event and system attributes that I will specify, and click Next. The Select name page appears.

  3. Enter a name in the Task name field, and click Next. The Select events page appears.

  4. Select the event search criteria for defining the task:

    • List criteria

    • Comparison option

    • Value for the criteria or comparison options selected

    To add additional search criteria, click Add.

  5. Click Next. The Select systems page appears.

  6. Select the system criteria for defining the task:

    • List criteria

    • Comparison option

    • Value for the criteria or comparison options selected

    To add additional criteria, click Add.

  7. When you have entered the information, click Next. The Select actions page appears.

  8. Select from the following options:

    • Send page (Windows only)

      Add users to be paged from the dropdown list of users by clicking >>. Click << to remove selected users from the list of users to be paged. The pager number for an HP Systems Insight Manager (HP SIM) user is set on the Users and Authorizations page. If a user name in the Users list is inactive, the pager information for the user has not been configured. You can add the user to the list of users to be paged, but pager messages are not sent to this user until the pager information is provided.

    • Send e-mail

      In the To field, enter the list of e-mail addresses that should receive the notification, separating each entry with a comma.

      In the CC field, enter any e-mail address that should receive a copy of the e-mail, separating each entry with a comma.

      In the Subject field, enter a note describing the subject of the e-mail.

      In the Message Format field, select from the following formats based on the encoding preference of the recipient:

      • Standard. A default message format that sends a text e-mail message to the recipients.

      • Pager/SMS. An e-mail message formatted with the same information and format as a pager message is sent to the recipients.

      • HTML. An e-mail message that looks like the HTML Event Details page is sent to the recipients.

      In the Encoding field, select from the following formats:

      • Western European (ISO-8859-1)

      • Unicode (UTF-8)

      • Japanese (ISO-2022-JP)

      • Japanese (Shift_JIS)

      • Japanese (EUC-JP)

    • Run custom command

      Select a custom command from the Name dropdown list. Custom commands are created under the Tools->Custom Commands->New Custom Command option.

    • Assign

      Enter the name of the person to whom to assign the task. The event is assigned to this user when received. Setting this field allows you to do searches assigned to this person.

    • Forward as SNMP trap

      Enter a system name or IP address in the Name or IP field, and click >> to add it to the Trap recipients box.

      Click Delete if you want to delete a recipient after selecting the name in the Trap recipients box. Use the up and down arrows to scroll to the recipient to delete.

    • Write to system log

      On Windows NT and Windows XP systems, the event details are written to the Application Log, and the Source column of the Event Log is listed as HP SIM for the logged event. On Linux and HP-UX systems, the event details are logged to the system log, which is usually located in the file /var/log/messages on Linux and in /var/adm/sysLog/syslog.log on HP-UX.

    • Clear event

      Received events are cleared based on the criteria selected when task executes.

  9. After you have made your selections, click Next. The Select time filter page appears.

  10. Select the Use time filter checkbox if you want to use time filters, and select an option from the dropdown list.

    1. Click Manage Filters if you want to set user-defined filters.

    2. Select the View time filter checkbox. A time filter window appears, showing the times selected.

      If the Use time filter checkbox is not selected, actions are triggered whenever the events matching the selected criteria are received.

      If the Use time filter checkbox is selected, actions are triggered only when they occur during the days and times specified by the selected time filter.

    3. When you have entered the information, click Next to continue with the next step. The Review summary page appears. The Task name, the events, system criteria, and Action(s) information are displayed. If a paging or e-mail option was selected, the modem and e-mail settings are displayed, along with buttons to change the settings.

  11. Click Edit Modem Settings to edit the modem settings, or click Edit email Settings to edit the SMTP settings.

    Note: The event and system search criteria appear at the bottom of the page. This information can be extremely complex and long. Therefore, you might need to scroll down to view all of the criteria.

  12. Click Finish to create the new task.

To set up automatic event handling with an existing event collection:

  1. Select Options->Events->Automatic Event Handling->New Task. The Automatic Event Handling - New Task page appears.

  2. Select with an existing event collection. The Step 1, Select name page appears.

  3. Enter a name for the task in the Task name box.

  4. Click Next. The Step 2, Select existing event collection page appears.

  5. Select the event collection from the dropdown list. This step enables you to select an event collection and its associated system information. Click View to view a read-only view of the event and system collection criteria. Click Previous to return to the previous step, or click Next to continue with the next step. The Step 3, Select actions page appears.

  6. Select any of the following actions for this task:

    • Send page (Windows only)

      Add users to be paged from the dropdown list of users by clicking >>. Click << to remove users from the list of users to be paged. The pager number for an HP SIM user is set on the Users and Authorizations page. If a user name in the Users list is inactive, the pager information for the user has not been configured. You can add the user to the list of users to be paged, but pager messages are not sent to this user until the pager information is provided on the Users and Authorizations page.

    • Send e-mail

      In the To field, enter the list of e-mail addresses that should receive the notification.

      In the CC field, enter any e-mail address that should receive a copy of the e-mail, separating each with a comma.

      In the Subject field, enter a note describing the subject of the e-mail.

      In the Message Format field, select from the following formats based on the encoding preference of the recipient:

      • Standard. A default message format that sends a text e-mail message to the recipients.

      • Pager/SMS. An e-mail message formatted with the same information and format as a pager message is sent to the recipients.

      • HTML. An e-mail message that looks like the HTML Event Details page is sent to the recipients.

      In the Encoding field, select from the following formats:

      • Western European (ISO-8859-1)

      • Unicode (UTF-8)

      • Japanese (ISO-2022-JP)

      • Japanese (Shift_JIS)

      • Japanese (EUC-JP)

    • Run custom command

      Select a custom command from the Name dropdown list. Custom commands are created under the Tools->Custom Commands->New Custom Command option.

    • Assign

      Enter the name of the person to whom to assign the task. The event is assigned to this user when received.

    • Forward as SNMP trap

      Enter a system name or IP address in the Name or IP text field, and click >> to add it to the Trap recipients box.

      Click Delete if you want to delete a recipient after first highlighting the name in the Trap recipients box. Use the up and down arrows to scroll to the recipient to delete.

    • Write to system log

      On Windows NT and Windows XP systems, the event details are written to the Application Log, and the Source column of the Event Log is listed as HP SIM for the logged event. OnHP-UX systems, the event details are logged to the system log, which is usually located in the file /var/log/messages on Linux and in /var/adm/sysLog/syslog.log on HP-UX.

    • Clear event

      Received events are cleared based on the criteria selected when task executes.

  7. Click Next to continue with the next step, or click Previous to return to the previous step. The Step 4, Select time filter pages appears.

  8. Select the Use time filter box if you want to use time filters, and select an option from the dropdown list.

    1. Click Manage Filters if you want to set user defined filters.

    2. Click View time filter. A time filter window appears, showing the times selected.

      If the Use time filter checkbox is not selected, actions are triggered whenever the events matching the selected criteria are received.

      If the Use time filter checkbox is selected, actions are triggered only when they occur during the days and times specified by the selected time filter.

    3. Click Next to continue with the next step, or click Previous to return to the previous step. The Step 5, Review summary page appears. The Task name, the selected event collection, the events, system criteria, and Action(s) information are displayed. If a paging or e-mail option was selected, the modem and e-mail settings are displayed, along with buttons to change the settings.

  9. Click Edit Modem Settings to edit the modem settings, or click Edit e-mail Settings to edit the SMTP settings.

  10. Click Finish to create the new task, or click Previous to go back to the previous step.

Adding toolboxes

Create a toolbox to configure a group of tools to which a user has access.

To add a toolbox:

  1. Select Options->Security->Users and Authorizations->Toolboxes, and then click New. The New Toolbox section appears.

  2. In the Name field, enter a name for the new toolbox. This field is required.

  3. In the Description field, enter a description for the toolbox.

  4. Select Toolbox is enabled to enable the toolbox and all authorizations created with this toolbox.

  5. In the Show tools in category field, select the category to display a list of tools in the available tools list. Select the tools to be assigned to this toolbox in the available tools list, and click >>.

    The selected tools appear in the Toolbox contents list. You can select a tool displayed in the Toolbox contents list, and click << to remove it from the assigned tools list.

  6. Click OK to save the new toolbox and close the New Toolbox section. Click Apply to save the settings without closing the New Toolbox section, or click Cancel to cancel the new toolbox creation and return to the Toolboxes section.

Adding authorizations

Authorize your users for a toolbox on a system or group of systems.

To add authorizations:

  1. Select Options->Security->Users and Authorizations->Authorizations, and then click New. The New Authorizations section appears.

  2. In the Select dropdown list, select User(s) or UserGroup(s), and select the users or groups in the box. This field is required.

  3. In the Enter authorizations for the selected user(s) section, select one of the following options:

    • Copy all authorizations of this user or [template]

      Select a user or template from the dropdown list.

    • Manually assign toolbox and system/system group authorizations

      1. In the Select Toolbox(es) section, select the toolboxes to include.

      2. In the Select Systems list box, the two default system groups are displayed. Select one of these groups or click Add to display the Add Systems section to select systems for the authorization.