Team alias node
An IP Address (North-Bound IP) alias is created on the node that is elected as team leader to
allow a controller team to be accessible with a single IP Address no matter which controller is
the leader. This IP Address is provided as part of the team configuration when creating a team.
If the elected node stops being the team leader, the team IP Address must be removed from the
interface because this address must be reassigned to the actual team leader. This must be done
as the
sdn
user. If assigning or removing an alias fails, one of the following messages appears
in the Alert log:
•
Programming team alias
ip-address
failed
•
Unprogramming team alias
ip-address
failed
In either of these instances, the condition is logged and the team continues to operate. In this
case you can manually program the team alias.
You can configure the alias as follows:
sudo ifconfig <
alias interface
> <
alias IP
> netmask <
net mask address
>
up
Example command
sudo ifconfig eth0:0 192.0.123.5 netmask 255.255.255.0 up
You can disable the alias as follows:
sudo ifconfig <
alias interface
> <
alias IP
> netmask <
net mask address
> down
Example command
sudo ifconfig eth0:0 192.0.123.5 netmask 255.255.255.0 down
Cassandra database maintenance in a team
Some applications may choose to use the Cassandra database to store persistent data. For
these applications, there is an extra maintenance step that you must run once every ten days to
help maintain the performance of the database and the consistency across the team, as follows:
1.
You need to make sure all controllers are up and Cassandra is running:
/opt/sdn/cassandra/bin/nodetool ring |grep -c 'Up'
This command must return 3.
2.
Login to each controller in sequence and run the following command. The command must
be run as the
sdn
user.
/opt/sdn/cassandra/bin/nodetool repair
NOTE:
Do not attempt to run this command at the same time on different controllers. It must run to
completion on one controller before you run it on another controller. This command may
have a significant impact on disk and network I/O across all controllers in the team and it
may take some time. You should run this command during a low usage window.
Disbanding a team using curl
Disbanding a team returns the teamed controllers to standalone operation. This action initiates
the team delete. The REST call might return before the delete has completed. You must check
the system to see the running state of the system.
1.
Before disbanding a team, delete the region configuration for that team.
See
“Removing a region using curl” (page 198)
2.
Acquire an authentication token for the team leader. (See step 4 of
.)
3.
Using the token acquired in the step 2, disband the team:
curl --noproxy
team-ip
--header "X-Auth-Token:
auth_token
" --fail
186
curl commands