Skip to content
Branch: master
Find file History
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

Automated Service Provider Fabric

This part is dedicated for automated deployment of:

  1. Underlaying MPLS infrastructure (ISIS, Segment Routing, TI-LFA)
  2. Underlaying BGP signaling (VPN-IPV4/VPN-IPV6 UNICAST, EVPN address-families)
  3. Overlay services (IP VPN (IPv4/IPv6), EVPN (L2/L3))

Powered by OpenConfig

Wherever possible, OpenConfig YANG models are used. More preciesly OpenConfig is used:

  1. In Arista EOS and Cisco IOS XR for configuration of underlay MPLS fabric running ISIS as IGP with Segment Routing extensions
  2. In Cisco IOS XR for configuration of underlay BGP sginaling for EVPN, VPNV4/VPNV6 unicast
  3. In Cisco IOS XR for configuration of VRF, interfaces in VRF and BGP within VRF for PE-CE routing

Important notes:

  1. As of today the most current Nokia SR OS release 16.0.R5 doesn't support Segment Routing in OpenConfig YANG models. Nevertheless the common templates openconfig-interfaces.j2 and openconfig-network-instance.j2 are prepared and can properly configure ISIS on all NOSes including Nokia SR OS. As soon as Nokia's OpenConfig YANG models will support Segment Routing, the Ansible playbooks will be changed so that Nokia start use OpenConfig as well. Temporary Nokia is using native YANG modules without JTOX drivers (direcly XML is templated).
  2. Arista EOS in version supports OpenConfig YANG modules only for IPV4/IPV6 UNICAST AFI/SAFI, hence Ansible module eos_config is used to configure underlay BGP. For Nokia SR OS also Ansible sros_config is used.
  3. During creation of automation using OpenConfig it turned out that there is no node for update-source wihtin BGP module, that's why native Cisco IOS XR YANG module is used to fix that. There is no JTOX used for that, but rather XML for NETCONF is constructed directly.
  4. For IP VPN services the following mix of provisioning techniques is used: OpenConfig/native YANG for Cisco, CLI-based for Arista, native YANG for Nokia.

How to use Service Provider Fabric automation

There are several possible options how you can automatically deploy Service Provider Fabric. The prerequisite is copy the initial configuration files called sp_{{ hostname }}_initial.conf from files folder to the running config of your network functions. Then use the following tags:

  1. To deploy undelay routing (ISIS) and MPLS (Segment Routing) use ansible-playbook service_provider_fabric.yml --inventory=hosts --tags=underlay_mpls.
  2. To deploy undelay BGP signaling use ansible-playbook service_provider_fabric.yml --inventory=hosts --tags=underlay_bgp.
  3. To deploy the whole underlay infrastructure (ISIS + Segment Routing + BGP) use ansible-playbook service_provider_fabric.yml --inventory=hosts --tags=underlay.
  4. To depoy overlay IP VPN service use ansible-playbook service_provider_fabric.yml --inventory=hosts --tags=ip_vpn.
  5. To provision customer sites for IP VPN use ansible-playbook customer_equipment.yml --inventory=hosts --tags=ip_vpn.
  6. To enable SNMPv3 monitoring use ansible-playbook service_provider_fabric.yml/customer_equipment.yml --inventory=hosts --tags=nms_snmp.

Temporary limitations

Currently there are no tag, which allow you to create EVPN overlay service.

How to use InfluxData TICK + Grafana and hosts automation

There are different tags for installation and operation:

  1. To update your /etc/hosts use ansibple-playbook management_cloud.yml --inventory=hosts --tags=update_hosts
  2. For the first time installation of Docker and all related tools use ansibple-playbook management_cloud.yml --inventory=hosts --tags=docker_install.
  3. For the first time installation of Telegraf + InfluxDB + Grafana use ansibple-playbook management_cloud.yml --inventory=hosts --tags=tick_install.
  4. For subsequent launch (2nd and later) of Docker use ansibple-playbook management_cloud.yml --inventory=hosts --tags=docker_ops.
  5. For subsequent launch (2nd and later) of Telegraf + InfluxDB + Grafana use ansibple-playbook management_cloud.yml --inventory=hosts --tags=tick_ops.

How to use YANG tools

There are some Ansible playbooks, which help a lot for development of automation based on YANG (NETCONF/YANG, RESTCONF/YANG, GNOI/YANG):

  1. Tool yang_extractor_config.yml is used to extract from the network function actual configuration and associated stated in particular YANG module. You can use calling ansible-playbook oc_extractor.yml --inventory=hosts --limit=X1 --tags=X2, where X1 is hostname of the network function (i.e. EOS1, SR1, XR1, etc) and X2 defines the intersted YANG module. Thr following modules are currently supported:
  • Tag oc-if stands for OpenConfig YANG module openconfig-interfaces.yang including all openconfig-if-*.yang extensions.
  • Tag oc-netinst stands for OpenConfig YANG module openconfig-network-instance.yang including all its imports.
  • Tag oc-lldp stands for OpenConfig YANG module openconfig-lldp.yang.
  • Tag cisco-bgp stands for Cisco native YANG module Cisco-IOS-XR-ipv4-bgp-cfg.yang.
  • Tag cisco-vrf stands for Cisco native YANG module Cisco-IOS-XR-infra-rsi-cfg.yang.
  • Tag nokia-conf stands for Nokia native YANG module nokia-conf.yang.
You can’t perform that action at this time.