HP HPE VAN SDN Controller 2.7 Administrator's Manual page 108

Edit the configuration file (for example vi build_team.conf) or create a custom configuration
file to include the following inputs about the team configuration. You cannot change the parameter
name, such as User or Team_IP. Some entries are optional as noted in the following table.
NOTE: You can create multiple configuration files, each for use with a different team
configuration. Then you can use the same script (but with a different configuration file) to create
another team.
Parameter
User
Password
Sleep_Time
Team_IP
IP1, IP2, IP3
Controller_IPs
Region1_name
Region1_Prioritized_Controller_IPs
Region1_Device_Ranges
Region1_Device_IPs
108 Configuring for High Availability
Value
(optional) The default login user name is sdn. Enter a different login user
name if a user name other than sdn has been set for the controllers. Or
leave the user name blank in the configuration file if you want the user to be
prompted to enter it when they run the script. All controllers in the team you
are configuring must have the same user name and password.
(optional) The default login password is skyline. Enter a different login
password if a different one has been set for the controllers. Or leave the
password blank if you want the user to be prompted to enter it when they
run the script. All controllers in the team you are configuring must have the
same user name and password.
(required) The default is 30 seconds. You can change this value if you want
to allow more time for the controller to propagate the changes to other
controllers. You may need to do this if, for example, your network is slow. If
you leave this blank, the default 30 seconds is used.
(required) The IP address to be assigned to the team. The team IP address
is different from the individual controller IP addresses. It is used as a virtual
address for connecting to the team leader.
Physical IP addresses for the three controllers in the team.
IP1, IP2, and IP3 are optional because alternately you can enter the IP
addresses under Controller_IPs instead of as IP1, IP2, and IP3.
If you enter an IP address for IP1, IP2, and IP3 you can use the notation
$IP1, $IP2, and $IP3 in the Controller_IPs and Region parameters that follow.
When running the team configuration script, it will check to verify that the IP
addresses are valid.
For requirements on the IP address you enter for team configuration, see
"High Availability best practices" (page
(required) The order of the controllers in the team from master to primary
slave and secondary slave. You can either enter the full IP addresses
separated by commas or you can use the notation $IPx where x is the number
from the values you defined above. For example $IP1, $IP2, $IP3.
(required if specifying regions) User-defined name for the first region. You
can specify 1, 2, or 3 regions in a team, or you can have a configuration with
no regions.
(required if specifying regions) The prioritized order of the controllers in this
region from first to last. You can either enter the full IP addresses separated
by commas or you can use the notation $IPx where x is the number from
the values you defined above. For example $IP1, $IP2, $IP3.
(optional but either range or device IPs are required if defining devices) The
ranges for devices that you want to be configured in Region1. You can either
define devices by range or by individual IP address.
For requirements on the device IPs you enter for team configuration, see
"High Availability best practices" (page
(optional but either range or device IP is required if defining devices) The
device IPs configured in Region1. You can either define devices by range
or by individual IP address.
99).
99).