ldap-agent

Displays an LDAP agent‘s join status (join status to a LDAP server domain). Use this command When LDAP is specified the external resource (as opposed to local RADIUS resources) to validate PEAP-MS-CHAP v2 authentication requests, user credentials, and password information needs to be made available locally to successfully connect to the external LDAP server. Up to two LDAP Agents (primary and secondary external resources) can be defined as external resources for PEAP-MS-CHAP v2 authentication requests.

Note

This command is not available in USER EXECUTABLE ,mode

Supported on the following devices:

Access Points: AP3000/X, AP5010, AP310i/e, AP410i/e, AP505i, AP510i, AP510e, AP560i, AP6522, AP6562, AP7161, AP7502, AP7522, AP7532, AP7562, AP7602, AP7612, AP7622, AP763, AP7662, AP8163, AP8543, AP8533.
Service Platforms: NX5500, NX7500, NX9500, NX9600
Virtual Platforms: CX9000, VX9000

Syntax

show ldap-agent join-status {on <DEVICE-NAME>}

Parameters


ldap-agent	Displays LDAP agent related configuration
join-status	Displays if the LDAP agent has successfully joined a LDAP server‘s domain
on <DEVICE-NAME>	Optional. Displays if the LDAP agent has successfully joined a specified LDAP server‘s domain. <DEVICE-NAME> – Specify the name of the device running the LDAP server (access point, wireless controller, or service platform).

Examples

nx9500-6C8809#show ldap-agent join-status
Primary LDAP Server's agent join-status : Joined domain TEST.

Secondary LDAP Server's agent join-status : Not Configured
nx9500-6C8809#