CISCO-VISM-CONN-MIB :: vismFarEndAddressType

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-VISM-CONN-MIBvismFarEndAddressType

vismFarEndAddressType

Module: CISCO-VISM-CONN-MIB

OID (symbolic): CISCO-VISM-CONN-MIB::vismFarEndAddressType

OID (numeric): 1.3.6.1.4.1.351.110.5.5.3.1.1.1.41

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: The address type can be one of five types: NSAP, E164, GWID, notapplicable or unspecified. It determines which object contains the scope for the VCCI, i.e. whether the VCCI needs to be unique relative to NSAP, E164 address or GWID. 'notApplicable (1)' : no valid addresses are required and no validation of VCCI uniqueness for a remote address is performed. 'nsap (2)' : object vismFarEndNSAPAddress contains the address. 'e164 (3)' : object vismFarEndE164Address contains the address. 'gwid (4)' : object vismFarEndGWIDAddress contains the address. 'unspecified (5)' : no valid addresses are required but VCCI needs to be unique.

While this object is writeable, it is recommended not to change the value of this object once it has been created. However, upon modification to any value other than notapplicable, it will be ensured that the resulting combination of VCCI and remote address is unique. Requests that would result in a non-unique combination will be rejected.

If the vismFarEndAddressType is one of 'nsap', 'e164' or 'gwid', the far end address has to be specified.

What is vismFarEndAddressType?

This read-write INTEGER object determines which of five address types (notapplicable, nsap, e164, gwid, unspecified) scopes the VCCI uniqueness requirement for a connection's far end. This setting determines which corresponding address object (E.164, GWID, or NSAP) is actually meaningful and validated for uniqueness for a given connection. An engineer configuring a connection identified by a gateway ID rather than a telephone number would set this object to gwid so the system validates VCCI uniqueness against vismFarEndGWIDAddress rather than an E.164 number.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.351.110.5.5.3.1.1.1.41
snmpwalk -v2c -c public <target> CISCO-VISM-CONN-MIB::vismFarEndAddressType

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.351.110.5.5.3.1.1.1.41.1
snmpget -v2c -c public <target> CISCO-VISM-CONN-MIB::vismFarEndAddressType.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.351.110.5.5.3.1.1.1.41.1 i <value>

Start monitoring Cisco VISM (Voice Interworking Service Module) card, MGX platform (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-VISM-CONN-MIB::vismFarEndAddressType OID value, configure state conditions and alerts, and monitor any Cisco VISM (Voice Interworking Service Module) card, MGX platform (legacy) from a single console.

OID Breakdown

Upper-level ancestors (12 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.351stratacomCISCOWAN-SMI
1.3.6.1.4.1.351.110basisBASIS-MIB
1.3.6.1.4.1.351.110.5basisServicesBASIS-MIB
1.3.6.1.4.1.351.110.5.5voiceBASIS-MIB
1.3.6.1.4.1.351.110.5.5.3vismChanGrpBASIS-MIB
1.3.6.1.4.1.351.110.5.5.3.1vismChanCnfGrpBASIS-MIB
Numeric OIDNameModule
1.3.6.1.4.1.351.110.5.5.3.1.1vismChanCnfGrpTableCISCO-VISM-CONN-MIB
1.3.6.1.4.1.351.110.5.5.3.1.1.1vismChanCnfGrpEntryCISCO-VISM-CONN-MIB
1.3.6.1.4.1.351.110.5.5.3.1.1.1.41vismFarEndAddressTypeCISCO-VISM-CONN-MIB