Cisco Cisco Security Manager 4.7 Guía Del Usuario
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
Cisco Security Manager 4.7 API Specification (Version 2.0)
OL- 32164-01
Page 14
1.2 Changes in Revision 1.1
The NB API 1.1 is a successor of the NB API 1.0. The following changes were added in the 1.1 version of the API:
1.2.1 Unified Access Rules
This is a new policy, supported in Version 1.1.
1.2.2 Security Policy Object
This is a new policy object, supported in Version 1.1.
1.2.3 Network object
This object has been changed to represent its data elements as <ipData>, in place of <ipv4Data>, when the API is
used for Unified Access Rules.
used for Unified Access Rules.
1.2.4 Return user/ticket that last modified a config rule
One of the use cases of the API is to get configuration data from CSM for compliance checks. The configuration
service API now also returns information regarding users and tickets that modified a configuration rule.
service API now also returns information regarding users and tickets that modified a configuration rule.
1.2.5 Add device status – up/down as part of the event service
Some Security Manager users have task threads that run daily and fetch changed configuration from the network
devices managed by Security Manager. For this they use the execDeviceReadOnlyCLICmds API call to get the
configuration from the Device.
devices managed by Security Manager. For this they use the execDeviceReadOnlyCLICmds API call to get the
configuration from the Device.
The execDeviceReadOnlyCLICmds API call hangs if the Device Status is down. Hence, users interested in this area
are advised to do a Device Status up/down check before executing the execDeviceReadOnlyCLICmds API call.
are advised to do a Device Status up/down check before executing the execDeviceReadOnlyCLICmds API call.
1.2.6 Exec command API call will be supporting custom
timeouts
In the version of the API prior to 1.1 (which was Version 1.0), execDeviceReadOnlyCliCmds has no timeout value,
so it can run for an infinite period of time and cause the API service to hang if a device is unresponsive. To prevent
that problem, the subsequent version of the API (Version 1.1) allows the method execDeviceReadOnlyCliCmds to
take an optional attribute in the Request. This optional attribute allows the API client to set an timeout for the
execDeviceReadOnlyCliCmds method call.
so it can run for an infinite period of time and cause the API service to hang if a device is unresponsive. To prevent
that problem, the subsequent version of the API (Version 1.1) allows the method execDeviceReadOnlyCliCmds to
take an optional attribute in the Request. This optional attribute allows the API client to set an timeout for the
execDeviceReadOnlyCliCmds method call.
1.2.7 API enhancement to return list of all the shared Policies
defined in CSM
A new API was added in Version 1.1 that returns the list of all shared policies in the system for a given policy type.
1.2.8 Return the Device’s SysObjectID in the Device Object
API Version 1.0 has many APIs which list out all the devices present in CSM. Additionally, API Version 1.1 now
includes the SysObjectID in the response.
includes the SysObjectID in the response.