Hello,
In V2R2C50, found it showing with cpdt_port_down_status.log, link status is the information of the physical layer.
link status is 0 ---- link down
link status is 1 ---- link up
link status is 3 ---- fault down (local fault or remote fault), detail fault reason you may check at log.log files.
https://support.huawei.com/hedex/hdx.do?docid=EDOC1000147767&id=DEVM_hwLocalFaultAlarm&lang=en
Link status 0 is PHY chip down which means physical down.
Link status 3 because detect the fault, but in this time the PHY status can be up down or may also be an intermediate state from up to down.
There are an independent event and record in the register with cpdt_port_down_status.log files.
The display interface is only showing current status up & down, but the detail and history reason we need to check in the cpdt_port_down_status.log.
For more details, please refer to RFC document 802.3-2008_section4.pdf CL44-CL49.
Do “0”, “1” and “3” represent the whole scope of the values which can describe link status?
YES
Please explain more about “intermediate state from up to down” – what is this state?
Example: the PHY status is up, and in this time port received the local fault & remote fault. And then the link status will become to 3.
Later time the PHY status will become to down. That is “intermediate state from up to down”
In client-side, you can see the port status with up & down, but why and what is the reason for the port is down in history, that need check-in the cpdt_port_down_status.log and log.log files, so the link status in logs files is only for troubleshooting to record the down reason, not a real port status.
And what are the possible reasons for link status 3?
In summary:
1) "/ COMMA /" code cannot be detected by PMA
2) PMA detects "/ COMMA /" encoding misalignment
For more detail, about fault, you can reference RFC document 802.3-2008_section4.pdf CL44-CL49.
Glad to help you! Any further questions, let us know.
