EXTREME-SERVICES-MIB

All MIBs › EXTREME-SERVICES-MIB

Organization: Extreme Networks, Inc.

Last Updated: 2000-07-24

Category: Vendor: Extreme Networks

Description: Extreme Networks MIB for network services configuration including NAT, load balancing, and application-aware services on Extreme platforms.

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 EXTREME-SERVICES-MIB?

EXTREME-SERVICES-MIB is an Extreme Networks vendor MIB covering upper-layer network services configured on Extreme switches, including DNS server settings and authentication server (RADIUS/TACACS+-style) configuration for network access control. It exposes configuration data such as configured DNS servers and per-server-type authentication server settings (address, address type, enablement by access type). Its monitoring role is primarily configuration/software-service oriented: an operator can verify which DNS and authentication servers are configured and enabled for a given access type, confirming services critical to network login and name resolution are correctly set up, rather than tracking physical sensors. It layers Extreme-specific service configuration on top of standard network concepts (DNS, AAA) with no explicit dependency noted on other formal IETF service MIBs in the available extract. It is typically deployed on Extreme switches/controllers providing centralized authentication and name-resolution services to network clients, and this EXTREME-SERVICES-MIB guide documents the DNS and authentication-server configuration objects.

IPNetwork Monitor allows you to monitor SNMP objects defined in EXTREME-SERVICES-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

Extreme Networks Ethernet switch/controller

Monitoring Examples

An administrator would poll extremeDNSServerTable/extremeDNSServerEntry to confirm configured DNS server addresses are correct and reachable. extremeAuthServerTable/extremeAuthServerEntry (indexed by extremeAuthServerIndex) exposes extremeAuthServerAddressType and extremeAuthServerAddress for each configured authentication server, while extremeAuthServerEnableTable/extremeAuthServerEnableEntry shows extremeAuthServerEnable status per extremeAuthServerEnableServerType and extremeAuthServerEnableAccessType. A disabled or misconfigured authentication server entry here would explain why client devices are failing 802.1X or web-authentication login attempts.

What Can Be Monitored

configured DNS servers
authentication server address/type
authentication server enable status per access type

Imported Objects

From EXTREME-BASE-MIB

extremeAgent

OBJECT-IDENTITY

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From SNMPv2-SMI

MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

RowStatus
TEXTUAL-CONVENTION
TruthValue

OIDs

