Team Configuration Using Curl Commands; Creating A Team Using Curl; Considerations When A Controller Team Is Formed Using Rest - HP HPE VAN SDN Controller 2.7 Administrator's Manual

Sample command
curl --header "X-Auth-Token: 131eaa225ece4293bcebfd7f8e3cffd0" -sX DELETE
http://localhost:8080/sdn/v2.0/net/keys/SNMP/description/"SampleNetconfKey"

Team configuration using curl commands

The following curl commands can be used to configure teaming.
NOTE: Examples of curl commands in this section use the --noproxy option, which is
appropriate where execution of curl commands does not need a proxy to access controllers. If
your network is set up such that a proxy is needed to access controllers, use the --proxy option.
For details on curl proxy options, visit http://curl.haxx.se/docs/manpage.html.

Creating a team using curl

Before creating a team ensure that your environment meets the requirements for teaming, see
"Requirements for teaming" (page
team, configure NTP to use a centralized NTP daemon, see
same local NTP servers" (page

Considerations when a controller team is formed using REST

The default configuration of the SDN Controller is the system's eth0 interface. When a controller
team is formed via REST with the team IP Address, an alias in the controller elected as leader
will be configured automatically by the system and will attach to the eth0 interface by default.
If the SDN Controller has multiple Ethernet interfaces, a different interface can be required for
the team IP Address. In this case the configuration /etc/sdn/admin/options might be
changed using vim or emacs to reflect the desired configuration.
sdncontroller:/opt/sdn/admin# cat options
export ADMIN_OPTS="-Dcom.hp.sdn.admin.interface=eth0"
Once the change has been made, the SDNA service must be restarted as shown with the following
command:
sdncontroller:/opt/sdn/admin#sudo service sdna restart
sdna stop/waiting
This change must be made for every active controller within the team and does not require that
the team be deleted via REST.
To view the team IP Address designation from the SDN Controller console or SSH session, use
the ifconfig command:
sdncontroller:$ ifconfig
100). And for each controller that will become a member of the
103).
eth0 Link encap:Ethernet HWaddr ac:16:2d:9a:62:60
inet addr:172.17.3.17 Bcast:172.17.15.255 Mask:255.255.240.0
inet6 addr: fe80::ae16:2dff:fe9a:6260/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1151070 errors:0 dropped:284 overruns:0 frame:0
TX packets:1134356 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:684988786 (684.9 MB) TX bytes:882495744 (882.4 MB)
Memory:f7f80000-f8000000
eth0:0 Link encap:Ethernet
inet addr:172.17.3.41 Bcast:172.17.15.255 Mask:255.255.240.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Memory:f7f80000-f8000000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:116581 errors:0 dropped:0 overruns:0 frame:0
TX packets:116581 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:32894518 (32.8 MB) TX bytes:32894518 (32.8 MB)
"Configuring controllers to use the
HWaddr ac:16:2d:9a:62:60
Team configuration using curl commands 181