AVAYA-LOAD-MIB :: avGenOpServerInetAddress

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsAVAYA-LOAD-MIBavGenOpServerInetAddress

avGenOpServerInetAddress

Module: AVAYA-LOAD-MIB

OID (symbolic): AVAYA-LOAD-MIB::avGenOpServerInetAddress

OID (numeric): 1.3.6.1.4.1.6889.2.6.5.1.2.1.25

Node type: OBJECT-TYPE

Type: InetAddress

Access: read-write

Description: The Inet Address of the remote file server. 1. The address type of this object is specified in avGenOpServerInetAddress. 2. Management applications can use avGenOpServerIP or avGenOpServerInetAddressType/avGenOpServerInetAddress to set IPv4 server address and only avGenOpServerInetAddressType/avGenOpServerInetAddress to set IPv6 server address. 3. The avGenOpServerInetAddressType must always been set before the avGenOpServerInetAddress is set (the avGenOpServerInetAddress must conform to the avGenOpServerInetAddressType). 4. Setting avGenOpServerIP address mib item will change avGenOpServerInetAddressType to IPv4(1) and avGenOpServerInetAddress to IPv4 address configured. 5. Setting avGenOpServerInetAddress as IPv4 address will also set avGenOpServerIP. 6. Setting avGenOpServerInetAddress as IPv6 address will also set avGenOpServerIP to 0.0.0.0. 7. Default of avGenOpServerInetAddressType is unknown(0) and avGenOpServerInetAddress is zero length. 8. Setting avGenOpServerInetAddressType to IPv4 will return avGenOpServerIP and avGenOpServerInetAddress to default value of 0.0.0.0. Setting avGenOpServerInetAddressType to value other than IPv4 return avGenOpServerIP to default value of 0.0.0.0 and avGenOpServerInetAddress to default value of null string.

What is avGenOpServerInetAddress?

Holds the address of the remote file-transfer server in whichever family avGenOpServerInetAddressType declares, letting this table support IPv6 servers in addition to the IPv4-only avGenOpServerIP. Setting this field to an IPv4 address also updates avGenOpServerIP, but setting it to an IPv6 address resets avGenOpServerIP to 0.0.0.0, since that legacy field cannot represent IPv6.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6889.2.6.5.1.2.1.25
snmpwalk -v2c -c public <target> AVAYA-LOAD-MIB::avGenOpServerInetAddress

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.6889.2.6.5.1.2.1.25.1
snmpget -v2c -c public <target> AVAYA-LOAD-MIB::avGenOpServerInetAddress.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.6889.2.6.5.1.2.1.25.1 s <value>

SNMPv3 example:

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

Start monitoring Avaya communication servers and network equipment with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the AVAYA-LOAD-MIB::avGenOpServerInetAddress OID value, configure state conditions and alerts, and monitor any Avaya communication servers and network equipment from a single console.

OID Breakdown

Upper-level ancestors (9 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.6889avayaAV-APPLICATION-ENABLEMENT-SERVICES-MIB
1.3.6.1.4.1.6889.2mibsAV-APPLICATION-ENABLEMENT-SERVICES-MIB
1.3.6.1.4.1.6889.2.6avGatewayMibsAVAYAGEN-MIB
Numeric OIDNameModule
1.3.6.1.4.1.6889.2.6.5avLoadAVAYA-LOAD-MIB
1.3.6.1.4.1.6889.2.6.5.1avGenOperationsAVAYA-LOAD-MIB
1.3.6.1.4.1.6889.2.6.5.1.2avGenOpTableAVAYA-LOAD-MIB
1.3.6.1.4.1.6889.2.6.5.1.2.1avGenOpEntryAVAYA-LOAD-MIB
1.3.6.1.4.1.6889.2.6.5.1.2.1.25avGenOpServerInetAddressAVAYA-LOAD-MIB