Cisco Cisco Network Registrar 7.2 Notas de publicación

CLI—Runs in a Windows, Solaris, or Linux command window.

For the CLI, the number of concurrent active user sessions and processes on a cluster can be 
no more than 14.

Include a network time service (such as NTP) in your configuration to avoid time differences between 
the local and regional clusters, so that aggregated data appears consistently at the regional server.

Cisco Network Registrar no longer supports Windows Server 2003, Red Hat 4.0, and Solaris 8 and 9. If 
you are running any of these operating systems, you must upgrade to Windows Server 2008, Red Hat 
5.0, or Solaris 10, as appropriate, before you install or upgrade to Cisco Network Registrar 7.2.2. (See 
the 

Cisco Network Registrar 7.2.2 protocol servers interoperate with versions 7.2.x, 7.1.x, 7.0.x, and 6.3.x. 
Cisco Network Registrar 7.2.2 will not support interoperability with the versions before 6.3.x.

Cisco Network Registrar 7.2.2 DHCPv4 failover servers interoperate with Cisco Network Registrar 
7.2.x, 7.1.x, 7.0.x, and 6.3.x failover servers.

OS version

1

1.

Cisco Network Registrar must run on 32-bit or 64-bit operating systems.

Solaris 10

2

2.

Cisco Network Registrar supports 128-KB block sizes in the Solaris 10 ZFS.

Red Hat Enterprise Linux 5.0

3

3.

Cisco Network Registrar now supports running in VMWARE (ESX 4.1 and 4.0) environment.

Windows Server 2008

Disk space

4

4.

Higher I/O bandwidth usually results in higher average leases per second.

2 x 73/146 SAS

5

 drives

5.

Serial Attached SCSI.

With basic DHCP and optimal hardware configuration:

SATA

6

 drives with 7500 RPM drive greater than 500 

leases/second

SAS drives with 15K RPM drive greater than 1000 
leases/second

(Recommended hard drive 146 GB)

6.

Serial Advanced Technology Attachment (Serial ATA).

Memory

7

7.

Faster CPU and more memory typically result in higher peak leases per second.

16 GB

4 GB (small networks), 8 GB (average networks), or 
16 GB (large networks)