Getting a Quick Start with NerveCenter - Working with Behavior Models - Enabling the IfData_LogToFile Behavior Model -
Importing the IfData_LogToFile Behavior Model      Enabling the IfLoad Behavior Model

Enabling the IfData_LogToFile Behavior Model

The IfData_LogToFile behavior model repeatedly logs interface attribute values that help you track bandwidth and data-flow levels over a period of time. You can use these values to establish baselines, identify user patterns, determine network utilization, and anticipate potential problems. Because you can change the attributes that are logged, you can use this behavior model to identify and log a variety of information about your network.

Viewing the IfData_LogToFile Alarm

The IfData_LogToFile alarm -- a key element of the behavior model -- is instantiated when a node returns values for all the attributes that are polled. To see how the alarm accomplishes this, open the alarm's definition window.

 
  To open the IfData_LogToFile Alarm Definition window:

  1. alarmShaded From the client's Admin menu, choose Alarm Definition List.

    The Alarm Definition List window is displayed. All alarms are turned off by default when you install NerveCenter.

    AlarmDefList_IfDataLogger

  2. Select the IfData_LogToFile alarm and select Open.

    The Alarm Definition window is displayed. Below is a picture of the alarm's finite state diagram.

    IfData_LogToFile Alarm State Diagram

    stateDiagram_IfDataLogger4

As you can see from the diagram, the alarm contains two states:

The alarm also contains two ifData transitions. The name assigned to a transition is based on the name of the trigger that causes the transition to occur.

In this alarm, the first ifData trigger instantiates the alarm, which transitions to the Logging state and automatically writes alarm data to a file. Subsequent ifData triggers continue the logging action.

Both states in the diagram have green icons. The color of a state icon indicates the severity level associated with that state. In this case, both states have a severity of Normal.

Select Notes to see a description of the alarm, including its severities, any polls or masks that trigger the alarm, any actions associated with a transition, and other useful information.

Poll that Triggers the Alarm

Only one poll is associated with this alarm -- the IfData poll. This poll is configured to solicit attribute values for certain base object attributes belonging to the interfaces MIB-II group. The poll fires the ifData trigger when these values are detected in a node.

To see how the poll accomplishes this, open the poll's definition window.

 
  To open the IfData Poll Definition window:

  1. pollShaded From the client's Admin menu, choose Poll List.

    The Poll List window is displayed. All polls are turned on by default when you install NerveCenter.

    pollList

  2. Select the IfData poll and select Open.

    The IfData Poll Definition window is displayed.

    PollDefinition

The Designing and Managing Behavior Models book shipped with NerveCenter describes polls in detail. For now, however, you will take only a cursory look at the IfData poll. Note specifically the following poll attributes:

The data-entry fields in the definition window are unavailable when the poll is on. If you want to make changes, for example by changing the poll rate, you must do the following:

 
  To make changes to a poll:

  1. In the Poll Definition window, select the Enable Off radio button.
  2. Make the changes you want to the poll.
  3. Select Save.
  4. Select the Enable On radio button and then select Save.

    This turns the updated poll back on.

The ifData poll solicits information for MIB values found in the Interfaces group in MIB-II. Each value represents one instance of the Interfaces ifEntry base object. MIB Values Detected by the ifData Poll contains a brief description of these MIB values:

MIB Values Detected by the ifData Poll

Value Description

ifType

Specific type of interface, for example, Ethernet.

ifSpeed

The interface's current estimated bandwidth measured in bits per second.

ifInOctets

The total number of octets received by the interface.

ifInUcastPkts

The number of subnetwork unicast packets delivered to the interface.

ifInNUcastPkts

The number of subnetwork nonunicast packets delivered to the interface.

ifInDiscards

The number of inbound packets that were discarded for reasons other than errors.

ifInErrors

The number of inbound packets that were not delivered to the interface because of errors.

ifOutOctets

The total number of octets sent from the interface.

ifOutUcastPkts

The number of packets requested to be transmitted to a subnet unicast address.

ifOutNUcastPkts

The number of packets requested to be transmitted to a subnet nonunicast address.

ifOutDiscards

The number of outbound packets that were discarded for reasons other than errors.

ifOutErrors

The number of outbound packets that were not sent because of errors.


Turning on the Alarm

You enable the IfData_LogToFile behavior model by turning on its alarm and poll. In our case, because all polls are turned on by default when you install NerveCenter, you need only turn on the alarm.

 
  To turn on the IfData_LogToFile alarm:

  1. alarmShaded From the client's Admin menu, choose Alarm Definition List.

    The Alarm Definition List window is displayed.

  2. Select the IfData_LogToFile alarm and select Open.

    The Alarm Definition window is displayed.

  3. Select the Enabled On radio button.
  4. Select Save.

The IfData_LogToFile alarm is now enabled and will transition when the defined MIB attributes are detected on one of the nodes you defined.


Importing the IfData_LogToFile Behavior Model Enabling the IfLoad Behavior Model
29 July 2003