An unexpected restart of the MRATE-4xQDD PIC is observed on the MX10008 router after configuring port speed on interfaces. 

Model: mx10008
Junos: 21.4R3-S6.1
JUNOS OS Kernel 64-bit

Hardware inventory:
Item       Version Part number Serial number   Description
Chassis                 ****                   JNP10008 [MX10008]
FPC 1      REV 38  750-114437  ****3595        JNP10K-LC9600
 PIC 0             BUILTIN     BUILTIN         MRATE-4xQDD

May 1 07:35:08.721 2026 router mgd[55575]: UI_CMDLINE_READ_LINE: User 'user@router', command 'set chassis fpc 1 pic 5 port 0 speed 400g '
May 1 07:35:38.470 2026 router mgd[55575]: UI_COMMIT: User 'user@router' requested 'commit' operation (comment: **********)

May 1 07:35:52.047 2026 router-fpc1 hwdfpc[14486]: fru_state_transition /Chassis[0]/Fpc[1]/Pic[5] ONLINE -> TRANSITION_OFFLINE
May 1 07:35:56.977 2026 router-fpc1 hwdfpc: HWD_FRU_OFFLINE_NOTICE: FRU offline pic5
May 1 07:35:56.977 2026 router chassisd[11104]: CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power off (jnxFruContentsIndex 8, jnxFruL1Index 2, jnxFruL2Index 6, jnxFruL3Index 0, jnxFruName PIC: MRATE-4xQDD @ 1/5/*, jnxFruType 11, jnxFruSlot 1, jnxFruOfflineReason 8, jnxFruLastPowerOff 1404892226, jnxFruLastPowerOn -969582218)
May 1 07:35:56.977 2026 router chassisd[11104]: CHASSISD_SNMP_TRAP3: ENTITY trap generated: entStateOperDisabled (entPhysicalIndex 91, entStateAdmin 2, entStateAlarm 0)
May 1 07:35:56.977 2026 router-fpc1 hwdfpc[14486]: fru_state_transition /Chassis[0]/Fpc[1]/Pic[5] TRANSITION_OFFLINE -> OFFLINE
May 1 07:35:56.977 2026 router-fpc1 hwdfpc[14486]: fru_state_transition /Chassis[0]/Fpc[1]/Pic[5] OFFLINE -> POWER_OFF_START
May 1 07:35:56.977 2026 router-fpc1 hwdfpc[14486]: fru_state_transition /Chassis[0]/Fpc[1]/Pic[5] POWER_OFF_START -> POWER_OFF

It is expected behavior for the MRATE-4xQDD PIC to restart when there is a mismatch between the PIC speed profile and the configured port speed profile. 

The PIC ports on the JNP10K-LC9600 support multiple port-speed configurations through predefined profiles, including:

- All supported ports in 10GE mode

- All supported ports in 25GE mode

- All supported ports in 40GE mode

- All supported ports in 100GE mode

- All supported ports in 400GE mode

- Flexible per-port configuration (10/25/40/100/400GE)

By default, when the PIC boots up, it loads a default PIC profile where all ports are configured to operate in 400GE mode. Port profiles 1 through 5 are configured at the PIC level, while profile 6 allows per-port level configuration. When switching from a PIC-level speed profile to a port-level configuration, the PIC undergoes a restart, and ports without an explicitly defined speed may disappear.

Lab Scenario 1: No PIC restart is observed when the configured PIC speed profile matches the default PIC profile.

user@router> show chassis hardware |match fpc 
May 19 11:15:07
FPC 1      REV 38  750-114437  ****3595     JNP10K-LC9600

user@router> show interfaces et-1/5/[0-3] | match "Physical|Speed" 
May 19 11:22:30

Physical interface: et-1/5/0, Enabled, Physical link is Down
 Link-level type: Ethernet, MTU: 1514, MRU: 1522, Speed: 400Gbps, BPDU Error: None, Loop Detect PDU Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled

Physical interface: et-1/5/1, Enabled, Physical link is Down
 Link-level type: Ethernet, MTU: 1514, MRU: 1522, Speed: 400Gbps, BPDU Error: None, Loop Detect PDU Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled

Physical interface: et-1/5/2, Enabled, Physical link is Down
 Link-level type: Ethernet, MTU: 1514, MRU: 1522, Speed: 400Gbps, BPDU Error: None, Loop Detect PDU Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled

Physical interface: et-1/5/3, Enabled, Physical link is Down
 Link-level type: Ethernet, MTU: 1514, MRU: 1522, Speed: 400Gbps, BPDU Error: None, Loop Detect PDU Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled

user@router# set chassis fpc 1 pic 5 pic-mode 400G 
May 19 11:28:31

user@router# commit and-quit 
May 19 11:28:36

user@router> show interfaces et-1/5/[0-3] | match "Physical|Speed"   
May 19 11:28:54

Physical interface: et-1/5/0, Enabled, Physical link is Down
 Link-level type: Ethernet, MTU: 1514, MRU: 1522, Speed: 400Gbps, BPDU Error: None, Loop Detect PDU Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled

Physical interface: et-1/5/1, Enabled, Physical link is Down
 Link-level type: Ethernet, MTU: 1514, MRU: 1522, Speed: 400Gbps, BPDU Error: None, Loop Detect PDU Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled

Physical interface: et-1/5/2, Enabled, Physical link is Down
 Link-level type: Ethernet, MTU: 1514, MRU: 1522, Speed: 400Gbps, BPDU Error: None, Loop Detect PDU Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled

Physical interface: et-1/5/3, Enabled, Physical link is Down
 Link-level type: Ethernet, MTU: 1514, MRU: 1522, Speed: 400Gbps, BPDU Error: None, Loop Detect PDU Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled

Lab Scenario 2: PIC restart is observed when the port speed on FPC1 PIC5 Port 0 is explicitly set to 400G, causing a mismatch with the active PIC speed profile. This results in a PIC reinitialization. During this process, interface et-1/5/0 is manually set to 400G, while other ports on the PIC disappear because they do not have explicit speed configurations applied.

user@router# set chassis fpc 1 pic 5 port 0 speed 400g   
May 19 11:33:00

May 19 11:33:08.250 router-fpc1 hwdfpc[16607]: fru_state_transition /Chassis[0]/Fpc[1]/Pic[5] ONLINE -> TRANSITION_OFFLINE
May 19 11:33:12.411 router-fpc1 hwdfpc: HWD_FRU_OFFLINE_NOTICE: FRU offline pic5
May 19 11:33:12.411 router-re0 chassisd[16724]: CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power off (jnxFruContentsIndex 8, jnxFruL1Index 2, jnxFruL2Index 6, jnxFruL3Index 0, jnxFruName PIC: MRATE-4xQDD @ 1/5/*, jnxFruType 11, jnxFruSlot 1, jnxFruOfflineReason 8, jnxFruLastPowerOff 35012290, jnxFruLastPowerOn 34974980)
May 19 11:33:12.411 router-fpc1 hwdfpc[16607]: fru_state_transition /Chassis[0]/Fpc[1]/Pic[5] TRANSITION_OFFLINE -> OFFLINE
May 19 11:33:12.411 router-fpc1 hwdfpc[16607]: fru_state_transition /Chassis[0]/Fpc[1]/Pic[5] OFFLINE -> POWER_OFF_START
May 19 11:33:12.411 router-fpc1 hwdfpc[16607]: fru_state_transition /Chassis[0]/Fpc[1]/Pic[5] POWER_OFF_START -> POWER_OFF

May 19 11:33:19.308 router-re0 chassisd[16724]: CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 8, jnxFruL1Index 2, jnxFruL2Index 6, jnxFruL3Index 0, jnxFruName PIC: MRATE-4xQDD @ 1/5/*, jnxFruType 11, jnxFruSlot 1, jnxFruOfflineReason 2, jnxFruLastPowerOff 35012290, jnxFruLastPowerOn 35012980)
May 19 11:33:19.310 router-fpc1 hwdfpc[16607]: fru_state_transition /Chassis[0]/Fpc[1]/Pic[5] POWER_OFF -> POWER_ON_PERMISSION
May 19 11:33:24.140 router-fpc1 hwdfpc[16607]: fru_state_transition /Chassis[0]/Fpc[1]/Pic[5] POWER_ON_PERMISSION -> POWER_ON_START
May 19 11:33:24.141 router-fpc1 hwdfpc[16607]: fru_state_transition /Chassis[0]/Fpc[1]/Pic[5] POWER_ON_START -> POWER_ON
May 19 11:33:25.424 router-fpc1 hwdfpc: HWD_FRU_ONLINE_NOTICE: FRU online pic5
May 19 11:33:25.426 router-re0 chassisd[16724]: CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface device for et-1/5/0
May 19 11:33:25.427 router-re0 kernel: PIC(1/5/3615): pic add successful
May 19 11:33:25.423 router-fpc1 hwdfpc[16607]: fru_state_transition /Chassis[0]/Fpc[1]/Pic[5] POWER_ON -> TRANSITION_ONLINE
May 19 11:33:25.424 router-fpc1 hwdfpc[16607]: fru_state_transition /Chassis[0]/Fpc[1]/Pic[5] TRANSITION_ONLINE -> ONLINE

user@router> show interfaces et-1/5/[0-3] | match "Physical|Speed"   
May 19 11:34:08
Physical interface: et-1/5/0, Enabled, Physical link is Down
 Link-level type: Ethernet, MTU: 1514, MRU: 1522, Speed: 400Gbps, BPDU Error: None, Loop Detect PDU Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled

Lab Scenario 3: No PIC restart is observed. This is a continuation of Scenario 2. In this case, the port speed for et-1/5/0 was modified to 100G. Since no PIC-level speed profile for PIC5 (i.e., port-level configuration is in use), the change does not trigger a PIC restart.

user@router# set chassis fpc 1 pic 5 port 0 speed 100g  
May 19 11:35:44

user@router# show | compare 
May 19 11:35:46
[edit chassis fpc 1 pic 5 port 0]
-   speed 400g;
+   speed 100g;

user@router# commit and-quit 

Lab Scenario 4: No PIC restart is observed. This is a continuation of Scenarios 2 and 3. In this case, a new port et-1/5/1 was added with a speed of 400G. Since the PIC is operating under port-level configuration (and not a PIC-level speed profile), adding the new port does not trigger a PIC restart.

user@router# show | compare 
May 19 11:51:44
[edit chassis fpc 1 pic 5]
+   port 1 {
+     speed 400g;
+   }

user@router# commit and-quit 
May 19 11:51:53

user@router> show interfaces et-1/5/[0-3] | match "Physical|Speed" 
May 19 11:52:52
Physical interface: et-1/5/0, Enabled, Physical link is Down
 Link-level type: Ethernet, MTU: 1514, MRU: 1522, Speed: 100Gbps, BPDU Error: None, Loop Detect PDU Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled

Physical interface: et-1/5/1, Enabled, Physical link is Down

 Link-level type: Ethernet, MTU: 1514, MRU: 1522, Speed: 400Gbps, BPDU Error: None, Loop Detect PDU Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled