>
    Strata Copilot
    inspect performance-policy error-correction status
    Focus
    Download PDF
    Focus
    1. Home
    2. Prisma SD-WAN
    3. Use CLI Commands
    4. Inspect Commands
    5. inspect performance-policy error-correction status
    Download PDF
    Prisma SD-WAN

    inspect performance-policy error-correction status

    Table of Contents

    inspect performance-policy error-correction status

    Use the inspect performance-policy error-correction status command to display the Forward Error Correction (FEC) state for each path of each VPN link.
    Use the inspect performance-policy fec status command to determine whether FEC is active on a given path or application and to understand the current packet loss conditions driving FEC behavior. FEC proactively reconstructs lost packets by sending parity data alongside the original stream. The output shows whether the path supports FEC, whether the performance policy action has triggered FEC, the observed uplink and downlink packet loss rates, and the parity ratios currently in use. Use this information to confirm that FEC is engaging when expected or to investigate why it is not.

    Command

    inspect performance-policy fec status ( path-id= path_ID | application= application_ID )

    Options

    path-idEnter a path ID to display the FEC status for that specific path.
    applicationEnter an application ID to display the FEC status for that application.

    When to Use

    • When a circuit has packet loss, to determine whether FEC is engaged before escalating to a circuit-level investigation.
    • After configuring a performance policy FEC action, to confirm the path-application combination falls within the rule's scope and the parity ratios are as expected.
    • When FEC overhead appears higher than expected in one direction, to compare uplink and downlink parity ratios.

    Command Notes

    RoleSuper, Read Only
    Related Commands
    inspect performance-policy lookup
    Introduced inRelease 6.3.1

    Example

    The following example displays FEC status for a specific path and application:
    inspect performance-policy fec status path-id=1695428550797008817 application=1696037546669005617
Path-ID             : 1695428550797008817
Path Type           : private vpn
DC Site Info        :
    Site ID         : 16325224801600128
    Site Name       : San Francisco
Uplink Packet Loss  : 0.666667
Downlink Packet Loss: 2.000000
Fec Supported       : True
Fec Action Match    : True
Fec Applied         : True
Fec Parity Upstream : 20:2 (10%)
Fec Parity Downstream: 20:2 (10%)

    Output Fields

    • Path-ID: The numeric identifier of the path being inspected.
    • Path Type: The type of the path, such as private VPN or public WAN.
    • DC Site Info: The data center site ID and name that the path terminates at.
    • Uplink Packet Loss: The observed packet loss percentage in the uplink direction.
    • Downlink Packet Loss: The observed packet loss percentage in the downlink direction.
    • Fec Supported: Whether the path hardware supports FEC.
    • Fec Action Match: Whether the performance policy action has matched and specified FEC for this path.
    • Fec Applied: Whether FEC is currently active on this path.
    • Fec Parity Upstream: The upstream FEC parity ratio in use, expressed as data packets to parity packets and the overhead percentage.
    • Fec Parity Downstream: The downstream FEC parity ratio in use, expressed as data packets to parity packets and the overhead percentage.

    Troubleshooting

    ConditionPossible CauseAction
    Fec Supported is True but Fec Applied is FalsePacket loss has not crossed the threshold that triggers the FEC action in the performance policy ruleCheck the performance policy rule thresholds with inspect performance-policy lookup; verify that loss measurements on the path are reaching the configured raise threshold
    Fec Action Match is FalseNo performance policy rule has matched this path-application combination with a FEC actionReview performance policy configuration in the controller; confirm the path ID and application are within scope of a rule that specifies a FEC action
    Fec Parity ratio is unexpectedly high (for example, 1:1 overhead)Sustained high packet loss is driving maximum FEC parity overheadInvestigate the root cause of packet loss on the circuit; FEC compensates for loss but does not address the underlying link quality issue

    © 2026 Palo Alto Networks, Inc. All rights reserved.