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 brfoster
Stats
Member since
12-12-2005
34
Posts
9
Helpful
1
Solution
Created by
brfoster
in YANG Development Kit (YDK)
in YANG Development Kit (YDK)
11-19-2019
09:59 AM
11-19-2019
09:59 AM
Team,
Can someone post example YDK code for configuring interface encapsulation? Like this XML...
< config >
< interface-configurations xmlns ="http://cisco.com/ns/yang/Cisco-IOS-XR-ifmgr-cfg" >
< interface-configuration >
< active > act </ active >
< interface-name > HundredGigE0/0/1/0.11 </ interface-name >
< interface-mode-non-physical > l2-transport </ interface-mode-non-physical >
< ethernet-service xmlns ="http://cisco.com/ns/yang/Cisco-IOS-XR-l2-eth-infra-cfg" >
< encapsulation >
< outer-tag-type > match-dot1q </ outer-tag-type >
< outer-range1-low > 1011 </ outer-range1-low >
</ encapsulation >
</ ethernet-service >
... View more
Labels:
Created by
brfoster
in Communities of Interest
in Communities of Interest
11-16-2019
02:16 PM
11-16-2019
02:16 PM
Hi, I'm closing this query. I realized I needed gpb endoding instead of json. That fixed my issue and it works now with both Pipeline and Telegraf.
destination-group DGroup2
address-family ipv4 172.16.1.189 port 57500
encoding self-describing-gpb
protocol tcp
!
!
... View more
Created by
brfoster
in Communities of Interest
in Communities of Interest
11-15-2019
10:01 AM
11-15-2019
10:01 AM
Team,
In my testbed I have pipeline working with xrv9000 devices with gRPC telemetry. Everything is working properly and writing to the Influx database and also I can use the Grafana.
However, if I change the telemetry to messages to use JSON/TCP, it stops writing to the Influx database.
But, I can still see the messages coming and written to the dump.txt log file.
I'm just using the standard metrics.json file and the Cisco-IOS-XR-infra-statsd-oper:infra-statistics/interfaces/interface/latest/generic-counters sensor path.
If I change the messages back to gRPC it starts working again!
The original examples Shelly has in her blog were using TCP, so I'm not sure if something has been broken since then?
... View more
Labels:
05-24-2018
10:06 AM
I'm hitting an error trying to install the YDK, can someone please help? (ydkenv) [gibson@nso1 ~]$ pip list Package Version ---------- ------- pip 10.0.1 setuptools 39.2.0 wheel 0.31.1 (ydkenv) [gibson@nso1 ~]$ pip install ydk-models-cisco-ios-xr Collecting ydk-models-cisco-ios-xr Collecting ydk>=0.7.1 (from ydk-models-cisco-ios-xr) Using cached https://files.pythonhosted.org/packages/e9/b4/799d2ecd94658c764c50f503d345bc31db2231973b3bb19a5459620f87a6/ydk-0.7.1.tar.gz Collecting ydk-models-ietf>=0.1.5 (from ydk-models-cisco-ios-xr) Collecting pybind11>=2.1.1 (from ydk>=0.7.1->ydk-models-cisco-ios-xr) Using cached https://files.pythonhosted.org/packages/12/90/0f92a575dc60c8fba6d0c91d6b45abdb1058da9ebed40400cbcfad2ac0a7/pybind11-2.2.3-py2.py3-none-any.whl Building wheels for collected packages: ydk Running setup.py bdist_wheel for ydk ... error Complete output from command /home/gibson/venvs/ydkenv/bin/python2.7 -u -c "import setuptools, tokenize;__file__='/tmp/pip-install-mSxrK8/ydk/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" bdist_wheel -d /tmp/pip-wheel-fpN2aj --python-tag cp27: running bdist_wheel running build running build_py creating build creating build/lib.linux-x86_64-2.7 creating build/lib.linux-x86_64-2.7/ydk copying ydk/__init__.py -> build/lib.linux-x86_64-2.7/ydk copying ydk/exthook.py -> build/lib.linux-x86_64-2.7/ydk creating build/lib.linux-x86_64-2.7/ydk/entity_utils copying ydk/entity_utils/__init__.py -> build/lib.linux-x86_64-2.7/ydk/entity_utils copying ydk/entity_utils/entity_utils.py -> build/lib.linux-x86_64-2.7/ydk/entity_utils creating build/lib.linux-x86_64-2.7/ydk/errors copying ydk/errors/__init__.py -> build/lib.linux-x86_64-2.7/ydk/errors copying ydk/errors/error_handler.py -> build/lib.linux-x86_64-2.7/ydk/errors creating build/lib.linux-x86_64-2.7/ydk/ext copying ydk/ext/__init__.py -> build/lib.linux-x86_64-2.7/ydk/ext creating build/lib.linux-x86_64-2.7/ydk/filters copying ydk/filters/__init__.py -> build/lib.linux-x86_64-2.7/ydk/filters creating build/lib.linux-x86_64-2.7/ydk/logging copying ydk/logging/__init__.py -> build/lib.linux-x86_64-2.7/ydk/logging creating build/lib.linux-x86_64-2.7/ydk/models copying ydk/models/__init__.py -> build/lib.linux-x86_64-2.7/ydk/models creating build/lib.linux-x86_64-2.7/ydk/path copying ydk/path/__init__.py -> build/lib.linux-x86_64-2.7/ydk/path creating build/lib.linux-x86_64-2.7/ydk/providers copying ydk/providers/__init__.py -> build/lib.linux-x86_64-2.7/ydk/providers copying ydk/providers/codec_provider.py -> build/lib.linux-x86_64-2.7/ydk/providers creating build/lib.linux-x86_64-2.7/ydk/services copying ydk/services/__init__.py -> build/lib.linux-x86_64-2.7/ydk/services copying ydk/services/codec_service.py -> build/lib.linux-x86_64-2.7/ydk/services copying ydk/services/crud_service.py -> build/lib.linux-x86_64-2.7/ydk/services copying ydk/services/executor_service.py -> build/lib.linux-x86_64-2.7/ydk/services copying ydk/services/netconf_service.py -> build/lib.linux-x86_64-2.7/ydk/services creating build/lib.linux-x86_64-2.7/ydk/types copying ydk/types/__init__.py -> build/lib.linux-x86_64-2.7/ydk/types copying ydk/types/py_types.py -> build/lib.linux-x86_64-2.7/ydk/types creating build/lib.linux-x86_64-2.7/ydk/path/sessions copying ydk/path/sessions/__init__.py -> build/lib.linux-x86_64-2.7/ydk/path/sessions copying ydk/path/sessions/netconf_session.py -> build/lib.linux-x86_64-2.7/ydk/path/sessions copying ydk/path/sessions/restconf_session.py -> build/lib.linux-x86_64-2.7/ydk/path/sessions running build_ext Traceback (most recent call last): File "<string>", line 1, in <module> File "/tmp/pip-install-mSxrK8/ydk/setup.py", line 149, in <module> zip_safe=False, File "/home/gibson/venvs/ydkenv/lib/python2.7/site-packages/setuptools/__init__.py", line 129, in setup return distutils.core.setup(**attrs) File "/usr/lib64/python2.7/distutils/core.py", line 152, in setup dist.run_commands() File "/usr/lib64/python2.7/distutils/dist.py", line 953, in run_commands self.run_command(cmd) File "/usr/lib64/python2.7/distutils/dist.py", line 972, in run_command cmd_obj.run() File "/home/gibson/venvs/ydkenv/lib/python2.7/site-packages/wheel/bdist_wheel.py", line 202, in run self.run_command('build') File "/usr/lib64/python2.7/distutils/cmd.py", line 326, in run_command self.distribution.run_command(command) File "/usr/lib64/python2.7/distutils/dist.py", line 972, in run_command cmd_obj.run() File "/usr/lib64/python2.7/distutils/command/build.py", line 127, in run self.run_command(cmd_name) File "/usr/lib64/python2.7/distutils/cmd.py", line 326, in run_command self.distribution.run_command(command) File "/usr/lib64/python2.7/distutils/dist.py", line 972, in run_command cmd_obj.run() File "/tmp/pip-install-mSxrK8/ydk/setup.py", line 72, in run self.build_extension(ext) File "/tmp/pip-install-mSxrK8/ydk/setup.py", line 79, in build_extension pip.main(['install', 'pybind11>=2.1.1']) AttributeError: 'module' object has no attribute 'main' ---------------------------------------- Failed building wheel for ydk Running setup.py clean for ydk Failed to build ydk
... View more
Labels:
03-12-2018
10:59 AM
Hi, I'm getting a *lot* of errors when attempting to build a Netconf NED for NSO. I'm using the XR 6.3.1 YANG schema downloaded from Github. Here is a sample of the errors... [gibson@nso1 631]$ ncs-make-package --netconf-ned . iosxr-netconf-ned-631-full [gibson@nso1 631]$ ( cd iosxr-netconf-ned-631-full/src && make ) mkdir -p ncsc-out mkdir -p ../load-dir mkdir -p ../shared-jar mkdir -p ../private-jar /home/gibson/nso-4.5.3/bin/ncsc --ncs-compile-bundle yang \ --ncs-device-dir ncsc-out \ --ncs-device-type netconf \ && \ cp ncsc-out/modules/fxs/*.fxs ../load-dir; yang/openconfig-mpls-ldp.yang:97: error: the node 'tunnel-type' from module 'openconfig-mpls' (in node 'p2p-lsp' from 'openconfig-mpls') is not found yang/openconfig-mpls-ldp.yang:97: warning: The when expression refers to descendant node 'tunnel-type', will probably not work as intended. yang/openconfig-mpls-ldp.yang:114: error: the node 'tunnel-type' from module 'openconfig-mpls' (in node 'p2mp-lsp' from 'openconfig-mpls') is not found yang/openconfig-mpls-ldp.yang:114: warning: The when expression refers to descendant node 'tunnel-type', will probably not work as intended. yang/openconfig-mpls-ldp.yang:128: error: the node 'tunnel-type' from module 'openconfig-mpls' (in node 'mp2mp-lsp' from 'openconfig-mpls') is not found yang/openconfig-mpls-ldp.yang:128: warning: The when expression refers to descendant node 'tunnel-type', will probably not work as intended. yang/openconfig-mpls-rsvp.yang:521: error: restriction 'require-instance' is not valid for the base type in YANG version 1 yang/openconfig-mpls-sr.yang:335: error: the node 'tunnel-type' from module 'openconfig-mpls' (in node 'p2p-lsp' from 'openconfig-mpls') is not found yang/openconfig-mpls-sr.yang:335: warning: The when expression refers to descendant node 'tunnel-type', will probably not work as intended. yang/openconfig-mpls-te.yang:549: error: restriction 'require-instance' is not valid for the base type in YANG version 1 yang/openconfig-mpls-te.yang:587: error: restriction 'require-instance' is not valid for the base type in YANG version 1 yang/openconfig-mpls-te.yang:771: error: restriction 'require-instance' is not valid for the base type in YANG version 1 yang/openconfig-mpls-te.yang:1064: error: restriction 'require-instance' is not valid for the base type in YANG version 1 yang/openconfig-mpls-te.yang:1149: error: restriction 'require-instance' is not valid for the base type in YANG version 1 yang/openconfig-mpls-te.yang:1183: error: restriction 'require-instance' is not valid for the base type in YANG version 1 yang/openconfig-mpls-te.yang:1192: error: restriction 'require-instance' is not valid for the base type in YANG version 1 yang/openconfig-mpls.yang:354: error: restriction 'require-instance' is not valid for the base type in YANG version 1 yang/openconfig-mpls.yang:485: error: restriction 'require-instance' is not valid for the base type in YANG version 1 make: *** [ncsc-out/.done] Error 1 The only way to get the NED build to complete is to remove all the openconfig YANG files from the directory. Is this expected? Is this going to be fixed? Thanks, Brent
... View more
Labels:
Created by
brfoster
in Automation and Analytics
in Automation and Analytics
11-10-2017
09:41 AM
11-10-2017
09:41 AM
Team, Is there a way to create a plan file by RPC or other API call by referencing an ISIS database dump? I can do it from the WAE Design user interface but is there a way to do it by an API call? Thanks,
... View more
- Tags:
- wae
Labels:
Created by
brfoster
in YANG Development Kit (YDK)
in YANG Development Kit (YDK)
06-21-2017
09:00 AM
06-21-2017
09:00 AM
Hi, I’m sorry, not sure what you are asking? I just did… virtualenv -p python2.7 ydk-gen-venv-27 source ydk-gen-venv-27/bin/activate cd PythonProjects/ git clone https://github.com/CiscoDevNet/ydk-gen.git cd ydk-gen pip install -r requirements.txt python generate.py --python --bundle profiles/bundles/cisco-ios-xe_16_5_1.json -v --generate-doc Then, I tried to access the “index.html” file that gets created under… /home/gibson/PythonProjects/ydk-gen/gen-api/python/cisco_ios_xe-bundle/docs_expanded And that is where I found the mal-formed HTML files with the incorrect CSS file name. Thanks, Brent
... View more
Created by
brfoster
in YANG Development Kit (YDK)
in YANG Development Kit (YDK)
06-20-2017
02:04 PM
06-20-2017
02:04 PM
I found a bug with ydk-gen When you generate documentation using the --generate-doc flag the html files reference a CSS file that does not exist. This line gets put in the HTML <head> section of every page... <link rel="stylesheet" href="_static/css/width.css" type="text/css"> If you look in the "_static" directory you will see this file does not exist but the "theme.css" does exist. If you edit this to <link rel="stylesheet" href="_static/css/theme.css" type="text/css"> Then the pages load correctly.
... View more
Labels:
Created by
brfoster
in Collaboration Blogs
in Collaboration Blogs
10-26-2016
12:11 PM
10-26-2016
12:11 PM
I'm hitting the same issue. Did you solve it?
... View more
Created by
brfoster
in Automation and Analytics
in Automation and Analytics
10-26-2016
12:09 PM
10-26-2016
12:09 PM
Just tried with Beryllium and same issue RemoteDevice{iosxrv-1}: YANG schema was not successfully retrieved for SourceIdentifier [name=Cisco-IOS-XR-lpts-pre-ifib-oper-sub1@2016-02-22]. Errors: [RpcError [message=, severity=ERROR, errorType=APPLICATION, tag=operation-failed, applicationTag=null, info=, cause=null]]
... View more
Created by
brfoster
in Automation and Analytics
in Automation and Analytics
10-25-2016
04:30 PM
10-25-2016
04:30 PM
UPDATE I examined the logs for ODL (data/logs/karaf.log) and I can see ODL is trying to make a NETCONF connection but it is having trouble retrieving the YANG schema. Does IOS-XR support this? I didn't have this issue with the Beryllium release. Error reply from remote device, request: <rpc message-id="m-85" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <get-schema xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring"> <identifier>Cisco-IOS-XR-lpts-pre-ifib-oper-sub1</identifier> <version>2016-02-22</version> <format>yang</format> </get-schema> </rpc> , response: <rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="m-85"> <rpc-error> <error-type>application</error-type> <error-tag>operation-failed</error-tag> <error-severity>error</error-severity> </rpc-error> </rpc-reply> RemoteDevice{iosxrv-1}: YANG schema was not successfully retrieved for RevisionSourceIdentifier [name=Cisco-IOS-XR-lpts-pre-ifib-oper-sub1@2016-02-22]. Errors: [RpcError [message=, severity=ERROR, errorType=APPLICATION, tag=operation-failed, applicationTag=null, info=, cause=null]] Unable to build schema context, unsatisfied imports {RevisionSourceIdentifier [name=cisco-xr-netconf-monitoring-deviations@2016-02-16]=[ModuleImportImpl [name=ietf-netconf-monitoring, revision=null, semanticVersion=0.0.0]], RevisionSourceIdentifier [name=Cisco-IOS-XR-ha-eem-policy-oper@2016-02-05]=[ModuleImportImpl [name=Cisco-IOS-XR-ha-eem-policy-oper-sub1, revision=2016-02-05
... View more
Created by
brfoster
in Automation and Analytics
in Automation and Analytics
10-24-2016
12:53 PM
10-24-2016
12:53 PM
UPDATE I had extra quotes around the XML body that was causing the POST to fail. Now, when I query the RESTCONF interface... http://192.168.5.101:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/controller-config/yang-ext:mount/config:modules <module> <type>x:sal-netconf-connector</type> <name>iosxrv-1</name> <tcp-only>false</tcp-only> <event-executor> <type>x:netty-event-executor</type> <name>global-event-executor</name> </event-executor> <keepalive-executor> <type>x:scheduled-threadpool</type> <name>global-netconf-ssh-scheduled-executor</name> </keepalive-executor> <sleep-factor>1.5</sleep-factor> <max-connection-attempts>0</max-connection-attempts> <dom-registry> <type>x:dom-broker-osgi-registry</type> <name>dom-broker</name> </dom-registry> <client-dispatcher> <type>x:netconf-client-dispatcher</type> <name>global-netconf-dispatcher</name> </client-dispatcher> <concurrent-rpc-limit>0</concurrent-rpc-limit> <schema-cache-directory>schema</schema-cache-directory> <between-attempts-timeout-millis>2000</between-attempts-timeout-millis> <port>830</port> <connection-timeout-millis>20000</connection-timeout-millis> <username>cisco</username> <password>cisco</password> <processing-executor> <type>x:threadpool</type> <name>global-netconf-processing-executor</name> </processing-executor> <binding-registry> <type>x:binding-broker-osgi-registry</type> <name>binding-osgi-broker</name> </binding-registry> <keepalive-delay>120</keepalive-delay> <default-request-timeout-millis>60000</default-request-timeout-millis> <address>192.168.0.1</address> <reconnect-on-changed-schema>false</reconnect-on-changed-schema> </module> However, when I open DLUX and select "nodes" I do not see the element listed.
... View more
Created by
brfoster
in Automation and Analytics
in Automation and Analytics
10-24-2016
11:59 AM
10-24-2016
11:59 AM
Team, I made a script for interfacing with ODL BORON release RESTCONF interface for adding a node. I'm getting an error as shown below. Any idea what is wrong? (ydk-py-venv) [gibson@rickenbacker yangtesting]$ python addnode_odl.py hello from Python 2.7.12 (default, Jun 29 2016, 15:48:48) [GCC 4.4.7 20120313 (Red Hat 4.4.7-17)] The REST URL is http://192.168.5.101:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/controller-config/yang-ext:mount/config:modules The XML POST body is... "<module xmlns="urn:opendaylight:params:xml:ns:yang:controller:config"> <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">prefix:sal-netconf-connector</type> <name>iosxrv-1</name> <address xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">192.168.0.1</address> <port xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">830</port> <username xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">cisco</username> <password xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">cisco</password> <tcp-only xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">false</tcp-only> <event-executor xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"> <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:netty">prefix:netty-event-executor</type> <name>global-event-executor</name> </event-executor> <binding-registry xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"> <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">prefix:binding-broker-osgi-registry</type> <name>binding-osgi-broker</name> </binding-registry> <dom-registry xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"> <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:md:sal:dom">prefix:dom-broker-osgi-registry</type> <name>dom-broker</name> </dom-registry> <client-dispatcher xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"> <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:config:netconf">prefix:netconf-client-dispatcher</type> <name>global-netconf-dispatcher</name> </client-dispatcher> <processing-executor xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"> <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:threadpool">prefix:threadpool</type> <name>global-netconf-processing-executor</name> </processing-executor> <keepalive-executor xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"> <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:threadpool">prefix:scheduled-threadpool</type> <name>global-netconf-ssh-scheduled-executor</name> </keepalive-executor> </module>" 400 application/xml <?xml version="1.0" ?> <errors xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf"> <error> <error-type>protocol</error-type> <error-tag>malformed-message</error-tag> <error-message>Error parsing input: Content is not allowed in prolog.</error-message> </error> </errors> (ydk-py-venv) [gibson@rickenbacker yangtesting]$
... View more
- Tags:
- odl
- OpenDaylight
Labels:
Created by
brfoster
in YANG Development Kit (YDK)
in YANG Development Kit (YDK)
10-20-2016
11:05 AM
10-20-2016
11:05 AM
Actually, I did those steps twice already! In the log I posted earlier I had completely deleted the venv and ydk installation directories and started over. Could we do a WebEx?
... View more
Created by
brfoster
in YANG Development Kit (YDK)
11-19-2019
11-19-2019
Team, Can someone post example YDK code for configuring interface
encapsulation? Like this XML...
...
Created by
brfoster
in Communities of Interest
11-16-2019
11-16-2019
Hi, I'm closing this query. I realized I needed gpb endoding instead of
json. That fixed my issue an...
Created by
brfoster
in Communities of Interest
11-15-2019
11-15-2019
Team, In my testbed I have pipeline working with xrv9000 devices with
gRPC telemetry. Everything is ...
05-24-2018
I'm hitting an error trying to install the YDK, can someone please
help?(ydkenv) [gibson@nso1 ~]$ pi...
Created by
brfoster
in Automation and Analytics
11-10-2017
11-10-2017
Team,Is there a way to create a plan file by RPC or other API call by
referencing an ISIS database d...
Created by
brfoster
in YANG Development Kit (YDK)
06-21-2017
06-21-2017
Hi,I’m sorry, not sure what you are asking? I just did…virtualenv -p
python2.7 ydk-gen-venv-27source...
06-20-2017
I found a bug with ydk-genWhen you generate documentation using the
--generate-doc flag the html fil...
Created by
brfoster
in Collaboration Blogs
10-26-2016
10-26-2016
I'm hitting the same issue. Did you solve it?
Created by
brfoster
in Automation and Analytics
10-26-2016
10-26-2016
Just tried with Beryllium and same issue RemoteDevice{iosxrv-1}: YANG
schema was not successfully re...
Created by
brfoster
in Automation and Analytics
10-25-2016
10-25-2016
UPDATEI examined the logs for ODL (data/logs/karaf.log) and I can see
ODL is trying to make a NETCON...
Created by
brfoster
in Automation and Analytics
10-24-2016
10-24-2016
UPDATEI had extra quotes around the XML body that was causing the POST
to fail.Now, when I query the...
10-24-2016
Team,I made a script for interfacing with ODL BORON release RESTCONF
interface for adding a node. I'...
Created by
brfoster
in YANG Development Kit (YDK)
10-20-2016
10-20-2016
Actually, I did those steps twice already! In the log I posted earlier I
had completely deleted the ...
Public Statistics
| Date Registered | 12-12-2005 07:11 AM |
| Date Last Visited | 11-20-2019 12:05 AM |
| Total Messages Posted | 34 |
| Total Helpful Votes Received | 9 |
