OID reference
1.3.6.1.4.1.3320.9.63.1.1.1.3
Identification
{1 3 6 1 4 1 3320 9 63 1 1 1 3}
| Value | Name |
|---|---|
| 1 | other |
| 100 | voiceEM |
| 101 | voiceFXO |
| 102 | voiceFXS |
At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.
In BDCOM-IF-MIB, the row index vifIndex is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.3320.9.63.1.1.1.3.<vifIndex>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.3320.9.63.1.1.1.3
Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
Product context
The FS.COM catalogue lists MIB packages containing this definition for these models:
S3400-24T4FP, S3400-24T4SP, S3400-48T4SP, S3400-48T6SP, S5500-48T6SP-R.
A definition in a model's MIB package does not establish that the device implements it or permits access.
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Description 1
Description 2
Parsed from BDCOM-IF-MIB.mib · BDCOM-IF-MIB
Source file: Download S5500-48T6SP-R Switch SNMP MIB Files.rar!NMS-IF-MIB.my · Publisher's file
Related source files and packages:
Source file: Download BDCOM-IF-MIB · Publisher's file
Vendor MIB copy from the Observium Community archive.
Related source files and packages:
Source file: Download NMS-IF-MIB · Publisher's file
Vendor MIB copy from the Observium Community archive.
Source file: Download NMS-IF-MIB · Publisher's file
Vendor MIB copy from the LibreNMS archive.
Related source files and packages:
Source file: Download BDCOM-IF-MIB.mib
Historical records
vifType OBJECT-TYPE
SYNTAX INTEGER {
other(1),
voiceEM(100),
voiceFXO(101),
voiceFXS(102)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The type of Voice interface, distinguished according to
the physical/link protocol(s) immediately `below'
the network layer in the protocol stack."
::= { vifEntry 3 }
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.3320.9.63.1.1.1.1 | vifIndex | 0 | 0 | A unique value for each voice interface. Its value ranges between 1 and the value of vifNumber. The value for each voice interf… |
| 1.3.6.1.4.1.3320.9.63.1.1.1.2 | vifDescr | 0 | 0 | A textual string containing information about the voice interface. This string should include the name of the manufacturer, the … |
| 1.3.6.1.4.1.3320.9.63.1.1.1.4 | vifMtu | 0 | 0 | The size of the largest datagram which can be sent/received on the voice interface, specified in octets. in fact,for voice inter… |
| 1.3.6.1.4.1.3320.9.63.1.1.1.5 | vifSpeed | 0 | 0 | contains a zero value. |
| 1.3.6.1.4.1.3320.9.63.1.1.1.6 | vifPhysAddress | 0 | 0 | contains an octet string of zero length. |
| 1.3.6.1.4.1.3320.9.63.1.1.1.7 | vifAdminStatus | 0 | 0 | The desired administrative status of the Analog Telephony interface port. |
| 1.3.6.1.4.1.3320.9.63.1.1.1.8 | vifOperStatus | 0 | 0 | The current operational state of the interface. The testing(3) state indicates that no operational packets can be passed. |
| 1.3.6.1.4.1.3320.9.63.1.1.1.9 | vifLastChange | 0 | 0 | The value of sysUpTime at the time the interface entered its current operational state. If the current state was entered prior t… |