<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: IOS NED different for different IOS versions? in NSO Developer Hub Discussions</title>
    <link>https://community.cisco.com/t5/nso-developer-hub-discussions/ios-ned-different-for-different-ios-versions/m-p/3697756#M2535</link>
    <description>&lt;BLOCKQUOTE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;HR /&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;FONT face="courier new,courier"&gt;switchport trunk allowed &lt;STRONG&gt;vlan&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/PRE&gt;
&lt;P&gt;Then the NED says the device would expect&amp;nbsp;the following:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;FONT face="courier new,courier"&gt;ios0(config-if)# switchport trunk allowed vlan ?
  WORD   VLAN IDs of the allowed VLANs when this port is in trunking mode
  none   no VLANs
&lt;/FONT&gt;&lt;/PRE&gt;
&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;So my question is:&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;Is it a mistake in the NED that it doesnt expect "add" followed by the VLAN ID? Or is this something that maybe behaves differently depending on which IOS/IOS-XE version is used on the actual device?&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;No, this is as it should be. The YANG model of the device does not include action verbs like "add". This only makes sense in a CLI world, and not in clean interfaces like e.g. NETCONF, so the YANG models do not have this. The VLAN you mention will be added if it is new, updated otherwise.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;BLOCKQUOTE&gt;&lt;HR /&gt;
&lt;PRE&gt;&lt;FONT face="courier new,courier"&gt;interface vlan&lt;/FONT&gt;&lt;/PRE&gt;
&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;a real device doesn't seem to be bothered about whether it is a capital V (in Vlan) or a lower case v (vlan).&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;&lt;SPAN style="font-weight: 400;"&gt;The NED does seem to mind whether upper or lower case is used:&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Yes, the NED follows the YANG module exactly, and there it was modeled as lowercase.&amp;nbsp;&lt;SPAN style="font-family: inherit;"&gt;Allowing multiple spellings only really makes sense in a CLI, and not in e.g. NETCONF. IIRC it is possible to configure NSO to ignore upper/lowercase in the CLI (and internally pick the spelling used in the YANG), if you really want that.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;BLOCKQUOTE&gt;&lt;HR /&gt;
&lt;P&gt;&amp;nbsp;Is that something I have to worry about (as the sample config the customer provided always&lt;/P&gt;
&lt;P&gt;uses lower case)?&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Well, your CLI commands and your code needs to use the right spelling (case), as defined in the YANG. If the customer's config always matches the YANG, no problem. NSO will yell out if you load a file that contains unknown words/symbols.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 30 Aug 2018 10:23:33 GMT</pubDate>
    <dc:creator>Jan Lindblad</dc:creator>
    <dc:date>2018-08-30T10:23:33Z</dc:date>
    <item>
      <title>IOS NED different for different IOS versions?</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/ios-ned-different-for-different-ios-versions/m-p/3696969#M2530</link>
      <description>&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;Hi,&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;for an upcoming PoC I have been sent a sample configuration and tried to test whether the IOS NED supports all the configurations required by the customer.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;I am using NSO 4.7 and IOS NED version&amp;nbsp;6.1.2.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;Here is the config which causes me concern:&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;FONT face="courier new,courier"&gt;int ${Int}
 switchport trunk allowed vlan add ${KNVLANID}&lt;/FONT&gt;&lt;/PRE&gt;
&lt;P&gt;Note: ${Int} will be some actual Interface Name (e.g. Ethernet0/0/0) and&amp;nbsp;${KNVLANID} will be a valid Vlan ID.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The problem I discovered is:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When I spin up a netsim device using the above mentioned NED and type in the config I only get&amp;nbsp;so far...up to&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;FONT face="courier new,courier"&gt;switchport trunk allowed &lt;STRONG&gt;vlan&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/PRE&gt;
&lt;P&gt;Then the NED says the device would expect&amp;nbsp;the following:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;FONT face="courier new,courier"&gt;ios0(config-if)# switchport trunk allowed vlan ?
  WORD   VLAN IDs of the allowed VLANs when this port is in trunking mode
  none   no VLANs
