BIANCA-BRICK-RADIUS-MIB

All MIBs › BIANCA-BRICK-RADIUS-MIB

Category: RADIUS and AAA, Vendor: bintec

Description: Covers RADIUS authentication client setup and statistics on bintec elmeg BIANCA/BRICK routers.

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 BIANCA-BRICK-RADIUS-MIB?

BIANCA-BRICK-RADIUS-MIB manages RADIUS authentication client configuration and statistics on bintec elmeg BIANCA/BRICK routers, used to authenticate dial-in, VPN, or PPP WAN users against a central RADIUS server. It exposes RADIUS server configuration such as server address and timeout/retry settings, plus statistics counters for authentication requests, accepts, rejects, and timeouts. Its monitoring value is software/service health: a rising rate of RADIUS rejects or timeouts signals a misconfigured shared secret, an unreachable RADIUS server, or a credential problem affecting user authentication. It directly depends on and complements the standard RADIUS protocol (RFC 2865) as its underlying authentication mechanism. It is typically deployed on branch-office BRICK routers authenticating remote-access or PPP WAN users against a centralized RADIUS infrastructure. Network engineers evaluating or troubleshooting this functionality can download the BIANCA-BRICK-RADIUS-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in BIANCA-BRICK-RADIUS-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

bintec elmeg BIANCA/BRICK router

Monitoring Examples

An admin would monitor the RADIUS request/accept/reject counters to establish a baseline authentication success rate, then investigate a spike in reject or timeout counts as an indicator that the configured RADIUS server is unreachable or the shared secret is mismatched. Server configuration objects would be checked to confirm the router is pointed at the correct primary/secondary RADIUS server addresses after a network change.

What Can Be Monitored

RADIUS server configuration
authentication request/accept/reject counts
authentication timeout counts
RADIUS client status

Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter
IpAddress

From SNMPv2-TC

DisplayString

OIDs

OID symbolic	OID numeric	Type	Access	Description
org	1.3
dod	1.3.6
internet	1.3.6.1
private	1.3.6.1.4
enterprises	1.3.6.1.4.1
bintec	1.3.6.1.4.1.272
bintecsec	1.3.6.1.4.1.272.254
radius	1.3.6.1.4.1.272.254.8
radiusServerTable	1.3.6.1.4.1.272.254.8.1		not-accessible
radiusServerEntry	1.3.6.1.4.1.272.254.8.1.1		not-accessible
INT radiusSrvProtocol	1.3.6.1.4.1.272.254.8.1.1.1	INTEGER	read-write	Type of authentication server. To configure the radius authentication use authentication(1), for radius accounting accounting(2), for user authentication on login shell login(3).
IP radiusSrvAddress	1.3.6.1.4.1.272.254.8.1.1.2	IpAddress	read-write	The Radius Server IP Address.
INT radiusSrvPort	1.3.6.1.4.1.272.254.8.1.1.3	INTEGER	read-write	The radius server port. Please notice that RFC2138 assigns port 1812 and 1813 for authentication and accounting, respectively. Many Radius servers still use the former assigned port 1645 and 1646 instead. The default value is 1812 and 1813.
STR radiusSrvSecret	1.3.6.1.4.1.272.254.8.1.1.4	DisplayString	read-write	The shared secret between radius server and Brick.
INT radiusSrvPriority	1.3.6.1.4.1.272.254.8.1.1.5	INTEGER	read-write	The radius server with the lowest priority is the first used for request. If there is no response (see also the values Timeout and Retries) the radius server with the next lowest priority will be used. Default value is 0.
INT radiusSrvTimeout	1.3.6.1.4.1.272.254.8.1.1.6	INTEGER	read-write	The amount of milliseconds (1/1000s) waiting for an outstanding request. Default is 1000 (1 second).
INT radiusSrvRetries	1.3.6.1.4.1.272.254.8.1.1.7	INTEGER	read-write	The number of retries sent for each request, until the server state is set to inactive. Default value is 1. To prevent the radiusSrvState ever switch to inactive, set this value to 0.
INT radiusSrvState	1.3.6.1.4.1.272.254.8.1.1.8	INTEGER	read-write	When operational, the server state is active(1). If the radius server does not respond, its state is set to inactive(2). The administrator can set the state manually to disabled(3), or delete(4) the entry.
INT radiusSrvPolicy	1.3.6.1.4.1.272.254.8.1.1.9	INTEGER	read-write	If set to authoritative(1), a negative answer to a request will be accepted. This is not necessarily true when set to non-authoritative(2), where the next radius server will be asked until there is finally an authoritative(1) server configured.
INT radiusSrvValidate	1.3.6.1.4.1.272.254.8.1.1.10	INTEGER	read-write	This additional option is only used for bogus RADIUS servers, which send response messages with a wrong calculated MD5 checksum. All messages generated by the brick, however, will always use the proper authentication scheme. For security reasons, this option should always be set to enabled(1).
INT radiusSrvDialout	1.3.6.1.4.1.272.254.8.1.1.11	INTEGER	read-write	This option provides a means for RADIUS dialout configuration. When set to enabled(1), routing information is read into the brick after system startup. This information must be configured in the RADIUS server as dialout-1 to dialout-n, where n is a value of range 1-99. The end is automatically determined when the brick gets a negative response. This means, all entrys must be consecutive. The default value is disabled(2).
STR radiusSrvDefaultPW	1.3.6.1.4.1.272.254.8.1.1.12	DisplayString	read-write	This is the default USER-PASSWORD the brick sends where no password is available (for example, in requests for the calling number or boot requests). Some RADIUS servers rely on a configured USER- or CHAP-PASSWORD for any RADIUS request. The default value is an empty string.
INT radiusSrvReloadInterval	1.3.6.1.4.1.272.254.8.1.1.13	INTEGER	read-write	Reload interval for RADIUS dialout configuration in minutes. The default is 0 (no reload is performed automatically.
CTR radiusSrvAuthRequests	1.3.6.1.4.1.272.254.8.1.1.14	Counter	read-only	Total number of access requests sent.
CTR radiusSrvAuthAccepts	1.3.6.1.4.1.272.254.8.1.1.15	Counter	read-only	Total number of access accepts received.
CTR radiusSrvAuthRejects	1.3.6.1.4.1.272.254.8.1.1.16	Counter	read-only	Total number of access rejects received.
CTR radiusSrvAuthReqRetrans	1.3.6.1.4.1.272.254.8.1.1.17	Counter	read-only	Total number of retransmitted access requests.
CTR radiusSrvAuthReqFailed	1.3.6.1.4.1.272.254.8.1.1.18	Counter	read-only	Total number of failed (not rejected) access requests.
CTR radiusSrvAuthReqPending	1.3.6.1.4.1.272.254.8.1.1.19	Counter	read-only	Total number of pending access requests.
CTR radiusSrvAcctStarts	1.3.6.1.4.1.272.254.8.1.1.20	Counter	read-only	Total number of accounting starts sent.
CTR radiusSrvAcctStops	1.3.6.1.4.1.272.254.8.1.1.21	Counter	read-only	Total number of accounting stops sent.
INT radiusSrvKeepalive	1.3.6.1.4.1.272.254.8.1.1.22	INTEGER	read-write	Enables the periodicaly keep alive check of 'inactive' (see radiusSrvState) server.

RFC description

Manages RADIUS authentication client configuration and statistics on bintec elmeg BIANCA/BRICK routers.

Start monitoring bintec elmeg BIANCA/BRICK routers 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 BIANCA-BRICK-RADIUS-MIB

What Is BIANCA-BRICK-RADIUS-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description