FELIXXRT
日本語English

Monitoring

Lets external monitoring servers collect this router's status. FELIXXRT supports the Zabbix agent, SNMP and the Prometheus node_exporter.

Use the SYSTEM › Monitoring page. Only the services you enable are started.

How it works

  • Each service accepts requests only from the monitoring server addresses (or networks) you enter for it.
  • This is independent of the zones. Even if a zone allows traffic to the router (Input), requests from any other source are refused.
  • The status (Running / Stopped) is shown to the right of each heading.
  • A PSK, password or community is stored as soon as you press Save or Generate next to it, and the running configuration is updated immediately. It does not become a pending change.
  • All other fields become pending changes when you press the section's Save. Apply them from Review changes at the top of the page and Confirm within 5 minutes (see Applying changes).

Zabbix agent

FELIXXRT runs Zabbix agent 2. Passive checks from the Zabbix server are received on TCP 10050.

  1. Under Zabbix agent, tick Enable.
  2. In Zabbix server, enter the address of the Zabbix server (or proxy), e.g. 192.168.1.50.
  3. To encrypt the traffic, enter a name in PSK identity, e.g. felixxrt.
  4. A PSK field appears. Press Generate. A 256-bit key is created and shown.
  5. Press Save, then apply and confirm the change.
  6. In Zabbix, create the host. Use the same host name as Host name (the router's hostname if blank), select PSK under Encryption and enter the same PSK identity and PSK.

You can display the PSK later with Show (requires edit permission). Pressing Generate again creates a new key, so Zabbix must be updated as well.

Field Description
Zabbix server Zabbix server (or proxy) allowed to query the agent, as an IP address or network. Separate multiple entries with commas.
Active checks Also lets the agent send data to the Zabbix server (used e.g. for log monitoring). When enabled, give the Zabbix server as an address, not a network.
Host name Host name registered in Zabbix. Defaults to the router's hostname.
PSK identity Name used for PSK encryption. Leave blank for no encryption.
PSK Hexadecimal key (at least 32 characters, an even number). Generate creates one.

SNMP

FELIXXRT runs a read-only SNMP agent on UDP 161.

  1. Under SNMP, tick Enable.
  2. In Allowed managers, enter the address or network of the monitoring server, e.g. 192.168.1.50.
  3. Select the Version. SNMPv3 is recommended.
  4. For SNMPv3, enter the User name, then enter the Auth password and Privacy password and press Save next to each (or use Generate). For SNMPv2c, set the Community the same way.
  5. Press the Save button at the bottom, then apply and confirm the change.
  6. Enter the same user name and passwords (or community) on the monitoring server.
Field Description
Allowed managers IP addresses or networks of monitoring servers allowed to query over SNMP, separated by commas.
Version SNMPv3 authenticates with a user name and passwords and encrypts the traffic. SNMPv2c uses only a community string and is not encrypted.
User name SNMPv3 user name. Must start with a lowercase letter, up to 15 characters.
Auth password Password for SNMPv3 authentication (SHA-256), at least 8 characters.
Privacy password Password for SNMPv3 encryption (AES), at least 8 characters.
Community The SNMPv2c shared string. Use a hard-to-guess value of at least 8 characters.
Location (optional), Contact (optional) Location and contact returned over SNMP.

Passwords and the community cannot contain spaces, " or \.

Prometheus node_exporter

FELIXXRT runs the Prometheus node_exporter, by default on TCP 9100.

  1. Under node_exporter, tick Enable.
  2. In Allowed Prometheus servers, enter the address or network of your Prometheus server, e.g. 192.168.1.60.
  3. Change the Port if needed.
  4. Press Save, then apply and confirm the change.
  5. Add a scrape target in Prometheus, e.g. http://192.168.1.1:9100/metrics.
Field Description
Allowed Prometheus servers IP addresses or networks of Prometheus servers allowed to scrape metrics, separated by commas.
Port TCP port for the metrics. Defaults to 9100.

If monitoring does not work

  • Check that the monitoring server's address is included in the allowed addresses or networks.
  • If the status stays Stopped, check that the change was applied and confirmed. If it cannot be applied, the problems are shown at the top of the page.
  • With Zabbix encryption, check that both the PSK identity and the PSK match the settings in Zabbix.
  • You can inspect the traffic with the packet capture on MONITOR › Diagnostics (see Status and maintenance).

Admin users and roles →