Fabric OS Administrator's Guide v6.4.0 (53-1001763-01, June 2010)

Fabric OS Administrator’s Guide 321
53-1001763-01
FCR SANtegrity
14
TABLE 66 VEX_Port-to-VE_Port authentication policy with correct secrets
TABLE 67 VEX_ Port-to-VE_Port authentication policy when secrets are not correct
Authentication of VEX_Port-to-VEX_Port connections
Connecting VEX_Ports to each other is not relevant for authentication, because both ports will
always operate in Passive mode. Because ports in Passive mode do not initiate authentication,
VEX_Ports cannot have an authenticated connection between them.
FCR SANtegrity
FC-FC Routing (FCR) SANtegrity is supported for Fabric Binding when EX_Ports are attached to a
McDATA edge switch. Fabric Binding lets you configure a Fabric Binding Membership list that each
switch in a fabric can use to validate between it and its neighbor. McDATA SANtegrity Fabric Binding
uses a list made up of domain ID and WWN pairs and implies the use of Insistent Domain IDs.
When Fabric Binding is enabled, a Fabric Binding check is performed each time a link is enabled to
ensure that the switches can connect. If the binding check fails, the McDATA port goes to an invalid
attachment state and the EX_Port disables itself.
NOTE
After a Fabric Binding check failure between a McDATA E_Port and an EX_Port, the current M-EOS
implementation requires you to disable the M-EOS port and then re-enable it before the link can
come up again. Enabling just the EX_Port does not always allow the link to come up again.
Fabric OS switch
VEX_Port-to-VE_Port
Passive Active On Off
Passive Yes
Connected without
any authentication
(Fabric builds
normally).
Yes!
Connected with
two-way
authentication; both
sides of the
connection perform
Authentication (Fabric
builds normally).
Yes!
Connected with
two-way
authentication; both
sides of the
connection perform
Authentication (Fabric
builds normally).
Yes
Connected without
any authentication
(Fabric builds
normally).
Fabric OS switch
VEX_Port-to-VE_Port
Passive Active On Off
Passive Yes
Connected without
any authentication
(Fabric builds
normally).
No
E_Port does not
connect
(Authentication
Rejected). When the
Fabric OS switch
generates the reject,
it disables the Fabric
OS port. When the
M-EOS switch
generates the reject,
it goes to an invalid
attachment state.
No
E_Port does not
connect
(Authentication
Rejected). When the
Fabric OS switch
generates the reject,
it disables the Fabric
OS port. When the
M-EOS switch
generates the reject,
it goes to an invalid
attachment state.
Yes
Connected
without any
authentication
(Fabric builds
normally).