Cisco Cisco Security Manager 4.11 Guia De Especificação
Cisco Security Manager 4.4 API Specification (Version 1.1)
OL- 29074-01
Page 138
Table 74: eventSubscription Response Elements and Attributes Description
Element.
Attribute
Name
Definition
eventSubResponse
Returns whether the subscription was successful or not. If successful it contains
the subscriptionId sent by the client.
the subscriptionId sent by the client.
Figure 89: EventSubResponse XML Schema
Following are some caveats for the syslog notifications:
The syslog notifications will only be sent for devices currently managed by CSM i.e. the device must be
added to the device inventory and must be “managed” by CSM.
added to the device inventory and must be “managed” by CSM.
CSM may optionally deploy changes to Auto Update Server (AUS) and Cisco Networking Services (CNS)
Configuration Engine based on how the device is managed in CSM. The AUS/CNS schemes provide an
intermediate “staging system” for the configuration updates before these actually get deployed on the real
device. Please see
Configuration Engine based on how the device is managed in CSM. The AUS/CNS schemes provide an
intermediate “staging system” for the configuration updates before these actually get deployed on the real
device. Please see
CNS or AUS successfully, the event notification scheme will send a successful config change update (It is
thus possible that at the time of sending the event, the config change might not be active on the real end
device).
thus possible that at the time of sending the event, the config change might not be active on the real end
device).
Following are specific points for Out of Band (OOB) notifications:
o The out of band change detection is currently only enabled for ASA devices (greater than version
7.2.x). Also OOB detection of ASA devices is only enabled if these devices are monitored by the
Health and Performance Monitoring (HPM) feature of CSM.
Health and Performance Monitoring (HPM) feature of CSM.
o The OOB notifications will only start detecting for OOB changes after at least “one successful event
subscription is done”. OOB events prior to this registration will be unknown and will not be
monitored.
monitored.
o The HPM component monitors devices every 5 or 10 minutes based on whether a device is actively
or non-actively monitored. Hence OOB events will only be created once the HPM monitoring
cycle/poll is completed. I.e It is likely that the OOB event will not be immediately generated as
soon as any OOB change is done on a device.
cycle/poll is completed. I.e It is likely that the OOB event will not be immediately generated as
soon as any OOB change is done on a device.
o The event service detects and notifies all OOB configuration changes including changed CLI/config
lines that may not managed by CSM. Detection also includes any CLI that may be changed and
reverted back. I.e. the system detects any configuration modified event on the device.
reverted back. I.e. the system detects any configuration modified event on the device.
o As a corner case, an OOB event may not be generated if a deployment via CSM is done
immediately succeeding an OOB change (before the HPM module can detect the change).
Consider the following case:
Consider the following case:
<xs:element
name
="
eventSubResponse
"
type
="
EventSubResponse
"/>
<xs:complexType
name
="
EventSubResponse
">
<xs:complexContent>
<xs:extension
base
="
BaseReqResp
">
<xs:sequence>
<xs:element
name
="
subscriptionId
"
type
="
xs:string
"
minOccurs
="
0
"
maxOccurs
="
1
"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>