<ma-connection>
Stores information about the connection between the management agent and the connected directory. The management agent reports the server that it connected to, in addition to any servers it failed to connect to. The management agent reports error information that can be helpful when you are debugging a problem.
Schema Hierarchy
<run-history>
<run-details>
<step-details>
Syntax
<ma-connection>
<connection-log>
</connection-log>
<server>
</server>
<connection-result>
</connection-result>
</ma-connection>
element
Attributes and Elements
The following sections describe attributes, child elements, and parent elements.
Attributes
None
Child Elements
| Element | Min Occurs | Max Occurs | Description |
|---|---|---|---|
1 |
1 |
Contains a non-localized string that provides the current status of the connection. The possible values are listed in the Remarks section. Note This value should be the same as the <connection-result> for the last <incident> in the <connection-log>. |
|
1 |
1 |
Contains a sequential list of the connection attempts against the servers, including cases where the connectivity dropped. |
|
0 |
1 |
Contains the name of the server that the management agent connected to, if it successfully connected to a server. In most cases, the name is the DNS name. This element must be present, or the user interface will not display the connection log. For management agents where a list of preferred servers can be configured—that is, Active Directory Domain Services (AD DS) or Microsoft Exchange 5.5—the server name that is displayed in this element is informative. The server connection order is not defined in these instances. |
Parent Elements
| Element | Description |
|---|---|
Stores run information about one step of the management agent run. |
Remarks
The <ma-connection> element can appear for both import and export runs for call-based management agents. The following table lists the possible values for the <connection-result> element.
| Value | Description |
|---|---|
successful-connection |
Successful connection to the connected directory. |
failed-connection |
Connection to the connected directory failed for a reason other than authentication. Generally, the connected directory error element is present to help troubleshoot. |
dropped-connection |
The connection between the management agent and the connected directory no longer exists. In many cases, the management agent tries to reconnect to the connected directory. Generally, the connected directory error element is present to help troubleshoot. |
failed-authentication |
Authentication is not possible using the supplied credentials. |
failed-permission |
Insufficient rights to access a container in the connected directory. This error is only expected for Lightweight Directory Access Protocol (LDAP) management agents that search different connected directory containers. Generally the connected directory error element is present to assist in troubleshooting, and the error literal indicates the name of the container in which the problem occurred. |
failed-search |
A container or table search failed with an unexpected error. Generally, the connected directory error element is present to assist in troubleshooting, and the error literal indicates the name of the container it had trouble searching. |
warning-no-watermark |
The management agent cannot read the watermark when doing a full import. This error is expected only for the management agent for Sun ONE Directory Server 5.1 (formerly iPlanet Directory Server), when the initial management agent configuration was completed when the connected directory had change log enabled. Later when the connected directory change log is turned off, if the management agent configuration is not updated, this warning occurs when a full import is done. |
Example
The following example shows a pseudo <ma-connection> section.
<ma-connection>
<connection-result>a string from documented list</connection-result>
<server> name of server </server>
<connection-log>
<incident>
<connection-result> string from list </connection-result>
<date> yyyy-mm-dd hh:mm:ss </date>
<server> name of server </server>
<cd-error>
<error-code> some MA-specific number</error-code>
<error-literal>some literal</error-literal>
<entity type="hellip"/>
</cd-error>
</incident>
<incident>
<type> connection-attempt|connection-dropped </type>
<connection-result> string from list </connection-result>
<date> yyyy-mm-dd hh:mm:ss </date>
<server> name of server </server>
<cd-error>
<error-code> some MA-specific number</error-code>
<error-literal>some literal</error-literal>
<entity type="hellip"/>
</cd-error>
</incident>
<entity type="hellip"/>
</connection-log>
<ma-connection>