All knowledge base posts in For Developers

Data Center Knowledge Base

alexstev — Tue, 01 Jun 2021 18:06:50 GMT

Data Center Knowledge Base

For one-on-one help with these products, you can open a ticket at https://developer.cisco.com/site/support/. For other products, please contact Cisco TAC at https://www.cisco.com/c/en/us/support/index.html

Data Center

Start

Data Center Dev Center - on Cisco DevNet
Cisco Data Center - Cisco Ecosystem Exchange
Data Center Automation - Infrastructure as Code in the Modern Data Center - on DevNet
Data Center - DevNet Code Exchange
Data Center - DevNet Automation Exchange

Learn

Data Center Networking - Cisco Blogs
Cisco Certified DevNet Specialist - Data Center Automation and Programmability - Certification
Automating and Programming Cisco Data Center Solutions - Exam Overview and Topics
Developer Data Center - Cisco Community forums
Data Center - Cisco Community forums
Cisco Data Center Network Manager - Releases / Documentation

Collaboration Management Knowledge Base

Paul Zimmerman — Mon, 24 May 2021 14:34:26 GMT

Collaboration Management Knowledge Base

Administrative XML (AXL)

Start

AXL on DevNet
AXL Docs - DevNet

Learn

Administrative XML (AXL) Developer Cookbook
AXL Forum - Cisco Community forums
Administrative XML (AXL) - DevNet Developer Support

Cisco Emergency Responder (CER)

Start

CER Get Started - Cisco DevNet
CER Overview - DevNet

Learn

Cisco Emergency Responder (CER) API Documentation - Cisco DevNet
CER Datasheets - DevNet

IOS XE VoIP

Start

IOS XE - Cisco DevNet
Cisco IOS XE Sandboxes - DevNet

Learn

Programmability Guide for Cisco IOS XE Unified Communications VoIP Products - Cisco DevNet
IOS XE Programmability - DevNet Learning Labs

Platform Administrative Web Services (PAWS)

Start

PAWS - Get Started - Cisco DevNet
PAWS Home - DevNet
PAWS Overview - DevNet

Learn

PAWS API Reference - Cisco DevNet
Build a Development Lab for PAWS - DevNet

UC Manager Serviceability (SXML)

Start

What is Unified CM Serviceability? - Cisco DevNet
SXML - DevNet

Learn

SXML - Getting Started - Cisco DevNet
Developer Collaboration (including SXML) - Cisco Community forums
UC Manager Serviceability (SXML) discussions - DevNet Developer Support

User Data Services (UDS)

Start

UDS - Get Started - Cisco DevNet
What is UDS? - DevNet
Why Use UDS? - DevNet
How Does UDS Work? - DevNet

Learn

UDS - How To - Cisco DevNet
Download the XML Schemas
Run the Sample App
Review the How to Articles - tips and tricks for working with UDS
Learn How to Build a Development Lab for UDS
UDS Developer Forums - Cisco
Explore the UDS APIs with a browser plug-in
Review the API Reference Guide - information about UDS including authentication, detailed descriptions, and example requests and responses.
Browse the Developer Guide - Comprehensive documentation including troubleshooting information
Subscribe to the UDS blog for updates

Networking Automation and Analytics Knowledge Base

alexstev — Wed, 05 May 2021 16:38:10 GMT

Networking Automation and Analytics Knowledge Base

Networking Automation and Analytics - Make Network Automation simple with the community.

Start

Automating Webex Teams (Python) - Leverage your favorite automation tools to incorporate Webex Teams REST APIs.
NSO Basics for Network Automation - Learn network programmability and Next Generation Orchestration using Cisco’s Network Service Orchestrator through theory and practice. Easily automate any networking vendor’s infrastructure at scale and see how NSO provides an incomparable API into both legacy CLI devices and RESTCONF/YANG model devices.
IOS-XR CLI Automation - Cisco IOS-XR offers a comprehensive portfolio of APIs at every layer of the network stack, allowing users to leverage automated techniques to provision and manage the lifecycle of a network device.
Cisco SD-WAN with Ansible - Learn the basics of SD-WAN automation with Ansible.
Using NAPALM for Network Automation - Accomplish network automation and device management with NAPALM.
Networking 101 - Learn coding basics for Networking.
EN Networking - Build Apps with Cisco DNA Center Platform Solutions.
DC Networking - Explore Application Centric Infrastructure (ACI) programmability options and explore data center APIs.

Learn

Cisco DevNet Learning Labs (Automation) - All DevNet Learning Labs tagged with the keyword 'Automation'
Cisco DevNet Learning Labs (Analytics) - All DevNet Learning Labs tagged with the keyword 'Analytics'
DevNet Automation Exchange - DevNet Automation Exchange provides shared code repositories for network automation and guides teams through their journey with a walk-run-fly methodology.
DevNet Automation Bootcamp - an intensive, 9-day course delivered over 6 weeks for a team of up to 12 learners. This schedule gives your team time to absorb the new material they’re learning as they apply it to your infrastructure and business needs.
Networking Dev Center - Learn how you can integrate with the network through full system management solutions in the cloud, utilize automation platforms and controllers, or directly interact with devices with APIs and Interfaces.

IDEs - an Integrated Development Environment (IDE) is a software package available for download and use that can help simplify the development process. IDEs integrate many of the common tasks in software development to enable rapid application development.

PyCharm - an IDE with full support for Python, as well as for HTML, CSS, JavaScript, Node.js and more.
Komodo - another IDE with full support for Python, as well as Go, Perl, Ruby and more.
VS Code - Visual Studio Code is technically not an IDE. It's a lightweight but powerful source code editor which runs on your desktop and is available for Windows, macOS and Linux. It comes with built-in support for several programming languages and has a rich ecosystem of extensions for other languages and runtimes.

SDKs - a software development kit (SDK) differs fundamentally from an IDE. An SDK is a set of functions, packages, documentation and programs required for development on a specific platform or technology, whereas an IDE can be thought of as providing tools for application development using a specific language or technology.

Sandboxes - Cisco and Networking are practically synonymous! The Sandbox offers many networking labs with SDN controllers or API driven network gear!

Networking Sandbox Highlights - on Cisco DevNet
Explore ALL Networking Sandboxes - on DevNet

Learning Labs - just like our Sandboxes, the Learning Labs on Cisco DevNet are FREE to use!

Networking Labs - all of the Networking Learning Labs on Cisco DevNet
Network Programmability for Network Engineers - Learning Track on DevNet

Cisco Modeling Labs - Cisco Modeling Labs (CML) is our premier platform for network simulation. With an easy-to-use HTML5 UI and a comprehensive API, Cisco Modeling Labs makes it fun to design, test, troubleshoot, and learn.

Cisco Modeling Labs - on Cisco DevNet

Postman - Postman can be utilized to build and test APIs. In the context of network programmability where an API is already constructed and ready to be followed, administrators and developers can utilize Postman to debug code and test REST calls that need to be made. Postman also offers a browser extension for Google Chrome, available within the Chrome Web Store. There are similar easy-to-use tools like Insomnia and Paw that are popular as well.

Postman - collaboration platform for API development
Cisco DevNet Postman Collection - DevNet's Postman collection, which is hosted on Postman site

VIRL - Cisco Virtual Internet Routing Lab (VIRL) is an extensible network virtualization platform that enables the development of high-fidelity models of real or planned networks. VIRL includes current virtualized versions of Cisco network operating systems and allows integration with 'real' physical / external networks, network elements, and servers.

VIRL - get VIRL, deploy VIRL, as well as tutorials and resources.

Cisco Active Advisor - Cisco Active Advisor simplifies network discovery and finds security alerts that apply to your devices. It also analyzes contract coverage and end-of-life status, and can compare your network against Cisco Validated Designs. Best of all, it's free.

Cisco Active Advisor - Reduce network risk and boost security for free

Cisco Network Assistant - Cisco Network Assistant is a PC-based network management application optimized for wired and wireless networks for growing Small-Medium sized businesses. Cisco Network Assistant provides a centralized network view with a user-friendly GUI that simplifies configuration, management, and troubleshooting.

Cisco Network Assistant - Using Cisco Network Assistant, network administrators can easily apply common services, generate inventory reports and synchronize passwords across Cisco switches, routers, wireless LAN controllers, and access points.

Cisco Bug Search Tool - The Cisco bug tracking system maintains a comprehensive list of defects and vulnerabilities in Cisco products and software.

Cisco Bug Search Tool - Bug Search is a web-based tool that acts as a gateway to the bug tracking system and provides you with detailed defect information about your products and software.

Cisco Internetworking Troubleshooting Tools

Troubleshooting Tools - information about the wide variety of tools available to assist you in troubleshooting your internetwork. This includes information on using router diagnostic commands, Cisco network management tools, and third-party troubleshooting tools.

Docs

Network Management System: Best Practices White Paper (2018)
Cisco Guide to Harden Cisco IOS Devices (2020)

External Resources

Best Cisco Monitoring Tools for Network Performance and Routers - Tools for monitoring Cisco networks

Networking Tools Knowledge Base

alexstev — Wed, 05 May 2021 16:36:56 GMT

Networking Tools Knowledge Base

Networking Tools - Making a Network Engineer's life easier. Work smarter.

Start

Networking 101 - Learn coding basics for Networking.
EN Networking - Build Apps with Cisco DNA Center Platform Solutions.
DC Networking - Explore Application Centric Infrastructure (ACI) programmability options and explore data center APIs.

Learn

Networking Dev Center - Learn how you can integrate with the network through full system management solutions in the cloud, utilize automation platforms and controllers, or directly interact with devices with APIs and Interfaces.

IDEs - an Integrated Development Environment (IDE) is a software package available for download and use that can help simplify the development process. IDEs integrate many of the common tasks in software development to enable rapid application development.

PyCharm - an IDE with full support for Python, as well as for HTML, CSS, JavaScript, Node.js and more.
Komodo - another IDE with full support for Python, as well as Go, Perl, Ruby and more.

SDKs - a software development kit (SDK) differs fundamentally from an IDE. An SDK is a set of functions, packages, documentation and programs required for development on a specific platform or technology, whereas an IDE can be thought of as providing tools for application development using a specific language or technology.

Sandboxes - Cisco and Networking are practically synonymous! The Sandbox offers many networking labs with SDN controllers or API driven network gear!

Networking Sandbox Highlights - on Cisco DevNet
Explore ALL Networking Sandboxes - on DevNet

Learning Labs - just like our Sandboxes, the Learning Labs on Cisco DevNet are FREE to use!

Networking Labs - all of the Networking Learning Labs on Cisco DevNet
Network Programmability for Network Engineers - Learning Track on DevNet

Cisco Modeling Labs - Cisco Modeling Labs (CML) is our premier platform for network simulation. With an easy-to-use HTML5 UI and a comprehensive API, Cisco Modeling Labs makes it fun to design, test, troubleshoot, and learn.

Cisco Modeling Labs - on Cisco DevNet

Postman - Postman can be utilized to build and test APIs. In the context of network programmability where an API is already constructed and ready to be followed, administrators and developers can utilize Postman to debug code and test REST calls that need to be made. Postman also offers a browser extension for Google Chrome, available within the Chrome Web Store. There are similar easy-to-use tools like Insomnia and Paw that are popular as well.

Postman - collaboration platform for API development
Cisco DevNet Postman Collection - DevNet's Postman collection, which is hosted on Postman site

Cisco Active Advisor - Cisco Active Advisor simplifies network discovery and finds security alerts that apply to your devices. It also analyzes contract coverage and end-of-life status, and can compare your network against Cisco Validated Designs. Best of all, it's free.

Cisco Active Advisor - Reduce network risk and boost security for free

Cisco Network Assistant - Cisco Network Assistant is a PC-based network management application optimized for wired and wireless networks for growing Small-Medium sized businesses. Cisco Network Assistant provides a centralized network view with a user-friendly GUI that simplifies configuration, management, and troubleshooting.

Cisco Network Assistant - Using Cisco Network Assistant, network administrators can easily apply common services, generate inventory reports and synchronize passwords across Cisco switches, routers, wireless LAN controllers, and access points.

Cisco Bug Search Tool - The Cisco bug tracking system maintains a comprehensive list of defects and vulnerabilities in Cisco products and software.

Cisco Bug Search Tool - Bug Search is a web-based tool that acts as a gateway to the bug tracking system and provides you with detailed defect information about your products and software.

Cisco Internetworking Troubleshooting Tools

Troubleshooting Tools - information about the wide variety of tools available to assist you in troubleshooting your internetwork. This includes information on using router diagnostic commands, Cisco network management tools, and third-party troubleshooting tools.

Docs

Network Management System: Best Practices White Paper (2018)
Cisco Guide to Harden Cisco IOS Devices (2020)

External Resources

Best Cisco Monitoring Tools for Network Performance and Routers - Tools for monitoring Cisco networks

IoT Knowledge Base

Paul Zimmerman — Thu, 22 Apr 2021 20:54:11 GMT

IoT Knowledge Base

For one-on-one help with these products, you can open a ticket at https://developer.cisco.com/site/support/. For other products, please contact Cisco TAC (tac.cisco.com).

Internet of Things (IoT)

Start

Learn

Sandbox Remote Labs - IoT
Cisco Code Exchange - Cisco IoT
DevNet Automation Exchange - IoT
Edge Compute and Software
- Cisco Edge Intelligence
- IOx

Networking
- Cisco IPv6 Mesh
- Industrial NetDevOps
Security
- Manufacturer Usage Descriptions (MUD)

Certifications

Exam

Developing Solutions Using Cisco IoT and Edge Platforms (300-915 DEVIOT)

Courses and Exam Prep

IoT APIs

IOx - Host applications on Cisco hardware, including container-based deployments.

Cisco IPv6 Mesh - Create a communication network overlay for the electric distribution grid to enable street lighting, connectivity to solar or wind power, on-demand metering, and other smart city use cases.

Control Center - Automate connectivity management, deployment, and track activity for all your connected devices.

Cisco Kinetic - Integrate data routes with fog application data, extract data from data pipes with connectors, and move or keep categorized data with policies.

Cisco Kinetic for Cities - Aggregate and organize data from city infrastructure sensors and other data sources in a consistent format.

Manufacturer Usage Description - Facilitate device visibility and segmentation of IoT devices by defining the corresponding behaviors for that device.

Cisco Community Forums

Docs

YANG Tools Knowledge Base

alexstev — Wed, 05 May 2021 16:40:05 GMT

YANG Tools Knowledge Base

For one-on-one help with developer products, you can open a ticket at https://developer.cisco.com/site/support/. For other products, please contact Cisco TAC (https://www.cisco.com/c/en/us/support/index.html).

YANG Tools - You can use these YANG tools to deploy, configure, monitor, and troubleshoot.

1. YANG Suite - a set of tools related to YANG models and related technologies such as NETCONF

Cisco YANG Suite GitHub Repo
The Wait Is Over: Cisco YANG Suite Is Here! - Cisco Blogs
YANG Suite - Documentation on Cisco DevNet
yangsuite-support-ext@cisco.com - YANG Suite external mailer

2. YANG Development Kit - a Python SDK generated from YANG data models.

YANG Development Kit - on Cisco DevNet
YANG Development Kit - Cisco DevNet's GitHub Repository (Python)

3. ncclient - a Python library that facilitates client-side scripting and application development around the NETCONF protocol.

ncclient - official GitHub Repository

4. pyang - a YANG validator, and code generator, written in python.

pyang - official GitHub Repository

5. yang.connector - a package containing collections of tools to test YANG models via NETCONF and RESTCONF protocols.

yang.connector - Documentation on Cisco DevNet

6. yang-explorer- an open-source Yang Browser and RPC Builder Application to experiment with Yang Data Models

yang-explorer - on Cisco Code Exchange

Cisco Community Forums

YANG Tools

Docs

YANG Tools - on Cisco DevNet
GitHub Repos - List of YANG-related repositories on the official Cisco DevNet GitHub page.
APIs - Model Driven Programmability with YANG (for NX-OS)

External Resources

YANG Tools - Repository of YANG Tools on the OpenDaylight Wiki

Difference between USGMII and USXGMII and why USGMII is better than SGMII/QSGMII

Paul Zimmerman — Wed, 10 Mar 2021 03:18:34 GMT

Difference between USGMII and USXGMII:

USGMII is used for 8x10M/100M/1GE network ports, with each port maximum speed of 1GE. USXGMII-Single Port version can be used to support ONE network port with 10M/100M/1G/2.5G/5G/10G data rates
USGMII is used for 10M/100M/1G network port speeds, while USXGMII support 10M/100M/1G/2.5G/5G/10G.
There are two types of USXGMII: USXGMII-Single Port and USXGMII-Multiple Ports.
USGMII and USXGMII provide the same capabilities using the packet control header.

Why USGMII is better than SGMII/QSGMII:

SGMII supports a single 10M/100M/1G network port over 1,25Gbps SERDES between MAC and PHY, while QSGMII supports four 10M/100M/1G network ports over 5Gbps SERDES between MAC and PHY.
USGMII supports eight 10M/100M/1G network ports over 10Gbps SERDES between MAC and PHY. This is most critical for high density switches and PHY. USGMII also provides packet control header to pass control/status between PHY and MAC. One of the application is Time-Stamp for PTP and 802.1AS.

Contact Center Knowledge Base

Paul Zimmerman — Mon, 26 Apr 2021 19:33:33 GMT

Contact Center Knowledge Base

The Contact Center knowledge base contains information about developer topics for Finesse and Task Routing. For one-on-one help with these products, you can open a ticket at https://developer.cisco.com/site/support/. For other products, please contact Cisco TAC (support.cisco.com).

Finesse

Start

Finesse REST API

Documentation 101: How to read the table

Finesse JavaScript API

Learn

Task Routing

Start

Learn

DevNet Sandbox

Re: NSO Dev Days: Python Reactive Fastmap Lab

ZAhmad04890 — Tue, 02 Mar 2021 12:00:40 GMT

Hi , While Implementing Reactive Fastmap Lab in Python , It says that Resource Manager Package needs to be Installed as it contains both an id allocator and an ip allocator functionality , which is not available by default in NSO install.

I have downloaded free copy of NSO 5.3 from Devnet for CCIE SP Lab purpose , but I could not find the Resource Manager Package on Devnet available for free dowload, does any one knows whether Resource Manager Package is available on Devnet for download? Thanks

https://software.cisco.com/download/home/286323467/type/286283941/release/5.3

Re: Delete the top-most diversion header or change order of Multiple Diversion

Leonard — Fri, 12 Feb 2021 21:59:52 GMT

Did you have any luck on this? As Im trying to modify the diversion headers just as you describe as well.

Re: CVRF at Cisco

ROBERT THOMSON — Sun, 07 Feb 2021 21:54:44 GMT

Could you please help me by explaining the apparent inconsistency in the CVRF data formatting with respect to the usage of the relationship xml element. For example in https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ipv6-acl-CHgdYk8j there is a relationship for each specific platform that is affected but when you look at https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-iosxr-pe-QpzCAePe it references two hardware platforms but there is no relationship element ?

Re: Web Page control vs Crestron control

DanRichardson — Sun, 07 Feb 2021 00:46:33 GMT

The first reply above refers to " our HOWTO-guide for the C-Series " That sounds like it would answer my questions, but it's a 404 link. Is it archived or available anywhere?

Re: CUPI User Import

alexstev — Fri, 05 Feb 2021 16:08:14 GMT

All,

I found a few known bugs regarding CUPI User Import. I think at least one may be relevant:

Cisco Bug Search Tool: 'CUPI User Import' Results

Re: CUPI User Import

Michael Stark — Thu, 04 Feb 2021 18:03:43 GMT

We are also experiencing this issue and have no opened a ticket for it with devnet.

Re: CVP 7 ApplicationAPI Usage

GauravKishore0360 — Thu, 21 Jan 2021 06:35:03 GMT

Thanks Janine .. I was restarting the VXML server but class file path folder was not correct . I changed the class class path as per my package name in eclipse and now it is working .

Re: CVP 7 ApplicationAPI Usage

janinegraves — Wed, 20 Jan 2021 20:55:40 GMT

Gourav,
Once you put your classes in VMLServer/common/classes or lib, did you restart VXMLServer?
If that doesn't work, you might have to put them into VXMLServer/Tomcat/classes or lib and restart VXMLServer.

Re: CVP 7 ApplicationAPI Usage

GauravKishore0360 — Fri, 15 Jan 2021 17:38:50 GMT

Hi James ..Did is resolved your and you were able to resolve classCastException?

I tried putting POJO in commons folder but the issue still persists.

Any workaound would be appreciated

Re: How to enable ztp on IOS-XE sandbox

bigevilbeard — Fri, 08 Jan 2021 09:53:41 GMT

sorry this took me a while to get back to you since we spoke in the WxT DevNet Support space, i thought it easier to reply here, that crawl back and find the chat again. For ZTP on XE see this new sandbox IOS XE on CSR Latest Code with ZTP functionality

Hope this helps.

Re: Error on DevNet intro-netconf learning lab at step 4

bigevilbeard — Wed, 06 Jan 2021 11:37:52 GMT

Our team confirmed this changed was fixed and pushed into production.

Thanks again!

Re: Error on DevNet intro-netconf learning lab at step 4

bigevilbeard — Sat, 02 Jan 2021 11:20:12 GMT

Hey opened this issues with our team here --> https://github.com/CiscoDevNet/learning-labs-issues/issues/286

Thank you for reporting this.

Webex Developer resources

Dirk-Jan Uittenbogaard — Thu, 06 May 2021 07:45:53 GMT

Welcome!
To my Webex Developer resource overview

Like it?
Please scroll to the end and click the 'Helpful' button!

Contribute?
Something I should add? Let me know in the comments!

QUICK ACCESS TO THIS PAGE: cs.co/webexdevinfo

NEW: LinkedIn Webex Developer group cs.co/webexdevlink news/tips/announcements/&more

GENERIC

DOCS & TRAINING

Webex Developer Portal
Developer blog
What's New
Admin API
Developer support GREAT!
Developer Support / portal
Awesome Webex GREAT!
Youtube integration videos
Communities
Webex Ambassador group
DevNet Webex Teams
Community Developer / Partner

Developer Portal
Bots
Integrations
Widgets
Guest Issuer

Getting Started
guide - Admin
guide - Compliance
guide - Webhooks
guide - Hybrid
API change-log

Change calendar LIKE

Learning Labs GREAT!
DevNet Webex API tracks
DevNet Collaboration Dev Center
Training: Python for Everyone  GREAT!
Firewall traversal
Teams Buttons & Cards school LIKE!

Cisco Live Collab Dev session list

EXAMPLE CODE

USE CASES & EXAMPLES

Teams Space archiver v2 (video)
Python oAuth basic example
Python Translate bot
EURL.io Space Member code on Github
[PHP] Webex Teams API
Browser SDK examples
Widget examples
IoT & Raspberry to Wx Teams part 1 / part 2 NodeJS oAuth example
Webex Buttons and Cards School
OVERVIEWS
Starter Kits (open source)
DevNet Creations
Cisco Code Exchange
DevNet Github
Search Github 'webex teams'

DevNet Creations
Cisco Code Exchange
Youtube Channel: Webex Teams Integrations

Video problem reporting to Wx Teams
Hospital wait times
Webex Teams articles by WWT (partner)
Webex App Hub

UCS Director integration
App: Talk 2 Webex Teams mobile app for audio/video/TTS

WIDGETS & SDK

LIBRARIES & FRAMEWORKS

Widget Documentation
Widget Learning Labs

SDK iOS /   Android
SDK Browser   /   NodeJS
SDK JAVA / Community
SDK Learning Labs

SDK example (TestFlight) ^LIKE

Python webexteamssdk - support

FRAMEWORK
Webex Node Bot framework ^LIKE
Node.JS bot framework (ObjectIsAdvantag)
Flint & Node.JS framework (nmarus) |
Botkit framework (template / examples)
  lab: create teams bot
  lab: create conversational bot
Python Webex Teams bot framework
LIBRARY
Python Teams library (brbester)
...more in 'awesome webex'

TOOLS

DEVELOPMENT TOOLS

Teams Power Pack
Space Archiving tool GITHUB
Teams Forms
Video System Status browser
WebSocket Events link

Postman Collections
DevNet Collaboration Sandboxes
Webex Teams API Emulator
Deactivate Bot & Integration tokens
Node-red integration
Webhook Proxy (github)

Tool: Postman
Editor: Atom
Editor: Notepad++

INTEGRATION PLATFORMS

WEBEX MEETINGS

Built.io link
Zapier link
Gupshup link
IFTTT link
Botkit.ai link
+ Sameroom.io, Workato, Zenbot.io,
No native Teams integration, but usable with API's:
Flow XO, Elastic.io, APIANT, Integromat

Meeting API - get started
Meetings DevNet site
Meetings API Support
Meetings Community

xAPI

DOCUMENTATION

xAPI command reference (all releases)

xAPI REST documentation
roomos.cisco.com: xAPI guides

roomos.cisco.com: xAPI reference

roomos.cisco.com: xAPI examples
Customization Guides
CE software release notes PDF
RoomOS what's new

Awesome xAPI GREAT!
Room Devices on DevNet
Room Device Macro examples

Video Unit sandbox
xAPI Support (Webex Space)

GITHUB
- Video System Status Monitor
- Meeting Feedback
- Javascript xAPI library

- Virtual Background Logos new

Getting Started
xAPI introduction LAB
xAPI In Room controls LAB (try editor)
xAPI Macro tutorial PDF
xAPI examples

TOOLS
Postman collection

LEARN
CE customization lab
Create custom in-room controls lab
Customizing devices from code lab
Introduction to XAPI lab
Exploring XAPI Macros lab

CISCO LIVE SESSIONS

Zero to Hero - programmability course ^NEW

BRKCOL-3008 - Custom.&Integrations Room Devices

BRKDEV-3244 - Advanced coding for Video devices
DEVNET-2071 - Customizing Collaboration Devices
DEVNET-1462 - Webex Room APIs: "the power of..."

NEW: LinkedIn Webex Developer group cs.co/webexdevlink

CHANGELOG

April 2021 - added LinkedIn group URL, added virtual-background link
November 2020 - major overhaul of page
July 2020 - adding xAPI resources
Dec 2019 - updated links
July 2019 - Added some xAPI links
July 2019 - Complete re-write of this page (was needed
xpost in Collaboration / Collaboration documents here

Re: How to enable ztp on IOS-XE sandbox

Chris Dixon — Tue, 27 Oct 2020 14:20:50 GMT

Apparently theres no dhcp server configured on the dev-box, and no internet access to install one. Anyone got any ideas how else to test this?

Re: How to enable ztp on IOS-XE sandbox

Chris Dixon — Tue, 27 Oct 2020 14:14:23 GMT

I read that just erasing the config would get it into day0 mode, however I dont have any kind of virtual console access on the sandbox, so cant tell if that worked really - so Ill check on dhcp server if its getting any traffic to find out

How to enable ztp on IOS-XE sandbox

Chris Dixon — Tue, 27 Oct 2020 13:38:00 GMT

Symptoms

I'm using the devnet IOS-XE sandbox to try and test the ZTP feature, however I can see that when I ssh into the fresh box it already has a startup config and hence I dont think it will attempt to ztp on reboot. How do you get the lab IOS-XE device into a state to be able to test ZTP?

How to debug NSO service/action with Pycharm pro

Rodolphe Trujillo — Fri, 18 Sep 2020 18:19:59 GMT

Step 1 : configure debug server in Pycharm

Go to Run => Edit Configurations, click on "+" => Python Remote Debug

In "Local Host name " enter ip or host name of your local machine. Enter a available port in "Port :"

Give a name, here it's "NSO debug".

Click ok.

Step 2 : install pydevd_pycharm

The debug tool uses pydevd-pycharm library to attach to the local debug server we just created.

Run

python -m pip install pydevd-pycharm

with the python interpreter used by NSO.

Step 3 : run debug server

Select NSO Debug and click on the green bug (or Shift + F9).

The debug server is now listening on port 8885

Step 4 : call the server from the service/action thread.

Insert the following code in the callback function of the service/action (change host and port) :

import pydevd_pycharm
pydevd_pycharm.settrace('host', port=port, stdoutToServer=True, stderrToServer=True)

That's all , now the service/action callback will try to reach the debug server (don't forget to do a packages reload)

You can now debug with pycharm :

And have full information about the variables :

NSO Developer Days 2019: Nano Services – Another approach for Reactive Fastmap (RFM) services

Jan Lindblad — Fri, 18 Sep 2020 18:19:58 GMT

Abstract: RFM services can be hard to implement. Especially the lifecycle management of the delete case of the service can be a challenge. Nano Services uses an executable plan and kickers to supports the full lifecycle of a RFM service.

Speaker: Try Ryeng

deleted

peter8498 — Mon, 17 Aug 2020 08:24:10 GMT

Re: Trying sandbox for WLC 9800 but timing out

carlocon — Mon, 17 Aug 2020 03:18:19 GMT

I was able finally to login to the Sandbox not sure why it was failing but now is working ok

Re: Possible to embed webex into mobile app? and/or website?

Luiz Rovero — Thu, 06 Aug 2020 22:10:06 GMT

Boa noite, pessoal.

Estou procurando um IFrame para utilizar o aplicativo webex Reuniões através do meu portal, onde toda vez que eu crio uma nova reunião e gera uma ID e Senha, eu copio nesse IFrame e disponibiliza para acesso dos demais, como um IFrame do Zoom.

Ex: <iframe allow='microphone;camera'src='https://us02web.zoom.us/wc/join/xxxxxxxxx?prefer=0&pwd=xxxxxx'scrolling='no' width='100%' height='600' type="text/html' frameborder='0' allowTransparency="true" style='padding-bottom=0%' sandbox='allow-forms allow-scripts allow-same-origin allow-pointer-lock allow-popups'></iframe>

Re: Accessing the Cisco PSIRT openVuln API Using curl

visxu — Tue, 04 Aug 2020 14:13:26 GMT

I created a another new application and it works with the new id and secret.
In the second creation, I just choose only one Grant Type : "Client Credentials"

Re: Accessing the Cisco PSIRT openVuln API Using curl

visxu — Tue, 04 Aug 2020 03:15:48 GMT

The KEY means client_id, CLIENT SECRET means client_secret, right ?
But I got 401 response

{
    "error_description": "Invalid client or client credentials.",
    "error": "invalid_client"
}

Re: Trying sandbox for WLC 9800 but timing out

Punit Joshi — Thu, 30 Jul 2020 14:49:29 GMT

Hi can you paste your code here please.

Re: Creating a GENERIC NED v 1.0

hoatruo — Thu, 30 Jul 2020 10:05:58 GMT

The code skeleton is not publicly available yet.

If you need a NED for your project, please contact .

Thanks,

Hoa

Re: Creating a GENERIC NED v 1.0

gusmb — Sat, 25 Jul 2020 21:33:16 GMT

Hi ,

I am looking forward to use this to create a Generic REST NED with basic functionality to interact with a McAfee Web Gateway proxy via REST API. Would you be able to provide the code skeleton to work on? It would work nicely just like in your example.

Thanks,

Gustavo

Re: Generic REST NED Reference

gusmb — Sat, 25 Jul 2020 21:27:31 GMT

Is it possible to have the source code to review more in depth? It is very useful to help integrate NSO with other in-house tools based on REST APIs

Re: How to mute a call

YouTee — Tue, 23 Jun 2020 14:33:41 GMT

Hi,

Any update on this..?

I have tried to mute myself from the call using JTAPI by using sendData(byte[]) and send the following XML to this:

This is working on Cisco IP communicator but not working on Cisco Jabber softphone. Any suggestions on this..?

Re: Phone Mute via JTAPI

YouTee — Tue, 23 Jun 2020 14:20:07 GMT

Hi,

I tried this with Cisco IP Communicator and it's working. However, when I tried the same on Cisco Jabber softphone, it did not work.

Re: Overall Server Status is reported as "Severe Fault"

bobbywayne08569 — Wed, 03 Jun 2020 10:29:52 GMT

