caviIfType

• 1.3.6.1.4.1.9.9.129.1.1.1.1.7
• Access readwrite
• Type uni(1), nni(2), vnni(3), vuni(4), evuni(5), evnni(6) ?

  uni(1), nni(2), vnni(3), vuni(4), evuni(5), evnni(6)

  This type is not a standard SMI/SNMP base type and is not defined as a documented TEXTUAL-CONVENTION in this MIB.

  It was extracted as raw syntax from the source MIB file and could not be resolved to a known type definition.

• Default uni

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.