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

HP StorageWorks 2/140 FW 08.01.00 McDATA Products in a SAN Environment Plannin - Page 239

Inband Management Access, System/390 SA OS/390 for native FICON, Version 1.3 or later

View all HP StorageWorks 2/140 manuals

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

Page 239 highlights

Physical Planning Considerations 5 Inband Management Access OSMS FMS Inband management console access (through a Fibre Channel port) is provided by enabling user-specified features that allow OSMS or FICON (FMS) host control of a director or fabric switch. The features can be simultaneously installed and enabled. When the OSMS feature key is enabled at the Element Manager application, host control and management of the director or switch is provided through an open-systems interconnection (OSI) device attached to a product port. When implementing inband product management through an OSI connection, plan for the following minimum host requirements: • Connectivity to an OSI server with a product-compatible host bus adapter (HBA) that communicates through the Fibre Channel common transport (FC-CT) protocol. • Installation of a storage network management application on the OSI server. Management applications include Veritas® SANPoint™ Control (Version 1.0 or later), or Tivoli® NetView® (Version 6.0 or later). For information about product-compatible HBAs, third-party SAN management applications, and minimum OSI server specifications, refer to the McDATA website at www.mcdata.com. When the FMS feature key is enabled at the Element Manager application, host control and management of the director or switch is provided through a server attached to a product port. The server communicates with the product through a FICON channel. When implementing inband product management through a FICON channel, plan for the following minimum host requirements: • Connectivity to an IBM S/390 Parallel Enterprise Server (Generation 5 or Generation 6), with one or more FICON channel adapter cards installed, using System Automation for Operating System/390 (SA OS/390) for native FICON, Version 1.3 or later, plus service listed in the appropriate preventive service planning (PSP) bucket. The PSP bucket upgrade is HKYSA30. The minimum OS/390 level for a director or switch without the control unit port (CUP) feature is Version 2.6, plus service listed in PSP bucket upgrade 2032, device subset 2032OS390G5+. The minimum OS/390 level for a director or switch with the CUP feature is Version 2.1, plus service listed in the preceding PSP bucket for that function. Physical Planning Considerations 5-35

