Cisco Cisco Prime Network Registrar 8.3 Release Notes
7
Cisco Prime Network Registrar 8.3 Release Notes
Limitations and Restrictions
Web UI Enhancements
Cisco Prime Network Registrar 8.3 supports a new web UI with improved usability that supports.
Enhanced display of attribute groups.
Customer display using widgets for special attributes.
The web UI enhancements in Cisco Prime Network Registrar 8.3 provide improved look and feel which is consistent with
the Cisco Prime suit of products.
the Cisco Prime suit of products.
External Authentication using Active Directory
Cisco Prime Network Registrar 8.3 supports authentication of users against Microsoft Active Directory.
Existing AD user accounts can be used to log into the Cisco Prime Network Registrar webUI/CLI/SDK local and regional
clusters by adding the user to the Cisco Prime Network Registrar access privileged group.
clusters by adding the user to the Cisco Prime Network Registrar access privileged group.
Cisco Prime Network Registrar CCM server uses Kerberos, LDAPv3, and DNS to provide secure, centralized
authentication for the identified users in AD and to determine if an authenticated user is authorized to access Cisco Prime
Network Registrar.
authentication for the identified users in AD and to determine if an authenticated user is authorized to access Cisco Prime
Network Registrar.
BYOD Support
Bring your own device (BYOD) support in Cisco Prime Network Registrar 8.3 is to permit users to use a personal mobile
devices for the business communications in a secured way. The advantage of BYOD support is that it supports hands-off,
user-driven configuration of device with correct IP Addresses and network settings.
devices for the business communications in a secured way. The advantage of BYOD support is that it supports hands-off,
user-driven configuration of device with correct IP Addresses and network settings.
When a BYOD device connects to the network for the first time, the user is redirected to the BYOD self-registration web
page to register the device. The web portal registration page populates the device details and prompts the user to
authenticate against the active directory server. Upon successful authentication, the device is registered with the DHCP
server. The BYOD registration portal is tightly integrated with DHCP, CDNS of Cisco Prime Network Registrar.
page to register the device. The web portal registration page populates the device details and prompts the user to
authenticate against the active directory server. Upon successful authentication, the device is registered with the DHCP
server. The BYOD registration portal is tightly integrated with DHCP, CDNS of Cisco Prime Network Registrar.
To support BYOD feature in Cisco Prime Network Registrar 8.3, the DHCP server and CDNS server (changes are required
in backup, if DHCP failover pairs is configured) needs to be configured with specific attributes.
in backup, if DHCP failover pairs is configured) needs to be configured with specific attributes.
Limitations and Restrictions
This section describes limitations and restrictions you might encounter while using Cisco Prime Network Registrar 8.3.
The Regional Pull Replica Address Space fails when reservations are being pulled for new failover-pair objects. This
problem occurs only if there is a new failover-pair and one or more reservations associated with that failover-pair.
problem occurs only if there is a new failover-pair and one or more reservations associated with that failover-pair.
To work around this issue, repeat the operation twice—first checking Omit Reservations and then without checking
Omit Reservations. After the failover-pairs have been pulled, subsequent pull replica address space operations will
work correctly.
Omit Reservations. After the failover-pairs have been pulled, subsequent pull replica address space operations will
work correctly.
In situations where a DHCPv6 server supports clients with multiple leases, the demand on server memory increases.
DHCPv4 supports only one lease per client, while DHCPv6 supports multiple leases. Therefore, a server running
DHCPv6 cannot support as many leases (clients) as the same server running DHCPv4. For example, one DHCPv6
client might require 2,500 bytes of space compared to 1,000 bytes per DHCPv4 client. This means that a machine
that would support one million DHCPv4 clients supports only 400,000 DHCPv6 clients. We recommend that you
allow three times the memory for DHCPv6 clients as you would for DHCPv4.
DHCPv4 supports only one lease per client, while DHCPv6 supports multiple leases. Therefore, a server running
DHCPv6 cannot support as many leases (clients) as the same server running DHCPv4. For example, one DHCPv6
client might require 2,500 bytes of space compared to 1,000 bytes per DHCPv4 client. This means that a machine
that would support one million DHCPv4 clients supports only 400,000 DHCPv6 clients. We recommend that you
allow three times the memory for DHCPv6 clients as you would for DHCPv4.
You must: