site_logo

Previous Next


  1. ENCOR Practice Tests
  2. ENARSI Practice Exam
  3. CCNA Practice Tests

CCNP ENCOR Certification Cram Notes : Automation

6.4 Describe APIs for Cisco DNA Center and vManage

Cisco DNA Center and vManage provide APIs (Application Programming Interfaces) to programmatically manage and automate network operations.

Cisco DNA Center API is based on RESTful principles and uses HTTPS for transport. It supports both XML and JSON encoding for data exchange. With the API, you can perform various tasks such as network device configuration, monitoring, and management. You can also use it to retrieve network topology, devices, and clients information.

vManage API is also based on RESTful principles and uses HTTPS for transport. It supports both JSON and XML encoding for data exchange. With the API, you can perform various tasks such as device configuration, monitoring, and management. You can also use it to retrieve network topology, devices, and clients information.

Using these APIs, you can develop custom applications or integrate with third-party tools to automate network operations, such as provisioning new network devices, updating configuration, monitoring network performance, and troubleshooting network issues.

6.5 Interpret REST API response codes and results in payload using Cisco DNA Center and RESTCONF

When using REST APIs, it is important to understand the different response codes and how to interpret the results in the payload. Here are some common REST API response codes:

  • 200 OK: The request was successful, and the server returned the requested data.

  • 201 Created: The request was successful, and a new resource was created.

  • 204 No Content: The request was successful, but there is no data to return.

  • 400 Bad Request: The request was not valid, and the server could not process it.

  • 401 Unauthorized: The request requires authentication, and the user does not have valid credentials.

  • 403 Forbidden: The request was valid, but the server refused to respond to it.

  • 404 Not Found: The requested resource was not found on the server.

  • 500 Internal Server Error: The server encountered an error while processing the request.

When working with Cisco DNA Center and RESTCONF, you can use these response codes to determine the success or failure of your API requests. The payload of the response will contain the requested data or an error message, depending on the response code.

For example, if you make a GET request to retrieve the list of devices in Cisco DNA Center, you may receive a response with a 200 OK status code and a JSON payload containing the device information. If you make a POST request to create a new VLAN, you may receive a response with a 201 Created status code and a JSON payload containing the details of the new VLAN. If there is an error with your request, such as an invalid parameter, you may receive a response with a 400 Bad Request status code and a JSON payload containing an error message.

6.6 Construct EEM applet to automate configuration, troubleshooting, or data collection

EEM (Embedded Event Manager) is a feature on Cisco IOS and IOS-XE devices that allows you to automate tasks and take action based on certain events or conditions. An EEM applet is a script that can be created to perform a specific action when triggered by an event. Here is an example of how to construct an EEM applet to automate a configuration change:

bashCopy code
event manager applet change_interface_speed
event syslog pattern "Interface GigabitEthernet1/0/1, changed state to administratively down"
action 1.0 cli command "enable"
action 2.0 cli command "configure terminal"
action 3.0 cli command "interface GigabitEthernet1/0/1"
action 4.0 cli command "speed 1000"
action 5.0 cli command "no shutdown"
action 6.0 cli command "end"

This applet will trigger when the syslog message "Interface GigabitEthernet1/0/1, changed state to administratively down" is generated, which indicates that the interface has been administratively shut down. The applet will then change the interface speed to 1000 Mbps and bring the interface back up.

Note that this is just a simple example, and there are many other ways to use EEM applets for automating network tasks, troubleshooting, or data collection.

6.7 Compare agent vs. agentless orchestration tools, such as Chef, Puppet, Ansible, and SaltStack

Agent and agentless orchestration tools are both used for automating network configurations, deployment, and management. The main difference between these two types of tools is that agentless tools use SSH, Telnet, and other remote access protocols to connect to the network devices and execute commands, while agent-based tools require an agent to be installed on the target devices.

Here are some characteristics and examples of each type of tool:

Agent-based orchestration tools:

  • Require an agent to be installed on the target devices.

  • Can provide more granular control and management over the devices.

  • Can handle more complex tasks such as software installation and configuration management.

  • Examples: Puppet, Chef, SaltStack.

Agentless orchestration tools:

  • Do not require an agent to be installed on the target devices.

  • Are easier to deploy and manage than agent-based tools.

  • Are usually simpler and less powerful than agent-based tools.

  • Examples: Ansible, SaltStack (also supports agent-based mode).

Overall, the choice between agent and agentless orchestration tools depends on the specific use case, network environment, and management requirements.


Previous Next



simulationexams.com ad

certexams.com ad