Consuming NSO Services as a Network Operator

The NSO service that this tutorial will use as an example is the SVI Verify Example. It is already installed on the system install server (10.10.20.49) in the reservable Sandbox. The main parts of the service YANG model are as follows:

  list svi_verify_example {
    description "This is an RFS skeleton service";

    key name;
    leaf name {
      tailf:info "Unique service id";
      tailf:cli-allow-range;
      type string;
    }
    // gives us linkage to selftest
    uses selftest:selftest-result;
    uses ncs:service-data;
    ncs:servicepoint svi_verify_example-servicepoint;
  
   list switches {
        key "id";
        leaf id{
          tailf:info "Switches identifier";
          type string;
        }
        leaf switch-device {
          mandatory true;
          type leafref {
            path "/ncs:devices/ncs:device/ncs:name";
          }
        }
      }
   list firewalls {
        key "id";
        leaf id{
          tailf:info "firewalls identifier";
          type string;
        }
        leaf firewall-device {
          mandatory true;
          type leafref {
            path "/ncs:devices/ncs:device/ncs:name";
          }
        }
      }
      
      leaf vlan-id {
        type uint16;
        mandatory true;
      }
      leaf vlan-name{
        type string;
        mandatory true;
      }

  }
}

Basically, there are two sets of devices that will be configured in the service:

Another two values that are required to make the SVI service work are a VLAN ID and a VLAN name. These input values are then fed into the configuration template:

<config-template xmlns="http://tail-f.com/ns/config/1.0">
  <devices xmlns="http://tail-f.com/ns/ncs">
    <?foreach {/switches}?>
    <device>
      <name>{switch-device}</name>
      <config>
        <vlan xmlns="http://tail-f.com/ned/cisco-nx">
          <vlan-list>
            <id>{/vlan-id}</id>
            <name>{/vlan-name}</name>
          </vlan-list>
        </vlan>
        <interface xmlns="http://tail-f.com/ned/cisco-nx">
          <Vlan>
            <name>{/vlan-id}</name>
            <description>{/vlan-name}</description>
            <ip>
              <address>
                <ipaddr>172.16.107.2/24</ipaddr>
              </address>
              <redirects>false</redirects>
              <router>
                <ospf>
                  <name>1</name>
                  <area>0.0.0.0</area>
                </ospf>
              </router>
            </ip>
            <ipv6>
              <redirects>false</redirects>
            </ipv6>
            <hsrp>
              <hsrp-list>
                <id>10</id>
                <addr_type>ipv4</addr_type>
                <ip>
                  <address>172.16.107.1</address>
                </ip>
              </hsrp-list>
            </hsrp>
          </Vlan>
        </interface>
      </config>
    </device>
    <?end?>    <!-- end foreach {/endpoint} -->
  </devices>


  <devices xmlns="http://tail-f.com/ns/ncs">
    <?foreach {/firewalls}?>
    <device>
      <name>{firewall-device}</name>
      <config>
        <object xmlns="http://cisco.com/ned/asa">
          <network>
            <name>INSIDE-{/vlan-name}</name>
            <subnet>
              <address>172.16.107.0</address>
              <mask>255.255.255.0</mask>
            </subnet>
          </network>
        </object>
        <object-group xmlns="http://cisco.com/ned/asa">
          <network>
            <id>INSIDE-NETWORKS</id>
            <network-object>
              <id>object INSIDE-{/vlan-name}</id>
            </network-object>
          </network>
        </object-group>
      </config>
    </device>
    <?end?>    <!-- end foreach {/endpoint} -->
  </devices>
</config-template>

What You’ll Learn

What You’ll Need

Configuring the CLI

Removing an NSO Service Instance

Learn More