RBN-BIND-MIB

All MIBs › RBN-BIND-MIB

Organization: Redback Networks, Inc.

Last Updated: 2003-10-13

Category: Vendor: Ericsson

Description: Manages subscriber circuit bindings to VRF contexts on Redback SmartEdge BRAS 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 RBN-BIND-MIB?

RBN-BIND-MIB is a vendor-specific module for Redback SmartEdge BRAS (Broadband Remote Access Server) platforms that manages the binding of subscriber circuits to interfaces, contexts (VRFs), and authentication settings. It exposes a bind table associating each circuit with a type, name, VRF context, authentication context, service group, ACL, and CHAP/PAP authentication credentials. Its monitoring value is largely configuration/service-status verification: checking rbnBindContext and rbnBindServiceGrp per rbnBindCircuit confirms that a subscriber's circuit is correctly bound to its intended VRF and service policy, and authentication object states (rbnBindAuthChap/rbnBindAuthPap) reveal whether the expected authentication method is active for that binding, both important for diagnosing subscriber connectivity or authentication failures. It depends on the router's broader circuit and VRF/context infrastructure defined elsewhere in the Redback MIB suite. It is typically deployed in broadband/ISP access networks on Redback SmartEdge routers provisioning large numbers of subscriber circuits, and administrators can download the RBN-BIND-MIB file to load it into their MIB browser.

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

Redback SmartEdge BRAS router

Monitoring Examples

An administrator would poll rbnBindTable/rbnBindEntry, checking rbnBindCircuit against rbnBindContext and rbnBindServiceGrp to confirm a subscriber's circuit is bound into the correct VRF and service group. If a subscriber cannot get service, rbnBindAuthChap/rbnBindAuthPap and rbnBindAuthContext would be checked to see whether the expected authentication method and authentication context are properly configured for that binding. rbnBindAcl would be inspected to verify the correct access control list is being applied to the bound circuit.

What Can Be Monitored

circuit-to-context binding
subscriber authentication method (CHAP/PAP)
service group assignment
ACL assignment per binding
authentication context per circuit

Imported Objects

From RBN-SMI

rbnMgmt

OBJECT-IDENTITY

From RBN-TC

RbnCircuitHandle
RbnPort
RbnSlot

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

TEXTUAL-CONVENTION
TruthValue

OIDs

