1 title: Network Interfaces
7 This uses the output of the section {hpux_if} sent by the HP-UX
8 agent of Check_MK. This uses the command {nwmgr -g --st mib -c $nic}
9 in order to get status and statistics of a network interface.
11 In all other aspects this check behaves identical to {if} and {if64}
12 (with respect to check parameters, performance data and configuration).
14 {Note}: This check does {not} use SNMP.
16 Depending on the check paramters this check can go WARN or CRIT when the
17 port status changes (i.e. is down), when the link speed changes (e.g. a
18 port expected to be set to 1GBit/s operates only at 100MBit/s), when the
19 absolute or procentual traffic of a port exceeds certain levels or if the
20 rate of errors or discards exceeds configurable limits.
22 As of Check_MK version 1.1.9i1 this check supports averaging the in- and
23 outgoing traffic over a configurable range of time by using an exponentially
24 weighted moving average - just as Linux does for the CPU load averages.
25 The averaging can be configured on a per host and per port base. This is
26 done by adding a key {"average"} to the parameter dictionary with the number
27 of minutes that the average should cover as its key. Port with averaging
28 turned on output two additional performance values: the averaged traffic
29 in bytes. If you have configured traffic levels, then those levels are
30 applied to the averaged values.
33 There are three allowed ways to specify a port: {1}: the last component of
34 the SNMP OID number (as string), the {ifDescr} of the port or the {ifAlias} of
35 the port. If you are using the alias, you have to make sure that it is unique
36 by configuring useful aliases in the switch. Check_MK does not check for uniqueness.
39 The inventory creates one service for each NIC found on the system. NICs are
40 assumed to be of type {6} (Ethernet).