Guest

Preview Tool

Cisco Bug: CSCvs55111 - OC-Platform mapping issues: fan/power-supply bad namespace, bad prefixes, and mismatch deviation

Last Modified

Sep 02, 2020

Products (1)

  • Cisco ASR 9000 Series Aggregation Services Routers

Known Affected Releases

7.0.12.BASE 7.1.1.BASE 7.2.1.BASE

Description (partial)

Symptom:
1. openconfig-platform:components/component/power-supply/config/openconfig-platform-psu:enabled leaf has data populated in a Netconf query made for a component of type POWER-SUPPLY even though it is listed in the deviation file as not supported.

2."fan" (and subnode "state") are defined in OC-Platform namespace; however, the Netconf response shows them inside OC-Platform-Fan namespace

   <component>
    <name>0/FT0-FAN_0_Speed</name>
    ...
    <fan xmlns="http://openconfig.net/yang/platform/fan">
     <state>
      <speed>19680</speed>
     </state>
    </fan>

3. Similar to 2., "power-supply" (and subnode "state") are defined in OC-Platform namespace; however, the Netconf response shows them inside OC-Platform-PSU namespace.


   <component>
    <name>0/PM0</name>
    <config>
     <name>0/PM0</name>
    </config>
    ...
    <power-supply xmlns="http://openconfig.net/yang/platform/psu">
     <state>
     ...

4. The Netconf response for openconfig-platform:components/component/power-supply/state/openconfig-platform-psu:enabled displays the leaf as a identityref even though this leaf has Boolean values.

<enabled xmlns:idx="http://openconfig.net/yang/platform-types">idx:true</enabled>

5. The identityref namespace for openconfig-platform:components/component/state/temperature/alarm-severity is wrongly represented as oc-platform-types instead of oc-alarm-types

Conditions:
This issues will be seen when a Netconf query will be made to fetch details via openconfig-platform.yang model as a whole or for power-supply/fan containers specifically.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.