napalm-automation/napalm

RPC on IOSXR for optics changes interface name in the output

Open

#435 建立於 2017年10月24日

在 GitHub 查看
 (0 留言) (0 反應) (0 負責人)Python (2,145 star) (553 fork)batch import
help wantediosxrquestion

描述

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

貢獻者指南

技術棧
python
領域
backend
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
unclear
前置要求
Python programmingNetwork device conceptsIOS XR RPC
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
15
研究方向
The issue describes a discrepancy in interface names returned by an RPC command for DWDM interfaces on IOS XR. Investigate the existing napalm iosxr driver code to understand how interface names are currently parsed. Look at the RPC response structure and explore alternative RPCs (e.g., show controllers) to retrieve correct names. Consider adding a mapping or fallback mechanism to align names with actual interface types (e.g., TenGigE).