Cisco CNS Network Registrar 6.1, base license and kit, all platforms, 1000 IP nodes CNR-6.1-BASE1K Manual De Usuario
Los códigos de productos
CNR-6.1-BASE1K
Cisco Systems, Inc.
All contents are Copyright © 1992–2004 Cisco Systems, Inc. All rights reserved. Important Notices and Privacy Statement.
Page 2 of 5
the Web interface, the administrator can also pull subnet usage and IP lease history data from the local clusters. The Single Sign-On feature
allows the administrator to traverse the local clusters without reauthentication.
•
The Router Interface Configuration (RIC) server manages the router interfaces on Cisco uBR7246VXR Universal Broadband Router and
Cisco uBR10012 Universal Broadband Router. An administrator can view, retrieve, and modify the router description; address of the
primary subnet on the interface; address of the secondary subnet on the interface; IP helper; and address of cable helper, owner, and region
where the router is deployed. As changes are made to the router over time, the RIC server will synchronize with the router to incorporate
these changes. Communication to the router can be done via Telnet or Secure Shell (SSH) Protocol. With the RIC server, Cisco CNS
Network Registrar delivers a centralized-management approach to help administrators achieve high productivity through integrated,
systemic manageability.
•
Users now have the option to have leases allocated by priority or by first available. With priority allocation, each scope is assigned a priority
and leases are handed out from scopes with the higher priority until the addresses in all the scopes are exhausted. If first available is
selected, Cisco CNS Network Registrar hands out the address that is first available. The two new DHCP-allocation options give the
administrator the flexibility to implement a more deterministic address-allocation strategy.
•
The IP lease-history feature has been enhanced in Cisco CNS Network Registrar 6.1 to significantly improve server performance when this
feature is enabled. This feature intelligently provides an audit mechanism in Cisco CNS Network Registrar while delivering the high
performance and scalability required for handling large networks.
•
To continue support for securing data and operations, Cisco CNS Network Registrar 6.1 allows users to restrict DNS zone transfers based on
Transaction Signature. With Transaction Signature enabled, users can verify dynamic DNS-update and zone-transfer requests and responses
to come from an authorized source.
•
To prevent unauthorized query, the restricted-query ACLs feature allows the administrator to constraint clients to querying only certain
servers based on the source IP address or source network address.
•
Several counters are added in Cisco CNS Network Registrar 6.1 to provide more detailed performance measurements for the DNS server.
These counters provide more information other than a value between 1 and 10 when gauging the health of the DNS server and can
potentially assist with identifying areas in the DNS servers that can be reconfigured to deliver a better throughput.
•
New administrative roles are added to Cisco CNS Network Registrar 6.1 to enable Web-based administration for the new features and
capabilities.
UPGRADE PATHS
Existing Cisco CNS Network Registrar customers currently can upgrade to the Cisco CNS Network Registrar 6.1 local cluster, which is
functionally equivalent to the Cisco CNS Network Registrar server of previous releases. When migrating to release 6.1, customers can use a
utility available with Cisco CNS Network Registrar that can import information from the current Cisco CNS Network Registrar database to
make Cisco CNS Network Registrar 6.1 operational in a short time.
Customers with an active Software Application Support plus Upgrades (SASU) can request a new local cluster license and a product kit at no
cost through the Product Upgrade Tool available at
When accessing this tool, customers need
to provide the SASU contract number and then request the Cisco CNS Network Registrar 6.1 upgrade kits, which will be shipped from
manufacturing in 5 to 10 days after receipt of the request. Because release 6.1 contains some new optional features that are not covered by the
SASU entitlements, customers need to purchase these optional features separately via additional product licenses.