VNIP topology is a feature that, for each interface, maps all
compatible VNIP peers, their DLCI value, ip address and relative
location. The 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 the interface, local DLCI value, remote peer DLCI value,
remote peer ip address, and the number of VNIP hops in between.
This table also reports the status of other VNIP features as well.
Parsed from file TFRAP.MIB.txt
Company: None
Module: TFRAP-MIB
VNIP topology is a feature that, for each interface, maps all
compatible VNIP peers, their DLCI value, ip address and relative
location. The 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 the interface, local DLCI value, remote peer DLCI value,
remote peer ip address, and the number of VNIP hops in between.
This table also reports the status of other VNIP features as well.
Parsed from file TFRAP-MIB.mib
Module: TFRAP-MIB
Vendor: Sync Research, Inc.
Module: TFRAP-MIB
[Automatically extracted from oidview.com]
tfrapVnipTopologyTable OBJECT-TYPE SYNTAX SEQUENCE OF TFRAPVnipTopologyEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "VNIP topology is a feature that, for each interface, maps all compatible VNIP peers, their DLCI value, ip address and relative location. The 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 the interface, local DLCI value, remote peer DLCI value, remote peer ip address, and the number of VNIP hops in between. This table also reports the status of other VNIP features as well." ::= { tfrapStatus 2 }
tfrapVnipTopologyTable OBJECT-TYPE SYNTAX SEQUENCE OF TFRAPVnipTopologyEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "VNIP topology is a feature that, for each interface, maps all compatible VNIP peers, their DLCI value, ip address and relative location. The 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 the interface, local DLCI value, remote peer DLCI value, remote peer ip address, and the number of VNIP hops in between. This table also reports the status of other VNIP features as well." ::= { tfrapStatus 2 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.485.5.4.2.1 | tfrapVnipTopologyEntry | 22 | 22 | The DLCI, IP address, and number of hops for a particular node, discovered via VNIP off of an interface. The entry may also have… |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.485.5.4.1 | tfrapStatusIntfTable | 9 | 18 | tfrapStatusIntftable |
| 1.3.6.1.4.1.485.5.4.3 | tfrapStatusMgmtTable | 5 | 10 | None |
| 1.3.6.1.4.1.485.5.4.4 | tfrapStatusLedTable | 7 | 14 | None |
| 1.3.6.1.4.1.485.5.4.5 | tfrapVnipTransitDelayClear | 1 | 1 | Allows the user to clear all the VNIP Transit Delay data collected in the VNIP topology database. (1) Clear entire Transit Delay … |
| 1.3.6.1.4.1.485.5.4.6 | tfrapLmiSourcing | 1 | 1 | If configured for Frame Relay with a non-zero LMI inactivity timer the unit will monitor the status of LMI and, if proper messag… |
| 1.3.6.1.4.1.485.5.4.11 | tfrapVBertClear | 1 | 1 | Allows the user to clear all the VBERT data collected in the VNIP topology database as long as the entry is not in a test status.… |
| 1.3.6.1.4.1.485.5.4.12 | tfrapStatusLmiAutosense | 1 | 1 | This indicates the current status of LMI Auto Sensing if it's enabled. (1) Disabled: LMI is configured as Type 1, Annex-D, or Ann… |