1. Manuals
  2. Brands
  3. Novell Manuals
  4. Software
  5. GROUPWISE 7 - SECURITY POLICIES
  6. Manual

Novell GROUPWISE 7 - MONITOR Manual

Hide thumbs Also See for GROUPWISE 7 - MONITOR:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Troubleshooting Manual, Manual
Monitor
X I I I
Chapter 58, "Understanding the Monitor Agent Consoles," on page 965
Chapter 59, "Configuring the Monitor Agent," on page 969
Chapter 60, "Configuring the Monitor Application," on page 991
Chapter 61, "Using GroupWise Monitor," on page 997
Chapter 62, "Comparing the Monitor Consoles," on page 1021
Chapter 63, "Using Monitor Agent Switches," on page 1023
XIII
Monitor
963

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the GROUPWISE 7 - MONITOR and is the answer not in the manual?

Questions and answers

Related Manuals for Novell GROUPWISE 7 - MONITOR

Summary of Contents for Novell GROUPWISE 7 - MONITOR

  • Page 1 XIII Monitor X I I I Chapter 58, “Understanding the Monitor Agent Consoles,” on page 965 Chapter 59, “Configuring the Monitor Agent,” on page 969 Chapter 60, “Configuring the Monitor Application,” on page 991 Chapter 61, “Using GroupWise Monitor,” on page 997 Chapter 62, “Comparing the Monitor Consoles,”...
  • Page 2 964 GroupWise 7 Administration Guide...

  • Page 3: Understanding The Monitor Agent Consoles

    Understanding the Monitor Agent Consoles The Monitor Agent offers three consoles: Section 58.1, “Monitor Agent Server Console,” on page 965 Section 58.2, “Monitor Agent Web Console,” on page 965 Section 58.3, “Monitor Web Console,” on page 966 For a comparison of the capabilities of the three consoles, see Chapter 62, “Comparing the Monitor Consoles,”...

  • Page 4: Monitor Web Console

    Monitor Agent Web Console Figure 58-2 To create the Monitor Agent Web console display, your Web server communicates directly with the Monitor Agent to obtain agent status information. You must be behind your firewall to use the Monitor Agent Web console. Because the Linux Monitor Agent does not have a server console, you use the Monitor Agent Web console in its place on Linux.
  • Page 5 Monitor Web Console Figure 58-3 To create the Monitor Web console display, your Web server communicates with the Monitor Application (a component of your Web server), which then communicates with the Monitor Agent to obtain agent status information. This enables the Monitor Web console to be available outside your firewall, while the Monitor Agent Web console can be used only inside your firewall.
  • Page 6 968 GroupWise 7 Administration Guide...

  • Page 7: Configuring The Monitor Agent

    Configuring the Monitor Agent ® For detailed instructions about installing and starting the GroupWise Monitor Agent for the first time, see “Installing GroupWise Monitor” in the GroupWise 7 Installation Guide. ® The default configuration of the GroupWise Monitor Agent is adequate to begin monitoring existing GroupWise agents (Post Office Agents, Message Transfer Agents, Internet Agents, and WebAccess Agents).
  • Page 8 The following topics help you customize the Monitor Agent for your specific needs: Section 59.1, “Selecting Agents to Monitor,” on page 970 Section 59.2, “Creating and Managing Agent Groups,” on page 973 Section 59.3, “Configuring Monitoring Protocols,” on page 975 Section 59.4, “Configuring Polling of Monitored Agents,”...

  • Page 9: Adding All Agents On A Server

    The Filtered Out list displays all agents that are not currently being monitored. 2 Select one or more agents in the Monitored list, then click Remove to move them to the Filtered Out list. 3 Click OK. Agents in the Filtered Out list are not monitored and do not appear at the Monitor Agent server console or at the Monitor Agent Web console.

  • Page 10: Adding An Individual Agent

    On Linux, at the Monitor Agent Web console, click Preferences > Add Agents. 2 Type the subnet portion of the IP addresses of the new servers, then click OK. All GroupWise agents on the subnet are added to the list of monitored agents. If the new servers are part of your local GroupWise system, you can simply restart the Monitor Agent and it picks up all new agents in your system.

  • Page 11: Creating And Managing Agent Groups

    59.2 Creating and Managing Agent Groups You might find it convenient to group related agents together for monitoring purposes. Initially, all agents are in a single group with the same name as your GroupWise system. Monitor Agent Console on Initial Startup Figure 59-3 Agent groups are displayed on the left side of the Monitor Agent server console.

  • Page 12: Creating An Agent Group

    NOTE: On Linux, you perform these tasks at the Monitor Agent Web console Monitor Web console, using steps similar to those provided in this section 59.2.1 Creating an Agent Group At the Windows Monitor Agent server console: 1 Right-click the folder where you want to create the agent group, then click Create. 2 Type a name for the group, then click OK to create a new folder for the agent group.

  • Page 13: Configuring An Agent Group

    Monitor Agent Server Console with Subgroup Agents Displayed Figure 59-5 Numbers in brackets beside each group indicate the number of agents in the selected group and the total number displayed 59.2.4 Configuring an Agent Group Configuration settings for monitoring can be set individually for each monitored agent, for each agent group, or for all monitored agents collectively.
  • Page 14 2 Modify the HTTP settings as needed: HTTP Refresh: Specify the number of seconds after which the Monitor Agent sends updated information to the Monitor Web console. The default is 300 seconds (5 minutes). HTTP Port: Specify the port number for the Monitor Agent to listen on for requests for information from the Web console.

  • Page 15: Configuring The Monitor Agent For Snmp

    Poll Cycle: Specify the number of seconds after which the Monitor Agent polls all monitored GroupWise agents for updated information. By default, the Monitor Agent starts 20 threads to poll monitored agents. You can use the pollthreads startup switch to adjust the number of threads. For more information, see Chapter 63, “Using Monitor Agent Switches,”...

  • Page 16: Configuring Polling Of Monitored Agents

    2 Specify the number of seconds after which the Monitor Agent polls all monitored GroupWise agents for updated information using SNMP. 3 In the SNMP box, modify the SNMP settings as needed: Time Out: Specify the number of seconds the Monitor Agent should wait for a response from servers where GroupWise agents run.

  • Page 17: Configuring E-Mail Notification

    2 Click Configuration > Poll Settings. At the Linux Monitor Agent Web console, select one ore more agents, click Preferences > Setup, then scroll down to the HTTP Settings section. Unless you selected the root agent group, Use Parent Notification Options is selected and all options are dimmed.
  • Page 18 On Linux, at the Monitor Agent Web console, select one or more agents, then click Preferences > Setup to display the Notify settings. Unless you selected the root agent group, Use Parent Notification Options is selected and all options are dimmed. Deselect Use Parent Notification Options to set up e-mail notification for an agent group or an individual agent.

  • Page 19: Customizing Notification Thresholds

    9 To monitor the Monitor Agent and assure it is functioning normally, select Periodic Monitor Confirmation, then select the number of minutes between Monitor Agent e-mail confirmation messages. 10 Click OK to save the e-mail notification settings. 59.5.2 Customizing Notification Thresholds To refine the types of events that trigger e-mail notification messages, you can create your own thresholds that describe very specific states.
  • Page 20 8 In the State field, select an existing state. Icon State Unknown Normal Informational Marginal Warning Minor Major Critical Create a new state: 8a At the Windows Monitor Agent server console, click Define State On Linux, at the Monitor Agent Web console, click Preferences >...
  • Page 21 59.6 Configuring Audible Notification for Agent Problems If the server where the Monitor Agent runs is located where someone can respond immediately to a GroupWise agent problem, you can configure the Monitor Agent to produce a different sound according to the nature of the problem. NOTE: Audible notification is not available on Linux.

  • Page 22: Configuring Snmp Trap Notification For Agent Problems

    59.7 Configuring SNMP Trap Notification for Agent Problems The Monitor Agent can throw SNMP traps for use by the Management and Monitoring component ® ® of Novell ZENworks for Servers or any other SNMP management and monitoring program. At the Windows Monitor Agent server console: 1 Select the root agent group to set up SNMP trap notification defaults for all monitored agents.

  • Page 23: Configuring Authentication And Intruder Lockout For The Monitor Web Console

    Unless you selected the root agent group, Use Parent Notification Options is selected and all options are dimmed. Deselect Use Parent Notification Options to set up notification for an agent group or individual agent. 3 Select Send SNMP Traps, then click OK. 4 Make sure that the Monitor Agent is properly configured for SNMP, as described in Section 59.3.2, “Configuring the Monitor Agent for SNMP,”...

  • Page 24: Configuring Monitor Agent Log Settings

    2 In the Authentication box, select Require Authentication to Browse GW Monitor. 3 Fill in the fields: User Name: Provide a username for the Monitor Agent to prompt for when a user attempts to access the Monitor Web console. Password: Provide a password for the Monitor Agent to prompt for when a user attempts access.

  • Page 25: Configuring Proxy Service Support For The Monitor Web Console

    Log File Path: Specify the full path of the directory where the Monitor Agent writes its log files. The default log file location varies by platform. Linux: /var/log/novell/groupwise/gwmon Windows: c:\gwmon Maximum Event Log File Age: Specify the number of days you want Monitor Agent event log files to remain on disk before being automatically deleted.

  • Page 26: Monitoring Messenger Agents

    The default location of this file varies by platform. Linux: /opt/novell/groupwise/gwmonitor Windows: c:\novell\gwmonitor 2 Locate the following line: Provider.GWMP.Agent.Http.level=basic 3 Change it to: Provider.GWMP.Agent.Http.level=full The basic setting restricts use of the Monitor Web console to within a firewall, while the full setting allows use of the Web console both inside and outside a firewall.

  • Page 27: Supporting The Groupwise High Availability Service On Linux

    1 Click Configuration > Add Novell Messenger System. 2 Fill in the following fields in the GroupWise Monitor Startup dialog box or the Add Novell Messenger System dialog box: Novell Messenger System Object: Browse to and select the eDirectory container where you created the Messenger system.
  • Page 28 990 GroupWise 7 Administration Guide...

  • Page 29: Configuring The Monitor Application

    Configuring the Monitor Application ® During installation, the GroupWise Monitor Application is set up with a default configuration. However, you can use the information in the following sections to optimize the Monitor Application configuration: Section 60.1, “Modifying Monitor Application Environment Settings,” on page 991 Section 60.2, “Modifying Monitor Application Log Settings,”...

  • Page 30: Modifying Monitor Application Log Settings

    3 Modify the fields as needed: ® ® Configuration File: The Monitor Application does not have access to Novell eDirectory the GroupWise domain database (wpdomain.db). Therefore, ConsoleOne writes the application’s configuration information to the file specified in this field. By default, this is the gwmonitor.cfg file located in the Monitor Application’s home directory.
  • Page 31 3 Modify the log settings as needed: Log File Path: Specify the path to the directory where you want to store the log files. The default log file directory varies by platform. Linux: /var/log/novell/groupwise/gwmon Windows: directory at the root of the Web server novell\gwmonitor\logs Maximum Log File Age: Specify the number of days you want to retain the log files.

  • Page 32: Adding Or Removing Service Providers

    Log Language: Select the language in which you want information written to the log files. The list contains many languages, some of which the Monitor Application might not support. If you select an unsupported language, the information is written in English. Log Time Format: Choose from the following formats to use when the Monitor Application records dates and times in the log files: HH:mm:ss:SS, MM/dd: H:mm:ss.SS, or dd/MM: H:mm:ss.SS.

  • Page 33: Modifying Monitor Application Template Settings

    GroupWise Monitor. If you create your own templates, you need to place the templates in a new subdirectory in the template base directory. The default installation directory varies by platform. Linux: /var/opt/novell/tomcat/webapps/gw/WEB-INF/classes/com/novell/ gwmonitor/templates Configuring the Monitor Application 995...
  • Page 34 Applets URL: The Monitor Application does not currently use applets. Help URL: Specify the URL for the GroupWise Monitor Help files. The default installation directory is the com\novell\gwmonitor\help directory under the Web server’s document root directory. Enable Template Caching: To speed up access to the template files, the Monitor Application can cache the files in memory.

  • Page 35: Using Groupwise Monitor

    Using GroupWise Monitor For a review of the three Monitor Agent consoles, see Section 58, “Understanding the Monitor Agent Consoles,” on page 965. This section focuses on using the Windows Monitor Agent server console and the Monitor Agent Web console, although many of these tasks can be performed at the Monitor Web console as well.

  • Page 36: Viewing All Agents

    Windows Monitor Agent Console Figure 61-2 You can display many types of monitoring information at the Windows Monitor Agent server console. Section 61.1.1, “Viewing All Agents,” on page 998 Section 61.1.2, “Viewing Problem Agents,” on page 998 Section 61.1.3, “Viewing an Agent Server Console,” on page 999 Section 61.1.4, “Viewing an Agent Web Console,”...

  • Page 37: Viewing An Agent Server Console

    At the Windows Monitor Agent server console: 1 Click View > Problem Agents. On Linux, at the Monitor Agent Web console, click Problems. Only problem agents are now displayed. If you leave the Monitor Agent with only problem agents displayed, many groups might appear empty because all agents have a status of Normal. 2 To view all monitored agents again, click View >...

  • Page 38: Viewing An Agent Web Console

    61.1.4 Viewing an Agent Web Console An agent Web console can be displayed anywhere you have access to a Web browser and the Internet. You can launch an agent Web console from the Windows Monitor Agent server console. 1 Right-click an agent, then click Agent Web Console. On Linux, at the Monitor Agent Web console, click the domain or post office link.

  • Page 39: Using The Monitor Web Console

    The suspended agent’s status is listed as Suspended, accompanied by the same icon used for the Unknown status To restart regular polling of an agent for which polling was suspended, right-click the agent, then click Resume Polling. 61.2 Using the Monitor Web Console The Monitor Web console lists all GroupWise agents that the Monitor agent is polling for status information.

  • Page 40: Generating Reports

    Click an agent group in the left panel to display all monitored agents in the group. Click the Problem button to display only those agents whose status is other than Normal in the agent group. Click the Problems icon to display all agents in your GroupWise system whose status is other than Normal. Click the status of an agent in the Status column to display agent status details.

  • Page 41: Link Configuration Report

    2 Select a starting domain and a target domain. 3 If you want to trace the path back, which is the route status messages will take, select Trace Return Path. 4 Click Trace. If any domain in the path is closed, an error message displays so you know where the problem is occurring.

  • Page 42: Image Map Report

    The list shows what domains a message would pass through to travel from the domain in the Source column to the domain in the Destination column. If a domain displays as closed, it means that the Monitor Agent could not contact the MTA for the domain or that a loop was detected in the link configuration.
  • Page 43 You can change the location using the /monwork startup switch. For more information, see Chapter 63, “Using Monitor Agent Switches,” on page 1023 3 Continue with Setting Up Maps. Setting Up Maps 1 In the Monitor Agent Web console, click Map. Initially, no maps are available in Monitor.
  • Page 44 If your maps are all independent from each other, skip to “Adding Agents to a Map” on page 1007. Setting Up Regions If some of your maps are subsets of other maps, you can set up a large-scale map so that it links to one or more smaller-scale maps.
  • Page 45 7 To define more regions on the large-scale map, click Done to return to the available maps, then repeat Step 3 through Step 6 for each region. To place agents on a map, continue with Adding Agents to a Map. Adding Agents to a Map 1 In the Monitor Agent Web console, click Map to display the maps that are available in Monitor.
  • Page 46 5 In the Line Color drop-down list, select the color to use to show links between locations. Make sure you select a color that shows up well on the particular map. Lines display on the map only when links between locations are down. 6 Click Done when the map includes all the needed GroupWise agents in their respective locations.

  • Page 47: Environment Report

    An environment report lists all monitored agents, along with each agent’s location, version, IP ® address, port number, and operating system information. For NetWare agents, the server name, CLIB version, TCP/IP version, Novell eDirectory version, and the number of packet receive buffers are also listed. At the Windows...

  • Page 48: Link Traffic Report

    6 After the results are displayed, click Save, provide a filename for the report, select the format for the report, then click OK. Reports can be saved in comma-separated or tab-separated format to meet the needs of the program you plan to use to display and print the report. For example, you could bring the data into a spreadsheet program.

  • Page 49: Performance Tracking Report

    In addition, you need to determine the message ID of the message. Have the sender check the Sent Item Properties of the message in the GroupWise client. The Mail Envelope Properties field displays the message ID of the message; for example, 3AD5EDEB.31D : 3 : 12763. At the Windows Monitor Agent server console Monitor Agent Web...

  • Page 50: Down Time Report

    4 Select the MIB variables that you want to collect values for over time, then click Add Trend. The Trend report appears in the Agent Trends list. 5 Click the Trend report to view the graphs. 61.3.12 Down Time Report The Down Time report graphically illustrates how much time each GroupWise agent has been down during the day.

  • Page 51: Selecting An Mta To Communicate With The Monitor Agent

    described in Section 61.5, “Collecting Gateway Accounting Data,” on page 1015, you can use this same external domain for collecting accounting data. 2 Name the external domain to reflect its role in your GroupWise system. For example, you could name it ExternalMonitorDomain. It does not matter which domain you link the external domain to.

  • Page 52: Configuring The Monitor Agent For Agent Performance Testing

    61.4.3 Configuring the Monitor Agent for Agent Performance Testing After you have created an external Monitor domain and configured a link from it to an MTA, you are ready to configure the Monitor Agent for performance testing. At the Windows Monitor Agent server console: 1 Click Configuration >...

  • Page 53: Viewing An Agent Performance Report

    2 Select a history log file > click View. 61.4.5 Viewing an Agent Performance Report A performance testing report enables you to measure how long it takes messages to travel through your GroupWise system. The performance testing report lists each domain that a performance test message was sent to, when it was sent by the Monitor Agent, and the number of seconds between when it was sent and when the Monitor Agent received a response from the tested agent.
  • Page 54 For information about external GroupWise domains, see “Creating an External Domain” in “Connecting to GroupWise 5.x, 6.x, and 7.x Systems” in the GroupWise 7 Multi-System Administration Guide. If you are going to set up agent performance reports, as described in Section 61.4, “Measuring Agent Performance,”...

  • Page 55: Setting Up An External Post Office And External User For Monitor

    6 Continue with Setting Up an External Post Office and External User for Monitor. 61.5.3 Setting Up an External Post Office and External User for Monitor The setup for gateway accounting requires an external post office and an external user in the external domain.

  • Page 56: Viewing The Gateway Accounting Report

    Agent uses this data to generate gateway accounting reports. The accounting log files on stored on the server where the Monitor Agent is running. The default location varies by platform. Linux: /var/log/novell/groupwise/gwmon/acct Windows: c:\gwmon\acct 61.5.5 Viewing the Gateway Accounting Report After gateway accounting files are being successfully sent to the Monitor Agent for processing, you can view the Gateway Accounting report in your Web browser.

  • Page 57: Searching For Agents

    2 In the Assign To field, type the name of the GroupWise administrator who is responsible for this agent. The name is displayed to the right of the agent status in the status window of the Monitor Agent console and the Monitor Web console. 3 In the Notes box, type any comments you might have about the agent.
  • Page 58 NOTE: The Search feature is not available in the Windows Monitor Agent server console Monitor Agent Web console. 2 Type the name of an agent. Select Problems to list all agents whose status is other than Normal. Select one or more types of agent to list. 3 Select the number of instances you want listed at one time.

  • Page 59: Comparing The Monitor Consoles

    Comparing the Monitor Consoles Many aspects of agent monitoring are available in one or more of the Monitor Agent consoles. The table below summarizes agent monitoring features and where they are available. Windows Monitor Agent Server Monitor Agent Web Monitor Web Task Console Console...
  • Page 60 Link Traffic Report Message Tracking Report Performance Tracking Report Connected User Report Gateway Accounting Report Trends Report Down Time Report 1022 GroupWise 7 Administration Guide...
  • Page 61 Linux: If you start the Monitor Agent by running the gwmon executable, you can create a script like the following: /opt/novell/groupwise/agents/bin/gwmon --home /domain_directory -- other_switches & If you start the Monitor Agent by running the grpwise-ma script, you can edit the MA_OPTIONS variable to include any switches you want to set.
  • Page 62 Windows Monitor Agent Server Console --log /log Log > Log Settings > Log File Path --monwork /monwork --nmaddress /nmaddress Configuration > Add Novell Messenger System > Replica Address --nmhome /nmhome Configuration > Add Novell Messenger System > Novell Messenger System Object --nmpassword /nmpassword Configuration >...
  • Page 63 Linux Monitor Agent Windows Monitor Agent Syntax: --hapoll seconds /hapoll-seconds Example: --hapoll 240 /hapoll-60 See also /hauser and /hapassword. 63.3 /hauser Specifies the Linux username that the Monitor Agent can use to log in to the Linux server where the GroupWise High Availability service is running.
  • Page 64 Linux Monitor Agent Windows Monitor Agent Example: --home /gwsystem/provo2 /home-\provo2 /home-mail:\provo2 /home-server2\mail:\provo2 /home-\\server2\mail\provo2 /home-\provo2 /home-m:\provo2 /home-\\server2\c\mail\provo See also /ipa and /ipp. 63.6 /httpagentpassword Specifies the password for the Monitor Agent to prompt for when contacting monitored agents for status information. Providing a password is optional. See Section 59.3.1, “Configuring the Monitor Agent for HTTP,”...
  • Page 65 63.9 /httpmonpassword Specifies the password for the Monitor Web console to prompt for before allowing a user to display ® the Monitor Web console. Do not use an existing Novell eDirectory password because the information passes over the non-secure connection between your Web browser and the Monitor Agent.
  • Page 66 63.11 /httpport Sets the HTTP port number used for the Monitor Agent to communicate with your Web browser. The default is 8200; the setting must be unique. See Section 59.3.1, “Configuring the Monitor Agent for HTTP,” on page 975. Linux Monitor Agent Windows Monitor Agent Syntax: --httpport port_number...
  • Page 67 Linux Monitor Agent Windows Monitor Agent Syntax: --lang code /lang-code Example: --lang de /lang-fr The table below lists the valid language codes. Contact your local Novell sales office for information about language availability. Language Codes Table 63-1 Language Language Language Language...
  • Page 68 Linux Monitor Agent Windows Monitor Agent Syntax: --log /dir/file /log-[drive:]\dir\file /log-\\svr\sharename\dir\file Example: --log /opt/novell/groupwise/agents/logs /log-\gw\logs /log-m:\gw\logs /log-\\server2\c\gw\logs 63.17 /monwork Specifies the location where the Monitor Agent creates it working directory. The default location varies by platform. Linux: /tmp/gwmon Windows: c:\gwmon...
  • Page 69 63.19 /nmhome Specifies the context of the eDirectory container object where a Novell Messenger system is located. Section 59.11, “Monitoring Messenger Agents,” on page 988. Linux Monitor Agent Windows Monitor Agent Syntax: --nmhome eDirectory_context /nmhome-eDirectory_context Example: --nmhome /nmhome- OU=MessengerService,O=Messenger OU=MessengerService,OU=Provo,O=Novell See also /nmuser, /nmpassword, and /nmaddress.
  • Page 70 Linux Monitor Agent Windows Monitor Agent Syntax: --nosnmp /nosnmp 63.23 /pollthreads Specifies the number of threads that the Monitor Agent uses for polling the agents for status information. Valid values range from 1 to 32. The default is 20. See Section 59.4, “Configuring Polling of Monitored Agents,”...

This manual is also suitable for:

Groupwise 7 monitor agent

Table of Contents