VNIP peer to peer communications are initiated following
the detection of a VNIP Hello message. The unit will
periodically issue this message out interfaces that have
VNIP enabled until a Hello response is received. Following
the reception of the Hello response, the unit will stop
issuing Hello messahges on that DLCI/interface and generate
periodic topology reports at the VNIP Keep Alive frequency.
The unit will generate periodic Hello messages, at the
InitTimer frequency if no Hello responses are ever detected
or a topology message not been detected within the time period
defined by the VNIP Inactivity timer.
(5-86400) VNIP Hello frequency (in seconds)
Parsed from file TFRAP.MIB.txt
Company: None
Module: TFRAP-MIB
VNIP peer to peer communications are initiated following
the detection of a VNIP Hello message. The unit will
periodically issue this message out interfaces that have
VNIP enabled until a Hello response is received. Following
the reception of the Hello response, the unit will stop
issuing Hello messahges on that DLCI/interface and generate
periodic topology reports at the VNIP Keep Alive frequency.
The unit will generate periodic Hello messages, at the
InitTimer frequency if no Hello responses are ever detected
or a topology message not been detected within the time period
defined by the VNIP Inactivity timer.
(5-86400) VNIP Hello frequency (in seconds)
Parsed from file TFRAP-MIB.mib
Module: TFRAP-MIB
Vendor: Sync Research, Inc.
Module: TFRAP-MIB
[Automatically extracted from oidview.com]
tfrapCfgVnipInitTimer OBJECT-TYPE SYNTAX INTEGER (5..86400) ACCESS read-write STATUS mandatory DESCRIPTION "VNIP peer to peer communications are initiated following the detection of a VNIP Hello message. The unit will periodically issue this message out interfaces that have VNIP enabled until a Hello response is received. Following the reception of the Hello response, the unit will stop issuing Hello messahges on that DLCI/interface and generate periodic topology reports at the VNIP Keep Alive frequency. The unit will generate periodic Hello messages, at the InitTimer frequency if no Hello responses are ever detected or a topology message not been detected within the time period defined by the VNIP Inactivity timer. (5-86400) VNIP Hello frequency (in seconds)" ::= { tfrapCfgVnipTable 2 }
tfrapCfgVnipInitTimer OBJECT-TYPE SYNTAX INTEGER (5..86400) ACCESS read-write STATUS mandatory DESCRIPTION "VNIP peer to peer communications are initiated following the detection of a VNIP Hello message. The unit will periodically issue this message out interfaces that have VNIP enabled until a Hello response is received. Following the reception of the Hello response, the unit will stop issuing Hello messahges on that DLCI/interface and generate periodic topology reports at the VNIP Keep Alive frequency. The unit will generate periodic Hello messages, at the InitTimer frequency if no Hello responses are ever detected or a topology message not been detected within the time period defined by the VNIP Inactivity timer. (5-86400) VNIP Hello frequency (in seconds)" ::= { tfrapCfgVnipTable 2 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.485.5.2.6.2.0 | tfrapCfgVnipInitTimer | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.485.5.2.6.1 | tfrapCfgVnipMode | 1 | 1 | This setting configures the unit for VNIP topology support on a per-interface basis. Establishing a VNIP topology is a fundamenta… |
| 1.3.6.1.4.1.485.5.2.6.3 | tfrapCfgVnipKeepAliveTimer | 1 | 1 | This is the frequency that topology reports are issued out any interface that has VNIP enabled. Once a Hello exchange occurs, the… |
| 1.3.6.1.4.1.485.5.2.6.4 | tfrapCfgVnipInactivityTimer | 1 | 1 | The length of time to wait before dropping a VNIP peer from the database and attempting tp reestablish communications by issuing … |
| 1.3.6.1.4.1.485.5.2.6.5 | tfrapCfgVnipTransitDelayFrequency | 1 | 1 | Transit Delay measurements may be enabled between any DLCI peers that have been logged through the topology protocol. Delay messa… |
| 1.3.6.1.4.1.485.5.2.6.20 | tfrapCfgTransitDelayTable | 1 | 6 | The table defining the transit delay measurement profile for each of the learned VNIP peers. As peers are located and logged into… |
| 1.3.6.1.4.1.485.5.2.6.21 | tfrapCfgTDDeleteTable | 1 | 3 | The table allows the user to disable transit delay measurements for a specific DLCI on a particular interface. |
| 1.3.6.1.4.1.485.5.2.6.22 | tfrapCfgTransitDelayTableClear | 1 | 1 | The tfrapCfgTransitDelayTable is cleared. (1) clear the table |