Cisco Cisco Security Manager 4.11 Guia De Especificação
Cisco Security Manager 4.4 API Specification (Version 1.1)
OL- 29074-01
Page 139
At time 10:00 AM user does a OOB change on ASA1 that is being monitored every 10
minutes (next monitoring schedule for 10:09 AM)
At time 10:03 AM user does a CSM deployment that overwrites the changes on ASA1
and deployment completes successfully
At time 10:09 AM, the HPM poll cycle will not recognize the OOB change as it is
overwritten by the CSM deployment done at 10:03 AM.
Following are the specific points for deviceStatus notifications.
o
Notifications will be sent for All the Alerts with description “Device Polling” in Health and
Performance Monitoring(HPM) feature of CSM. All the notifications will be sent whenever the
CSM server is restarted. Henceforth only Device Status change notifications will be sent.
CSM server is restarted. Henceforth only Device Status change notifications will be sent.
o
If the Alert description is “Device Polling: Connection Timedout” then a DEVICE_DOWN
notification will be sent.
o
If the Alert description is “Device Polling: Connected” then a DEVICE_UP notification will be sent.
o The HPM component monitors devices every 5 or 10 minutes based on whether a device is actively
or non-actively monitored. Hence device status events will only be created once the HPM
monitoring cycle/poll is completed. I.e It is likely that the device might have gone down and come
up, a device status change notification will not be sent in this case as the HPM would not have
detected it.
monitoring cycle/poll is completed. I.e It is likely that the device might have gone down and come
up, a device status change notification will not be sent in this case as the HPM would not have
detected it.
The following are error codes specific to this method. There could be additional generic errors that the method
might return in cases of error
might return in cases of error
Code
Description
4001
This indicates a duplicate subscription request was made during the event
subscription. If two subscriptions are made using the same subscription id (for the
same user session) then this error is returned.
subscription. If two subscriptions are made using the same subscription id (for the
same user session) then this error is returned.
4002
This error indicates that the Syslog destination IP address specified was invalid. The
IP address must be in the a.b.c.d format without any mask address i.e. something like
192.168.10.10
IP address must be in the a.b.c.d format without any mask address i.e. something like
192.168.10.10
4003
This error is returned if the user tries to delete a subscription that does not exist.
4004
This error indicates that the syslog port specified was invalid. Valid ports range
between 1-65535.
between 1-65535.
4005
This error indicates an invalid subscriber ID was specified. Subscriber ID’s
containing only whitespaces are not allowed.
containing only whitespaces are not allowed.
4006
This error indicates that either the “Syslog Server” element or the “Event Filter”
element was not specified. Both these elements must be specified for an add request
only.
element was not specified. Both these elements must be specified for an add request
only.
4007
This error indicates that either the “Syslog Server” element or the “Event Filter”
element was specified for a delete operation. Both these elements must not be
specified for an delete request.
element was specified for a delete operation. Both these elements must not be
specified for an delete request.
Table 75: EventSubscription Method Error Codes
The following two sections elaborate on the content of syslog notification based on whether an XML based on plain
text format was chosen during subscription.
text format was chosen during subscription.