Service Manual
• shallow — Retrieves a resource with no subresources inline.
• select — Client uses to select the nodes and subresources.
• with-defaults — Client uses to control and display the default data in GET request.
To request a ltered partial response, use the select query parameter in the following patterns to specify the nodes and subresources.
• Use a semicolon separated list to select multiple nodes.
• Use a/b to select a node b that is nested within node a. Use a/b/c to select a node c nested within b.
• Use expressions in parentheses ( ) after any selected node to request specic subnodes.
• Use the wildcard notation within parentheses (*) to specify all sub nodes of a specic node.
NOTE: The node a/b/c;a/b/d is equivalent to a/b(c;d).
The following request selects the routes name and next-hop/name nodes:
GET
/running/sys/routes/inet/route/10.20.0.0,16?select=name;next-hop(name)
Sample BGP Congurations
The following are the sample BGP congurations via REST API.
Figure 3. BGP Topology
The PDU structure for conguring the IP address on an interface is as follows:
cat ipaddr_config_put.xml
<interface>
<name>tengig-0-0</name>
<ip>
<address>
<primary>
<address>11.1.1.1/24</address>
</primary>
</address>
</ip>
</interface>
The following conguration depicts the IP address conguration for router interfaces via REST– PUT request:
curl -v -u admin:admin http://10.16.151.159:8008/api/running/dell/interfaces/interface/
tengig-0-0 -X PUT -T ipaddr_config_put.xml
* About to connect() to 10.16.151.159 port 8008
* Trying 10.16.151.159... connected
* Connected to 10.16.151.159 (10.16.151.159) port 8008
* Server auth using Basic with user 'admin'
> PUT /api/running/dell/interfaces/interface/tengig-1-37 HTTP/1.1
> Authorization: Basic YWRtaW46YWRtaW4=
> User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.8b zlib/1.2.3
libidn/0.6.5
> Host: 10.16.151.159:8008
REST API
131