Why are alerts for network interfaces not raised when the configured thresholds are crossed?
In Linux SSH mode of monitoring, alerts will be triggered according to the following conditions.
- When the interface name starts with 'bond', alerts will be raised.
- When the interface has a master name as 'bond', alerts will be skipped.
- When an interface is not a master bond / slave to a bond, it should have an IPv4 address configuration. If it has, alerts will be raised for that interface, otherwise skipped.
This is implemented to prevent redundant/ unwanted alerts when the Network interfaces are configured with bond interfaces (or) do not have an IP in the server environment.
Follow below steps to check if there are any bond interfaces in a Linux server :
1) Execute the LANG=C /sbin/ip -s a command. The output will be like as follows,
$ LANG=C /sbin/ip -s a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
RX: bytes packets errors dropped missed mcast
8778 9678 0 0 0 0
TX: bytes packets errors dropped carrier collsns
263 5 0 0 0 0
4: ens1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond1 state UP group default qlen 1000
link/ether 44:2f:37:a6:b2:00 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
60 4 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0
6: bond1: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 44:df:35:25:c2:00 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
76 12 0 0 0 78
TX: bytes packets errors dropped carrier collsns
456 234 0 0 0 0
2) In case any interface has master name as 'bond', it is a slave of that particular interface. Here, alerts will not be raised for the interfaces in Applications Manager. For example, as per the sample output, the interface 'ens1' is a slave interface of 'bond1'.
There can be multiple slave interfaces for a single bond interface. The bond interface status will go DOWN if all the slaves goes DOWN. So, if alerts are raised for each slave interface, it will be redundant, as alerts were already raised for the specific bond. To avoid this, alerting is skipped for slave interfaces.
If alerts are mandatorily needed for those slave interfaces, Login as Admin user -> Go to Support Tab -> Database Summary -> Query Tool. Execute the below query and then restart the service.
UPDATE AM_GlobalConfig SET VALUE='true' WHERE NAME='am.server.linux.netinterface.alert.for.slave'
Note:
This handling is not supported for SNMP and Agent mode of Linux monitoring.
New to ADSelfService Plus?
Related Articles
Why are thresholds and alerts not working in Database tab metrics of MS SQL monitor?
In Applications Manager's MS SQL monitor, metrics under the Database tab are collected once every hour by default. This is controlled by the 'Collect data in every hour' option under Settings → Performance Polling → MS SQL → Metric Name: Database, ...Performance data not collected for Linux monitor with RHEL 8 & above in SSH mode
If you notice an issue regarding the performance data collection for the Linux monitor with RHEL 8 & above (No data in GUI) then from the Applications Manager GUI --> Admin --> Product Settings --> Logging --> choose Print all logs option and save ...Memory Usage Calculation (Linux- Telnet/SSH)
Physical Memory Utilization Calculation: Note: For version 16800 and above , the Skip option will be under Settings -> Performance Polling -> Servers -> Linux monitor type. Formula: (i) If Skip buffer and cache from monitoring (Applicable only for ...Critical\Warning alarm was raised, but action wasn't triggered
1.) Ensure that actions have been associated for the attribute that generated the alarm. For example, if the CPU utilisation of the server exceeded the permissible levels and generated the alarm, navigate to Monitor page-> Configure Alarm and ..."Prompt not matching the target server" alerts in Servers
Critical Alert: Prompt not matching the target server. Kindly check whether the given Command Prompt is correct. This alert is generated when the target server's prompt does not match the prompt value configured during monitor addition. Possible ...