Cisco Cisco Network Registrar 7.2 Notas de publicación

On Linux or Solaris, the following test program verifies that you have set your PATH or 
LD_LIBRARY_PATH correctly:

On Windows, the following test program verifies that you have set your CLASSPATH correctly:

For Java SDK client code developed with an earlier version of the SDK, you can simply recompile most 
code with the latest JAR file to connect to an upgraded server.

But in cases where the client code for versions before 7.1 directly manipulates reservation lists in scopes 
or prefixes, changes are required. These changes are required because the embedded reservation lists in 
both scopes and prefixes are no longer used. Beginning with version 7.1, individual reservations are 
stored separately and reference the parent scope or prefix by name.

The new design provides the following benefits:

Reservation edits (add/modify/delete) do not require a scope or prefix edit.

Reservations can be indexed directly to allow quick search and retrieval.

Edits to scopes or prefixes with a large number of reservations no longer result in large scope or 
prefix change entry logs.

No changes are required for client code that adds or removes reservations using the addReservation or 
removeReservation methods. However, these methods are now deprecated because the edit functionality 
is replaced and extended by the general addObject, modifyObject, removeObject, addObjectList, 
modifyObjectList, and removeObjectList methods.

 lists the enhancement features added in the Cisco Network Registrar 7.2.2 release.

Click on the identifier to view the impact and workaround for the caveat. This information is displayed 
in the 

DNS should have default exception-forwarding set to forward-always