1. Manuals
  2. Brands
  3. Novell Manuals
  4. Software
  5. GROUPWISE 8 - MONITOR
  6. Manual

Novell GROUPWISE 8 - MONITOR Manual

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

Advertisement

Quick Links

Download this manual See also: Troubleshooting Manual, Manual
Monitor
X I V
Chapter 62, "Understanding the Monitor Agent Consoles," on page 1003
Chapter 63, "Configuring the Monitor Agent," on page 1007
Chapter 64, "Configuring the Monitor Application," on page 1029
Chapter 65, "Using GroupWise Monitor," on page 1037
Chapter 66, "Comparing the Monitor Consoles," on page 1061
Chapter 67, "Using Monitor Agent Startup Switches," on page 1063
XIV
Monitor
1001

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Novell GROUPWISE 8 - MONITOR

Summary of Contents for Novell GROUPWISE 8 - MONITOR

  • Page 1 Monitor X I V Chapter 62, “Understanding the Monitor Agent Consoles,” on page 1003 Chapter 63, “Configuring the Monitor Agent,” on page 1007 Chapter 64, “Configuring the Monitor Application,” on page 1029 Chapter 65, “Using GroupWise Monitor,” on page 1037 Chapter 66, “Comparing the Monitor Consoles,”...
  • Page 2 1002 GroupWise 8 Administration Guide...

  • Page 3: Understanding The Monitor Agent Consoles

    Understanding the Monitor Agent Consoles The Monitor Agent offers three different consoles where you can check the status of your GroupWise agents: Section 62.1, “Monitor Agent Server Console,” on page 1003 Section 62.2, “Monitor Agent Web Console,” on page 1003 Section 62.3, “Monitor Web Console,”...

  • Page 4: Monitor Web Console

    Monitor Agent Web Console Figure 62-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 The Monitor Web console is divided into the Agent Groups window on the left and the Agent Status window on the right. Using the Agents Groups window, you can create and manage agent groups the same as you can at the Monitor Agent server console. The Monitor Web console does not include some features that are available at the Monitor Agent server console and the Monitor Agent Web console.
  • Page 6 1006 GroupWise 8 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 8 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 Monitor Agent Web Console on Linux Figure 63-2 The following topics help you customize the Monitor Agent for your specific needs: Section 63.1, “Selecting Agents to Monitor,” on page 1008 Section 63.2, “Creating and Managing Agent Groups,” on page 1011 Section 63.3, “Configuring Monitoring Protocols,”...

  • Page 9: Filtering The Agent List

    Section 63.1.2, “Adding All Agents on a Server,” on page 1009 Section 63.1.3, “Adding All Agents on a Subnet,” on page 1010 Section 63.1.4, “Adding an Individual Agent,” on page 1010 Section 63.1.5, “Removing Added Agents,” on page 1011 63.1.1 Filtering the Agent List You can configure the Monitor Agent to stop and start monitoring selected agents as needed.

  • Page 10: Adding All Agents On A Subnet

    2 Type the IP address of the new server, then click OK. All GroupWise agents on the new server are added to the list of monitored agents. If the new server is 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: Removing Added Agents

    2 Type the IP address of the server where the agent runs. 3 Type the port number the agent listens on. 4 Click OK. The agent is added to the list of monitored agents. 63.1.5 Removing Added Agents To stop monitoring agents that you have manually added to the Monitor Agent’s configuration: At the Windows Monitor Agent server console:...

  • Page 12: Creating An Agent Group

    Monitor Agent Console with Agent Groups Defined Figure 63-4 You can create additional groups and subgroups as needed to make monitoring similar agents easier. You might want to create agent groups based on geographical areas, on administrative responsibilities, or on agent configuration similarities. The number of agents in the group is displayed to the right of the group name in the agent groups window.

  • Page 13: Managing Agent Groups

    63.2.2 Managing Agent Groups Managing agent groups is easy at the Monitor Agent server console: To rename an agent group, right-click the agent group, click Rename, type the new name, then press Enter. To move an agent group, drag and drop it to its new location. To delete an agent group, right-click the agent group, then click Delete.

  • Page 14: Configuring Monitoring Protocols

    63.3 Configuring Monitoring Protocols By default, the Monitor Agent uses HTTP to communicate with the agents it monitors. If HTTP is not available, the Monitor Agent changes automatically to SNMP. GroupWise 8 agents, GroupWise 7 agents, GroupWise 6.x agents and 6.x-level gateways, as well as the GroupWise agents provided with the GroupWise 5.5 Enhancement Pack, can be monitored using HTTP.
  • Page 15 At the Windows Monitor Agent server console: 4 Click Configuration > Poll Settings. On Linux, at the Monitor Agent Web console, click Preferences > Setup, then scroll down to the HTTP Settings section. 5 Fill in the following fields: Poll Cycle: Specify the number of seconds after which the Monitor Agent polls all monitored GroupWise agents for updated information.

  • Page 16: Configuring The Monitor Agent For Snmp

    6 Select Apply options to subgroups if you want subgroups to inherit these settings. 7 Click OK to put the specified poll cycle into effect. 63.3.2 Configuring the Monitor Agent for SNMP The Monitor Agent must use SNMP to communicate with GroupWise agents that date from earlier than the GroupWise 5.5 Enhancement Pack.

  • Page 17: Configuring Polling Of Monitored Agents

    5 Click OK to put the new SNMP settings into effect. 6 Make sure the GroupWise agents you want to monitor using SNMP are enabled for SNMP. See Section 37.6.1, “Setting Up SNMP Services for the POA,” on page 555 Section 42.6.1, “Setting Up SNMP Services for the MTA,”...

  • Page 18: Configuring E-Mail Notification

    63.5 Configuring E-Mail Notification for Agent Problems The Monitor Agent can notify you by e-mail when agent problems arise. Section 63.5.1, “Configuring E-Mail Notification,” on page 1018 Section 63.5.2, “Customizing Notification Thresholds,” on page 1019 63.5.1 Configuring E-Mail Notification You can configure the Monitor Agent to notify one or more users by e-mail if an agent goes down. You can also receive e-mail confirmation messages showing that the Monitor Agent itself is still running normally.

  • Page 19: Customizing Notification Thresholds

    4 Specify the Internet domain name of your GroupWise system. 5 If the mail system to which e-mail notification is being sent performs reverse DNS lookups, specify the IP address or hostname of a server to relay the notification messages through. The Monitor Agent should relay e-mail notifications through a server that has a published DNS address.
  • Page 20 The tabs at the top of the dialog box enable you to create a separate threshold for each type of GroupWise agent. 4 Select the type of agent to create a threshold for. 5 In the Expression field, select a MIB variable. GroupWise agent MIB files are located in the directory of your GroupWise \agents\snmp...
  • Page 21 On Linux, at the Monitor Agent Web console, click Preferences > States. 8b Type a name for the new state. 8c Select a severity level. 8d Provide instructions about how to handle the new state. 8e Click Close to save the new state. 9 Click OK to create the new threshold.

  • Page 22: Configuring Snmp Trap Notification For Agent Problems

    63.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. 1022 GroupWise 8 Administration Guide...

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

    At the Windows Monitor Agent server console: 1 Select the root agent group to set up SNMP trap notification defaults for all monitored agents. Select any agent group to set up SNMP trap notification for the agents in the selected group. Select any agent to set up SNMP trap notification for that individual agent.

  • Page 24: Configuring Monitor Agent Log Settings

    NOTE: To limit access on Linux, use the --httpmonuser --httpmonpassword startup switches when you start the Monitor Agent. For more information, see Chapter 67, “Using Monitor Agent Startup Switches,” on page 1063 The intruder lockout functionality is not available on Linux. At the Windows Monitor Agent server console: 1 Click Configuration >...
  • Page 25 Linux: /var/log/novell/groupwise/gwmon Windows: c:\Program Files\Novell\GroupWise Server\Monitor 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. The default event log file age is 30 days.

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

    Monitor Agent to support proxy service. 1 In a text editor, open the Monitor Application configuration file ( gwmonitor.cfg The default location of this file varies by platform. Linux: /opt/novell/groupwise/gwmonitor Windows: c:\Novell\GroupWise\gwmonitor on the Web server 2 Locate the following line: Provider.GWMP.Agent.Http.level=basic...
  • Page 27 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: Supporting The Groupwise High Availability Service On Linux

    NOTE: On Linux, use the Preferences > Add Agents at the Monitor Agent Web console to add the individual Messenger agents to the list of monitored agents. For more information, see Section 63.1.4, “Adding an Individual Agent,” on page 1010. 63.12 Supporting the GroupWise High Availability Service on Linux The GroupWise High Availability service, described in...

  • Page 29: Modifying Monitor Application Environment Settings

    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 64.1, “Modifying Monitor Application Environment Settings,” on page 1029 Section 64.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 ( ). Therefore, ConsoleOne writes the wpdomain.db application’s configuration information to the file specified in this field. By default, this is the 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: on the Web server c:\Novell\GroupWise\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

    The verbose and diagnostic logging levels do not degrade Monitor Agent performance, but log files saved to disk consume more disk space when verbose or diagnostic logging is in use. 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.

  • Page 33: Modifying Monitor Application Template Settings

    3 Choose from the following options: Add: To add a service provider to the list, click Add, browse to and select the service provider’s object, then click OK. Edit: To edit a service provider’s information, select the provider in the list, then click Edit. Delete: To remove a service provider from the list, select the provider, then click Delete.
  • Page 34 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 template path is based on the Tomcat installation location and varies by platform: NetWare: sys:\tomcat\4\webapps\gwmon\WEB-INF\classes\templates OES Linux: /var/opt/novell/tomcat5/ webapps/gwmon/WEB-INF/classes/templates SLES: /srv/www/tomcat5/base/ webapps/gwmon/WEB-INF/classes/templates Windows: c:\Novell\GroupWise\Tomcat5.5\...
  • Page 35 Cache Size: Select the maximum amount of memory, in kilobytes, you want to use when caching the templates. The default cache size, 1024 KB, is sufficient to cache all templates shipped with GroupWise Monitor. If you modify or add templates, you can turn on Verbose logging on the Monitor Application object Log Settings page to view the size of the template files.
  • Page 36 1036 GroupWise 8 Administration Guide...

  • Page 37: Using Groupwise Monitor

    Using GroupWise Monitor For a review of the three Monitor Agent consoles, see Section 62, “Understanding the Monitor Agent Consoles,” on page 1003. 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 38: Viewing All Agents

    Windows Monitor Agent Console Figure 65-2 You can display many types of monitoring information at the Windows Monitor Agent server console. Section 65.1.1, “Viewing All Agents,” on page 1038 Section 65.1.2, “Viewing Problem Agents,” on page 1038 Section 65.1.3, “Viewing an Agent Server Console,” on page 1039 Section 65.1.4, “Viewing an Agent Web Console,”...

  • Page 39: 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 40: Viewing An Agent Web Console

    65.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 41: 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. 65.2 Using the Monitor Web Console The Monitor Web console lists all GroupWise agents that the Monitor agent is polling for status information.

  • Page 42: Generating Reports

    Click an agent in the Name column to open its agent Web console. For information about the agent Web consoles, see Section 65.1.4, “Viewing an Agent Web Console,” on page 1040. Click Refresh to update the agent status information. To modify the default poll cycle, see Section 63.4, “Configuring Polling of Monitored Agents,”...

  • Page 43: Link Configuration Report

    If any domain in the path is closed, an error message displays so you know where the problem is occurring. 5 When you are finished tracing links, click Close. 65.3.2 Link Configuration Report A link configuration report enables you to list the links from one or more GroupWise domains to all other domains in your GroupWise system.

  • Page 44: Image Map Report

    You can select from images in PNG and JPG format. 2 Copy the maps you want to use into the subdirectory of the directory. maps monwork The default location of the directory varies by platform. monwork Linux: /tmp/gwmon/monwork/maps Windows: c:\Program Files\Novell\GroupWise Server\Monitor\monwork\maps 1044 GroupWise 8 Administration Guide...
  • Page 45 You can change the location using the /monwork startup switch. For more information, see Chapter 67, “Using Monitor Agent Startup Switches,” on page 1063 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 46 If your maps are all independent from each other, skip to “Adding Agents to a Map” on page 1047. 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 47 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 48 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 49: 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 50: 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 51: Performance Tracking Report

    In addition, you need to determine the message ID of the message. Have the sender check the Sent Item Advanced Properties of the message in the GroupWise client. The Message Id 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 52: Down Time Report

    2 Click the type of agent for which you want to set up a Trend report. 3 Specify a unique name for the Trend 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.
  • Page 53 round-trip time for e-mail messages to travel to recipients and for status messages to travel back to senders. If you are going to set up gateway accounting reports, as described in Section 65.5, “Collecting Gateway Accounting Data,” on page 1055, you can use this same external domain for collecting accounting data.

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

    3b Specify a unique port number for the MTA to use to communicate with the Monitor Agent. 3c Click OK. 4 Click OK to save your changes to the link. 5 Exit the Link Configuration Tool to save the new link configuration information. 6 Continue with Section 65.4.3, “Configuring the Monitor Agent for Agent Performance Testing,”...

  • Page 55: Viewing Agent Performance Data

    65.4.4 Viewing Agent Performance Data The information gathered by the Monitor Agent through performance test messages is recorded in the Monitor history log. At the Windows Monitor Agent server console Monitor Agent Web console: 1 Click Log > View History Files. 2 Select a history log file, then click View.

  • Page 56: Setting Up An External Monitor Domain

    65.5.1 Setting Up an External Monitor Domain Before you can run a gateway accounting report, you must create a specially configured Monitor domain and select an MTA to transfer accounting data to and from the Monitor Agent. The Monitor Agent uses an external GroupWise domain as part of this process. ®...

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

    3a Click the pencil icon to provide the IP address of the server where the Monitor Agent runs. 3b Specify a unique port number for the MTA to use to communicate with the Monitor Agent. 3c Click OK. 4 Click OK to save your change to the link. 5 Exit the Link Configuration Tool to save the new link configuration information.

  • Page 58: Receiving The Accounting Files

    Linux: /var/log/novell/groupwise/gwmon/acc Windows: c:\Program Files\Novell\GroupWise Server\Monitor\acct 65.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. The Gateway Accounting report organizes information gathered in gateway accounting files into a format that is visually easy to read.

  • Page 59: Assigning Responsibility For Specific Agents

    65.6 Assigning Responsibility for Specific Agents If multiple GroupWise administrators manage the agents throughout your GroupWise system, you can assign a contact for each agent. Or, in a help desk environment, a person can be assigned to an agent when a problem occurs. The person assigned to the agent can record notes about the functioning of the agent, which are then available to other administrators.
  • Page 60 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 61: 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. Task Windows Monitor Monitor Agent Web Monitor Web Agent Server Console Console...
  • Page 62 Link Traffic Report Message Tracking Report Performance Tracking Report Connected User Report Gateway Accounting Report Trends Report Down Time Report 1062 GroupWise 8 Administration Guide...

  • Page 63: Using Monitor Agent Startup Switches

    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 script, you can edit the grpwise-ma MA_OPTIONS variable to include any switches you want to set.
  • Page 64 /lang --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 > Add Novell Messenger System >...
  • Page 65 the time during which the Monitor Agent is checking agent status and restarting agents as needed. Then the specified poll cycle begins again and continues for the specified number of seconds. See Section 63.12, “Supporting the GroupWise High Availability Service on Linux,” on page 1028.
  • Page 66 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. 67.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 63.3.1, “Configuring the Monitor Agent for HTTP,”...
  • Page 67 67.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 68 Linux Monitor Agent Windows Monitor Agent Syntax: --httpport port_number /httpport-port_number Example: --httpport 8201 /httpport-9200 67.12 /httpssl Enables secure SSL communication between the Monitor Agent and the Monitor Web console displayed in your Web browser. See Section 63.8, “Configuring Authentication and Intruder Lockout for the Monitor Web Console,”...
  • Page 69 --lang code /lang-code Example: --lang de /lang-fr Contact your local Novell sales office for information about language availability. See Chapter 7, “Multilingual GroupWise Systems,” on page 111 for a list of language codes. 67.16 /log Specifies the full path of the directory where the Monitor Agent writes its log files. The default...
  • Page 70 --nmaddress 172.16.5.18 /nmaddress-172.16.5.19 See also /nmuser, /nmpassword, and /nmhome. 67.19 /nmhome Specifies the context of the eDirectory container object where a Novell Messenger system is located. Section 63.11, “Monitoring Messenger Agents,” on page 1026. Linux Monitor Agent Windows Monitor Agent...
  • Page 71 Linux Monitor Agent Windows Monitor Agent Syntax: --nmuser eDirectory_context /nmuser-eDirectory_context Example: --nmuser CN=Admin,OU=Users,O=Novell /nmuser-CN=Admin,OU=Provo,O=Novell See also /nmpassword, /nmhome, and /nmaddress. 67.22 /nosnmp Disables SNMP for the Monitor Agent. The default is to have SNMP enabled. See Section 63.3.2, “Configuring the Monitor Agent for SNMP,” on page 1016.
  • Page 72 67.25 /tcpwaitconnect Sets the maximum number of seconds the Monitor Agent waits for a connection to a monitored agent. The default is 5. Linux Monitor Agent Windows Monitor Agent Syntax: --tcpwaitconnect seconds /tcpwaitconnect-seconds Example: --tcpwaitconnect 10 /tcpwaitconnect-15 1072 GroupWise 8 Administration Guide...

This manual is also suitable for:

Groupwise 8 monitor agent

Table of Contents