- Introducing the IOS XE REST API
- Installing the Virtual Services Management Container
- Client Authentication
- Global Configuration Requirements
- Domain Name System (DNS) Server
- Network Time Protocol (NTP)
- IP Interface Configuration Requirements
- L2 Interfaces
- Bridge Domains
- Multicast
- VxLAN
- DHCP Server and Relay Agent
- Routing Protocol (OSPF, BGP, EIGRP) Requirements
- ACL Requirements for Subnets or IP Ranges
- Network Address Translation (NAT)
- Firewall Inspection Requirements
- License Requirements
- Memory and CPU Usage Report
- VRF
- Virtual Private Networks (SVTI and EzVPN)
- LISP
- QoS
- HSRP
Interface IP Configuration Requirements
Resource Summary for IP Interface
|
|
|||||
|---|---|---|---|---|---|
|
|
|
|
|
|
|
| /api/v1/interfaces/{if-id}1 |
|||||
|
1.{if-id} = Interface ID returned from the REST API used to create the interface. |
Interface Resources
History
|
|
|
Enhanced interface API for BDI support: Added a new interface type: "bdi" |
|
Properties
JSON Representation
Examples Demonstrating Use of Interface ID
Examples Using Interface ID
Resource URI
|
|
|
|---|---|
Example 1: Creating a Loopback Interface
The following example is for a logical Ethernet network interface, and creates a loopback interface.
Note
POST /api/v1/ is available only for loopback. Cisco IOS XE 3.10 does not support POST /api/v1/ on a sub-interface.
Example 2: Retrieving an Interface
Example 3: Modifying an Interface
Examples Without Interface ID
Resource URI
|
|
|
|---|---|
Example: GET
Example: POST
Retrieve Interface Details
Resource URI
|
|
|
|---|---|
Example 1: Retrieve Interface Details
Example 2: Retrieve Sub-interface Details
Note
Available in Cisco IOS XE 3.11 and later
Retrieve All Interfaces and Details
Resource URI
|
|
|
|---|---|
Properties for Retrieve All
|
|
|
|
|---|---|---|
Example
Modify an Interface Configuration
Resource URI
|
|
|
|---|---|
Example 1: Changing the IP-address from 172.15.15.15 to 172.15.15.16
Example 2: Modify VLAN IDs (Example Includes Sub-interface Property)
Create an Interface
–
The loopback or sub-interface cannot be on the same network as a physical interface.
–
After a loopback interface is configured, a router-id can be generated from it.
If the if-name in the HTTP POST body has a dash (for example, myintf-0), the API controller code would add another dash to the if-name to make an if-id (for example, myintf--0). The if-name with one dash should be passed to the 1-P API calls.
Resource URI
|
|
|
|---|---|
Example 1: Create a Loopback Interface
JSON Response: Returning the Interface ID
Example 2: Create a Sub-interface
Note
Available in Cisco IOS XE 3.11 and later
Delete an Interface
Resource URI
|
|
|
|---|---|
Example 1: Delete an Interface
Example 2: Delete a Sub-interface
Note
Available in Cisco IOS XE 3.11 and later
Interface State
History
|
|
|
|
|
|
|
|
|---|---|---|---|
Retrieve Interface State
Resource URI
|
|
|
|---|---|
Example
Bring an Interface Up or Down
Resource URI
|
|
|
|---|---|
Example: "no shut" GigabitEthernet1
Interface Statistics
History
|
|
|
Properties
Retrieve Interface Statistics
Resource URI
|
|
|
|---|---|
Example
Clear Interface Statistics
This resource also supports clearing of interface statistics by doing a POST on the resource with the following request message. See Resource specific operations for more details & examples.
Feedback