3
A to NET B directly without passing through A, B, C and D. The
dashed line in Figure 1 indicates the traffic direction.
Note that:
To make sure the PFC can work normally when the device is working
abnormally, enable external securityservice bypass on the device. For
details, see the Layer 2—LAN Switching configuration guide for the
PFC.
Interfaces NET A and A have peering relationship with interfaces NET
B and B, that is, they can be deployed in the reverse sequence. For
more information, see Table 1.
Table 1 Traffic direction in the PFC
Device
status Traffic direction
The device is
operating
correctly
External network interface > NET A > A > interface added to the
external zone of the device > interface added to the internal
zone of the device > B > NET B > internal network interface
(follows the direction indicated by the solid line)
or
External network interface > NET B > B > interface added to the
external zone of the device > interface added to the internal
zone of the device > A > NET A > internal network interface (in
the reverse direction as indicated by the solid line).
A power
failure,
reboot, or
interface
down occurs
External network interface > NET A > NET B > internal network
interface (follows the direction indicated by the dashed line)
or
External network interface > NET B > NET A > internal network
interface (in the reverse direction as indicated by the dashed
line)
If the device is configured with two segments and is connected to the
PFC, the interface down event of one segment will trigger the PFC to
perform a traffic switchover. Power failure and link state changes can
cause a working mode change of the PFC.
