cnos-vlag-1tier-leaf

Ansible Role: cnos-vlag-1tier-leaf - Single Layer vLAG Leaf Configuration


This is a template driven playbook for a single layer vLAG configuration. The role applies to the access switches that are downstream from the vLAG peers. These switches will be referred to as leaf switches.

The templates used in this configuration example are the same. They will be used to configure the leaf switches. The templates will be executed with different settings suitable to each leaf switch. Since there are two leaf switches, there will be two sets of values used in the templates.

The Ansible modules will execute or skip tasks given in the playbook depending on the flag setup of each IP address.

The configuration commands and their results can be verified in the commands and results directories.

For more details, see Configuring a single layer vLAG network.

Requirements


  • Ansible version 2.3 or later (Ansible installation documentation)
  • Lenovo switches running CNOS version 10.2.1.0 or later
  • an SSH connection to the Lenovo switch (SSH must be enabled on the network device)

Role Variables


Available variables are listed below, along with description.

The following are mandatory inventory variables:

Variable Description
ansible_connection Has to be network_cli
ansible_network_os Has to be enos
ansible_ssh_user Specifies the username used to log into the switch
ansible_ssh_pass Specifies the password used to log into the switch

The values of the variables used need to be modified to fit the specific scenario in which you are deploying the solution. To change the values of the variables, you need to visits the vars directory of each role and edit the main.yml file located there. The values stored in this file will be used by Ansible when the template is executed.

The syntax of main.yml file for variables is the following:

<template variable>:<value>

You will need to replace the <value> field with the value that suits your topology. The <template variable> fields are taken from the template and it is recommended that you leave them unchanged.

Available variables are listed below, along with description:

Variable Description
username Specifies the username used to log into the switch
password Specifies the password used to log into the switch
flag Configures the condition flag associated with the switch
stp_mode1 Configures the STP mode (mst - MSTP, rapid-pvst - Rapid PVST+, disable - STP is disabled)
port_range1 Specifies the ethernet port range
portchannel_interface_number1 Specifies the LAG number (1-4096)
portchannel_mode1 Configures the LAG type (on - static LAG, active - active member of a LACP LAG, passive - passive member of a LACP LAG)
slot_chassis_number1 Specifies the ethernet port (slot number/port number)
switchport_mode1 Configures the switch port mode (access - the port can be part of only a single VLAN, trunk - the port can be part of any number of VLANs)

Dependencies


  • username.iptables - Configures the firewall and blocks all ports except those needed for web server and SSH access.
  • username.common - Performs common server configuration.
  • /etc/ansible/hosts - You must edit the /etc/ansible/hosts file with the device information of the switches designated as leaf switches. You may refer to cnos-vlag-1tier-leaf-hosts for a sample configuration.

Ansible keeps track of all network elements that it manages through a hosts file. Before the execution of a playbook, the hosts file must be set up.

Open the /etc/ansible/hosts file with root privileges. Most of the file is commented out by using #. You can also comment out the entries you will be adding by using #. You need to copy the content of the hosts file for the role into the /etc/ansible/hosts file. The sample hosts file for the role is located in the main directory.

[cnos-vlag-1tier-leaf]
10.240.178.74   ansible_network_os=cnos ansible_ssh_user=<username> ansible_ssh_pass=<password> deviceType=g8272_cnos condition=leaf_switch1
10.240.178.75   ansible_network_os=cnos ansible_ssh_user=<username> ansible_ssh_pass=<password> deviceType=g8272_cnos condition=leaf_switch2

Note: You need to change the IP addresses to fit your specific topology. You also need to change the <username> and <password> to the appropriate values used to log into the specific Lenovo network devices.

Example Playbook


To execute an Ansible playbook, use the following command:

ansible-playbook cnos-vlag-1tier-leaf.yml -vvv

-vvv is an optional verbos command that helps identify what is happening during playbook execution. The playbook for each role of the single layer vLAG configuration solution is located in the main directory of the solution.

- hosts: cnos-vlag-1tier-leaf
  roles:
    - cnos-vlag-1tier-leaf
```	


## License
---
<add license information below>
Copyright (C) 2017 Lenovo, Inc.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
About

The cnos-vlag-1tier_leaf role facilitates the configuration of the leaf switches in the PoD for VLAG in a Tier 1 fabric for switches running Lenovo's CNOS operating system.

Install
ansible-galaxy install lenovo/ansible-role-cnos-vlag-1tier-leaf
GitHub repository
License
apache-2.0
Downloads
59
Owner
Open source projects from Lenovo