
********************************************************************************
* Copyright (C) 2019-2024 by Extreme Networks , Inc.                           *
* This file is part of rcBreeze Dump                                            *
*                                                                              *
* Author: Pradeep Raj.                                                         *
*                                                                              *
*                                                                              *
* Directions to Use:                                                           *
* 1. Replace all the values enclosed in the "%" with                           *
*    the values to be configured. The string present with in the braces        * 
*    indicates its type.                                                       *
* 2. To pass "" in the request replace the " with %22.                         *
* 3. To pass multiple keys in the URI enclose seperate them with %2c or        *
*    comma(",").                                                               *
* 4. Avoid using the requests with [DO NOT USE] tag in the payload. These could*
*    be defective because of the tailf extensions they have.                   *
*                                                                              *
* 5. RestConf also supports Json formatting which can be obtained by simply    *
*    updating Content-Type: application/yang-data+xml to                       *
*    Content-Type: application/yang-data+json                                  * 
*                                                                              * 

* Disclaimer:                                                                  *
* 1. The queries mentioned here do not have a one-to-one correlation with CLI. *
* 2. The queries inferred here are based on an automated tool and are not      *
*    gauranteed to work. Its the functional teams responsibilty to ensure its  *
*    working.                                                                  *
* 3. In case if you find any discrepancy you can always contact the author to  *
*    get it fixed.                                                             *
* 4. Avoid using the requests with [DO NOT USE] tag in the payload. These could*
*    be defective because of the tailf extensions they have.                   *
********************************************************************************
curl -v -X POST -H "Content-Type: application/yang-data+json" -k -d "{\"bridge-domain\": {\"bridge-domain-id\": \"%bridge-domain-id-type%\", \"bridge-domain-type\": \"%enumeration%\"}}"  -u admin:password https://%ipaddress%:443/restconf/data/

curl -v -X POST -H "Content-Type: application/yang-data+json" -k -d "[DO NOT USE]{\"peer\": {\"peer-ip\": \"%inet:ipv4-address%\"}}"  -u admin:password https://%ipaddress%:443/restconf/data/brocade-bridge-domain:bridge-domain=%bridge-domain-id%,%bridge-domain-type%

curl -v -X POST -H "Content-Type: application/yang-data+json" -k -d "{\"router-interface\": {\"router-ve\": \"%interface:ve-type%\"}}"  -u admin:password https://%ipaddress%:443/restconf/data/brocade-bridge-domain:bridge-domain=%bridge-domain-id%,%bridge-domain-type%

curl -v -X POST -H "Content-Type: application/yang-data+json" -k -d "{\"ethernet\": {\"lif-bind-id\": \"%import-lif:lif-interface-type%\"}}"  -u admin:password https://%ipaddress%:443/restconf/data/brocade-bridge-domain:bridge-domain=%bridge-domain-id%,%bridge-domain-type%/logical-interface

curl -v -X POST -H "Content-Type: application/yang-data+json" -k -d "{\"port-channel\": {\"pc-lif-bind-id\": \"%import-lif:lif-port-channel-type%\"}}"  -u admin:password https://%ipaddress%:443/restconf/data/brocade-bridge-domain:bridge-domain=%bridge-domain-id%,%bridge-domain-type%/logical-interface

