Home
Administering
This documentation provides information about the administration tools for HCL Domino.
Administering with Domino Administrator
This documentation provides information about the administration tools for managing and monitoring servers and databases.
Monitoring servers
This section describes how to use the tools and features that help you monitor a Domino® system.
The Domino® SNMP Agent
The Domino® SNMP Agent enhances the monitoring and control features of Domino by enabling third-party management stations, which use industry standard SNMP, to manage aspects of the Domino server.
Configuring the Domino® SNMP Agent
To configure the Domino® SNMP Agent, you perform a procedure specific to each platform and then complete the configuration by performing another procedure that applies to all platforms.
Configuring Master SNMP Agent for systemd
On the Linux™ platform, the Domino® SNMP Agent uses the SMUX protocol, per RFC 1227, to communicate with the system's Master SNMP Agent. Some Linux distributions include a Master SNMP Agent that supports the SMUX protocol; others do not.

Administering
This documentation provides information about the administration tools for HCL Domino.
- Administering with AdminCentral
  The AdminCentral application (admincentral.nsf) is automatically created by adminP on the Domino administration server. You can open AdminCentral directly from your Notes Standard or Nomad web client, without the need to start Domino Administrator. This application provides a simplified and easy-to-use way of managing fully functional Notes users and groups in a Domino deployment.
- Administering with Domino Administrator
  This documentation provides information about the administration tools for managing and monitoring servers and databases.
  - Administration tools
    Topics in this section describe the tools you can use to administer a Domino® server.
  - Managing users
    The Administration Process helps you manage users by automating many of the associated administrative tasks. For example, if you rename a user, the Administration Process automates changing the name throughout databases in the Notes® domain by generating and carrying out a series of requests, which are posted in the Administration Requests database.
  - Monitoring servers
    This section describes how to use the tools and features that help you monitor a Domino® system.
    - Monitoring the Domino® system
      You can monitor system activity and platform use using the Domino® Administrator or the server console.
    - Entitlement tracking
      As of Domino 12.0, a new internal mechanism is provided for collecting the highest entitlement that individual users have across a Domino domain. When a user appears in the ACL of a database with Reader access or above and that person has the right to access the server, the user is said to be an entitled user.
    - Domino® domain monitoring (DDM)
      Domino® domain monitoring (DDM) provides one location in the Domino Administrator client that you can use to view the overall status of multiple servers across one or more domains, and then use the information provided by DDM to quickly resolve problems.
    - The Domino® SNMP Agent
      The Domino® SNMP Agent enhances the monitoring and control features of Domino by enabling third-party management stations, which use industry standard SNMP, to manage aspects of the Domino server.
      - Domino® SNMP Agent architecture
        Domino® SNMP Agent services are provided by two types of programs.
      - About the Domino® Management Information Base (MIB)
        The Domino® Management Information Base (MIB) covers only the Domino server and not any other HCL or third-party server add-ins.
      - Special considerations for partitioned servers
        There are several different ways to use the Domino® SNMP Agent on a partitioned server. If you plan to use SNMP on a partitioned server, this section provides information you need to know prior to using SNMP with Domino.
      - Configuring the Domino® SNMP Agent
        To configure the Domino® SNMP Agent, you perform a procedure specific to each platform and then complete the configuration by performing another procedure that applies to all platforms.
        Configuring the Domino® SNMP Agent for Microsoft™ Windows™
        Complete these steps, once per platform, to configure the Domino® SNMP Agent for Microsoft™ Windows™.
        Configuring the Domino® SNMP Agent for AIX®
        Complete these steps, once per platform, to configure the Domino® SNMP Agent for IBM® AIX®.
        Configuring the Domino SNMP Agent for Linux
        Complete these steps, once per platform, to configure the Domino® SNMP Agent for Linux™.
        Completing the configuration of the Domino® SNMP Agent
        After you have performed the platform-specific configuration steps, complete the configuration of the Domino® SNMP Agent by following these steps which apply to all platforms. Repeat these steps as necessary for each Domino partition.
        Manually starting and stopping the Domino SNMP Agent
        After you configure the Domino® SNMP Agent, when you restart the system the Domino SNMP Agent automatically starts. If necessary, you can stop the agent and then manually restart it.
        Configuring Master SNMP Agent for systemd
        On the Linux™ platform, the Domino® SNMP Agent uses the SMUX protocol, per RFC 1227, to communicate with the system's Master SNMP Agent. Some Linux distributions include a Master SNMP Agent that supports the SMUX protocol; others do not.
      - Using the Domino® MIB with your SNMP management station
        To access any Domino® server's objects in the Domino MIB, you must load the Domino MIB on your SNMP management station.
      - Troubleshooting the Domino® SNMP Agent
        SNMP agent troubleshooting tips are presented here.
    - Overview of server maintenance
      As a Domino® administrator, a major part of your job is maintaining each server that you administer.
    - Tools for mail monitoring
      Domino® provides three tools that you can use to monitor mail. Message tracking allows you to track specific mail messages to determine if the intended recipients received them. Mail usage reports provide the information you need to resolve mail problems and improve the efficiency of your mail network. Mail probes test and gather statistics on mail routes.
    - Monitoring directory assistance
      You can monitor directory assistance by using Show Xdir command to display information about all the directories a server uses for directory services. You can also view directory assistance statistics.
    - Monitoring databases
      You can monitor database activity, replication, and document deletions.
    - Monitoring a cluster
      Domino® provides several ways to find out what is happening in a cluster and make adjustments to keep the cluster running smoothly and efficiently, so that no server is overloaded. You can monitor failover, workload balancing, and cluster replication to see how efficiently the cluster is running.
    - Monitoring slow or unresponsive servers with the Domino® Diagnostic Probe
      Use the Domino® Diagnostic Probe (DDP), a Java™ utility provided by Support, to monitor servers that have been intermittently slow or unresponsive. The probe is a Java process (dbopen.jar) that runs in the background. The utility probes a specific Domino server over time by invoking database open transactions. If the probe detects a slow response, it will invoke Notes® System Diagnostic (NSD) to gather diagnostic data. This data is used by Support to troubleshoot and determine the cause or causes of the performance degradation.
    - Monitoring Smart Server Startup
      With Smart Server Startup, users are prevented from connecting to a Domino server until it is fully up and ready to accept user requests. For example, during startup of the Domino server after a crash, users can connect to the Domino server only after the server has fully recovered.
    - Monitoring quality of service
      Quality of Service, or QoS, is designed to react to the general operation of a Domino® server in order to keep that server functioning reliably and always available. If QoS detects that a server is not responding or hung, QoS probing can be configured to email an administrator about the problem and/or automatically terminate the server and restart it. QoS log information can also be useful for analysis by Support.
    - Understanding Quality of Service (QoS) behavior and logging
      This topic covers details of QoS including server and server controller behavior during kill events, failover trigger, and log file content.
  - Managing servers
    Manage Domino® servers by performing any of these tasks.
  - Managing databases
    Topics in this section describe how to set up and manage Domino® databases.

