Network

The Network settings are used to integrate the Reddoxx Appliance within the network.
These settings should be configured with the utmost care to ensure a reliable functionality.

  • Hostname: Enter any name for the REDDOXX Appliance in the network.
    The standard value can be exchanged for any Name.
  • Domainname: If applicable, enter the name of the domain the Reddoxx Appliance belongs to.
  • 1. DNS-Server: Enter the corresponding IP address of your network's DNS server.
    This entry is mandatory! At least one DNS server must be stated.
    Ensure that the DNS server is accessible, also if the REDDOXX Appliance is operated in a DMZ.
  • 2. DNS-Server: Enter the IP address of another DNS server.
    Make sure both DNS Servers consist of the same dataset, if configuring a second DNS Server.
  • Confirm the changes with "Apply Settings"

  • eth0: This is the Lan Interface 1, choose dhcp or configure a static IP.
  • eth0:MdCon: This is the Alias Interface that can be used to make the SMTP Connector listen to Port 25.
    This is a virtual interface, so it is not required to attach another network card to the appliance.
  • eth1: This Interface can be used for Clustermode, or to configure a separated connection to a storage network.
    An eth1 Interface is required for Bridge Mode, but does not need to be configured additionally.

Changes to the IP Settings for the corresponding Interfaces can be done via double click and are applied with "save".

  • You can configure static routes, if connections to mailservers or other communication partners are not allowed to be routed via the default gateway.
  • The target has to be configured in the CIDR notation (e.g, 192.168.0.0/24)
  • If the Gateway for a static route cannot be reached, there is no Connection to the defined target (No Route to Host)

Consider, that static routes should be configured on the Default Gateway, instead of setting up static routes on Clients

  • Via the timeserver configuration, you can enter the timeservers and choose the applicable time zone via the selection list.
  • With "Enable NTP" the NTP Service can be enabled (Microsoft recommends to disable this Feature when using HyperV Appliances)
  • We recommend entering at least one timeserver that supports NTP (Network Time Protocol), as the correct time is important for the functioning of the REDDOXX Appliance.
  • Especially in a Cluster Configuration, both nodes need to have the exact same Time Server settings
  • It is recommended to use a local timeserver (e.g. Domain Controller or dedicated Timeserver) instead of Public Timeservers
  • Make sure that the port 123 UDP on your firewall is opened
  • Confirm the changes with "Apply Settings"

  • A proxy can be configured in the Proxy tab, if there is no direct connection to the Internet.
  • Configure the Proxy settings for http Proxy or socks proxy, if needed.
  • The socks proxy is only used by the fuzzy service.
  • Confirm the changes with "Apply Settings".

  • The REDDOXX appliance supports system network monitoring based on the Simple Network Management Protocol (SNMP)
  • You can use any kind of monitoring tools as long as it supports SNMP
  • For an example, the administrator can monitor the queue length of the incoming mails and if the value reaches a specified limit (say 500) the monitoring system sends an alert to the admin.
  • Then the admin can for e.g. upgrade the hardware performance so that the mails are processed faster.

When running a failover cluster, the failoveradress should be used for snmp monitoring. A direct monitoring of active and passive node would produce errors especially on the passive node.

The following steps are required to use SNMP (it is possible to use SNMPv2 and SNMPv3 together):

  1. Use a descriptive Name in System Location (Some informational data for the monitoring software, where this appliance is located)
  2. Set the Sytem contact (informational data, like a username)
  3. Select if SNMPv2 should be used and set the SNMP Community (The authentication string to allow access to the appliance for data collection)
  4. Select if SNMPv3 should be used and set the corresponding Authentication and Privacy Credentials
  5. Confirm the changes with "Apply Settings".

The authentication user for snmpv3, which you need to use in your monitoring system when setting up the connection credentials, is called: rdxsnmp

To monitor the REDDOXX appliance and watch for its values the administrator of the network monitoring system needs the Object-IDs.
The Root Object-ID for REDDOXX is 31581. The single messure point values (Keys) are addressed via the Object-IDs as listed in the following table.

