The following alarm is seen when the make port speed changes:
user@router> show chassis alarms 2 alarms currently active Alarm time Class Description 2021-03-29 16:20:32 PDT Minor FPC 2 Need bounce 2021-03-29 16:20:32 PDT Minor FPC 3 Need bounce
The issue is confirmed when checking the message logs in chassisd:
Mar 29 16:20:32 tvp_pic_process_tpic_port_map FPC 3 PIC 0 Port speed configuration, requires FPC reboot, raising Alarm Mar 29 16:20:32 ch_tvp_ng_send_alarm_request: fru_type=3, slot=0, reason=62 Mar 29 16:20:32 send: yellow alarm set, device FPC 3, reason FPC 3 Need bounce Mar 29 16:20:32 tvp_pic_process_tpic_port_map FPC 2 PIC 0 Port speed configuration, requires FPC reboot, raising Alarm Mar 29 16:20:32 ch_tvp_ng_send_alarm_request: fru_type=3, slot=0, reason=62 Mar 29 16:20:32 send: yellow alarm set, device FPC 2, reason FPC 2 Need bounce
Mar 29 16:20:32 labbox mgd[86080]: UI_CMDLINE_READ_LINE: User 'test', command 'set chassis fpc 2 pic 0 port 20 speed 10g ' Mar 29 16:20:32 labbox mgd[86080]: UI_CMDLINE_READ_LINE: User 'test', command 'set chassis fpc 2 pic 0 port 21 speed 10g ' Mar 29 16:20:32 labbox mgd[86080]: UI_CMDLINE_READ_LINE: User 'test', command 'set chassis fpc 2 pic 0 port 22 speed 10g ' Mar 29 16:20:32 labbox mgd[86080]: UI_CMDLINE_READ_LINE: User 'test', command 'set chassis fpc 2 pic 0 port 23 speed 10g ' Mar 29 16:20:32 labbox mgd[86080]: UI_CMDLINE_READ_LINE: User 'test', command 'set chassis fpc 2 pic 0 port 24 speed 10g '
Originally, this change will automatically reboot the FPC. However, the behavior has been changed so users can manually schedule a reboot later to the corresponding FPCs without affecting productivity. Change in port speed will only take effect after restarting the FPC.
Restart the FPC during a maintenance window to avoid traffic impact and to make the port speed change effective.
Example for bouncing (restarting) an FPC:
request chassis fpc restart slot 0
2021-05-03: Added example for restarting (bouncing) and FPC.