Administrator's Guide

Table 4 Error log for team configuration (continued)
DescriptionLog message
to those controllers where the operation was a success. To
recover from this failure it is recommended to delete the
team on each failed controller so configuration files are
removed and so the controllers transition to standalone
mode.
Table 5 Success log
DescriptionMessage
Team created.
Team created with the following configuration: [Team IP:
<team ip>, [Members<member list>].
Team disbanded.
Programmed Team alias: <team ip>.
Unprogrammed Team alias: <team ip>.
Table 6 Team IP error log
DescriptionMessage
Exception while checking alias: <team ip>, <exception>
Team alias: <team ip> already programmed
Exception while programing alias: <team ip>, <exception>
Exception while unprograming alias: <team ip>,
<exception>
7.8.1 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 team leader, the team IP Address must be removed from the aliases because this
address must be reassigned to the actual team leader. 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 using the following commands:
7.8.1.1 Configuring the alias
sudo ifconfig Mask:network_masketh0:0 controller_ip netmask network_mask
eth0 up
7.8.1.2 Disabling the alias
sudo ifconfig Mask:network_mask eth0:0 controller_ipnetmask
network_masketh0 down
7.8 Error log for team configuration 87