---------------------------
Free [hw-grps: 3 out of 3]
No dynamic tcam usage
The output indicates that the fw-l2-in application is running out of TCAM resources
and moves into a FAILED state. Although there are two TCAM slices available at the
ingress stage, the fw-l2-in application is not able to use the available TCAM space
due to its mode (DOUBLE), resulting in resource shortage failure.
3. Fixing the applications that have failed due to the shortage of TCAM resouces.
The fw-l2-in application failed because of adding more number of services on the
routers, which resulted in shortage of TCAM resources. Although other applications
seems to work fine, it is recommended to deactivate or remove the newly added
services so that the fw-l2-in application moves to an OK state. After removing or
deactivating the newly added services, you need to run the show pfe tcam usage and
show pfe tcam error commands to verify that there are no more applications in failed
state.
To view the TCAM resource usage for all stages (egress, ingress, and pre-ingress), use
the show pfe tcam usage all-tcam-stages detail command.
user@host> show pfe tcam usage all-tcam-stages detail
Slot 0
Tcam Resource Stage: Pre-Ingress
--------------------------------
Free [hw-grps: 3 out of 3]
No dynamic tcam usage
Tcam Resource Stage: Ingress
----------------------------
Free [hw-grps: 2 out of 8]
Group: 11, Mode: SINGLE, Hw grps used: 3, Tcam apps: 2
Used Allocated Available Errors
Tcam-Entries 800 1024 224 0
Counters 800 1024 224 0
Policers 0 1024 1024 0
App tcam usage:
----------------
App-Name Entries Counters Policers Precedence State
Related-App-Name ..
-----------------------------------------------------------------
cfm-filter 500 500 0 3 OK
cfm-bd-filter 300 300 0 2 OK
Group: 8, Mode: DOUBLE, Hw grps used: 2, Tcam apps: 1
Used Allocated Available Errors
Tcam-Entries 500 512 12 18
Counters 500 1024 524 0
Policers 0 1024 1024 0
App tcam usage:
----------------
App-Name Entries Counters Policers Precedence State
Related-App-Name ..
1165Copyright © 2017, Juniper Networks, Inc.
Chapter 34: Configuring Operations, Administration, and Management (OAM)