Configuring Master SNMP Agent for systemd

On the Linux™ platform, the Domino® SNMP Agent uses the SMUX protocol, per RFC 1227, to communicate with the system's Master SNMP Agent. Some Linux distributions include a Master SNMP Agent that supports the SMUX protocol; others do not.

About this task

On the Linux platform, starting in Domino 14.5, the NET-SNMP Master Agent called NET-SNMPD is not included. You need to install your own NET-SNMP Master Agent packages from the Net-SNMP website, which contain many optional components, from which you might want to create and/or configure your own Master SNMP Agent for use with Domino.

Installing and configuring NET-SNMP to run as a systemd service

Procedure

Run the following commands to install the NET-SNMP packages:
```
yum install net-snmp
yum install net-snmp-utils
```
Verify the NET-SNMP install with the following command.
```
snmpwalk --version
```
Create a new service file for SNMP at the following location:
/etc/systemd/system/snmpd.service

Refer to the /opt/hcl/domino/notes/latest/linux/dominosnmp.service file or add the following in the service file.

[Unit]
Description=Simple Network Management Protocol (SNMP) Daemon
Documentation=man:snmpd(8)
After=syslog.target, network.target

[Service]
ExecStart=/usr/sbin/snmpd -Lsd -Lf /dev/null -p /run/snmpd.pid
ExecReload=/bin/kill -HUP $MAINPID
PIDFile=/run/snmpd.pid

[Install]
WantedBy=multi-user.target

Enable the snmpd service with the following commands:
```
systemctl daemon-reload
systemctl enable snmpd
```
Restart the system and after the startup, verify that the snmpd service is running by entering the following command:
```
systemctl status snmpd
```

Configuring NET-SNMPD

Procedure

Update the /etc/snmp/snmpd.conf file with appropriate trap destinations and community names for your remote management infrastructure. Trap destinations are set using the trapsink directive. Community names are set using the rocommunity and rwcommunity directives.

Note: If you use the install-dominosnmp.sh provided with Domino, you do not need to create or configure your own NET-SNMP Master Agent. Both have been done for you.