Deployment Guide

FIP Snooping Example
The following gure shows an Aggregator used as a FIP snooping bridge for FCoE trac between an ENode (server blade) and an FCF
(ToR switch). The ToR switch operates as an FCF and FCoE gateway.
Figure 44. FIP Snooping on an Aggregator
In tbe above gure, DCBX and PFC are enabled on the Aggregator (FIP snooping bridge) and on the FCF ToR switch. On the FIP snooping
bridge, DCBX is congured as follows:
A server-facing port is congured for DCBX in an auto-downstream role.
An FCF-facing port is congured for DCBX in an auto-upstream or conguration-source role.
The DCBX conguration on the FCF-facing port is detected by the server-facing port and the DCB PFC conguration on both ports is
synchronized. For more information about how to congure 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 specied event type, where:
all enables all debugging options.
acl enables debugging only for ACL-specic events.
error enables debugging only for error conditions.
FIP Snooping
337