CISCO-UNIFIED-COMPUTING-VNIC-MIB :: cucsVnicSanConnTemplRedundancyPairType

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-UNIFIED-COMPUTING-VNIC-MIBcucsVnicSanConnTemplRedundancyPairType

cucsVnicSanConnTemplRedundancyPairType

Module: CISCO-UNIFIED-COMPUTING-VNIC-MIB

OID (symbolic): CISCO-UNIFIED-COMPUTING-VNIC-MIB::cucsVnicSanConnTemplRedundancyPairType

OID (numeric): 1.3.6.1.4.1.9.9.719.1.53.32.1.23

Node type: OBJECT-TYPE

Type: CucsVnicRedundancyPairType

Access: read-only

Description: Cisco UCS vnic:SanConnTempl:redundancyPairType managed object property

What is cucsVnicSanConnTemplRedundancyPairType?

This indicates the role this SAN connectivity template plays in a redundant vHBA pair, for example primary or secondary. An admin uses this to understand which of the two paired templates is the primary member, useful for troubleshooting failover behavior between the fabric-A and fabric-B vHBAs. For example, one template in the pair reports as primary and its partner as secondary, telling the admin which side normally carries traffic first.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.53.32.1.23
snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-VNIC-MIB::cucsVnicSanConnTemplRedundancyPairType

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.53.32.1.23.1
snmpget -v2c -c public <target> CISCO-UNIFIED-COMPUTING-VNIC-MIB::cucsVnicSanConnTemplRedundancyPairType.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> cucsVnicSanConnTemplRedundancyPairType.1

Start monitoring Cisco UCS blade/rack servers and fabric interconnects (vNIC/vHBA) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-UNIFIED-COMPUTING-VNIC-MIB::cucsVnicSanConnTemplRedundancyPairType OID value, configure state conditions and alerts, and monitor any Cisco UCS blade/rack servers and fabric interconnects (vNIC/vHBA) from a single console.

OID Breakdown

Upper-level ancestors (10 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.9ciscoMgmtCISCO-SMI
1.3.6.1.4.1.9.9.719ciscoUnifiedComputingMIBCISCO-UNIFIED-COMPUTING-MIB
1.3.6.1.4.1.9.9.719.1ciscoUnifiedComputingMIBObjectsCISCO-UNIFIED-COMPUTING-MIB
Numeric OIDNameModule
1.3.6.1.4.1.9.9.719.1.53cucsVnicObjectsCISCO-UNIFIED-COMPUTING-VNIC-MIB
1.3.6.1.4.1.9.9.719.1.53.32cucsVnicSanConnTemplTableCISCO-UNIFIED-COMPUTING-VNIC-MIB
1.3.6.1.4.1.9.9.719.1.53.32.1cucsVnicSanConnTemplEntryCISCO-UNIFIED-COMPUTING-VNIC-MIB
1.3.6.1.4.1.9.9.719.1.53.32.1.23cucsVnicSanConnTemplRedundancyPairTypeCISCO-UNIFIED-COMPUTING-VNIC-MIB