&lt;/FONT&gt;&lt;/PRE&gt;
&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;So my question is:&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;Is it a mistake in the NED that it doesnt expect "add" followed by the VLAN ID? Or is this something that maybe behaves differently depending on which IOS/IOS-XE version is used on the actual device?&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;The used versions at the customer site are:&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;&lt;SPAN style="font-weight: 400;"&gt;- Cisco IOS Software, c6880x Software (c6880x-IPSERVICESK9-M), Version 15.1(2)SY7&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;&lt;SPAN style="font-weight: 400;"&gt;- Cisco IOS Software, C800 Software (C800-UNIVERSALK9-M), Version 15.3(3)M5&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;&lt;SPAN style="font-weight: 400;"&gt;- Cisco IOS XE Software, Version 16.03.02&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN style="font-weight: 400;"&gt;Cisco IOS Software [Denali], ASR1000 Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 16.3.2&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;&lt;SPAN style="font-weight: 400;"&gt;If it is a mistake/error/bug in the NED I would like to contact the NED team for a fix/enhancement as soon as possible but I do not want to contact them before I know for sure that there isn't some other fix already available (e.g. a different NED version?).&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;&lt;SPAN style="font-weight: 400;"&gt;I also noticed that when I do&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;FONT face="courier new,courier"&gt;interface vlan&lt;/FONT&gt;&lt;/PRE&gt;
&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;a real device doesn't seem to be bothered about whether it is a capital V (in Vlan) or a lower case v (vlan).&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;&lt;SPAN style="font-weight: 400;"&gt;The NED does seem to mind whether upper or lower case is used:&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;FONT face="courier new,courier"&gt;ios0(config)# interface V? 
  Video              video service interface
  Virtual-Template   Virtual Template interface
  VirtualPortGroup   Virtual Port Group
  Vlan               Vlan interface
ios0(config)# interface v?
  vasileft    VasiLeft interface
  vasiright   VasiRight interface
&lt;/FONT&gt;&lt;/PRE&gt;
&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;Is that something I have to worry about (as the sample config the customer provided always uses lower case)?&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 29 Aug 2018 12:53:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/ios-ned-different-for-different-ios-versions/m-p/3696969#M2530</guid>
      <dc:creator>ian.scheidler1</dc:creator>
      <dc:date>2018-08-29T12:53:25Z</dc:date>
    </item>
    <item>
      <title>Re: IOS NED different for different IOS versions?</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/ios-ned-different-for-different-ios-versions/m-p/3697756#M2535</link>
      <description>&lt;BLOCKQUOTE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;HR /&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;FONT face="courier new,courier"&gt;switchport trunk allowed &lt;STRONG&gt;vlan&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/PRE&gt;
&lt;P&gt;Then the NED says the device would expect&amp;nbsp;the following:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;FONT face="courier new,courier"&gt;ios0(config-if)# switchport trunk allowed vlan ?
  WORD   VLAN IDs of the allowed VLANs when this port is in trunking mode
  none   no VLANs
&lt;/FONT&gt;&lt;/PRE&gt;
&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;So my question is:&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;Is it a mistake in the NED that it doesnt expect "add" followed by the VLAN ID? Or is this something that maybe behaves differently depending on which IOS/IOS-XE version is used on the actual device?&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;No, this is as it should be. The YANG model of the device does not include action verbs like "add". This only makes sense in a CLI world, and not in clean interfaces like e.g. NETCONF, so the YANG models do not have this. The VLAN you mention will be added if it is new, updated otherwise.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;BLOCKQUOTE&gt;&lt;HR /&gt;
&lt;PRE&gt;&lt;FONT face="courier new,courier"&gt;interface vlan&lt;/FONT&gt;&lt;/PRE&gt;
&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;a real device doesn't seem to be bothered about whether it is a capital V (in Vlan) or a lower case v (vlan).&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;&lt;SPAN style="font-weight: 400;"&gt;The NED does seem to mind whether upper or lower case is used:&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Yes, the NED follows the YANG module exactly, and there it was modeled as lowercase.&amp;nbsp;&lt;SPAN style="font-family: inherit;"&gt;Allowing multiple spellings only really makes sense in a CLI, and not in e.g. NETCONF. IIRC it is possible to configure NSO to ignore upper/lowercase in the CLI (and internally pick the spelling used in the YANG), if you really want that.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;BLOCKQUOTE&gt;&lt;HR /&gt;
&lt;P&gt;&amp;nbsp;Is that something I have to worry about (as the sample config the customer provided always&lt;/P&gt;
&lt;P&gt;uses lower case)?&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Well, your CLI commands and your code needs to use the right spelling (case), as defined in the YANG. If the customer's config always matches the YANG, no problem. NSO will yell out if you load a file that contains unknown words/symbols.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 30 Aug 2018 10:23:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/ios-ned-different-for-different-ios-versions/m-p/3697756#M2535</guid>
      <dc:creator>Jan Lindblad</dc:creator>
      <dc:date>2018-08-30T10:23:33Z</dc:date>
    </item>
  </channel>
</rss>

