RBN-BIND-MIB :: rbnBindName

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

All MIBs › RBN-BIND-MIB › rbnBindName

rbnBindName

Module: RBN-BIND-MIB

OID (symbolic): RBN-BIND-MIB::rbnBindName

OID (numeric): 1.3.6.1.4.1.2352.2.17.1.1.1.3

Node type: OBJECT-TYPE

Type: SnmpAdminString

Access: read-create

Description: 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.

What is rbnBindName?

This SnmpAdminString (1-192 chars) holds the name of whatever object the binding actually points to, and its meaning shifts with rbnBindType: an existing bypass for bypassBind, an interface for interfaceBind or multiIntfBind, a subscriber for subscriberBind or multiSubBind, a tunnel for l2tptunnelBind, or a peer/L2TP group for sessionBind. It is not applicable, and is left uninstantiated, when rbnBindType is set to a type outside that list. For instance, with rbnBindType set to interfaceBind, an admin would populate rbnBindName with an existing interface name such as "ethernet0/1" to complete the binding.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.2352redBackNetworksRBN-SMI
1.3.6.1.4.1.2352.2rbnMgmtRBN-SMI
Numeric OIDNameModule
1.3.6.1.4.1.2352.2.17rbnBindMibRBN-BIND-MIB
1.3.6.1.4.1.2352.2.17.1rbnBindMIBObjectsRBN-BIND-MIB
1.3.6.1.4.1.2352.2.17.1.1rbnBindTableRBN-BIND-MIB
1.3.6.1.4.1.2352.2.17.1.1.1rbnBindEntryRBN-BIND-MIB
1.3.6.1.4.1.2352.2.17.1.1.1.3rbnBindNameRBN-BIND-MIB