HP StorageWorks 1606 Brocade Fabric Watch Administrator's Guide v6.3.0 (53-100 - Page 135

Port fencing types

Get HP StorageWorks 1606 - Extension SAN Switch PDF manuals and user guides View all HP StorageWorks 1606 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 135 highlights

Port fencing types Appendix D The following table lists and describes the set of port fencing types that are available in M-EOS and Fabric OS v6.3.0. Fencing Type Security Violation Subtype Port Binding Security Switch Binding Security Authentication Security N_Port connection Not Allowed Link Level (hot I/O) Link Transition Threshold Exceeded Protocol ISL Fencing Description Firmware Class / Area FOS Support 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. 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. 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. 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. 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.3.0. An E_Port is bouncing because of a loss of light/signal link bouncing. E_Port/Link loss Implemented in Fabric OS v6.3.0. Fabric Watch Administrator's Guide 111 53-1001342-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
Fabric Watch Administrator’s Guide
111
53-1001342-01
Appendix
D
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.3.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.3.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.3.0.