Use the information in the following tables to learn about all possible LDAP alerts in detail that are raised by Fault Management.
31030 | LDAP Connectivity Failure |
---|---|
Description | Send an alert when LDAP server in XCO is not reachable |
Preconditions |
The polling is enabled only if:
|
Requirements | Alert shows the following data:
The following example shows an alert when an LDAP server is not
reachable:
<114>1 2003-10-11T22:14:15.003Z xco.machine.com FaultManager - - [meta sequenceId=”47”] [origin ip=”10.20.30.40” enterpriseId=”1916” software=”XCO” swVersion=”3.3.0”] [alert@1916 resource=”/App/System/Security/Authentication?server=10.1.2.3” alertId=”31030” cause=”underlyingResourceUnavailable” type=”communicationsAlarm” severity=”major”] [alertData@1916 server=”10.1.2.3” name=”ldap1” error=”failed to connect to the LDAP server with the given credentials”] BOMLDAP connectivity check failed for the server ‘10.x.x.x‘ configured with the name ‘ldap1‘ due to ‘failed to connect to the LDAP server with the given credentials. |
Health Response |
Response
{ Resource: /App/System/Security/Authentication?server=10.1.2.3 HQI { Color: Red Value: 3 } StatusText: LDAP connectivity check failed for the server ‘10.1.2.3‘ configured with the name ‘ldap1‘ due to ‘failed to connect to the LDAP server with the given credentials. } |
31031 | LDAP Server Connectivity Success |
---|---|
Description | Send an alert when LDAP server configured in XCO is reachable. |
Preconditions |
The polling is enabled only if:
|
Requirements | Alert shows the following data:
The following example shows an alert when an LDAP server is
reachable:
<118>1 2003-10-11T22:14:15.003Z xco.machine.com FaultManager - - [meta sequenceId=”47”] [origin ip=”10.20.30.40” enterpriseId=”1916” software=”XCO” swVersion=”3.3.0”] [alert@1916 resource=”/App/System/Security/Authentication?server=10.1.2.3” alertId=”31031” cause=”connectionEstablished” type=”communicationsAlarm” severity=”info”] [alertData@1916 server=”10.1.2.3” name=”ldap1”] BOMLDAP connectivity check success for the server ‘10.1.2.3‘ configured with the name ‘ldap1‘. |
Health Response |
Response
{ Resource: /App/System/Security/Authentication?server=10.1.2.3 HQI { Color: Green Value: 0 } StatusText: LDAP connectivity check success for the server ‘10.1.2.3‘ configured with the name ‘ldap1‘. } |
31032 | LDAP Server Configuration Removed |
---|---|
Description | Send an alert when LDAP server configuration is removed |
Preconditions |
The polling is enabled only if:
|
Requirements | Alert shows the following data:
The following example shows an alert when an LDAP server is
removed:
<118>1 2003-10-11T22:14:15.003Z xco.machine.com FaultManager - - [meta sequenceId=”47”] [origin ip=”10.20.30.40” enterpriseId=”1916” software=”XCO” swVersion=”3.3.0”] [alert@1916 resource=”/App/System/Security/Authentication?server=10.1.2.3” alertId=”31032” cause=”configRemoved” type=”communicationsAlarm” severity=”info”] [alertData@1916 server=”10.1.2.3” name=”ldap1”] BOMLDAP ‘ldap1‘ with server ip ‘10.1.2.3‘ removed |
Health Response |
Response
{ Resource: /App/System/Security/Authentication?server=10.1.2.3 HQI { Color: Green Value: 0 } StatusText: LDAP ‘ldap1‘ with server ip ‘10.1.2.3‘ removed. } |