Технические ссылки для Cisco Cisco Prime IP Express 8.3
Lists the RSOO-enabled options that server will process, if
provided by a relay and no option is otherwise available. See
RFC 6422 for more details on RSOO (Relay Supplied Options Option).
This attribute has special handling during the policy hierarchy
processing when checking the Prefix policies (embedded or named)
for the Prefixes on a Link. The Prefixes for the Link are
processed in alphabetic (case blind) order. For each Prefix, the
embedded and then named policy are checked. Only Prefixes to which
the client has access (based on selection tags, etc.) are checked.
provided by a relay and no option is otherwise available. See
RFC 6422 for more details on RSOO (Relay Supplied Options Option).
This attribute has special handling during the policy hierarchy
processing when checking the Prefix policies (embedded or named)
for the Prefixes on a Link. The Prefixes for the Link are
processed in alphabetic (case blind) order. For each Prefix, the
embedded and then named policy are checked. Only Prefixes to which
the client has access (based on selection tags, etc.) are checked.
default = 2w
Assigns the default and maximum valid lifetime for leases to
DHCPv6 client interfaces. Expressed in seconds and relative
to the time the server sent the packet, this attribute sets
the length of time that an address remains valid. When this
period of time expires, the address becomes invalid and
unusable. The valid lifetime must be greater than or equal
to the preferred lifetime.
Note: For IA_TA's, the min-valid-lifetime is used as the
default, if configured.
DHCPv6 client interfaces. Expressed in seconds and relative
to the time the server sent the packet, this attribute sets
the length of time that an address remains valid. When this
period of time expires, the address becomes invalid and
unusable. The valid lifetime must be greater than or equal
to the preferred lifetime.
Note: For IA_TA's, the min-valid-lifetime is used as the
default, if configured.
Designates the optional view associated with zones used for DNS
update that overrides the view-id configuration in forward
(reverse) DNS Update configuration object.
update that overrides the view-id configuration in forward
(reverse) DNS Update configuration object.
cluster
cluster - Configures the local and remote clusters
Synopsis
cluster <name> create <address> [<attribute>=<value>]
cluster <name> delete
cluster list
cluster listnames
cluster listbrief
cluster <name> show
cluster <name> set <attribute>=<value> [<attribute>=<value> ...]
cluster <name> get <attribute>
cluster <name> unset <attribute>
cluster <name> delete
cluster list
cluster listnames
cluster listbrief
cluster <name> show
cluster <name> set <attribute>=<value> [<attribute>=<value> ...]
cluster <name> get <attribute>
cluster <name> unset <attribute>
cluster <name> enable <attribute>
cluster <name> disable <attribute>
cluster <name> disable <attribute>
cluster <name> activate
cluster <name> deactivate
cluster <name> resynchronize
cluster <name> sync
cluster <name> updateReplicaData
cluster <name> removeReplicaData
cluster <name> recoverData
cluster <name> pollLeaseHistory
cluster <name> getLeaseHistoryState
cluster <name> pollSubnetUtilization
cluster <name> deactivate
cluster <name> resynchronize
cluster <name> sync
cluster <name> updateReplicaData
cluster <name> removeReplicaData
cluster <name> recoverData
cluster <name> pollLeaseHistory
cluster <name> getLeaseHistoryState
cluster <name> pollSubnetUtilization
Description
The cluster command configures the specified local or remote
cluster, primarily providing connection and polling information;
for example, IP address, fully qualified domain name, and HTTP port.
This information provides reference points for objects related to
the cluster.
The activate, deactivate, resynchronize, sync, updateReplicaData,
removeReplicaData, recoverData, pollLeaseHistory,
getLeaseHistoryState, and pollSubnetUtilization are only available
when connected to a regional cluster.
cluster, primarily providing connection and polling information;
for example, IP address, fully qualified domain name, and HTTP port.
This information provides reference points for objects related to
the cluster.
The activate, deactivate, resynchronize, sync, updateReplicaData,
removeReplicaData, recoverData, pollLeaseHistory,
getLeaseHistoryState, and pollSubnetUtilization are only available
when connected to a regional cluster.
Examples