This object reflects the type of ATM virtual interface that can be
configured within a physical interface. The supported types of virtual
interfaces and their description is shown below:
uni : Only one virtual interface of uni type can be configured within
a physical interface. The ATM cells used in this interface would
use a 8 bit VPI and a 4 bit GFC.
nni : Only one virtual interface of nni type can be configured within
a physical interface.The ATM cells used in this interface would
use a 12 bit VPI.
vnni: Multiple virtual interfaces of vnni type can be configured
within a physical interface. However, all cells sent on this
interface belong to a single VPI (defined by caviVpiNum) and
the cells use a 12 bit VPI.
vuni: Multiple virtual interfaces of vuni type can be configured
within a physical interface. However, all cells sent on this
interface belong to a single VPI (defined by caviVpiNum) and
the cells use a 8 bit VPI and a 4 bit GFC.
evuni: Multiple virtual interfaces of evuni type can be configured
within a physical interface. However, all cells sent on this
interface belong to a range of VPI (defined by caviMinVpiNum
& caviMaxVpiNum) and the cells use a 8 bit VPI and a 4 bit GFC.
evnni: Multiple virtual interfaces of evuni type can be configured
within a physical interface. However, all cells sent on this
interface belong to a range of VPI (defined by caviMinVpiNum
& caviMaxVpiNum) and the cells use a 12 bit VPI.
Parsed from file CISCO-ATM-VIRTUAL-IF-MIB.mib
Module: CISCO-ATM-VIRTUAL-IF-MIB
This object reflects the type of ATM virtual interface that can be
configured within a physical interface. The supported types of virtual
interfaces and their description is shown below:
uni : Only one virtual interface of uni type can be configured within
a physical interface. The ATM cells used in this interface would
use a 8 bit VPI and a 4 bit GFC.
nni : Only one virtual interface of nni type can be configured within
a physical interface.The ATM cells used in this interface would
use a 12 bit VPI.
vnni: Multiple virtual interfaces of vnni type can be configured
within a physical interface. However, all cells sent on this
interface belong to a single VPI (defined by caviVpiNum) and
the cells use a 12 bit VPI.
vuni: Multiple virtual interfaces of vuni type can be configured
within a physical interface. However, all cells sent on this
interface belong to a single VPI (defined by caviVpiNum) and
the cells use a 8 bit VPI and a 4 bit GFC.
evuni: Multiple virtual interfaces of evuni type can be configured
within a physical interface. However, all cells sent on this
interface belong to a range of VPI (defined by caviMinVpiNum
& caviMaxVpiNum) and the cells use a 8 bit VPI and a 4 bit GFC.
evnni: Multiple virtual interfaces of evuni type can be configured
within a physical interface. However, all cells sent on this
interface belong to a range of VPI (defined by caviMinVpiNum
& caviMaxVpiNum) and the cells use a 12 bit VPI.
caviIftype
View at oid-info.com
This object reflects the type of ATM virtual interface that can be
configured within a physical interface. The supported types of virtual
interfaces and their description is shown below:
uni : Only one virtual interface of uni type can be configured within
a physical interface. The ATM cells used in this interface would
use a 8 bit VPI and a 4 bit GFC.
nni : Only one virtual interface of nni type can be configured within
a physical interface.The ATM cells used in this interface would
use a 12 bit VPI.
vnni: Multiple virtual interfaces of vnni type can be configured
within a physical interface. However, all cells sent on this
interface belong to a single VPI (defined by caviVpiNum) and
the cells use a 12 bit VPI.
vuni: Multiple virtual interfaces of vuni type can be configured
within a physical interface. However, all cells sent on this
interface belong to a single VPI (defined by caviVpiNum) and
the cells use a 8 bit VPI and a 4 bit GFC.
evuni: Multiple virtual interfaces of evuni type can be configured
within a physical interface. However, all cells sent on this
interface belong to a range of VPI (defined by caviMinVpiNum
& caviMaxVpiNum) and the cells use a 8 bit VPI and a 4 bit GFC.
evnni: Multiple virtual interfaces of evuni type can be configured
within a physical interface. However, all cells sent on this
interface belong to a range of VPI (defined by caviMinVpiNum
& caviMaxVpiNum) and the cells use a 12 bit VPI.
Parsed from file CISCO-ATM-VIRTUAL-IF-MIB.my.txt
Company: None
Module: CISCO-ATM-VIRTUAL-IF-MIB
This object reflects the type of ATM virtual interface that can be
configured within a physical interface. The supported types of virtual
interfaces and their description is shown below:
uni : Only one virtual interface of uni type can be configured within
a physical interface. The ATM cells used in this interface would
use a 8 bit VPI and a 4 bit GFC.
nni : Only one virtual interface of nni type can be configured within
a physical interface.The ATM cells used in this interface would
use a 12 bit VPI.
vnni: Multiple virtual interfaces of vnni type can be configured
within a physical interface. However, all cells sent on this
interface belong to a single VPI (defined by caviVpiNum) and
the cells use a 12 bit VPI.
vuni: Multiple virtual interfaces of vuni type can be configured
within a physical interface. However, all cells sent on this
interface belong to a single VPI (defined by caviVpiNum) and
the cells use a 8 bit VPI and a 4 bit GFC.
evuni: Multiple virtual interfaces of evuni type can be configured
within a physical interface. However, all cells sent on this
interface belong to a range of VPI (defined by caviMinVpiNum
& caviMaxVpiNum) and the cells use a 8 bit VPI and a 4 bit GFC.
evnni: Multiple virtual interfaces of evuni type can be configured
within a physical interface. However, all cells sent on this
interface belong to a range of VPI (defined by caviMinVpiNum
& caviMaxVpiNum) and the cells use a 12 bit VPI.
caviIfType OBJECT-TYPE SYNTAX INTEGER { uni(1), nni(2), vnni(3), vuni(4), evuni(5), evnni(6) } MAX-ACCESS read-create STATUS current DESCRIPTION "This object reflects the type of ATM virtual interface that can be configured within a physical interface. The supported types of virtual interfaces and their description is shown below: uni : Only one virtual interface of uni type can be configured within a physical interface. The ATM cells used in this interface would use a 8 bit VPI and a 4 bit GFC. nni : Only one virtual interface of nni type can be configured within a physical interface.The ATM cells used in this interface would use a 12 bit VPI. vnni: Multiple virtual interfaces of vnni type can be configured within a physical interface. However, all cells sent on this interface belong to a single VPI (defined by caviVpiNum) and the cells use a 12 bit VPI. vuni: Multiple virtual interfaces of vuni type can be configured within a physical interface. However, all cells sent on this interface belong to a single VPI (defined by caviVpiNum) and the cells use a 8 bit VPI and a 4 bit GFC. evuni: Multiple virtual interfaces of evuni type can be configured within a physical interface. However, all cells sent on this interface belong to a range of VPI (defined by caviMinVpiNum & caviMaxVpiNum) and the cells use a 8 bit VPI and a 4 bit GFC. evnni: Multiple virtual interfaces of evuni type can be configured within a physical interface. However, all cells sent on this interface belong to a range of VPI (defined by caviMinVpiNum & caviMaxVpiNum) and the cells use a 12 bit VPI." DEFVAL { uni } ::= { caviEntry 7 }
caviIfType OBJECT-TYPE SYNTAX INTEGER { uni(1), nni(2), vnni(3), vuni(4), evuni(5), evnni(6) } ACCESS read-write STATUS mandatory DESCRIPTION "This object reflects the type of ATM virtual interface that can be configured within a physical interface. The supported types of virtual interfaces and their description is shown below: uni : Only one virtual interface of uni type can be configured within a physical interface. The ATM cells used in this interface would use a 8 bit VPI and a 4 bit GFC. nni : Only one virtual interface of nni type can be configured within a physical interface.The ATM cells used in this interface would use a 12 bit VPI. vnni: Multiple virtual interfaces of vnni type can be configured within a physical interface. However, all cells sent on this interface belong to a single VPI (defined by caviVpiNum) and the cells use a 12 bit VPI. vuni: Multiple virtual interfaces of vuni type can be configured within a physical interface. However, all cells sent on this interface belong to a single VPI (defined by caviVpiNum) and the cells use a 8 bit VPI and a 4 bit GFC. evuni: Multiple virtual interfaces of evuni type can be configured within a physical interface. However, all cells sent on this interface belong to a range of VPI (defined by caviMinVpiNum & caviMaxVpiNum) and the cells use a 8 bit VPI and a 4 bit GFC. evnni: Multiple virtual interfaces of evuni type can be configured within a physical interface. However, all cells sent on this interface belong to a range of VPI (defined by caviMinVpiNum & caviMaxVpiNum) and the cells use a 12 bit VPI." DEFVAL { uni } ::= { caviEntry 7 }
Vendor: Cisco
Module: CISCO-ATM-VIRTUAL-IF-MIB
[Automatically extracted from oidview.com]
caviIfType OBJECT-TYPE SYNTAX INTEGER { uni(1), nni(2), vnni(3), vuni(4), evuni(5), evnni(6) } MAX-ACCESS read-create STATUS current DESCRIPTION "This object reflects the type of ATM virtual interface that can be configured within a physical interface. The supported types of virtual interfaces and their description is shown below: uni : Only one virtual interface of uni type can be configured within a physical interface. The ATM cells used in this interface would use a 8 bit VPI and a 4 bit GFC. nni : Only one virtual interface of nni type can be configured within a physical interface.The ATM cells used in this interface would use a 12 bit VPI. vnni: Multiple virtual interfaces of vnni type can be configured within a physical interface. However, all cells sent on this interface belong to a single VPI (defined by caviVpiNum) and the cells use a 12 bit VPI. vuni: Multiple virtual interfaces of vuni type can be configured within a physical interface. However, all cells sent on this interface belong to a single VPI (defined by caviVpiNum) and the cells use a 8 bit VPI and a 4 bit GFC. evuni: Multiple virtual interfaces of evuni type can be configured within a physical interface. However, all cells sent on this interface belong to a range of VPI (defined by caviMinVpiNum & caviMaxVpiNum) and the cells use a 8 bit VPI and a 4 bit GFC. evnni: Multiple virtual interfaces of evuni type can be configured within a physical interface. However, all cells sent on this interface belong to a range of VPI (defined by caviMinVpiNum & caviMaxVpiNum) and the cells use a 12 bit VPI." DEFVAL { uni } ::= { caviEntry 7 }
caviIfType OBJECT-TYPE SYNTAX INTEGER { uni(1), nni(2), vnni(3), vuni(4), evuni(5), evnni(6) } MAX-ACCESS read-create STATUS current DESCRIPTION "This object reflects the type of ATM virtual interface that can be configured within a physical interface. The supported types of virtual interfaces and their description is shown below: uni : Only one virtual interface of uni type can be configured within a physical interface. The ATM cells used in this interface would use a 8 bit VPI and a 4 bit GFC. nni : Only one virtual interface of nni type can be configured within a physical interface.The ATM cells used in this interface would use a 12 bit VPI. vnni: Multiple virtual interfaces of vnni type can be configured within a physical interface. However, all cells sent on this interface belong to a single VPI (defined by caviVpiNum) and the cells use a 12 bit VPI. vuni: Multiple virtual interfaces of vuni type can be configured within a physical interface. However, all cells sent on this interface belong to a single VPI (defined by caviVpiNum) and the cells use a 8 bit VPI and a 4 bit GFC. evuni: Multiple virtual interfaces of evuni type can be configured within a physical interface. However, all cells sent on this interface belong to a range of VPI (defined by caviMinVpiNum & caviMaxVpiNum) and the cells use a 8 bit VPI and a 4 bit GFC. evnni: Multiple virtual interfaces of evuni type can be configured within a physical interface. However, all cells sent on this interface belong to a range of VPI (defined by caviMinVpiNum & caviMaxVpiNum) and the cells use a 12 bit VPI." DEFVAL { uni } ::= { caviEntry 7 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.129.1.1.1.1.1 | caviIndex | 0 | 0 | A unique value for the ATM virtual interface. |
| 1.3.6.1.4.1.9.9.129.1.1.1.1.2 | caviPhyIfIndex | 0 | 0 | This object identifies the interface number ( 'ifIndex' ) assigned to sonet(39),ds3(30),ds1(18),atmIma(107). |
| 1.3.6.1.4.1.9.9.129.1.1.1.1.3 | caviViIfIndex | 0 | 0 | This object identifies the ATM virtual interface number ('ifIndex') assigned to this entry, and is used to identify corresponding… |
| 1.3.6.1.4.1.9.9.129.1.1.1.1.4 | caviMinRate | 0 | 0 | ATM virtual interface's guaranteed cell rate. This is the guaranteed bandwidth allocated for the interface. The sum of caviMinRat… |
| 1.3.6.1.4.1.9.9.129.1.1.1.1.5 | caviMaxRate | 0 | 0 | ATM virtual interface's maximum cell rate. If bandwidth is available, the interface will be allocated bandwidth upto this value. T… |
| 1.3.6.1.4.1.9.9.129.1.1.1.1.6 | caviFileId | 0 | 0 | The ID of the file that holds module specific configuration parameters for this ATM virtual interface. |
| 1.3.6.1.4.1.9.9.129.1.1.1.1.8 | caviVpiNum | 0 | 0 | This object is used when configuring ATM virtual interfaces of caviIftype vuni(4) or vnni (3). A non-zero value is required for v… |
| 1.3.6.1.4.1.9.9.129.1.1.1.1.9 | caviRowStatus | 0 | 0 | This object allows create and delete operations on caviTable entries. An entry is created in the table by setting this object to c… |
| 1.3.6.1.4.1.9.9.129.1.1.1.1.10 | caviMinVpiNum | 0 | 0 | This object is mandatory while configuring this ATM virtual interface as caviIfType evuni(5) or evnni(6). The range of VPI accept… |
| 1.3.6.1.4.1.9.9.129.1.1.1.1.11 | caviMaxVpiNum | 0 | 0 | This object is mandatory while configuring this ATM virtual interface as caviIfType evuni(5) or evnni(6). The range of VPI accept… |