HP StorageWorks Reference Information Storage System Administrator Guide Product Version: 1.
© Copyright 2004-2005 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. HewlettPackard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Contents Chapter 1: RISS overview RISS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 RIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Chapter 2: Platform Control Center Tour of PCC user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 Accessing PCC . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Displaying DAS configuration associations . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting DAS configuration associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating or deleting mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating or deleting assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting or scheduling DAS jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Alerts folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-94 Alerts Histogram view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-94 Alerts History view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-97 Alerts Summary view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-100 Software Version view . . . . . . . .
Contents Performing basic PAM tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8 Creating PAM objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8 Viewing PAM objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8 Modifying PAM objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10 Deleting PAM objects . . . . . . . . . . . . . . .
Contents Viewing non-editable simple routing rule information . . . . . . . . . . . . . . . . . . . Adding simple routing rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding repositories to simple routing rules . . . . . . . . . . . . . . . . . . . . . . . . . . Removing repositories from simple routing rules . . . . . . . . . . . . . . . . . . . . . . 3-32 3-33 3-33 3-33 Managing routing filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Installing the Outlook plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8 Configuring your system for Lotus Domino and Lotus Notes . . . . . . . . . . . . . . . . Requirements for Domino server configuration . . . . . . . . . . . . . . . . . . . . . . . Installing Email Miner for Lotus Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Administering Email Miner for Lotus Notes . . . . . . . . . . . . . . . . . . . . . . . . . .
CHAPTER 1 RISS overview This chapter describes key concepts involving the HP StorageWorks Reference Information Storage System (RISS) and Reference Information Manager (RIM).
Chapter 1: RISS overview RISS RISS The Reference Information Storage System (RISS) is a fault-tolerant, secure system of hardware and software that archives files and email messages for your organization, and lets you search for archived documents. RISS provides the following main functions: • Automatic, active data archiving (email and specific document types) that helps your organization meet regulatory requirements.
Chapter 1: RISS overview RIM RIM Reference Information Manager (RIM) is management software supplied with RISS. To interact with the system, users can access the following applications: Table 1-1: RIM applications for users Application Tasks RISS Web Interface Use a web browser to search for documents archived on the system. Save and reuse search-query definitions and results. RISS Outlook Interface (customer option) Search for emails using Microsoft Outlook with a Microsoft Exchange mail server.
Chapter 1: RISS overview RIM Table 1-2: RIM applications for administrators Application Tasks PST Importer Use for batch processing of multiple PST files. See Chapter 4, PST Importer. Mail Attender for Exchange Create selective archiving rules for Microsoft Exchange and Outlook. See Configuring your system for Exchange and Outlook, on page 5-2. Email Miner Create selective archiving rules for IBM Domino and Lotus Notes. See Configuring your system for Lotus Domino and Lotus Notes, on page 5-14.
CHAPTER 2 Platform Control Center This chapter describes the Platform Control Center (PCC) tool for monitoring and troubleshooting RISS.
Chapter 2: Platform Control Center • Warnings folder, on page 2-120 • Additional views, on page 2-121 LO 2-2 HP StorageWorks Reference Information Storage System Administrator Guide, February 2005
Tour of PCC user interface Chapter 2: Platform Control Center Tour of PCC user interface Accessing PCC To access PCC, open a web browser, and type the RISS server’s administrative IP address. User interface components PCC is an HTML-based application containing a menu on the left side of the page (referred to as the left menu). Use the left menu to access most views in PCC. All PCC views contain the left menu. Some views also contain a gray box heading, links to related views, and a help button.
Chapter 2: Platform Control Center View Left menu Site name Tour of PCC user interface Gray-box heading Links to related views Help button Figure 2-1: Platform Control Center user interface User interface orientation tips Views are often associated with several names or brief descriptions. To orient yourself, pay attention to the different ways a view is characterized. • Link text: A navigation link leading to a view is often the most specific description of the view.
Tour of PCC user interface Chapter 2: Platform Control Center frequency (see User interface components, on page 2-3, for an illustration). The heading sometimes provides an additional characterization of the view. For example, the gray-box heading for the Nagios Stats view is Performance Information, indicating the view displays performance information about the Nagios monitoring process.
Chapter 2: Platform Control Center Tour of PCC user interface • Printing view frames, on page 2-7 Views for common tasks Table 2-1: Views for common system administration tasks Task View Check system health Status Summary view, on page 2-17 If everything is green, system is healthy. If something is red, click on it to zoom in and examine the problem. Check system performance Status Summary view, on page 2-17 High store and indexing rates are good. Low query times are good.
Chapter 2: Platform Control Center Tour of PCC user interface Table 2-1: Views for common system administration tasks (continued) Task View Display status information about email mining servers Mining Overview view, on page 2-42 Updating views before printing PCC views displayed in the web browser are automatically updated approximately every 90 seconds. To manually update the view, click Refresh (or Reload) in the browser.
Chapter 2: Platform Control Center Tour of PCC user interface Left menu views The left menu provides quick access to many PCC views. Shaded cells in Table 2-2 indicate the most commonly used views. Table 2-2: Views accessible from left menu Left menu item Description Page Status Summary view View high-level summary of system health. For each host group, shows how many hosts and services have each status value. View status of each host group without details.
Chapter 2: Platform Control Center Tour of PCC user interface Table 2-2: Views accessible from left menu (continued) Left menu item Description Page Tactical Monitoring view View high-level summary of system health and monitoring, showing how many hosts and services have each status value and which monitoring features are enabled. Set monitoring features. 2-50 Service Detail view View status of services running on each host, organized by host groups. Examine details of particular services.
Chapter 2: Platform Control Center Tour of PCC user interface Table 2-2: Views accessible from left menu (continued) 2-10 Left menu item Description Page Scheduling Queue view View scheduled service checks for each host in the system. Schedule service checks. 2-73 Email Reporter view Configure summary monitoring reports to be sent periodically to email recipients you choose. 2-75 LogFile Sender view Select log files to send to HP to assist in troubleshooting.
Chapter 2: Platform Control Center Tour of PCC user interface Table 2-2: Views accessible from left menu (continued) Left menu item Description Page All Warnings view View exceptions (warnings) for the system.
Chapter 2: Platform Control Center Tour of PCC user interface Hosts and services are monitored by polling. You schedule polling intervals for services, but host polling is purposely kept to a minimum. Depending on the polling interval, there is more or less delay between occurrences on the system and reporting those occurrences in the PCC interface. In general, a host is polled only at system startup and after one or more service checks indicate a potential host problem.
Tour of PCC user interface Chapter 2: Platform Control Center Smart cell life cycle states Table 2-3: Smart cell life cycle states Life cycle state Definition Importance DISCOVERY Metaserver and smart cell are determining cell’s start state (state following DISCOVERY), based on expected states of the cell and its mirror smart cell. Cell is not available for document storage, search, or retrieval. maintenance (startup only) ASSIGNED Cell is assigned to a domain.
Chapter 2: Platform Control Center Tour of PCC user interface Table 2-3: Smart cell life cycle states (continued) Life cycle state Definition Importance RESTORE Cell is a target for data restoration from another smart cell. Cell is not available for document storage, search, or retrieval. maintenance DEAD Cell requires attention. Cell is not available for document storage, search, or retrieval. If backup is enabled, some or all cell data might not be backed up; if so, data will never be backed up.
Chapter 2: Platform Control Center Tour of PCC user interface Table 2-4: Host status values (continued) Status Color Description UNREACHABLE Brown Parent cloud router of the UNREACHABLE smart cell or HTTP portal is DOWN. Table 2-5: Service status values Status Description PENDING Gray Service has not been checked for status since PCC monitoring started. OK Green Service is functioning normally. WARNING Yellow Service might have a problem.
Chapter 2: Platform Control Center Tour of PCC user interface A SOFT status condition indicates the status value has not yet been confirmed; a HARD status condition has been confirmed. Confirmation is required only for problem status values, not for normal operation values (UP for hosts, OK for services). A normal status value always has a HARD status condition. When host or service problems are detected, PCC rechecks the problem a certain number of times.
Chapter 2: Platform Control Center Status Summary view Status Summary view This view provides a high-level look at system health. Depending on how it is accessed, this view displays information about a single host group or all host groups. You can quickly see overall status of each host group. Note: Other views use the charts Host Status Totals and Service Status Totals. These charts always refer to the set of hosts and services the view targets.
Chapter 2: Platform Control Center Status Summary view Table 2-7: Links to Status Summary view Origin Link left menu Overview Service Overview view, on page 2-58 View Status Summary . . . Host Detail view, on page 2-56 View Status Summary . . . Host Problems view, on page 2-62 View Status Summary . . . Service Detail view, on page 2-53 View Host Status Summary . . . Status Grid view, on page 2-141 View Status Summary . . .
Status Summary view Chapter 2: Platform Control Center Displaying services with a specific status In the System Status page, under Service Status Totals, click a status column heading, such as Critical. The Service Detail view appears. See Service Detail view, on page 2-53 for more information. Displaying specific host groups In the System Status page, under Status Summary for HostGroup, click a Host Group name, such as Smart Cells. The Service Overview view appears.
Chapter 2: Platform Control Center System Status view System Status view This view provides graphical performance and resource information.
Chapter 2: Platform Control Center System Status view Table 2-9: System Status view features (continued) Feature Description Graph Information • Other graphs: Link to custom performance graphs of selectable components. • 24-hour time bar: Selectable time periods for graph displayed at bottom of window. You can select Last 24 Hours or hourly periods expressed in 24-hour (military) format. Selected period has a gray background. (All times are in time zone where system is installed.
Chapter 2: Platform Control Center System Status view Related Views • Email Reporter view, on page 2-75, configures a periodic email report similar to the System Status view information. • Displaying the Smart Cell Groups for Domain view, on page 2-23, provides Store/Index/Indexer Latency graphs for individual smart cell groups.
Chapter 2: Platform Control Center System Status view Displaying software versions Click Software Versions.
Chapter 2: Platform Control Center System Status view Table 2-12: Smart Cell Groups for Domain view features, single group Feature Description Secondary Secondary smart cell of group. Same information as Primary (see previous). Replica Remote replica of one or both smart cells in group. Replicas are numbered 1 and 2. Same information as Primary (see previous). Graph Document storage and indexing rates, and difference between rates over last 24 hours.
Chapter 2: Platform Control Center Application Management view Application Management view Use this view to start, stop, and restart one or more servers on the system. This view is useful to show the start, stop, and pending status of a server. However, use this view only when necessary, such as when upgrading a host or before a planned power outage. This view should be used only by service personnel or administrators.
Chapter 2: Platform Control Center Application Management view Table 2-15: Application Management view features (continued) Feature Description All Systems If ALL Systems is displayed, shows all server groups associated with the system. • General status of server group. A check icon ( indicates normal operation. An X icon ( ) ) indicates one or more servers in group is down. An ! icon ( ) indicates an action is pending.
Application Management view Chapter 2: Platform Control Center Starting, stopping, and restarting servers on the system 1. Click to select server group. 2. Click one of the following buttons: – Start: Start all systems or hosts in selected server group. – Stop: Stop all systems or hosts in selected server group. – Restart: Stop and immediately start all systems or hosts in selected server group.
Chapter 2: Platform Control Center User Management view (Dynamic Account Synchronization) User Management view (Dynamic Account Synchronization) Use this view to configure Dynamic Account Synchronization (DAS) to automatically create and update email user accounts on Reference Information Storage System. You can define multiple configurations to extract various sets of users from one or more LDAP servers for specific Reference Information Storage System domains.
User Management view (Dynamic Account Synchronization) Chapter 2: Platform Control Center – In the Hostname field, enter IP address of LDAP server where user information is located. – In the Port field, enter LDAP server port that DAS uses. The default is 389. – In the Binder user field, enter user ID with administrative privileges on the LDAP server. You might want to create a user profile on the LDAP server specifically for DAS use. Include the domain in this entry.
Chapter 2: Platform Control Center User Management view (Dynamic Account Synchronization) 11. Click Associate. 12. Return to the User Management view, and click Job Mappings. The Job Mappings view appears. 13. Click Create. A mapping entry form is displayed, or a message informs you there are no configurations to be mapped. 14. Enter the following information: Table 2-17: User Management view, job mappings form Field Description Configuration ID DAS configuration that uses this mapping.
User Management view (Dynamic Account Synchronization) Chapter 2: Platform Control Center Table 2-17: User Management view, job mappings form (continued) Field Description USNChanged Active Directory’s unique sequence number (USN) the last time DAS ran. Active Directory increments the USN for each change in any of its user accounts. When DAS finds a larger USN, it extracts new information. For initial Reference Information Storage System setup, set USNChanged to “1” so DAS extracts all users.
Chapter 2: Platform Control Center User Management view (Dynamic Account Synchronization) Table 2-17: User Management view, job mappings form (continued) Field Description Delete USNChanged USN in deleted users directory the last time DAS ran. For initial Reference Information Storage System setup, set this value to “0”. Thereafter, do not change this value. To change this value, stop all scheduled jobs for this DAS configuration.
User Management view (Dynamic Account Synchronization) Chapter 2: Platform Control Center Updating connections to LDAP servers 1. In the User Management view, under the LDAP Server Connection(s) section, click the option button next to the existing LDAP server connection. 2. Click Update. A new view displays current host, port, user, and password. 3. Type new values as needed. To clear all values, click Reset before entering new data. 4. Click Update. Deleting connections to LDAP servers 1.
Chapter 2: Platform Control Center User Management view (Dynamic Account Synchronization) 3. To delete the mapping, locate the configuration, and click Delete below the form. Note: If there is more than one configuration, be sure to click the correct Update or Delete button. If you do not, the wrong mapping might be updated or deleted. Updating or deleting assignments 1. In the User Management view, click Job Assignments. 2.
User Management view (Dynamic Account Synchronization) Chapter 2: Platform Control Center Displaying servers with assigned DAS configurations The Web Servers and Assignments area of the User Management view lists HTTP servers with their assigned DAS configurations. Click a DAS configuration. The Job Assignments view appears, where you can view, change, delete, or start and stop the configuration.
Chapter 2: Platform Control Center Smartcell Cloning view Smartcell Cloning view This view shows status of current and past cloning operations. Use this view to clone a smart cell. You can clone a smart cell if its mirror smart cell is SUSPENDED, DEAD, or FAILED. (See Smart cell life cycle states, on page 2-13.) Cloning a smart cell copies all its information to another smart cell that is in the FREE state to give the smart cell a new, viable mirror.
Chapter 2: Platform Control Center Smartcell Cloning view Table 2-18: Smartcell Cloning view features (continued) Feature Description Status Area The following information about an ongoing cloning operation: • Source selected: IP address of smart cell being duplicated. • Target selected: IP address of smart cell receiving duplicate data. • Current Step Percentage: Dynamic bar showing how much source data has been duplicated. • Overall Percentage: Current step in cloning operation.
Chapter 2: Platform Control Center Smartcell Cloning view Cloning smart cells (copying data) 1. Select smart cell from the Source field. Note: Click Change Source, when present, to select a different smart cell for cloning. When the selection box appears, select the desired smart cell from the pull-down list, and click Select. 2. Click Clone Cell. This button is unavailable if there are no smart cells to clone. 3. Check the Status Area to see results of cloning operation.
Chapter 2: Platform Control Center Replication view Replication view Note: This view is available only if a replicated system is configured. Use this view to monitor and start or stop replicating a domain on a remote system. Replication status is updated after each polling cycle, so it could be up to 5 minutes after you start replication before you see results on the graph of replication rates. Errors and warnings, however, are displayed as soon as they happen on the system.
Chapter 2: Platform Control Center Replication view Related Views • Displaying all services running on specific hosts, on page 2-51 • Smartcell Cloning view, on page 2-36 Table 2-21: Links to Replication view Origin Link left menu Replication Links from Replication view: none Displaying replication statuses for groups in a domain and replication performance over time Click Details. For each group in domain, detail view shows: • Status, name, and total messages of group on local system.
Replication view Chapter 2: Platform Control Center Starting replication for specific domains Click START NOW below domain information. Replication will replicate batch that was next when it stopped. Stopping replication for specific domains Click STOP NOW below domain information. Replication will stop after current batch is replicated.
Chapter 2: Platform Control Center Selective Archiving folder Selective Archiving folder Mining Overview view This view provides status information about the mining system for each domain. It shows information about Exchange server, mining server, and system; and mining system information about host and service status. In addition, this view provides graphical store rate information. If selective archiving is not available or running, an error message is displayed.
Chapter 2: Platform Control Center Selective Archiving folder Table 2-22: Mining Overview view features (continued) Feature Description Mining Server Information about mining server and its status. • Server host name or IP address. • General status of mining server. A check icon ( indicates normal operation. An X icon ( problem. An ! icon ( ) ) indicates a ) indicates mining has stopped. • • • • Number of journal and mailbox miners. Rate and number of stored journal items.
Chapter 2: Platform Control Center Selective Archiving folder Table 2-22: Mining Overview view features (continued) Feature Description Mining System Info Host and service status information about mining system. • Host name and IP address. • Host sending mode. INTERNAL is the default and indicates data is being sent directly to RISS. EXTERNAL indicates data is being sent to memory before reaching RISS. RELAY indicates a mix of internal and external sending modes are occurring.
Selective Archiving folder Chapter 2: Platform Control Center Starting mining servers Click START NOW below server information. Based on number of servers, there is a latency period when starting servers. Note: You can also start the mining server from the Application Management view. Miner 1 Use the Miner1 link on the left menu to access VNC. Use VNC to access the email miner through PCC. More than one email miner might be available.
Chapter 2: Platform Control Center System Backup view System Backup view Note: This view is available only if a backup system is configured. Access this view from the System Backup left menu item. This view provides information about the status of backup servers, signature backups, and data backups, and direct access to a Tivoli Server Administration web client.
Chapter 2: Platform Control Center System Backup view The System Backup view contains tabbed panels: Overview, Signatures, and Data Backup. Click on a panel to view the system status for that item. Table 2-24: Overview panel features, System Backup view Feature Description Backup Status For each backup server: • General status of backup server and each of its services. Check icons ( or ! icons ( ) indicate normal operation; X icons ( ) ) indicate a problem or inactive service.
Chapter 2: Platform Control Center System Backup view Table 2-26: Data Backup panel features, System Backup view Feature Description Library Name of library for data backups. A backup library is a collection of backup volumes. Server Name Server (Internal or External) where data backup services run. Files backed up • Proportion of files backed up, expressed as a percentage and as a ratio of total number of files. • Graph of percentage of data files backed up over last 24 hours.
System Backup view Chapter 2: Platform Control Center Links from System Backup view: none Checking status of backups Click System Backup on the left menu. Accessing Tivoli Server Administration web client Click Tivoli Console to access the Tivoli Server Administration web client. See the Tivoli documentation for more information. Also, see the RISS 1.1 release notes for late-breaking issues.
Chapter 2: Platform Control Center Monitoring folder Monitoring folder Tactical Monitoring view This view provides a high-level summary of system status (health) and monitoring services. Use this view to enable or disable individual monitoring features. This view shows how many hosts and services have each status value and how many problems are acknowledged and unacknowledged (unhandled). Use other views to investigate these problems further.
Chapter 2: Platform Control Center Monitoring folder • The following views provide more information about monitoring performance: – Scheduling Queue view, on page 2-73 – Hostgroup Information view, on page 2-121 • Use the command Acknowledge this host/service problem in the Host/Service Information view to acknowledge host and service problems. See Example: Acknowledging problems, on page 2-144.
Chapter 2: Platform Control Center Monitoring folder • <#> Unhandled Problems The Service Status Details view appears. See Service Detail view, on page 2-53, for more information. See Example: Acknowledging problems, on page 2-144, for information about acknowledging problems. Displaying service status of specific services In the Tactical Monitoring view, under Services, click number of services with a given status value, for example 3 CRITICAL. The Service Status Details view appears.
Chapter 2: Platform Control Center Monitoring folder Service Detail view This view provides detailed service information for a specific host, all hosts in a host group, or all hosts in the system.
Chapter 2: Platform Control Center Monitoring folder Related Views • The Service Problems view is a subset of the Service Status Details view, providing information about only services that have problems. See Service Problems view, on page 2-61. Table 2-32: Links to Service Status Details view Origin Link left menu Service Detail Status Summary view, on page 2-17 • View Service Status Detail . . .
Chapter 2: Platform Control Center Monitoring folder Table 2-32: Links to Service Status Details view (continued) Origin Link Availability view, on page 2-85, for single host View Status Detail For This Host Creating availability reports, on page 2-88 View Status Detail For This Host Alerts History view, on page 2-97 View Status Detail . . . Notifications view, on page 2-89, for single host or when gray-box heading is Notifications View Status Detail . . .
Chapter 2: Platform Control Center Monitoring folder Table 2-33: Links from Service Detail view Destination Link Service Information view, on page 2-133 service name When main heading is Service Status Details For . . . Status Summary view, on page 2-17 View Host Status Summary . . Host Detail view, on page 2-56 View Host Status Detail . . Service Overview view, on page 2-58 View Service Overview . . Status Grid view, on page 2-141 View Host Status Grid . .
Chapter 2: Platform Control Center Monitoring folder Table 2-34: Host Detail view, Host Status Details chart features Feature Host Description Target hosts. Icons indicate presence of a comments ( scheduled downtimes ( ) and/or ). Status Current host status values. See Host and service status values, on page 2-14. Last Check Time host was last checked. Duration Length of time host has been running. Status Information Additional information about host status.
Chapter 2: Platform Control Center Monitoring folder Table 2-36: Links from Host Detail view Destination Link Service Detail view, on page 2-53 View Service Status Detail . . . Service Overview view, on page 2-58 View Service Overview . . . Status Summary view, on page 2-17 View Status Summary . . . Status Grid view, on page 2-141 View Status Grid . . .
Chapter 2: Platform Control Center Monitoring folder Table 2-37: Service Overview view features (continued) Feature Description Services Number of services running on host having each status value (counts of zero are omitted). For example, 6 OK means six services are functioning correctly. Actions (two buttons): • View Extended Information For This Host ( ) • View Service Details For This Host ( • Displays host’s Host Information view. See Host Information view, on page 2-126.
Chapter 2: Platform Control Center Monitoring folder Table 2-38: Links to Service Overview view (continued) Origin Link Status Grid view, on page 2-141 • View Service Overview . . .
Chapter 2: Platform Control Center Monitoring folder The Service Status Details view appears. See Service Detail view, on page 2-53, for more information. Displaying host information for specific hosts 1. Scroll to the bottom of the Service Overview view. 2. Find host’s host group. 3. In the Actions column, click View Extended Information For This Host ( ). The Host Information view appears. See Host Information view, on page 2-126, for more information.
Chapter 2: Platform Control Center Monitoring folder Table 2-40: Links to Service Problems view (continued) Origin Link Service Detail view, on page 2-53 All Problems, in chart Host Status Totals or Service Status Totals Service Overview view, on page 2-58 All Problems, in chart Host Status Totals or Service Status Totals Status Grid view, on page 2-141 All Problems, in chart Host Status Totals or Service Status Totals Host Detail view, on page 2-56 All Problems, in chart Service Status Totals T
Chapter 2: Platform Control Center Monitoring folder Table 2-43: Links from Host Problems view Destination Link Service Detail view, on page 2-53 View Service Status Details For All Host Groups Service Overview view, on page 2-58 View Service Overview For All Host Groups Status Summary view, on page 2-17 View Status Summary For All Host Groups Status Grid view, on page 2-141 View Status Grid For All Host Groups Comments view Comments are notes you make to yourself or other system administrators.
Chapter 2: Platform Control Center Monitoring folder Adding service or host comments 1. In the Service Comments or the Host Comments section, click the Add new service comment or the Add new host comment link ( ). The External Command Interface appears. 2. In the Command Options section, enter the following information: – Host Name – Service (if you are adding a service comment) Note: Enter host and service names exactly as they appear in PCC views. – Author (Your Name) – Comment 3.
Chapter 2: Platform Control Center Monitoring folder Host Downtime view Use this view to display and schedule host and service downtimes, and disable notifications during periods when target hosts and services are down. Scheduled downtimes are generally periods of planned outage. You can also schedule downtime for a host or service that is already down. Note: The only effect of a scheduled downtime is to suppress sending notifications; in particular, services are not disabled during downtimes.
Chapter 2: Platform Control Center Monitoring folder Table 2-47: Links from Host Downtime view Destination Link External Command Interface view, on page 2-143 Schedule host/service downtime Disabling notifications by scheduling service or host downtimes 1. In the Scheduled Service Downtime or the Scheduled Host Downtime section, click Schedule service downtime or Schedule host downtime. The External Command Interface appears. 2.
Chapter 2: Platform Control Center Monitoring folder A snore icon ( ) appears next to host or service entry in various views, such as Service Status Details. Re-enabling notifications by deleting scheduled downtimes 1. Find downtime. 2. In the Actions column, click the wastebasket icon ( ). The External Command Interface view appears. 3. Click Commit to save changes, or click Reset to clear input fields.
Chapter 2: Platform Control Center Nagios folder Nagios folder Nagios Info view This view provides information about Nagios, the PCC process monitoring hosts and services. The gray-box heading for this view is Nagios Process Information. PCC does not use several features of this view. Only features that PCC uses are described. Program Information chart Table 2-48: Program Information chart, Nagios Info view Variable Description Program Start Time Time PCC started.
Chapter 2: Platform Control Center Nagios folder Table 2-48: Program Information chart, Nagios Info view (continued) Variable Description Last Log File Rotation Time and date of latest event log file rotation. During daily rotation, file is copied from the log directory (/var/ log/nagios) to the log archive directory (/var/log/ nagios/archives). Log file is of limited size; when full, oldest log entries are discarded to make room for new entries.
Chapter 2: Platform Control Center Nagios folder Commands that disable (notifications, status checks, and so on) override commands that enable. For example, suppose you disable checks for a particular service, such as PING, using the Service Information view (command Disable checks of this service), but enable checks for all services using the Nagios Info view (command Start executing service checks). That particular service (PING) is not checked because disabling overrides enabling.
Chapter 2: Platform Control Center Nagios folder Table 2-52: Process commands, Nagios Info view Command link Description Shutdown the Nagios process Shuts down Nagios process. Note: After Nagios is shut down, it cannot be restarted via the web interface. Restart the Nagios process Restarts Nagios process. This is equivalent to sending the process a HUP signal. All information is flushed from memory, configuration files are reread, and Nagios starts monitoring with new configuration information.
Chapter 2: Platform Control Center Nagios folder Table 2-53: Nagios Stats view features Feature Description Time Frame/ Checks Completed Number and percentage of PCC services checked in each indicated time frame (since PCC startup or in the last 1, 5, 15, or 60 minutes). Metric/Min/Max/Average • Check Execution Time • Check Latency Minimum, maximum, and average times: • it took to check a service • between time a service check was scheduled and time it was executed (Percent State Change is not used.
Chapter 2: Platform Control Center Nagios folder Scheduling Queue view Use this view to display and schedule service checks. This view provides information about when each service on each host is scheduled to be checked. The gray-box heading for this view is Service Check Scheduling Queue. Current sort order is indicated by the heading above the chart, for example, Entries sorted by next check time (ascending). Some chart column headings have associated vertical arrows.
Chapter 2: Platform Control Center Nagios folder Displaying status information for specific hosts In the Host column, click host name, such as sc-sc1-172-1. See Host Information view, on page 2-126. Displaying status information for specific services In the Service column, click service name, such as PING. See Service Information view, on page 2-133. Disabling or enabling service checks Click the X icon ( ) or check-mark icon ( ) to disable or enable service checks, respectively.
Chapter 2: Platform Control Center Reporting folder Reporting folder Email Reporter view Use this view to configure summary monitoring reports to be sent periodically to email recipients you choose. You choose report types to send and how often to send them. For each report type (ReportTypes), Detailed and TextSummary, choose a reporting period (NotificationGroups) and any number of email recipients (Members).
Chapter 2: Platform Control Center Reporting folder Table 2-59: Email Reporter view features (continued) Feature Description NotificationGroups Currently configured email report periods. Choose how often to send email report: • Every_Two_Hours • Every_Four_Hours • Every_Six_Hours • Every_Eight_Hours • Every_Ten_Hours • Twice_A_Day • Once_A_Day If the period you want is not listed, select it from the pull-down list, and click Add.
Reporting folder Chapter 2: Platform Control Center Detailed email reports Detailed email reports provide system status and performance information in an HTML document. The detailed HTML format provides more content and the format is more sophisticated than the text summary report. The following information is provided in detailed reports: • Appliance Performance: Information available through the System Status view (see System Status view, on page 2-20).
Chapter 2: Platform Control Center Reporting folder • Smart Cell Metrics: Subset of the Smart Cell Groups for Domain view (see Displaying the Smart Cell Groups for Domain view, on page 2-23). For each domain, includes the following metrics for each smart cell in each smart cell group: – Role: If smart cell is primary, secondary, or first or second replica of smart cell group. – HostName: Smart cell’s IP address. – State: Smart cell’s current life cycle state.
Reporting folder Chapter 2: Platform Control Center In addition to information in the report itself, plain-text attachments provide exception logs for the following host groups: • SmartCell_Exceptions.txt: Smart cells host group • MetaServer_Exceptions.txt: Metaserver host group • HTTP_Exceptions.txt: HTTP portals host group • SMTP_Exceptions.txt: SMTP portals host group • LogServer_Exceptions.
Chapter 2: Platform Control Center Reporting folder • For each domain (DOMAIN SPECIFIC INFORMATION): – Domain name – Number of smart cell groups (SetSize) – If system is ready for storage operations (SMTP portals are ready and smart cells are allocated for domain) – If system is currently storing – If system is currently backing up data – If system is currently backing up message signatures – Size in gigabytes of raw data (documents) to be stored, before compression – Percentage of disk utilization • Nu
Chapter 2: Platform Control Center Reporting folder Editing reports 1. In the Report Types list, select report. Email report periods appear in the Notification Groups list. 2. Select email report period. Recipients appear in the Members list. 3. To edit the Members list, add email address and click Add, or select email address and click Delete. 4. Click Submit Configuration. LogFile Sender view The LogFile Sender view allows you to select log files to send to HP to assist in troubleshooting.
Chapter 2: Platform Control Center Reporting folder Table 2-61: Trends view features (continued) Feature Description State History Color-coded chart indicating host/service status value trends over reported time period. Pause the mouse pointer over status bar to display tooltip of additional information. (Pausing has no effect if Suppress pop-ups is turned on – see Creating trends reports, on page 2-84.
Reporting folder Chapter 2: Platform Control Center In addition to report features described previously, the report view has an input form at the upper right you can use to update the report. After changing report options, click Update to regenerate the report with new options. Input form options you can set are the same as those used to create displayed report: Assume initial states, Report period, and so on, with the addition of the Zoom factor.
Chapter 2: Platform Control Center Reporting folder Table 2-63: Links from Trends view Destination Link Trends view for host this service is running on (when view shows service trends) View Trends For This Host Availability view, on page 2-85, for host or service View Availability Report For This Host/ Service Creating availability reports, on page 2-88, for host or service View Alert Histogram For This Host/ Service Service Detail view, on page 2-53, for host (when view shows host trends) View S
Chapter 2: Platform Control Center Reporting folder – Backtracked Archives: Not used – Suppress image map: Turn on to inhibit zooming into the State History chart by clicking status color. – Suppress popups: Turn on to inhibit display of tooltips in State History chart status bars. 4. Click Create Report. Availability view Use this view to create reports on availability of individual hosts, services, or host groups, over given time periods.
Chapter 2: Platform Control Center Reporting folder Table 2-64: Availability view features, single host or service (continued) Feature Description State Breakdowns For Host Services (host report only) For each service running on host, percent of total elapsed time for each service status value. Values in parentheses represent percentages of total time minus time with Undetermined status. Click service name to view service Availability report.
Chapter 2: Platform Control Center Reporting folder Table 2-66: Links to Availability view (continued) Origin Link Alerts folder, on page 2-94 View Availability Report For This Host/Service Creating availability reports, on page 2-88 View Availability Report For This Host/Service Hostgroup Information view, on page 2-121 View Availability Report For This Hostgroup Host Information view, on page 2-126 View Availability Report For This Host Service Information view, on page 2-133 View Availabilit
Chapter 2: Platform Control Center Reporting folder Table 2-67: Links from Availability view (continued) Destination Link From single host report Service Detail view, on page 2-53, for host View Status Detail For This Host From single service report Availability report for host this service is running on View Availability Report For This Host Creating availability reports 1. Choose report type: Hostgroup(s), Host(s), or Service(s). 2.
Chapter 2: Platform Control Center Reporting folder 4. Click Create Availability Report. Notifications view This view provides a chronology of host and service notifications sent to system contact. It shows notifications for specific host, specific service, or all hosts and services, depending on how the view is accessed. Notifications are sent whenever host or service problems are detected or resolved.
Chapter 2: Platform Control Center Reporting folder Table 2-68: Notifications view features (continued) Feature Description Notification Command Notification command name (defined during system configuration). Information Additional information (corresponds to the Additional Info field of notification email) update form (upper right) To update the Notifications view: 1.
Chapter 2: Platform Control Center Reporting folder Table 2-69: Links to Notifications view (continued) Origin Link Alerts History view, on page 2-97 • for all hosts and services • single host • single service View Notifications For: • All Hosts • This Host • This Service Alerts folder, on page 2-94 View Notifications For This Host/Service Availability view, on page 2-85, for single host or service View Notifications For This Host/Service Creating availability reports, on page 2-88 View Notificat
Chapter 2: Platform Control Center Reporting folder Event Log view This view provides a chronology of logged PCC events. The Nagios event log (file /var/log/nagios/nagios.log) is rotated daily at midnight, and a copy named with the date (for example, nagios-12-20-200200.log) is placed in the archive directory, /var/log/nagios/archives.
Chapter 2: Platform Control Center Reporting folder • Alerts folder, on page 2-94, shows status value trends over time for hosts and/or services.
Chapter 2: Platform Control Center Alerts folder Alerts folder Alerts Histogram view Use this view to create reports with simple graphs showing, for individual hosts or services, number of events of different types over different time periods. The following histogram shows all service events over a one-day period. It shows, for example, two CRITICAL events and three WARNING events occurred around 6:45, and two recovery (OK) events occurred around 7:00.
Chapter 2: Platform Control Center Alerts folder value. For example, the following histogram shows only recovery (OK) events for the same time period. The OK event line from 11:15 to 13:15 was hidden by CRITICAL and WARNING event lines in the previous histogram. OK Event Line Was Hidden Behind Warning Event Line Figure 2-3: Alerts histogram of recovery service events over one-day period Table 2-73: Alerts Histogram view features Feature Description heading • Name of host or service reported on.
Chapter 2: Platform Control Center Alerts folder In addition to report features described previously, the report view has an input form at the upper right you can use to update the report. After changing report options, click Update to regenerate the report with new options. Input form options you can set are the same as those used to create the displayed report: Report period, Assume state retention, and so on. Related Views • Alerts folder, on page 2-94, shows status value trends for hosts or services.
Chapter 2: Platform Control Center Alerts folder Table 2-75: Links from Alerts Histogram view (continued) Destination Link Service Detail view, on page 2-53, for host View Status Detail For This Host Creating alert histogram reports 1. Choose report type: Host or Service. 2. Choose host or service. 3.
Chapter 2: Platform Control Center Alerts folder Table 2-76: Alerts History view features Feature Description Log File Navigation Day covered by current view. alerts Information for each alert, including: • Color-coded status icon (green: normal, yellow: warning, red: failure, orange: unknown). • Time stamp. • Alert type: HOST or SERVICE. • Host identifier. • Service identifier (service alerts only). • Host or service status value. See Host and service status values, on page 2-14.
Chapter 2: Platform Control Center Alerts folder Table 2-77: Links to Alerts History view (continued) Origin Link Service Detail view, on page 2-53, when main heading is Service Status Details For All Hosts View History For All Hosts Service Problems view, on page 2-61 View History For All Hosts Notifications view, on page 2-89 • when gray-box heading is Notifications • single host • single service View History For: • All Hosts • This Host • This Service Host Information view, on page 2-126 View
Chapter 2: Platform Control Center Alerts folder Table 2-78: Links from Alerts History view (continued) Destination Link When view shows alerts for single service Alert History view, filtered for host where service is running View History For This Host Updating Alerts History view 1. Choose the following update options: – To show only alerts about certain status conditions, choose a condition (SOFT, HARD, All) from the State type options list. See Hard and soft status conditions, on page 2-15.
Chapter 2: Platform Control Center Alerts folder Table 2-79: Alerts Summary view features, general (continued) Feature Description main chart heading Brief description of report contents. Examples: • Displaying most recent 25 of 742 total matching alerts • Totals By Hostgroup See Table 2-80, Table 2-81, and Table 2-82 for more information about specific report type features. Table 2-80: Alerts Summary view features, most recent alerts Feature Description Time Time of alert.
Chapter 2: Platform Control Center Alerts folder Table 2-81: Alerts Summary view features, alert totals Feature Description State Host/service status value. The row All States provides totals of each type of alert for all possible status values. Soft Alerts Number of SOFT alerts for given status value. See Hard and soft status conditions, on page 2-15. Hard Alerts Number of HARD alerts for given status value. Total Alerts Total number of alerts (SOFT and HARD) for given status value.
Chapter 2: Platform Control Center Alerts folder Table 2-84: Links from Alerts Summary view Destination Link Host Information view, on page 2-126 host Service Information view, on page 2-133 service Creating standard alert summary reports 1. Choose standard Report Type under Standard Reports. Only alerts with HARD status conditions are reported. See Hard and soft status conditions, on page 2-15.
Chapter 2: Platform Control Center Alerts folder Creating custom alert summary reports 1. Choose custom Report Type under Custom Report Options. Table 2-86: Custom alert summary report types Custom report type Information reported Most Recent Alerts The 25 most recent alerts, with such details as alert time and alert message. Alert Totals Summary information about number of alerts for each host and service status value. Alert Totals By Hostgroup Same as Alert Totals, but totals for each host group.
Alerts folder Chapter 2: Platform Control Center – Max List Items: Enter maximum number of alerts to report. 3. Click Create Summary Report.
Chapter 2: Platform Control Center Software Version view Software Version view This view shows software versions of hosts in each host group. Table 2-87: Software Version view features Feature Description Host Name Host’s IP address. (Not available for HostType System.) Spine Version Reference Information Storage System software versions used. This software includes operating system. Application Version Reference Information Storage System software versions used.
Chapter 2: Platform Control Center View Config view View Config view This view shows system configuration from different viewpoints, based on different object types. You can examine system parameters as defined when system was configured. You cannot change any parameters; they are readonly. This view always shows RISS settings made at system configuration/installation.
Chapter 2: Platform Control Center View Config view Table 2-89: View Config view features, hosts (continued) Feature Description Max. Check Attempts Maximum number of times to check host before a host problem status condition is considered HARD. See Hard and soft status conditions, on page 2-15. Host Check Command Command used to check host. Click link to display command definition. See View Config view features, commands, on page 2-112. Enable Checks If host checking is currently enabled.
Chapter 2: Platform Control Center View Config view Table 2-91: View Config view features, services Feature Description Host Name of host on which service is running. Click link to display configuration information for host. See View Config view features, hosts, on page 2-107. Description Description of service. Example: Spine Check. Max. Check Attempts Maximum number of times to check service before a service problem status condition is considered HARD.
Chapter 2: Platform Control Center View Config view Table 2-91: View Config view features, services (continued) Feature Description Notification Period Name of defined notification period: always, which means notifications can be sent any time; they are sent immediately. Click link to display definition of the always period. See View Config view features, time periods, on page 2-111. Types of information retained in retention file, /usr/local/nagios/ var/status.sav: all types of information.
Chapter 2: Platform Control Center View Config view Table 2-92: View Config view features, contacts (continued) Feature Description Service Notification Period Name of defined notification period: always, which means notifications can be sent any time; they are sent immediately. Host Notification Period Service Notification Commands Host Notification Commands Click link to display definition of the always period. See View Config view features, time periods, on page 2-111.
Chapter 2: Platform Control Center View Config view Table 2-94: View Config view features, time periods (continued) Feature Description Time Ranges Time period defined for given day of the week. The always time period has no time restriction on any day of the week. Table 2-95: View Config view features, commands Feature Description Command Name Command’s name. Example: check_ping. Command Line Command itself (its definition). Example: $USER1$/check_ping -H $HOSTADDRESS$ -w 200.
Chapter 2: Platform Control Center Services tools folder Services tools folder View Cell Space view Use this view to determine data-archiving system status by providing information about hosts involved directly with the active-archive application. Also use this view to restore data when both smart cells in a group have failed. To access this view, click View Cell Space in the left menu. Note: This view is available only for system installers and advanced system administrators.
Chapter 2: Platform Control Center Services tools folder Table 2-97: View Cell Space view features (continued) Feature Description Unaffiliated Smart Cells Smart cells not currently affiliated with any domain (not belonging to a smart cell group). These are reserve cells you can use when needed. Cell descriptions are the same as those in domain lists. Unaffiliated cells are in the FREE or RESET life cycle state.
Services tools folder Chapter 2: Platform Control Center 2. Find smart cell’s smart cell group identification number. Host names of smart cells in the smart cell group appear beneath the smart cell group identification number. Displaying domain-affiliated smart cells 1. In the View Cell Space view, find smart cell’s domain. 2. Find smart cell’s smart cell group identification number. 3. Click smart cell’s name. The Agent view appears.
Chapter 2: Platform Control Center Services tools folder 2. Find smart cell’s smart cell group identification number. Replicas are designated by the first letter in the smart cell group identification number: – R1 (primary replica) – R2 (secondary replica) Restoring data on failed smart cells To restore data on a failed smart cell, you must have at least one free smart cell. If only one smart cell in a group failed, clone a smart cell instead (see Smartcell Cloning view, on page 2-36).
Services tools folder Chapter 2: Platform Control Center 4. Determine which smart cells failed and can be restored: a. In the MBean view for the primary controller, click the button next to ListBrokenGroups. Groups that failed and have not been recovered are listed. b. Copy GroupIDs and Roles of broken groups. c. Click Back to MBean view. 4. Restore the smart cell: a. Under the RestoreSmartCellUsingGroupIDAndRole attribute, enter the group ID in the first field and the role in the second field. b.
Chapter 2: Platform Control Center Services tools folder Note: Do not modify settings in this view. For monitoring purposes, you normally do not need to use this view. It is intended only for installers and advanced system administrators. You can view the life cycle state change history for an individual smart cell in the MBean view for the SmartCellStateControllerMBean of the smart cell.
Chapter 2: Platform Control Center Services tools folder Noteworthy MBeans include: • For smart cells – ArchiveServiceMBean (document archiving) – Indexer (document indexing) – SmartCellStateControllerMBean • For SMTP services – SMTPService Related Views • Displaying all services running on specific hosts, on page 2-51 Table 2-102: Links to Agent view Origin Link Displaying all services running on specific hosts, on page 2-51 • Back to Agent View • host name MBean view, on page 2-117 Back to Agent
Chapter 2: Platform Control Center Warnings folder Warnings folder All Warnings view This view displays a program stack trace for each exception occurring on each host in a given host group. Note: For monitoring purposes, you normally do not need to use this view. It is intended only for troubleshooting and configuration by installers and advanced system administrators.
Chapter 2: Platform Control Center Additional views Additional views Hostgroup Information view This view provides information about service monitoring performance for a given host group. Except for the addition of access to Hostgroup Commands, this view provides the same information as the Nagios Stats view, filtered for a single host group.
Chapter 2: Platform Control Center Additional views Related Views • See Nagios Info view, on page 2-68, for information about global commands affecting all host groups. • The Nagios Stats view presents the same monitoring performance information, but for all host groups; and it does not have Hostgroup Commands. See Scheduling Queue view, on page 2-73. • Tactical Monitoring view, on page 2-50, also provides limited information about monitoring performance.
Chapter 2: Platform Control Center Additional views Hostgroup Commands section To execute a command: 1. Click on any link listed in Table 2-109. The External Command Interface view for that command appears. See External Command Interface view, on page 2-143, for more information. 2. Specify appropriate information. See command descriptions in Table 2-109 for more information. 3. Click Commit to save changes, or click Reset to clear input fields.
Chapter 2: Platform Control Center Additional views Table 2-109: Hostgroup Commands section, Hostgroup Information view Command link Description Schedule downtime for all services in a specific hostgroup Schedules downtime for all services in a particular hostgroup. During scheduled downtimes, Nagios does not send notifications about services. When scheduled downtimes expire, Nagios sends notifications for services as normal. Scheduled downtimes are preserved across program shutdowns and restarts.
Chapter 2: Platform Control Center Additional views Table 2-109: Hostgroup Commands section, Hostgroup Information view Command link Description Enable notifications for all services in a specific hostgroup Enables notifications for all services in specified hostgroup. Notifications are only sent for service state types defined in your service definitions. Enter information in the Hostgroup Name field. To enable notifications for all hosts in this hostgroup, select the Enable for Hosts Too check box.
Chapter 2: Platform Control Center Host Information view Host Information view This view provides status information for a given host. Table 2-110: Host Information view features Feature Description heading Full and abbreviated names of host, and host IP address. For example: • SmartCellMachines:sc-s1-172-1.mycorp.com: Full host name • sc-s1-172-1: Abbreviated host name • 10.0.172.
Host Information view Chapter 2: Platform Control Center Table 2-110: Host Information view features (continued) Feature Description Host State Information Host status information: • Host Status, Status Information, Last Status Check: Current status value, with additional status information and time of last status check. • Host Checks Enabled?: If host is checked for status. Change this value with the associated host command (see Host Commands section, on page 2-128).
Chapter 2: Platform Control Center Host Information view Table 2-111: Links to Host Information view (continued) Origin Link Alerts Summary view, on page 2-100 specific host name Notifications view, on page 2-89 specific host name Status Grid view, on page 2-141 specific host name Service Information view, on page 2-133 View Information For This Host Table 2-112: Links from Host Information view Destination Link Service Detail view, on page 2-53, for host View Status Detail For This Host Ale
Chapter 2: Platform Control Center Host Information view Table 2-113: Host Commands section, Host Information view Command Link Description Disable checks of a specific host Temporarily prevents Nagios from checking a particular host’s status. If Nagios must check host’s status, it assumes the host is in the same state it was in before checks were disabled. Enter information in the Host Name field. Acknowledge a specific host problem Note: This option appears only if the host status is not OK.
Chapter 2: Platform Control Center Host Information view Table 2-113: Host Commands section, Host Information view (continued) Command Link Description Schedule downtime for a specific host Schedules downtime for a particular host. During specified downtimes, Nagios does not send notifications about host. When scheduled downtimes expire, Nagios sends notifications for host as normal. Scheduled downtimes are preserved across program shutdowns and restarts.
Chapter 2: Platform Control Center Host Information view Table 2-113: Host Commands section, Host Information view (continued) Command Link Description Schedule an immediate check of all services on a specific host Schedules immediate check of all services on specified host. Checks are scheduled immediately, not necessary executed immediately. If Nagios falls behind in its scheduling queue, it checks services queued prior to these services.
Chapter 2: Platform Control Center Host Information view 1. In the Host Comments section, click the Add new comment link ( ). The External Command Interface appears. 2. In the Command Options section, enter the following information: – Host Name – Author (Your Name) – Comment 3. To retain comment between Nagios restarts, click to select the Persistent check box. 4. Click Commit to save changes, or click Reset to clear input fields. Deleting all comments for specific hosts 1.
Service Information view Chapter 2: Platform Control Center Service Information view This view provides status information for a given service. Table 2-114: Service Information view features Feature Description heading Name of service. Full and abbreviated names of host and host IP address. See Host Information view, on page 2-126. Service State Statistics Amount and percentage of time service has had each service status value, and total time. See Host and service status values, on page 2-14.
Chapter 2: Platform Control Center Service Information view Table 2-114: Service Information view features (continued) Feature Description Service State Information Status information for service: • Current Status, Status Information: Current service status value, and additional status information. • Last Check Time, Next Scheduled Active Check: Times of latest and next scheduled status checks. • Current Attempt: Number of successful attempts and total number of attempts to check service.
Chapter 2: Platform Control Center Service Information view Table 2-115: Links to Service Information view (continued) Origin Link Service Problems view, on page 2-61 service name Scheduling Queue view, on page 2-73 service name Alerts Summary view, on page 2-100 service name Notifications view, on page 2-89 service name Status Grid view, on page 2-141 service name Table 2-116: Links from Service Information view Destination Link Host Information view, on page 2-126 View Information For Thi
Chapter 2: Platform Control Center Service Information view 2. Specify appropriate information. See command descriptions in Table 2-117 for more information. 3. Click Commit to save changes, or click Reset to clear input fields. Table 2-117: Service Commands section, Service Information view Command link Description Acknowledge a specific service problem Note: This option appears only if service status is not OK. Acknowledges service problem.
Chapter 2: Platform Control Center Service Information view Table 2-117: Service Commands section, Service Information view (continued) Command link Description Delay next service notification Delays next problem notification sent for specified service. Notification delay is disregarded if service changes state before next notification is scheduled to be sent. This command has no effect if service is currently in an OK state.
Chapter 2: Platform Control Center Service Information view Table 2-117: Service Commands section, Service Information view (continued) Command link Description Disable checks of a specific service Disables service checks. When service is disabled, Nagios does not monitor service and stops sending notifications for specified service while it is disabled. To have Nagios check service again, you must re-enable service.
Chapter 2: Platform Control Center Service Information view Table 2-117: Service Commands section, Service Information view (continued) Command link Description Disable event handler for a specific service Temporarily prevents Nagios from running the service event handler for service. The following fields are required: • Host Name • Service Disable flap detection for a specific service Disables flap detection for service.
Chapter 2: Platform Control Center Service Information view Deleting all comments for specific services 1. In the Service Comments section, click the Delete all comments link ( ). The External Command Interface appears. 2. In the Command Options section, enter the following information: – Host Name – Service 3. Click Commit to save changes, or click Reset to clear input fields.
Chapter 2: Platform Control Center Status Grid view Status Grid view This view provides a high-level summary of hosts and services, organized by host group. Each host and service is listed, and its status value is shown by color coding (see Host and service status values, on page 2-14). To see details, click host or service entry. The charts Host Status Totals and Service Status Totals of the Status Grid view are the same as those of the Status Summary view. See Status Summary view, on page 2-17.
Chapter 2: Platform Control Center Status Grid view Table 2-120: Links from Status Grid view Destination Link Host Detail view, on page 2-56 View Host Status Detail . . . Service Detail view, on page 2-53 View Service Status Detail . . . Service Overview view, on page 2-58 View Service Overview . . . Status Summary view, on page 2-17 View Status Summary . . .
External Command Interface view Chapter 2: Platform Control Center External Command Interface view Use this view to run commands that perform actions. Some commands allow or require additional command information. Fields labeled in red are required input. To run a command, enter command information, and click Commit. Reset clears all input fields. Some commands are applicable to individual hosts or services, all hosts of a host group, or all services running on a host.
Chapter 2: Platform Control Center External Command Interface view Example: Enabling or disabling notifications If you click Disabled next to Notifications in the Tactical Overview view (see Tactical Monitoring view, on page 2-50), which indicates notifications are currently disabled, the External Command Interface view appears with the message You are requesting to enable notifications. No additional command information is required; just click Commit.
Chapter 2: Platform Control Center External Command Interface view • Service Information view, on page 2-133 Table 2-122: Links to External Command Interface view Origin Link Tactical Monitoring view, on page 2-50 Enabled/Disabled Comments view, on page 2-63 Add a new host/service comment Host Downtime view, on page 2-65 Schedule host/service downtime Nagios Info view, on page 2-68 commands (Process Commands) Scheduling Queue view, on page 2-73 Actions for specific service Hostgroup Informatio
Chapter 2: Platform Control Center External Command Interface view LO 2-146 HP StorageWorks Reference Information Storage System Administrator Guide, February 2005
CHAPTER 3 Platform Account Manager This chapter explains how to use the Platform Account Manager (PAM) to provision and update user accounts.
Chapter 3: Platform Account Manager PAM overview PAM overview Use the Platform Account Manager (PAM) to view and update individual user accounts for unusual circumstances on the HP StorageWorks Reference Information Storage System (RISS). Initial setup and routine addition and deletion of user accounts occurs automatically through synchronization with Windows Active Directory. RISS archives emails and other documents in one or more repositories.
Chapter 3: Platform Account Manager PAM overview Logging in to PAM 1. Navigate to the pam/bin directory on your Windows machine. 2. Double-click pam.bat. The Login dialog box appears. 3. Enter the following: – User Name: Your user name. (You must be a user with administrative privileges to use PAM.) – User Password: Your password. To change your password, use the RISS Web Interface (choose Preferences). – PCC NAT Host: Name or IP address of the PCC NAT host.
Chapter 3: Platform Account Manager PAM overview PAM window After logging in to PAM (see Logging in to PAM, on page 3-3), the Platform Account Manager window appears.
Chapter 3: Platform Account Manager PAM overview Table 3-1: Platform Account Manager window features (continued) Feature Description Options menu • Show Users – Determines registered users displayed in the Users panel. Options are: – All Users – Shows all users of the system. – Active Users – Shows only users who are allowed to log in (active Outlook Integration Users and active Non-Outlook Integration Users). – Inactive Users – Shows only users who are not allowed to log in.
Chapter 3: Platform Account Manager PAM overview Table 3-1: Platform Account Manager window features (continued) Feature Description A-to-Z buttons Used to show only names starting with button letter. Names correspond to objects of current panel. (Panels are described later in this table.) When the Domain box is available, names are limited to those in selected domain. (These buttons are not available in the Routing Filters panel.
Chapter 3: Platform Account Manager PAM overview Table 3-1: Platform Account Manager window features (continued) Feature Description navigation buttons Shows number of qualified objects displayed. For example, 1-50 of 230 means the first 50 objects are shown and a total of 230 objects match selected type and filter criteria. Click navigation buttons to: • < – Display previous 50 qualified objects. • << – Display 50 qualified objects before previous 50. • > – Display next 50 qualified objects.
Chapter 3: Platform Account Manager Performing basic PAM tasks Performing basic PAM tasks Use the Platform Account Manager window to create, view, modify, or delete objects, such as user accounts, ACLs, or routing rules. For a sample scenario, see Example: Integrating new department, on page 3-39. For detailed information about individual PAM panels, see panel descriptions later in this chapter. Creating PAM objects 1. Click the object tab, (for example, ACLS). 2. Click New.
Performing basic PAM tasks Chapter 3: Platform Account Manager Repositories tab Figure 3-2: Repositories tab 2. Use the Search, A-to-Z, <, <<, >, and >> buttons to display target object in the list. 3. Select target object in the list. 4. To modify selected object, do one or more of the following, and click Apply. – Change values in editable parts of the panel.
Chapter 3: Platform Account Manager Performing basic PAM tasks Modifying PAM objects 1. Click the object tab (for example, click Repositories). 2. Use the Search, A-to-Z, <, <<, >, and >> buttons to display target object in the list. 3. Select target object in the list. 4. To modify selected object, do one or more of the following, and click Apply. – Change values in editable parts of the panel.
Performing basic PAM tasks Chapter 3: Platform Account Manager 5. To delete selected object, click Delete, and click Yes in confirmation message. Deleting PAM objects 1. Click the object tab (for example, click Active Users). 2. Use the Search, A-to-Z, <, <<, >, and >> buttons to display target object in the list. 3. Select target object in the list. 4. To delete selected object, click Delete, and click Yes in confirmation message.
Chapter 3: Platform Account Manager Performing basic PAM tasks Adding member objects to collection objects These procedures assume you selected the collection object in the list at the left of the PAM window. See Viewing PAM objects, on page 3-8, for instructions. 1. Click Add . (The object depends on the current panel.) The Select dialog box appears. Click All to list all users Select user to add Click Add to add selected user Figure 3-5: Select User dialog box 2.
Performing basic PAM tasks Chapter 3: Platform Account Manager 3. Select user in the Select User dialog box. 4. Click Add in the Select User dialog box. 5. Click Apply in the ACLs panel. Removing member objects from collection objects These procedures assume you selected the collection object in the list at the left of the PAM window. See Viewing PAM objects, on page 3-8, for instructions. 1. Select object in the list. 2. Click Remove . (The object depends on the current panel.
Chapter 3: Platform Account Manager Managing user accounts Managing user accounts Use the Users panel to view or change individual user accounts on RISS. Choose set of users to view with Options > Show Users. See Options menu in Table 3-1. The panel name (on the tab) changes accordingly. For example, if you choose Options > Show Users > Active Users, the panel heading is Active Users, and you can view only active users (those able to log in to the system).
Managing user accounts Chapter 3: Platform Account Manager Table 3-2: Users panel, PAM window Feature Description object list Users on this system determined by Options > Show Users, and indicated by current panel name. (See Filtering list of users, on page 3-16.) Synchronize this Account If DAS is allowed to update selected user account. See Viewing noneditable user information, on page 3-16. UserID Automatically generated identifier for selected user; unique to the system. (Not editable.
Chapter 3: Platform Account Manager Managing user accounts Table 3-2: Users panel, PAM window (continued) Feature Description Object GUID Globally Unique Identifier of corresponding user account on LDAP server. (Not editable.) This is DAS’ key to correct account on LDAP server. Apply button Used to save changes made to editable fields. Button is unavailable until you change a value. Reset button Used to clear unsaved changes and redisplay last saved values.
Managing user accounts Chapter 3: Platform Account Manager Adding new users Choose set of users to view with Options > Show Users. These instructions specify actions for the Active Users selection. 1. Click the Active Users tab. 2. Click New. The Add New Item dialog box appears. 3. Choose domain for new user and enter name, email, and host information. You cannot select user status or enter comments. 4.
Chapter 3: Platform Account Manager Managing user accounts 6. If you change selected options, click Apply. Otherwise, click Cancel to close the User Status dialog box. Note: The User Status button is unavailable if Synchronize this Account is selected. Viewing and modifying user comments 1. Click User Comments. 2. In the Comment dialog box, click Update. 3. Type new comments in the Input dialog box, and click OK. The new comment replaces the previous comment. 4. Click OK. The Input dialog box closes.
Chapter 3: Platform Account Manager Managing repositories Managing repositories Use the Repositories panel to view, add, or change RISS repositories. You can change which ACLs apply to a given repository. You cannot delete a repository. Accessing Repositories panel Click the Repositories tab. Figure 3-7: Repositories panel Table 3-3: Repositories panel, PAM window Feature Description object list Repositories on system. Repository ID Automatically generated identifier for selected repository.
Chapter 3: Platform Account Manager Managing repositories Table 3-3: Repositories panel, PAM window (continued) Feature Description Access ACL ID ACLs defined for selected repository. Domain Name Domain to which selected repository belongs. (Value is supplied when repository is created. See User Management view (Dynamic Account Synchronization), on page 2-28, for DAS configuration.) Add ACLs button Used to add ACL to repository. See Adding ACLs to repositories, on page 3-22.
Managing repositories Chapter 3: Platform Account Manager Figure 3-8: Filter repositories Viewing non-editable repository information Under the Access ACL ID feature, double-click an ACL entry to display the ACL dialog box, where you can view (but not modify) the ACL definition. The ACL dialog box provides the same information as the ACLs panel for that ACL. See Managing access control lists (ACLs), on page 3-23. Adding repositories 1. Click New. The Add New Item dialog box appears. 2.
Chapter 3: Platform Account Manager Managing repositories Adding ACLs to repositories 1. Select repository from the object list. 2. Click Add ACLs. 3. Click to display the Select ACL Entries dialog box, where you can select access control lists and add them to selected repository. 4. Click Apply in the Repositories panel. Removing ACLs from repositories 1. Select repository from the object list. 2. Click Remove ACLs. 3. Select Access ACL ID entry, and click Remove ACLs. 4. Click Apply.
Managing access control lists (ACLs) Chapter 3: Platform Account Manager Managing access control lists (ACLs) Use the ACLs panel to create or delete an access control list, or change users in a given ACL. Accessing ACLs panel Click the ACLs tab. Figure 3-9: ACLs panel Table 3-4: ACLs panel, PAM window Feature Description object list Access control lists on the system. See Filtering list of ACLs, on page 3-24. ACL ID Automatically generated identifier for selected ACL. Value is unique to the system.
Chapter 3: Platform Account Manager Managing access control lists (ACLs) Table 3-4: ACLs panel, PAM window (continued) Feature Description Name (Required.) Name of selected ACL. See Viewing non-editable ACL information, on page 3-24. Description Description of selected ACL. See Viewing non-editable ACL information, on page 3-24. User Entries for this ACL List of user names in selected ACL. See Viewing user profiles, on page 3-26. Add User button Used to add users to selected ACL.
Managing access control lists (ACLs) Chapter 3: Platform Account Manager Adding ACLs 1. Click New. The Add New Item dialog box appears. 2. Type ACL name in the ACL Name field. 3. Type ACL description in the Description field. 4. Choose user entries for ACL. Note: See Creating ACL for managers to access marketing email, on page 3-42, for an example. Adding users to ACLs 1. Click Add User. The Select User dialog box appears. 2. Select one or more users. 3. Click Add. 4. Click Apply in the ACLs panel.
Chapter 3: Platform Account Manager Managing access control lists (ACLs) Note: See Removing member objects from collection objects, on page 3-13, for an example. Viewing user profiles Under the User Entries for ACL feature, double-click an entry to display the User dialog box, where you can view (but not modify) the user profile. The User dialog box provides the same information as the Users panel for that user. See Managing user accounts, on page 3-14.
Managing routing rules Chapter 3: Platform Account Manager Managing routing rules Use the Routing Rules panel of the PAM window to create, edit, or delete routing rules, or choose the repository associated with a rule. Note: Use simple routing rules (see Managing simple routing rules, on page 3-31) instead of the Routing Rules panel whenever possible. Extensive use of rules can negatively impact system performance. Accessing Routing Rules panel Click the Routing Rules tab.
Chapter 3: Platform Account Manager Managing routing rules Table 3-5: Routing Rules panel, PAM window Feature Description candidate objects List of all routing rules. See Filtering list of routing rules, on page 3-28. Routing Rule ID Automatically generated identifier for selected routing rule. See Viewing non-editable routing rule information, on page 3-28. Name (Required.) Name of selected routing rule. Domain Domain of selected routing rule.
Managing routing rules Chapter 3: Platform Account Manager Adding routing rules 1. Click New. The Add New Item dialog box appears. 2. Define rule name. 3. Choose domain. 4. Choose repositories for new routing rule. 5. Define the Routing Rule Info. See Defining routing rule information, on page 3-29. 6. Click Add. Defining routing rule information Note: Matching is not case-sensitive (b matches B and b), except for Subject field.
Chapter 3: Platform Account Manager Managing routing rules email Date field (date, local time, local offset from GMT). Example: MessageDateRange="2003-7-1 00:00 +0700 TO 2003-8-1 00:00 +0700". • Email addresses are used as match strings for TO and FROM. Each must respect standard email address syntax. Each is matched completely. Example: TO="c@b.com" matches c@b.com, but not abc@b.com. • Parentheses ( (, ) ) are used for grouping. Example: (FROM="a@b.com" OR (TO="w@z.org" AND Subject=”meeting”)).
Managing simple routing rules Chapter 3: Platform Account Manager Managing simple routing rules Use the Simple Routing Rules panel to create, edit, or delete simple routing rules, or choose the repository associated with a rule. Note: Use simple routing rules instead of the Routing Rules panel (see Managing routing rules, on page 3-27) whenever possible. Extensive use of rules can negatively impact system performance. Accessing Simple Routing Rules panel Click the Simple Routing Rules tab.
Chapter 3: Platform Account Manager Managing simple routing rules Table 3-6: Simple Routing Rules panel, PAM window Feature Description candidate objects List of all simple routing rules for selected domain. See Filtering list of simple routing rules, on page 3-32. Mail Address (Required.) Mailing address of selected simple routing rule. See Viewing non-editable simple routing rule information, on page 3-32. Repository ID (Required.) List of repositories simple routing rule applies to.
Managing simple routing rules Chapter 3: Platform Account Manager Adding simple routing rules 1. Click New. The Add New Item dialog box appears. 2. Define the Mail Address. 3. Choose applicable repositories. Note: For a simple routing rule to have any effect, there must be a routing filter with the same email domain as in the routing rule Mail Address. When you create a simple routing rule, check the Routing Filters panel for a filter with the corresponding domain. If there is no such filter, create one.
Chapter 3: Platform Account Manager Managing routing filters Managing routing filters Use the Routing Filters panel to create, edit, or delete routing filters, or choose the repositories associated with a routing filter. A routing filter checks email domains appearing in all addresses of each email. For each domain in an email matching the Email Domain of a routing filter, the following occurs: • All simple routing rules with that domain are checked against the email.
Chapter 3: Platform Account Manager Managing routing filters Note: Before you add a repository to a filter Repository ID field already containing the special value R0000000 Catchall Repository, remove the entry R0000000 Catchall Repository. A routing filter with R0000000 Catchall Repository must not contain any other Repository ID values. Routing filter examples Table 3-7 shows what happens when emails with various addresses are filtered using different values for Repository ID.
Chapter 3: Platform Account Manager Managing routing filters Accessing Routing Filters panel Click the Routing Filters tab. Figure 3-12: Routing Filters panel Table 3-8: Routing Filters panel, PAM window Feature Description candidate objects List of routing filters for selected domain. See Filtering list of routing rules, on page 3-37. Email Domain (Required.) Email domain of selected routing filter (example: mycorp.com). Filter applies to all emails with this domain in the mail header.
Managing routing filters Chapter 3: Platform Account Manager Table 3-8: Routing Filters panel, PAM window (continued) Feature Description ... Used to display the Select Repository dialog box, where you can add a repository to selected routing filter. The new repository replaces the previous repository in the Routing Filters panel. You must click Apply in the Routing Filters panel for the addition to take effect.
Chapter 3: Platform Account Manager Managing routing filters Modifying routing filters 1. Select a routing filter in the object list. 2. Change values in the Email Domain or Repository ID fields. 3. Click Apply. Deleting routing filters 1. Select a routing filter in the object list. 2. Click Delete, and click Yes in confirmation message.
Example: Integrating new department Chapter 3: Platform Account Manager Example: Integrating new department Problem statement and solution Problem In this example scenario, your company, OurCorp, is splitting the marketing function from the Sales Department to create a separate Marketing Department. The current marketing person, Mark Marcom, is becoming the manager of the Marketing Department, and two new marketing employees, John Doe and Jane Choi, are being hired.
Chapter 3: Platform Account Manager Example: Integrating new department – Create individual repositories for John’s email and Jane’s email. – Create access control lists (ACLs) for John and Jane to access (query) their respective individual repositories. – Create simple routing rules to route John’s email and Jane’s email to their respective individual repositories. The new repositories and ACLs are named the same as the users (johndoe and janechoi).
Example: Integrating new department Chapter 3: Platform Account Manager For ease in maintenance and flexibility in access control, using abstract collection objects like a marketing repository and a marketing ACL can be advantageous. Trying to manage everything at the fine-grain level of individual users and their relationships to user repositories can lead to extra work for both system administrators and end users.
Chapter 3: Platform Account Manager Example: Integrating new department 5. Click Apply in the Users panel (PAM window). Creating ACL for managers to access marketing email Use the ACLs panel to give Manager Mark and CEO Betty access to all email to and from members of the Marketing Department. 1. Click the ACLs tab. 2. Click New. The Add New Item dialog box appears. 3. Enter the following: – Name – marketingaccess. – Description – Access to the Marketing Department repository.
Example: Integrating new department Chapter 3: Platform Account Manager Editing simple routing rules for marketing email Use the Simple Routing Rules panel to add the new Marketing Department repository, marketingstore, to the existing simple routing rules for each Marketing Department user (John, Jane, and Mark): 1. Click the Simple Routing Rules tab. 2. Use the A-to-Z buttons or Search button to navigate to the list of candidate objects containing the user’s email address. 3.
Chapter 3: Platform Account Manager Example: Integrating new department LO 3-44 HP StorageWorks Reference Information Storage System Administrator Guide, February 2005
CHAPTER 4 PST Importer This chapter contains these topics: • PST Importer overview, on page 4-2 • Installing PST Importer, on page 4-4 • Using PST Importer, on page 4-6 • Archive Request file, on page 4-16 HP StorageWorks Reference Information Storage System Administrator Guide, February 2005 4-1
Chapter 4: PST Importer PST Importer overview PST Importer overview PST Importer allows system administrators to: • Load legacy (pre-RISS 1.0) PST files into RISS. • Scan PST files to ensure RISS finds and archives new messages. • Provide optional “tombstoning” of messages in PST files. Note: PST Importer modifies messages by removing attachments and possibly body content. This altered message is referred to as a tombstone. You may be more familiar with the term stub.
PST Importer overview Chapter 4: PST Importer Archive Request file The Archive Request file defines the set of documents to be archived. Each file requires the following: • Universal Naming Convention (UNC) path • Option to distribute emails to all recipients (From, To, Cc, and Bcc) • Option to tombstone and remove body and/or attachments • List of user repositories to receive document These parameters are supplied in an XML file format generated with Archive Request Loader.
Chapter 4: PST Importer Installing PST Importer Installing PST Importer This section discusses these topics: • Installation requirements, on page 4-4 • Installation procedure, on page 4-5 Installation requirements Before installing PST Importer, verify you meet the following requirements. Hardware requirements • Client machine with 512 MB RAM and 200 MB free disk space Client software requirements • Uninstall HP RISS Document Manager before installing PST Importer. • Windows 2000 or later.
Installing PST Importer Chapter 4: PST Importer • Read/Write access to PST files to be imported • Access to Outlook and Exchange without logon prompts Installation procedure Install PST Importer on a client machine. 1. Verify that client machine meets installation requirements. HP highly recommends using Outlook 2003 on Windows XP. See Installation requirements, on page 4-4. 2. On a client machine, run the setup.exe installation file provided by your HP representative. 3.
Chapter 4: PST Importer Using PST Importer Using PST Importer This section explains how to use the PST Importer tools and discusses these topics: • Archive Request Loader, on page 4-6 • PST Import Monitor, on page 4-11 Archive Request Loader Use Archive Request Loader to create or validate an Archive Request file. This tool also generates an output log file, detailing issues that occurred during the load process. Before adding a file to PST.
Using PST Importer Chapter 4: PST Importer Figure 4-1: Archive Request Loader window 2. Click New. The following window appears. Figure 4-2: Creating a new file 3. Click Add, and select PST files. Only files in the Select Files To Process list are imported. In the file you are creating, corresponding XML tags are and .
Chapter 4: PST Importer Using PST Importer 4. To import PST files larger than 150 MB, edit the following setting in RISS PST Importer.ini to reduce performance degradation and increase throughput: [PSTLaunchMgr] MaxProcesses=1 5. If necessary, select PST files you do not want to process, and click Remove. 6. In the Select Output File box, enter the path and file name of the file you are creating or revising, or click Browse to navigate to a location. 7.
Using PST Importer Chapter 4: PST Importer – Use TNEF: If selected, stores submitted messages in TNEF format. XML tag is . – Distribute To All Recipients: If selected, PST Importer sends a copy of the document to all addresses specified in the message. If unselected, only the owner specified in the Repository box receives the document. XML tag is . If you do not select this setting, HP highly recommends using a repository that is not associated with an active email account.
Chapter 4: PST Importer Using PST Importer file contains processing and error information generated while loading the Archive Request file. If the log file already exists, the application appends processing and error information to the existing file. Note: The log file’s verbosity level is set to the default, which is 3 (information). To change the level, edit RISS PST Importer.
Chapter 4: PST Importer Using PST Importer Parameter Description /o Required. Name of Archive Request Loader log file to which diagnostic and processing information is written. Replace LoadLogFileName.log with the full UNC path and log file name. /c Optional. Parses XML structure in input file for syntax and file accessibility only. No records are added to PST.MDB for processing. /v Optional. Verbosity level used when processing Archive Request file.
Chapter 4: PST Importer Using PST Importer The following window appears: Figure 4-3: PST Import Monitor 2. PST Import Monitor displays basic data about the PST process status. To view specific processing information, see the following: Item Information area: – Total: Total number of items found in the PST files so far. LO percentage of items processed and submitted – Processed: Number and to RISS.
Using PST Importer Chapter 4: PST Importer – Rejected: Number and percentage of items that PST Importer could not process due to errors. The PST Importer log file contains error information explaining why the item was rejected. See PST Importer log file, on page 4-15 for more information. – Ignored: Number and percentage of items that were not processed because they cannot be submitted to RISS. These items include, but are not limited to, calendar items, tasks, contacts, and messages stubs.
Chapter 4: PST Importer Using PST Importer Figure 4-4: Resetting process Depending on the reasons the process failed, resetting a failed process may not correct the problem. However, PST Importer tries to reprocess it as directed.
Using PST Importer Chapter 4: PST Importer Status Monitor report At each refresh interval, status information is automatically saved to /LogFiles/PSTImporterStats.log. This is useful if the installation has its own separate process that monitors import progress. Modify the following RISS PST Importer.ini settings to specify a different path and file name for the report: [PSTImporter] MonitorPath=UNCPath When the MonitorPath is specified, PST Importer creates the file specified by UNCPath.
Chapter 4: PST Importer Archive Request file Archive Request file This section describes settings specified in an Archive Request file and provides a sample file. Settings description All settings specified under can be overridden at the level. All settings described in the Archive Request file are required in either the or sections unless otherwise noted.
Chapter 4: PST Importer Archive Request file Table 4-1: Tags in (continued) Tag Description Specifies if submitted messages are stored in TNEF format. True indicates TNEF format is used. False indicates TNEF format is not used. Specifies if PST Importer sends a copy of the document to all addresses specified in the message. True enables this setting. False indicates only the owner specified in receives the document.
Chapter 4: PST Importer Archive Request file The contains a list of file specifications bounded by the tag. The settings described for are required unless otherwise noted. Table 4-2: Tags in Tag Description Path and file name of imported file. Wildcards are allowed and are expanded prior to processing. UNC paths are supported and highly recommended. Type of import processing to be performed on the .
Chapter 4: PST Importer Archive Request file Sample file 1.0 pleexc01 dmontgomery papoon 25 papoon firesign user@firesign.dev audit@firesign.
Chapter 4: PST Importer Archive Request file E:\PSTFiles\Outlook.
CHAPTER 5 Configuring Outlook or Lotus Notes This chapter contains information about these topics: • Configuring your system for Exchange and Outlook, on page 5-2 • Configuring your system for Domino and Lotus Notes, on page 5-14 HP StorageWorks Reference Information Storage System Administrator Guide, February 2005 5-1
Chapter 5: Configuring Outlook or Lotus Notes Configuring your system for Exchange and Outlook Configuring your system for Exchange and Outlook This section contains information about these topics: • Configuring user accounts on customer servers, on page 5-2 • Configuring Journal Mining, on page 5-3 • Configuring Mailbox Mining, on page 5-5 • Installing the Outlook plug-in, on page 5-8 Configuring user accounts on customer servers Table 5-1 illustrates how to configure user accounts for Selective Archiv
Configuring your system for Exchange and Outlook Chapter 5: Configuring Outlook or Lotus Notes Table 5-1: User accounts on customer servers (continued) For User type and mailbox location Default last name, user logon (password), aliasa Journal Mining Active Directory user and mailbox on Exchange servers LocalJournalUser, User LocalJournalUser (skyline); alias=LocalJournalUser Dynamic Account Synchronization Active Directory user on servers where user accounts exist appuser, appuser (skyline) [or a
Chapter 5: Configuring Outlook or Lotus Notes Configuring your system for Exchange and Outlook Table 5-2: User accounts for Journal Mining For User type and mailbox location Default last name, user logon (password), aliasa Selective archiving Domain user and mailbox on Exchange servers Appuser, appuser Administrators, (skyline); alias=appuser Exchange Domain Servers a. Group membership or permissions The same user account can be used for more than one of these activities.
Configuring your system for Exchange and Outlook Chapter 5: Configuring Outlook or Lotus Notes b. Open a Storage Group. c. Right-click Mailbox Store, and select Properties. d. Click General. e. Select Archive all messages sent or received by mailboxes in this store. f. Click Browse. g. Select journal user and mailbox where messages from the mailbox store are copied. h. Click OK twice. i. Repeat step b through step h for each Storage Group on the server. 10.
Chapter 5: Configuring Outlook or Lotus Notes Configuring your system for Exchange and Outlook Configuring Exchange for email stub support Before publishing the Outlook template, generate a forms registry so the Outlook form can be published to the system. This procedure requires you or the Exchange administrator to log on the Exchange server with administrator permissions. 1. Log on the Exchange server as Administrator. 2.
Configuring your system for Exchange and Outlook Chapter 5: Configuring Outlook or Lotus Notes 2. Run Outlook using the profile created. 3. In Outlook, select Tools > Forms > Design a Form. 4. From the Look In list in the Design Form dialog box, select User Templates in File System. 5. Click Browse, and select the drive containing the RISS Utilities CD, select the Exchange folder, and select the PERSISTMailItem form (PERSISTMailItem.oft). Click OK.
Chapter 5: Configuring Outlook or Lotus Notes Configuring your system for Exchange and Outlook 6. Close the EMS Scheduler application. 7. Restart the Launch Manager service to make the new setting take effect. Repeat this procedure as needed for all Mailbox Mining events. Installing the Outlook plug-in The HP RISS Outlook plug-in is a “COM Add-In” for Microsoft’s Outlook application.
Configuring your system for Exchange and Outlook Chapter 5: Configuring Outlook or Lotus Notes CacheEML=True: The default is True, which indicates the intermediate .eml file is cached for the message being retrieved from RISS. Setting this to False causes the .eml file to be deleted when it is no longer needed. This setting is ignored if UseCache=False. This is a userconfigurable setting. CacheMsg=True: The default is True, which indicates the resultant .
Chapter 5: Configuring Outlook or Lotus Notes Configuring your system for Exchange and Outlook administrator/diagnostic setting and should be modified only at the direction of Support Personnel. DefaultFolder=Default: Name of folder within generated PST files into which the Message Export Facility downloads archived messages. This is a user-configurable setting. PSTFileFolder=C:\PSTFiles: File system folder used to store individual PST Files when UseExternalFolderSupport=True.
Configuring your system for Exchange and Outlook Chapter 5: Configuring Outlook or Lotus Notes LogFilePath=: Fully-qualified path name where the plug-in records diagnostic information. This is an administrator/diagnostic setting and should be modified only at the direction of Support Personnel. Manually creating other registry settings To repackage the installation for deployment with Software Management Server (SMS) or other client management tool, components must be registered.
Chapter 5: Configuring Outlook or Lotus Notes Configuring your system for Exchange and Outlook To properly install the plug-in for users other than the administrator who installs it, make the following settings in HKLM: • [HKLM\Software\Microsoft\Office\Outlook\Addins\ PTOutlookArchive.
Configuring your system for Exchange and Outlook Chapter 5: Configuring Outlook or Lotus Notes Note: For more information about the Archive Options panel of the Options dialog box, see the “System administrator tasks” section of the user guide.
Chapter 5: Configuring Outlook or Lotus Notes Configuring your system for Domino and Lotus Notes Configuring your system for Domino and Lotus Notes This section contains information about configuring your system to enable Lotus Notes selective archiving.
Configuring your system for Domino and Lotus Notes Chapter 5: Configuring Outlook or Lotus Notes Installing Email Miner for Lotus Notes The Email Miner for Lotus Notes is an application (miner.nsf) loaded to and signed by the Domino Servers. Your HP installer performed the initial installation on the HP Gateway server. See Email Miner Version P2.0 for Lotus Notes Installation Guide, on page A-1, for more information. Administering Email Miner for Lotus Notes See Email Miner Version P2.
Chapter 5: Configuring Outlook or Lotus Notes Configuring your system for Domino and Lotus Notes LO 5-16 HP StorageWorks Reference Information Storage System Administrator Guide, February 2005
APPENDIX A Email Miner Version P2.0 for Lotus Notes Installation Guide This appendix contains the following information.
Appendix A: Email Miner Version P2.0 for Lotus Notes Installation Guide Overview Overview Email Miner is a Lotus Notes mail administration product that mines documents from mail databases and/or journal databases and places the documents within the RISS architecture. Architecture The Email Miner databases must be installed on every mail server that requires processing.
Overview Appendix A: Email Miner Version P2.0 for Lotus Notes Installation Guide Question Answer Does Email Miner update my Name and Address Book? No. All Name and Address Book accesses are references (read) only. Does Email Miner update my notes.ini? No. There are no .ini settings required. How does Email Miner work with clustered servers? Clustering does not affect Email Miner.
Appendix A: Email Miner Version P2.0 for Lotus Notes Installation Guide Overview Migration Question Answer What must I do when I migrate my servers from R5 to R6? Nothing. The same version of Email Miner can process on an R5 or an R6 server. What must I do when I migrate my servers' operating systems? Nothing. There is only one code-stream for Email Miner.
Appendix A: Email Miner Version P2.0 for Lotus Notes Installation Guide Overview Question Answer Must I upgrade every server (replica) of Email Miner? No. The upgrade only needs to be performed on one server, providing that the Email Miner database can properly replicate to all other replicas. What happens to the Email Miner data when I upgrade? Nothing. All of the data remains intact. Will I need to re-sign the agents after upgrading? No.
Appendix A: Email Miner Version P2.0 for Lotus Notes Installation Guide Overview • Set 'Max LotusScript execution time' to at least 120 minutes.
Email Miner Appendix A: Email Miner Version P2.0 for Lotus Notes Installation Guide Email Miner Installation The installation database MUST be located on a Lotus Notes server and can reside in any directory within the Notes data structure. Note: If Email Miner already exists on the installation server, the installation database MUST be located within the directory where Email Miner resides.
Appendix A: Email Miner Version P2.0 for Lotus Notes Installation Guide Email Miner 2. Specify the values – Use Servers to specify the servers where Email Miner is to be installed. Note: This field will be automatically populated with the name of the server where the Installation database resides. – Use Managers to specify the entries that are to be placed into the ACL as 'Manager' within the Email Miner databases.
Email Miner Appendix A: Email Miner Version P2.0 for Lotus Notes Installation Guide 1. Select Actions | 2. Additional Servers Installation Figure A-2: Additional Servers installation 2. Specify the values – Use Servers to specify the servers where Email Miner is to be installed. – Use Options to specify the installation options. Select Automatically create replicas if you want to create the Email Miner replicas during the installation.
Appendix A: Email Miner Version P2.0 for Lotus Notes Installation Guide Email Miner 3. Install – Click Install to begin the installation. The installation process will display the tasks being performed. The results from this process are saved within the installation database. Upgrade The installation database MUST be located on a Lotus Notes server and MUST be placed within the directory where Email Miner currently resides. The upgrade will replace the existing design of Email Miner.
Appendix A: Email Miner Version P2.0 for Lotus Notes Installation Guide Email Miner 2. Upgrade – Click Upgrade to begin the upgrade. The upgrade process will display the tasks being performed. The results from this process are saved within the installation database. Note: When the 'Replace Design' dialog box appears, be sure to select the 'Email Miner' (miner.ntf) template for the 'miner.nsf' database, and the 'Email Miner Reference' (referenc.ntf) template for the 'referenc.nsf' database.
Appendix A: Email Miner Version P2.0 for Lotus Notes Installation Guide Error messages Error messages The Installation database can generate numerous error messages. Each error message is categorized as either 'expected' or 'unexpected'. An 'expected' error is caused by a configuration problem within the installation database. Email Miner generates all 'expected' errors and each error will begin with 'ERRxxxx' (where 'xxxx' is the specific error number).
Error messages Appendix A: Email Miner Version P2.0 for Lotus Notes Installation Guide Table A-1: Installation Error Messages (continued) Error number Error message Cause Action ERR0004 Unable to delete 'xxx\miner.nsf' The Email Miner database 'xxx\miner.nsf' (where 'xxx' is the directory structure) is either locked by another process or you do not have sufficient access to delete the database.
Appendix A: Email Miner Version P2.0 for Lotus Notes Installation Guide Error messages Table A-1: Installation Error Messages (continued) Error number Error message Cause Action ERR0008 Could not find agent 'Email Miner Tombstone' The installation cannot find the agent ('Email Miner Tombstone') needed to create the server-specific agents. Contact HP technical support. ERR0009 Insufficient access to 'xxx\miner.
APPENDIX B Email Miner Version P2.
Appendix B: Email Miner Version P2.0 for Lotus Notes Administration Guide Email Miner Email Miner Overview Email Miner uses Mail Restrictions to locate the documents that are to be placed within the RISS architecture. Information for each document that matches the specified criteria is added to the Email Miner reference database. This information is then used to place the document within the RISS. Security Below is a table that describes how Email Miner is secured.
Email Miner Appendix B: Email Miner Version P2.0 for Lotus Notes Administration Guide Mail server configuration There are two components for every mail server. • Server Definition The Server Definition defines the characteristics of each mail server. A Server Definition will automatically be created for each mail server during the Email Miner Installation. Each mail server must be included on a Server Definition and if one does not exist, Email Miner will email the administrators of the problem.
Appendix B: Email Miner Version P2.0 for Lotus Notes Administration Guide Email Miner To create and complete a new Server Definition, perform the following steps: 1. Select Create | Administration | 1. Server Definition Figure B-1: Server Definition 2. Specify the 'Basics' values – Use Servers to specify the servers that should be included within the Server Definition. All servers within the same Server Definition will have the same characteristics/properties.
Email Miner Appendix B: Email Miner Version P2.0 for Lotus Notes Administration Guide Figure B-2: Processing options – Use RISS email address to specify the email address for the RISS. – Use Maximum queue size to specify the maximum number of messages that can be queued before no more messages are sent to the RISS. – Use Options to specify the processing options to be used when Email Miner encounters an error while processing.
Appendix B: Email Miner Version P2.0 for Lotus Notes Administration Guide Email Miner Use From to specify the sender of the email. Use Subject to specify the subject of the email. Use Message to specify the message (instructions) for the user. Figure B-3: Message and Title fields Use Title to specify the title of the user's confirmation dialog box that displays upon a successful deployment.
Email Miner Appendix B: Email Miner Version P2.0 for Lotus Notes Administration Guide Select Verbose if you want Email Miner to log information per mail user processed. This will also log the start and end times for each mail database, as well as the restriction being applied to each user. Select Extensive if you want Email Miner to log information per mail user processed. This will log more information for each mail user.
Appendix B: Email Miner Version P2.0 for Lotus Notes Administration Guide Email Miner Figure B-6: Server Status This view displays the server name, the last start/end time and what processes were executed. If opened during the execution of Email Miner, you will see the mail user currently being processed within the 'Process Information' column. The mail users are processed alphabetically (by first name/ last name).
Email Miner Appendix B: Email Miner Version P2.0 for Lotus Notes Administration Guide Mail user configuration Email Miner will only manage the mail users that have a Mail User Information document within the Email Miner database. If a document does not exist for a mail user within Email Miner, the mail database will NOT be processed. There are two ways to create Mail User Information documents within Email Miner.
Appendix B: Email Miner Version P2.0 for Lotus Notes Administration Guide Email Miner Select By specifics to import the users using specific group/user names. Use Options to specify the import options. Select Include mail-in databases to import mail-in database documents. Select Include resource databases to import resource database documents. Select Use debug logging to create additional logging information during the import process. This does not affect the import processing.
Email Miner Appendix B: Email Miner Version P2.0 for Lotus Notes Administration Guide Synchronize with Address Book This is an automated process that allows you to specify what mail users should be automatically synchronized. You can specify if you want to add, delete and/or update the Mail User Information. The Name and Address Book is used as a reference only, and will NOT be updated by this process.
Appendix B: Email Miner Version P2.0 for Lotus Notes Administration Guide Email Miner – Use Actions to specify what should occur within the Mail User Information documents. Select Create to automatically create Mail User Information documents when a new address book document has been created. Select Delete to automatically delete Mail User Information documents when a corresponding address book document no longer exists.
Email Miner Appendix B: Email Miner Version P2.0 for Lotus Notes Administration Guide 2. Enable the Synchronization Agent You must enable the Email Miner Synchronization agent. If the agent is not enabled, the synchronization process will not occur. Make sure that you specify the server on which the Email Miner Synchronization agent is to run. You may choose any server on which this agent is to run, but it is recommended that you specify the server where the administrators make address book changes.
Appendix B: Email Miner Version P2.0 for Lotus Notes Administration Guide Email Miner maximum age for the documents, thus managing any document that is older than the maximum age. 3. Size - The administrator can manage the documents by the document size. Within the document restriction, the administrator would specify the maximum size for the documents, thus managing any document that is larger than the maximum size.
Appendix B: Email Miner Version P2.0 for Lotus Notes Administration Guide Email Miner Select Enabled to activate the Mail Restriction. This will allow the Mail Restriction to be processed by the Email Miner agent. Select Disabled to deactivate the Mail Restriction. – Use Title to specify a title for the Mail Restriction. This value does not affect processing. – Use Priority to specify the priority of the Mail Restriction.
Appendix B: Email Miner Version P2.0 for Lotus Notes Administration Guide Email Miner Figure B-12: Basics – Use Method to specify if the documents should be managed. – Use Type to specify how to locate the documents. Select Content to locate using keywords/phrases. Select Retention to locate using the document age. Select Size to locate using the document size. – Use Retention method to specify how to determine the age of the documents.
Appendix B: Email Miner Version P2.0 for Lotus Notes Administration Guide Email Miner Figure B-13: Content – Use Syntax to specify the keywords/phrases to be used. b. Size Figure B-14: Size – Use Size to specify the threshold size for the documents. Any document larger than this size will be mined. – Use Options to specify the size options. Select Include documents with attachments to include documents that contain attachments. 3.
Appendix B: Email Miner Version P2.0 for Lotus Notes Administration Guide Email Miner Figure B-16: Exclude folders – Select Include calendar entries to include calendar entries. – Select Include foldered to include documents that exist in personal folders. – Select Include protect from archive to include documents that are protected from archiving. – Select Include stationery to include stationery documents. – Select Include tasks to include todos.
Email Miner Appendix B: Email Miner Version P2.0 for Lotus Notes Administration Guide Users Figure B-18: Users – Use User specification to specify what users are to use the restriction. Select All to specify all users. Select Exclude for all users, except for specified users. Select Include for specified users only. – Use Users to specify the users. The administrators can enter groups (nested groups), OU structures and/or explicit user names.
Appendix B: Email Miner Version P2.0 for Lotus Notes Administration Guide Error messages Error messages Email Miner can generate numerous error messages. Each error message is categorized as either 'expected' or 'unexpected'. An 'expected' error is caused by a configuration problem within Email Miner, the mail databases, or address Book. Email Miner generates all 'expected' errors. An 'unexpected error' is caused when Email Miner encounters an error from LotusScript that was not expected.
Error messages Appendix B: Email Miner Version P2.0 for Lotus Notes Administration Guide The Email Miner Agent MUST execute via a schedule This will occur if you attempt to manually execute the Email Miner scheduled agents. Schedule the agent. Email notifications Email Miner could generate emails when a severe problem occurs. The error is placed into the subject of the email. The emails are automatically sent to whoever has 'Manager' rights to the Email Miner database.
Appendix B: Email Miner Version P2.0 for Lotus Notes Administration Guide Error messages Table B-1: Email Miner Log Messages B-22 Log message number Log message Cause Action ERR0001 Could not find Server Definition for 'xxx' The Server Definition for the specified server ('xxx') cannot be found within Email Miner. Contact HP technical support. ERR0011 Could not find view 'Mail Restrictions' The 'Mail Restrictions' view cannot be found within the Email Miner database.
Error messages Appendix B: Email Miner Version P2.0 for Lotus Notes Administration Guide Table B-1: Email Miner Log Messages (continued) Log message number Log message Cause Action ERR0017 Could not find view '($VIMGroups)' in Public Name and Address Book The '($VIMGroups)' view cannot be found within the address book. Contact HP technical support. ERR0018 Could not open Reference database The reference database is not available to be used. Contact HP technical support.
Appendix B: Email Miner Version P2.0 for Lotus Notes Administration Guide Error messages Table B-1: Email Miner Log Messages (continued) Log message number Log message Cause Action ERR0023 Could not find mail database for 'xxx' (yyy) The mail database for a user (where xxx is the user name and yyy is the file path) could not be located. Ensure that the mail database has not been moved/ deleted.
Error messages Appendix B: Email Miner Version P2.0 for Lotus Notes Administration Guide Table B-1: Email Miner Log Messages (continued) Log message number Log message Cause Action ERR0027 Stopped processing folder 'xxx' (Error encountered) A 'Bad document ID/key' error occurred while processing a folder during 'Content' processing. Contact HP technical support.
Appendix B: Email Miner Version P2.
INDEX ABCDEFGHIJKLMNOPQRSTUVWXYZ A access control lists.
commands, PCC external 2-143 host 2-128 hostgroup 2-123 overriding 2-143 process 2-69 service 2-133, 2-135 View Config view 2-112 comments host 2-131, 2-144 service 2-133, 2-139 user 3-18 view 2-63 COMPLETE_PROCESSING smart cell state, definition 2-13 conditions, status definition 2-12 hard and soft 2-15 contacts 2-110 CRITICAL service status value, definition 2-15 D DAS configuring 2-28 displaying configuration associations 2-33 displaying servers 2-35 starting or scheduling jobs 2-34 data archiving, defi
Index security B-2 Server Definition B-3 Server options B-18 Server Status B-7 upgrading A-4, A-10 user configuration B-9 User options B-19 enabling notifications 2-144 error messages Email Miner administration B-20 Email Miner installation A-12 event log Alert History view 2-97 Notifications view 2-89 rotation 2-69, 2-92 Exchange server 2-42 Exchange, Microsoft journal mining 5-3 mailbox mining 5-5 non-sticky ports 5-7 publishing forms 5-6 stub support 5-6 user accounts 5-2 External Command Interface view
hosts Availability view 2-85 commands 2-128 comments, adding 2-131 downtimes, scheduling 2-130 Host Detail view 2-56 Host Information view 2-126 notifications 2-129, 2-130 problems, viewing 2-62 service checks 2-131 Service Detail view 2-53 Service Overview view 2-58 software version, viewing 2-106 Status Grid view 2-141 status, displaying 2-18 Tactical Monitoring view 2-51 Trends view 2-81 View Cell Space view 2-113 View Config view 2-107 HP StorageWorks Reference Information Storage System, definition 1-2
Index MBean components Agent view 2-118 MBean view 2-117 MBean view 2-117 menus, PAM 3-4 MetaServer, View Cell Space view 2-113 Microsoft Exchange journal mining 5-3 mailbox mining 5-5 non-sticky ports 5-7 publishing forms 5-6 stub support 5-6 user accounts 5-2 Microsoft Outlook plug-in, installing 5-8 Mining Overview view 2-42 monitoring, PCC 2-11, 2-50 N Nagios Info view 2-68 Nagios Stats view 2-71 non-sticky ports, configuring 5-7 notifications Alert Histogram view 2-94 Alert History view 2-97 Alert Su
logging in 3-3 menus 3-4 modifying objects 3-10 modifying routing filters 3-38 modifying routing rules 3-30 profiles, user 3-26 removing ACLs from repositories 3-22 removing collection object members 3-13 Repositories tab 3-9 repositories, creating, modifying, deleting 3-19 Routing Filters panel 3-34 Routing Rules panel 3-27 Simple Routing Rules panel 3-31 user accounts 3-2 Users panel 3-14 users, adding to ACLs 3-25 users, removing from ACLs 3-25 viewing ACL information 3-24 viewing objects 3-8 viewing rep
Index Scheduling Queue view 2-73 service checks 2-125, 2-131, 2-138 Service Detail view 2-53 Service Information view 2-133 service notifications 2-136 Service Overview view 2-58 Service Problems view 2-61 smart cell life cycle states 2-13 states 2-12 status conditions 2-12 Status Grid view 2-141 Status Summary view 2-17 System Backup view 2-46 System Status view 2-20 Tactical Monitoring view 2-50 text-summary reports 2-79 Tivoli Console 2-49 Trends view 2-81 updating views 2-7 user interface 2-4 User Mana
creating, modifying, deleting 3-19 definition 3-2 filtering list of 3-20 removing ACLs 3-22 routing rules 3-30 simple routing rules 3-33 viewing information 3-21 Repositories tab, PAM 3-9 Repository ID 3-34 requirements Email Miner A-5 PST Importer 4-4 rescheduling services 2-74 RESET smart cell state, definition 2-13 restarting servers 2-25 RESTORE smart cell state, definition 2-14 restoring data on failed smart cells 2-116 retention file 2-108, 2-110 RIM, application programs for users 1-3 RISS applicatio
Index Service Overview view, PCC 2-58 Service Problems view 2-61 Service Status Totals 2-17, 2-18, 2-56 services commands 2-133, 2-135 comments 2-139 Status Grid view 2-141 Trends view 2-81 View Config view 2-109 signature backup, definition 2-46 Signatures panel 2-47 Simple Routing Rules panel 3-31 smart cells active groups 2-48 cloning 2-36 domain 2-20 domain-affiliated 2-115 groups 2-23 lost 2-20, 2-113 MBeans 2-119 primary 2-115 replication, used for 2-115 restoring data on 2-116 secondary 2-115 state,
UNREACHABLE host status value, definition 2-15 UP host status value, definition 2-14 upgrading Email Miner A-4, A-10 User Management view 2-28 users accounts 3-2 adding new 3-17 adding to ACLs 3-25 comments, modifying 3-18 email information, modifying 3-17 Email Miner B-9 filtering list of 3-16 Microsoft Exchange 5-2 Outlook plug-in 5-12 PCC management 2-28 profiles 3-26 removing from ACLs 3-25 Users panel 3-14 viewing information 3-16 Users panel 3-14 V value, status definition 2-12 normal values 2-14 ver
