The Interface MIB monitor is used to monitor interfaces on SNMP-enabled devices. It uses BMC ProactiveNet Auto Discovery Framework. The Auto Discovery engine discovers all available managed object instances available on a given device during monitor instance creation. After discovery, BMC ProactiveNet server automatically creates child level instances of Interface MIB monitor for each of the devices. Based on the Auto Discovery Poll Period, the Auto Discovery Engine periodically polls the specified device to determine if new instances are to be added or existing instances are to be updated or removed.
Monitored attributes for Interface MIB monitors
The following table lists the monitored attributes of an Interface MIB monitor.
| Attribute | Description |
|---|---|
| Availability (%) | Availability indicates whether interface is available or not. By default, availability is reported as 100% if Admin state is “up” or “down” and Operational statusstate is “up”. Availability state can be configured using the monitor configuration file InterfaceMIBMon.conf in installDirectory \monitors\monitors\InterfaceMIBMon directory. |
| Out Utilization (%) | Octets transmitted out of the interface (including framing characters) expressed as a percentage of the available bandwidth. |
| In Utilization (%) | Octets received on the interface (including framing characters) expressed as a percentage of the available bandwidth. |
| In Broadcast Pkts (%) | Percentage of non-unicast (i.e., subnetwork- broadcast or subnetwork-multicast) packets being delivered to a higher-layer protocol. |
| In Discards (%) | Percentage of inbound packets discarded for reasons other than content error. These packets are otherwise fit to be delivered to a higher-layer protocol. For example, packets may be discarded to free buffer space. |
| In Errors (%) | Percentage of inbound packets discarded for content errors. These packets contain errors and cannot be delivered to higher-layer protocol. |
| Out Broadcast Pkts (%) | Percentage of packet transmission from a non-unicast (i.e., a subnetwork-broadcast or subnetwork-multicast) address requested by a higher-level protocols. This includes packets that were discarded or not transmitted. |
| Out Discards (%) | Percentage of outbound packets discarded for reasons other than content error. These packets are otherwise fit for transmission. For example, packets may be discarded to free buffer space. |
| Out Errors (%) | Percentage of outbound packets discarded for content errors. These packets contain errors and cannot be transmitted. |
| Total In Pkts (pkts/sec) | Rate of delivery of subnetwork-unicast packets to a higher-layer protocol. |
| Total Out Pkts (pkts/sec) | Rate of packet transmission from subnetwork-unicast address requested by a higher-level protocol. This includes packets discarded or not transmitted. |
| Admin Status (#) | Administrative status of the Interface. Available states are: Up (1), Down (2), and Testing (3). |
| Operational Status (#) | Current operational state of the interface. Available states are: Up (1), Down (2), Testing (3), Unknown (4), Dormant (5), Not Present (6), and Down due to lower layer interfaces (7). |
| Interface Type (#) | Type of interface, distinguished according to the physical/link protocol(s) immediately below the network layer in the protocol stack. Valid codes are: Other (1), Regular1822 (2), hdh1822 (3), ddn-x25 (4), rfc877-x25 (5), ethernet-csmacd (6), iso88023-csmacd (7), iso88024-tokenBus (8), iso88025-tokenRing (9), iso88026-man (10), starLan (11), proteon-10Mbit (12), proteon-80Mbit (13), hyperchannel (14), fddi (15), lapb (16), sdlc (17), ds1 (18), e1 (19), basicISDN (20), primaryISDN (21), propPointToPointSerial (22), ppp (23), softwareLoopback (24), eon (25), ethernet-3Mbit (26), nsip (27), slip (28), ultra (29), ds3 (30), sip (31), and frame-relay (32). |
Configuration information for Interface MIB monitors
The following table describes the information required during configuration of the Interface MIB monitor.
| Configuration information | Description |
|---|---|
| Input fields on the Configuration tab | |
| InterfaceMon | Specify the instance name for the child monitor (interface monitor) at parent level.
Example: INSTANCE_ID=2,IF_IP_ADDRESS=192.168.3.249,IF_SLOT=0,IF_PORT=0,IF SPEED=100000000,IF_PORT_NAME=null,IF_ALIAS=null,IF_DESC |
| Tag | Specify a tag value to search or group the objects. You can enter multiple name-value pairs, text, or include both (name-value pair and text). This gives you the option to group objects in different forms. Click the + icon to select a default tag class. The Enter Tag Details screen opens. Select Tag Class from the drop-down list and enter a tag value. Click Add to append tag class and value. Click Finish. The tag specified by you is not considered as a default class. You cannot enter special characters &"/<>' in the tag field.
|
| Source Agent | Select the BMC ProactiveNet agent on which the monitor instance is to be created. |
| Port | Specify the port number on which the SNMP agent is running. Default port is 161. |
| Community String | Specify the read community string of the SNMP agent. Default string is 'public'. |
| SNMP Retries | Specify the number of failed data requests (from BMC ProactiveNet server to target device) for BMC ProactiveNet server to generate an event. Default is 2. |
| SNMP Timeout | Specify the time (in seconds) for which BMC ProactiveNet server must wait for data from the device before reporting an event. Default is 2 seconds. |
| SNMP Version | Select the SNMP version to be used to connect to the remote SNMP agent. If you select v3, complete the required details in the SNMPv3 Details tab. If the version selected is v2 or v3, then the value of ifHighSpeed is used as interface speed. |
| Use IfEntry | Select check box to use IfEntry MIB. By default, this option is not selected. IfEntry MIB is used for SNMP v1. For SNMP v2 and v3, the extended MIB IFXEntry is used. On some devices the new extended MIB IfXEntry is not available for SNMP v2 and v3 also. In such cases, select the Use IfEntry option so that monitor instance polls the IfEntry MIB to get data. |
| System-populated fields | |
| Admin Status | Administrative status of the Interface. Available states are: Up (1), Down (2), and Testing (3). |
| Description | Brief description about the interface. |
| IF# | The Interface number. |
| IP Address | IP address of the interface. |
| MAC Address | The MAC address corresponding to the interface at the protocol layer immediately below the network layer in the protocol stack. For interfaces, which do not have such an address (example, a serial line), this object should contain an octet string of zero length. |
| Media Type | The type of interface, distinguished according to the physical/link protocol(s) immediately below the network layer in the protocol stack. Valid codes are: Other (1), Regular1822 (2), hdh1822 (3), ddn-x25 (4), rfc877-x25 (5), ethernet-csmacd (6), iso88023-csmacd (7), iso88024-tokenBus (8), iso88025-tokenRing (9), iso88026-man (10), starLan (11), proteon-10Mbit (12), proteon-80Mbit (13), hyperchannel (14), fddi (15), lapb (16), sdlc (17), ds1 (18), e1 (19), basicISDN (20), primaryISDN (21), propPointToPointSerial (22), ppp (23), softwareLoopback (24), eon (25), ethernet-3Mbit (26), nsip (27), slip (28), ultra (29), ds3 (30), sip (31), and frame-relay (32). |
| Monitor Version | Version of the BMC ProactiveNet monitor installed. |
| Mtu | Size of the largest datagram (in octets), which can be sent/received on the interface. In case of interfaces used for transmitting network datagrams, it is the largest network datagram that can be sent via the interface. |
| Operational Status | The current operational state of the interface. Available states are: Up (1), Down (2), Testing (3), Unknown (4), Dormant (5), Not Present (6), and Down due to lower layer interfaces (7). |
| Port | Index value uniquely identifying the port within a module. |
| Port name | Descriptive string used by the network administrator to name the port. |
| Slot | Index value uniquely identifying the module where the port is located. |
| SNMP Version | The SNMP version in use. |
| Speed | Total bandwidth available on the Interface is displayed in short-hand notation. If device reports incorrect values then edit this attribute to set the correct interface speed. The unit of conversion is 1000. For example, if the speed of the interface is 100000000 b/s then it will display as 100 mb/s. |
| Time Recorded | Date and time of recording configuration information. For monitors running on BMC ProactiveNet agents prior to version 7.0, this field is displayed blank. |
| VLAN | The virtual LAN port. |
| Control tab | |
| Collect Data | Select/clear check box to enable/disable data collection for the monitored component. By default, data collection is enabled (check box selected). |
| Statistics Poll Interval | Specify the time interval between two consecutive Statistical data polls. Default is 5 minutes. |
| Statistics Poll Timeout | Specify the time-out period for each poll of statistical data. If no data is available at the end of this interval, system records zero availability and proceeds with the next scheduled poll. Default is 2 minutes. |
| Configuration Poll Interval | Specify the time interval between two consecutive configuration data polls. Default is 24 hours (One day). |
| Configuration Poll Timeout | Specify the time-out period for each poll of configuration data. If no data is available at the end of this interval, system records zero availability and proceeds with the next scheduled poll. Default is 10 minutes. |
| Auto Discovery Poll Interval | Specify the time interval between two consecutive Auto Discovery polls. Default is 24 hours (One day). |
| Auto Discovery Poll Timeout | Specify the time-out period for each Auto Discovery Poll. If no data is available at the end of this interval, system records zero availability and proceeds with the next scheduled poll. Default is 1 minute. |
| Group tab | |
| Group Membership | This enables you to add a device and its monitors to one or more groups. Optionally, you may associate the device with a group. A group is used to logically organize the devices and monitors by department, geographic area, or service. Assigning a device to a group also enables the system administrator to restrict or allow access to certain devices. To associate the device with a group, select the group name here. |
| SNMPV3 Details tab a | |
| User Name (Security Name) | Specify the user name to access the SNMP agent. |
| Authorization Protocol | Select the authorization protocol (MD5 or SHA) to use. |
| Authorization Password | Specify the authorization password to access the SNMP agent. |
| Privacy Protocol | Select the privacy protocol (CBC-DES) to use. |
| Privacy Password | Specify the privacy password to access the SNMP agent. |
| a This tab is enabled for use only when 'v3' is selected as the SNMP Version in the Configuration tab. | |
Special configuration notes
- BMC ProactiveNet recommends using a dedicated Remote Agent for monitoring more than 100 interfaces. Creating more than 100 Interface MIB monitor instances on the local agent will impact data collection for other monitor instances running on the local agent.
- A regular Server class machine hosting BMC ProactiveNet agent can support up to 1000 Interface MIB monitors without performance impacts. To monitor more than 1000 interfaces, edit pronet.conf and set 'pronet.jvm.maxthreadlimit' value greater than or equal to the number of interfaces to be monitored.
- Some interfaces report wrong speed values and hence monitor instance discards data. This can be verified by checking More Info feature, which reports the reason for data being discarded. In such cases, edit the Speed of the interface and set the correct value. Once the speed is edited, it will not be updated even if the speed of the interface is changed.
- Once speed of an interface is edited, then you cannot rollback to the original interface speed.
Instance naming convention of auto discovered monitor instances
Given below is the hierarchy of how an auto Discovered instance is named:
- ifAlias (if available)
- ifDescription (if Available)
- Interface ID
If Slot and Port Details are available then the same are shown as bracketed text. For example, IfDescription: "IPLC", Slot: 3, and Port: 2. The instance name will be shown as "IPLC (S#3; P#2)".
Recreating deleted instances.
This is a unique feature of Interface MIB monitor.
All Auto Discovery-enabled monitors have a special feature wherein auto-created instances can be deleted and later be recreated whenever required. Deleting an autocreated monitor instance is the same as deleting any other BMC ProactiveNet monitor. The Auto Discovery Engine marks such Interfaces instances as deleted and removes them from BMC ProactiveNet server. But the engine still retains all unique information of the monitor instance so that it can be recreated later whenever required.
When a deleted monitor instance is recreated, data collected previously by the deleted monitor is lost and cannot be retrieved.
To recreate instances from the Administration Console
- Right-click the Interface MIB folder on the selected device.
- Select Recreate Deleted Instances.
The Recreate Deleted Instance window is displayed. The window lists all
Interfaces instances that were deleted since the Interface MIB was created. - Select the Interfaces instances to be recreated.
- Click Recreate.
Automatic instance removal
If an instance is continuously not discovered over a predefined period of time (default is 7 days), the auto created instance is removed from BMC ProactiveNet server. The period of time before an unavailable instance is removed can be configured using the property pronet.autodiscovery.cleanuptime in pronet.conf file (installDirectory \pronto\conf). The period of time must be specified as seconds and by default this property is set to 604800 seconds (7 days).
Additional configuration and setup issues
The following table presents details about Additional configuration and setup issues for the Interface MIB monitor.
| Issue | Details |
|---|---|
| Monitor configuration | No additional configuration requirements for this monitor. Maintain the default configuration of BMC ProactiveNet. |
| External setup | No external setup requirements for this monitor. |
| External dependencies | SNMP Agent must be running on the target machine. |
| BMC ProactiveNet agent dependencies | BMC ProactiveNet agent installation on the monitored host is not mandatory. Monitor instance can be created on any BMC ProactiveNet agent. |
Distributed Interface MIB monitor thresholds
Absolute thresholds for Distributed Interface MIB monitor
| Attribute | Severity | Duration (min) | Flag | Default Threshold | Outside Baseline | Baseline Type |
|---|---|---|---|---|---|---|
| In Utilization | Major | 15 | Above | 80 | Y | ALL |
| Out Utilization | Major | 15 | Above | 80 | Y | ALL |
Signature thresholds for Distributed Interface MIB monitor
| Attribute | Severity | Duration (min) | Flag | Threshold | Sensitivity | Absolute Deviation | % Deviation | Suppress | Baseline Type |
|---|---|---|---|---|---|---|---|---|---|
| In Utilization | Abnormal | 10 | Below | 0 | 50 | 6 | 5 | 0 | Hourly |
| In Utilization | Abnormal | 10 | Above | 0 | 50 | 3 | 5 | 0 | Hourly |
| Out Utilization | Abnormal | 10 | Below | 0 | 50 | 6 | 5 | 0 | Hourly |
| Out Utilization | Abnormal | 10 | Above | 0 | 50 | 3 | 5 | 0 | Hourly |
| In Errors | Abnormal | 10 | Below | 0 | 0 | 0 | 5 | 1 | Hourly |
| In Errors | Abnormal | 10 | Above | 0 | 50 | 5 | 5 | 0 | Hourly |
| In Discards | Abnormal | 10 | Below | 0 | 0 | 0 | 5 | 1 | Hourly |
| In Discards | Abnormal | 10 | Above | 0 | 50 | 5 | 5 | 0 | Hourly |
| Out Discards | Abnormal | 10 | Below | 0 | 0 | 0 | 5 | 1 | Hourly |
| Out Discards | Abnormal | 10 | Above | 0 | 50 | 5 | 5 | 0 | Hourly |
| In Broadcast Pkts | Abnormal | 10 | Below | 0 | 0 | 0 | 5 | 1 | Hourly |
| In Broadcast Pkts | Abnormal | 10 | Above | 0 | 0 | 0 | 5 | 1 | Hourly |
| Out Broadcast Pkts | Abnormal | 10 | Below | 0 | 0 | 0 | 5 | 1 | Hourly |
| Out Broadcast Pkts | Abnormal | 10 | Above | 0 | 0 | 0 | 5 | 1 | Hourly |
| In Pkts | Abnormal | 10 | Below | 0 | 0 | 0 | 5 | 1 | Hourly |
| In Pkts | Abnormal | 10 | Above | 0 | 0 | 0 | 5 | 1 | Hourly |
| Out Pkts | Abnormal | 10 | Below | 0 | 0 | 0 | 5 | 1 | Hourly |
| Out Pkts | Abnormal | 10 | Above | 0 | 0 | 0 | 5 | 1 | Hourly |
| Operational Status | Abnormal | 10 | Above | 0 | 50 | 0.25 | 5 | 0 | Hourly |
| Admin Status | Abnormal | 10 | Above | 0 | 50 | 0.25 | 5 | 0 | Hourly |
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks