Use this page to control and configure the DS Agent.
The functionality available on the Agent Configuration page will depend on the rights of the current identity and the version of eDirectory that you are looking at.
Agent Information
Select this option to view the
connection information for your server.
For more information, see Agent Information.
Partitions
Select this option to view the replicas on the
server you are communicating with.
For more information, see Partitions.
Replication Filters
Select this option to view the
replication filters configured for the specified eDirectory agent.
A description of what Filtered Replicas are, why they are used, and how to
configure them is covered in the eDirectory Administration Guide in the Managing
Partitions and Replicas section.
Agent Triggers
Agent triggers allow you to initiate
certain background processes. Most triggers are equivalent to using a SET
DSTRACE=*option command as specified below.
Janitor
On the janitor interval, the following tasks are performed:
- Inherited ACLs are updated
- Synthetic time is checked
- DS Agent credentials are checked and updated if a server rename has occurred.
On the cleaner interval, the janitor will update the status of NCP servers that it knows about, and it will purge expired dynamic bindery entries.
Purger
This trigger purges all entries and attributes whose modification time is less than the current purge time. The purge time is advanced after all servers in a replica ring have seen the given change. This trigger is equivalent to using the SET DSTRACE=*J command.Limber
This trigger checks for tree renames, address changes, and keeps a local cache of information about its own NCP server object up-to-date. This cache is kept because a given NCP server cannot be counted on to contain a replica of its own object. On the limber interval, the cache is kept up-to-date by contacting a real replica containing this server's object. Among other things, this cache contains information about index definitions and predicate statistics settings. Details about errors occurring in the limber process can be found through the Agent Process Status page in iMonitor or by using DS Trace with the limber flag set. This trigger is equivalent to using the SET DSTRACE=*L command.Assume All Servers Up
The DS Agent will put servers that it cannot communicate with into a "bad address" cache. This is done to prevent needlessly slowing down background processes which need to communicate with a server that currently cannot be communicated with. Items in this cache are expired every 30 minutes. Use this trigger to get the DS Agent to assume that all servers it needs to communicate with are up. In other words, using this trigger will clear the bad address cache. This trigger is equivalent to using the SET DSTRACE=*A and SET DSTRACE=*U commands together.Replication
Use this trigger to initiate outbound object synchronization. This trigger is equivalent to using the SET DSTRACE=*H command.Schema Synchronization
Use this trigger to initiate outbound schema synchronization. This trigger is equivalent to using the SET DSTRACE=*SS command.Reference Check
Use this trigger to start the process that maintains and expires backlinks and maintains and updates Dynamic Reference Links (DRLs). This trigger is equivalent to using the SET DSTRACE=*B command.
Background Process Settings
Allows you to modify the
settings for the background processes.
Background Process Settings (minutes)
Allows you to modify the interval at which certain background processes run. These settings are equivalent to using the SET DSTRACE=!option command.Configure Advanced Referral Costing
Allows you to specify whether to enable or disable Advanced Referral Costing (ARC). ARC is enabled by default. You can also run ARC in debug mode. ARC is an improved costing algorithm. Its main purpose is to prevent server outages.Async Outbound Sync Settings (milliseconds)
Allows you to avoid overloading the receiving server during asynchronous replication. The setting depends on your environment. This option is disabled by default. When enabling, try 100 first, and then adjust up or down as needed.Background Process Delay Settings (milliseconds)
Allows you to configure delays into the background process cycles, to prevent the cycles from running too long. Select one of the following policies:
- CPU specifies that delays will occur between any two instances of a background process when the computer is using a certain percentage of its resources. You can also specify the maximum lenght of the delay. These settings apply to all background processes.
- Hard Limit specifies that a delay will always occur between any two instances of a background process. You can set the length of the delay for each individual background process.
Agent Synchronization
Synchronization consists of
outbound and inbound synchronization. If the modifications to a data have to be
synced across server1 and server2, the term outbound refers to the
synchronization process that is sent from server1 to server2. The term inbound
refers to the synchronization process that is received by server1 from
server2
You can set the following parameters:
Inbound Synchronization
You can
enable or disable the Inbound Synchronization for a server. When you disable
this option for a server, the modifications to the data on other servers will
not be synced with this server.
Outbound Synchronization
You
can enable or disable the Outbound Synchronization for a server. When you
disable this option on a server, the modifications to the data on this server
will not be synced with other servers. You can specify the amount of time, in
hours, for which you want the outbound synchronization disabled. The maximum
time is 24 hours. By default, this value is 24 hours. After the specified time
the modifications to the data on this server will be synced with other
servers.
Inline Change Cache
You can enable or disable the Inline Change Cache for a server. You can
disable Inline Change Cache only when Outbound
Synchronization and Priority Sync Outbound is disabled. Enabling Outbound Synchronization
and Priority Sync Outbound will
also enable Inline Change Cache.
Disabling Inline Change Cache will mark the change cache as invalid for this
replica and will be displayed with an invalid flag in Agent Configuration >
Partitions.
Enabling Inline Change Cache will remove the invalid change cache flag once
change cache is rebuilt.
Synchronization Method
Normally, eDirectory will automatically choose the method based on the number of
replicas and replication partners. You can
specify the method of synchronization using any of the following methods:
Partition
Server
Dynamic Adjust
For single server tree, do not select "By Server" synchronization method.
System Computed Synchronization Threads
Specifies whether the system automatically determines the number of threads for outbound
synchronization.
Max. System Computed Synchronization Threads - If you enable System Computed Synchronization Threads, you can specify the maximum number of threads the system uses for outbound synchronization. The supported values are 1 through 16. Ensure your environment can support the value you set.
Max. Manual Setting Synchronization Threads - If you disable System Computed Synchronization Threads, you can manually specify the number of threads you want the system to use for outbound synchronization. The supported values are 1 through max integer (2,147,483,647). Ensure your environment can support the value you set.
Priority Sync Outbound
In
eDirectory 8.8 and later, you can enable or disable the outbound priority
sync. By disabling this option on a server, the modifications to the critical
data on this server will not be synced with other servers through priority sync.
However, the modified data will by synchronized by the normal synchronization
process. Outbound priority sync is enabled by default.
Priority Sync Inbound
In eDirectory 8.8 and later, you can enable or disable
the inbound priority sync. By disabling this option on a server, the
modifications to the critical data on the other servers will not be synced with
this server through priority sync. However, the modified data will by
synchronized by the normal synchronization process. Inbound priority sync is
enabled by default.
Priority Sync
Threads
You can specify the number of threads to be used
for outbound priority sync. The supported values are:
1 (minimum) and up
32 (maximum)By default this value is 4. Depending on the system resources you could give a suitable value.
Priority Sync Queue Size
In eDirectory 8.8 and later, you can specify the queue size for priority sync. This value can vary from 0 to 232 -1. By default, this value is 232 -1.
The value -1 implies unlimited queue size. -1 is 232 - 1. When a negative value is specified, for example, -3, it means -3 = -1-2 which is 232 - 1-2.For more information on priority sync queue size, refer to the eDirectory 9.2 Administration Guide.
Schema Synchronization
Lets you enable or disable inbound and
outbound schema synchronization.
Database Cache
Lets you configure the amount of database
cache used by the DS database engine. Various cache statistics are also provided
to assist you in determining whether you have an appropriate amount of cache
available. Having an inadequate amount of cache may severely impact your
system's performance.
If the database cache settings have not been set by the administrator and made permanent, then the DS Agent will automatically adjust the cache settings. At system startup, the DS Agent will start with a temporary hard limit. Later, after all system services have been given a chance to start up, the DS Agent will switch to dynamic adjust mode.
Login Settings
Allows you to specify whether eDirectory
updates login attributes when users log in. The following options control how
eDirectory responds when a user logs in:
Permanent Setting
Lets you view currently stored instances of
permanent configuration parameters, displays information about permanent
configuration parameters that are supported by this eDirectory agent, and add
new or modify existing permanent configuration parameters.
For more information, see Agent Configuration: Permanent Configuration Parameters.
Clone DIB Set
Use this option to create a complete DIB fileset
duplicate of a tree and all of its objects. The clone can then be placed on
another server. When the destination server initiates DS, it will load the DIB
fileset, contact the master (original) replica of the tree, resolve its name,
then synchronize any changes to the DIB fileset made after the clone was
created.
For more information, see Clone DIB Set.
For information about NetIQ trademarks, see http://www.netiq.com/company/legal/.