RBN-BIND-MIB
File:
RBN-BIND-MIB.mib (22351 bytes)
Imported modules
Imported symbols
Defined Types
| RbnBindType |
|
| The binding type. The comment after the enumeration
label is the equivalent CLI command that would config
the corresponding bind type. |
| TEXTUAL-CONVENTION |
|
|
|
| |
INTEGER |
unbound(1), authBind(2), bypassBind(3), interfaceBind(4), subscriberBind(5), l2tptunnelBind(6), sessionBind(7), dot1qBind(8), multiIntfBind(9), multiSubBind(10), multiClipsBind(11) |
|
| RbnBindEntry |
|
| SEQUENCE |
|
|
|
| |
rbnBindCircuit |
RbnCircuitHandle |
|
| |
rbnBindType |
RbnBindType |
|
| |
rbnBindName |
SnmpAdminString |
|
| |
rbnBindPassword |
SnmpAdminString |
|
| |
rbnBindContext |
SnmpAdminString |
|
| |
rbnBindAuthContext |
SnmpAdminString |
|
| |
rbnBindServiceGrp |
SnmpAdminString |
|
| |
rbnBindAcl |
SnmpAdminString |
|
| |
rbnBindAuthChap |
TruthValue |
|
| |
rbnBindAuthPap |
TruthValue |
|
| |
rbnBindAuthWait |
TruthValue |
|
| |
rbnBindAuthPapFirst |
TruthValue |
|
| |
rbnBindMaxSessions |
Unsigned32 |
|
| |
rbnBindPvcSlot |
RbnSlot |
|
| |
rbnBindPvcPort |
RbnPort |
|
| |
rbnBindVpn |
Unsigned32 |
|
| |
rbnBindAuthDhcp |
TruthValue |
|
Defined Values
| rbnBindMib |
1.3.6.1.4.1.2352.2.17 |
| Defines the objects necessary to support binding
circuits to interfaces. |
| MODULE-IDENTITY |
|
|
|
| rbnBindTable |
1.3.6.1.4.1.2352.2.17.1.1 |
| 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. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
RbnBindEntry |
|
| rbnBindEntry |
1.3.6.1.4.1.2352.2.17.1.1.1 |
| A conceptual row in the rbnBindTable. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
RbnBindEntry |
|
|
| rbnBindCircuit |
1.3.6.1.4.1.2352.2.17.1.1.1.1 |
| 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. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
RbnCircuitHandle |
|
|
| rbnBindType |
1.3.6.1.4.1.2352.2.17.1.1.1.2 |
| 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. |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
RbnBindType |
|
|
| rbnBindName |
1.3.6.1.4.1.2352.2.17.1.1.1.3 |
| 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. |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
SnmpAdminString |
Size(1..192) |
|
| rbnBindPassword |
1.3.6.1.4.1.2352.2.17.1.1.1.4 |
| 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. |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
SnmpAdminString |
Size(1..64) |
|
| rbnBindContext |
1.3.6.1.4.1.2352.2.17.1.1.1.5 |
| 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. |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
SnmpAdminString |
Size(1..64) |
|
| rbnBindAuthContext |
1.3.6.1.4.1.2352.2.17.1.1.1.6 |
| 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. |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
SnmpAdminString |
Size(1..64) |
|
| rbnBindServiceGrp |
1.3.6.1.4.1.2352.2.17.1.1.1.7 |
| 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. |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
SnmpAdminString |
Size(1..64) |
|
| rbnBindAcl |
1.3.6.1.4.1.2352.2.17.1.1.1.8 |
| 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. |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
SnmpAdminString |
Size(1..64) |
|
| rbnBindAuthChap |
1.3.6.1.4.1.2352.2.17.1.1.1.9 |
| 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. |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
TruthValue |
|
|
| rbnBindAuthPap |
1.3.6.1.4.1.2352.2.17.1.1.1.10 |
| 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. |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
TruthValue |
|
|
| rbnBindAuthWait |
1.3.6.1.4.1.2352.2.17.1.1.1.11 |
| 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. |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
TruthValue |
|
|
| rbnBindAuthPapFirst |
1.3.6.1.4.1.2352.2.17.1.1.1.12 |
| 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. |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
TruthValue |
|
|
| rbnBindMaxSessions |
1.3.6.1.4.1.2352.2.17.1.1.1.13 |
| 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 |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
1..65535 |
|
| rbnBindPvcSlot |
1.3.6.1.4.1.2352.2.17.1.1.1.14 |
| 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. |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
RbnSlot |
|
|
| rbnBindPvcPort |
1.3.6.1.4.1.2352.2.17.1.1.1.15 |
| 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. |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
RbnPort |
|
|
| rbnBindVpn |
1.3.6.1.4.1.2352.2.17.1.1.1.16 |
| 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. |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
2..4094 |
|
| rbnBindAuthDhcp |
1.3.6.1.4.1.2352.2.17.1.1.1.17 |
| 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. |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
TruthValue |
|
|
| 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. |
| Status: deprecated |
Access: read-create |
| MODULE-COMPLIANCE |
|
|
|
| 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. |
| Status: current |
Access: read-create |
| MODULE-COMPLIANCE |
|
|
|
| rbnBindConfigGroup |
1.3.6.1.4.1.2352.2.17.2.2.1 |
| The collection of all objects applicable for all values of
rbnBindType. |
| Status: deprecated |
Access: read-create |
| OBJECT-GROUP |
|
|
|
| rbnBindConfigGroup2 |
1.3.6.1.4.1.2352.2.17.2.2.2 |
| The collection of all objects applicable for all values of
rbnBindType. |
| Status: current |
Access: read-create |
| OBJECT-GROUP |
|
|
|