ccm (nrcmd)						ccm (nrcmd)


NAME
    ccm - Configures and controls the CCM server

SYNOPSIS    
    ccm get <attribute>
    ccm set <attribute>=<value> [<attribute>=<value> ...]
    ccm unset <attribute>
    ccm show

DESCRIPTION
   The ccm command manages the CCM server in the cluster. 

EXAMPLES

STATUS

SEE ALSO
    server

PROPERTIES
  Attributes:

    atul-port[37] (AT_RANGEINT(1-65535), Optional, default: 7543)
        Enables the CCM server to listen for incoming ATUL queries
        on this UDP port. This attribute is used only by the
        regional CCM server. Changes to this setting take effect
        on the next server restart.

    atul-support[38] (AT_BOOL, Optional, 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.

    lease-hist-detail[30] (AT_BOOL, Optional, default: true)
        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.

    local-zone-edit-mode[40] (AT_ENUMINT(), Optional, default: synchronous)
        Indicates the efault mode that local clients should use for DNS
        updates.
        This default mode is overridden if a mode is specified in a given CCM
        SCP message (in other words, by specific client request).  If
        unset, clients should always present the choice of mode to the user.

    poll-lease-hist-interval[11] (AT_RANGETIME, Optional, 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.

    poll-lease-hist-offset[22] (AT_RANGETIME, Optional, default: <none>)
        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.

    poll-lease-hist-retry[12] (AT_RANGEINT(0-4), Optional, default: 1)
        The number of retries for a given polling interval, if polling fails.

    poll-replica-interval[35] (AT_RANGETIME, Optional, default: 4h)
        This interval specifies the default value of how often to poll
        for configuration changes when replicating data from a local cluster.

    poll-replica-offset[36] (AT_RANGETIME, Optional, default: 0)
        Provides a fixed time of day for replica 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.

    poll-subnet-util-interval[1] (AT_RANGETIME, Optional, default: 4h)
        This interval specifies how often to collect subnet
        utilization from all the DHCP servers. If set to 0, polling
        is disabled.

    poll-subnet-util-offset[23] (AT_RANGETIME, Optional, default: <none>)
        Provides a fixed time of day for subnet utilization 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.

    poll-subnet-util-retry[2] (AT_RANGEINT(0-4), Optional, default: 1)
        The number of retries for a given polling interval, if polling fails.

    poller-event-threads[21] (AT_RANGEINT(1-5), Optional, default: 2)
        This specifies how many threads that the poller will create.
        Changes to this setting will take effect on the next server restart.

    regional-zone-edit-mode[39] (AT_ENUMINT(), Optional, default: staged)
        Indicates the default mode that regional clients should use
        for DNS updates.
        This default mode is overridden if a mode is specified in a given CCM
        SCP message (in other words, by specific client request).  If
        unset, clients should always present the choice of mode to the user.

    scope-edit-mode[45] (AT_ENUMINT(), Optional, default: staged)
        Indicates the default mode that web UI and CLI clients use
        for DHCP edits:
            1  staged
               Edits are written to the database but are not immediately
               forwarded to the DHCP server; that is, they remain
               unpublished by DHCP.
            2  synchronous
               Edits are written to the database and are immediately
               forwarded for publishing to the DHCP server.

    trim-changeset-age[42] (AT_RANGETIME, Optional, default: 1y)
        Sets the minimum age for a change log entry to be eligible
        for trimming.

    trim-lease-hist-age[14] (AT_RANGETIME, Optional, default: 24w)
        The minimum length of time that we will keep a lease history record in
        the lease history database.  Any lease history record older than this
        time will be deleted when the next lease history database trimming
        operation occurs.
        If set to 0, all lease history data will be trimmed. Changes to this
        setting will take effect on the next server restart.

    trim-lease-hist-interval[13] (AT_RANGETIME, Optional, default: 24h)
        This interval specifies how often to trim the old lease history data.
        If set to 0 no automatic lease history trimming occurs.
        If lease history collection and polling are enabled and this parameter
        is set to 0, the lease history database will continue to grow without
        bound. Changes to this setting will take effect on the next server
        restart.

    trim-subnet-util-age[4] (AT_RANGETIME, Optional, default: 24w)
        The age that we will allow a subnet-util trimming element to be before
        deciding to delete that element. If this value is set to zero, we will
        not consider the record age when trimming. Changes to this setting
        will take effect on the next server restart.

    trim-subnet-util-interval[3] (AT_RANGETIME, Optional, default: 24h)
        This interval specifies how often to trim the old subnet utilization
        data. If set to 0 no automatic subnet utilization trimming occurs.
        Changes to this setting will take effect on the next server restart.

    webui-mode[51] (AT_ENUMINT(), Optional, default: Basic)
        Sets the mode for the web UI at session startup:
            0  basic
            1  advanced
            2  expert

