Cisco Cisco Prime IP Express 8.3 Technical References
atul-support
default = disabled
Enables CCM support for the ATUL query protocol. The atul-port
parameter configures the port number to listen on for ATUL
queries. Changes to this setting take effect on the next server
restart.
parameter configures the port number to listen on for ATUL
queries. Changes to this setting take effect on the next server
restart.
(Local=0, RADIUS=1, Active-Directory=2) default = Local
Sets the external authentication type to be used
0 Local
1 RADIUS
2 Active Directory
Changes to this setting will take effect the next time the product
is restarted.
0 Local
1 RADIUS
2 Active Directory
Changes to this setting will take effect the next time the product
is restarted.
default = 4h
Sets the maximum amount of time CCM will wait for a request
over an incoming SCP connection. If set to 0, there is no
idle timeout and CCM will wait forever.
over an incoming SCP connection. If set to 0, there is no
idle timeout and CCM will wait forever.
default = enabled
If polling for lease history data, this causes CCM to ask for history
detail data when polling DHCP servers, and save the detail data when
it's returned. Changes to this setting will take effect on
the next server restart.
detail data when polling DHCP servers, and save the detail data when
it's returned. Changes to this setting will take effect on
the next server restart.
default = enabled
Specifies that CCM should maintain an index by transaction sequence
number when polling DHCP lease history. This index is used with
Java SDK methods to periodically export lease history data to an
external process, server, or database. When disabled, these Java
methods cannot be used to access lease history data. However, disk
storage needed to maintain the lease history database is reduced.
Changes to this setting will take effect on the next server
restart, and apply only to new lease history records.
number when polling DHCP lease history. This index is used with
Java SDK methods to periodically export lease history data to an
external process, server, or database. When disabled, these Java
methods cannot be used to access lease history data. However, disk
storage needed to maintain the lease history database is reduced.
Changes to this setting will take effect on the next server
restart, and apply only to new lease history records.
(dhcp=2, dns=3) default = dhcp,dns
Indicates the default mode that web UI and CLI clients use for local
edits:
2 dhcp
If set, scope and reservation edits are forwarded to the DHCP
server after being saved to the configuration database. If
unset, a DHCP reload is required before the changes will
take effect.
3 dns
If set, zone and RR edits are forwarded to the DNS server
after being saved to the configuration database. If unset, a
'Zone Distribution Sync' function is required to update the
DNS server; a DNS server reload is also required for zone
changes to take effect.
The default mode is applied only when the client requests the server
default, or does not request a specific edit mode.
edits:
2 dhcp
If set, scope and reservation edits are forwarded to the DHCP
server after being saved to the configuration database. If
unset, a DHCP reload is required before the changes will
take effect.
3 dns
If set, zone and RR edits are forwarded to the DNS server
after being saved to the configuration database. If unset, a
'Zone Distribution Sync' function is required to update the
DNS server; a DNS server reload is also required for zone
changes to take effect.
The default mode is applied only when the client requests the server
default, or does not request a specific edit mode.
(0-1y) default = 4h
This interval specifies how often to collect the lease history
information from all the DHCP servers. If set to 0, polling
is disabled.
information from all the DHCP servers. If set to 0, polling
is disabled.
(0-24h)
Provides a fixed time of day for lease history polling.
This time is interpreted as a time of day offset, with 0 being
12 midnight, provided the polling interval is less than 24 hours,
and the offset value is less than the polling interval. If the offset
value is greater than the polling interval, or the interval is
greater than 24 hours, the offset will be ignored.
The scheduler for polling will ensure that the first polling event
occurs at the offset time. For example, if you set the interval to
4 hours and the offset to 2am, the polling would occur at 2am, 6am,
10am, 2pm, 6pm and 10pm.
This time is interpreted as a time of day offset, with 0 being
12 midnight, provided the polling interval is less than 24 hours,
and the offset value is less than the polling interval. If the offset
value is greater than the polling interval, or the interval is
greater than 24 hours, the offset will be ignored.
The scheduler for polling will ensure that the first polling event
occurs at the offset time. For example, if you set the interval to
4 hours and the offset to 2am, the polling would occur at 2am, 6am,
10am, 2pm, 6pm and 10pm.