Chapter 8 Data Models and Dynamic Templates

TenGigabitEthernet2/1/16: 
 
  Port-channel100: 
    port_channel: 100 
    description: LegacyVLANs 
    switchport: true 
    switchport_mode: trunk 
    lacp_mode: "active"

Dist01: 
      vlans: 100,200 
      service_policy: 
        input: QoS-IN-Legacy_VLANs 
      members:  
        TenGigabitEthernet1/1/13:        
 
        TenGigabitEthernet2/1/13: 
 
    Dist02: 
      vlans: 100,200 
      service_policy: 
        input: QoS-IN-Legacy_VLANs 
      members:  
        TenGigabitEthernet1/1/13:      
 
        TenGigabitEthernet2/1/13: 
 
platform_interfaces: 
  Dist01: 
    TenGigabitEthernet1/1/14: 
      type: DAD

TenGigabitEthernet2/1/14: 
      type: DAD

Dist02: TenGigabitEthernet1/1/14: type: DAD TenGigabitEthernet2/1/14: type: DAD Data Models – Host Variables Information that is unique to a specific device should be modeled in the host variable for that device. Follow the same standards, if possible, as group_vars and have a host_defaults section along with all the other applicable data dictionaries such as host_vrfs, host_vlans, host_interfaces, and host_port_channels. Looking at the data model for one of the distribution layer switches, DIST01, a partial configuration is started for DIST01 from the coverage provided by the [CAMPUS- DISTRIBUTION] group_vars data model. Now, complete the unique configurations specific to DIST01 using host_vars.