7.5.2 interface

This section may appear more than once, but it is used only for SNMP data collectors, naturally. The parameters can be divided into three groups: a) condition parameters, b) exclude parameter and c) configuration parameters. The first one regulates the time when an interface falls within the scope of a section; the second one regulates whether the measurement should be created or not and the third one controls the values the system should create the measurement with.

Condition parameters:

For every condition parameter a Perl regular expression may be given as a value, which the system tries to match to the actual value of the interface during equipment creation. So for example, interfaces including the word Uplink can be collected with the expression “ifdecription=Uplink .+”. If one of the values is not specified, then the system disregards that.

·       ifnumber: Sequence number of the interface. Example: the number cannot be bigger than 15: (.|1[0-5])

·       ifdescription: Description of the interface, which appears during normal equipment creation too

·       ifadminstatus: Admin status of the interface. Example: up or testing status: ifadminstatus=(1|3)

·       ifoperstatus: Oper status of the interface. Example: up or testing status: ifoperstatus=(1|3)

·       iftype: Type of the interface. Example: ethernetCsmacd: iftype=6

·       ifspeed: Speed of the interface, in bits/sec

·       if_add_descr: PVSR can use the Cisco specific descriptions for naming the interfaces. If this option is not turned on (this is the default) then this parameter can be used to filter the interfaces based on the Cisco specific description or on the ifAlias

The system contains a “hidden” condition too: it does no accept interfaces for which the interface traffic counter cannot be queried. Similarly to normal equipment configuration, it determines automatically whether the interface traffic measurement should be performed with a 32 or 64 bit counter.

Exclusion parameter

If an interface matches the filter parameters then it is created with the configuration parameters mentioned below, unless the

exclude=1

line is present in the section. If it present then the interface will not be created, so in this case the section acts as an exlusion mechanism. This can be used for example to exclude the interface traffic for the loopback interface.

Configuration parameters:

With the exception of the description, each parameter is optional:

·       description: The name of the created measurement. The <ifdescription> field may be used here, which is automatically replaced by the system with the above defined ifdescription value of the interface.

·       retention: If it’s specified, then not the value set for the equipment is used for the measurement but the one set here. Only a concrete numerical value may be given, not an <input> type

·       interval: If it’s specified, then not the value set for the equipment is used for the measurement but the one set here. Only a concrete numerical value may be given, not an <input> type

·       minimum: If it’s specified in the section, and the system has found fewer number of instances (e.g. interface) than this amount during equipment creation, then it does not create the equipment and displays an error

·       switch: It corresponds to the Switched field in normal equipment creation, with value 1 for yes and 0 for no. By default it is 0

·       inoutoctet: It corresponds to the Traffic field in normal equipment creation with value 1 for yes and 0 for no. By default it is 1

·       inouterror: It corresponds to the Error field in normal equipment creation with value 1 for yes and 0 for no. By default it is 0

·       inoutcarrier: It corresponds to the Carrier field in normal equipment creation with value 1 for yes and 0 for no. By default it is 0

·       peek_y: It corresponds to the Year field in normal equipment creation with value 1 for yes and 0 for no. By default it is 0

·       peek_m: It corresponds to the Month field in normal equipment creation with value 1 for yes and 0 for no. By default it is 0

·       peek_w: It corresponds to the Week field in normal equipment creation with value 1 for yes and 0 for no. By default it is 0

Example:

[interface1]

#Only 100Mbit up interfaces

iftype=6

ifoperstatus=1

ifspeed=100000000

#measure the interface error too

description=<ifdescription>

inouterror=1

#the system has to have at least 3 such interfaces

minimum=3

interval=300

[interface2]

#Only interfaces whose name starts with Uplink

ifdescription=Uplink.+

#Before the other interfaces

description=<ifdescription>