Cisco Cisco Prime IP Express 8.3

ページ / 8
6
Cisco Prime IP Express 8.3.3 Release Notes
 
Important Notes
Using the Bug Search Tool
Use the Bug Search tool to search for a specific bug or to search for all bugs in a release.
1.
.
2.
At the Log In screen, enter your registered Cisco.com username and password; then, click Log In. The Bug Search 
page opens.
Note: 
If you do not have a Cisco.com username and password, you can register for them at 
.
3.
To search for a specific bug, enter the bug ID in the Search For field and press Return.
4.
To search for bugs in the current release:
a.
Click the Search Bugs tab and specify the following criteria:
b.
In the Search For field, enter Prime IP Express or Prime Network Registrar 8.3.3 and press Return. (Leave the 
other fields empty.)
c.
When the search results are displayed, use the filter tools to find the types of bugs you are looking for. You can 
search for bugs by status, severity, modified date, and so forth.
Note: 
To export the results to a spreadsheet, click the Export All to Spreadsheet link.
Important Notes
This section contains the important information related to this software release and information in response to recent 
customer queries. It describes:
RFC 3597 Standard for Unknown RR Types and Classes
Earlier, Cisco Prime IP Express was not compliant with RFC 3597 naming of unknown RR types and classes. These issues 
have been corrected in Cisco Prime IP Express 8.3.3 release:
The CLI zone addRR command implied it supported a class argument, which indicates, it supported the 'standard' 
DNS classes. However, it was only supporting the IN class. In Cisco Prime IP Express 8.3.3, the addRR command 
help has been modified to show that it supports only IN class.
zone <name> addRR [-sync] <name> [<ttl>] [IN] <type> <data>
The CLI used a non-standard RRType-number for unknown resource record types; this does not follow RFC 3597 
which uses TYPEnumber. Starting with Cisco Prime IP Express 8.3.3, resource records can be created with type as 
TYPEnumber through CLI.
Troubleshooting DHCP Server Out of Memory Aborts on Linux
In Cisco Prime IP Express 8.3.3, an issue on Linux with the DHCP server potentially using large amount of memory and 
aborting itself with an out-of-memory condition that was found to be related to an interaction of the glibc MALLOC 
behavior and the DHCP server has been addressed (see 
). In Cisco Prime IP Express 8.3.3, the cnrservagt 
will automatically set the MALLOC_PER_THREAD=1 and MALLOC_ARENA_MAX=1 environment variables to change the 
MALLOC behavior to prevent issues when starting the CPIPE processes.