Home » HP Manuals » Storage Devices » HP StorageWorks 2/24 » Manual Viewer

HP StorageWorks 2/24 FW 07.00.00/HAFM SW 08.06.00 McDATA Products in a SAN Env - Page 235

Server and Storage-Level Access Control, Reasons for zone implementation

View all HP StorageWorks 2/24 manuals

Add to My Manuals
Save this manual to your list of manuals

Page 235 highlights

Physical Planning Considerations 5 Obtaining Professional Services • Reasons for zone implementation - Determine if zoning is to be implemented for the enterprise. If so, evaluate if the purpose of zoning is to differentiate between operating systems, data sets, user groups, devices, processes, or some combination thereof. Plan the use of zone members, zones, and zone sets accordingly. • Zone members specified by port number or WWN - Determine if zoning is to be implemented by port number or WWN. Because changes to port connections or fiber-optic cable configurations disrupt zone operation and may incorrectly include or exclude a device from a zone, zoning by WWN is recommended. However, if zoning is implemented by WWN, removal and replacement of a device HBA or Fibre Channel interface disrupts zone operation and will exclude a new device from a zone unless the device is added to the zone set. • Zoning implications for a multiswitch fabric - For a multiswitch fabric, zoning is configured on a fabric-wide basis, and any change to the zoning configuration is applied to all switches in the fabric. To ensure zoning is consistent across a fabric, there can be no duplicate Domain_IDs, the active zone set name must be consistent, and zones with the same name must have identical elements. Ensure these rules are enforced when planning zones and zone sets, and carefully coordinate the zoning and multiswitch fabric tasks. Planning and implementing the zoning feature is a complex and difficult task, especially for multiswitch fabrics. Obtain planning assistance from McDATA's professional services organization before implementing the director or switch zoning feature. Server and Storage-Level Access Control To enhance the access barriers and network security provided by zoning through the director or fabric switch, security measures for SANs can also be implemented at servers and storage devices. Server-level access control is called persistent binding. Persistent binding uses configuration information stored on the server and is implemented through the server's HBA driver. The process binds a server device name to a specific Fibre Channel storage volume or logical unit number (LUN), through a specific HBA and storage port WWN. For persistent binding: Physical Planning Considerations 5-29

