napalm-automation/napalm

RPC on IOSXR for optics changes interface name in the output

Open

#435 opened on Oct 24, 2017

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (553 forks)batch import
help wantediosxrquestion

Repository metrics

Stars
 (2,145 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

In reference to napalm-automation/napalm-base#60:

RPC command provides a detailed output of the dwdm interfaces on the ASR. However, in the output, for instance, the interface names are specified as dwdm0/0/0/0 as opposed to TenGigE0/0/0/0. Now I am not sure how to validate the actual interface name due to the output of the RPC command.

Instead, if there were a way to retrieve the output provided by show controllers physical using an XML RPC, it would really help. I was hoping to have a discussion about this and figure out the way forward.

Issue moved from https://github.com/napalm-automation/napalm-iosxr/issues/30

Contributor guide

Research direction
Investigate the XML RPC response for optics interfaces on IOSXR and map the internal dwdm interface names to the actual hardware interfaces like TenGigE. Look into how other RPC commands (e.g., show controllers physical) can be invoked via XML to retrieve the correct names.
Tech stack
python
Domain
backendnetworking
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
PythonCisco IOSXR
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40