324
If the two SN codes are the same, the device uses the device role and system description in
the tag file.
If the two SN codes are different, the device does not use the device role and system
description.
4.
Determines the name of the template file to download based on the following information:
The device role in the tag file or the default device role.
The template file name obtained from the DHCP server.
For example, template file
dist_leaf.template
is for a leaf node in a VXLAN network with
distributed IP gateways.
5.
Downloads the template file from the TFTP server.
6.
Parses the template file and performs the following operations:
Deploys static configurations that are independent from the VCF fabric topology.
Deploys dynamic configurations according to the VCF fabric topology.
−
In a data center network, the device usually uses a management Ethernet interface to
connect to the fabric management network. Only links between leaf nodes and servers
are automatically aggregated.
−
In a campus network, the device uses VLAN-interface 1 to connect to the fabric
management network. Links between two access nodes cascaded through
GigabitEthernet interfaces and links between leaf nodes and access nodes are
automatically aggregated. For links between spine nodes and leaf nodes, the
trunk
permit vlan
command is automatically executed.
NOTE:
•
On a data center network, if the template file contains software version information, the device
first compares the software version with the current software version. If the two versions are
inconsistent, the device downloads the new software version to perform software upgrade. After
restarting, the device executes the configurations in the template file.
•
After all configurations in the template file are executed, use the
save
command to save the
configurations to a configuration file.
Template file
A template file contains the following:
•
System-predefined variables
—The variable names cannot be edited, and the variable values
are set by the VCF topology discovery feature.
•
User-defined variables
—The variable names and values are defined by the user. These
variables include the username and password used to establish a connection with the Neutron
server, network type, and so on. The following are examples of user-defined variables:
#USERDEF
_underlayIPRange = 10.100.0.0/16
_master_spine_mac = 1122-3344-5566
_backup_spine_mac = aabb-ccdd-eeff
_username = aaa
_password = aaa
_rbacUserRole = network-admin
_neutron_username = openstack
_neutron_password = 12345678
_neutron_ip = 172.16.1.136
_loghost_ip = 172.16.1.136
_network_type = centralized-vxlan