This setting configures the unit for VNIP topology support on
a per-interface basis. Establishing a VNIP topology is a
fundamental prerequisite to applying the VNIP feature set which
includes PVC-based delay measurement, diagnostics, and congestion
monitoring. With VNIP enabled on an interface the unit
will attempt to locate VNIP peers out that port. As peers are
discovered and logged the unit will report the topology it has
learned on its opposite interface. If VNIP is inactive on one
interface it will not engage in any VNIP dialog; however it will
continue to listen for topology messages on the inactive interface
and will reflect these messages out the opposite interface if VNIP
is enabled. With VNIP inactive on both interfaces the unit will
transparently pass all VNIP messages. The topology database includes
ip addresses, DLCI values, and the number of VNIP hops in between.
(1) Topology Inactive: VNIP messages pass through unit
(2) Topology Enabled on DTE only: unit logs VNIP peers seen
out the DTE interface. Unit listens for topology reports
from the WAN but doesn't generate any towards the WAN. Will
report learned WAN topology towards the DTE.
(3) Topology Enabled on WAN only: unit logs VNIP peers seen
out the WAN interface. Unit listens for topology reports
from the DTE but doesn't generate any towards the DTE. Will
report learned DTE topology towards the WAN.
(4) Topolgy Enabled on Both DTE and WAN: Unit logs VNIP peers
seen out both interfaces and generates DTE topolgy reports
towards the WAN and vice versa.
Parsed from file TFRAP.MIB.txt
Company: None
Module: TFRAP-MIB
This setting configures the unit for VNIP topology support on
a per-interface basis. Establishing a VNIP topology is a
fundamental prerequisite to applying the VNIP feature set which
includes PVC-based delay measurement, diagnostics, and congestion
monitoring. With VNIP enabled on an interface the unit
will attempt to locate VNIP peers out that port. As peers are
discovered and logged the unit will report the topology it has
learned on its opposite interface. If VNIP is inactive on one
interface it will not engage in any VNIP dialog; however it will
continue to listen for topology messages on the inactive interface
and will reflect these messages out the opposite interface if VNIP
is enabled. With VNIP inactive on both interfaces the unit will
transparently pass all VNIP messages. The topology database includes
ip addresses, DLCI values, and the number of VNIP hops in between.
(1) Topology Inactive: VNIP messages pass through unit
(2) Topology Enabled on DTE only: unit logs VNIP peers seen
out the DTE interface. Unit listens for topology reports
from the WAN but doesn't generate any towards the WAN. Will
report learned WAN topology towards the DTE.
(3) Topology Enabled on WAN only: unit logs VNIP peers seen
out the WAN interface. Unit listens for topology reports
from the DTE but doesn't generate any towards the DTE. Will
report learned DTE topology towards the WAN.
(4) Topolgy Enabled on Both DTE and WAN: Unit logs VNIP peers
seen out both interfaces and generates DTE topolgy reports
towards the WAN and vice versa.
Parsed from file TFRAP-MIB.mib
Module: TFRAP-MIB
Vendor: Sync Research, Inc.
Module: TFRAP-MIB
[Automatically extracted from oidview.com]
tfrapCfgVnipMode OBJECT-TYPE SYNTAX INTEGER { inactive (1), dte (2), t1 (3), both (4) } ACCESS read-write STATUS mandatory DESCRIPTION "This setting configures the unit for VNIP topology support on a per-interface basis. Establishing a VNIP topology is a fundamental prerequisite to applying the VNIP feature set which includes PVC-based delay measurement, diagnostics, and congestion monitoring. With VNIP enabled on an interface the unit will attempt to locate VNIP peers out that port. As peers are discovered and logged the unit will report the topology it has learned on its opposite interface. If VNIP is inactive on one interface it will not engage in any VNIP dialog; however it will continue to listen for topology messages on the inactive interface and will reflect these messages out the opposite interface if VNIP is enabled. With VNIP inactive on both interfaces the unit will transparently pass all VNIP messages. The topology database includes ip addresses, DLCI values, and the number of VNIP hops in between. (1) Topology Inactive: VNIP messages pass through unit (2) Topology Enabled on DTE only: unit logs VNIP peers seen out the DTE interface. Unit listens for topology reports from the WAN but doesn't generate any towards the WAN. Will report learned WAN topology towards the DTE. (3) Topology Enabled on WAN only: unit logs VNIP peers seen out the WAN interface. Unit listens for topology reports from the DTE but doesn't generate any towards the DTE. Will report learned DTE topology towards the WAN. (4) Topolgy Enabled on Both DTE and WAN: Unit logs VNIP peers seen out both interfaces and generates DTE topolgy reports towards the WAN and vice versa." ::= { tfrapCfgVnipTable 1 }
tfrapCfgVnipMode OBJECT-TYPE SYNTAX INTEGER { inactive (1), dte (2), t1 (3), both (4) } ACCESS read-write STATUS mandatory DESCRIPTION "This setting configures the unit for VNIP topology support on a per-interface basis. Establishing a VNIP topology is a fundamental prerequisite to applying the VNIP feature set which includes PVC-based delay measurement, diagnostics, and congestion monitoring. With VNIP enabled on an interface the unit will attempt to locate VNIP peers out that port. As peers are discovered and logged the unit will report the topology it has learned on its opposite interface. If VNIP is inactive on one interface it will not engage in any VNIP dialog; however it will continue to listen for topology messages on the inactive interface and will reflect these messages out the opposite interface if VNIP is enabled. With VNIP inactive on both interfaces the unit will transparently pass all VNIP messages. The topology database includes ip addresses, DLCI values, and the number of VNIP hops in between. (1) Topology Inactive: VNIP messages pass through unit (2) Topology Enabled on DTE only: unit logs VNIP peers seen out the DTE interface. Unit listens for topology reports from the WAN but doesn't generate any towards the WAN. Will report learned WAN topology towards the DTE. (3) Topology Enabled on WAN only: unit logs VNIP peers seen out the WAN interface. Unit listens for topology reports from the DTE but doesn't generate any towards the DTE. Will report learned DTE topology towards the WAN. (4) Topolgy Enabled on Both DTE and WAN: Unit logs VNIP peers seen out both interfaces and generates DTE topolgy reports towards the WAN and vice versa." ::= { tfrapCfgVnipTable 1 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.485.5.2.6.1.0 | tfrapCfgVnipMode | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.485.5.2.6.2 | tfrapCfgVnipInitTimer | 1 | 1 | VNIP peer to peer communications are initiated following the detection of a VNIP Hello message. The unit will periodically issue … |
| 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 |