To get a list of all used and available SNMP Object-IDs, the SNMP Diagnose can be used.

Object-ID Key Description
.1.3.6.1.4.1.31581.1.1.1 rdxSmtpServerConnectionsIn Reddoxx SMTP Server Inbound Connections
.1.3.6.1.4.1.31581.1.1.2 rdxSmtpServerConnectionsOut Reddoxx SMTP Client Outbound Connections
.1.3.6.1.4.1.31581.1.2.1 rdxSmtpServerMsgRecvIn Reddoxx Amount of inbound messages received
.1.3.6.1.4.1.31581.1.2.2 rdxSmtpServerMsgRecvOut Reddoxx Amount of outbound messages received
.1.3.6.1.4.1.31581.1.3.1 rdxSmtpServerBytesRecvIn Reddoxx Amount of bytes received inbound
.1.3.6.1.4.1.31581.1.3.2 rdxSmtpServerBytesRecvOut Reddoxx Amount of bytes received outbound
.1.3.6.1.4.1.31581.1.4 rdxSmtpServerActiveSessions Reddoxx Number of active SMTP Connections
.1.3.6.1.4.1.31581.2.1.1 rdxSmtpClientConnectionsIn Reddoxx inbound SMTP Client Connections count
.1.3.6.1.4.1.31581.2.1.2 rdxSmtpClientConnectionsOut Reddoxx outbound SMTP Client Connections count
.1.3.6.1.4.1.31581.2.2.1 rdxSmtpClientMsgSentIn Reddoxx Amount of inbound messages sent
.1.3.6.1.4.1.31581.2.2.2 rdxSmtpClientMsgSentOut Reddoxx Amount of outbound messages sent
.1.3.6.1.4.1.31581.2.3.1 rdxSmtpClientBytesSentIn Reddoxx Amount of bytes sent inbound
.1.3.6.1.4.1.31581.2.3.2 rdxSmtpClientBytesSentOut Reddoxx Amount of bytes sent outbound
.1.3.6.1.4.1.31581.2.4 rdxSmtpClientSessions Reddoxx Current outgoing SMTP Connections count
.1.3.6.1.4.1.31581.2.5 rdxSmtpClientQueueLength Reddoxx Messages to be sent
.1.3.6.1.4.1.31581.3.1 rdxValidatorSessions Reddoxx Validation Sessions
.1.3.6.1.4.1.31581.3.2 rdxValidatorQueueLength Reddoxx Validation Queue Length
.1.3.6.1.4.1.31581.4.1 rdxArchiveMsgCount Reddoxx Archived Messages
.1.3.6.1.4.1.31581.10.1 rdxSpamfinderRecjects Reddoxx Rejected Messages
.1.3.6.1.4.1.31581.10.2 rdxSpamfinderTagMessages Reddoxx Tagged Messages
.1.3.6.1.4.1.31581.10.3 rdxSpamfinderCissQuarantine Reddoxx CISS Quarantined Messages
.1.3.6.1.4.1.31581.10.4 rdxSpamfinderSpamQuarantine Reddoxx Quarantined Messages
.1.3.6.1.4.1.31581.10.5 rdxSpamfinderSpamBounced Reddoxx Bounced Messages
.1.3.6.1.4.1.31581.10.6 rdxSpamfinderVirusesDetected Reddoxx Viruses Detection
.1.3.6.1.4.1.31581.10.100 rdxSpamfinderBatvHits Reddoxx BATV Filter Drops
.1.3.6.1.4.1.31581.10.101 rdxSpamfinderAddedIpBlacklistEntries Reddoxx IP-Blacklist Entries
.1.3.6.1.4.1.31581.10.102 rdxSpamfinderRecipientVerificationHits Reddoxx Rejected Recipient Addresses
.1.3.6.1.4.1.31581.11.1 rdxSessionsTotal Active User Sessions

Object IDs for ram usage by each appliance service

