|
This behavior comes from the fact that the xpdr-type had been introduced with release 2.0 of OpenROADM models. This field is contained in the xponder list which has not been forced as mandatory. So, when a xpdr node configuration contains that list of xponder, we can read this xpdr-type and set it in the mapping, but in our xpdra and xpdrc node configurations, we stayed with the same device configurations as in release 1.2.1, it means without this list of xponder. Since the xpdr-type was not present in the node configuration, it was neither set in the mapping.
Since in version 1.x of OpenROADM models there was only tpdr as xponder node type, and OpenROADM recommends using the list of xponder from version 2.0, we can consider that if the xpdr device configuration does not contain any list of xponder, it is a Transponder, and thus we can set "tpdr" in the corresponding mapping.
|