When breakout ET8001-2FR4 to 2x400G, and configstates would be ConfigSuccess for 4 lanes and ConfigUndefined for the others.
root@ais800-64o-1:/home/admin# show interfaces transceiver status Ethernet0
Ethernet0:
Tx fault flag on media lane 1: N/A
Tx fault flag on media lane 2: N/A
Tx fault flag on media lane 3: N/A
Tx fault flag on media lane 4: N/A
Tx fault flag on media lane 5: N/A
Tx fault flag on media lane 6: N/A
Tx fault flag on media lane 7: N/A
Tx fault flag on media lane 8: N/A
Rx loss of signal flag on media lane 1: False
Rx loss of signal flag on media lane 2: False
Rx loss of signal flag on media lane 3: False
Rx loss of signal flag on media lane 4: False
Rx loss of signal flag on media lane 5: False
Rx loss of signal flag on media lane 6: False
Rx loss of signal flag on media lane 7: False
Rx loss of signal flag on media lane 8: False
TX disable status on lane 1: False
TX disable status on lane 2: False
TX disable status on lane 3: False
TX disable status on lane 4: False
TX disable status on lane 5: False
TX disable status on lane 6: False
TX disable status on lane 7: False
TX disable status on lane 8: False
Disabled TX channels: 0
Current module state: ModuleReady
Reason of entering the module fault state: No Fault detected
Datapath firmware fault: False
Module firmware fault: False
Module state changed: False
Data path state indicator on host lane 1: DataPathActivated
Data path state indicator on host lane 2: DataPathActivated
Data path state indicator on host lane 3: DataPathActivated
Data path state indicator on host lane 4: DataPathActivated
Data path state indicator on host lane 5: DataPathActivated
Data path state indicator on host lane 6: DataPathActivated
Data path state indicator on host lane 7: DataPathActivated
Data path state indicator on host lane 8: DataPathActivated
Tx output status on media lane 1: True
Tx output status on media lane 2: True
Tx output status on media lane 3: True
Tx output status on media lane 4: True
Tx output status on media lane 5: True
Tx output status on media lane 6: True
Tx output status on media lane 7: True
Tx output status on media lane 8: True
Rx output status on host lane 1: True
Rx output status on host lane 2: True
Rx output status on host lane 3: True
Rx output status on host lane 4: True
Rx output status on host lane 5: True
Rx output status on host lane 6: True
Rx output status on host lane 7: True
Rx output status on host lane 8: True
Tx loss of signal flag on host lane 1: False
Tx loss of signal flag on host lane 2: False
Tx loss of signal flag on host lane 3: False
Tx loss of signal flag on host lane 4: False
Tx loss of signal flag on host lane 5: False
Tx loss of signal flag on host lane 6: False
Tx loss of signal flag on host lane 7: False
Tx loss of signal flag on host lane 8: False
Tx clock and data recovery loss of lock on host lane 1: False
Tx clock and data recovery loss of lock on host lane 2: False
Tx clock and data recovery loss of lock on host lane 3: False
Tx clock and data recovery loss of lock on host lane 4: False
Tx clock and data recovery loss of lock on host lane 5: False
Tx clock and data recovery loss of lock on host lane 6: False
Tx clock and data recovery loss of lock on host lane 7: False
Tx clock and data recovery loss of lock on host lane 8: False
Rx clock and data recovery loss of lock on media lane 1: False
Rx clock and data recovery loss of lock on media lane 2: False
Rx clock and data recovery loss of lock on media lane 3: False
Rx clock and data recovery loss of lock on media lane 4: False
Rx clock and data recovery loss of lock on media lane 5: False
Rx clock and data recovery loss of lock on media lane 6: False
Rx clock and data recovery loss of lock on media lane 7: False
Rx clock and data recovery loss of lock on media lane 8: False
Configuration status for the data path of host line 1: ConfigUndefined
Configuration status for the data path of host line 2: ConfigUndefined
Configuration status for the data path of host line 3: ConfigUndefined
Configuration status for the data path of host line 4: ConfigUndefined
Configuration status for the data path of host line 5: ConfigSuccess
Configuration status for the data path of host line 6: ConfigSuccess
Configuration status for the data path of host line 7: ConfigSuccess
Configuration status for the data path of host line 8: ConfigSuccess
When execute the api "api.scs_apply_datapath_init(host_lanes_mask)" for 0xf0,
the config status of lanes 1...4 would be ConfigUndefined and the config status of lanes 5...8 would be ConfigSuccess.
If the config state is ConfigUndefined, then it would do CMIS reinit for any set in the CONFIG_DB PORT table.
If the config state is ConfigUndefined, then it would do CMIS reinit when restart pmon.
Motivation and Context
In is_cmis_application_update_required, it check if the application is the same and if datapath is DataPathActivated.
It would not happen that the state of the config is fail, but the dataptach is activated.
I think skip CMIS int when config state is ConfigUndefined is saved.
Description
When breakout ET8001-2FR4 to 2x400G, and configstates would be ConfigSuccess for 4 lanes and ConfigUndefined for the others.
When execute the api "api.scs_apply_datapath_init(host_lanes_mask)" for 0xf0, the config status of lanes 1...4 would be ConfigUndefined and the config status of lanes 5...8 would be ConfigSuccess. If the config state is ConfigUndefined, then it would do CMIS reinit for any set in the CONFIG_DB PORT table. If the config state is ConfigUndefined, then it would do CMIS reinit when restart pmon.
Motivation and Context
In is_cmis_application_update_required, it check if the application is the same and if datapath is DataPathActivated. It would not happen that the state of the config is fail, but the dataptach is activated. I think skip CMIS int when config state is ConfigUndefined is saved.
How Has This Been Tested?
Additional Information (Optional)