All MIBs › DIAMETER-BASE-PROTOCOL-MIB › dbpRealmMessageRouteAction
dbpRealmMessageRouteAction
Module: DIAMETER-BASE-PROTOCOL-MIB
OID (symbolic): DIAMETER-BASE-PROTOCOL-MIB::dbpRealmMessageRouteAction
OID (numeric): 1.3.6.1.2.1.119.1.1.6.1.1.5
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: The action is used to identify how a message should be treated based on the realm, application and type. local - Diameter messages that resolve to a route entry with the Local Action set to Local can be satisfied locally, and do not need to be routed to another server. relay - All Diameter messages that fall within this category MUST be routed to a next-hop server, without modifying any non-routing AVPs. proxy - All Diameter messages that fall within this category MUST be routed to a next-hop server. redirect - Diameter messages that fall within this category MUST have the identity of the home Diameter server(s) appended, and returned to the sender of the message.
What is dbpRealmMessageRouteAction?
Defines how messages matching this realm/application/type are handled: local(1) answers them on this server, relay(2) or proxy(3) forwards them unmodified (or modified) to a next-hop server, and redirect(4) returns the home server's identity to the sender instead of forwarding. An admin sets this to control the Diameter routing behavior -- e.g. whether this node acts as the terminating server or just a relay -- for traffic to this realm.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.2.1.119.1.1.6.1.1.5 snmpwalk -v2c -c public <target> DIAMETER-BASE-PROTOCOL-MIB::dbpRealmMessageRouteAction
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.2.1.119.1.1.6.1.1.5.1 snmpget -v2c -c public <target> DIAMETER-BASE-PROTOCOL-MIB::dbpRealmMessageRouteAction.1
Start monitoring AAA server/Diameter agent (vendor-neutral, IETF standard) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the DIAMETER-BASE-PROTOCOL-MIB::dbpRealmMessageRouteAction OID value, configure state conditions and alerts, and monitor any AAA server/Diameter agent (vendor-neutral, IETF standard) from a single console.
OID Breakdown
Upper-level ancestors (6 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.2 | mgmt | APERTUS-NPG-MIB |
| 1.3.6.1.2.1 | mib_2 | AXON-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.2.1.119 | diameterBasePMIB | DIAMETER-BASE-PROTOCOL-MIB |
| 1.3.6.1.2.1.119.1 | diameterBaseProtocolMIB | DIAMETER-BASE-PROTOCOL-MIB |
| 1.3.6.1.2.1.119.1.1 | diameterBaseObjects | DIAMETER-BASE-PROTOCOL-MIB |
| 1.3.6.1.2.1.119.1.1.6 | dbpRealmStats | DIAMETER-BASE-PROTOCOL-MIB |
| 1.3.6.1.2.1.119.1.1.6.1 | dbpRealmMessageRouteTable | DIAMETER-BASE-PROTOCOL-MIB |
| 1.3.6.1.2.1.119.1.1.6.1.1 | dbpRealmMessageRouteEntry | DIAMETER-BASE-PROTOCOL-MIB |
| 1.3.6.1.2.1.119.1.1.6.1.1.5 | dbpRealmMessageRouteAction | DIAMETER-BASE-PROTOCOL-MIB |