Frequent logs are reported in the MX10003 device as below.

Logs FPC[0]PIC[1] have invalid profile type 1, reson Both PICs need to be in port-mode or other pic should have number-of-port as 0

Frequent log  messages  are reported in MX10003 device

Mar 27 08:25:16.237 2024  DUT chassisd[8937]: summit_pic_port_profile_isvalid: FPC[0]PIC[1] have invalid profile type 1, reson Both PICs need to be in port-mode or other pic should have number-of-port as 0
Mar 27 08:25:16.237 2024  DUT chassisd[8937]: summit_pic_port_profile_isvalid: FPC[0]PIC[1] have invalid profile type 1, reson Both PICs need to be in port-mode or other pic should have number-of-port as 0

Chassis alarms report invalid port profile on PIC1 and PIC0

labroot@DUT# run show chassis alarms 
2 alarms currently active
Alarm time               Class  Description
2024-02-27 08:25:16 UTC  Minor  FPC 0 PIC 1 Invalid port profile configuration
2024-02-27 08:24:51 UTC  Minor  FPC 0 PIC 0 Invalid port profile configuration
 

This is due to mismatch of mode between PIC1 and PIC0. In the customer config we observed fpc0/pic1 ports 0 and ports 1 were configured as 100g but fpc0/pic0 was still pic-mode.

fpc 0 {
    pic 1 {
        port 0 {
            number-of-sub-ports 1;
            speed 100g;
        }
        port 1 {
            number-of-sub-ports 1;
            speed 100g;
        }
    }
}

Since pic1 in fpc0 is configured in port mode , fpc0/pic0 must also be configured in port mode

In order to resolve this Please follow below steps in MW

Note:: fpc0 /pic0/port 0 is assumed as 10g in this scenario , check the customer config and modify step 1 speeds accordingly.

1) Configure below on pic0 and pic1

set chassis fpc 0 pic 0 port 0 speed 10g  

2) Perform commit

3) Restart the FPC 0
 

run request chassis fpc slot 0 offline 

run request chassis fpc slot 0 online
 

4) Verify the alarms