Team this is unrelated to this topic but i am trying to monitor the UCS C240 M4S2 series server by whenever a fault is raised by the specific OID alert should be triggered in SCOM by looking up in the OID lsit for UCS c series below are the only OID related to fault whenever it raised but testing this tends to fail wanted to check if this is the accurate OID which represents whenever a fault is raised please suggest.

.1.3.6.1.4.1.9.9.719.0.1 -Fault raised(is this the correct OID)
.1.3.6.1.4.1.9.9.719.0.2-Fault cleared

The Goal is to check the Overall server status usually status is GOOD but when a fault is raised this needs to be monitored

.1.3.6.1.4.1.9.9.719.0.1 -Fault raised
.1.3.6.1.4.1.9.9.719.0.2-Fault cleared

Re: REST API Basics

srisikha@cisco.com — Mon, 04 May 2020 15:23:16 GMT

i go to the

http://IP/api - i get the page downloaded instead of displayed - how i browse the api ? or some swagger type tool so i try the curl inside a tool ?

Re: NX-OS versions via APIC API

Claudia de Luna — Sun, 26 Apr 2020 03:48:09 GMT

Hi ,

Try topSystem like below:

https://{{URL}}//api/node/class/topSystem.json?query-target=subtree&target-subtree-class=topSystem,eqptCh,firmwareRunning

You will get lots of data back and for each topSystem object you get back you will also get the firmwareRunning object which has a "version" key.

        {
            "topSystem": {
                "attributes": {
                    "address": "10.0.248.2",
                    "bootstrapState": "done",
                    "childAction": "",
                    "configIssues": "",
                    "controlPlaneMTU": "9000",
                    "currentTime": "2020-04-26T05:09:04.123+00:00",
                    "dn": "topology/pod-1/node-102/sys",
                    "enforceSubnetCheck": "no",
                    "etepAddr": "0.0.0.0",
                    "fabricDomain": "ACI Fabric1",
                    "fabricId": "1",
                    "fabricMAC": "00:22:BD:F8:19:FF",
                    "id": "102",
                    "inbMgmtAddr": "0.0.0.0",
                    "inbMgmtAddr6": "::",
                    "inbMgmtAddr6Mask": "0",
                    "inbMgmtAddrMask": "0",
                    "inbMgmtGateway": "0.0.0.0",
                    "inbMgmtGateway6": "::",
                    "lcOwn": "local",
                    "modTs": "2020-04-25T14:25:02.324+00:00",
                    "mode": "unspecified",
                    "monPolDn": "uni/fabric/monfab-default",
                    "name": "leaf-2",
                    "nameAlias": "",
                    "nodeType": "unspecified",
                    "oobMgmtAddr": "10.10.10.102",
                    "oobMgmtAddr6": "::",
                    "oobMgmtAddr6Mask": "0",
                    "oobMgmtAddrMask": "0",
                    "oobMgmtGateway": "0.0.0.0",
                    "oobMgmtGateway6": "::",
                    "podId": "1",
                    "remoteNetworkId": "0",
                    "remoteNode": "no",
                    "rldirectMode": "no",
                    "role": "leaf",
                    "serial": "TEP-1-102",
                    "serverType": "unspecified",
                    "siteId": "0",
                    "state": "in-service",
                    "status": "",
                    "systemUpTime": "00:14:58:31.000",
                    "tepPool": "10.0.0.0/16",
                    "unicastXrEpLearnDisable": "no",
                    "virtualMode": "no"
                }
            }
        },
        {
            "firmwareRunning": {
                "attributes": {
                    "biosTs": "1970-01-01T00:00:00.000+00:00",
                    "biosVer": "",
                    "childAction": "",
                    "descr": "",
                    "dn": "topology/pod-1/node-102/sys/fwstatuscont/running",
                    "internalLabel": "",
                    "ksFile": "",
                    "modTs": "2020-04-25T14:12:39.049+00:00",
                    "mode": "normal",
                    "peVer": "",
                    "status": "",
                    "sysFile": "",
                    "ts": "1970-01-01T00:00:00.000+00:00",
                    "type": "switch",
                    "version": "simsw-4.1(1k)"
                }
            }
        },

Trying sandbox for WLC 9800 but timing out

carlocon — Fri, 24 Apr 2020 19:57:12 GMT

Hi team,

Starting to work with some of the sandboxes on this site, as a Wireless engineer I wanted to start with the WLC 9800 sandbox that is always on. Basically wanted to try APIs to read telemetry, however after reading the instructions I have tried several times to access a link to accept a "certificate" from a link wlc9800.cisco.com and always timing out. I have tried being out of the VPN or in but no result on any case. Since this is one of my first attempts I am wondering if I am missing something or doing something wrong, since the instructions for SandBoxes always on according to documentation don't require VPN access. Let me know your comments please

Regards
Carlos Contreras

Re: CUPI User Import

karthikkrishnan07580 — Tue, 21 Apr 2020 07:48:33 GMT

Hi,

while i tried to import LDAP users via API, it shows data exception error like "Enter Vaild Relay Email Address". please find below in detail,

NOTE: able to import user via GUI

API:

https://<ip>/vmrest/import/users/ldap?templateAlias=voicemailusertemplate

Payload:

</ImportUser>

OutputError:

<code>DATA_EXCEPTION</code>

<message>Enter Vaild Relay Email Address</message>

</errors>

</ErrorDetails>

could you please help on that. thanks in advance.

Re: Using CUPI to Import LDAP user

karthikkrishnan07580 — Fri, 17 Apr 2020 13:14:37 GMT

Hi,

while I tried to import LDAP user, with below payload but I am data_exception. it will be more helpful if it is solved earlier.

thanks in advance.

API:

https://<ip>/vmrest/import/users/ldap?templateAlias=voicemailusertemplate

Payload:

</ImportUser>

OutputError:

<code>DATA_EXCEPTION</code>

<message>Enter Vaild Relay Email Address</message>

</errors>

</ErrorDetails>

Re: Determining if a endUser password/pin is locked

dstaudt — Mon, 06 Apr 2020 23:20:04 GMT

It looks like the missing info is in the 'credentialdynamic' table - not accessible via regular AXL requests, as far as I can tell, so you will need to use <executeSqlQuery>.

I think something like this, might get you pretty close:

<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <ns:executeSQLQuery xmlns:ns="http://www.cisco.com/AXL/API/11.5">
      <sql xsi:type="xsd:string">select enduser.userid, tkcredential, credential.timeadminlockout, credentialdynamic.timehackedlockout
		from enduser, credential, credentialdynamic
		where credential.fkenduser = enduser.pkid and
	  	credential.pkid = credentialdynamic.fkcredential and
      	enduser.userid = 'dstaudtTest' 
	</sql>
    </ns:executeSQLQuery>
  </soap:Body>
</soap:Envelope>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Body>
      <ns:executeSQLQueryResponse xmlns:ns="http://www.cisco.com/AXL/API/11.5">
         <return>
            <row>
               <userid>dstaudtTest</userid>
               <tkcredential>3</tkcredential>
               <timeadminlockout>1586214942</timeadminlockout>
               <timehackedlockout/>
            </row>
            <row>
               <userid>dstaudtTest</userid>
               <tkcredential>4</tkcredential>
               <timeadminlockout/>
               <timehackedlockout/>
            </row>
         </return>
      </ns:executeSQLQueryResponse>
   </soapenv:Body>
</soapenv:Envelope>

( where tkcredential = 3 is password, 4 is pin)

Determining if a endUser password/pin is locked

stephan.steiner — Tue, 31 Mar 2020 15:37:39 GMT

I'm tasked with providing a credential unlock for CUCM endusers. Looking at the AXL schema and doing some trial & error I found that pinCredentials.pinResetHackCount / passwordCredentials.pwdResetHackCount is what I'm looking for.. setting this to true in a user update resets the history. But, extracting the user, it seems I'm missing some properties that are visible in ccmadmin. So, given that locking yourself out by trying the wrong credential for too many times does not set any property gettable by AXL, the question is: how can I know if a user's pin or password credential has been locked?

The same seems to be possible via CUPI. There's the "Hacked" property that if true means the user has been locked out for trying an incorrect credential too many times.

Re: NSO Developer Days 2019: Nano Services – Another approach for Reactive Fastmap (RFM) services

Jan Lindblad — Thu, 19 Mar 2020 14:35:11 GMT

I have to admit your use case sounds a bit odd. But if this what you need to do, you need to use the RFM or Nano service design patterns. The design you outline above (starting and committing a transaction in create()) has no chance of working.

Have a look at the NSO examples collection, e.g.

examples.ncs/service-provider/virtual-mpls-vpn

examples.ncs/getting-started/developing-with-ncs/20-nano-services

Re: NSO Developer Days US 2019: Nano services presentation

adamsmith62956 — Thu, 19 Mar 2020 14:20:30 GMT

Nanoservices are like each and every activity you perform in microservices but in lesser quantity. Moreover, it is designed in such a way that it can only perform a single task. Well, this may be a disadvantage for some, but can also be advantageous for certain businesses.

https://www.yourtechdiet.com/blogs/nanoservices/

Re: NSO Developer Days 2019: Nano Services – Another approach for Reactive Fastmap (RFM) services

ElisabettaParacuollo28312 — Thu, 19 Mar 2020 14:00:16 GMT

Good morning,

my goal is to create a SERVICE in JAVA that must delete, through a template, the instance of a different service and then commit it. We say Service1 the service that must delete and Service2 the service that must be deleted.
Subsequently Service1 must recreate the instance of Service2 with a new json.
All this must be done in Service1 .

The problem is not the cancellation and creation of Service2 but the commit between cancellation and creation.

I open a transaction inside wich I delete Service2 instance and I apply the template:

maapi.ncsApplyTemplate(tid, "deleteService2-Template", newPath, myVarsDelete, true, true);
maapi.applyTrans(tid, false);

But I take Aborted: TimeOut on instruction maapi.applyTrans(tid, false);.

My question is:

1) is it right way to implement in a single transaction both the operations? (cancellation and creation)

2) If so, do anyone has idea in wich way can I overcome the timeout?

Thanks a lot for any contribution

Re: 'Devices on rent' kind of services

LanDownUnda — Tue, 10 Mar 2020 08:51:59 GMT

Not a bad idea at all! The Sandboxes on the Devnet website won't actually show you VIRL because its a backend system used to emulate the various Cisco iOS platforms.

There are rack rental companies out there that you can pay to reserve an amount of time with some devices. They are typically used for Labbing. Depending on how many devices you want ect the costs can vary.

I hope this helps!

Re: 'Devices on rent' kind of services

Temmokan — Tue, 10 Mar 2020 06:34:41 GMT

Thanks for suggestion. I visited a few "always on" labs at DevNet Sandbox, to have an impression; before investing into VIRL, I'd like to find a lab allowing to connect via SNMP to the emulated network/device(s).

Re: 'Devices on rent' kind of services

LanDownUnda — Mon, 09 Mar 2020 10:24:30 GMT

