LDAP Virtual Schema

The LDAP interface uses the virtual schema illustrated in Figure 194—Figure 199 to represent the structure of the Steel-Belted Radius Carrier database. LDAP clients use the virtual schema to exchange configuration data over the LDAP configuration interface.

Many of the top-level items in the LDAP virtual schema correspond to pages in the WEb GUI, as shown in Table 60.

Table 60: LDAP Schema and Web GUI Dialogs

Item	See
`radiusclass=client`	Administering RADIUS Clients and Client Groups
`radiusclass=ClientGroup`	Administering RADIUS Location Groups
`radiusclass=native-user, …`	Administering Users
`radiusclass=profile`	Administering Profiles
`radiusclass=proxy`	Administering Proxy RADIUS
`radiusclass=tunnel`	Administering RADIUS Tunnels
`radiusclass=server`	Setting Up EAP Methods
`radiusclass=ip-addr-pool`	Administering Address Pools
`radiusstatus=statistics`	Displaying Statistics
`radiusstatus=sessions`	Current Sessions Overview Note: LDAP searches that call `radiusstatus=sessions` can adversely affect Steel-Belted Radius Carrier performance. When possible, search using the `sessions_by` keywords. New attributes can be added by updating the session table.
`radiusstatus=sessions_by_mobile_session`	You can use the LCI to locate a session by its mobile session identifier (the concatenation of the values of the `User-Name` and `3GPP-NSAPI` attributes included in authentication and accounting requests). Use the `radiusstatus=sessions_by_mobile_session` node to specify a filter of `mobile-session-id=session_id` to locate a specific mobile session. You can also use this part of the schema to delete sessions.

Note

radiusstatus items can be read, but they cannot be modified.

Note

Figure 196 and Figure 198 incorrectly list Tribe as an available attribute for session queries. This attribute is not supported in the LDAP schema.

Note

The radiusclass=ip-addr-pool applies only to the standalone version and not to the cluster.