Object-ID Key
.1.3.6.1.4.1.31581.12.1.1 rdxServicesRssMemoryUsageEngine
.1.3.6.1.4.1.31581.12.1.2 rdxServicesRssMemoryUsageAcs
.1.3.6.1.4.1.31581.12.1.3 rdxServicesRssMemoryUsageMailDepotConnector
.1.3.6.1.4.1.31581.12.1.4 rdxServicesRssMemoryUsageComplianceLog
.1.3.6.1.4.1.31581.12.1.5 rdxServicesRssMemoryUsageRestProxy
.1.3.6.1.4.1.31581.12.1.6 rdxServicesRssMemoryUsageClamav
.1.3.6.1.4.1.31581.12.1.7 rdxServicesRssMemoryUsageFirebird
.1.3.6.1.4.1.31581.12.1.8 rdxServicesRssMemoryUsageApache

Object IDs for cpu usage by each appliance service

Object-ID Key
.1.3.6.1.4.1.31581.12.2.1 rdxServicesCpuUsageEngine
.1.3.6.1.4.1.31581.12.2.2 rdxServicesCpuUsageAcs
.1.3.6.1.4.1.31581.12.2.3 rdxServicesCpuUsageMailDepotConnector
.1.3.6.1.4.1.31581.12.2.4 rdxServicesCpuUsageComplianceLog
.1.3.6.1.4.1.31581.12.2.5 rdxServicesCpuUsageRestProxy
.1.3.6.1.4.1.31581.12.2.6 rdxServicesCpuUsageClamav
.1.3.6.1.4.1.31581.12.2.7 rdxServicesCpuUsageFirebird
.1.3.6.1.4.1.31581.12.2.8 rdxServicesCpuUsageApache

Object IDs for uptime by each appliance service

Object-ID Key
.1.3.6.1.4.1.31581.12.3.1 rdxServicesUptimeEngine
.1.3.6.1.4.1.31581.12.3.2 rdxServicesUptimeAcs
.1.3.6.1.4.1.31581.12.3.3 rdxServicesUptimeMailDepotConnector
.1.3.6.1.4.1.31581.12.3.4 rdxServicesUptimeComplianceLog
.1.3.6.1.4.1.31581.12.3.5 rdxServicesUptimeRestProxy
.1.3.6.1.4.1.31581.12.3.6 rdxServicesUptimeClamav
.1.3.6.1.4.1.31581.12.3.7 rdxServicesUptimeFirebird
.1.3.6.1.4.1.31581.12.3.8 rdxServicesUptimeApache

Object IDs for open file handles

Object-ID Key
.1.3.6.1.4.1.31581.14.1 rdxOpenFilesTotal
.1.3.6.1.4.1.31581.14.2 rdxOpenFilesContainer
.1.3.6.1.4.1.31581.14.3 rdxOpenFilesIndex

Common Linux-Object-IDs

Object-ID Key Description
.1.3.6.1.4.1.2021.10.1.3.1 Linux_System_Load.1 1 Minute System Load
.1.3.6.1.4.1.2021.10.1.3.2 Linux_System_Load.2 5 Minute System Load
.1.3.6.1.4.1.2021.10.1.3.3 Linux_System_Load.3 15 Minute System Load
.1.3.6.1.4.1.2021.9.1.7.1 FreeDiskSpaceSystemPartition Free Disk Space System Partition
.1.3.6.1.4.1.2021.9.1.7.8 FreeDiskSpaceDataPartition Free Disk Space Data Partition
.1.3.6.1.4.1.2021.9.1.8.1 UsedDiskSpaceSystemPartition Used Disk Space System Partition
.1.3.6.1.4.1.2021.9.1.8.8 UsedDiskSpaceDataPartition Used Disk Space Data Partition

  • The Reddooxx Appliance provides an SMB Share for the connected storages.
  • This share can be reached via \\Appliance-IP\
  • You can configure an user for Read-Only Access or as Admin Account with read/write access.
  • The share can be used to move a Container from one storage to another, or to integrate a storage into a backup plan.
  • Confirm the changes with "Apply Settings".