Cisco Cisco Configuration Engine 1.4 Notas de publicación

For the smooth transition of existing applications from the old subject namespace, the Namespace 
Mapping service (NSM) has been updated with a new mechanism that maps old subjects to the new 
ones.

There are no code or configuration changes required in applications written using the NSM API 
since the API interfaces have not been modified. However, upgrading to Cisco CNS SDK 1.5.4 is a 
required procedure for the transition.

Applications that are written without the use of the Namespace Mapper have to be modified to 
accommodate the change in CNS event subjects. For example, the subject cisco.cns.config.load has 
been modified to cisco.mgmt.cns.config.load.

We recommend that all applications use the Namespace Mapper in order to maintain the separation 
between design-time and deployment-time subjects.

For a complete list of the new event subject names, see 

The none mode under Event Services Setting in the Setup program is not supported from the Cisco 
CNS Configuration Engine 1.4 user interface for updates made from the user interface to devices 
that use the old CNS event subject names. This is because NSM is not invoked in the none mode. 
NSM has been modified to translate subject names in support of devices not running Cisco IOS 12.3.

Refer to the Cisco CNS Configuration Engine 1.4 Administrator Guide for more information about 
these features.

Other documentation related to this product include:

Normal terminal login to the CNSIE-2110-K9 (x330) system is supported by way of the system serial 
port. The CNS 2100 Series system redirects and supports console login at the serial port. 

For more information about console access to the CNSIE-2110-K9 (x330) system, refer to the Release 
Notes for Cisco CNS 2100 Series Intelligence Engine, Release 1.3.