ccDetailsRequiredIfIndex
AT-ISDN-MIB ·
.1.3.6.1.4.1.207.8.4.4.4.37.1.1.12
Object
The ifIndex of an ISDN interface on this router which is the required ISDN interface on which to make an outgoing call using this call details entry. The ifIndex, if not 0, must reference the ifEntry which contains information about the entire ISDN interface, at the lowest layer. If a channel is not available on this interface, the call fails. This object is not used on incoming calls. If the value of this object is set to 0, no interface will be required. If the value of this object does not reference the ifEntry for the entire ISDN interface, no interface will be required.
Context
- MIB
- AT-ISDN-MIB
- OID
.1.3.6.1.4.1.207.8.4.4.4.37.1.1.12- Type
- column
- Access
- readwrite
- Status
- current
- Parent
- ccDetailsEntry
Net-SNMP examples
How SNMP and these commands workWalk the column to discover its indexed instances, or supply every index to read one instance.
Walk the column
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'AT-ISDN-MIB' -M '/opt/observium/mibs/allied-old:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'AT-ISDN-MIB::ccDetailsRequiredIfIndex'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'AT-ISDN-MIB' -M '/opt/observium/mibs/allied-old:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'AT-ISDN-MIB::ccDetailsRequiredIfIndex.<ccDetailsIndex>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'AT-ISDN-MIB' -M '/opt/observium/mibs/allied-old:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'AT-ISDN-MIB::ccDetailsRequiredIfIndex'
Syntax
- Source
- IF-MIBInterfaceIndexOrZero
- Base type
Integer32- Display format
d
Type Description
This textual convention is an extension of the InterfaceIndex convention. The latter defines a greater than zero value used to identify an interface or interface sub-layer in the managed system. This extension permits the additional value of zero. the value zero is object-specific and must therefore be defined as part of the description of any object which uses this syntax. Examples of the usage of zero might include situations where interface was unknown, or when none or all interfaces need to be referenced.
Values & Constraints
Type Constraints
range: 0..2147483647