Discovering Your Enterprise › Discovering IPv6 Network Devices using Common Discovery › Using Common Discovery GUI › Set Discovery Server Options › Discovery Server Options

Discovery Server Options

To set discovery server options, the following information is required:

IPv6 Display Format

Specifies the IPv6 address display format.

Scan history deletion frequency (in days)

Specifies the retention period of scan history.

Log Destinations

(Optional) Defines the destination where you want to route the log data. You can route the log data to the following options:

• eTrust Audit agent
• Event Management node
• System event log

Note: If you route the log data to a remote machine, ensure that the remote machine has the Enterprise Common Services (ECS) installed and running.

Trusted Servers

Configures a list of CA Common Discovery servers. You must configure the discovery server’s options so that both the servers are listed in each others Trusted Servers list to share information.

Subnet Hierarchy

Configures subnet hierarchy. The IPv6 protocol gives network administrators the ability to define subnet hierarchy in their IPv6 networks. The following parameters can be used to define a subnet hierarchy:

Global Routing Prefix Length

Determines the number of bits in IPv6 address that precede the subnetID.

Bits Per Level

Associates bits in the subnetID with subnet levels in an IPv6 subnet hierarchy.

Note: The bits are left justified. The first subnet level comprises the leftmost n bits of the subnetID. There is a corresponding filter in scan policies that lets you use these bits to filter scan requests.

Subnet hierarchy configuration is adjusted only if scan policies do not use it. The policies that leverage the current subnet hierarchy configuration are listed on the right hand side. You can use the Scan tab to review and edit the subnet hierarchy filters individually. You can click Disable Filters to remove the subnet hierarchy filters for all listed policies.

To set global scan options, the following information is required:

Global SNMP Community Names

Controls the SNMP community names list globally for your discovery server. You can avoid adding community names when you define scan policy by adding enterprise-wide SNMP community names in the list. For better performance, keep the community names list small or the discovery agent could incur overhead when attempting to connect to SNMP enabled devices.

Note: Global exclusion criteria and SNMP community name values are appended to the scan policy at the time it is run.

Global Exclude IP Addresses

Sets global exclusion criteria for all scans.

More information:

Set Discovery Server Options