This article describes the issue where the packets are not forwarded to the analyzer when input parameters - rate or maximum-packet-length - are configured.
No packets are seen in the captures when the analyzer is configured as below:
forwarding-options { analyzer { TEST { input { rate 10; maximum-packet-length 9000; ingress { interface ge-5/3/9; } egress { interface ge-5/3/9; } } output { interface ge-5/3/8; } } } }
}
Even using the default parameters in the analyzer configuration, we do not get any captures.
Configuring the analyzer without input parameters defined is referred to as the Default Analyzer, which will be applied at the global level. In the default analyzer level, there is no need to bind the analyzer to the physical ports.
When the analyzer is configured with input parameters defined, it referred to as a Statistical Analyzer. In the statistical analyzer level, you need to bind the analyzer to the physical ports at chassis level; for example:
set chassis fpc <fpc_name> port-mirror-instance <analyzer_name>
In our example, since we are monitoring the ge-5/3/9 interface located in FPC 5, the following command needs to be committed to bind the statistical analyzer to the FPC that contains the input interface.
set chassis fpc 5 port-mirror-instance TEST