CROUTE-MIB :: relayVlRelayAddr

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCROUTE-MIBrelayVlRelayAddr

relayVlRelayAddr

Module: CROUTE-MIB

OID (symbolic): CROUTE-MIB::relayVlRelayAddr

OID (numeric): 1.3.6.1.4.1.81.31.1.6.1.5

Node type: OBJECT-TYPE

Type: IpAddress

Access: read-write

Description: The IP address of the Relay, i.e. the router's IP address to write in the relayed request (giaddr field in the Bootp packet). When there are multiple IP interfaces on the same VLAN such that the router has multiple IP addresses on the VLAN, the user can configure which of these addresses to use when relaying requests arriving on this VLAN. This relay address is used by the server to determines the subnet from which the address shall be allocated. The special value 255.255.255.255 means DUPLICATE. In this case the Relay will duplicate each request arriving on this VLAN and send to the server multiple copies of the request, a copy for each of the router's IP addresses on that VLAN. The relay address in each copy of the request shall be the router's IP address (NOT 255.255.255.255). The special value 0.0.0.0 means that the router shall use the Default value (lowest IP address on the VLAN) for the relay address

What is relayVlRelayAddr?

This read-write IpAddress object sets the router's own IP address written into the giaddr field of relayed BOOTP requests for this VLAN, letting the admin choose which of the router's multiple IP addresses on that VLAN to present to the server. An admin configures this when a VLAN has multiple IP interfaces so the DHCP server allocates addresses from the correct subnet based on which relay address is presented. For example, on a VLAN with two IP subnets, setting relayVlRelayAddr to the address of the subnet clients should draw from ensures the DHCP server assigns leases from the right pool.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.81.31.1.6.1.5
snmpwalk -v2c -c public <target> CROUTE-MIB::relayVlRelayAddr

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.81.31.1.6.1.5.1
snmpget -v2c -c public <target> CROUTE-MIB::relayVlRelayAddr.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.81.31.1.6.1.5.1 a <value>

SNMPv3 example:

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

Start monitoring Layer 3 switch platform (vendor unclear, BOOTP/RIP) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CROUTE-MIB::relayVlRelayAddr OID value, configure state conditions and alerts, and monitor any Layer 3 switch platform (vendor unclear, BOOTP/RIP) from a single console.

OID Breakdown

Upper-level ancestors (7 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.81lannetGEN-MIB
Numeric OIDNameModule
1.3.6.1.4.1.81.31crouteCROUTE-MIB
1.3.6.1.4.1.81.31.1ipRouteCROUTE-MIB
1.3.6.1.4.1.81.31.1.6relayTableCROUTE-MIB
1.3.6.1.4.1.81.31.1.6.1relayEntryCROUTE-MIB
1.3.6.1.4.1.81.31.1.6.1.5relayVlRelayAddrCROUTE-MIB