Juniper-RADIUS-Initiated-Request-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › Juniper-RADIUS-Initiated-Request-MIB

Organization: Juniper Networks, Inc.

Last Updated: 2004-06-10

Category: Protocol: RADIUS, RADIUS and AAA, Vendor: Juniper

Description: Juniper Networks MIB for handling RADIUS-initiated change-of-authorization and disconnect requests from RADIUS servers.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is Juniper-RADIUS-Initiated-Request-MIB?

Juniper-RADIUS-Initiated-Request-MIB is a Juniper Networks enterprise MIB covering RADIUS server-initiated requests, such as Change-of-Authorization and Disconnect messages, on JUNOSe E-series routers. It exposes counters for disconnect requests, accepts, and rejects, plus error conditions like invalid client addresses, unknown request types, missing shared secrets, and bad authenticators, alongside a table of RADIUS clients authorized to send such requests. Its main monitoring value is as a software/protocol health indicator: rising reject, no-secret, or bad-authenticator counts flag AAA misconfiguration or an unauthorized/misconfigured RADIUS server attempting to control subscriber sessions, rather than any hardware condition. It complements standard RADIUS Authentication/Accounting MIBs (RFC 2618/2620) and the router's broader AAA subsystem. It is typically deployed on broadband/edge access routers where a centralized RADIUS server dynamically disconnects or re-authorizes subscriber sessions. Engineers can download the Juniper-RADIUS-Initiated-Request-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in Juniper-RADIUS-Initiated-Request-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

  • Juniper E-series router (JUNOSe broadband/edge access platform)

Monitoring Examples

An admin watching juniRadiusInitiatedRequestDisconnectRequests alongside juniRadiusInitiatedRequestDisconnectRejects can spot a spike in rejected disconnects, then check juniRadiusInitiatedRequestClientTable (keyed by juniRadiusInitiatedRequestClientAddress and juniRadiusInitiatedRequestClientPortNumber) to confirm which servers are authorized to issue them. A nonzero juniRadiusInitiatedRequestNoSecret or juniRadiusInitiatedRequestInvalidClientAddresses counter points to a shared-secret mismatch or an unauthorized server attempting session control.

What Can Be Monitored

  • disconnect request/accept/reject counts
  • invalid client address attempts
  • missing shared-secret events
  • bad authenticator events
  • unknown request type counts
  • authorized RADIUS client list
Imported Objects

From Juniper-MIBs

juniMibsMODULE-IDENTITY

From Juniper-TC

JuniEnable

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
IpAddress
MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

DisplayString
RowStatus

How to Use in IPNetwork Monitor

Example using juniRadiusInitiatedRequestInvalidClientAddresses OID:

Select a Juniper E-series router, JUNOSe broadband/edge platform (RADIUS CoA/Disconnect requests) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type juniRadiusInitiatedRequestInvalidClientAddresses into the Find box to locate it in the OID tree, then select it and click OK. The number of RADIUS initiated request packets received from unknown addresses. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Supports RADIUS Disconnect and CoA messages for dynamic session management derived from RFC 3576 on Juniper ERX platforms.

Start monitoring Juniper E-series router, JUNOSe broadband/edge platform (RADIUS CoA/Disconnect requests) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download Juniper-RADIUS-Initiated-Request-MIB