Hi Temmokan,

Cool stuff making some monitoring software. Might I recommend using something like Cisco VIRL which is what the DevNet Sandbox's run off? That way you can play with different SNMP, RestConf, NetConf protocols which might break the T&C's of the publically available DevNet Sandboxes?

I hope this helps!

'Devices on rent' kind of services

Temmokan — Fri, 28 Feb 2020 03:28:20 GMT

Hello,

We are developing a network monitoring piece of software. To create monitoring presets, we would need to actually access a number of Cisco devices (via HTTPS/SNMP), within a sandbox environment.

I noticed there are several 'Cisco devices on rent' kind of services on the Net, but still waiting for response from them. Are there any well-known 'devices on rent' kind of services, with Cisco devices available?

Thanks.

Re: Webex Teams Developer resources

samimsahrai53759 — Wed, 26 Feb 2020 04:46:28 GMT

how to create custom corporate directory thanks

Re: Play Audio while waiting for a process to be completed in Decision Element

StumpycoinsM80708 — Mon, 17 Feb 2020 14:30:00 GMT

How to iterate/loop/repeat the fetchaudio file in vxml?

Re: Device types supported by Cisco NSO NEDs

SiewSE55115 — Wed, 05 Feb 2020 09:23:20 GMT

Thanks KJ Rossavik for your prompt and clear explanation. Really appreciate it. :)

Re: Device types supported by Cisco NSO NEDs

KJ Rossavik — Wed, 05 Feb 2020 08:28:05 GMT

We do not offer training for this, as nobody does this, and neither should they. If you require a NED for a bespoke device/system then we would recommend that you get that developed and supported by one of the partners that we use for NED development.

SNMP NEDs can be generated from the SNMP MIBs as described in the NED development guide

Re: Device types supported by Cisco NSO NEDs

SiewSE55115 — Wed, 05 Feb 2020 05:31:09 GMT

Thanks KJ Rossavik for your explanation.

You mentioned that it is theoretically possible to develop NED for a Bespoke hardware using documented Cisco APIs though it is quite a specialized skill set.

Does Cisco provide training on how to develop NED for bespoke hardware (I have 1 bespoke equipment using its own custom protocol and another 1 bespoke equipment using SNMP)? Thanks again :)

CUCM Sandbox Version 12.5 - automatic deletion after 5 days

Thomas Biesterfeldt — Fri, 31 Jan 2020 16:40:16 GMT

Dear all,

our development Team is facing a Problem with the CUCM sandbox.

Everything in the sandbox is getting completely deleted after 5 days.

This is a big Problem for us, because we'd like to use the test Environment für a longer period of time.

What do we have to do so that the data is not being deleted?

Thank you very much in Advance for your support!

Best regards,

Thomas

NX-OS versions via APIC API

bdbauer — Thu, 23 Jan 2020 20:08:20 GMT

I'm able to pull the topology using the API GET

https://n.n.n.n/api/node/mo/topology/pod-1.json?query-target=children&target-subtree-class=fabricNode

(after authenticating and getting a cookie, of course)

But the version field is empty. I don't see a way to get the version of our NX-OS switches via APIC REST API. Is this something that can be done via API?

NSO and Network Management Datastore Architecture (NMDA)

Akira Iwamoto — Wed, 19 Aug 2020 01:59:32 GMT

NSO as the sample implementation of new technology

Cisco NSO is a product implimenting RFC 6020 (yang) faithfully, and we could use it for testing new in the automation technology before even going on implementing ourselves. The author of the RFC is also developing the product, and it is one of the software leading the industory.

From NSO 5.3, RFC 8342 Network Management Datastore Architecture (NMDA) has been implemented, and this article shows the rough introduction using NSO.

The all won't be explained, but the below are related RFCs.

Yang
- RFC 6020 YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)
- RFC 7950 The YANG 1.1 Data Modeling Language
- RFC 8342 Network Management Datastore Architecture (NMDA)
Netconf
- RFC 6241 Network Configuration Protocol (NETCONF)
- RFC 8526 NETCONF Extensions to Support the Network Management Datastore Architecture
Restconf
- RFC 8040 RESTCONF Protocol
- RFC 8527 RESTCONF Extensions to Support the Network Management Datastore Architecture

IETF Yang has been also updated refrecting NMDA. Here's the RFCs for it.

IETF Yang implementation

RFC 8343 A YANG Data Model for Interface Management
RFC 8344 A YANG Data Model for IP Management
RFC 8345 A YANG Data Model for Network Topologies
RFC 8346 A YANG Data Model for Layer 3 Topologies
RFC 8347 A YANG Data Model for the Virtual Router Redundancy Protocol (VRRP)
RFC 8348 A YANG Data Model for Hardware Management
RFC 8349 A YANG Data Model for Routing Management (NMDA Version)

About Network Management Datastore Architecture

Network Management Datastore Architecture (NMDA) has been introduced since NSO 5.3, and it is described in RFC 8342. This gives new ideas of datastores we have been using, and it is meaningful to know about it. New datastores are added, and the usage of existing datastore is changed. NMDA is based on RFC 7950 (Yang 1.1), and reading RFC 8342 needs the knowledge from it as well.

RFC 8342 Section 5 gives the relations between datastores in a diagram. Previous model is in Section 4.

     +-------------+                 +-----------+
     | <candidate> |                 | <startup> |
     |  (ct, rw)   |<---+       +--->| (ct, rw)  |
     +-------------+    |       |    +-----------+
            |           |       |           |
            |         +-----------+         |
            +-------->| <running> |<--------+
                      | (ct, rw)  |
                      +-----------+
                            |
                            |        // configuration transformations,
                            |        // e.g., removal of nodes marked as
                            |        // "inactive", expansion of
                            |        // templates
                            v
                      +------------+
                      | <intended> | // subject to validation
                      | (ct, ro)   |
                      +------------+
                            |        // changes applied, subject to
                            |        // local factors, e.g., missing
                            |        // resources, delays
                            |
       dynamic              |   +-------- learned configuration
       configuration        |   +-------- system configuration
       datastores -----+    |   +-------- default configuration
                       |    |   |
                       v    v   v
                    +---------------+
                    | <operational> | <-- system state
                    | (ct + cf, ro) |
                    +---------------+

     ct = config true; cf = config false
     rw = read-write; ro = read-only
     boxes denote named datastores

Datastores defined in RFC 6020 / 6241

RFC 6020/6241 has defined the datastores are referred from the datastores used in network devices at the time. Today, the below datastores are still been actively used in many routers and switches.

startup
candidate
running

Startup datastore has configurations that is loaded when the device is booted up. Running datastore includes configurations that is currently running used on the device. Each session can have own candidate datastore on memory, and when commiting it, finally it's copied to running.

Data can be in two categories, configuration data and operational data. System becomes to the specific state with specific configuration data, and systems become always to the same state when the same configuration data is used. Operational data is something generated at runtime including like interface stats or VRRP state that users are not meant to configure.

On Yang model, "config" flag tells if the node is configuration or operational.

Configuration data
- config true
Operational data
- config false

Additions by RFC 8342 (NMDA)

Datastores are added as like the below. Operational may make misunderstanding, but this is not for "config false" data.

Datastore	Read/Write	Tag
startup	R/W	<startup>
candidate	R/W	<candidate>
running	R/W	<running>
intended	R	<intended>
operational state	R	<operational>

startup/candidate/running

There's no much differences when using startup, candidate and running datastores, however running datastore may not have some configurations that previously existed. For example, default configuration is not included.

Configuration example	description
inactive	inactive attribute can be added to configurations, and that config is not copied to intended datastore.
template-mechanism-oriented	The config is like a macro configuration, and the actual content will be expanded (configuration transformation) and set to operational datastore.

inactive would be used when operators want to disable it temporary, for example. They don't want to delete it and just mark the configuration is inactive.

In the example of template-mechanism-oriented, the macro configuration should be enough in running, and the actual content is redundant information. For instance, when config "A" is a template of config "B,C,D", having "A,B,C,D" in running doesn't make sense as the system should know "A" is "B,C,D" and it can calculate itself, so operators should not need to give "A,B,C,D"

In addition, with <intended> datastore explained next, these datastores are called conventional datastore.

intended datastore

Configurations derived from configurations in start/candidate/running datastore, and users can't modify contents on intended datastore. Depending on the configurations, the content of intended datastore is may be same with running datastore. When device is rebooted, the content in intended datastore is re-calculated from running datastore everytime.

It also can be validated at this time. In an example, when running datastore has a configuration with inactive, it's not affected in intended, so validation would work. Operators removes the inactive attributes, however the validation can fail and it cannot be injected into intended datastore.

operational state datastore

This datastore has the all required data to make the device in exactly same state. Because the oper-data (config false) is also included, when this datastore has the same data with another device, those two are behaving same.

This datastore includes other types of configurations like default configuration, learned configuration such as BGP RIB content and system configurations like chassis serial numbers.

Config examples

RFC 8342 Appendix C.2 (bgp configuration)

<running> datastore has the below configurations. BGP is being configured, and local-as, peer-as and peers (neighbors) are listed.

<bgp>
  <local-as>64501</local-as>
  <peer-as>64502</peer-as>
  <peer>
    <name>2001:db8::2:3</name>
  </peer>
</bgp>

We can confirm the all system state in <operational> datastore. If specific config is not found in <running>, origin attributes are set so that we can check where the config is from.

/bgp/peer/local-port is the data that operating system gives when BGP TCP session is created, so origin is system.

/bgp/peer/state is "config false" data, and it's not coming from anywhere, so there's no attributes attached.

<bgp xmlns:or="urn:ietf:params:xml:ns:yang:ietf-origin"
      or:origin="or:intended">
  <local-as>64501</local-as>
  <peer-as>64502</peer-as>
  <peer>
      <name>2001:db8::2:3</name>
      <local-as or:origin="or:default">64501</local-as>
      <peer-as or:origin="or:default">64502</peer-as>
      <local-port or:origin="or:system">60794</local-port>
      <remote-port or:origin="or:default">179</remote-port>
      <state>established</state>
    </peer>
</bgp>

Configurations in <operational> are not modified immediately after users configure on <running>. When BGP peer is removed in <running>, it's removed also from <intended>, however it's not removed in <operational>. bgp needs to shutdown the peer, and tcp needs to close the session, and it takes while. In this case, the modification on <opoerational> happens delayed.

Config examples

RFC 8342 Appendix C.3 (preconfig)

Physical interfaces on routers are added/removed by inserting/removing line cards. Even when <running> has configurations of non-existing interfaces, that cannot be used in the system. However by preparing those in <running> in advance of card insertion, that config is appeared in <operational> when the card is available automatically. This will increase the maintenancebility in enterprises.

<interfaces>
  <interface>
    <name>et-0/0/0</name>
    <description>Test interface</description>
  </interface>
