Description

Why does cosd generate "Input queuing may not be supported on underlying AE IFD ge-0/2/9" when input queuing is not configured on AE interface?

Symptoms

Whenever an addition or modification of the class of service configuration involving the AE interface is done, the following messages are printed.

Aug 11 11:53:15 puck-re0 cosd[1625]: Input queuing may not be supported on underlying AE IFD ge-0/0/4
Aug 11 11:53:15 puck-re0 cosd[1625]: Input queuing may not be supported on underlying AE IFD ge-0/0/5

The logs are printed despite there is no input queuing configured on the AE interface or its member links.

Solution

Log messages are printed due to issues in the routine that checks whether input queuing is supported on a particular interface.  Currently that check is getting invoked irrespective of whether input queuing is configured or not on a particular interface. These log messages are harmless and can be safely ignored.

PR466745 was raised to address to this issue. Fix of this PR avoids the unnecessary log generation. The issue is also seen on all other bundle interfaces such as aggregated sonnet, link bundles, etc.