network Integration
mib-ii-interface (en)


ServicePilot network-mib-ii-interface


# MIB-II Interface

Overview

This package is designed to monitor a standard MIB-II Interface or Interface list using SNMP.

Description

This package automatically configures the ServicePilot Manager to monitor Standard Network Interface in terms of load, traffic, discards, errors and speed in 32 or 64 bits based on an SNMP collection.

Requirements

  • SNMP must be configured and started on the MIB-II Interface Device

  • Network Flows - It is necessary to ensure network connectivity between ServicePilot and the monitored device. In case of a network infrastructure with a firewall, all of the following flows must be opened:

    • UDP/161 (SNMP): Between ServicePilot Manager and the network device
    • UDP/162 (SNMP Trap): (Optional) Between the network device and ServicePilot Agent
  • ServicePilot Requirements

    • ServicePilot Manager minimum version: 8.5

Installation

Before adding a resource to monitor, make certain that all pre-requisites are in place and if a ServicePilot Agent is required, that it is communicating correctly with the ServicePilot Manager. Resources can be added to ServicePilot configuration in a number of ways:

Add resource using Views Configuration web interface

  1. As an administrative user of ServicePilot, open the ServicePilot web interface.
  2. Navigate to Administration. The Configuration > Views web page will open.
  3. Click on the view in which to place the new resource in the Views hierarchy on the left of the interface. The View editor section will show the existing view contents.
  4. From the Packages list on the right of the interface, click and drag the network-mib-ii-interface package into the View editor and let go.
  5. The Package properties dialog box will open to allow resource configuration.
  6. Click OK to close the Package properties dialog box. Note that the dialog box will not close if required parameters are not set.
  7. Click Save to apply the new resource to ServicePilot configuration.

Add resource by changing servicepilot.conf configuration file

Resources can be added to ServicePilot configuration by directly editing the servicepilot.conf or other included YAML configuration files. The ServicePilot web interface can be used to make these changes and apply them to the running configuration.

  1. As an administrative user of ServicePilot, open the ServicePilot web interface.
  2. Navigate to Administration.
  3. Navigate to Configuration > Edit configuration.
  4. Expand the configuration to find the provisioning: and then packages: section of the view in which the new resource will be placed.
  5. Add the example package configuration line below.
  6. Click on the green - package: word to open then Package properties dialog box to allow resource configuration.
  7. Click OK to close the Package properties dialog box. Note that the dialog box will not close if required parameters are not set.
  8. Click Save to apply the new resource to ServicePilot configuration.

Example:

- package: "network-mib-ii-interface;;;;;;;;network-mib-ii-interface;;127.0.0.1;Auto-Discovery;N;;;;;;No;;Picture"

Key field notes

In the Monitoring Policies tab, specify the policy or policies to apply to the package

  1. Basic Parameters tab:

    1. IP address/FQDN: Specify the IP address, host name or FQDN for the MIB-II Interface, as resolvable by the machine on which ServicePilot Manager is running
  2. Interface Type tab: Select the interface creation type,

    1. Auto-Discovery: a separate interface object is created for all interfaces discovered
    2. Single: a single object is created for the specified interface to be monitored
    3. None: only the classes are defined and no views or objects are added to the configuration
  3. Interface Discovery and Filtering tab:

    1. Use Interface filter instead of Addressing Information: tick to get statistics for a specified list on interfaces only. Set it off to get statistics for all available interfaces
    2. {Optional} Ignored Interfaces names separated with '|': Specify name(s) of interface(s) NOT to be monitored
    3. {Optional} Allowed Interfaces names separated with '|': Specify name(s) of interface(s) to be monitored

      Note: Each element of the interface lists is a regular expression as defined by Like Operator (Visual Basic)

  4. Default Interface Parameter Overrides tab:

    1. SNMP Table Index: Specify the index of the interface to be monitored (for Single interface type)
    2. ifSpeed In for Asymetrical Interface (bps): Specify maximum download speed (empty => use ifSpeed)
    3. ifSpeed Out for Asymetrical Interface (bps): Specify maximum upload speed (empty => use ifSpeed)

      Note: The creation type must be single to be able to specify the speed

    4. Redundant Interface Group: Select Yes to have the device failing if all interface fail

      Note: The creation type must be not be single to be able to choose between Yes and No

    5. {Optional} Custom interface speed separated with '|': Specify speed of the interface

  5. Graphical tab:

    1. Interface creation type: Specify how the interfaces will appear in the map

Notes

MIB Used:

RFC1213-MIB2

network mib-ii-interface 0

network mib-ii-interface 1

network mib-ii-interface 2