</interfaces>

<interfaces xmlns:or="urn:ietf:params:xml:ns:yang:ietf-origin"
                 or:origin="or:intended">
  <interface>
    <name>et-0/0/0</name>
    <description>Test interface</description>
    <mtu or:origin="or:system">1500</mtu>
  </interface>
</interfaces>

New NETCONF operation

NMDA capable netconf servers can process new operations.

<get-data>

Previously <get-config> for getting configuration data (config true) and <get> for both configuration data (config true) and operational data (config false).

<edit-data>

It used as like the <edit-config> operation. <config> node was previously defined as anyxml when using <edit-config>. As <config> node is anydata for <edit-data> operation, the data can be in JSON, for example.

Usage of RESTCONF for NMDA

"ds" resource has been added to RESTCONF URI, and datastores can be specified as like the below.

For running datastore, GET/POST/PUT/PATCH is available while intended datastore can accept only GET. operational datastore is also readonly, however it can accept also POST for action invocation.

http://..../restconf/ds/ietf-datastores:running/
http://..../restconf/ds/ietf-datastores:intended/
http://..../restconf/ds/ietf-datastores:operational/

NMDA with NSO

NMDA is supported from NSO 5.3, but origin attribute is not supported currently. Let's try the feature.

NETCONF hello

NSO NETCONF Northbound interface responds as the below to <hello> operation. yang-library 1.1 capability is included.

$ netconf-console --hello
<?xml version="1.0" encoding="UTF-8"?>
<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">

//snip//

    <capability>urn:ietf:params:netconf:capability:yang-library:1.0?revision=2019-01-04&amp;module-set-id=3f1f4f98aba52a2290a6a29a1a8d9c0b</capability>
    <capability>urn:ietf:params:netconf:capability:yang-library:1.1?revision=2019-01-04&amp;content-id=3f1f4f98aba52a2290a6a29a1a8d9c0b</capability>

Sample NSO package for NMDA testing

The below simple yang model is created for testing. test1 module has a conatiner "server", and apps are running on it. Each application has a leaf with config false node to have a version information.

module test1 {
  namespace "http://com/example/test1";
  prefix test1;

  container server {
    list app {
      key name;
      leaf name {
        type string;
      }
      leaf version {
        config false;
        type string;
      }
    }
  }
}

app1, app2, app3 and app4 will be created on this example, but let's set app2, app3 and app4 with inactive attribute. On NSO, we can add inactive annotation by deactivate/activate command from CLI, and NETCONF/RESTCONF can accept in normal attribute in nodes.

Creating app1 and app2 from CLI

admin@ncs# conf
Entering configuration mode terminal
admin@ncs(config)# server app app1
admin@ncs(config-app-app1)# server app app2
admin@ncs(config-app-app3)# exit
admin@ncs(config)# deactivate server app app2
admin@ncs(config)# commit dry-run outformat xml
result-xml {
    local-node {
        data <server xmlns="http://com/example/test1">
               <app>
                 <name>app1</name>
               </app>
               <app inactive="inactive">
                 <name>app2</name>
               </app>
             </server>
    }
}
admin@ncs(config)#
admin@ncs(config)# commit
Commit complete.
admin@ncs(config)#

Creating app3 from NETCONF

First, here's the payload for the NETCONF <edit-data> operation. Please note that inactive attribute is added.

$ cat server-app3.xml
<server xmlns="http://com/example/test1">
  <app inactive="inactive">
    <name>app3</name>
  </app>
</server>

Then, netconf-console is used with the xml payload to create app3.

$ netconf-console --edit-data=server-app3.xml
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1">
  <ok/>
</rpc-reply>

Creating app4 from RESTCONF

In the same way, app4 is created with inactive attribute using RESTCONF.

$ cat server-app4.xml
<app inactive="inactive">
  <name>app4</name>
</app>
$ curl -X POST -u admin:admin -H 'Content-Type: application/yang-data+xml' \
http://localhost:8080/restconf/ds/ietf-datastores:running/test1:server \
-d @server-app4.xml
$

Set any data on /server/app/version

/server/app/version is a leaf of config false node. This is supposed to be entered by any app, but in this example, let's set data manually.

$ ncs_cmd -o -c 'set /server/app{app1}/version 1.0'
$ ncs_cmd -o -c 'set /server/app{app2}/version 1.0'
$ ncs_cmd -o -c 'set /server/app{app3}/version 1.0'
$ ncs_cmd -o -c 'set /server/app{app4}/version 1.0'

Status confirmation

So far, we have configured 4 apps in running, however app2, app3 and app4 are at inactive status.

$ netconf-console --get-data --db running -x /server
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1">
  <data>
    <server xmlns="http://com/example/test1">
      <app>
        <name>app1</name>
      </app>
      <app inactive="inactive">
        <name>app2</name>
      </app>
      <app inactive="inactive">
        <name>app3</name>
      </app>
      <app inactive="inactive">
        <name>app4</name>
      </app>
    </server>
  </data>
</rpc-reply>

Next, let's check the intended datastore. As you can see, app2, app3 and app4 are not listed.

$ netconf-console --get-data --db intended -x /server
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1">
  <data>
    <server xmlns="http://com/example/test1">
      <app>
        <name>app1</name>
      </app>
    </server>
  </data>
</rpc-reply>

Then, let's check operational datastore. Please notice that config false data is shown.

$ netconf-console --get-data --db operational -x /server
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1">
  <data>
    <server xmlns="http://com/example/test1">
      <app>
        <name>app1</name>
        <version>1.0</version>
      </app>
    </server>
  </data>
</rpc-reply>

From NCS CLI, we can see running and operational datastore as the below.

admin@ncs# show running-config server
server app app1
!
! Inactive
server app app2
!
! Inactive
server app app3
!
! Inactive
server app app4
!
admin@ncs#

To see the operational datastore, we will look at the operation-state container information. It is populated only when it's configured to do so in ncs.conf as like the below.

<ncs-config xmlns="http://tail-f.com/yang/tailf-ncs-config">
  <cli>
    <nmda>
      <show-operational-state>true</show-operational-state>
    </nmda>
  </cli>
</ncs-config>

Now we can show it in CLI.

admin@ncs# show operational-state server
server app app1
 version 1.0
!
admin@ncs#

Re: Device types supported by Cisco NSO NEDs

KJ Rossavik — Wed, 08 Jan 2020 08:42:15 GMT

Today all non-NETCONF NEDs (i.e. CLI/REST/TL1/etc.) are developed by the Cisco NSO NED team. NED development is a specialised skillset, so although theoretically others could do it, it is most cost-effective for everybody to leave it to the NED team. The exception to that is if a customer requires a NED for a bespoke system, i.e. something that is not generally available. In that case the NED would not be subject to productisation, since there is no market for it outside of the one customer. In that case we would point the customer towards one of the partners that we use for NED development, as they have the skillset and critical mass of people to be able to develop, maintain and support such a bespoke NED.

From a vendor perspective, rather than attempting to develop their own NED, it would make more sense to offer a NETCONF interface on their devices, so that the NED can be auto-generated.

Re: Device types supported by Cisco NSO NEDs

SiewSE55115 — Wed, 08 Jan 2020 00:51:30 GMT

Hi KJ Rossavik Do companies look for Cisco to develop NEDs for their devices or they can self help to create a NED on their own? For example, the hardware is a customized one but its communication protocol is standard like TL1 or SNMP. Many thanks in advance.

Re: Create a 'commserver' for USB Serial console ports with a Raspberry Pi

mbroders — Tue, 07 Jan 2020 10:21:33 GMT

Neat and elegant. Thanks.

Create a 'commserver' for USB Serial console ports with a Raspberry Pi

Emmanuel Tychon — Wed, 10 Feb 2021 16:49:46 GMT

Introduction

As a person working with Cisco's portfolio of IoT products you have probably realized that some new platforms are ditching away the old RJ45-based RS232 serial communication console in favour of the newer USB-based serial communication port. If this a good news for technicians as they are now able to connect a computer straight to the router console using just a mini-USB cable, this is not such a great news for those who need to operate serial connections remotely.

The purpose of a commserver is to map a serial console port to TCP port, so that using Telnet to the commserver one can actually talk directly to the equipment console port. This is very handy to have out-of-band management this way, as it works even when the main network is down, an access-list has been misconfigured, a router is stuck in ROMMON mode and plenty other hair pulling scenario.

With the classic RJ45 serial it was a simple task to use a router with a number of serial lines and connect them to console ports for out of band access. But you can't do that with USB... unless you want to use an active USB-to-RJ45 converter, which is messy and they are not that easy to find.

Proposed Solution

I had an old Raspberry Pi 2B+ lying around that I wanted to leverage, but it only has USB ports. You have four USB ports as standard, but I wanted more therefore added an additional board called UUGear BIG7 USB HUB but I'm sure other alternatives will work equally well. The purpose is really to extend the number of USB ports available from 4 up to 11.

Making serial USB ports predictable and persistent

I have used Raspbian as a base operating system, and on my setup and by default the first USB-to-serial connection will be device /dev/ttyACM0. This is not desirable! What we want is to be able to predict which Cisco device console is connected to which USB port, to map a predictable serial device name and ultimately map it to a specific TCP port. For example, if we connect a gateway console to the first USB, we want to map it to /dev/csco1, and to TCP/2001. We will do this my modifying the udev rules, but first we need to uniquely identify the USB ports.

To identify how your ports are mapped: plug in a Serial USB console and watch using "dmesg" on which port this new serial connection has been mapped. For example in my case it shows ttyACM0:

[16201.694459] usb 1-1.3.1: new full-speed USB device number 17 using dwc_otg
[16201.851950] usb 1-1.3.1: New USB device found, idVendor=05a6, idProduct=0009, bcdDevice= 0.00
[16201.851975] usb 1-1.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[16201.851987] usb 1-1.3.1: Product: Cisco USB Console
[16201.851997] usb 1-1.3.1: Manufacturer: Cisco
[16201.883380] cdc_acm 1-1.3.1:1.0: ttyACM0: USB ACM device

Now that I know the device name is ttyACM0, let's check for some unique identifier using:

udevadm info --name=/dev/ttyACM0 --attribute-walk

You should see a long list of attributes but the beginning is what is interesting for us. It could be something like:

looking at device '/devices/platform/soc/20980000.usb/usb1/1-1/1-1.3/1-1.3.1/1-1.3.1:1.0/tty/ttyACM0':
  KERNEL=="ttyACM0"
  SUBSYSTEM=="tty"
  DRIVER=="" 
[...]
looking at parent device '/devices/platform/soc/20980000.usb/usb1/1-1/1-1.3/1-1.3.1':
  KERNELS=="1-1.3.1"
  SUBSYSTEMS=="usb"
  DRIVERS=="usb"
  ATTRS{manufacturer}=="Cisco"

