White Papers

Table Of Contents
FIP Snooping Example
The following figure shows an Aggregator used as a FIP snooping bridge for FCoE traffic between an ENode (server blade) and
an FCF (ToR switch). The ToR switch operates as an FCF and FCoE gateway.
Figure 45. FIP Snooping on an Aggregator
In tbe above figure, DCBX and PFC are enabled on the Aggregator (FIP snooping bridge) and on the FCF ToR switch. On the
FIP snooping bridge, DCBX is configured as follows:
A server-facing port is configured for DCBX in an auto-downstream role.
An FCF-facing port is configured for DCBX in an auto-upstream or configuration-source role.
The DCBX configuration on the FCF-facing port is detected by the server-facing port and the DCB PFC configuration on both
ports is synchronized. For more information about how to configure DCBX and PFC on a port, refer to FIP Snooping
After FIP packets are exchanged between the ENode and the switch, a FIP snooping session is established. ACLS are
dynamically generated for FIP snooping on the FIP snooping bridge/switch.
Debugging FIP Snooping
To enable debug messages for FIP snooping events, enter the debug fip-snooping command..
1. Enable FIP snooping debugging on for all or a specified event type, where:
all enables all debugging options.
acl enables debugging only for ACL-specific events.
error enables debugging only for error conditions.
ifm enables debugging only for IFM events.
info enables debugging only for information events.
ipc enables debugging only for IPC events.
rx enables debugging only for incoming packet traffic.
EXEC PRIVILEGE mode
320
FIP Snooping