Move tx_disable/tx_disabled_channel/rx_los/tx_fault to get_transceiver_status API#359
Move tx_disable/tx_disabled_channel/rx_los/tx_fault to get_transceiver_status API#359prgeor merged 5 commits intosonic-net:masterfrom longhuan-cisco:tx_disable
Conversation
|
@longhuan-cisco could you please paste the sample output in the PR description? |
|
How will the exiting CLI output will be impacted? for example: show interface transceiver eeprom -d ? |
sample output added. |
yea, verified it. |
today's |
|
@prgeor I've addressed the comments, could you take a look plz? |
|
@longhuan-cisco in the description i read two times the same API:- did u mean get_transceiver_bulk_status? For motiviation and context can you instead point to the HLD? |
|
@yxieca @StormLiangMS - Can you please help with cherry-pick for this to 202205 and 202211 |
Description
Move tx_disable/tx_disabled_channel from get_transceiver_bulk_status API (which serves DOM_SENSOR table) to get_transceiver_status API (which serves STATUS table)
Also, add get_transceiver_status API for non-CMIS optics for the following fields: rx_los tx_fault tx_disable tx_disabled_channel
Motivation and Context
According to updated schema of STATUS table in HLD, tx_disable/tx_disabled_channel should belong to STATUS table instead of DOM_SENSOR table.
How Has This Been Tested?
Verified on 400G optics, tx_disable/tx_disabled_channel are in the output of new status API, and in the DB as well.
Additional Information (Optional)