OID symbolic	OID numeric	Type	Access	Description
extremeServices	1.3.6.1.4.1.1916.1.26			Extreme Upper layer services objects
extremeSyslog	1.3.6.1.4.1.1916.1.26.1
extremeRemoteSyslogServerTable	1.3.6.1.4.1.1916.1.26.1.1		not-accessible	This table is used to configure remote syslog servers and contains information on the same.
extremeRemoteSyslogServerEntry	1.3.6.1.4.1.1916.1.26.1.1.1		not-accessible	An entry in the extremeRemoteSyslogServerTable.
IPt extremeRemoteSyslogServerAddressType	1.3.6.1.4.1.1916.1.26.1.1.1.1	InetAddressType	read-only	The type of address specified in the object 'extremeRemoteSyslogServerAddress'. Currently, only 'ipv4' and 'dns' are supported.
IP extremeRemoteSyslogServerAddress	1.3.6.1.4.1.1916.1.26.1.1.1.2	InetAddress	read-only	The address of the remote syslog server. This can be a DNS name or an IPv4 address.
INT extremeRemoteSyslogServerPort	1.3.6.1.4.1.1916.1.26.1.1.1.3	INTEGER	read-only	The UDP port number of the remote syslog server to which syslog messages will be sent.
INT extremeRemoteSyslogServerFacility	1.3.6.1.4.1.1916.1.26.1.1.1.4	INTEGER	read-only	The facility which will be sent in all syslog messages to this remote syslog server.
BIT extremeRemoteSyslogServerSeverity	1.3.6.1.4.1.1916.1.26.1.1.1.5	Bits	read-create	The syslog message severity. All syslog messages of the specified severity for which the Bits are set, will be sent to this syslog server. When setting this object in a 'createAndGo' request, all lower bits upto and including the desired bit position must be set. For example, if bit info(4) needs to be set then bits critical(0), error(1), warning(2), notice(3) and info(4) must also be set in the request. Consequently, all syslog messages of a given severity and higher will be sent to the syslog server. It is not possible to send messages that match only a few selected non-contiguous severities.
ROW extremeRemoteSyslogServerStatus	1.3.6.1.4.1.1916.1.26.1.1.1.6	RowStatus	read-create	The status of the Row as per standard row status conventions. Only 'createAndGo', 'active' and 'destroy' will be supported. It is not possible to change the values of the objects of a row once it has been created, except by 'destroy'ing and re-creating the row.
T/F extremeEnableRemoteSyslog	1.3.6.1.4.1.1916.1.26.1.2	TruthValue	read-write	The enable/disable status of remote syslog messages.
extremeDNS	1.3.6.1.4.1.1916.1.26.3
extremeDNSServerTable	1.3.6.1.4.1.1916.1.26.3.1		not-accessible	This table is used to configure DNS servers. There can be at most two rows in this table.
extremeDNSServerEntry	1.3.6.1.4.1.1916.1.26.3.1.1		not-accessible	An entry in the extremeDNSServerTable.
INT extremeDNSServerAddressIndex	1.3.6.1.4.1.1916.1.26.3.1.1.1	INTEGER	not-accessible	This is an integer index. Only 1 and 2 are supported for this
IPt extremeDNSServerAddressType	1.3.6.1.4.1.1916.1.26.3.1.1.2	InetAddressType	read-only	The address type of the DNS server. This can be a DNS name or an IPv4 address.
IP extremeDNSServerAddress	1.3.6.1.4.1.1916.1.26.3.1.1.3	InetAddress	read-only	The address of the DNS server. This can be a DNS name or an IPv4 address.
extremeAuthServer	1.3.6.1.4.1.1916.1.26.4
extremeAuthServerEnableTable	1.3.6.1.4.1.1916.1.26.4.1		not-accessible	This table is used to enable/disable Auth servers
extremeAuthServerEnableEntry	1.3.6.1.4.1.1916.1.26.4.1.1		not-accessible	An entry in the extremeAuthServerEnableTable.
AUT extremeAuthServerEnableServerType	1.3.6.1.4.1.1916.1.26.4.1.1.1	AuthServerType	not-accessible	Specifies whether this is a radius/radius-acct/tacacs/tacacs-acct server
AUT extremeAuthServerEnableAccessType	1.3.6.1.4.1.1916.1.26.4.1.1.2	AuthServerAccessType	not-accessible	Specifies whether this server is for management access or netlogin access.
T/F extremeAuthServerEnable	1.3.6.1.4.1.1916.1.26.4.1.1.3	TruthValue	read-write	Enable/Disable the Radius/tacas Server
extremeAuthServerTable	1.3.6.1.4.1.1916.1.26.4.2		not-accessible	This table is used to configure radius/tacacs servers.
extremeAuthServerEntry	1.3.6.1.4.1.1916.1.26.4.2.1		not-accessible	An entry in the extremeAuthServerTable.
INT extremeAuthServerIndex	1.3.6.1.4.1.1916.1.26.4.2.1.1	INTEGER	not-accessible	Integer index of the server.
IPt extremeAuthServerAddressType	1.3.6.1.4.1.1916.1.26.4.2.1.2	InetAddressType	read-write	Type IP address of the radius/tacas server.
IP extremeAuthServerAddress	1.3.6.1.4.1.1916.1.26.4.2.1.3	InetAddress	read-write	IP address of the radius/tacas server.
IPt extremeAuthServerClientAddressType	1.3.6.1.4.1.1916.1.26.4.2.1.4	InetAddressType	read-write	Type of IP address to use as the SRC address when contacting the the radius/tacas server. The radius/tacas server should be configured with this address as one of its clients. The switch should have a VLAN with this IP address.
IP extremeAuthServerClientAddress	1.3.6.1.4.1.1916.1.26.4.2.1.5	InetAddress	read-write	IP address to use as the SRC address when contacting the the radius/tacas server. The radius/tacas server should be configured with this address as one of its clients. The switch should have a VLAN with this IP address.
INT extremeAuthServerPort	1.3.6.1.4.1.1916.1.26.4.2.1.6	INTEGER	read-write	Port number of the radius/tacas server.
OCT extremeAuthServerSecret	1.3.6.1.4.1.1916.1.26.4.2.1.7	OCTET STRING	read-write	This is the shared secret between the Authenticator and radius/tacas server. This is logically write-only.
INT extremeAuthServerReTransmit	1.3.6.1.4.1.1916.1.26.4.2.1.8	INTEGER	read-write	This is the timeout in seconds after which the Authenticator will re transmit requests to the radius/tacas server.
AUT extremeAuthServerType	1.3.6.1.4.1.1916.1.26.4.2.1.9	AuthServerType	read-write	Specifies whether this is a radius/radius-acct/tacacs/tacacs-acct server
T/F extremeAuthServerIsPrimary	1.3.6.1.4.1.1916.1.26.4.2.1.10	TruthValue	read-write	Specifies whether this is the primary or the secondary server. Is TRUE if the server is primary.
AUT extremeAuthServerAccessType	1.3.6.1.4.1.1916.1.26.4.2.1.11	AuthServerAccessType	read-write	Specifies whether this server is for management access or netlogin access
ROW extremeAuthServerStatus	1.3.6.1.4.1.1916.1.26.4.2.1.12	RowStatus	read-create	The status of the Row as per standard row status conventions. Only 'createAndGo', 'active' and 'destroy' will be supported. It is not possible to change the values of the objects of a row once it has been created, except by 'destroy'ing and re-creating the row.

RFC description

Manages upper-layer services including syslog, DNS, and authentication server configuration on Extreme switches.

Start monitoring Extreme Networks Ethernet switch/controller (DNS/AAA upper-layer services) 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 EXTREME-SERVICES-MIB

What Is EXTREME-SERVICES-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description