When the port speed configuration change is made, the minor alarm could be triggered if we didn't restart relative FPC/PIC.

The article tells how to check the alarms and clear the alarm to make the changed port speed take into effect. 

When port speed changes, there might generate alarm if we didn't restart relative FPC/PIC.

Port speed changing example: 

Before port speed changes: 

#set chassis fpc 1 pic 0 port 0 speed 1g

After port speed changes: 

#set chassis fpc 1 pic 0 port 0 speed 10g

Alarms might be generated: 

root@R1> show chassis alarms no-forwarding

1 alarms currently active
Alarm time               Class  Description
2024-06-20 15:41:43 PDT  Minor FPC 1 PIC 0 Need bounce

Or

root@R1> show chassis alarms no-forwarding

1 alarms currently active
Alarm time               Class  Description
2024-06-20 15:41:43 PDT  Minor  FPC 1 Need bounce

Usually, reboot the PIC or FPC is required after you change an existing port speed configuration to a new one in order to make the new speed take into effect. you can run the command "  show chassis alarms"  as mentioned above to check which component needs to be restarted. 

root@R1> show chassis alarms no-forwarding

1 alarms currently active
Alarm time               Class  Description
2024-06-20 15:41:43 PDT  Minor FPC 1 PIC 0 Need bounce

Or

root@R1> show chassis alarms no-forwarding

1 alarms currently active
Alarm time               Class  Description
2024-06-20 15:41:43 PDT  Minor  FPC 1 Need bounce

Restart relative component: 

1)If the Minor alarm is for PIC (example : Minor FPC 1 PIC 0 Need bounce):

>request chassis pic fpc-slot 1 pic-slot 0 offline
<wait for 2 minutes>
>request chassis pic fpc-slot 1 pic-slot 0 online

2)If the Minor alarm is for FPC (example: Minor FPC 1 Need bounce):

>request chassis fpc offline slot 1
<wait for 2 minutes>
>request chassis fpc online slot 1

OR

>request chassis fpc restart slot 1

2024/11/12 created