![](/images/backgrounds/285925/hp-van-sdn-controller-software-products-administrators-guide-66988687x1.png)
Table 4 Error log for team configuration (continued)
Log message | Description |
| 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
Message | Description |
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 | |
|
|
|
Message |
| Description |
|
| |
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> | ||
|
|
|
An IP Address
•Programming team alias
•Unprogramming team alias
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