Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- :
- About tsiemers1
08-21-2019
Stats
Member since
02-24-2015
66
Posts
5
Helpful
1
Solution
08-07-2019
06:26 AM
Just upgraded to 4.7.4.3, saw in changelog this was fixed in 4.7.4.1. Works now. - restconf: Corrected the body format of yang-patch-status response message in success cases. (ENG-20606, RT:36346, PS-31425)
... View more
Created by
tsiemers1
in NSO Developer Hub Documents
in NSO Developer Hub Documents
07-31-2019
12:13 PM
07-31-2019
12:13 PM
Just finished the book, highly recommended for anybody getting into the NETCONF and yang. Very good read with examples to go along with it.
... View more
07-31-2019
12:09 PM
Testing out trying to use yang-patch (rfc 8072) for pushing two edits of the same service in one restconf call. I can get the yang-patch to work fine and it creates two services and commits them with the one call. The problem I am running into is not getting a response from yang-patch. Per the RFC section 2.6: If a YANG Patch is completed without errors, the RESTCONF server MUST
return a "yang-patch-status" message with a "global-status" choice
set to "ok".
Refer to Appendix A.1.2 for an example of a successful YANG Patch
response. Currently with postman, curl, or python calls I am getting 500 internal errors. Am I missing a step that will show the yang-patch-status? Attached is yang, below the restconf call. RESTCONF: (Shell Curl) curl --request PATCH \
--url http://ncslab.com:8080/restconf/data/patch-service-test \
--header 'Accept: application/yang-data+json' \
--header 'Authorization: Basic daaaaaaaaaaaaa2Ux' \
--header 'Content-Type: application/yang-patch+json' \
--data 'service_patch.json' service_patch.json {
"ietf-yang-patch:yang-patch": {
"patch-id": "patch-1",
"comment": "Test Patch responses",
"edit": [
{
"edit-id": "edit1",
"operation": "create",
"target": "/",
"value": {
"patch-service-test:patch-service-test": [
{
"patch-service-test:circuit_id": "patch_yang_CID_1",
"patch-service-test:name": "patch_description1",
"patch-service-test:deviceName": "xe_virl",
"patch-service-test:deviceID": "1111",
"patch-service-test:deviceType": "cisco-ios",
"patch-service-test:interfaceType": "GigabitEthernet",
"patch-service-test:interfaceName": "0/0/0"
}
]
}
},
{
"edit-id": "edit2",
"operation": "create",
"target": "/",
"value": {
"patch-service-test:patch-service-test": [
{
"patch-service-test:circuit_id": "patch_yang_CID_2",
"patch-service-test:name": "patch_description2",
"patch-service-test:deviceName": "xe_virl",
"patch-service-test:deviceID": "1111",
"patch-service-test:deviceType": "cisco-ios",
"patch-service-test:interfaceType": "GigabitEthernet",
"patch-service-test:interfaceName": "0/0/0"
}
]
}
}
]
}
} The server just responds with the following: 500 Internal Server Error Logs from NSO just show the service being created and a commit performed by rest. Can more verbose logging be turned on or something added to the restconf call to get the response part working?
... View more
Created by
tsiemers1
in NSO Developer Hub Discussions
in NSO Developer Hub Discussions
07-30-2019
06:11 AM
07-30-2019
06:11 AM
Looks like you can add dirs as load paths in nso.conf. I think my process now is to create yangs, run make command to get the .fxs and move it to the load directory specified in ncs.conf <load-path> <dir>./packages</dir> <dir>${NCS_DIR}/etc/ncs</dir> <!-- To disable northbound snmp altogether --> <!-- comment out the path below --> <dir>${NCS_DIR}/etc/ncs/snmp</dir> </load-path>
... View more
Created by
tsiemers1
in NSO Developer Hub Discussions
in NSO Developer Hub Discussions
07-29-2019
08:35 PM
07-29-2019
08:35 PM
I put my custom test-external-pkg.yang into the /opt/ncs/current/src/ncs/yang directory where all the other default yang files ( for example ietf-inet-types.yang) Then ran the make command, it created my test-external-pkg.fxs inside of the /opt/ncs/current/src/ncs/yang. After watching the debug logs of NSO trying to start I noticed that all the other default .fxs files were located in: /opt/ncs/ncs-4.7.2/etc/ncs/ I manually moved my test-external-pkg.fxs to that above directory and it worked. sudo mv /opt/ncs/current/src/ncs/yang/test-external-pkg.fxs /opt/ncs/ncs-4.7.2/etc/ncs/ Still looking for docs on the correct process of adding a custom yang then getting the .fxs to create in the proper load directory. Thinking something with the way I am running the make command. Thanks
... View more
Created by
tsiemers1
in NSO Developer Hub Discussions
in NSO Developer Hub Discussions
07-29-2019
06:40 PM
07-29-2019
06:40 PM
Just read over the Yang Schema mount rfc, looks very handy. Any plans to release it to more than NEDS? Also, I must be missing something trivial on getting external yang files to work in my package. I created the following structure to test a custom yang file in the /opt/ncs/current/src/ncs/yang directory. /opt/ncs/ncs-4.7.2/src/ncs/yang/
└── test-external-pkg.yang
module test-external-pkg {
namespace "http://example.com/test-external-pkg";
prefix tpext;
} When I run make on my test package src folder it comes back fine. When I went to reload NSO I got a namespace error. I tried adding it as a required-package in the package-meta-data.xml, thinking this is not the right approach but I find a similar error on this post so I tried it. <ncs-package xmlns="http://tail-f.com/ns/ncs-packages">
<name>testpkg</name>
<package-version>1.0</package-version>
<description>Generated Python package</description>
<ncs-min-version>4.7</ncs-min-version>
<required-package>
<name>test-external-pkg</name>
</required-package>
<component>
<name>main</name>
<application>
<python-class-name>testpkg.main.Main</python-class-name>
</application>
</component>
</ncs-package> The reload gives the error that the package is undefined so I must be missing a piece since this isn't a package, only a single yang file. Error: Failed to load NCS package: testpkg; required package test-external-pkg of version undefined is not present (found none)
... View more
Created by
tsiemers1
in NSO Developer Hub Discussions
in NSO Developer Hub Discussions
07-29-2019
09:44 AM
07-29-2019
09:44 AM
I am looking over the guides and trying to find information on the correct way to use external yang files. For example, lets say I do not want to recreate ethernet-groupings for XE and just want to import Cisco's submodule Cisco-IOS-XE-interfaces and from there use the grouping grouping ethernet-grouping Would I just copying over the "Cisco-IOS-XE-interfaces" over to the "/opt/ncs/ncs-4.7.3.1/src/ncs/yang" folder that contains all the other default talif/ietf yang files and then import it into my yang? module TESTPKG {
namespace "http://example.com/TESTPKG";
prefix TESTPKG;
import Cisco-IOS-XE-native {
prefix xe;
}
} Is this recommended our is a better method preferred over copying the source yang files? Or is it better to use the ios-ned and create choices/groupings similar to the accepted solution in this thread? Thanks
... View more
Labels:
Created by
tsiemers1
in NSO Developer Hub Discussions
in NSO Developer Hub Discussions
07-29-2019
07:00 AM
07-29-2019
07:00 AM
You can use the following xpath function current() to set the path back to the current node, in this case Interface-Description. You went ../name/.. to get out of the list and into the ncs:config. Using current()/../intf-number will bring you back to the Interface-Description then up one back to intf-number to get value. leaf Interface-Description {
tailf:info "Interface specific description";
type leafref {
path "deref(../name)/../ncs:config/ios:interface/ios:GigabitEthernet[ios:name=current()/../intf-number]/ios:description";
}
}
... View more
Created by
tsiemers1
in NSO Developer Hub Discussions
in NSO Developer Hub Discussions
07-24-2019
01:47 PM
07-24-2019
01:47 PM
Thanks, Currently we are working on using the code (python) to evaluate the device and see if that vrf exists and if its current RD matches the one passed into the service. If it doesn't match the current one we will just display a log message or error message to notify the user that the RD wasn't changed. Was wondering if I was using the create tag wrong or missing something since it works on vrf itself just not the child nodes under it. Working: <name tags="create">{/VRF_NAME}</name> but that does just as you mentioned and causes an exception.
... View more
Created by
tsiemers1
in NSO Developer Hub Discussions
in NSO Developer Hub Discussions
07-24-2019
12:37 PM
07-24-2019
12:37 PM
Testing with a vrf configuration to push out vrfs for a l3vpn service. When pushing a vrf we don't want to overwrite a vrf RD if it already exists for that vrf. Doing so on a 920 ios-xe deletes the route targets and disrupts traffic. I tried to use the xml tag 'create' to tell the service not to overwirte the RD node, but I am finding that even if the RD node is already set and sync'd to the NSO it will still overwrite it. create: Creates a node. The node can not already exist. An error is raised if the node exists. Is this not correct that it should error out since the node already exist? I am not seeing that result Template:
<config-template xmlns="http://tail-f.com/ns/config/1.0"
servicepoint="VRF_TEST">
<devices xmlns="http://tail-f.com/ns/ncs">
<device>
<name>{/device}</name>
<config>
<vrf xmlns="urn:ios">
<definition>
<name>{/VRF_NAME}</name>
<rd tags="create">9999:{/RD}</rd>
<address-family>
<ipv4>
<route-target>
<export>
<asn-ip>9999:{/RTE}</asn-ip>
</export>
<import>
<asn-ip>9999:{/RTI}</asn-ip>
</import>
</route-target>
</ipv4>
</address-family>
</definition>
</vrf>
</config>
</device>
</devices>
</config-template> Router Before: CQ6CORPLBB12#sh run vrf VRF_CREATE_TEST
Building configuration...
Current configuration : 99 bytes
vrf definition VRF_CREATE_TEST
rd 9999:5222
!
address-family ipv4
route-target export 9999:5201
route-target import 9999:5201
exit-address-family
!
!
end After commit: CQ6CORPLBB12#sh vrf VRF_CREATE_TEST
Name Default RD Protocols Interfaces
VRF_CREATE_TEST <being deleted> ipv4
CQ6CORPLBB12#sh vrf VRF_CREATE_TEST
Name Default RD Protocols Interfaces
VRF_CREATE_TEST 9999:5444 ipv4
CQ6CORPLBB12#sh run vrf VRF_CREATE_TEST
Building configuration...
Current configuration : 99 bytes
vrf definition VRF_CREATE_TEST
rd 9999:5444
!
address-family ipv4
exit-address-family
!
!
end commit dry-run | debug template tas3@labncs(config)# VRF_TEST test2 device CQ6CORPLBB12 VRF_NAME VRF_CREATE_TEST RD 5444 RTE 5201 RTI 5201
tas3@labncs(config-VRF_TEST-test2)# commit dry-run | debug template
Evaluating "/device" (from file "VRF_TEST-template.xml", line 5)
Context node: /VRF_TEST[name='test2']
Result:
For /VRF_TEST[name='test2']/device[.='CQ6CORPLBB12'], it evaluates to "CQ6CORPLBB12"
Operation 'merge' on existing node: /devices/device[name='CQ6CORPLBB12'] (from file "VRF_TEST-template.xml", line 5)
Evaluating "/VRF_NAME" (from file "VRF_TEST-template.xml", line 9)
Context node: /VRF_TEST[name='test2']/device[.='CQ6CORPLBB12']
Result:
For /VRF_TEST[name='test2'], it evaluates to "VRF_CREATE_TEST"
Operation 'merge' on existing node: /devices/device[name='CQ6CORPLBB12']/config/ios:vrf/definition[name='VRF_CREATE_TEST'] (from file "VRF_TEST-template.xml", line 9)
Operation 'create' on node: /devices/device[name='CQ6CORPLBB12']/config/ios:vrf/definition[name='VRF_CREATE_TEST']/rd (from file "VRF_TEST-template.xml", line 10)
Fetching literal "9999:" (from file "VRF_TEST-template.xml", line 10)
Evaluating "/RD" (from file "VRF_TEST-template.xml", line 10)
Context node: /VRF_TEST[name='test2']
Result:
For /VRF_TEST[name='test2'], it evaluates to "5444"
Setting /devices/device[name='CQ6CORPLBB12']/config/ios:vrf/definition[name='VRF_CREATE_TEST']/rd to "9999:5444"
Operation 'merge' on existing node: /devices/device[name='CQ6CORPLBB12']/config/ios:vrf/definition[name='VRF_CREATE_TEST']/address-family/ipv4 (from file "VRF_TEST-template.xml", line 12)
Fetching literal "9999:" (from file "VRF_TEST-template.xml", line 15)
Evaluating "/RTE" (from file "VRF_TEST-template.xml", line 15)
Context node: /VRF_TEST[name='test2']
Result:
For /VRF_TEST[name='test2'], it evaluates to "5201"
Operation 'merge' on existing node: /devices/device[name='CQ6CORPLBB12']/config/ios:vrf/definition[name='VRF_CREATE_TEST']/address-family/ipv4/route-target/export[asn-ip='9999:5201'] (from file "VRF_TEST-template.xml", line 15)
Fetching literal "9999:" (from file "VRF_TEST-template.xml", line 18)
Evaluating "/RTI" (from file "VRF_TEST-template.xml", line 18)
Context node: /VRF_TEST[name='test2']
Result:
For /VRF_TEST[name='test2'], it evaluates to "5201"
Operation 'merge' on existing node: /devices/device[name='CQ6CORPLBB12']/config/ios:vrf/definition[name='VRF_CREATE_TEST']/address-family/ipv4/route-target/import[asn-ip='9999:5201'] (from file "VRF_TEST-template.xml", line 18)
cli {
local-node {
data +VRF_TEST test2 {
+ device [ CQ6CORPLBB12 ];
+ RD 5444;
+ VRF_NAME VRF_CREATE_TEST;
+ RTI 5201;
+ RTE 5201;
+}
devices {
device CQ6CORPLBB12 {
config {
ios:vrf {
definition VRF_CREATE_TEST {
- rd 9999:5222;
+ rd 9999:5444;
}
}
}
}
}
}
}
tas3@labncs(config-VRF_TEST-test2)# commit
Commit complete. Operation 'create' on node: /devices/device[name='CQ6CORPLBB12']/config/ios:vrf/definition[name='VRF_CREATE_TEST']/rd (from file "VRF_TEST-template.xml", line 10)
Fetching literal "9999:" (from file "VRF_TEST-template.xml", line 10)
Evaluating "/RD" (from file "VRF_TEST-template.xml", line 10)
Context node: /VRF_TEST[name='test2']
Result:
For /VRF_TEST[name='test2'], it evaluates to "5444"
Setting /devices/device[name='CQ6CORPLBB12']/config/ios:vrf/definition[name='VRF_CREATE_TEST']/rd to "9999:5444"
... View more
Labels:
Created by
tsiemers1
in NSO Developer Hub Discussions
in NSO Developer Hub Discussions
06-18-2019
07:53 AM
06-18-2019
07:53 AM
Thanks, @Michael Maddern Was able to work over most of this during Live this year. I ended up changing it as you recommended above to close the transaction outside of the wait function. I do however think the right way to approach this is to use the example you referenced 'Action request without transaction', just tested and this way works and in my opinion is the correct way to handle the ios exec commands. All that said we ended up scraping this service and using CSM to do the upgrade of devices. Thanks!
... View more
Created by
tsiemers1
in NSO Developer Hub Discussions
in NSO Developer Hub Discussions
05-30-2019
10:46 AM
05-30-2019
10:46 AM
@lmanor Thanks, for the link to the transaction slides. The part I am stuck on is when the registered path is changed and the subscriber kicks off it will only handle one commit change at a time before moving on to the next one. Say user A makes a commit to the registered path, it kicks off the subscriber, gets iterated and starts the post_iterate. Then user B commits a change to the registered path a min later, subscriber sees the change and iterates the change, but waits to run post_iterate until user A's post_iterate is done. What I am looking for is if the subscriber has the ability to run both users A request and user B request in post_iterate at the same time in different threads. In the below user B's request makes it to the iterate function but will not be processed until user A has finished post_iterate function write_result. Wondering if this isn't the right way to be kicking something like this off, the problem is it upgrades the router, reloads and waits for it to come back to do some post checks in the write_result function within post_iterate. Which causes user B's request to the /iosxe-upgrade/request/device to sit until post_iterate finishes the first one which could be 20-25 mins. class IosxeUpgrade(Subscriber):
def init(self):
self.register('/iosxe-upgrade/request/device')
def pre_iterate(self):
return []
def iterate(self, kp, op, oldval, newval, state):
if op is ncs.MOP_VALUE_SET:
self.log.info('New IOS upgrade request: %s' % (str(kp[1:])))
state.append((newval, str(kp[1:])))
return ncs.ITER_RECURSE
def post_iterate(self, state):
for request in state:
self.write_result(ios_upgrade(self.log, request[0], request[1]), request[1])
def should_post_iterate(self, state):
return state != [] I read over the API for subscriber but it's either not possible or I am missing something with getting post_iterate to run per request. Thanks
... View more
Created by
tsiemers1
in NSO Developer Hub Discussions
in NSO Developer Hub Discussions
05-29-2019
12:16 PM
05-29-2019
12:16 PM
Currently running a subscriber that is watching an action. The subscriber works and kicks off when the registered path is updated. If I make multiple changes to the registered path it will wait until it is done with the first notification then on to the next one. Is it possible for the subscriber to run with multiple threads. The path the subscriber is registered takes devices names as input, then the subscriber runs some code on each device. Thanks,
... View more
Labels:
Created by
tsiemers1
in NSO Developer Hub Discussions
in NSO Developer Hub Discussions
05-28-2019
09:31 AM
05-28-2019
09:31 AM
You can use the api to retrive this info. Below is a python example for restconf to get the ncs-state. If you go to the console and run the command you are instersted in with a ' | display keypath' you can get the path to the data. The python example below will retrive the ncs-state version, you will have to modify it and change url and port, and include your user/password in the headers. nsouser@labncs# show ncs-state version | display keypath
/ncs-state/version 4.7.3.1
Python example: import requests
url = "http://<ncs-server.com>:<ncs-port>/restconf/data/ncs-state/version"
payload = ""
headers = {
'Accept': "*/*",
'Cache-Control': "no-cache",
'Host': "<ncs-server>:<ncs-port>",
'accept-encoding': "gzip, deflate",
'Connection': "keep-alive",
'cache-control': "no-cache"
}
response = requests.request("GET", url, data=payload, headers=headers)
print(response.text) Response: <version xmlns="http://tail-f.com/yang/ncs-monitoring" xmlns:tfnm="http://tail-f.com/yang/ncs-monitoring">4.7.3.1</version>
... View more
08-07-2019
Just upgraded to 4.7.4.3, saw in changelog this was fixed in 4.7.4.1.
Works now. - restconf: Correct...
07-31-2019
Just finished the book, highly recommended for anybody getting into the
NETCONF and yang. Very good ...
07-31-2019
Testing out trying to use yang-patch (rfc 8072) for pushing two edits of
the same service in one res...
Created by
tsiemers1
in NSO Developer Hub Discussions
07-30-2019
07-30-2019
Looks like you can add dirs as load paths in nso.conf. I think my
process now is to create yangs, ru...
Created by
tsiemers1
in NSO Developer Hub Discussions
07-29-2019
07-29-2019
I put my custom test-external-pkg.yang into the
/opt/ncs/current/src/ncs/yang directory where all th...
Created by
tsiemers1
in NSO Developer Hub Discussions
07-29-2019
07-29-2019
Just read over the Yang Schema mount rfc, looks very handy. Any plans to
release it to more than NED...
Created by
tsiemers1
in NSO Developer Hub Discussions
07-29-2019
07-29-2019
I am looking over the guides and trying to find information on the
correct way to use external yang ...
Created by
tsiemers1
in NSO Developer Hub Discussions
07-29-2019
07-29-2019
You can use the following xpath function current() to set the path back
to the current node, in this...
Created by
tsiemers1
in NSO Developer Hub Discussions
07-24-2019
07-24-2019
Thanks, Currently we are working on using the code (python) to evaluate
the device and see if that v...
Created by
tsiemers1
in NSO Developer Hub Discussions
07-24-2019
07-24-2019
Testing with a vrf configuration to push out vrfs for a l3vpn service.
When pushing a vrf we don't w...
Created by
tsiemers1
in NSO Developer Hub Discussions
06-18-2019
06-18-2019
Thanks, @Michael Maddern Was able to work over most of this during Live
this year. I ended up changi...
Created by
tsiemers1
in NSO Developer Hub Discussions
05-30-2019
05-30-2019
@lmanor Thanks, for the link to the transaction slides. The part I am
stuck on is when the registere...
05-29-2019
Currently running a subscriber that is watching an action. The
subscriber works and kicks off when t...
Created by
tsiemers1
in NSO Developer Hub Discussions
05-28-2019
05-28-2019
You can use the api to retrive this info. Below is a python example for
restconf to get the ncs-stat...
Public Statistics
| Date Registered | 02-24-2015 08:22 AM |
| Date Last Visited | 08-21-2019 12:28 AM |
| Total Messages Posted | 66 |
| Total Helpful Votes Received | 5 |
