Cisco Cisco ASA for Nexus 1000V Series Switch
About the ASA REST API
REST Agent in ASA
REST Agent in ASA
15
Recommendation/Action:
The administrator should attempt to disable "no rest-api agent" and enable the REST API Agent again using "rest-api
agent".
Syslog #3
Description/Rationale/Overview:
A notification that the REST API Agent has failed.
Syslog Number and Format:
%ASA-3-342003: REST API Agent failure notification received. Agent will be restarted automatically.
Explanation:
A notification of the REST API Agent is received and a restart of the Agent is being attempted.
Recommendation/Action:
None
Syslog #4
Description/Rationale/Overview:
The REST API Agent could not be successfully started after multiple attempts.
Syslog Number and Format:
%ASA-3-342004: Failed to automatically restart the REST API Agent after 5 unsuccessful attempts. Use the 'no rest-api
agent' and 'rest-api agent' commands to manually restart the Agent.
Explanation:
The REST API Agent has failed to start after many attempts.
Recommendation/Action:
Administrator should refer should to syslog %ASA-3-342002 (if logged) to better understand the reason behind the
failure. The administrator should attempt to disable "no rest-api agent" and enable the REST API Agent again using
failure. The administrator should attempt to disable "no rest-api agent" and enable the REST API Agent again using
"rest-api agent".
Out of band changes handling
When processing the REST API request if out-of-band configuration change was observed, configuration will be
reloaded in to REST API Agent before further handling the request.
reloaded in to REST API Agent before further handling the request.
Typical request flow
The following is the flow for any REST PUT/POST/DELETE API request:
• REST Client establishes SSL connection to ASA.
• REST Client sends API request with basic authentication header to ASA.