ciscoAtmVclCrossIfIndex
CISCO-ATM-CONN-MIB ·
.1.3.6.1.4.1.9.10.13.1.2.1.1.15
Object
For point to point, this is the cross-connected VCL's ifIndex of this VCL. For point to multi-point connection, this will be the root VCL's ifIndex for a leaf VCL entry in the multicast chain, or it's the 1st leaf VCL for a root VCL entry. If it's zero, it means it's not cross-connected yet. Atomically set ciscoAtmVclConnState, ciscoAtmVclCrossIfindex, ciscoAtmVclCrossVpi and ciscoAtmVclCrossVci will create or delete a cross connection to crossed half leg of this ciscoAtmVclCrossIfindex, ciscoAtmVclCrossVpi and ciscoAtmVclCrossVci for p2p PVC, or add or drop a multicast connection to/from the root of this ciscoAtmVclCrossIfindex, ciscoAtmVclCrossVpi and ciscoAtmVclCrossVci on the multicast chain for p2mp PVC.
Context
- MIB
- CISCO-ATM-CONN-MIB
- OID
.1.3.6.1.4.1.9.10.13.1.2.1.1.15- Type
- column
- Access
- readwrite
- Status
- current
- Parent
- ciscoAtmVclEntry
- Groups
- 3
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 'CISCO-ATM-CONN-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-ATM-CONN-MIB::ciscoAtmVclCrossIfIndex'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'CISCO-ATM-CONN-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-ATM-CONN-MIB::ciscoAtmVclCrossIfIndex.<ifIndex>.<atmVclVpi>.<atmVclVci>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-ATM-CONN-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-ATM-CONN-MIB::ciscoAtmVclCrossIfIndex'
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