A device uses the static CR-LSP's source interface check function to check whether the inbound interface of labeled packets is the same as that of a configured static CR-LSP. If the inbound interfaces match, the device forwards the packets. If the inbound interfaces do not match, the device discards the packets.
A static CR-LSP is established using manually configured forwarding and resource information. Signaling protocols and path calculation are not used during the setup of CR-LSPs. Setting up a static CR-LSP consumes few resources because the two ends of the CR-LSP do not need to exchange MPLS control packets. The static CR-LSP cannot be adjusted dynamically in a changeable network topology. A static CR-LSP configuration error may cause protocol packets of different NEs and statuses interfere one another, which adversely affects services. To address the preceding problem, a device can be enabled to check source interfaces of static CR-LSPs. With this function configured, the device can only forward packets if both labels and inbound interfaces are correct.