Since there can only be one USB driver in 1-1.3.1 this is enough for us to write the rules. Try other ports and see how the numbers are changing, for me this was the first USB port and then it goes 1-1.3.2, 1-1.3.3, ... 1-1.3.7. The udev mapping can be done by editing (or creating) the file in /etc/udev/rules.d/99-usb-serial.rules with the following content:

SUBSYSTEM=="tty",DRIVERS=="usb",KERNELS=="1-1.3.1",SYMLINK+="csco1"
SUBSYSTEM=="tty",DRIVERS=="usb",KERNELS=="1-1.3.2",SYMLINK+="csco2"
SUBSYSTEM=="tty",DRIVERS=="usb",KERNELS=="1-1.3.3",SYMLINK+="csco3"
SUBSYSTEM=="tty",DRIVERS=="usb",KERNELS=="1-1.3.4",SYMLINK+="csco4"
SUBSYSTEM=="tty",DRIVERS=="usb",KERNELS=="1-1.3.5",SYMLINK+="csco5"
SUBSYSTEM=="tty",DRIVERS=="usb",KERNELS=="1-1.3.6",SYMLINK+="csco6"
SUBSYSTEM=="tty",DRIVERS=="usb",KERNELS=="1-1.3.7",SYMLINK+="csco7"

Make sure that you restart udev with:

sudo /etc/init.d/udev restart

From this point on, when a serial-to-usb device is connected to USB port 1, it will be mapped to a serial device /dev/csco1, the USB port 2 will be mapped to /dev/csco2, and so on. This will make it very predictable for the next step.

Using ser2net to map serial ports to Telnet TCP ports

Now in order to map specific USB / Serial ports to TCP / Telnet connections there is a very handy software called ser2net. We are very lucky as this is in the Raspbian repository and it can therefore be installed with:

sudo apt install ser2net

Ater the previous where we made the serial ports predictable this will be very simple. One can configure ser2net by editing the file /etc/ser2net.conf with the following:

2001:telnet:600:/dev/csco1:9600 8DATABITS NONE 1STOPBIT -XONXOFF -RTSCTS banner kickolduser
2002:telnet:600:/dev/csco2:9600 8DATABITS NONE 1STOPBIT -XONXOFF -RTSCTS banner kickolduser
2003:telnet:600:/dev/csco3:9600 8DATABITS NONE 1STOPBIT -XONXOFF -RTSCTS banner kickolduser
2004:telnet:600:/dev/csco4:9600 8DATABITS NONE 1STOPBIT -XONXOFF -RTSCTS banner kickolduser
2005:telnet:600:/dev/csco5:9600 8DATABITS NONE 1STOPBIT -XONXOFF -RTSCTS banner kickolduser
2006:telnet:600:/dev/csco6:9600 8DATABITS NONE 1STOPBIT -XONXOFF -RTSCTS banner kickolduser
2007:telnet:600:/dev/csco7:9600 8DATABITS NONE 1STOPBIT -XONXOFF -RTSCTS banner kickolduser

The "kickolduser" is optional but can be very handy: it will disconnect any existing session still active on that serial port and give precedence to the last arrived.

Make sure to restart ser2net for the configuration to take effect (sudo systemctl restart ser2net).

Testing

You can then telnet straight to a given console by using the corresponding TCP port number, for example for the console connected to my first USB port:

etychon@ETYCHON-M-D2ZR~ telnet 192.168.2.7 2001
Trying 192.168.2.7...
Connected to 192.168.2.7.
Escape character is '^]'.
ser2net port 2001 device /dev/csco1 [9600 N81] (Debian GNU/Linux)
ic3k>

That's it - now I'm on the IC3000 serial-USB console using Telnet on a Raspberry Pi!

Thank you for reading, and let us know in the comments should you have any other ways you are willing to share?

Re: HTTPFeedback

elvis.cruz — Mon, 16 Dec 2019 22:36:44 GMT

Hello,

I am attempting to log into the web gui of one of my codecs (Webex Pro) and receive a "Bad Gateway The request could not be served due to a proxy error.". I also ran Putty and under xstatus HTTPFeedback does not populate like my other codecs. Is there a way of resolving this by turning something on/off?

NSO Developer Days US 2019: NSO 5.x Migration

Nicklas Wagerth — Mon, 16 Dec 2019 11:19:06 GMT

Martin Akerstrom, NSO Solutions Architect

NSO Developer Days US 2019:NSO in Docker

Nicklas Wagerth — Fri, 13 Dec 2019 12:27:51 GMT

Kristian Larsson, Architect
See how placing NSO in a Docker container can help you streamline your development, testing and deployment flow. Kristian goes through why you might want to use Docker for your NSO development and shows the official NSO Dockerfile as well as how to apply it to your NSO projects.

NSO Developer Days US 2019: What's Up NSO? Optimize and Troubleshoot

Nicklas Wagerth — Tue, 10 Dec 2019 13:05:02 GMT

Speaker Sebastian Strollo, Principal Engineer

Learn more about your NSO system fundamentals and how to optimize and troubleshoot in case performance is slower than you expect.

NSO Developer Days US 2019: A Low Code Approach to Brownfield Service Discovery

Nicklas Wagerth — Thu, 05 Dec 2019 21:07:56 GMT

Dan Sullivan, Principal Solutions Architect

A low code approach to brownfield service discovery in NSO

NSO Developer Days US 2019: NSO In and On Kubernetes - Lab instructions

Nicklas Wagerth — Thu, 05 Dec 2019 15:43:28 GMT

See the slides here

NSO Developer Days US 2019: NSO In and On Kubernetes

Nicklas Wagerth — Thu, 05 Dec 2019 15:44:40 GMT

Fredrik Jansson, Principal Engineer & John Mullooly, Distinguished Architect, Sales
In the first half of this lab, we build a k8s deployment of NSO from the ground up. We will start packaging NSO in a docker container, from there we will gradually build up to having Helm charts that can deploy NSO in a k8s cluster. In the second half, we will turn things upside down. We will use NSO to orchestrate deployment and "day-n" configuration of an example cloud-native application running in k8s via NSO integration with Helm. This is an intermediate lab; You need to be comfortable with container concepts. You need to be comfortable with container concepts, hands-on container experience will help but is not mandatory.

Find lab instructions here.

NSO Developer Days US 2019: Key Note by Fredrik Lundberg

Nicklas Wagerth — Thu, 05 Dec 2019 14:52:04 GMT

Fredrik Lundberg, Dir. Strategy & Planning, NSO

NSO State of the Union

NSO Developer Days US 2019: Fastmap Templates in Cisco NSO

Nicklas Wagerth — Thu, 05 Dec 2019 14:45:00 GMT

Michael Maddern, Technical Marketing Engineer

This session will demonstrate the use of template-based fastmap in Cisco NSO. It’s easy to underestimate how quickly and simply a new service can be configured based on a synced configuration and templates. Rapid service velocity can be a major competitive differentiator. The presentation will include an introduction to the templating functionality and a demo focused on creating a service from scratch using template-based fastmap in Cisco NSO.

NSO Developer Days US 2019: Network Automation Delivery Model

Nicklas Wagerth — Thu, 05 Dec 2019 14:31:04 GMT

Fredrik Swahn, Product Marketing Manager
Network automation is high on the agenda, but remains a daunting challenge, with results often failing to live up to expectations. Many are struggling with both the technical and organizational changes it requires. With years of experience of implementing network automation using the Cisco Network Services Orchestrator (NSO), we have developed a Network Automation Delivery Model (NADM) that aims to guide customers in their journey towards a fully automated network. A powerful, standardized, model that covers the essential parts of a network automation transformation will be presented and discussed. The model covers all four perspectives of People, Process, Technology, and Organization and therefore targets all the stakeholders from C-level decision makers to the network engineers that execute the operations of the network as of today. During the session, both challenges and success factors for implementing network automation will be presented and put into context.

NSO Developer Days US 2019: Workflow vs NSO Service vs Nano Service

Nicklas Wagerth — Thu, 05 Dec 2019 14:16:22 GMT

Viktor Leijon, Technical Leader, NSO

In this presentation, Viktor gives an overview of the design choices that goes into designing an orchestration solution, explaining the motivation for key NSO features and explain how that position NSO within the larger automation landscape. We will take a look at the principles behind orchestration in general and NSO in particular and discuss how they combine to form the system we have today as well as how to integrate that into a larger solution.

NSO Developer Days US 2019: A Breakneck Journey into Network Service Based Automation in DevNet Sandbox

Nicklas Wagerth — Thu, 05 Dec 2019 13:55:49 GMT

Hank Preston, Principal Engineer, Cisco DevNet
Sandbox is a public Software as a Service offering from Cisco DevNet that provides developers access to Cisco hardware and software (as well as relevant third-party and open source solutions) for building applications and automation using the APIs and platforms provided in them. Under the hood, this means we operate data center networks that aren’t that different from most enterprises, but with some unique design and scale needs. We recently decided to go all-in with network automation and chose Cisco NSO to be our tool for defining and managing the network services that power Sandbox. As stars aligned, we also were building a new data center with a very short timeline… hence our breakneck journey into network service automation.

NSO Developer Days US 2019: Nano services presentation

tryeng — Thu, 05 Dec 2019 11:09:57 GMT

Presentation performed at NSO Developer days in New York 2019

Re: Blackboard Integration

WaleedReda — Mon, 02 Dec 2019 13:57:40 GMT

In order to connect the integration, we would need to start with the webex URL and if its connected to their single sign on, we would need someone at Cisco to connect to the backend of the webex account to add some information.

Re: Adding Translation Pattern

nbraun1987 — Mon, 18 Nov 2019 23:26:03 GMT

The below is working for me - take the new out of your <newTransPattern> tags

IMPORTANT --- the add below was created for blocking calls.

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.cisco.com/AXL/API/11.5">
<soapenv:Header/>
<soapenv:Body>
<ns:addTransPattern>
<transPattern>
<routePartitionName>dummy_part</routePartitionName>
<description>AXL Test</description>
<pattern>8675309</pattern>
<blockEnable>true</blockEnable>
<releaseClause>Call Rejected</releaseClause>
<usage>Translation</usage>
</transPattern>
</ns:addTransPattern>
</soapenv:Body>
</soapenv:Envelope>

Re: C++ guidlines

Zeevik — Mon, 21 Oct 2019 06:28:39 GMT

Hi,

Several years ago, I've developed a C++ process (running on Linux RedHAT 7) that connects via SSH to Cisco routers (IOS 12.2).

The process's task is to monitor (retrieve&update) some preconfigured ACL and it uses the libshh 0.7.0 version (https://www.libssh.org/?s=libssh+0.7.0).

The ssh_set_blocking(session, 1) command is activated prior to the ssh_connect(session) one.

Several months ago, we've received two new Cisco routers with the IOS 15.1, and since then there is the SSH connection problem.

