Users Guide

B–Configuration File Examples
Understanding Team Configuration Files
Doc No. TD-000971 Rev. 1
January 29, 2021 Page 175 Copyright © 2021 Marvell
Team Configuration File Requirements
Requirements for the team configuration file include the following:
 A team configuration file must contain at least one team configuration.
QCSCLI.exe recognizes name as the starting point of a team
configuration section. All lines after name apply to the team_name until
another name or end-of-file is encountered.
 Each team configuration must contain at least one physical network adapter.
Otherwise the configuration of the team is ignored.
 If type is missing, the default is set to Smart Load Balancing (SLB). The
four team types include: SLB = 0, GEC = 1, LACP = 2 and SLB-AFD = 4.
 If ip is set, smask must also be set or ip is ignored. If ip is not set,
DHCP is used.
 The team IP can be set if no VLANs are configured. If any VLAN is
configured, the team IP is ignored. Multiple VLAN configurations are
allowed. Each VLAN configuration allows an optional static IP information.
Each IP must be coupled with smask, otherwise it is ignored.
 There must at least one white space or tab between the tag (name, pnic,
and so on) and the value pair (team_name, MAC_address, and so on) in
each line.
 Keywords before semicolons are case sensitive.
Team Configuration File Examples
The following show examples of a team configuration XML file. For details about
the command, see “Save (Team)” on page 128.
Example Without LiveLink Parameters
The following shows an example of the TeamConfig.txt configuration file with
NO_LIVELINK_PARAMS:
name: BRCMTeam type: 1
pnic: 00101801794D
pnic: 00:0B.2 vname: VLAN2 vid: 2
vname: VLAN3 vid: 3
ip: 172.16.8.3
smask: 255.255.255.0
vname: VLAN4 vid: 4
NOTE
In NPAR mode, the team configuration type GEC is not supported.