Templates: Domain Controllers – Samba3 Domain Controller

Monitors included into Domain Controllers – Samba3 Domain Controller (Linux/UNIX) template

The monitors of this application template check overall status and performance of the essential DC daemons of a Samba3 Domain Controller. Most of the monitors collect their data over SSH, hence the sshd daemon should be running on a target host. More about templates.

Monitors list

Monitors description

SLAP daemon process count (enabled by default) OpenLDAP server process count. Shows if the main DC daemon (slapd) is up and running. slapd is the stand-alone LDAP daemon. It listens for LDAP connections on any number of ports (default 389), responding to the LDAP operations it receives over these connections.

LDAP server, TCP port (enabled by default) Shows if LDAP Server TCP port (default 389) is available and slapd daemon listens on this port.

SMB port (enabled by default) Shows if SMB over TCP port (default 445) is available and SMB daemon listens on this port.

DNS response time Shows DNS server response time. Off by default. The DNS server is optional for a Samba3 DC, hence you need to turn this monitor on only if a DNS server is running on the domain controller. Uses default port 53.

DNS server process count Shows if the DNS server running on the Domain Controller is alive. Off by default. The DNS server is optional for a Samba3 DC.

LDAP SSL port Shows if LDAP Server uses SSL-encrypted connection. Uses default port 636. This monitor is off by default.

LDAP server, UDP port Shows if LDAP Server listens on UDP port (default 389). A client uses a so-called LDAP “Ping” to the candidate domain controller to determine whether the domain controller is handling requests. This monitor is off by default.

NETLOGON share disk space Free disk space on NETLOGON share. The NETLOGON share plays a central role in domain logon and domain membership support. It is used to provide logon scripts, as well as to locate other common tools that may be needed for logon processing. This is an essential share on a domain controller.

NMB daemon CPU usage Shows NetBIOS name server (nmbd) CPU usage.

NMB daemon memory usage Shows NetBIOS name server (nmbd) memory usage.

NMB daemon process count NetBIOS name server process count. nmbd is a server that understands and can reply to NetBIOS over IP name service requests. It also participates in the browsing protocols which make up the Windows “Network Neighborhood” view. This monitor shows if nmbd daemon is up and running.

NTP daemon process count Shows if Network Time Protocol daemon is up and running. ntpd allows time synchronization with external sources and can also be configured to be a time source for others. An accurate time synchronization is absolutely necessary for a domain.

SLAP daemon CPU usage Shows OpenLDAP server (slapd) CPU usage.

SLAP daemon memory usage Shows OpenLDAP server (slapd) memory usage.

SMB daemon CPU usage Shows Samba server (smbd) CPU usage.

SMB daemon memory usage Shows Samba server (smbd) memory usage.

SMB daemon process count Shows Samba server (smbd) process count. smbd is the server daemon that provides filesharing and printing services. The server provides filespace and printer services to clients using the SMB (or CIFS) protocol. In addition, it is responsible for user authentication, resource locking, and data sharing through the SMB protocol.

Samba3 Domain Controller (Linux/UNIX) tips

  • enable process count monitor for every essential DC service
  • enable NETLOGON share disk space monitor to make sure all the user logon procedures are available
  • collect data on CPU/memory usage from all the DC essential process during several days and add state conditions to the corresponding monitors, so that an alert is issued if a value exceeds the configured limit

Templates overview

IPHost Network Monitor provides application templates (or just “templates” later in document), to create multiple relevant monitors in only a few clicks. Templates facilitate adding typical monitors sets; this can be particularly useful in case of big networks, when creating same-type monitors for many same-type devices is a common task. Application templates are sets of monitors that can be added, using specific predefined parameters, for a given host at once. The said set, added for given host, is displayed as a separate node in tree view pane, and is named application.

There are predefined templates; user can as well generate templates of their own – either out of existing monitors, or by cloning a predefined template. User-added template definitions are saved in XML files and can thus be conveniently augmented or applied to specific needs.