Identifying Unsuitable Scenarios for Interface PBR Deployment

Policy-Based Routing (PBR) is designed to override standard routing table decisions based on criteria such as source IP, protocol, or packet length. It operates by matching traffic against an access control list (ACL) and applying a policy action, typically changing the next-hop IP address.

Option A describes forwarding traffic to an off-path device like an Access Controller (AC). This is a primary use case for PBR, where traffic is steered to a specific appliance not in the normal forwarding path without requiring complex static routes for every subnet. Similarly, Option B involves steering traffic to an off-path security detection device; this is also a classic scenario where PBR ensures inspection traffic is captured correctly.

Option D addresses multi-ISP environments. Using PBR to direct traffic from different internal subnets to specific ISP uplinks based on source address is the standard method for load balancing or policy enforcement across multiple outbound links. Community comments confirm that multi-ISP policy routing is a common application of this feature.

Option C suggests using PBR to modify the next-hop for locally originated traffic (traffic generated by the device itself, such as ping or SSH sessions initiated by the router). In most enterprise networking architectures, including Huawei's VRP platform, PBR policies are applied only to transit traffic (packets passing through the device). Locally originated traffic follows the standard routing table or uses specific commands like 'ip route-static' with a preference value, or 'peer-route' features, but it does not traverse the PBR engine. Therefore, deploying interface PBR for locally generated packets is technically unsupported or ineffective.