OID symbolic	OID numeric	Type	Access	Description
rbnBindMib	1.3.6.1.4.1.2352.2.17			Defines the objects necessary to support binding circuits to interfaces.
rbnBindMIBObjects	1.3.6.1.4.1.2352.2.17.1
rbnBindTable	1.3.6.1.4.1.2352.2.17.1.1		not-accessible	This table contains the objects which identify and configure circuit bindings. With respect to creation and deletion of entries in this table, rows are created or deleted when a circuit is created or deleted - there is no explicit explicit creation or deletion of rows allowed or required.
rbnBindEntry	1.3.6.1.4.1.2352.2.17.1.1.1		not-accessible	A conceptual row in the rbnBindTable.
RBN rbnBindCircuit	1.3.6.1.4.1.2352.2.17.1.1.1.1	RbnCircuitHandle	not-accessible	A key identifying the circuit for which the binding applies. Note the implication: this key identifies an existing circuit. A basic tenent thus evolves: the circuit must exist before it can be bound. See the definition of the RbnCircuitHandle TEXTUAL-CONVENTION for the definition of this key.
RBN rbnBindType	1.3.6.1.4.1.2352.2.17.1.1.1.2	RbnBindType	read-create	The type of the binding. See the definition of the RbnBindType TEXTUAL-CONVENTION for the possible types. The bind type must be appropriate to the type of circuit that it is being applied to. See the AOS Command Reference Manual for a complete exposition of what circuit types may be associated with which bindings. Note that when a circuit is created, an initial binding is established of type 'unbound'. So there is always some binding in effect for a circuit; there is no concept of explicitly creating or deleting a binding, there is merely setting it's type and supplying the applicable attributes for the bind type. In other words, with respect to entries in this table, when a circuit is created, a row in this table is also created. and when a circuit is deleted, the row in this table is also deleted. If you change the bind type to a new bind type for a circuit, the previous binding is removed and any active sessions are dropped. If an existing binding on the circuit is exactly the same as specified in the new binding, the existing binding is not removed. When changing the bind type to a new bind type, all objects mandatory for the new bind type must be included in the set operation. Thus, the bind type will determine which group of objects in a row of the rbnBindTable that will be applicable for that instance of a circuit. For example, if the bind type is 'subscriberBind', then the columns in the row that are applicable will be: rbnBindType rbnBindName rbnBindContext rbnBindPassword In a set operation, if additional columns are specified for some given bind type, that is, columnar objects which are not applicable to the given bind type, an INCONSISTENT VALUE error will be returned. The DESCRIPTION clause for each of the rbnBindTable objects specifies the bind types that are applicable for that object. For a complete specification of the various bind types and the applicable columns of the rbnBindTable, please see AOS Command Reference manual.
STR rbnBindName	1.3.6.1.4.1.2352.2.17.1.1.1.3	SnmpAdminString	read-create	A name associated with the binding. This field is only applicable when the value of rbnBindType is: bypassBind interfaceBind subscriberBind l2tptunnelBind multiIntfBind multiSubBind sessionBind If the value of rbnBindType is not one of these bind types, then rbnBindName is not instantiated for this entry. The value of rbnBindName is dependent on the value specified in rbnBindType as described below: Bind Type Value of Name --------- ------------- bypassBind the name of an existing bypass to which the circuit is to be bound interfaceBind the name of an existing interface subscriberBind the name of a subscriber l2tptunnelBind the tunnel to which the circuit is to be bound multiIntfBind the name of an existing interface multiSubBind the name of a subscriber sessionBind the name of the peer or L2TP group to which the circuit is to be bound Don't think of rbnBindName as the name of the binding. Rather, it is the name of some other attribute associated with the binding.
STR rbnBindPassword	1.3.6.1.4.1.2352.2.17.1.1.1.4	SnmpAdminString	read-create	The AAA password. This field is only applicable when the value of rbnBindType is: subscriberBind If the value of rbnBindType is not this bind type, then rbnBindPassword is not instantiated for this entry.
STR rbnBindContext	1.3.6.1.4.1.2352.2.17.1.1.1.5	SnmpAdminString	read-create	The name of the context associated with the binding. This field is applicable only when one of the following rbnBindType values is specified: Bind Type Value of Context --------- ---------------- bypassBind The name of the context where the bypass exists. interfaceBind The name of the context in which the specified interface exists. subscriberBind The name of the context used to locate the subscriber information. l2tptunnelBind The name of the context in which the tunnel is configured. sessionBind The name of the context for the peer. multiIntfBind The name of the context for the interface to which the IP over Ethernet portion of the circuit is to be bound. multiSubBind The name of the context for the interface to which the IP over Ethernet portion of the circuit is to be bound. multiClipsBind The name of the context for the interface to which the IP over Ethernet portion of the circuit is to be bound. If the value of rbnBindType is not one of these bind types, then rbnBindContext is not instantiated for this entry.
STR rbnBindAuthContext	1.3.6.1.4.1.2352.2.17.1.1.1.6	SnmpAdminString	read-create	The name of the authentication context associated with the binding. It is the name of the context to which PPP sessions on the circuits being bound are restricted. Specification of this column for a given entry is optional. When using this optional context name, all attempts to bind PPP sessions to contexts other than the one specified will fail. This object is applicable only when one of the following rbnBindType values is specified: authBind multiIntfBind multiSubBind If the value of rbnBindType is not one of these bind types, then rbnBindAuthContext is not instantiated for this entry.
STR rbnBindServiceGrp	1.3.6.1.4.1.2352.2.17.1.1.1.7	SnmpAdminString	read-create	The name of the service access list associated with the binding. It is the name of the service access list that defines the services available to the PPP-encapsulated circuit. Specification of this column for a given entry is optional. When using this optional service access list, all attempts to authenticate to contexts or domains not permitted by the named service access list fail. This object is applicable only when one of the following rbnBindType values is specified: authBind multiIntfBind multiSubBind multiClipsBind If the value of rbnBindType is not one of these bind types, then rbnBindServiceGrp is not instantiated for this entry.
STR rbnBindAcl	1.3.6.1.4.1.2352.2.17.1.1.1.8	SnmpAdminString	read-create	The name of the bridge access control list associated with the binding. It is the name of the Access control list to be applied to the session. The access control list must already have been configured in the context of the session peer. This is typically used to filter packets so that only PPPoE traffic is allowed through an Ethernet L2TP tunnel. Specification of this column for a given entry is optional. This object is applicable only when one of the following rbnBindType values is specified: sessionBind If the value of rbnBindType is not one of these bind types, then rbnBindAcl is not instantiated for this entry.
T/F rbnBindAuthChap	1.3.6.1.4.1.2352.2.17.1.1.1.9	TruthValue	read-create	If 'true', specifies that the PPP authentication protocol to be used is Challenge Handshake Authentication Protocol. This object is applicable only when one of the following rbnBindType values is specified: authBind multiIntfBind multiSubBind If the value of rbnBindType is not one of these bind types, then rbnBindAuthChap is not instantiated for this entry. When performing a set operation on a row which involves one of these bind types, either rbnBindAuthChap or rbnBindAuthPap or both must be specified. If both rbnBindAuthChap and rbnBindAuthPap are true, then either authentication protocol may be used.
T/F rbnBindAuthPap	1.3.6.1.4.1.2352.2.17.1.1.1.10	TruthValue	read-create	If 'true', specifies that the PPP authentication protocol to be used is Password Authentication Protocol. This object is applicable only when one of the following rbnBindType values is specified: authBind multiIntfBind multiSubBind If the value of rbnBindType is not one of these bind types, then rbnBindAuthPap is not instantiated for this entry. When performing a set operation on a row which involves one of these bind types, either rbnBindAuthChap or rbnBindAuthPap or both must be specified. If both rbnBindAuthChap and rbnBindAuthPap are true, then either authentication protocol may be used.
T/F rbnBindAuthWait	1.3.6.1.4.1.2352.2.17.1.1.1.11	TruthValue	read-create	If 'true', specifies that the inbound CHAP authentication is completed first. In other words, after the two sides have decided to use CHAP, the SMS waits for the inbound side to initiate athentication. If 'true', rbnBindAuthChap must also be specified. This object is applicable only when one of the following rbnBindType values is specified: authBind multiIntfBind multiSubBind If the value of rbnBindType is not one of these bind types, then rbnBindAuthWait is not instantiated for this entry. When performing a set operation on a row which involves this bind type, specification of this column is optional. If not specified, this object will not be instantiated.
T/F rbnBindAuthPapFirst	1.3.6.1.4.1.2352.2.17.1.1.1.12	TruthValue	read-create	If 'true', specifies that Password Authentication Protocol (PAP) shall be negotiated before Challenge Handshake Authentication Protocol (CHAP). IF 'false', then CHAP is negotiated before PAP. With SNMP get operations, both rbnBindAuthChap and rbnBindAuthPap must be true or this object is not instantiated. With SNMP set operations, if 'true', then both rbnBindAuthChap and rbnBindAuthPap must also be specified as 'true'. This object is applicable only when one of the following rbnBindType values is specified: authBind multiIntfBind multiSubBind If the value of rbnBindType is not one of these bind types, then rbnBindAuthPapFirst is not instantiated for this entry. When performing a set operation on a row which involves one of these bind types, specification of this column is optional. If not specified, this object will not be instantiated.
U32 rbnBindMaxSessions	1.3.6.1.4.1.2352.2.17.1.1.1.13	Unsigned32	read-create	The maximum number of concurrent sessions allowed on the circuit. Applicable only to circuits which have an encapsulation of type PPPoE. If the circuit is not of this type, then this entry is ignored. Specification of this column for a given row is optional. If not specified, this object will not be instantiated. This object is applicable only when one of the following rbnBindType values is specified: authBind sessionBind multiIntfBind multiSubBind multiClipsBind If the value of rbnBindType is not one of these bind types, then rbnBindMaxSessions is not instantiated for this entry. The maximum number of concurrent sessions allowed on the circuit depends on the platform as specified in the table below: Platform Sessions MemSize -------- -------- ------- SMS10000 65535 SMS1800/1000 10000 64MB FE SMS1800/1000 8000 48MB FE SMS1800/1000 4000 32MB FE SMS1800/1000 4000 16MB FE SMS1800/1000 4000 8MB FE SMS500 2000
RBN rbnBindPvcSlot	1.3.6.1.4.1.2352.2.17.1.1.1.14	RbnSlot	read-create	The chassis slot number associated with this binding. Use of the 'dot1qBind' type is for binding an ATM or Frame Relay PVC to an Ethernet port using the specified VLAN ID in rbnBindVpn. This object is applicable only when one of the following rbnBindType values is specified: dot1qBind If the value of rbnBindType is not one of these bind types, then rbnBindPvcSlot is not instantiated for this entry.
RBN rbnBindPvcPort	1.3.6.1.4.1.2352.2.17.1.1.1.15	RbnPort	read-create	The chassis port number associated with this binding. Use of the 'dot1qBind' type is for binding an ATM or Frame Relay PVC to an Ethernet port using the specified VLAN ID in rbnBindVpn. This object is applicable only when one of the following rbnBindType values is specified: dot1qBind If the value of rbnBindType is not one of these bind types, then rbnBindPvcPort is not instantiated for this entry.
U32 rbnBindVpn	1.3.6.1.4.1.2352.2.17.1.1.1.16	Unsigned32	read-create	The specific tag to which the PVC is mapped on the specified Ethernet port. Use of the 'dot1qBind' type is for binding an ATM or Frame Relay PVC to an Ethernet port using the specified VLAN ID in rbnBindVpn. This object is applicable only when one of the following rbnBindType values is specified: dot1qBind If the value of rbnBindType is not one of these bind types, then rbnBindVpn is not instantiated for this entry.
T/F rbnBindAuthDhcp	1.3.6.1.4.1.2352.2.17.1.1.1.17	TruthValue	read-create	If 'true', specifies an authentication mechanism where the DHCP server makes a request to the authentication subsystem upon receipt of incoming DHCP discover packets. This object is applicable only when one of the following rbnBindType values is specified: multiIntfBind multiClipsBind If the value of rbnBindType is not one of these bind types, then rbnBindAuthDhcp is not instantiated for this entry. When performing a set operation on a row which involves one of these bind types, if either rbnBindAuthChap or rbnBindAuthPap or both are specified, then rbnBindAuthDhcp may not be specified.
rbnBindMIBConformance	1.3.6.1.4.1.2352.2.17.2
rbnBindCompliances	1.3.6.1.4.1.2352.2.17.2.1
rbnBindCompliance	1.3.6.1.4.1.2352.2.17.2.1.1			The compliance statement for SNMP entities which implement the RBN-BIND-MIB.
rbnBindCompliance2	1.3.6.1.4.1.2352.2.17.2.1.2			The compliance statement for SNMP entities which implement the RBN-BIND-MIB.
rbnBindGroups	1.3.6.1.4.1.2352.2.17.2.2
rbnBindConfigGroup	1.3.6.1.4.1.2352.2.17.2.2.1			The collection of all objects applicable for all values of rbnBindType.
rbnBindConfigGroup2	1.3.6.1.4.1.2352.2.17.2.2.2			The collection of all objects applicable for all values of rbnBindType.
rbnBindMIBNotifications	1.3.6.1.4.1.2352.2.17.3

RFC description

Redback Networks vendor-private MIB for binding management and session control in broadband access concentrators.

Start monitoring Redback SmartEdge BRAS router (subscriber circuit-to-interface 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 RBN-BIND-MIB

What Is RBN-BIND-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description