EXTREME-DLCS-MIB

All MIBs › EXTREME-DLCS-MIB

Organization: Extreme Networks, Inc.

Last Updated: 1999-03-04

Category: Technology: Network Monitoring, Vendor: Extreme Networks

Description: Manages Extreme Networks Dynamic Link Context System (DLCS) for user and device identity tracking.

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-DLCS-MIB?

EXTREME-DLCS-MIB is an Extreme Networks vendor-specific MIB (extremeDlcs, under the extremeAgent enterprise branch) implementing the Dynamic Link Context System, a feature that binds network identity information -- usernames, groups, applications, hostnames, and IP addresses -- to the switch port they were observed on. It exposes per-protocol collection toggles (extremeDlcsEnable, extremeDlcsNetbiosEnable, extremeDlcsKerberos5Enable, extremeDlcsRsvpEnable, extremeDlcsDnsEnable) and a binding table, extremeDlcsBindingTable, whose entries carry a BITS-valued extremeDlcsBindingType (user2ip, user2port, ip2port, application2user, application2ip, host2ip, group2ip, group2port, user2group), the detection source, the resolved user/group/application/host names, IP address, physical port, and last-update timestamp. This data lets an operator correlate a given switch port to the actual user, application, or device using it -- useful for access tracking, NAC-style investigations, and troubleshooting which endpoint is generating traffic on a given interface. It is designed to work alongside NetBIOS, Kerberos V5, RSVP, and DNS traffic snooped directly off the wire, and integrates with Extreme's Smart Trap Rules mechanism to notify managers when bindings change. Administrators can download the EXTREME-DLCS-MIB file to load it into their MIB browser for identity-binding visibility on Extreme switches.

IPNetwork Monitor allows you to monitor SNMP objects defined in EXTREME-DLCS-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 switches (ExtremeXOS-era platforms supporting DLCS)

Monitoring Examples

An operator polls extremeDlcsBindingTable filtering on extremeDlcsBindingPhysPort for a suspect switch port, reading extremeDlcsBindingUser and extremeDlcsBindingApplication to identify who and what is using it; an entry whose extremeDlcsBindingUpdateTime is stale despite active traffic on that port would suggest DLCS has lost visibility into that binding.

What Can Be Monitored

per-protocol binding collection enable state
user-to-IP/port binding table entries
binding type bitmask (user/group/application/host correlations)
binding detection source
binding last-update timestamp

Imported Objects

From EXTREME-BASE-MIB

extremeAgent

OBJECT-IDENTITY

From RFC1213-MIB

DisplayString

From SNMPv2-SMI

IpAddress
MODULE-IDENTITY
OBJECT-TYPE
TimeTicks

From SNMPv2-TC

TruthValue

OIDs

OID symbolic	OID numeric	Type	Access	Description
extremeDlcs	1.3.6.1.4.1.1916.1.8			Extreme Dynamic-Link Context System (DLCS) status objects
T/F extremeDlcsEnable	1.3.6.1.4.1.1916.1.8.1	TruthValue	read-write	Setting this to true will allow the agent to start collecting DLCS binding information.
T/F extremeDlcsNetbiosEnable	1.3.6.1.4.1.1916.1.8.2	TruthValue	read-write	Setting this to true will allow the agent to start collecting DLCS binding information using the NetBios protocol.
T/F extremeDlcsKerberos5Enable	1.3.6.1.4.1.1916.1.8.3	TruthValue	read-write	Setting this to true will allow the agent to start collecting DLCS binding information using the Kerberos V5 protocol.
T/F extremeDlcsRsvpEnable	1.3.6.1.4.1.1916.1.8.4	TruthValue	read-write	Setting this to true will allow the agent to start collecting DLCS binding information using the RSVP protocol.
T/F extremeDlcsDnsEnable	1.3.6.1.4.1.1916.1.8.5	TruthValue	read-write	Setting this to true will allow the agent to start collecting DLCS binding information using the DNS protocol.
extremeDlcsBindingTable	1.3.6.1.4.1.1916.1.8.6		not-accessible	Table of DLCS Binding information. Entries are added and deleted by the agent based on information gathered from the local network environment. Multiple entries may exist for almost identical sets of bindings although the agent will ensure that exactly matching entries are coalesced.
extremeDlcsBindingEntry	1.3.6.1.4.1.1916.1.8.6.1		not-accessible	Entry in table of DLCS bindings.
INT extremeDlcsBindingIndex	1.3.6.1.4.1.1916.1.8.6.1.1	INTEGER	read-only	An index into this table, chosen by the agent. This has no significance to the manager beyond its uniqueness within this agent.
BIT extremeDlcsBindingType	1.3.6.1.4.1.1916.1.8.6.1.2	Bits	read-only	The type of binding expressed here. A given bit is set if DLCS has detected that the two relevant items are bound together. e.g. an entry with application2user(3) set to 1 implies that the username extremeDlcsBindingUser has been seen to be using the application extremeDlcsBindingApplication. In addition, if this entry also has user2port(1) set to 1 then this user and application have been detected as running on the physical switch port extremeDlcsBindingPhysPort.
INT extremeDlcsBindingSource	1.3.6.1.4.1.1916.1.8.6.1.3	INTEGER	read-only	The source of the information binding.
STR extremeDlcsBindingUser	1.3.6.1.4.1.1916.1.8.6.1.4	DisplayString	read-only	The User name detected by DLCS. A string of length zero indicates no valid User name has been detected for this binding.
STR extremeDlcsBindingGroup	1.3.6.1.4.1.1916.1.8.6.1.5	DisplayString	read-only	The Group name detected by DLCS. A string of length zero indicates no valid Group name has been detected for this binding.
STR extremeDlcsBindingApplication	1.3.6.1.4.1.1916.1.8.6.1.6	DisplayString	read-only	The Application name detected by DLCS. A string of length zero indicates no valid Application name has been detected for this binding.
STR extremeDlcsBindingHost	1.3.6.1.4.1.1916.1.8.6.1.7	DisplayString	read-only	The Host name detected by DLCS. A string of length zero indicates no valid Host name has been detected for this binding.
IP extremeDlcsBindingIpAddress	1.3.6.1.4.1.1916.1.8.6.1.8	IpAddress	read-only	The IP address detected by DLCS. A value of 0.0.0.0 indicates no valid IP address has been detected for this binding.
INT extremeDlcsBindingPhysPort	1.3.6.1.4.1.1916.1.8.6.1.9	INTEGER	read-only	The physical port number (ifIndex) detected by DLCS. This is valid in all bindings.
TIK extremeDlcsBindingUpdateTime	1.3.6.1.4.1.1916.1.8.6.1.10	TimeTicks	read-only	The value of sysUpTime when this entry was last updated.

RFC description

Monitors Extreme Dynamic-Link Context System (DLCS) binding information for network protocol applications.

Start monitoring Extreme Networks switch, ExtremeXOS-era (Dynamic Link Context System identity binding) 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-DLCS-MIB

What Is EXTREME-DLCS-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description