Users Guide
CAM ACL Table
update it with below.
show cam-acl
-- Chassis Cam ACL --
Current Settings(in block sizes)
1 block = 256 entries
L2Acl : 2
Ipv4Acl : 0
Ipv6Acl : 0
Ipv4Qos : 2
L2Qos : 0
L2PT : 0
IpMacAcl : 0
VmanQos : 0
EtsAcl : 1
FcoeAcl : 2
iscsiOptAcl : 2
ipv4pbr : 0
vrfv4Acl : 0
Openflow : 0
fedgovacl : 0
nlbclusteracl: 0
-- stack-unit 1 --
Current Settings(in block sizes)
1 block = 256 entries
L2Acl : 2
Ipv4Acl : 0
Ipv6Acl : 0
Ipv4Qos : 2
L2Qos : 0
L2PT : 0
IpMacAcl : 0
VmanQos : 0
EtsAcl : 1
FcoeAcl : 2
iscsiOptAcl : 2
ipv4pbr : 0
vrfv4Acl : 0
Openflow : 0
fedgovacl : 0
nlbclusteracl: 0
Dell(conf)#
Enabling the FCoE Transit Feature
The following sections describe how to enable FCoE transit.
NOTE
: FCoE transit is disabled by default. To enable this feature, you must follow the Congure FIP
Snooping.
As soon as you enable the FCoE transit feature on a switch-bridge, existing VLAN-specic and FIP snooping congurations are applied.
The FCoE database is populated when the switch connects to a converged network adapter (CNA) or FCF port and compatible DCB
congurations are synchronized. By default, all FCoE and FIP frames are dropped unless specically permitted by existing FIP snooping-
generated ACLs. You can recongure any of the FIP snooping settings.
If you disable FCoE transit, FIP and FCoE trac are handled as normal Ethernet frames and no FIP snooping ACLs are generated. The
VLAN-specic and FIP snooping conguration is disabled and stored until you re-enable FCoE transit and the congurations are re-applied.
288
FIP Snooping