I've written a simple tester that loops (100 cycles) over all the Cisco routers (IOS 12.2 and the new IOS 15.1 ones). The tester just connects, disconnects and sleeps for 2 seconds.

All the 100 tests performed on the Cisco routers with IOS 12.2 - were successful.

Only 75-85 tests performed on the Cisco routers with IOS 15.1 - were successful, the other 15-25 attempts failed due to the timeout error.

What are the IOS 15 changes that could cause this problem, and how may I solve the problem?

Thanks

Zeev

Re: Create a device using REST

yfherzog — Sun, 06 Oct 2019 07:53:46 GMT

if you want to use POST call then you'd need to provide the URI to the device-name list, and provide the new device-name instance in the payload.

If you want to add multiple devices to a group, you need to run a PATCH call on the same URI, and provide all new instances in the payload.

Re: Create a device using REST

Islam_Hassanin — Thu, 26 Sep 2019 11:56:49 GMT

what if i want to add device to specific group, i tried to do it like below using python:

#add device to group
resp = requests.post("http://localhost:8080/api/running/devices/device-group/xr-test/device-name/xr1" , auth=auth, headers=headers)
print(resp)

put it response with 404.

any idea about how to add multiple devices to a group ?

Getting a gateway serial number from Cisco IOx

Emmanuel Tychon — Tue, 24 Sep 2019 12:37:53 GMT

If you are required to retrieve the gateway serial number from an IOx application, environment variables set by the Cisco Application Framework (CAF) are automatically set in the execution environment in the /data/.env file.

You can access this file from your IOx application directly, or invoke it to set all the variables as environment variables, such as:

/ # source /data/.env
/ # echo $CAF_SYSTEM_SERIAL_ID
FGL23362022

To see all the variables available in an IOx container, this can be done by accessing the console with the ioxclient utility. The following command (to get console to the application called iox-serial) and then list all the variables:

 etychon@squeeze:~/iox/iox-serial$ ioxclient app con iox_serial
Currently active profile :  default
Command Name:  application-console
Console setup is complete..
Running command : [ssh -p 2222 -i iox_serial.pem appconsole@192.168.2.231]
/ # cat /data/.env
#!/bin/sh
export CAF_APP_PERSISTENT_DISK_SIZE_KB=102400
export CAF_APP_MEMORY_SIZE_KB=51200
export CAF_SYSTEM_PRODUCT_ID=IR829M-2LTE-EA-EK9
export CAF_SYSTEM_NAME=IR800
export CAF_SS_PORT=9443
export CAF_APP_APPDATA_DIR=/data/appdata
export CAF_APP_CONFIG_DIR=/data
export CAF_SS_IP_ADDR=192.168.1.6
export CAF_APP_CORE_DIR=/tmp/cores
export CAF_APP_LOG_DIR=/data/logs
export CAF_SYSTEM_SERIAL_ID=FGL23362022
export CAF_APP_PERSISTENT_DIR=/data
export CAF_APP_CPU_SHARES=342
export CAF_APP_ID=iox_serial
export CAF_APP_USERNAME=root
export HOST_DEV1=/dev/ttyACM0
export CAF_SYSTEM_UUID=7581eb7b-8c04-4412-b2bb-503598f06a72/

To learn more about these variables check the "Environment Variables" section of Cisco IOx DevNet Documentation: https://developer.cisco.com/docs/iox/#!application-development-concepts/application-development-concepts

Getting a gateway Cellular RSSI from Cisco IOx

Emmanuel Tychon — Mon, 23 Sep 2019 18:10:06 GMT

How to I get the gateway Cellular RSSI from Cisco IOx ?

If you have an IOx application that requires tp capture the cellular modem signal strength (for example to include in telemetry data along with GPS position and map signal with location), you will find that there is no direct way to get it from IOx. The reason is that the application hosting environment is virtualized and therefore Cisco IOS metrics are not directly accessible.

Simple Network Management Protocol (SNMP) which is an IOS feature can be leverage to exposed this variable or any other SNMP variable. SNMP can be easily configured on the gateway with just a few lines:

On a Cisco IR829 with guest-os running in the 192.168.1.0/24 range, where 192.168.1.1 is being assigned to the virtual Gigabit Ethernet 5 interface, then this is what it takes to give SNMP access to all the virtual instances running on the gateway:

IR829(config)# access-list 10 permit 192.168.1.0 0.0.0.255
IR829(config)# snmp-server community public RO 10

The IOx application can then poll the right SNMP OIDs straight from the gateway, and this OID may change depending on the particular model. Always refer the device's MIB.

For example in Python to poll both cellular interface's RSSI on a Cisco IR829M:

from pysnmp.entity.rfc3413.oneliner import cmdgen
import time

SNMP_HOST = '192.168.1.1'
SNMP_PORT = 161
SNMP_COMMUNITY = 'public'


cmdGen = cmdgen.CommandGenerator()

errorIndication, errorStatus, errorIndex, varBinds = cmdGen.getCmd(
    cmdgen.CommunityData(SNMP_COMMUNITY),
    cmdgen.UdpTransportTarget((SNMP_HOST, SNMP_PORT)),
    '1.3.6.1.4.1.9.9.661.1.3.4.1.1.1.20',
    '1.3.6.1.4.1.9.9.661.1.3.4.1.1.1.21'
)

for name, val in varBinds:
    print('%s = %s' % (name.prettyPrint(), val.prettyPrint()))

You should see the RSSI signal (in dBm) returned like so:

SNMPv2-SMI::enterprises.9.9.661.1.3.4.1.1.1.20 = -128
SNMPv2-SMI::enterprises.9.9.661.1.3.4.1.1.1.21 = -128

Re: pi_wlan_report.py

jegan_rajappa — Sun, 22 Sep 2019 07:15:23 GMT

Hi Spencer,

Thanks for sharing Python Script.

This script brings only 100 lines in CSV, I mean I can see only 100 SSID from few WLC, but I have 450+ WLC in PI and these WLC has 1000+ SSID.

Please advice.

Re: builtin:grammar

nicole.burmeister — Tue, 27 Aug 2019 21:05:12 GMT

Is this still a known issue with a form element? That the ; in a grammar url fails to parse properly and content is stripped? This is an old thread, but here's hoping Cisco addressed this in the last 7 years.

Re: CSMP_Spec_30July2014.pdf

shenruizhan3732 — Fri, 16 Aug 2019 23:34:59 GMT

Hello Mr. Mathaker:

Sorry to bother you. But is it possible that you give us any suggestion about where can we download the "Csmprequest.jar" software? I'm doing experiment on IR509 and from your post in CISCO community I found this software very useful. But I search it on the Internet and also CISCO's website and can't find it. Could you give us any suggestions?

You're the only person I know that post messages about csmprequest.jar software in CISCO community, that's why I ask this question here. I'd say sorry if I have bothered you, and would highly appreciate you if you can give us any suggestion. Thanks.

Re: NSO Developer Days 2019: Network Programmability with YANG -- The YANG Book

tsiemers1 — Wed, 31 Jul 2019 19:13:25 GMT

Just finished the book, highly recommended for anybody getting into the NETCONF and yang. Very good read with examples to go along with it.

Re: NSO Developer Days 2019: Brownfield Service Reconcile Operations

lweddewer — Thu, 18 Jul 2019 11:08:26 GMT

Shouldn't the code of this solution be provided?

Regards

Lothar

Help me Caculator PortIndext Cisco ASR 9010+7600

minhanh01081 — Sat, 06 Jul 2019 10:18:44 GMT

example:

Name/OID: ifDescr.447; Value (OctetString): TenGigE0/7/1/2

please help me , how to caculator ifDescr of interface.

gi0/1/1/1-->ifDescr=?.....

thank!

Re: NSO Developer Days 2019: NSO Interop, EANTC and YANG

dbs_hh — Mon, 01 Jul 2019 08:41:42 GMT

Hi Jan,

the download didn't work. It stopped somewhere in the middle.

NSO Developer Days 2019: EXPERIENCE THE THRILL OF FOILING Two Flying Dutchman stories demystified

Nicklas Wagerth — Mon, 01 Jul 2019 08:16:30 GMT

Abstract: Telindus, SURFnet and T-Mobile share their outcomes of different automation strategies. How to go above and beyond the traditional way of networking to experience the thrill of foiling. The thrill to master core and B2B connectivity services in full flight with automation is changing the networking landscape for good. The future of networking is like foiling is for sailing: agility and speed with less effort and reduced risks. Telindus enabled this foiling state with Cisco NSO for T-Mobile and SURFnet with different approaches.

Speakers:

Wouter Huisman, SurfNet

Albert Lentink, Telindus

Re: 11 Option Menu in CVP Studio

manojpatil_in — Sun, 30 Jun 2019 07:07:34 GMT

Where we have to configure \* in form element

Also how to ignore metacharacter in CVP

Re: NSO Developer Days 2019: Telefonica - A Glance At Our Automation Journey

carlos.martinezcabrera — Thu, 27 Jun 2019 18:38:28 GMT

Amazing experience! thinking of NSODevDays2020!

Re: NSO Developer Days 2019: Opening Welcome

lweddewer — Thu, 27 Jun 2019 12:32:34 GMT

Yes, now it works!

Re: NSO Developer Days 2019: Roadmap and Future outlook

Chri_Erenti — Thu, 27 Jun 2019 11:29:55 GMT

Now it works! Thank you

Re: NSO Developer Days 2019: Roadmap and Future outlook

Jan Lindblad — Thu, 27 Jun 2019 11:23:19 GMT

Thanks for the heads up. Not sure why the system does that. Anyway, try again now. I uploaded the file again, and it seems to work now.

Re: NSO Developer Days 2019: Roadmap and Future outlook

Chri_Erenti — Thu, 27 Jun 2019 11:07:53 GMT

The download of the slides does not work... it is only possible to view them.

NSO Developer Days 2019: Telefonica - A Glance At Our Automation Journey

Nicklas Wagerth — Thu, 27 Jun 2019 10:34:21 GMT

Abstract: From Telefonica International we are proud to share with the community our experience using Cisco NSO. The evolution from NetOps towards NetDevOps perspective to carry out our daily network operations and the use of Cisco NSO as core SDN controller of proprietary integrated solutions are the base of our automation journey to perform current and arising network challenges.

Speakers:

Carlos Cabrera, Telefonica, Network Developer

Javier Marquez, Telefonica, Network Developer

NSO Developer Days 2019: AUTLAN – The Automation Journey of an Integrated Telecommunications Company

Nicklas Wagerth — Thu, 27 Jun 2019 10:25:54 GMT

Abstract: With a strategy to lead in customer experience, technology and business productivity, Deutsche Telekom has some great aspirations. We are more than an infrastructure company; in this complex digital world we make life easier for people enriching it at every opportunity - at home and at work, anytime, anyplace.

Speakers:

Johannes Peternek, DT, Referent Technikbereitstellung IP

Annand Sanghani, Itential, Sales Engineer