Section	Page
Cover	1
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	40
Fabric Switch Performance	41
Sphereon 3232 Fabric Switch	41
Sphereon 4300 Fabric Switch	42
Sphereon 4400 Fabric Switch	44
Sphereon 4500 Fabric Switch	45
Sphereon 4700 Fabric Switch	47
SAN Routers	48
SAN Router Performance	49
Eclipse 1620 SAN Router	50
Eclipse 2640 SAN Router	52
Product Features	54
Connectivity Features	54
Security Features	57
Serviceability Features	58
Product Management	63
Product Management	64
Out-of-Band Management	64
Inband Management	67
Management Interface Summary	68
Management Server Support	69
Management Server Specifications	70
Ethernet Hub	72
Remote User Workstations	72
Product Firmware	73
Firmware Services	74
Backup and Restore Features	75
SAN Management Applications	77
SANavigator and EFCM Applications	77
SANvergence Manager Application	80
EFCM Basic Edition Interface	82
Command Line Interface	83
Planning Considerations for Fibre Channel Topologies	85
Fibre Channel Topologies	85
Characteristics of Arbitrated Loop Operation	86
Shared Mode Versus Switched Mode	87
Public Versus Private Devices	90
Public Versus Private Loops	92
FL_Port Connectivity	94
Planning for Private Arbitrated Loop Connectivity	94
Planning for Fabric-Attached Loop Connectivity	95
Connecting FC-AL Devices to a Switched Fabric	95
Server Consolidation	96
Tape Device Consolidation	97
Fabric Topologies	98
Mesh Fabric	98
Core-to-Edge Fabric	100
SAN Islands	102
Planning for Multiswitch Fabric Support	102
Fabric Topology Limits	103
Factors to Consider When Implementing a Fabric Topology	104
General Fabric Design Considerations	113
Fabric Initialization	113
Fabric Performance	114
Fabric Availability	121
Fabric Scalability	123
Obtaining Professional Services	124
Mixed Fabric Design Considerations	124
FCP and FICON in a Single Fabric	125
Multiple Data Transmission Speeds in a Single Fabric	135
FICON Cascading	136
High-Integrity Fabrics	137
Minimum Requirements	137
FICON Cascading Best Practices	138
Implementing SAN Internetworking Solutions	143
SAN Island Consolidation	144
Flexible Partitioning Technology	146
SAN Routing	150
Implementing BC/DR Solutions	178
Extended-Distance Operational Modes	179
SAN Extension Transport Technologies	181
Distance Extension Through BB_Credit	191
Intelligent Port Speed	193
Distance Extension Best Practices	197
Consolidating and Integrating iSCSI Servers and Storage	200
iSCSI Protocol	201
iSCSI Server Consolidation	202
iSCSI Storage Consolidation	203
Physical Planning Considerations	205
Port Connectivity and Fiber-Optic Cabling	205
Port Requirements	206
SFP Optical Transceivers	208
Extended-Distance Ports	210
High-Availability Considerations	210
Fibre Channel Cables and Connectors	211
Routing Fiber-Optic Cables	212
Management Server, LAN, and Remote Access Support	213
Management Server	214
Remote User Workstations	215
SNMP Management Workstations	217
EFCM Basic Edition Interface	218
Security Provisions	219
Password Protection	219
SANtegrity Authentication	220
SANtegrity Binding	223
PDCM Arrays	224
Preferred Path	227
Zoning	229
Server and Storage-Level Access Control	233
Security Best Practices	234
Optional Feature Keys	237
Inband Management Access	239
Flexport Technology	240
SANtegrity Authentication	240
SANtegrity Binding	240
OpenTrunking	241
Full Volatility	242
Full Fabric	242
Remote Fabric	243
N_Port ID Virtualization	243
Element Manager Application	243
Configuration Planning Tasks	245
Task 1: Prepare a Site Plan	246
Task 2: Plan Fibre Channel Cable Routing	247
Task 3: Consider Interoperability with Fabric Elements and End Devices	248
Task 4: Plan Console Management Support	249
Task 5: Plan Ethernet Access	251
Task 6: Plan Network Addresses	251
Task 7: Plan SNMP Support (Optional)	254
Task 8: Plan E-Mail Notification (Optional)	255
Task 9: Establish Product and Server Security Measures	255
Task 10: Plan Phone Connections	256
Task 11: Diagram the Planned Configuration	256
Task 12: Assign Port Names and Nicknames	257
Rules for Port Names	257
Rules for Nicknames	258
Task 13: Complete the Planning Worksheet	258
Task 14: Plan AC Power	272
Task 15: Plan a Multiswitch Fabric (Optional)	273
Task 16: Plan Zone Sets for Multiple Products (Optional)	274
Task 17: Plan SAN Routing (Optional)	275
Task 18: Complete Planning Checklists	278
Product Specifications	283
Director, Fabric Switch, and SAN Router Specifications	283
Dimensions	283
Power Requirements	285
Heat Dissipation	287
Clearances	287
Acoustical Noise and Physical Tolerances	288
Storage and Shipping Environment	288
Operating Environment	289
FC-512 Fabricenter Cabinet Specifications	289
Dimensions	290
Power Requirements	290
Clearances	290
Cabinet Footprint	290
Firmware Summary	293
System-Related Differences	293
Fibre Channel Protocol-Related Differences	295
Management-Related Differences	297
Index	305
A	305
B	305
C	306
D	307
E	308
F	309
G	310
H	310
I	311
J	311
L	312
M	312
N	313
O	313
P	313
R	315
S	315
T	317
V	318
W	318

Match case Limit results 1 per page

Physical Planning Considerations

5-35

Physical Planning Considerations

Inband

Management

Access

Inband management console access (through a Fibre Channel port) is

provided by enabling user-specified features that allow OSMS or

FICON (FMS) host control of a director or fabric switch. The features

can be simultaneously installed and enabled.

OSMS

When the OSMS feature key is enabled at the Element Manager

application, host control and management of the director or switch is

provided through an open-systems interconnection (OSI) device

attached to a product port. When implementing inband product

management through an OSI connection, plan for the following

minimum host requirements:

•

Connectivity to an OSI server with a product-compatible host bus

adapter (HBA) that communicates through the Fibre Channel

common transport (FC-CT) protocol.

•

Installation of a storage network management application on the

OSI server. Management applications include Veritas

SANPoint™ Control (Version 1.0 or later), or Tivoli

NetView

(Version 6.0 or later).

For information about product-compatible HBAs, third-party SAN

management applications, and minimum OSI server specifications,

refer to the McDATA website at

www.mcdata.com

FMS

When the FMS feature key is enabled at the Element Manager

application, host control and management of the director or switch is

provided through a server attached to a product port. The server

communicates with the product through a FICON channel. When

implementing inband product management through a FICON

channel, plan for the following minimum host requirements:

•

Connectivity to an IBM S/390 Parallel Enterprise Server

(Generation 5 or Generation 6), with one or more FICON channel

adapter cards installed, using System Automation for Operating

System/390 (SA OS/390) for native FICON, Version 1.3 or later,

plus service listed in the appropriate preventive service planning

(PSP) bucket. The PSP bucket upgrade is HKYSA30.

The minimum OS/390 level for a director or switch without the

control unit port (CUP) feature is Version 2.6, plus service listed in

PSP bucket upgrade 2032, device subset 2032OS390G5+. The

minimum OS/390 level for a director or switch with the CUP

feature is Version 2.1, plus service listed in the preceding PSP

bucket for that function.