All MIBs › CME-MIB › ldapRBSModelCfg
ldapRBSModelCfg
Module: CME-MIB
OID (symbolic): CME-MIB::ldapRBSModelCfg
OID (numeric): 1.3.6.1.4.1.2.3.51.2.4.9.3.6.20
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: There are two mechanisms to authenticate and authorize users on the MM when using an LDAP-enabled server. The first mechanism (oldPermissionString), also known as version 1, uses bitstrings to associate permissions to users and groups. Version1 supports Active Directory, Novell eDirectory, and OPenLDAP based servers. The second mechanism (newRBSModel), also known as version 2, uses a new Role-Based-Security (RBS) model. This mechanism is only available for Active Directory servers, and requires the use of a snap-in that runs on any windows platform. This snap-in tool allows you to configure roles on an Active Directory server of your choice, and to associate users/groups and MMs to those roles. A role identifies the permissions given to users and groups associated with that role, and also identifies the targets (e.g. MM) to which this role is attached. The use of bitstrings in version 2 disappears, making the configuration much more manageable and user-friendly. Note that if you are not using Active Directory, then you should not enable version 2. Also note that before enabling version 2, you should already have your roles configured on your Active Directory server. The old version 1 bitstring model cannot be automatically converted to the new version 2 model. This is why you must configure your users and groups before enabling version 2. Once enabled, the change takes effect immediately. The default value for this field is oldPermissionString.
What is ldapRBSModelCfg?
This writable enum selects which LDAP permission model the MM uses for authenticating and authorizing users: the older bitstring-based model (oldPermissionString, compatible with Active Directory, Novell eDirectory, and OpenLDAP) or the newer role-based model (newRBSModel). It matters because switching models changes how user permissions must be structured on the LDAP server side, so picking the wrong one will lock out users whose permissions were set up for the other scheme. An admin migrating from a legacy bitstring LDAP setup to the newer Enhanced Role Based Security model would set ldapRBSModelCfg to newRBSModel(1) only after the LDAP-side roles have been reconfigured to match.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2.3.51.2.4.9.3.6.20 snmpwalk -v2c -c public <target> CME-MIB::ldapRBSModelCfg
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.2.3.51.2.4.9.3.6.20.1 snmpget -v2c -c public <target> CME-MIB::ldapRBSModelCfg.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.2.3.51.2.4.9.3.6.20.1 i <value>
Start monitoring Cisco Communications Manager Express (CME) router/gateway with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CME-MIB::ldapRBSModelCfg OID value, configure state conditions and alerts, and monitor any Cisco Communications Manager Express (CME) router/gateway from a single console.
OID Breakdown
Upper-level ancestors (14 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.2 | ibm | BLADE-MIB |
| 1.3.6.1.4.1.2.3 | ibmAgents | BLADE-MIB |
| 1.3.6.1.4.1.2.3.51 | netfinitySupportProcessorAgent | BLADE-MIB |
| 1.3.6.1.4.1.2.3.51.2 | bladeCenterSnmpMIB | BLADE-MIB |
| 1.3.6.1.4.1.2.3.51.2.4 | configureSP | BLADE-MIB |
| 1.3.6.1.4.1.2.3.51.2.4.9 | networkConfiguration | BLADE-MIB |
| 1.3.6.1.4.1.2.3.51.2.4.9.3 | tcpProtocols | BLADE-MIB |
| 1.3.6.1.4.1.2.3.51.2.4.9.3.6 | ldapClientCfg | BLADE-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.2.3.51.2.4.9.3.6.20 | ldapRBSModelCfg | CME-MIB |