Brocade Fabric Watch Administrator's Guide v6.2.0 (53-1001188-01, April 2009)

Fabric Watch Administrator’s Guide 93
53-1001188-01
Appendix
B
Port fencing types
The following table lists and describes the set of port fencing types that are available in M-EOS and
Fabric OS v6.2.0.
Fencing Type Violation Subtype Description Firmware Class / Area FOS Support
Security Port Binding The login server detects a
Port Binding violation when
an attached device
attempts to FLOGI with a
port name WWN that does
not match the WWN in the
Port Binding configuration
for that F_Port.
Security/DCC
violations
DCC check disables the
port on failure, so no
additional port fencing is
required.
Security Switch Binding The login server detects a
Switch Binding violation
when an attached device
attempts to FLOGI with a
port name that is not
contained in the Switch
Membership list.
Security/DCC
violations
DCC check disables the
port on failure, so no
additional port fencing is
required.
Security Authentication Authentication violations
are detected by the
Authentication Services
subsystem (the Radius
feature) during an
authentication protocol
session initiated
immediately after an E_Port
or F_Port login.
Security/SLAP failures DH-CHAP / FCAP port will be
segmented/disabled on
Auth failures, so no
additional port fencing is
required.
Security N_Port connection Not
Allowed
When a device attempts to
log into a port not
configured for N_Port
support, the Login server
detects an N_Port
Connection Not Allowed
violation.
Not supported FOS has locked L_Port,
disabled E_Port, and locked
G_Port. These do not fall in
“Not configured for N_Port”
category.
Link Level (hot I/O) Link Transition Threshold
Exceeded
Repeated link transitions
between Active and Inactive
states caused by bad
cables, driver defects, and
hardware device protocol
errors.
Port/Link Loss Implemented in Fabric OS
v6.2.0.
Protocol ISL Fencing An E_Port is bouncing
because of a loss of
light/signal link bouncing.
E_Port/Link loss Implemented in Fabric OS
v6.2.0.