This article explains why IQ2 and IQ2E physical interface cards (PICs) reboot when the traffic manager mode is changed. The PIC is changing from default value of ingress-and-egress to egress-only . This reboot is expected behavior. Non-IQ PICs do not support ingress scheduling, so they will not reboot.
ingress-and-egress
egress-only
IQ2 and IQ2E PICs will reboot when traffic manager mode is changed under the following hierarchy.
{MASTER.EN_US}[edit] lab#set chassis fpc 1 pic 2 traffic-manager mode egress-only {MASTER.EN_US}[edit] lab# commit re0: configuration check succeeds re1: commit complete re0: commit complete
The following log messages will be seen:
%DAEMON-4-CHASSISD_CONFIG_WARNING: pic_should_bounce: Traffic manager mode is not valid for this PIC, FPC 0 PIC 0 %DAEMON-4-CHASSISD_CONFIG_WARNING: pic_should_bounce: Traffic manager mode is not valid for this PIC, FPC 0 PIC 1 %DAEMON-4-CHASSISD_CONFIG_WARNING: pic_should_bounce: Traffic manager mode is not valid for this PIC, FPC 0 PIC 2 %DAEMON-4-CHASSISD_CONFIG_WARNING: pic_should_bounce: Traffic manager mode is not valid for this PIC, FPC 0 PIC
NON-IQ2 PIC will not reboot.
A traffic-manager mode change from the default value of ingress-and-egress to egress-only will cause the PIC to reboot. Non-IQ PICs do not support ingress scheduling so they will not reboot.
A traffic-manager mode change will cause the PIC to bounce. It is changing from default value of ingress-and-egress to egress-only. This is expected behavior.
Non-IQ PICs do not support ingress scheduling so they will not reboot.