Concept Guide

</bgp>
<neighbor>
<neighbor-router>11.1.1.2</neighbor-router>
</neighbor>
</bgp>
</collection>
* Connection #0 to host 10.16.151.159 left intact
* Closing connection #0
The following conguration depicts adding another BGP peer to the conguration via REST– PATCH request:
cat BGP_HTTP_REST_PATCH_PDU.xml
<bgp>
<as-name>100</as-name>
<neighbor>
<neighbor-router>11.1.1.3</neighbor-router>
<remote-as>200</remote-as>
<dmzlink-bw>false</dmzlink-bw>
<shutdown>false</shutdown>
</neighbor>
</bgp>
curl -v -u admin:admin http://10.16.151.159:8008
/api/running/dell/router/bgp -X PATCH -T
BGP_HTTP_REST_PATCH_PDU.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'
> PATCH /api/running/dell/router/bgp 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
> Accept: */*
> Content-Length: 493
> Expect: 100-continue
>
< HTTP/1.1 100 Continue
< Server: ConfD/5.2
< Allow: GET, POST, OPTIONS, HEAD
< Content-Length: 0
< HTTP/1.1 204 No Content
< Server: ConfD/5.2
< Cache-control: private, no-cache, must-revalidate, proxy-revalidate
< Date: Thu, 04 Dec 2014 13:25:31 GMT
< Allow: GET, POST, OPTIONS, HEAD
< Content-Length: 0
< Content-Type: text/html
< Etag: 1417-699531-877544@0
* Connection #0 to host 10.16.151.159 left intact
* Closing connection #0
Following is the current congurations applied on the system:
DellEMC#show config
!
router bgp 100
neighbor 11.1.1.2 remote-as 200
neighbor 11.1.1.2 no shutdown
neighbor 11.1.1.3 remote-as 200
neighbor 11.1.1.3 no shutdown
DellEMC#
144
REST API