Cisco Cisco Email Security Appliance C650 Entwickleranleitung
13
AsyncOS API for Cisco Email Security Appliances - Getting Started Guide
Troubleshooting AsyncOS API
API Logs
Subscribe to the API logs using System Administration > Log Subscriptions. For instructions, see
Cisco AsyncOS for Email User Guide or Online Help.
Cisco AsyncOS for Email User Guide or Online Help.
The following are some of the events that are logged in the API logs:
•
API has started or stopped
•
Connection to the API failed or closed (after providing response)
•
Authentication succeeded or failed
•
Request contains errors
•
Error while communicating network configuration changes with AsyncOS API
Alerts
Ensure that the appliance is configured to send you alerts related to AsyncOS API. You will receive alerts
when:
when:
Alert About Network Configuration or Certificate Changes Not Communicated to AsyncOS API
Problem
You receive a critical alert stating that the network configuration or certificate changes made
using web interface or CLI are not communicated to the API.
Solution
Try the following:
•
Restart the appliance.
•
If the problem persists, contact TAC.
Certificate Error while Using cURL
Problem
If you are using HTTPS and your own certificate for secure communication with API, on some
operating systems (such as Unix, Ubantu, Mac OS X, and so on) you may receive certificate errors while
requesting API resources using cURL. The following are a few examples:
requesting API resources using cURL. The following are a few examples:
•
curl: (60) SSL certificate problem: Invalid certificate chain
•
curl: (77) error setting certificate verify locations
Solution
Refer cURL documentation:
Alert Description
Type
Severity
API has restarted due to an error
System
Warning
Network configuration or certificate changes made
using web interface or CLI are not communicated to the
API. See
using web interface or CLI are not communicated to the
API. See
System
Critical