Juniper M-Series Netconf
Connector dependencies​
The following monitoring connectors will be installed when you install the Juniper M-Series Netconf connector through the Configuration > Connectors > Monitoring Connectors menu:
Pack assets​
Templates​
The Monitoring Connector Juniper M-Series Netconf brings a host template:
- Net-Juniper-Mseries-Netconf-custom
The connector brings the following service templates (sorted by the host template they are attached to):
- Net-Juniper-Mseries-Netconf-custom
- Not attached to a host template
Service Alias | Service Template | Service Description |
---|---|---|
CPU | Net-Juniper-Mseries-Cpu-Netconf-custom | Check CPU usage |
Hardware | Net-Juniper-Mseries-Hardware-Netconf-custom | Check hardware |
Memory | Net-Juniper-Mseries-Memory-Netconf-custom | Check memory usage |
OSPF | Net-Juniper-Mseries-Ospf-Netconf-custom | Check OSPF neighbors |
The services listed above are created automatically when the Net-Juniper-Mseries-Netconf-custom host template is used.
Service Alias | Service Template | Service Description | Discovery |
---|---|---|---|
BGP | Net-Juniper-Mseries-Bgp-Netconf-custom | Check BGP peers | X |
Disks | Net-Juniper-Mseries-Disks-Netconf-custom | Check disks usage | X |
Interfaces | Net-Juniper-Mseries-Interfaces-Netconf-custom | Check the interfaces | X |
LDP-session | Net-Juniper-Mseries-Ldp-Netconf-custom | Check LDP sessions status | X |
LSP | Net-Juniper-Mseries-Lsp-Netconf-custom | Check LSP status | X |
RPM-services | Net-Juniper-Mseries-Services-Rpm-Netconf-custom | Check RPM services | X |
RSVP-sessions | Net-Juniper-Mseries-Rsvp-Netconf-custom | Check RSVP sessions | X |
The services listed above are not created automatically when a host template is applied. To use them, create a service manually, then apply the service template you want.
If Discovery is checked, it means a service discovery rule exists for this service template.
Discovery rules​
Service discovery​
Rule name | Description |
---|---|
Net-Juniper-Mseries-Netconf-Bgp | Discover BGP peers and monitor them |
Net-Juniper-Mseries-Netconf-Disks | Discover the disk partitions and monitor space occupation |
Net-Juniper-Mseries-Netconf-Interfaces | Discover network interfaces and monitor bandwidth utilization |
Net-Juniper-Mseries-Netconf-Ldp | Discover LDP sessions and monitor their status |
Net-Juniper-Mseries-Netconf-Lsp | Discover LSP and monitor their status |
Net-Juniper-Mseries-Netconf-Rsvp | Discover RSVP sessions and monitor them |
Net-Juniper-Mseries-Netconf-Services-Rpm | Discover RPM services and monitor them |
More information about discovering services automatically is available on the dedicated page and in the following chapter.
Collected metrics & status​
Here is the list of services for this connector, detailing all metrics and statuses linked to each service.
- BGP
- CPU
- Disks
- Hardware
- Interfaces
- LDP-session
- LSP
- Memory
- OSPF
- RPM-services
- RSVP-sessions
Name | Unit |
---|---|
bgp.peers.detected.count | count |
status | N/A |
bgp~bgp.peer.traffic.in.bytes | B |
bgp~bgp.peer.traffic.out.bytes | B |
rib-status | N/A |
bgp~ribs#bgp.peer.rib.prefixes.active.count | count |
Name | Unit |
---|---|
cpu#cpu.utilization.1m.percentage | % |
cpu#cpu.utilization.5m.percentage | % |
cpu#cpu.utilization.15m.percentage | % |
Name | Unit |
---|---|
disk_name#disk.space.usage.bytes | B |
disk_name#disk.space.free.bytes | B |
disk_name#disk.space.usage.percentage | % |
Name | Unit |
---|---|
hardware. afeb.count | count |
afeb status | N/A |
hardware.fan.count | count |
fan status | N/A |
hardware.fpc.count | count |
fpc status | N/A |
hardware.mic.count | count |
mic status | N/A |
hardware.pic.count | count |
pic status | N/A |
hardware.psu.count | count |
psu status | N/A |
hardware.temperature .count | count |
temperature status | N/A |
Name | Unit |
---|---|
status | N/A |
interfaces~interface.traffic.in.bitspersecond | b/s |
interfaces~interface.traffic.out.bitspersecond | b/s |
interfaces~interface.packets.in.discard.percentage | % |
interfaces~interface.packets.in.error.percentage | % |
interfaces~interface.packets.in.fcserror.percentage | % |
interfaces~interface.packets.in.runts.percentage | % |
interfaces~interface.packets.in.giant.percentage | % |
interfaces~interface.packets.in.l3incomplete.percentage | % |
interfaces~interface.packets.in.fifo.error.percentage | % |
interfaces~interface.packets.in.l2mismatch.timeout.percentage | % |
interfaces~interface.packets.in.drop.percentage | % |
interfaces~interface.packets.in.resource.error.percentage | % |
interfaces~interface.packets.out.discard.percentage | % |
interfaces~interface.packets.out.error.percentage | % |
interfaces~interface.packets.out.drop.percentage | % |
interfaces~interface.packets.out.carrier.transition.percentage | % |
interfaces~interface.packets.out.collision.percentage | % |
interfaces~interface.packets.out.mtu.error.percentage | % |
interfaces~interface.packets.out.aged.percentage | % |
interfaces~interface.packets.out.hslink.crc.error.percentage | % |
interfaces~interface.packets.out.fifo.error.percentage | % |
interfaces~interface.packets.out.resource.error.percentage | % |
Name | Unit |
---|---|
ldp.sessions.detected.count | count |
status | N/A |
Name | Unit |
---|---|
lsp.sessions.detected.count | count |
status | N/A |
lsp~lsp.session.traffic.bytespersecond | B/s |
Name | Unit |
---|---|
memory#memory.usage.percentage | % |
Name | Unit |
---|---|
ospf.neighbors.detected.count | count |
neighbors-changed | N/A |
neighbor-status | N/A |
Name | Unit |
---|---|
services.detected.count | count |
status | N/A |
services~service.rpm.probe.loss.percentage | % |
service-rpm-probe-rtt-delay-average | N/A |
service-rpm-probe-rtt-delay-jitter | N/A |
service-rpm-probe-rtt-delay-stdev | N/A |
service-rpm-probe-prtj-delay-average | N/A |
service-rpm-probe-prtj-delay-jitter | N/A |
service-rpm-probe-prtj-delay-stdev | N/A |
service-rpm-probe-nrtj-delay-average | N/A |
service-rpm-probe-nrtj-delay-jitter | N/A |
service-rpm-probe-nrtj-delay-stdev | N/A |
Name | Unit |
---|---|
rsvp.sessions.detected.count | count |
status | N/A |
rsvp#rsvp.session.lsp.traffic.bytespersecond | B/s |
Prerequisites​
The Netconf service must be enabled on the Juniper M-Series router, and the router must be configured to allow connections from the Centreon server or poller. A user account with the necessary rights to access Netconf data must also be created.
Installing the monitoring connector​
Pack​
The installation procedures for monitoring connectors are slightly different depending on whether your license is offline or online.
- If the platform uses an online license, you can skip the package installation instruction below as it is not required to have the connector displayed within the Configuration > Connectors > Monitoring Connectors menu. If the platform uses an offline license, install the package on the central server with the command corresponding to the operating system's package manager:
- Alma / RHEL / Oracle Linux 8
- Alma / RHEL / Oracle Linux 9
- Debian 11 & 12
- CentOS 7
dnf install centreon-pack-network-routers-juniper-mseries-netconf
dnf install centreon-pack-network-routers-juniper-mseries-netconf
apt install centreon-pack-network-routers-juniper-mseries-netconf
yum install centreon-pack-network-routers-juniper-mseries-netconf
- Whatever the license type (online or offline), install the Juniper M-Series Netconf connector through the Configuration > Connectors > Monitoring Connectors menu.
Plugin​
Since Centreon 22.04, you can benefit from the 'Automatic plugin installation' feature. When this feature is enabled, you can skip the installation part below.
You still have to manually install the plugin on the poller(s) when:
- Automatic plugin installation is turned off
- You want to run a discovery job from a poller that doesn't monitor any resource of this kind yet
More information in the Installing the plugin section.
Use the commands below according to your operating system's package manager:
- Alma / RHEL / Oracle Linux 8
- Alma / RHEL / Oracle Linux 9
- Debian 11 & 12
- CentOS 7
dnf install centreon-plugin-Network-Routers-Juniper-Mseries-Netconf
dnf install centreon-plugin-Network-Routers-Juniper-Mseries-Netconf
apt install centreon-plugin-network-routers-juniper-mseries-netconf
yum install centreon-plugin-Network-Routers-Juniper-Mseries-Netconf
Using the monitoring connector​
Using a host template provided by the connector​
- Log into Centreon and add a new host through Configuration > Hosts.
- Fill in the Name, Alias & IP Address/DNS fields according to your resource's settings.
- Apply the Net-Juniper-Mseries-Netconf-custom template to the host. A list of macros appears. Macros allow you to define how the connector will connect to the resource, and to customize the connector's behavior.
- Fill in the macros you want. Some macros are mandatory.
Macro | Description | Default value | Mandatory |
---|---|---|---|
NETCONFEXTRAOPTIONS | Any extra option you may want to add to every command (a --verbose flag for example). All options are listed here. |
- Deploy the configuration. The host appears in the list of hosts, and on the Resources Status page. The command that is sent by the connector is displayed in the details panel of the host: it shows the values of the macros.
Using a service template provided by the connector​
- If you have used a host template and checked Create Services linked to the Template too, the services linked to the template have been created automatically, using the corresponding service templates. Otherwise, create manually the services you want and apply a service template to them.
- Fill in the macros you want (e.g. to change the thresholds for the alerts). Some macros are mandatory (see the table below).
- BGP
- CPU
- Disks
- Hardware
- Interfaces
- LDP-session
- LSP
- Memory
- OSPF
- RPM-services
- RSVP-sessions
Macro | Description | Default value | Mandatory |
---|---|---|---|
FILTERSNMPINDEX | Filter BGP peer by SNMP index | ||
FILTERLOCALADDRESS | Filter BGP peer by local address | ||
FILTERPEERADDRESS | Filter BGP peer by peer address | ||
FILTERRIBNAME | Filter BGP RIB by RIB name | ||
WARNINGBGPPEERDETECTED | Warning threshold for number of BGP peers detected | ||
CRITICALBGPPEERDETECTED | Critical threshold for number of BGP peers detected | ||
WARNINGBGPPEERRIBPREFIXESACTIVE | Warning threshold for number of active prefixes in BGP peer RIB | ||
CRITICALBGPPEERRIBPREFIXESACTIVE | Critical threshold for number of active prefixes in BGP peer RIB | ||
WARNINGBGPPEERTRAFFICIN | Warning threshold for BGP peer traffic in | ||
CRITICALBGPPEERTRAFFICIN | Critical threshold for BGP peer traffic in | ||
WARNINGBGPPEERTRAFFICOUT | Warning threshold for BGP peer traffic out | ||
CRITICALBGPPEERTRAFFICOUT | Critical threshold for BGP peer traffic out | ||
WARNINGRIBSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{localAddr}, %{localAs}, %{peerAddr}, %{peerAs}, %{peerState}, %{ribName}, %{sendState} | ||
CRITICALRIBSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{localAddr}, %{localAs}, %{peerAddr}, %{peerAs}, %{peerState}, %{ribName}, %{sendState} | ||
CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{peerState} !~ /established/i'). You can use the following variables: %{localAddr}, %{localAs}, %{peerAddr}, %{peerAs}, %{peerState} | %{peerState} !~ /established/i | |
WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{localAddr}, %{localAs}, %{peerAddr}, %{peerAs}, %{peerState} | ||
EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed here. |
Macro | Description | Default value | Mandatory |
---|---|---|---|
FILTERNAME | Filter CPU by name | ||
WARNINGAVERAGE15M | Warning threshold for 15 minutes average CPU usage (%) | ||
CRITICALAVERAGE15M | Critical threshold for 15 minutes average CPU usage (%) | ||
WARNINGAVERAGE1M | Warning threshold for 1 minute average CPU usage (%) | ||
CRITICALAVERAGE1M | Critical threshold for 1 minute average CPU usage (%) | ||
WARNINGAVERAGE5M | Warning threshold for 5 minutes average CPU usage (%) | ||
CRITICALAVERAGE5M | Critical threshold for 5 minutes average CPU usage (%) | ||
EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed here. |
Macro | Description | Default value | Mandatory |
---|---|---|---|
FILTERNAME | Filter disks by name (can be a regexp) | ||
WARNINGSPACEUSAGE | Warning threshold for space usage (in bytes) | ||
CRITICALSPACEUSAGE | Critical threshold for space usage (in bytes) | ||
WARNINGSPACEUSAGEFREE | Warning threshold for free space (in bytes) | ||
CRITICALSPACEUSAGEFREE | Critical threshold for free space (in bytes) | ||
WARNINGSPACEUSAGEPRCT | Warning threshold for space usage (in percentage) | ||
CRITICALSPACEUSAGEPRCT | Critical threshold for space usage (in percentage) | ||
EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed here. |
Macro | Description | Default value | Mandatory |
---|---|---|---|
COMPONENT | Which component to check (default: '.*'). Can be: afeb , fan , fpc , mic , pic , psu , temperature | ||
EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed here. |
Macro | Description | Default value | Mandatory |
---|---|---|---|
FILTERUSE | Define the value to be used to filter interfaces (default: name ) (values: name , descr ) | name | |
FILTERINTERFACE | Filter interface name (regexp can be used) | ||
WARNINGBIASCURRENT | Threshold in mA | ||
CRITICALBIASCURRENT | Threshold in mA | ||
WARNINGINDISCARD | Threshold | ||
CRITICALINDISCARD | Threshold | ||
WARNINGINDROP | Threshold | ||
CRITICALINDROP | Threshold | ||
WARNINGINERROR | Threshold | ||
CRITICALINERROR | Threshold | ||
WARNINGINFCSERROR | Threshold | ||
CRITICALINFCSERROR | Threshold | ||
WARNINGINFIFOERROR | Threshold | ||
CRITICALINFIFOERROR | Threshold | ||
WARNINGINGIANT | Threshold | ||
CRITICALINGIANT | Threshold | ||
WARNINGINL2MISMATCHTIMEOUT | Threshold | ||
CRITICALINL2MISMATCHTIMEOUT | Threshold | ||
WARNINGINL3INCOMPLETE | Threshold | ||
CRITICALINL3INCOMPLETE | Threshold | ||
WARNINGINPUTPOWER | Threshold in dBm | ||
CRITICALINPUTPOWER | Threshold in dBm | ||
WARNINGINRESOURCEERROR | Threshold | ||
CRITICALINRESOURCEERROR | Threshold | ||
WARNINGINRUNTS | Threshold | ||
CRITICALINRUNTS | Threshold | ||
WARNINGINTRAFFIC | Threshold | ||
CRITICALINTRAFFIC | Threshold | ||
WARNINGMODULETEMPERATURE | Threshold in C | ||
CRITICALMODULETEMPERATURE | Threshold in C | ||
WARNINGOUTAGED | Threshold | ||
CRITICALOUTAGED | Threshold | ||
WARNINGOUTCARRIERTRANSITION | Threshold | ||
CRITICALOUTCARRIERTRANSITION | Threshold | ||
WARNINGOUTCOLLISION | Threshold | ||
CRITICALOUTCOLLISION | Threshold | ||
WARNINGOUTDISCARD | Threshold | ||
CRITICALOUTDISCARD | Threshold | ||
WARNINGOUTDROP | Threshold | ||
CRITICALOUTDROP | Threshold | ||
WARNINGOUTERROR | Threshold | ||
CRITICALOUTERROR | Threshold | ||
WARNINGOUTFIFOERROR | Threshold | ||
CRITICALOUTFIFOERROR | Threshold | ||
WARNINGOUTHSLINKCRCERROR | Threshold | ||
CRITICALOUTHSLINKCRCERROR | Threshold | ||
WARNINGOUTMTUERROR | Threshold | ||
CRITICALOUTMTUERROR | Threshold | ||
WARNINGOUTPUTPOWER | Threshold in dBm | ||
CRITICALOUTPUTPOWER | Threshold in dBm | ||
WARNINGOUTRESOURCEERROR | Threshold | ||
CRITICALOUTRESOURCEERROR | Threshold | ||
WARNINGOUTTRAFFIC | Threshold | ||
CRITICALOUTTRAFFIC | Threshold | ||
CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: C<'%{admstatus} eq "up" and %{opstatus} ne "up"'>). You can use the following variables: C<%{admstatus}>, C<%{opstatus}>, C<%{display}> | %{admstatus} eq "up" and %{opstatus} ne "up" | |
WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: C<%{admstatus}>, C<%{opstatus}>, C<%{display}> | ||
EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed here. |
Macro | Description | Default value | Mandatory |
---|---|---|---|
FILTERID | Filter LDP session by ID | ||
FILTERREMOTEADDRESS | Filter LDP session by remote address | ||
WARNINGLDPSESSIONMESSAGESADDRESSRECEIVED | Threshold | ||
CRITICALLDPSESSIONMESSAGESADDRESSRECEIVED | Threshold | ||
WARNINGLDPSESSIONMESSAGESADDRESSSENT | Threshold | ||
CRITICALLDPSESSIONMESSAGESADDRESSSENT | Threshold | ||
WARNINGLDPSESSIONMESSAGESADDRESSWITHDRAWRECEIVED | Threshold | ||
CRITICALLDPSESSIONMESSAGESADDRESSWITHDRAWRECEIVED | Threshold | ||
WARNINGLDPSESSIONMESSAGESADDRESSWITHDRAWSENT | Threshold | ||
CRITICALLDPSESSIONMESSAGESADDRESSWITHDRAWSENT | Threshold | ||
WARNINGLDPSESSIONMESSAGESINITIALIZATIONRECEIVED | Threshold | ||
CRITICALLDPSESSIONMESSAGESINITIALIZATIONRECEIVED | Threshold | ||
WARNINGLDPSESSIONMESSAGESINITIALIZATIONSENT | Threshold | ||
CRITICALLDPSESSIONMESSAGESINITIALIZATIONSENT | Threshold | ||
WARNINGLDPSESSIONMESSAGESKEEAPLIVERECEIVED | Threshold | ||
CRITICALLDPSESSIONMESSAGESKEEAPLIVERECEIVED | Threshold | ||
WARNINGLDPSESSIONMESSAGESKEEAPLIVESENT | Threshold | ||
CRITICALLDPSESSIONMESSAGESKEEAPLIVESENT | Threshold | ||
WARNINGLDPSESSIONMESSAGESLABELABORTRECEIVED | Threshold | ||
CRITICALLDPSESSIONMESSAGESLABELABORTRECEIVED | Threshold | ||
WARNINGLDPSESSIONMESSAGESLABELABORTSENT | Threshold | ||
CRITICALLDPSESSIONMESSAGESLABELABORTSENT | Threshold | ||
WARNINGLDPSESSIONMESSAGESLABELMAPPINGRECEIVED | Threshold | ||
CRITICALLDPSESSIONMESSAGESLABELMAPPINGRECEIVED | Threshold | ||
WARNINGLDPSESSIONMESSAGESLABELMAPPINGSENT | Threshold | ||
CRITICALLDPSESSIONMESSAGESLABELMAPPINGSENT | Threshold | ||
WARNINGLDPSESSIONMESSAGESLABELRELEASERECEIVED | Threshold | ||
CRITICALLDPSESSIONMESSAGESLABELRELEASERECEIVED | Threshold | ||
WARNINGLDPSESSIONMESSAGESLABELRELEASESENT | Threshold | ||
CRITICALLDPSESSIONMESSAGESLABELRELEASESENT | Threshold | ||
WARNINGLDPSESSIONMESSAGESLABELREQUESTRECEIVED | Threshold | ||
CRITICALLDPSESSIONMESSAGESLABELREQUESTRECEIVED | Threshold | ||
WARNINGLDPSESSIONMESSAGESLABELREQUESTSENT | Threshold | ||
CRITICALLDPSESSIONMESSAGESLABELREQUESTSENT | Threshold | ||
WARNINGLDPSESSIONMESSAGESLABELWITHDRAWRECEIVED | Threshold | ||
CRITICALLDPSESSIONMESSAGESLABELWITHDRAWRECEIVED | Threshold | ||
WARNINGLDPSESSIONMESSAGESLABELWITHDRAWSENT | Threshold | ||
CRITICALLDPSESSIONMESSAGESLABELWITHDRAWSENT | Threshold | ||
WARNINGLDPSESSIONMESSAGESNOTIFICATIONRECEIVED | Threshold | ||
CRITICALLDPSESSIONMESSAGESNOTIFICATIONRECEIVED | Threshold | ||
WARNINGLDPSESSIONMESSAGESNOTIFICATIONSENT | Threshold | ||
CRITICALLDPSESSIONMESSAGESNOTIFICATIONSENT | Threshold | ||
WARNINGLDPSESSIONSDETECTED | Threshold | ||
CRITICALLDPSESSIONSDETECTED | Threshold | ||
CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: C<'%{connectionState} !~ /open$/i || %{sessionState} !~ /operational/i'>). You can use the following variables: C<%{id}>, C<%{remoteAddress}>, C<%{connectionState}>, C<%{sessionState}> | %{connectionState} !~ /open$/i || %{sessionState} !~ /operational/i | |
WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: C<%{id}>, C<%{remoteAddress}>, C<%{connectionState}>, C<%{sessionState}> | ||
EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed here. |
Macro | Description | Default value | Mandatory |
---|---|---|---|
FILTERTYPE | Filter LSP session by type | ||
FILTERNAME | Filter LSP session by name | ||
WARNINGLSPSESSIONSDETECTED | Define the LSP sessions detected conditions to match for the status to be WARNING | ||
CRITICALLSPSESSIONSDETECTED | Define the LSP sessions detected conditions to match for the status to be CRITICAL | ||
WARNINGLSPSESSIONTRAFFIC | Define the LSP session traffic conditions to match for the status to be WARNING | ||
CRITICALLSPSESSIONTRAFFIC | Define the LSP session traffic conditions to match for the status to be CRITICAL | ||
CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{lspState} !~ /up/i'). You can use the following variables: C<%{type}>, C<%{name}>, C<%{srcAddress}>, C<%{dstAddress}>, C<%{lspState}> | %{lspState} !~ /up/i | |
WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: C<%{type}>, C<%{name}>, C<%{srcAddress}>, C<%{dstAddress}>, C<%{lspState}> | ||
EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed here. |
Macro | Description | Default value | Mandatory |
---|---|---|---|
FILTERNAME | Filter memory by name | ||
WARNINGUSAGEPRCT | Warning threshold for memory usage (%) | ||
CRITICALUSAGEPRCT | Critical threshold for memory usage (%) | ||
EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed here. |
Macro | Description | Default value | Mandatory |
---|---|---|---|
FILTERNEIGHBORADDRESS | Filter neighbors by address (can be a regexp) | ||
WARNINGNEIGHBORSCHANGED | Warning threshold for number of OSPF neighbors changed | ||
CRITICALNEIGHBORSCHANGED | Critical threshold for number of OSPF neighbors changed | ||
WARNINGNEIGHBORSDETECTED | Warning threshold for number of OSPF neighbors detected | ||
CRITICALNEIGHBORSDETECTED | Critical threshold for number of OSPF neighbors detected | ||
CRITICALNEIGHBORSTATUS | Define the conditions to match for the status to be CRITICAL (default: '%{state} =~ /down/i'). You can use the following variables: %{state}, %{address}, %{interfaceName} | %{state} =~ /down/i | |
WARNINGNEIGHBORSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{address}, %{interfaceName} | ||
EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed here. |
Macro | Description | Default value | Mandatory |
---|---|---|---|
FILTERNAME | Filter service by name | ||
FILTERTYPE | Filter service by type | ||
WARNINGSERVICERPMPROBELOSSPERCENTAGE | Define the service RPM probe loss percentage conditions to match for the status to be WARNING | ||
CRITICALSERVICERPMPROBELOSSPERCENTAGE | Define the service RPM probe loss percentage conditions to match for the status to be CRITICAL | ||
WARNINGSERVICERPMPROBENRTJDELAYAVERAGE | Define the service RPM probe negative round trip jitter delay average conditions to match for the status to be WARNING | ||
CRITICALSERVICERPMPROBENRTJDELAYAVERAGE | Define the service RPM probe negative round trip jitter delay average conditions to match for the status to be CRITICAL | ||
WARNINGSERVICERPMPROBENRTJDELAYJITTER | Define the service RPM probe negative round trip jitter delay jitter conditions to match for the status to be WARNING | ||
CRITICALSERVICERPMPROBENRTJDELAYJITTER | Define the service RPM probe negative round trip jitter delay jitter conditions to match for the status to be CRITICAL | ||
WARNINGSERVICERPMPROBENRTJDELAYSTDEV | Define the service RPM probe negative round trip jitter delay standard deviation conditions to match for the status to be WARNING | ||
CRITICALSERVICERPMPROBENRTJDELAYSTDEV | Define the service RPM probe negative round trip jitter delay standard deviation conditions to match for the status to be CRITICAL | ||
WARNINGSERVICERPMPROBEPRTJDELAYAVERAGE | Define the service RPM probe positive round trip jitter delay average conditions to match for the status to be WARNING | ||
CRITICALSERVICERPMPROBEPRTJDELAYAVERAGE | Define the service RPM probe positive round trip jitter delay average conditions to match for the status to be CRITICAL | ||
WARNINGSERVICERPMPROBEPRTJDELAYJITTER | Define the service RPM probe positive round trip jitter delay jitter conditions to match for the status to be WARNING | ||
CRITICALSERVICERPMPROBEPRTJDELAYJITTER | Define the service RPM probe positive round trip jitter delay jitter conditions to match for the status to be CRITICAL | ||
WARNINGSERVICERPMPROBEPRTJDELAYSTDEV | Define the service RPM probe positive round trip jitter delay standard deviation conditions to match for the status to be WARNING | ||
CRITICALSERVICERPMPROBEPRTJDELAYSTDEV | Define the service RPM probe positive round trip jitter delay standard deviation conditions to match for the status to be CRITICAL | ||
WARNINGSERVICERPMPROBERTTDELAYAVERAGE | Define the service RPM probe route-trip time delay average conditions to match for the status to be WARNING | ||
CRITICALSERVICERPMPROBERTTDELAYAVERAGE | Define the service RPM probe route-trip time delay average conditions to match for the status to be CRITICAL | ||
WARNINGSERVICERPMPROBERTTDELAYJITTER | Define the service RPM probe route-trip time delay jitter conditions to match for the status to be WARNING | ||
CRITICALSERVICERPMPROBERTTDELAYJITTER | Define the service RPM probe route-trip time delay jitter conditions to match for the status to be CRITICAL | ||
WARNINGSERVICERPMPROBERTTDELAYSTDEV | Define the service RPM probe route-trip time delay standard deviation conditions to match for the status to be WARNING | ||
CRITICALSERVICERPMPROBERTTDELAYSTDEV | Define the service RPM probe route-trip time delay standard deviation conditions to match for the status to be CRITICAL | ||
WARNINGSERVICESDETECTED | Define the services detected conditions to match for the status to be WARNING | ||
CRITICALSERVICESDETECTED | Define the services detected conditions to match for the status to be CRITICAL | ||
WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: %{testName}, %{probeType}, %{sourceAddress}, %{targetAddress}, %{probeStatus} | ||
CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{testName}, %{probeType}, %{sourceAddress}, %{targetAddress}, %{probeStatus} | ||
EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed here. |
Macro | Description | Default value | Mandatory |
---|---|---|---|
FILTERNAME | Filter RSVP session by name | ||
FILTERTYPE | Filter RSVP session by type | ||
WARNINGRSVPSESSIONLSPTRAFFIC | Define the RSVP session traffic conditions to match for the status to be WARNING | ||
CRITICALRSVPSESSIONLSPTRAFFIC | Define the RSVP session traffic conditions to match for the status to be CRITICAL | ||
WARNINGRSVPSESSIONSDETECTED | Define the RSVP sessions detected conditions to match for the status to be WARNING | ||
CRITICALRSVPSESSIONSDETECTED | Define the RSVP sessions detected conditions to match for the status to be CRITICAL | ||
CRITICALSTATUS | Define the conditions to match for the status to be CRITICAL (default: C<'%{lspState} !~ /up/i'>). You can use the following variables: C<%{type}>, C<%{name}>, C<%{srcAddress}>, C<%{dstAddress}>, C<%{lspState}> | %{lspState} !~ /up/i | |
WARNINGSTATUS | Define the conditions to match for the status to be WARNING. You can use the following variables: C<%{type}>, C<%{name}>, C<%{srcAddress}>, C<%{dstAddress}>, C<%{lspState}> | ||
EXTRAOPTIONS | Any extra option you may want to add to the command (a --verbose flag for example). All options are listed here. |
- Deploy the configuration. The service appears in the list of services, and on the Resources Status page. The command that is sent by the connector is displayed in the details panel of the service: it shows the values of the macros.
How to check in the CLI that the configuration is OK and what are the main options for?​
Once the plugin is installed, log into your Centreon poller's CLI using the
centreon-engine user account (su - centreon-engine
). Test that the connector
is able to monitor a resource using a command like this one (replace the sample values by yours):
/usr/lib/centreon/plugins/centreon_juniper_mseries_netconf.pl \
--plugin=network::juniper::mseries::netconf::plugin \
--mode=rsvp \
--hostname=10.0.0.1 \
--filter-name='' \
--filter-type='' \
--warning-rsvp-sessions-detected='' \
--critical-rsvp-sessions-detected='' \
--warning-status='' \
--critical-status='%\{lspState\} !~ /up/i' \
--warning-rsvp-session-lsp-traffic='' \
--critical-rsvp-session-lsp-traffic=''
The expected command output is shown below:
OK: detected: 29162 All RSVP sessions are ok | 'rsvp.sessions.detected.count'=29162;;;0; 'rsvp1#rsvp.session.lsp.traffic.bytespersecond'=22122B/s;;;; 'rsvp2#rsvp.session.lsp.traffic.bytespersecond'=603B/s;;;;
Troubleshooting​
Please find the troubleshooting documentation for Centreon Plugins typical issues.
Available modes​
In most cases, a mode corresponds to a service template. The mode appears in the execution command for the connector. In the Centreon interface, you don't need to specify a mode explicitly: its use is implied when you apply a service template. However, you will need to specify the correct mode for the template if you want to test the execution command for the connector in your terminal.
All available modes can be displayed by adding the --list-mode
parameter to
the command:
/usr/lib/centreon/plugins/centreon_juniper_mseries_netconf.pl \
--plugin=network::juniper::mseries::netconf::plugin \
--list-mode
The plugin brings the following modes:
Mode | Linked service template |
---|---|
bgp [code] | Net-Juniper-Mseries-Bgp-Netconf-custom |
cache [code] | Not used in this Monitoring Connector |
collection [code] | Not used in this Monitoring Connector |
cpu [code] | Net-Juniper-Mseries-Cpu-Netconf-custom |
disks [code] | Net-Juniper-Mseries-Disks-Netconf-custom |
hardware [code] | Net-Juniper-Mseries-Hardware-Netconf-custom |
interfaces [code] | Net-Juniper-Mseries-Interfaces-Netconf-custom |
ldp [code] | Net-Juniper-Mseries-Ldp-Netconf-custom |
list-bgp [code] | Used for service discovery |
list-disks [code] | Used for service discovery |
list-interfaces [code] | Used for service discovery |
list-ldp [code] | Used for service discovery |
list-lsp [code] | Used for service discovery |
list-rsvp [code] | Used for service discovery |
list-services-rpm [code] | Used for service discovery |
lsp [code] | Net-Juniper-Mseries-Lsp-Netconf-custom |
memory [code] | Net-Juniper-Mseries-Memory-Netconf-custom |
ospf [code] | Net-Juniper-Mseries-Ospf-Netconf-custom |
rsvp [code] | Net-Juniper-Mseries-Rsvp-Netconf-custom |
services-rpm [code] | Net-Juniper-Mseries-Services-Rpm-Netconf-custom |
Available options​
Generic options​
All generic options are listed here:
Option | Description |
---|---|
--mode | Define the mode in which you want the plugin to be executed (see --list-mode). |
--dyn-mode | Specify a mode with the module's path (advanced). |
--list-mode | List all available modes. |
--mode-version | Check minimal version of mode. If not, unknown error. |
--version | Return the version of the plugin. |
--custommode | When a plugin offers several ways (CLI, library, etc.) to get information the desired one must be defined with this option. |
--list-custommode | List all available custom modes. |
--multiple | Multiple custom mode objects. This may be required by some specific modes (advanced). |
--pass-manager | Define the password manager you want to use. Supported managers are: environment, file, keepass, hashicorpvault and teampass. |
--verbose | Display extended status information (long output). |
--debug | Display debug messages. |
--filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. |
--filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. |
--explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '_max' suffix. Example: it will split 'used_prct'=26.93%;0:80;0:90;0;100 into 'used_prct'=26.93%;0:80;0:90;0;100 'used_prct_max'=100%;;;; |
--change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target[,[<new-unit-of-mesure>],[min],[max]] Common examples: onvert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic_in,,percent()' =back |
--change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target[,[<new-unit-of-mesure>],[min],[max]] Common examples: onvert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic_in,,percent()' =back |
--extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target[,[<new-unit-of-mesure>],[min],[max]] Common examples: onvert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic_in,,percent()' =back |
--extend-perfdata-group | Add new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,<names-of-new-metrics>,calculation[,[<new-unit-of-mesure>],[min],[max]] regex: regular expression <names-of-new-metrics>: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated <new-unit-of-mesure> (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: um wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets_wrong,sum(packets_(discard|error)_(in|out))' Sum traffic by interface: --extend-perfdata-group='traffic_in_(.*),traffic_$1,sum(traffic_(in|out)_$1)' =back |
--change-short-output --change-long-output | Modify the short/long output that is returned by the plugin. Syntax: --change-short-output=pattern |
--change-short-output | Modify the short/long output that is returned by the plugin. Syntax: --change-short-output=pattern |
--change-long-output | Modify the short/long output that is returned by the plugin. Syntax: --change-short-output=pattern |
--change-exit | Replace an exit code with one of your choice. Example: adding --change-exit=unknown=critical will result in a CRITICAL state instead of an UNKNOWN state. |
--change-output-adv | Replace short output and exit code based on a "if" condition using the following variables: short_output, exit_code. Variables must be written either %{variable} or %(variable). Example: adding --change-output-adv='%(short_ouput) =~ /UNKNOWN: No daemon/,OK: No daemon,OK' will change the following specific UNKNOWN result to an OK result. |
--range-perfdata | Rewrite the ranges displayed in the perfdata. Accepted values: 0: nothing is changed. 1: if the lower value of the range is equal to 0, it is removed. 2: remove the thresholds from the perfdata. |
--filter-uom | Mask the units when they don't match the given regular expression. |
--opt-exit | Replace the exit code in case of an execution error (i.e. wrong option provided, SSH connection refused, timeout, etc). Default: unknown. |
--output-ignore-perfdata | Remove all the metrics from the service. The service will still have a status and an output. |
--output-ignore-label | Remove the status label ("OK:", "WARNING:", "UNKNOWN:", CRITICAL:") from the beginning of the output. Example: 'OK: Ram Total:...' will become 'Ram Total:...' |
--output-xml | Return the output in XML format (to send to an XML API). |
--output-json | Return the output in JSON format (to send to a JSON API). |
--output-openmetrics | Return the output in OpenMetrics format (to send to a tool expecting this format). |
--output-file | Write output in file (can be combined with JSON, XML and OpenMetrics options). Example: --output-file=/tmp/output.txt will write the output in /tmp/output.txt. |
--disco-format | Applies only to modes beginning with 'list-'. Returns the list of available macros to configure a service discovery rule (formatted in XML). |
--disco-show | Applies only to modes beginning with 'list-'. Returns the list of discovered objects (formatted in XML) for service discovery. |
--float-precision | Define the float precision for thresholds (default: 8). |
--source-encoding | Define the character encoding of the response sent by the monitored resource Default: 'UTF-8'. <output>. |
--ssh-backend | Define the backend you want to use. It can be: sshcli (default), plink and libssh . |
--ssh-username | Define the user name to log in to the host. |
--ssh-password | Define the password associated with the user name. Cannot be used with the sshcli backend. Warning: using a password is not recommended. Use --ssh-priv-key instead. |
--ssh-port | Define the TCP port on which SSH is listening. |
--ssh-priv-key | Define the private key file to use for user authentication. |
--memcached | Memcached server to use (only one server). |
--redis-server | Redis server to use (only one server). Syntax: address[:port] |
--redis-attribute | Set Redis Options (--redis-attribute="cnx_timeout=5"). |
--redis-db | Set Redis database index. |
--failback-file | Fall back on a local file if Redis connection fails. |
--memexpiration | Time to keep data in seconds (default: 86400). |
--statefile-dir | Define the cache directory (default: '/var/lib/centreon/centplugins'). |
--statefile-suffix | Define a suffix to customize the statefile name (default: ''). |
--statefile-concat-cwd | If used with the '--statefile-dir' option, the latter's value will be used as a sub-directory of the current working directory. Useful on Windows when the plugin is compiled, as the file system and permissions are different from Linux. |
--statefile-format | Define the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default). |
--statefile-key | Define the key to encrypt/decrypt the cache. |
--statefile-cipher | Define the cipher algorithm to encrypt the cache (default: 'AES'). |
--hostname | Hostname to query. |
--timeout | Timeout in seconds for the command (default: 45). |
--command | Command to get information. Used it you have output in a file. |
--command-path | Command path. |
--command-options | Command options. |
--cache-use | Use the cache file (created with cache mode). |
Modes options​
All available options for each service template are listed below:
- BGP
- CPU
- Disks
- Hardware
- Interfaces
- LDP-session
- LSP
- Memory
- OSPF
- RPM-services
- RSVP-sessions
Option | Description |
---|---|
--filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx|yyyy$' |
--filter-snmp-index | Filter BGP peer by SNMP index. |
--filter-local-address | Filter BGP peer by local address. |
--filter-peer-address | Filter BGP peer by peer address. |
--filter-rib-name | Filter BGP RIB by RIB name. |
--custom-perfdata-instances-bgp-peer | Define performance data instances (default: '%(localAddr) %(peerAddr)') |
--unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{localAddr}, %{localAs}, %{peerAddr}, %{peerAs}, %{peerState} |
--warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{localAddr}, %{localAs}, %{peerAddr}, %{peerAs}, %{peerState} |
--critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{peerState} !~ /established/i'). You can use the following variables: %{localAddr}, %{localAs}, %{peerAddr}, %{peerAs}, %{peerState} |
--unknown-rib-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{localAddr}, %{localAs}, %{peerAddr}, %{peerAs}, %{peerState}, %{ribName}, %{sendState} |
--warning-rib-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{localAddr}, %{localAs}, %{peerAddr}, %{peerAs}, %{peerState}, %{ribName}, %{sendState} |
--critical-rib-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{localAddr}, %{localAs}, %{peerAddr}, %{peerAs}, %{peerState}, %{ribName}, %{sendState} |
--warning-bgp-peer-detected | Warning threshold for number of BGP peers detected. |
--critical-bgp-peer-detected | Critical threshold for number of BGP peers detected. |
--warning-bgp-peer-traffic-in | Warning threshold for BGP peer traffic in. |
--critical-bgp-peer-traffic-in | Critical threshold for BGP peer traffic in. |
--warning-bgp-peer-traffic-out | Warning threshold for BGP peer traffic out. |
--critical-bgp-peer-traffic-out | Critical threshold for BGP peer traffic out. |
Option | Description |
---|---|
--filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx|yyyy$' |
--filter-name | Filter CPU by name. |
--warning-average-1m | Warning threshold for 1 minute average CPU usage (%). |
--critical-average-1m | Critical threshold for 1 minute average CPU usage (%). |
--warning-average-5m | Warning threshold for 5 minutes average CPU usage (%). |
--critical-average-5m | Critical threshold for 5 minutes average CPU usage (%). |
--warning-average-15m | Warning threshold for 15 minutes average CPU usage (%). |
--critical-average-15m | Critical threshold for 15 minutes average CPU usage (%). |
Option | Description |
---|---|
--filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx|yyyy$' |
--filter-name | Filter disks by name (can be a regexp). |
--warning-space-usage | Warning threshold for space usage (in bytes). |
--critical-space-usage | Critical threshold for space usage (in bytes). |
--warning-space-usage-free | Warning threshold for free space (in bytes). |
--critical-space-usage-free | Critical threshold for free space (in bytes). |
--warning-space-usage-prct | Warning threshold for space usage (in percentage). |
--critical-space-usage-prct | Critical threshold for space usage (in percentage). |
Option | Description |
---|---|
--component | Which component to check (default: '.*'). Can be: afeb , fan , fpc , mic , pic , psu , temperature . |
--filter | Exclude the items given as a comma-separated list (example: --filter=fan ). You can also exclude items from specific instances: C<--filter=fan,Top> |
--absent-problem | Return an error if a component is not 'present' (default is skipping). It can be set globally or for a specific instance: --absent-problem='component_name' or --absent-problem='component_name,instance_value'. |
--no-component | Define the expected status if no components are found (default: critical ). |
--threshold-overload | Use this option to override the status returned by the plugin when the status label matches a regular expression (syntax: section,[instance,]status,regexp). Example: C<--threshold-overload='fpc,CRITICAL,Unknown'> |
--warning | Set warning threshold (syntax: type,regexp,threshold) Example: C<--warning='temperature,.*,30'> |
--critical | Set critical threshold (syntax: type,regexp,threshold) Example: C<--critical='temperature,.*,40'> |
--warning-count-* | Define the warning threshold for the number of components of one type (replace '*' with the component type). |
--critical-count-* | Define the critical threshold for the number of components of one type (replace '*' with the component type). |
Option | Description |
---|---|
--filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx|yyyy$' |
--add-status | Check interface status. |
--add-traffic | Check interface traffic. |
--add-errors | Check interface errors. |
--add-extra-errors | Check interface detailed errors. |
--add-optical | Check interface optical. |
--warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: C<%{admstatus}>, C<%{opstatus}>, C<%{display}> |
--critical-status | Define the conditions to match for the status to be CRITICAL (default: C<'%{admstatus} eq "up" and %{opstatus} ne "up"'>). You can use the following variables: C<%{admstatus}>, C<%{opstatus}>, C<%{display}> |
--warning-bias-current | Threshold in mA. |
--critical-bias-current | Threshold in mA. |
--warning-in-discard | Threshold. |
--critical-in-discard | Threshold. |
--warning-in-drop | Threshold. |
--critical-in-drop | Threshold. |
--warning-in-error | Threshold. |
--critical-in-error | Threshold. |
--warning-in-fcserror | Threshold. |
--critical-in-fcserror | Threshold. |
--warning-in-fifo-error | Threshold. |
--critical-in-fifo-error | Threshold. |
--warning-in-giant | Threshold. |
--critical-in-giant | Threshold. |
--warning-in-l2-mismatch-timeout | Threshold. |
--critical-in-l2-mismatch-timeout | Threshold. |
--warning-in-l3-incomplete | Threshold. |
--critical-in-l3-incomplete | Threshold. |
--warning-in-resource-error | Threshold. |
--critical-in-resource-error | Threshold. |
--warning-in-runts | Threshold. |
--critical-in-runts | Threshold. |
--warning-in-traffic | Threshold. |
--critical-in-traffic | Threshold. |
--warning-input-power | Threshold in dBm. |
--critical-input-power | Threshold in dBm. |
--warning-module-temperature | Threshold in C. |
--critical-module-temperature | Threshold in C. |
--warning-out-aged | Threshold. |
--critical-out-aged | Threshold. |
--warning-out-carrier-transition | Threshold. |
--critical-out-carrier-transition | Threshold. |
--warning-out-collision | Threshold. |
--critical-out-collision | Threshold. |
--warning-out-discard | Threshold. |
--critical-out-discard | Threshold. |
--warning-out-drop | Threshold. |
--critical-out-drop | Threshold. |
--warning-out-error | Threshold. |
--critical-out-error | Threshold. |
--warning-out-fifo-error | Threshold. |
--critical-out-fifo-error | Threshold. |
--warning-out-hslink-crc-error | Threshold. |
--critical-out-hslink-crc-error | Threshold. |
--warning-out-mtu-error | Threshold. |
--critical-out-mtu-error | Threshold. |
--warning-out-resource-error | Threshold. |
--critical-out-resource-error | Threshold. |
--warning-out-traffic | Threshold. |
--critical-out-traffic | Threshold. |
--warning-output-power | Threshold in dBm. |
--critical-output-power | Threshold in dBm. |
--units-traffic | Units of thresholds for the traffic (default: percent\_delta ) (percent\_delta , bps , counter ). |
--units-errors | Units of thresholds for errors/discards (default: percent\_delta ) (percent\_delta , percent , delta , counter ). |
--filter-use | Define the value to be used to filter interfaces (default: name ) (values: name , descr ). |
--display-use | Define the value that will be used to name the interfaces (default: name ) (values: name , descr ). |
--filter-interface | Filter interface name (regexp can be used). |
--exclude-interface | Exclude interface name (regexp can be used). |
--speed | Set interface speed (in Mb). |
Option | Description |
---|---|
--filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx|yyyy$' |
--filter-id | Filter LDP session by ID. |
--filter-remote-address | Filter LDP session by remote address. |
--custom-perfdata-instances | Define performance data instances (default: C<%(remoteAddress) %(messageType)>) |
--unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: C<%{id}>, C<%{remoteAddress}>, C<%{connectionState}>, C<%{sessionState}> |
--warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: C<%{id}>, C<%{remoteAddress}>, C<%{connectionState}>, C<%{sessionState}> |
--critical-status | Define the conditions to match for the status to be CRITICAL (default: C<'%{connectionState} !~ /open$/i || %{sessionState} !~ /operational/i'>). You can use the following variables: C<%{id}>, C<%{remoteAddress}>, C<%{connectionState}>, C<%{sessionState}> |
--warning-ldp-session-messages-address-received | Threshold. |
--critical-ldp-session-messages-address-received | Threshold. |
--warning-ldp-session-messages-address-sent | Threshold. |
--critical-ldp-session-messages-address-sent | Threshold. |
--warning-ldp-session-messages-address-withdraw-received | Threshold. |
--critical-ldp-session-messages-address-withdraw-received | Threshold. |
--warning-ldp-session-messages-address-withdraw-sent | Threshold. |
--critical-ldp-session-messages-address-withdraw-sent | Threshold. |
--warning-ldp-session-messages-initialization-received | Threshold. |
--critical-ldp-session-messages-initialization-received | Threshold. |
--warning-ldp-session-messages-initialization-sent | Threshold. |
--critical-ldp-session-messages-initialization-sent | Threshold. |
--warning-ldp-session-messages-keeaplive-received | Threshold. |
--critical-ldp-session-messages-keeaplive-received | Threshold. |
--warning-ldp-session-messages-keeaplive-sent | Threshold. |
--critical-ldp-session-messages-keeaplive-sent | Threshold. |
--warning-ldp-session-messages-label-abort-received | Threshold. |
--critical-ldp-session-messages-label-abort-received | Threshold. |
--warning-ldp-session-messages-label-abort-sent | Threshold. |
--critical-ldp-session-messages-label-abort-sent | Threshold. |
--warning-ldp-session-messages-label-mapping-received | Threshold. |
--critical-ldp-session-messages-label-mapping-received | Threshold. |
--warning-ldp-session-messages-label-mapping-sent | Threshold. |
--critical-ldp-session-messages-label-mapping-sent | Threshold. |
--warning-ldp-session-messages-label-release-received | Threshold. |
--critical-ldp-session-messages-label-release-received | Threshold. |
--warning-ldp-session-messages-label-release-sent | Threshold. |
--critical-ldp-session-messages-label-release-sent | Threshold. |
--warning-ldp-session-messages-label-request-received | Threshold. |
--critical-ldp-session-messages-label-request-received | Threshold. |
--warning-ldp-session-messages-label-request-sent | Threshold. |
--critical-ldp-session-messages-label-request-sent | Threshold. |
--warning-ldp-session-messages-label-withdraw-received | Threshold. |
--critical-ldp-session-messages-label-withdraw-received | Threshold. |
--warning-ldp-session-messages-label-withdraw-sent | Threshold. |
--critical-ldp-session-messages-label-withdraw-sent | Threshold. |
--warning-ldp-session-messages-notification-received | Threshold. |
--critical-ldp-session-messages-notification-received | Threshold. |
--warning-ldp-session-messages-notification-sent | Threshold. |
--critical-ldp-session-messages-notification-sent | Threshold. |
--warning-ldp-sessions-detected | Threshold. |
--critical-ldp-sessions-detected | Threshold. |
Option | Description |
---|---|
--filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx|yyyy$' |
--filter-type | Filter LSP session by type. |
--filter-name | Filter LSP session by name. |
--custom-perfdata-instances | Define performance data instances (default: C<'%(type) %(name)'>) |
--unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: C<%{type}>, C<%{name}>, C<%{srcAddress}>, C<%{dstAddress}>, C<%{lspState}> |
--warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: C<%{type}>, C<%{name}>, C<%{srcAddress}>, C<%{dstAddress}>, C<%{lspState}> |
--critical-status | Define the conditions to match for the status to be CRITICAL (default: '%{lspState} !~ /up/i'). You can use the following variables: C<%{type}>, C<%{name}>, C<%{srcAddress}>, C<%{dstAddress}>, C<%{lspState}> |
--warning-lsp-sessions-detected | Define the LSP sessions detected conditions to match for the status to be WARNING. |
--critical-lsp-sessions-detected | Define the LSP sessions detected conditions to match for the status to be CRITICAL. |
--warning-lsp-session-traffic | Define the LSP session traffic conditions to match for the status to be WARNING. |
--critical-lsp-session-traffic | Define the LSP session traffic conditions to match for the status to be CRITICAL. |
Option | Description |
---|---|
--filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx|yyyy$' |
--filter-name | Filter memory by name. |
--warning-usage-prct | Warning threshold for memory usage (%). |
--critical-usage-prct | Critical threshold for memory usage (%). |
Option | Description |
---|---|
--filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx|yyyy$' |
--filter-neighbor-address | Filter neighbors by address (can be a regexp). |
--unknown-neighbors-changed | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{detectedLast}, %{detected} |
--warning-neighbor-changed | Define the conditions to match for the status to be WARNING. You can use the following variables: %{detectedLast}, %{detected} |
--critical-neighbor-changed | Define the conditions to match for the status to be CRITICAL. You can use the following variables: %{detectedLast}, %{detected} |
--unknown-neighbor-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %{state}, %{address}, %{interfaceName} |
--warning-neighbor-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %{state}, %{address}, %{interfaceName} |
--critical-neighbor-status | Define the conditions to match for the status to be CRITICAL (default: '%{state} =~ /down/i'). You can use the following variables: %{state}, %{address}, %{interfaceName} |
--warning-neighbors-detected | Warning threshold for number of OSPF neighbors detected. |
--critical-neighbors-detected | Critical threshold for number of OSPF neighbors detected. |
Option | Description |
---|---|
--filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx|yyyy$' |
--filter-name | Filter service by name. |
--filter-type | Filter service by type. |
--custom-perfdata-instances | Define performance data instances (default: C<%(testName)>) |
--unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: C<%{testName}>, C<%{probeType}>, C<%{sourceAddress}>, C<%{targetAddress}>, C<%{probeStatus}> |
--warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: C<%{testName}>, C<%{probeType}>, C<%{sourceAddress}>, C<%{targetAddress}>, C<%{probeStatus}> |
--critical-status | Define the conditions to match for the status to be CRITICAL. You can use the following variables: C<%{testName}>, C<%{probeType}>, C<%{sourceAddress}>, C<%{targetAddress}>, C<%{probeStatus}> |
--warning-services-detected | Define the services detected conditions to match for the status to be WARNING. |
--critical-services-detected | Define the services detected conditions to match for the status to be CRITICAL. |
--warning-service-rpm-probe-loss-percentage | Define the service RPM probe loss percentage conditions to match for the status to be WARNING. |
--critical-service-rpm-probe-loss-percentage | Define the service RPM probe loss percentage conditions to match for the status to be CRITICAL. |
--warning-service-rpm-probe-rtt-delay-average | Define the service RPM probe route-trip time delay average conditions to match for the status to be WARNING. |
--critical-service-rpm-probe-rtt-delay-average | Define the service RPM probe route-trip time delay average conditions to match for the status to be CRITICAL. |
--warning-service-rpm-probe-rtt-delay-jitter | Define the service RPM probe route-trip time delay jitter conditions to match for the status to be WARNING. |
--critical-service-rpm-probe-rtt-delay-jitter | Define the service RPM probe route-trip time delay jitter conditions to match for the status to be CRITICAL. |
--warning-service-rpm-probe-rtt-delay-stdev | Define the service RPM probe route-trip time delay standard deviation conditions to match for the status to be WARNING. |
--critical-service-rpm-probe-rtt-delay-stdev | Define the service RPM probe route-trip time delay standard deviation conditions to match for the status to be CRITICAL. |
--warning-service-rpm-probe-prtj-delay-average | Define the service RPM probe positive round trip jitter delay average conditions to match for the status to be WARNING. |
--critical-service-rpm-probe-prtj-delay-average | Define the service RPM probe positive round trip jitter delay average conditions to match for the status to be CRITICAL. |
--warning-service-rpm-probe-prtj-delay-jitter | Define the service RPM probe positive round trip jitter delay jitter conditions to match for the status to be WARNING. |
--critical-service-rpm-probe-prtj-delay-jitter | Define the service RPM probe positive round trip jitter delay jitter conditions to match for the status to be CRITICAL. |
--warning-service-rpm-probe-prtj-delay-stdev | Define the service RPM probe positive round trip jitter delay standard deviation conditions to match for the status to be WARNING. |
--critical-service-rpm-probe-prtj-delay-stdev | Define the service RPM probe positive round trip jitter delay standard deviation conditions to match for the status to be CRITICAL. |
--warning-service-rpm-probe-nrtj-delay-average | Define the service RPM probe negative round trip jitter delay average conditions to match for the status to be WARNING. |
--critical-service-rpm-probe-nrtj-delay-average | Define the service RPM probe negative round trip jitter delay average conditions to match for the status to be CRITICAL. |
--warning-service-rpm-probe-nrtj-delay-jitter | Define the service RPM probe negative round trip jitter delay jitter conditions to match for the status to be WARNING. |
--critical-service-rpm-probe-nrtj-delay-jitter | Define the service RPM probe negative round trip jitter delay jitter conditions to match for the status to be CRITICAL. |
--warning-service-rpm-probe-nrtj-delay-stdev | Define the service RPM probe negative round trip jitter delay standard deviation conditions to match for the status to be WARNING. |
--critical-service-rpm-probe-nrtj-delay-stdev | Define the service RPM probe negative round trip jitter delay standard deviation conditions to match for the status to be CRITICAL. |
Option | Description |
---|---|
--filter-counters | Only display some counters (regexp can be used). Example to check SSL connections only : --filter-counters='^xxxx|yyyy$' |
--filter-name | Filter RSVP session by name. |
--filter-type | Filter RSVP session by type. |
--custom-perfdata-instances | Define performance data instances (default: C<'%(type) %(name)'>) |
--unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: C<%{type}>, C<%{name}>, C<%{srcAddress}>, C<%{dstAddress}>, C<%{lspState}> |
--warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: C<%{type}>, C<%{name}>, C<%{srcAddress}>, C<%{dstAddress}>, C<%{lspState}> |
--critical-status | Define the conditions to match for the status to be CRITICAL (default: C<'%{lspState} !~ /up/i'>). You can use the following variables: C<%{type}>, C<%{name}>, C<%{srcAddress}>, C<%{dstAddress}>, C<%{lspState}> |
--warning-rsvp-sessions-detected | Define the RSVP sessions detected conditions to match for the status to be WARNING. |
--critical-rsvp-sessions-detected | Define the RSVP sessions detected conditions to match for the status to be CRITICAL. |
--warning-rsvp-session-lsp-traffic | Define the RSVP session traffic conditions to match for the status to be WARNING. |
--critical-rsvp-session-lsp-traffic | Define the RSVP session traffic conditions to match for the status to be CRITICAL. |
All available options for a given mode can be displayed by adding the
--help
parameter to the command:
/usr/lib/centreon/plugins/centreon_juniper_mseries_netconf.pl \
--plugin=network::juniper::mseries::netconf::plugin \
--mode=rsvp \
--help