Section	Page
Contents	3
Preface	13
Introduction to McDATA Multi-Protocol Products	27
Product Overview	28
Multi-Protocol Hardware	28
SAN Management Applications	31
Directors	32
Director Performance	33
Intrepid 6064 Director	34
Intrepid 6140 Director	36
Intrepid 10000 Director	38
Fabric Switches	41
Fabric Switch Performance	41
Sphereon 3232 Fabric Switch	42
Sphereon 4300 Fabric Switch	43
Sphereon 4500 Fabric Switch	44
SAN Routers	46
SAN Router Performance	47
Eclipse 1620 SAN Router	48
Eclipse 2640 SAN Router	50
Product Features	51
Connectivity Features	52
Security Features	54
Serviceability Features	55
Product Management	61
Product Management	62
Out-of-Band Management	62
Inband Management	65
Management Interface Summary	66
Management Server Support	67
Management Server Specifications	68
Ethernet Hub	70
Remote User Workstations	70
Product Firmware	71
Firmware Services	72
Backup and Restore Features	73
SAN Management Applications	75
SANavigator and EFCM Applications	75
SANvergence Manager Application	81
SANpilot Interface	84
Command Line Interface	86
Planning Considerations for Fibre Channel Topologies	87
Fibre Channel Topologies	87
Characteristics of Arbitrated Loop Operation	88
Shared Mode Versus Switched Mode	89
Public Versus Private Devices	92
Public Versus Private Loops	94
FL_Port Connectivity	96
Planning for Private Arbitrated Loop Connectivity	96
Planning for Fabric-Attached Loop Connectivity	97
Connecting FC-AL Devices to a Switched Fabric	97
Server Consolidation	98
Tape Device Consolidation	99
Fabric Topologies	100
Mesh Fabric	100
Core-to-Edge Fabric	102
SAN Islands	104
Planning for Multiswitch Fabric Support	104
Fabric Topology Limits	105
Factors to Consider When Implementing a Fabric Topology	106
General Fabric Design Considerations	115
Fabric Initialization	116
Fabric Performance	117
Fabric Availability	123
Fabric Scalability	125
Obtaining Professional Services	126
Mixed Fabric Design Considerations	126
FCP and FICON in a Single Fabric	127
Multiple Data Transmission Speeds in a Single Fabric	137
FICON Cascading	138
High-Integrity Fabrics	139
Minimum Requirements	140
FICON Cascading Best Practices	141
Implementing SAN Internetworking Solutions	145
SAN Island Consolidation	146
Flexible Partitioning Technology	148
SAN Routing	152
Implementing BC/DR Solutions	180
Extended-Distance Operational Modes	181
SAN Extension Transport Technologies	183
Distance Extension Through BB_Credit	193
Intelligent Port Speed	195
Distance Extension Best Practices	199
Consolidating and Integrating iSCSI Servers and Storage	202
iSCSI Protocol	203
iSCSI Server Consolidation	204
iSCSI Storage Consolidation	205
Physical Planning Considerations	207
Port Connectivity and Fiber-Optic Cabling	207
Port Requirements	208
SFP Optical Transceivers	209
Extended-Distance Ports	212
High-Availability Considerations	212
Fibre Channel Cables and Connectors	212
Routing Fiber-Optic Cables	214
Management Server, LAN, and Remote Access Support	215
Management Server	215
Remote User Workstations	217
SNMP Management Workstations	219
SANpilot Interface	220
Security Provisions	221
Password Protection	221
SANtegrity Authentication	222
SANtegrity Binding	225
PDCM Arrays	226
Preferred Path	229
Zoning	231
Server and Storage-Level Access Control	235
Security Best Practices	236
Optional Feature Keys	239
Inband Management Access	241
Flexport Technology	242
SANtegrity Authentication	243
SANtegrity Binding	243
OpenTrunking	243
Full Volatility	244
Full Fabric	245
Remote Fabric	245
CNT WAN Support	246
Element Manager Application	246
Configuration Planning Tasks	249
Task 1: Prepare a Site Plan	250
Task 2: Plan Fibre Channel Cable Routing	251
Task 3: Consider Interoperability with Fabric Elements and End Devices	252
Task 4: Plan Console Management Support	253
Task 5: Plan Ethernet Access	254
Task 6: Plan Network Addresses	255
Task 7: Plan SNMP Support (Optional)	258
Task 8: Plan E-Mail Notification (Optional)	259
Task 9: Establish Product and Server Security Measures	259
Task 10: Plan Phone Connections	260
Task 11: Diagram the Planned Configuration	261
Task 12: Assign Port Names and Nicknames	261
Task 13: Complete the Planning Worksheet	262
Task 14: Plan AC Power	276
Task 15: Plan a Multiswitch Fabric (Optional)	277
Task 16: Plan Zone Sets for Multiple Products (Optional)	278
Task 17: Plan SAN Routing (Optional)	279
Task 18: Complete Planning Checklists	282
Product Specifications	287
Director, Fabric Switch, and SAN Router Specifications	287
Dimensions	287
Power Requirements	289
Heat Dissipation	290
Clearances	290
Acoustical Noise and Physical Tolerances	292
Storage and Shipping Environment	292
Operating Environment	293
FC-512 Fabricenter Cabinet Specifications	293
Dimensions	293
Power Requirements	294
Clearances	294
Cabinet Footprint	294
Firmware Summary	297
System-Related Differences	297
Fibre Channel Protocol-Related Differences	299
Management-Related Differences	301

Match case Limit results 1 per page

Physical Planning Considerations

5-29

Physical Planning Considerations

•

Reasons for zone implementation -

Determine if zoning is to be

implemented for the enterprise. If so, evaluate if the purpose of

zoning is to differentiate between operating systems, data sets,

user groups, devices, processes, or some combination thereof.

Plan the use of zone members, zones, and zone sets accordingly.

•

Zone members specified by port number or WWN -

Determine

if zoning is to be implemented by port number or WWN. Because

changes to port connections or fiber-optic cable configurations

disrupt zone operation and may incorrectly include or exclude a

device from a zone, zoning by WWN is recommended. However,

if zoning is implemented by WWN, removal and replacement of a

device HBA or Fibre Channel interface disrupts zone operation

and will exclude a new device from a zone unless the device is

added to the zone set.

•

Zoning implications for a multiswitch fabric -

For a multiswitch

fabric, zoning is configured on a fabric-wide basis, and any

change to the zoning configuration is applied to all switches in

the fabric. To ensure zoning is consistent across a fabric, there can

be no duplicate Domain_IDs, the active zone set name must be

consistent, and zones with the same name must have identical

elements. Ensure these rules are enforced when planning zones

and zone sets, and carefully coordinate the zoning and

multiswitch fabric tasks.

Obtaining Professional

Services

Planning and implementing the zoning feature is a complex and

difficult task, especially for multiswitch fabrics. Obtain planning

assistance from McDATA’s professional services organization before

implementing the director or switch zoning feature.

Server and

Storage-Level

Access Control

To enhance the access barriers and network security provided by

zoning through the director or fabric switch, security measures for

SANs can also be implemented at servers and storage devices.

Server-level access control is called persistent binding. Persistent

binding uses configuration information stored on the server and is

implemented through the server’s HBA driver. The process binds a

server device name to a specific Fibre Channel storage volume or

logical unit number (LUN), through a specific HBA and storage port

WWN. For persistent binding: