9032 005 Presentation

IBM ESCON Director 9032-5 Presentation
Ken Trowell, Helen Howard

International Technical Support Organization
SG24-2005-00
http://www.redbooks.ibm.com
International Technical Support Organization
SG24-2005-00
September 1999
Copyright International Business Machines Corporation 1999. All rights reserved.
Note to U.S Government Users - Documentation related to restricted rights - Use, duplication or disclosure is subject to restrictions
set forth in GSA ADP Schedule Contract with IBM Corp.
First Edition (September 1999)
This edition applies to the 9032 Model 5 at a LIC level of 5.1 or higher to support the FICON Bridge adapter.
Comments may be addressed to:
IBM Corporation, International Technical Support Organization
Dept. HYJ Mail Station P099
522 South Road
Poughkeepsie, NY 12601-5400
When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way
it believes appropriate without incurring any obligation to you.
Before using this information and the product it supports, be sure to read the general information in Appendix A,
Special Notices on page 109.
Take Note!
Copyright IBM Corp. 1999 iii
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
The Team That Wrote This Redbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Comments Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Chapter 1. 9032-5 ESCON Director Introduction . . . . . . . . . . . . . . . . . . . . . .1
1.1 9032-5 Functions and Features (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
1.2 9032-5 Functions and Features (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
1.3 Comparison of 9032-3, 9033-4 and 9032-5 . . . . . . . . . . . . . . . . . . . . . . . . .4
1.4 9032-5 Feature Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
1.5 Spare Ports Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
1.6 Hardware Component Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
1.7 Hardware Components (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
1.8 Hardware Components (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
1.9 Port Card Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
1.10 FICON Bridge Card Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
1.11 Logical Partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
1.12 Logical Partitioning Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
1.13 Concurrent Maintenance Capability. . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Chapter 2. Installation Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
2.1 Environmental Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
2.2 Console Support Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
2.3 Fiber Cabling Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
2.4 Fiber Optic Transport Services (FTS) Direct Attach. . . . . . . . . . . . . . . . . .22
2.5 Trunking Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
2.6 FTS Direct Attach Trunking Options (1). . . . . . . . . . . . . . . . . . . . . . . . . . .24
2.9 Supported Software Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
2.10 Software Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
2.11 ESCON Manager - System Automation for OS/390 . . . . . . . . . . . . . . . . .30
2.12 9032-5 Port Definition - HCD Support . . . . . . . . . . . . . . . . . . . . . . . . . . .31
2.13 9032-5 I/O Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
2.14 HCD I/O Definition - 9032-5 Control Unit and Device . . . . . . . . . . . . . . .33
2.15 Operating System 9032-5 Device Definition . . . . . . . . . . . . . . . . . . . . . .34
2.16 ESCON Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
2.17 ESCON and FICON I/O Definition Guidelines . . . . . . . . . . . . . . . . . . . . .36
Chapter 3. 9032-5 Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
3.1 Console Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
3.2 Minimum Console Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
3.3 Console Platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
3.4 Console Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
3.5 Some Supported Console Configurations . . . . . . . . . . . . . . . . . . . . . . . . .42
3.6 More Supported Console Configurations. . . . . . . . . . . . . . . . . . . . . . . . . .43
3.7 Console Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
3.8 Recommended Console Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Chapter 4. ESCON Matrix and Connectivity Management . . . . . . . . . . . . .47
4.1 Matrix and Connectivity Management . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
4.2 ESCON Director Console Application as Matrix Manager . . . . . . . . . . . . .50
iv IBM ESCON Director 9032-5 Presentation
4.3 ESCON Director Console Application - Save Matrix. . . . . . . . . . . . . . . . . 51
4.4 ESCON Manager as Matrix manager (1) . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.5 ESCON Manager as Matrix Manager (2) . . . . . . . . . . . . . . . . . . . . . . . . . 53
4.6 ESCON Manager ISPF Port Matrix Display . . . . . . . . . . . . . . . . . . . . . . . 54
4.7 ESCON Manager Workstation Port Matrix Display . . . . . . . . . . . . . . . . . . 55
4.8 HCD as Matrix Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
4.9 HCD Matrix Manager Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
4.10 HCD Port Matrix Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
4.11 Matrix Management Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . 59
Chapter 5. ESCON Director Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 61
5.1 ESCON Director Console Application Terminology . . . . . . . . . . . . . . . . . 62
5.2 ESCON Director Console Application Terminology Examples . . . . . . . . . 63
5.3 HCD 9032-5 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
5.4 HCD 9032-5 Terminology Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
5.5 ESCON Manager Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
5.6 ESCON Manager Terminology Examples . . . . . . . . . . . . . . . . . . . . . . . . 67
5.7 Terminology Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Chapter 6. ESCON and FICON (FCV) Topology . . . . . . . . . . . . . . . . . . . . . 69
6.1 ESCON Point-to-Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
6.2 Switched Point-to-Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
6.3 ESCON Dedicated Connection (Static Connection) . . . . . . . . . . . . . . . . . 72
6.4 Chained Directors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
6.5 FICON (FCV) Connections - One Bridge Card Shown . . . . . . . . . . . . . . . 74
6.6 ESCON and FICON - Valid and Invalid Topologies . . . . . . . . . . . . . . . . . 75
6.7 Connectivity Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
6.8 Port Attributes - Matrix Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
6.9 LED and XDF Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
6.10 ESCON CNC to CU Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
6.11 FICON (FCV) Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
6.12 ESCON (CNC) and FICON (FCV) Intermix . . . . . . . . . . . . . . . . . . . . . . 81
6.13 FICON (FCV) MCP Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
6.14 Mode Conditioner Patch (MCP) Cables . . . . . . . . . . . . . . . . . . . . . . . . . 83
6.15 MCP Cables Invalid Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Chapter 7. Error recovery and Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . 85
7.1 Error Reporting and Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
7.2 ESCON Director Component Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
7.3 IRD000E Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
7.4 Director Event Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
7.5 Failures External to the ESCON Director . . . . . . . . . . . . . . . . . . . . . . . . . 90
7.6 Director LIN Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
7.7 Link Problem Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
7.8 Port Status Display with Graphics Off . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
7.9 Port Status Display with Graphics On . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
7.10 ESCON Manager Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
7.11 ESCON Manager Device View - Console or ISPF . . . . . . . . . . . . . . . . . 96
7.12 ESCON Manager Workstation Device Selection . . . . . . . . . . . . . . . . . . 97
7.13 ESCON Manager Workstation - Device Display . . . . . . . . . . . . . . . . . . . 98
7.14 Node Descriptor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
7.15 ESCON Director Node Descriptor Display (1) . . . . . . . . . . . . . . . . . . . 100
7.16 ESCM Workstation Node Descriptor Display (2) . . . . . . . . . . . . . . . . . 101
v
Chapter 8. Migration to the 9032-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103
8.1 Migration Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104
8.2 Port Address Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
8.3 Port Address by Quadrant for the 9032-5 and 9032-3 . . . . . . . . . . . . . . .106
8.4 Port Card Layout for the 9032-5 and the 9032-3 . . . . . . . . . . . . . . . . . . .107
Appendix A. Special Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Appendix B. Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
B.1 International Technical Support Organization Publications. . . . . . . . . . . . . . 111
B.2 Redbooks on CD-ROMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
B.3 Other Publications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
How to Get ITSO Redbooks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113
IBM Redbook Fax Order Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115
List of Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123
ITSO Redbook Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127
vi IBM ESCON Director 9032-5 Presentation
Copyright IBM Corp. 1999 vii
Preface
This redbook provides information on the 9032 Model 5 to enable you to plan for
the installation of the 9032-5, to operate and respond to OS/390 error messages
associated with the 9032-5, to define the 9032-5 to both the S/390 processor and
OS/390, and to understand how and where to support the 9032-5 switch matrix.
Also included are details of the various topologies that the 9032-5 ESCON
Director can be part of, and what fiber cabling is required to support the link
connections to and from the 9032-5. Both valid and invalid connection topologies
are discussed.
This Redbook also includes information on the installation and use of the FICON
Bridge card and FICON Bridge por in the 9032-5, and what topologies and
cabling are required to support the FICON channel (in FCV mode) links.
The Team That Wrote This Redbook
This redbook was produced by two specialists working at the International
Technical Support Organization Poughkeepsie Center.
Ken Trowell is a S/390 Systems Specialist at the International Technical Support
Organization, Poughkeepsie Center. He writes extensively and presents at IBM
workshops worldwide on all areas of S/390 Processors, Channels, Channel
Topology, and S/390 Architecture. Before joining the ITSO 3 years ago, Ken has
worked in a number of countries during his extensive career in IBM, providing
system support and consulting activities in the S/390 area.
Helen Howard is a S/390 Configuration design specialist in IBM Australia. She
has 12 years of experience in S/390. Her areas of expertise include S/390
support and ESCON configuration design. She has written extensively on S/390
recovery and I/O configurations.
Comments Welcome
Your comments are important to us!
We want our redbooks to be as helpful as possible. Please send us your
comments about this or other redbooks in one of the following ways:
Fax the evaluation form found in ITSO Redbook Evaluation on page 127 to
the fax number shown on the form.
Use the online evaluation form found at http://www.redbooks.ibm.com/
Send your comments in an internet note to redbook@us.ibm.com
viii IBM ESCON Director 9032-5 Presentation
Copyright IBM Corp. 1999 1
Chapter 1. 9032-5 ESCON Director Introduction
This chapter describes the functions and features of the 9032-5 ESCON Director.
Included is a comparison with previous ESCON Director models and detailed
information on the features that have been introduced with the 9032-5.
IBM 9032 Model 5
ESCON Director
Introduction
ITSO Technical Presentation
2 IBM ESCON Director 9032-5 Presentation
1.1 9032-5 Functions and Features (1)
This part of the presentation discusses the advanced functions and features of
the 9032-5.
The 9032-5 provides double the ESCON port capacity of its predecessor, the
9032-3.
The 9032-5 offers any to any connectivity for its full range of 248 ESCON ports.
All ESCON ports support attachment of channels, control units, serial CTCs,
converters (for attachment to convertors two 9032-5 ESCON ports are defined as
having a dedicated connection) and other ESCON Directors.
The 9032-5 ESCON will also support up to 16 FICON Bridge cards. Each FICON
Bridge card can support 1 FICON port. The internal matrix connections from the
FICON Bridge card can be to any ESCON port that logically connects to a
ESCON interface control unit or an ESCON serial CTC channels. The external
connection to the FICON Bridge card can only be to a S/390 FICON channel in
FCV mode. FCV mode is FICON ConVersion mode.
The 9032-5 supports both LED and XDF ESCON ports.
The minimum number of ESCON ports on a 9032-5 is 24 (this is 3 ESCON port
cards) and the maximum is 248 ESCON ports (this is 31 port cards). The
minimum number of FICON Bridge ports on a 9032-5 is zero and the maximum is
16 (this is 16 FICON Bridge cards). Together the number of ESCON port cards
and FICON Bridge cards in a 9032-5 cannot exceed 31.
Up to 248 ESCON Ports with any to any connectivity, with up
to 124 active simultaneous ESCON connections
There are 8 ESCON ports per ESCON port card
Up to 16 FICON Bridge Ports with any FICON to ESCON
connection, with up to 120 simultaneous communication
paths
There is 1 FICON (FCV) port per FICON Bridge card
Combination of 3 to 31 ESCON port cards with 0 to 16 FICON
Bridge cards (up to 31 cards in total)
Each ESCON port allows attachment of any ESCON Control
Unit, ESCON channel or another ESCON Director
LED and XDF Port ESCON support
FICON Bridge ports can only be externally connected S/390
FICON channels operating in FCV mode
Copyright IBM Corporation, 1999
IBM 9032 Model 5 ESCON Director
Functions and Features (1)
Chapter 1. 9032-5 ESCON Director Introduction 3
1.2 9032-5 Functions and Features (2)
The 9032-5 also offers some significant availability features, both standard and
optional, increased reliability and enhanced error detection, correction, and
recovery.
These features, listed above, will be discussed in more detail in the following
diagrams.
Functions and Features (2)
Enhanced Availability Features
Standard redundant power supplies
Standard redundant cooling fan assemblies
ESCON spare ports feature
Logical Partitioning capability
Non-disruptive maintenance for most components
Non-disruptive upgrades
1.3 Comparison of 9032-3, 9033-4 and 9032-5
This table compares the features available on the 9032-3, 9033-4 and 9032-5.
Some highlights of the comparison are:
The 9032-5 provides double the port capacity of the 9032-3.
The 9032-5 offers greater flexibility in port configuration.
The 9032-5 supports a higher maximum number of ports than the 9032-3 in
all categories.
The 9032-5 supports a lower minimum number of ports than the 9032-3 in
all categories.
Logical partitioning.
The redundant power supply feature that was an option on the 9032-3 is
standard on the 9032-5.
The 9032-5 also offers two new features, logical partitioning which is standard
and a spare ports card which is optional. Both of these features will be
discussed in detail.
9032-3, 9033-4, 9032-5 Comparison
Feature 9032-3 9033-4 9032-5
Maximum Ports (total) 124 16 248
Minimum ESCON Ports (total) 28 8 24
Maximum ESCON LED Ports 124 16 248
Minimum ESCON LED Ports 16 4 0
Maximum ESCON XDF Ports 108 12 248
Minimum ESCON XDF Ports 0 0 0
ESCON Ports per Card 4 4 8
Maximum FICON Bridge Ports Not Available Not Available 16
Minimum FICON Bridge Ports Not Available Not Available 0
FICON Ports per Card Not Available Not Available 1
Spare Ports Card Not Available Not Available Feature
Power Redundancy Feature Not Available Standard
CTP Card Redundancy Feature Not Available Feature
MXC/MXS Card Redundancy Feature Not Available Feature
TKRG Card Redundancy Feature Not Available Feature
Logical Partitioning Not Available Not Available Standard
1.4 9032-5 Feature Codes
This table shows the feature codes for the 9032-5. The console feature codes
have not been included. Console requirements and feature codes will be
discussed in 3.3, Console Platforms on page 40.
Feature code 5240 - ESCON LED port card
Feature code 5250 - ESCON XDF port card
Feature code 5260 - FICON Bridge port card
Feature code 5600 - Additional CTP card
Feature code 5500 - Additional MXC/MCS card set
Feature code 5800 - Additional TKRG controller adapter card
Feature code 5245 - Spare ports card, 4 ESCON LED ports
Feature code 5255 - Spare ports card, 2 ESCON LED and 2 ESCON XDF
ports
Feature codes 5700, 5701, 5702 and 5703 (when optional FC 5500 is
installed) - FICON enablement features for an already installed 9032-5
Feature codes 6700, 6701, 6702 and 5703 (when optional FC 5500 is
installed) - FICON enablement feature for a new 9032-5 (post June 1999)
Feature code 5902 - Installed ports in 9032-2 address range
Feature code 5903 - Installed ports in 9032-3 address range
The rows with the shaded background make up the Enhanced Availability
Features. These are shown in order of preference. The reliability of all of these
9032-5 Feature Codes
Feature
Code
Description Function
5240 LED Port Card Provides 8 x LED Ports
5250 XDF Port Card Provides 8 x XDF Ports
5260 FICON Bridge Card Provides 1 x FICON Bridge Port
5600 Additional CTP Card Provides redundancy for CTP Card
function, allows concurrent LIC updates
5500 Additional MXS/MCS Card Set Provides redundancy for MXC and MXS
Card function
5800 Additional TKRG Controller
Adapter Card
Provides redundancy for TKRG Controller
Adapter Card function
5245 Spare Ports Card - 4 LED
Ports
Provides Spare Port Capacity
5255 Spare Ports Card - 2 LED and
2 XDF Ports
Provides Spare Port Capacity
5700/3
5701
5702
MXC2 card for - FICON
3.3 power supply - FICON
Console Application - FICON
570x FICON enablement features for an
already installed 9032-5.
670x FICON enablement, new 9032-5
5900 9032-5 Console Standalone Console for the 9032-5
5902 Installed Ports in 9032-2
Address Range
Allows simple migration from 9032-2
5903 Installed Ports in 9032-3
Address Range
Allows simple migration from 9032-3
E
n
h
a
n
c
e
d
A
v
a
i
l
a
b
i
l
i
t
y
F
e
a
t
u
r
e
s
components is very high, so other factors should be taken into consideration in
the selection of appropriate features for each environment.
The CTP Enhanced Availability Feature provides redundancy for the CTP card
function, allows concurrent replacement of a CTP card and allows concurrent
LIC changes. LIC updates are disruptive if the CTP Enhanced Availability
Feature is not installed.
The MXC/MXS Enhanced Availability Feature provides redundancy for the
MXC/MXS card function and allows for concurrent replacement of MXC and
MXS cards.
The TKRG (Token Ring) Enhanced Availability Feature provides redundancy
for the TKRG card function. The TKRG card can be replaced non-disruptively
even when the TKRG Enhanced Availability Feature is not installed.
In an environment where high availability is required all Enhanced Availability
Features should be installed.
The spare ports card features are discussed with the next diagram.
Feature codes 5700, 5701, 5702 and 5703 (required when FC 5500 is installed)
optional) or 6700, 6701, 6702 and 5703 (required when FC 5500 is installed) are
required to be installed on the 9032-5 for the 9032-5 to support FICON. These
feature codes provide a new MXC card, new 3.3 volt power supplies, the console
application code to support FICON, and a new redundant MXC card. The 570x
group of feature codes will be provided as a result of ordering a FICON Bridge
port card (FC 5260) for an already installed 9032-5 that is not FICON enabled.
The 670x group of feature codes will be provided as a result of ordering a new
9032-5 (post June 1999).
Feature code 5902 should be ordered if the 9032-5 is going to replace a 9032-2
and 5903 should be ordered if the 9032-5 is going to replace a 9032-3, and the
customer wants the same port address scheme. The migration from a 9032-2 or
9032-3 to a 9032-5 is simplified if the port addresses on the old ESCON Director
are provided for on the new ESCON Director because the required I/O path
routing definition changes (destination port addresses) will be minimized.
The port addressing scheme for the 9032-5 is different from that of the 9032-2 or
9032-3. If the full complement of port cards is not ordered, the default address
range may not overlap with the existing address range on the ESCON Director
that is to be replaced. Feature codes 5902 and 5903 will ship a 9032-5 with port
cards positioned to correspond with the address ranges of the 9032-2 or 9032-3
respectively.
If neither of the feature codes is ordered, the port cards can be repositioned by
the service representative at installation time to satisfy customers port address
requirements. This applies to both the ESCON and FICON-bridge port cards. See
also 1.10, FICON Bridge Card Layout on page 13 for recommendations on
where to install the FICON Bridge cards.
Another option may be to use the ESCD Console to assign port addresses other
than the defaults to the installed ports, but this is not recommended.
For information on migration to the 9032-5 (with less than 248 ESCON ports)
from a previous ESCON Director Model (which may have a different port number
scheme) refer to Chapter 8, Migration to the 9032-5 on page 103. Also the
existing configuration on a previous ESCON Director model may not be suitable
for the 9032-5 in trying to meet a systems current availability requirement due to
the change in the quantity of ports per ESCON port card. The 9032-2 and the
9032-3 both had 4 ports per ESCON port card, whereas the 9032-5 has 8 ports
per ESCON port card.
1.5 Spare Ports Card
The logical port swap facility that was available on the 9032-3 is also available on
the 9032-5. This facility allows any failed ESCON port to be swapped with any
other ESCON port so that operation of the attached component can continue.
This process relies on a unused (free) port of the correct ESCON port type (LED
or XDF) being available or being able to be made available.
The 9032-5 ESCON spare ports feature is an enhancement to the basic port
swap facility.
If the spare ports feature is installed, four additional ESCON ports will be
available for port swapping in the event of port failures or for problem
determination. This eliminates potential difficulty in trying to obtain an unused
ESCON port if problems arise. The spare ports are not available to provide
additional connectivity. They can only be used as substitutes for existing ESCON
port addresses.
The spare ESCON ports card feature provides an
additional 4 ports that can be used in the event of
ESCON port failures
This is in addition to the standard any to any port swap
capability
The ESCON ports on the spare ports card cannot be
used as normal additional ports
The spare ESCON ports card may be either:
4 LED ESCON ports - FC5240
OR
2 LED and 2 XDF ESCON ports - FC5250
Can provide higher availability during maintenance and
repair activity
Provides a useful problem determination tool
Spare Ports Card Feature
1.6 Hardware Component Layout
This diagram shows the hardware layout of the 9032-5. The locations for
Enhanced Availability Features are shown with cross-hatching.
The footprint of the 9032-5 is the same as that of the 9032-3. Capacity is doubled
without the need for increased floor space.
The diagram shows the following components:
CTP card(s)
TKRG card(s) (Token Ring)
MXC/MXS card set(s)
Power supplies
ESCON or FICON port cards
Spare ESCON ports card
Quadrants
Hardware Component Layout
Port Cards MXC/MXS Card Sets
Cooling Fan Assemblies
Power On/Off Switch
Operator Panel
Spare Ports Card
CTP Cards
TKRG Cards
Power Supplies
Fiber Cable
Restraints
Quadrant
A
Quadrant
B
Quadrant
C
Quadrant
D
1.7 Hardware Components (1)
This diagram describes the function of some of the hardware components of the
9032-5.
Operator Panel
The operator panel includes the Initial Machine Load (IML) button, System Error
LED indicator and Power-on LED indicator. The IML button is protected by the
front cover when the door is closed. IML reloads the Licensed Internal Code (LIC)
and resets all the hardware, except the MXC/MXS and DVP cards, without
switching off power.
The operator panel also includes a Liquid Crystal Display (LCD) that can display
status and event messages using two 16-character lines. Four buttons are used
to control information displayed on the LCD.
Control Processor (CTP) Card
The CTP card contains the microprocessor and associated logic that provides
overall coordination for the director. The CTP card initializes hardware
components of the system after power-on or reset. While in operation the CTP
card supports the director Control Unit Port (CUP), maintenance port, operator
panel, ESCON port exception handling and error recovery.
Device Port (DVP) Cards
The ESCON DVP card provides the hardware interface to the ESCON fiber optic
media. Each ESCON card contains either 8 ESCON LED or 8 ESCON XDF
Hardware Components (1)
Operator Panel
Liquid Crystal Display (LCD) showing status and event messages
IML (Initial Machine Load) button
System Error and Power On LED indicators
Control Processor (CTP) Card
Overall co-ordination of the Director
Initializes hardware components after power on or reset
Supports the Director Control Unit Port (CUP)
Exception and error handling
Device Port (DVP) Cards (ESCON)
Hardware interface to ESCON fibre optic media
Supports either 8 LED or 8 XDF port interfaces
FICON Bridge Cards
Hardware interface to FICON (FCV) fibre optic media
Supports 1 FICON Bridge port interface
interfaces for ESCON fiber optic media. Fiber cables access to the ESCON LED
ports is by using IBM duplex connectors and ESCON XDF ports using FCS
connectors. XDF cables with IBM duplex connectors cannot be connected to the
ESCON XDF ports without the use of an adapter.
FICON Bridge Card
The FICON Bridge card is the hardware interface to the FICON FCS fiber optic
media, which requires that 9 micron single mode fiber cabling be used.
It is possible to re-use multi-mode fiber. If this is required, then a Mode
Conditioner Patch (MCP) cable must be installed at each end of the FICON (FCV
mode) link. See 6.13, FICON (FCV) MCP Cables on page 82 and 6.14, Mode
Conditioner Patch (MCP) Cables on page 83 for more details.
1.8 Hardware Components (2)
This diagram describes the function of the remainder of the critical hardware
components.
Spare Ports Card
The spare ESCON ports can only be used when a standard ESCON port is
swapped for the spare port. It does not increase the total number of active
connections available in the director. The fiber cable receptacles in the spare
Hardware Components (2)
ESCON Spare Ports Card
4 spare ports to provide redundancy
MXC/MXS (Matrix Controller/Matrix Switch) Cards
Make decisions on dynamic connection requests
Enforce attributes as configured in the active switch matrix
Token-Ring (TKRG) Adapter Card
Provides a port to connect the Director to a Token-Ring LAN for
console access
Power Supply
Provide DC power to the director
Operating load is shared by 2 power supplies
Provide cooling for internal components
Operation can continue with only 2 of the 4 fans operational
ports card are the same as those for the DVP card: IBM duplex for LED
connections and FCS for XDF connections.
MXC/MXS Cards
The three-card Matrix Controller and Matrix Switch set makes decisions on
dynamic connection requests. It also provides for connection paths between ports
specified by port attributes defined in the active matrix configuration.
TKRG Controller Adapter Card
This card provides a port to connect the Director to a 4/16 Mbps Token-Ring
Local Area Network (LAN) for access by a console on the LAN. The card also
contains an RS-232-D asynchronous serial port for connecting a maintenance
terminal. The maintenance terminal port is intended for use by service
representatives and allows access to 9032-5 maintenance utilities and functions.
Power Supplies
The power supplies provide DC power to the ESCON Director. The operating load
is shared by both power supplies until one fails. The operating power supply then
handles the full power load.
This differs from the operation of the Enhanced Availability Features, where the
secondary component is a backup component and is unused until a failure is
detected in the primary component.
Four fans provide cooling for the Director's internal components. The four fans are
housed in two assemblies, each containing two fans. The ESCON Director can
operate with any two of the four fans being operational. If three fans become
inoperative the ESCON Director will power off after 10-20 minutes.
1.9 Port Card Layout
The ESCON port cards in the 9032-5 are installed in four quadrants. Quadrants
A, B and C support up to eight ESCON port cards. Each ESCON port card
contains 8 ESCON ports for a maximum of 64 ports per quadrant for quadrants A,
B and C. Quadrant D supports only 7 port cards plus the spare ports card, so it
supports a maximum of 56 standard ESCON ports plus 4 spare ESCON ports.
Up to 16 FICON Bridge port cards can be installed in the 9032-5. They can be
installed in any port card location in any of the quadrants. However they are
recommended to be installed in the locations shown in 1.10, FICON Bridge Card
Layout on page 13.
The above table shows the port addresses assigned to each quadrant. In a
9032-5 without the full complement of ESCON port cards, quadrant A will be filled
first, followed by quadrant B, then C, and finally, D. This means that the default
ESCON port addresses will be contiguous even when the 9032-5 is not fully
populated with port cards.
The spare ESCON ports card will always be installed in the last position in
quadrant D regardless of the total number of ESCON port cards installed.
There are no FICON Bridge spare ports available as a 9032-5 feature code. If a
spare FICON Bridge port is required, it should be ordered and installed as a
normal FICON Bridge card (up to a maximum of 16).
Each quadrant is a potential failure boundary and this should be taken into
consideration when designing the ESCON Director configuration. For maximum
Port Card Layout
The port card layout is divided into four quadrants
Default port address assignments are as follows:
Quadrant Position Default Port Addresses
A Lower Right 04 - 43
B Lower Left 44 - 83
C Upper Right 84 - C3
D Upper Left C4 - FB
S1 - S4 (spare ports card)
In a 9032-5 that is not fully populated with port cards,
Quadrant A is filled first, followed by B, C and then D
All port cards are supported by a single logic board but
Quadrants provide isolation of some logic board
components
availability, multiple connections from a processor to a 9032-5 for either ESCON
or FICON ports, and multiple connections from a 9032-5 to the same control unit
for ESCON ports should be spread across multiple quadrants in the 9032-5.
1.10 FICON Bridge Card Layout
This diagram shows both the recommended port slot locations for the installation
of the FICON Bridge port cards and the sequence of installation. The port
addresses shown are for a 9032-5 ESCON Director using the standard default
port address assignment.
As the FICON Bridge port card only has one port, only the first port address
assigned to the port slot is used. The other 7 port addresses assigned to the port
slot are unused.
FICON Bridge Card Layout
S S S S
MXC/
MXS
Card
set 1
MXC/
MXS
Card
set 2
0 1
15 14 13 12 11 9 10 8
T
K
R
G
C
T
P
C
T
P
T
K
R
G
23 22 21 20 19 17 18 16
7 6 5 4 3 1 2 0
31 30 29 28 27 25 26 24
0 0 1 1 2 3
0 1
Quadrant
B
Port
Addr.
83 - 44
Quadrant
A
Port
Addr.
43 - 04
Quadrant
C
Port
Addr.
C3 - 84
Quadrant
D
Port
Addr.
FB - C4
Plugging Considerations
FICON Bridge port cards
Bridge port cards can be installed in any slot position except
the spare port slot.
To provide the maximum availability, the bridge port cards
should be installed in the order of Quadrant A, C, B, D.
Shown are the recommended slot locations and
installation sequence for 16 FICON Bridge port cards,
this allows for high availability.
Quadrant A - FICON Bridge port address 0C
Quadrant C - FICON Bridge port address 84
Quadrant B - FICON Bridge port address 4C
Quadrant D - FICON Bridge port address C4
Quadrant C - FICON Bridge port address A4
Quadrant D - FICON Bridge port address E4
Quadrant C - FICON Bridge port address 94
Quadrant D - FICON Bridge port address D4
Quadrant C - FICON Bridge port address B4
Quadrant D - FICON Bridge port address F4
1.11 Logical Partitioning
This diagram summarizes the logical partitioning capability of the 9032-5.
Logical partitioning allows an administrator to create port level access control that
is unique to each defined operator. This capability allows operators to access only
the ports that they are authorized to use and restricts unauthorized operators
from changing the port connectivity of any single device or set of devices under
control of the ESCON Director. This feature offers increased security and
maximizes the flexibility of the system configuration. Port authorization is
activated as soon as a user ID with limited port access is defined.
There are no restrictions on the allocation of ports to a Logical Partition. The
logical partition setup can be changed at any time by a user with administrator
authority.
Some examples of situations where logical partitioning could be used are:
A Service Bureau manages a mainframe site that processes data for several
businesses. Each business provides its own operations staff. The businesses
need to be able to make alterations to the ESCON Director configuration but
the Service Bureau needs to ensure that these changes cannot impact other
clients. Logical partitioning allows the Service Bureau to restrict the authority
of each of the operators at port level. This removes the possibility of an
operator inadvertently altering the connectivity attributes of a port outside the
authorized logical partition.
A test group and a production group share the use of a mainframe and
ESCON Directors but do not share other control units. The production control
Logical Partitioning
Logical partitioning allows the 9032-5 to be operated
securely as several separate ESCON Directors
A logical partition can be:
As small as 1 port to as large as 248 contiguous or
non-contiguous ports in any increment or physical location
A different size from any other logical partition
Made up of dedicated or shared ports
Easily implemented and modified
Some suitable environments for this feature may be:
A service bureau managing systems for several clients but
requiring operational isolation
A test system sharing ESCON directors with a production
environment
units can be protected from impact by the actions of the test group if the
production control unit ports and unshared channel ports are excluded from
the test group's partition. The production group can maintain control of the
entire switch by allowing all ports to be part of the production logical partition.
1.12 Logical Partitioning Examples
This diagram shows an example of the ESCON Director matrix with logical
partitioning active.
In this case the user is a printer operator who needs to reconfigure the printers
between 2 different systems. Logical partitioning has been set up to allow the
operator to alter only the ports associated with the printers. The ports that the
printer operator is able to alter are in the unshaded areas and are indicated by
arrows in the left margin. When port authorization is active the Operator ID of the
current user is displayed in the status window at the bottom of the matrix window.
This operator is not able to change attributes for any of the ports in the shaded
part of the matrix. The information in these areas is still visible and available for
reference but it is not alterable.
Logical Partitioning Example
Operator level
1.13 Concurrent Maintenance Capability
This table shows the non-disruptive maintenance and upgrade capability of the
9032-5.
All 9032-5 upgrade activity can be performed without disruption to the operation
of the Director. Many of the major hardware components can also be replaced
while the director continues to operate, particularly with the Enhanced Availability
Features installed.
Even with all of the Enhanced Availability Features installed, some 9032-5 parts
cannot be replaced while the Director is operational. We recommend that a high
availability I/O configuration should include at least two ESCON Directors to
eliminate these single points of failure at the Director level.
Concurrent Maintenance Capability
Component Concurrent
Replacement
without EAF
Concurrent
Replacement
with EAF
Concurrent
Upgrade
Cooling Fan Assembly Yes Yes N/A
Device Port Card (ESCON) Yes Yes Yes
FICON Bridge Card Yes Yes Yes
Operator Panel Yes Yes N/A
TKRG Adapter Card Yes Yes Yes
Power Supply Yes Yes N/A
Spare Port Card Yes Yes Yes
CTP Card No Yes Yes
MXC Card No Yes Yes
MXS Card No Yes Yes
Main Power Switch No No N/A
AC Power Receptacles No No N/A
Base Logic Board No No N/A
Chapter 2. Installation Planning
This chapter describes the preparation required for the installation of a 9032-5
ESCON Director.
There are many factors to be considered, including:
Physical placement and environment requirements
Console support requirements
Fiber cabling infrastructure and strategy
Software support requirements
ESCON Director definition
Configuration planning and definition
Each of these requirements is discussed in this chapter.
IBM 9032 Model 5
ESCON Director
Installation Planning
2.1 Environmental Specifications
This diagram shows some of the basic environmental specifications for the
9032-5 ESCON Director.
The 9032-5 has the same footprint as the 9032-3 but is significantly taller. Like
the 9032-3, service clearance is required at the front and back only, so Directors
can be installed in a row. Although there is no service clearance required at the
top of the 9032-5, the area must be kept clear to permit airflow.
The 9032-5 has dual power supplies as a standard feature. In order to take
maximum advantage of this availability feature the two power inputs should be
sourced from dedicated circuits on separate distribution boards and where
possible, separate UPS components.
This is not a comprehensive list of environmental specifications. For more
detailed information refer to IBM System/360, System/370, 4300, 9370
Processors Input/Output Equipment Installation Manual - Physical Planning -
GC22-7064.
Physical Characteristics
Width 660 mm
Depth 660 mm
Height 1645 mm
Weight 231.3 kg
Service Clearance required at front and rear only
Single phase power
2 independent sources recommended for high availability
Operating Environment
Temperature: 4.4 to 40.5 degrees C (40 to 105 degrees F)
Humidity: 10% to 80%
Air movement 23.67 cubic meters/minute
Air exits from bottom and top rear
Heat dissipation: 6390 BTU/hr
Environmental Specifications
Chapter 2. Installation Planning 19
2.2 Console Support Planning
.
Console Features
Need to determine where the ESCON Director Console Application will be
installed.
On an IBM provided 9032-5 Console, has the ESCD application pre-installed.
Via an orderable feature code to install the ESCD application on the S/390
HMC.
Via an orderable feature code to install the ESCD application on a customer
provided PC.
For full details of the console configuration and connectivity requirements see
Chapter 3, 9032-5 Console on page 37.
IP Addresses
Depending on the chosen console configuration there may be a requirement to
assign some TCP/IP addresses for the Director and the console. If the Director
and console are to be attached to a dedicated LAN, then the default IP addresses
may be acceptable for the installation. The default addresses are 1.1.1.x for the
ESCON Director and 1.1.1.1 for the IBM-supplied ESCON Director console. If
these addresses are not acceptable, the network administrator will need to assign
new IP addresses.
The number of addresses required depends on whether a secondary console is
to be used and whether that console is to be used as a backup or a replacement
Console Support Planning
IP address requirements if the Director and Console are
to be attached to other than a dedicated LAN
TCP/IP IP address for Director
TCP/IP IP address for Console
TCP/IP IP address for backup console
A unique IP address is not required for a replacement console
because it uses the same IP address as the primary
LAN cable and MAU requirements
Shielded twisted pair wiring for token-ring LAN
6.1 m (20') cables are supplied
MAUs should support 4/16 Mbps
Optional MAUs can be ordered with the Director
Set up for DCAF Remote Support access and security
LAN
Modem
console. If the second console is a replacement console an additional IP address
will not be required because the second console will use the same IP address as
the primary. If the second console is a backup console (with LAN attachment) it
will require its own IP address.
LAN Cabling
Prior to installation, consideration should be given to the LAN cabling
requirements.
If the ESCON Director and console are to be attached to an existing LAN then
MAU ports must be available. If addition MAU ports are required, a MAU can be
ordered with the ESCON Director by specifying Feature Code 5400.
If the MAU ports are not in close proximity to the Director and console, additional
LAN cables will also be required. The LAN cables supplied with the ESCON
Director have D shell connectors at the Director end of the cable and an IBM
Type-1 LAN connector at the other end. This type of connector may not be
compatible with existing LAN infrastructure so adapters may be required.
Remote Access
DCAF remote access may be provided either via the LAN or via a telephone
connection and modem.
If DCAF access is to be provided via a modem, it will be necessary to ensure that
an appropriate modem is available and that telephone access is available in close
proximity to the console.
2.3 Fiber Cabling Considerations
This diagram shows some of the fiber cabling considerations when installing a
9032-5.
The amount of cable required for routing inside the director for a 9032-5 is
significantly more than that required for the previous models. This may lead to
some difficulties if the 9032-5 is to replace an earlier model. The existing cables
may not be long enough to reach many of the ports in the new ESCON Director.
This should also be taken into consideration when jumper cables are installed in
preparation for the 9032-5 install.
A fully populated 9032-5 may have up to 248 ESCON jumper cables connected to
its ports. This volume of cables can be cumbersome and can even be damaged if
appropriate cable routing and strain relief is not used.
Because of the volume of jumper cables required in a fully populated switch, the
9032-5 is a good candidate for the use of trunk cables.
The 9032-5 has the added advantage of supporting the IBM Fiber Optic Transport
Services (FTS) Direct Attach Feature. The FTS is discussed in more detail in the
following sections.
Fiber Cabling Considerations
Plan for 2.8 meters of fiber cable inside the Director to
provide for cable routing
This is more than was required for previous 9032 models
When the 9032-5 is a straight replacement for a previous 9032
model, many existing fiber cables may be too short
Plan for 1.0 meter of slack cable external to the Director
for limited machine movement
This requirement was the same for previous 9032 models
Follow a logical plan for routing cables
Spread across 3 access/cable restraint areas
Use the strain relief provided to avoid cable and port card damage
Consider direct attach trunking options
9032-5 supports FTS Direct Attach
2.4 Fiber Optic Transport Services (FTS) Direct Attach
FTS is a well-established fiber trunking system, and consists of a FTS trunking
system, FTS zone cabinets, FTS central cabinets and standard IBM ESCON
jumper cables.
It utilizes the zone and central cabinet concept. Components are directly attached
to zone cabinets by jumper cables. These connections are propagated to a
central cabinet via a trunk.
The advantage of the Direct Attach feature is that it allows the ESCON Director
ports to be trunked to a central cabinet without the need for an intervening zone
cabinet. The Direct Attach feature is also supported on most of IBM's processors
so it is now possible to trunk directly from a processor to an ESCON Director
without the need for zone or central cabinets.
The diagrams which follow illustrate this feature in more detail.
FTS Direct Attach
IBM Fiber Transport Services (FTS) Direct Attach
FTS-III Direct Attach fiber optic trunk cables contain groups of 12
fibers that support 6 ESCON channels (62.5 micron fibers)
The trunk cables connect to harnesses which convert the trunk
connectors into groups of 6 IBM duplex connectors
The trunk cables are run inside the 9032-5 and plug to harnesses at
the rear of the machine
The harnesses plug into the individual ESCON fiber optic ports
(ESCD ESCON ports or S/390 processor ESCON channel ports)
Eliminates the need for zone distribution cabinets at the
ESCON Directors (and S/390 Processors)
ESCON Director ports can be trunked directly to a central cabinet
Reduces the requirement for central distribution cabinets
ESCON Director ports can be trunked directly to the Direct Attach
feature on S/390 processors
2.5 Trunking Options
These diagrams show examples of commonly used fiber cabling methods.
Throughout this series of diagrams, the aim is to connect six ESCON channels
from the processor on the right hand side, through the switch and to the control
units on the left hand side.
The first example is a simple configuration using no trunk cables. Six jumper
cables connect the processor to the ESCON Director and another six jumper
cables connect the ESCON Director to the control units.
This is a suitable configuration where short distances are involved and where the
configuration is stable. If the configuration changes frequently the workload due
to the cabling change could become a concern.
The second example shows a fully trunked configuration. Processors, ESCON
Directors and control units are all attached to zone cabinets. The Zone cabinets
are attached via trunks to central cabinets. The connections between
components are made using jumper cables at the central cabinets.
This is a suitable environment where extended distances are involved or where
frequent reconfigurations, involving physical recabling, is required.
Trunking Options
No Trunking
Full Trunking
Jumper Cable
Trunk Cable
9032-5
Control Units S/390
Central
Cabinets
Zone
Cabinet
Zone
Cabinet
9032-5
Control Units S/390
2.6 FTS Direct Attach Trunking Options (1)
This diagram shows some examples of the use of FTS Direct Attach. The
illustrated configurations achieve exactly the same connectivity as the previous
examples.
The first example shows the use of FTS Direct Attach at the ESCON Director.
This removes the requirement for the ESCON Director ports to be cabled to a
zone cabinet. They are trunked directly to a central cabinet.
This is a suitable environment where extended distances are involved or where
frequent reconfiguration, involving physical recabling, is required. This
configuration offers exactly the same flexibility for reconfiguration as the fully
trunked example on the previous diagram but with reduced connections and
complexity.
The second example shows the use of the FTS Direct Attach feature in
combination with the same feature on a processor. This allows the processor to
be trunked directly to the ESCON director rather than via zone and central
cabinets. Full flexibility for the reconfiguration of control unit ports is maintained.
In some environments a combination of direct processor trunking and trunking via
a cabinet would be used. This allows more flexibility for reconfiguration,
particularly if direct connections between processors and control units are
required.
In most environments, however, the majority of CHPIDs will be attached to
ESCON Directors so the Direct Attach feature is of significant value.
FTS Direct Attach Trunking Options (1)
FTS Direct Attach at ESCD
Jumper Cable
Trunk Cable
FTS Direct Attach at
ESCD and Processor
Central
Cabinets
Zone
Cabinet
Zone
Cabinet
9032-5
Control Units S/390
Central
Cabinets
Zone
Cabinet
9032-5
Control Units S/390
There are many different central cabinet configurations possible. This diagram
shows the use of two different sets of central cabinets.
In most cases the paths from the S/390 processor to the ESCON-attached control
units should be routed through at least 2 ESCON Directors. The diagram shows
the S/390 processor ESCON channels split between different central cabinets
and using direct attach trunking systems for the connections. The routing is then
through 2 different direct attached trunking system 9032-5s, and then on to the
zone cabinets, with final connections being to the control units.
Jumper Cable
Trunk Cable
FTS Direct Attach at ESCD and Processor
Central
Cabinets
Zone
Cabinet
9032-5
Control Units S/390
Zone
Cabinet
Central
Cabinets
9032-5
Other S/390
Processor
channels
There are many different central cabinet configurations possible. This diagram
shows the sharing of a common set of central cabinets.
This will still support the paths from the S/390 processor to the ESCON-attached
control units being routed through at least 2 ESCON Directors. This diagram
shows the S/390 processor ESCON channels all going to the same set of central
cabinets and using direct attach trunking systems for the connections. The
routing is then through 2 different direct attached trunking system 9032-5s, and
then on to the zone cabinets, with final connections being to the control units.
Jumper Cable
Trunk Cable
FTS Direct Attach at ESCD and Processor
Central
Cabinets
Zone
Cabinet
Control Units S/390
9032-5 9032-5
Other S/390
Processor
channels
2.9 Supported Software Levels
This table shows the minimum level and release requirements for support of the
9032-5.
All of the major IBM operating systems are supported.
Also included in this table are the optional OS/390 products for support of the
ESCON Director environment. These are ESCON Manager and System
Automation for OS/390.
ESCON Manager
The IBM Enterprise Systems Connection Manager (ESCON Manager) is a
licensed program (Program Number 5688-008) that provides host control to help
manage connectivity within a computer facility.
Release 3 of ESCON Manager is designed to run on MVS/ESA 5.1 and
subsequent releases of that host operating system. With the application of the
resolution to Authorized Problem Analysis Report (APAR) PN51474, however,
Release 3 can run on MVS 4.2 and 4.3.Therefore, Release 3 can provide a
unified system image that includes hosts on any of these MVS/ESA levels. The
9032-5, however, is only supported by MVS/ESA V5 and higher.
To support the FICON channel in FCV mode the minimum OS/390 level required
is version 1 release 3, plus PTFs shown in the diagram.
Supported Software Levels
Platform Levels
Supported
Minimum Host
Requirements
MVS/ESA V5 or higher
OS/390 V1R2 or higher V1R3 for FICON
VM/ESA 2.1 and 2.2 2.2 and 2.3 FICON Bridge
TPF 4.1
VSE/ESA
ESCON Manager V1R3M0 MVS/ESA 4.2 (with PTF)
OS/390 1.3 with FICON
Guest Support under VM/ESA
System Automation
for OS/390
V1R2 MVS/ESA 5.1
OS/390 1.3 with FICON
Guest support under VM/ESA
Release 3 of ESCON Manager can run on MVS/ESA when that operating system
is running as a guest in a VM/ESA environment. Release 3 does not run directly
on VM/ESA.
If the ESCON Manager workstation feature is to be utilized, the following
minimum software requirements apply:
Host software
MVS/ESA Version 5.1
ACF/VTAM Version 3 Release 4.1
Workstation software
OS/2 2.1
Communications Manager/2 1.0
GraphicsView/2 1.1 (Service level 7)
System Automation for OS/390 (SA/MVS)
System Automation for OS/390 (SA/MVS), which runs on MVS/ESA in addition to
OS/390, is a NetView-based application designed to provide you with a single
point of control for a full range of systems management functions. SA/MVS plays
a key role in supplying high-end automation solutions, as Tivoli Systems (TME
10) delivers integrated cross-platform management functions. SA/MVS functions
include the monitoring, control, and automation of a large range of system
elements spanning both the hardware and software resources of your enterprise.
SA/MVS not only provides new functions previously unavailable in the systems
management environment, but also integrates in a single product the functions of
three established licensed programs: Automated Operations
Control/MVS(AOC/MVS), ESCON Manager (ESCM) and Target System Control
Facility (TSCF). Integrating these products provides you with simpler and more
consistent installation, customization, maintenance, product documentation,
workstation windows, automation and more. Integrating the products also builds a
foundation of information and control functions, which SA/MVS exploits for new
functions like I/O Exception Monitoring. SA/MVS host-based program requires:
OS/390 1.0 or MVS/ESA 5.1 with either JES2 5.1 or JES3 5.1.1
OS/390 1.3 is required for FICON support
NetView 3.1 for MVS/ESA (includes NGMF and RODM)
ACF/VTAM 3.4.1
ACF/VTAM 4.1, optional, for 4-digit device numbering
ISPF 4.1 (with PTF UW20596)
TSO/E 2.4
C/370 Run Time Library 2.1
PL/I Run Time Library 2.3
DFSMS/MVS 2.1
SMP/E 1.8
RMF 5.1 (with PTF UW21592)
IBM Library for SAA REXX/370 1.3 or REXX Alternate Library 1.3 (FMID
HWJ9123), shipped with System Automation for OS/390
IBM 3270 PC File Transfer Program 1.1.1
APVUFILE can be substituted for this in Japanese.
2.10 Software Prerequisites
This table shows the software prerequisites for support of the 9032-5.
Use IBM Service Link or contact your IBM representative to obtain a current copy
of the Preventive Service Planning (PSP) Bucket. This contains specific software
planning information; for example, APARs and PTFs required for each of the
levels of support.
Software Prerequisites
Platform APARs Component
MVS/ESA IR35816
OW28009
OW28013
EREP
ESCD device support including HCD
IOS
OS/390 IR35816
OW28009
OW28013
EREP
ESCD device support including HCD
IOS
VM/ESA VM61260
VM61305
VM62090
ESCD device support
EREP
2.2.0 and 2.3.0 basic FICON support
including ESCD FICON bridge
TPF n/a
VSE/ESA DY44548 EREP
ESCON Manager (server) PQ06732 9032-5 device support
ESCON Manager (client) BQ06732 9032-5 device support
System Automation for
OS/390 (server)
OW28450
OW32307
OW32306
OW35299
9032-5 device support
248 ports support
V1.3 FICON Bridge support
V1.2 FICON Bridge support
System Automation for
OS/390 (client)
9032-5 device support
2.11 ESCON Manager - System Automation for OS/390
In any large, multisystem computing facility, understanding and controlling
connectivity is a complex task. For even a minor system change, you may need
more than definition files to understand whether two objects have the correct
chain of connections through channels, switches, control units, and devices.
Assistance by operations personnel may be needed to complete the proper
sequence of actions, especially if the task at hand involves problem determination
procedures or "disaster" recovery actions.
ESCON Manager is a systems management product that provides a broad set of
configuration information and control functions to help make these tasks relatively
simple. It also ensures system integrity by taking into account the perspectives of
multiple systems. One ESCON Manager communicates with other ESCON
Managers and with other computer facilities to coordinate and manage
connectivity changes.
This foil describes some of the advantages of ESCON Manager. ESCON
Manager can:
Provide a unified system image
Provide a single point of control
Simplify or eliminate some planner and operator tasks
Provide a means to automate connectivity changes to a dynamic switch, such
as an ESCON Director
Reduce system problems caused by human error
ESCON Manager - SA/MVS
ESCON Manager or System Automation for OS/390 are
optional products to support an ESCON environment
ESCON Manager provides:
Single point of control for managing ESCON connectivity across all
operating systems
ESCON Manager on each operating system is in communication with ESCON
Manager on every other operating system
ESCON manager self discovery
ESCON manager self discovers the system I/O configuration
High availability connectivity management
ESCON Manager prevents and ESCD change that would cause the loss of the
last path to an allocated device on any operating system sharing the ESCD
Valuable problem determination aids
The only source of switch routing information available from the operating
system
The option to manage ESCON Director matrix configuration definitions
using HCD
Provide access to the active and saved configurations of a dynamic switch
Update the ESCON Manager internal configuration map to reflect I/O
configuration changes
Remove a dynamic switch from, and restore it to, system communication
All of this is useful for a variety of tasks like reconfiguration, availability
management, backup and recovery, and migration.
2.12 9032-5 Port Definition - HCD Support
The installed 9032-5 port addresses should be defined as being installed using
HCD when being supported by OS/390.
For ESCON installed ports, define them in a contiguous group of 8 ports.
For a FICON Bridge port, only one port is defined in a group of 8 port addresses
that are assigned to the port slot that the FICON Bridge card is installed in. The
port address for the FICON Bridge port will be modulo 8 minus 4. The other 7 port
addresses assigned to the port slot should be defined as not installed.
The example in this diagram shows both ESCON installed ports (1C to 23) and a
FICON Bridge installed port (24).
9032-5 Port Definition - HCD Support
Use HCD to define the ports installed in the 9032-5; only define those
ports that are actually installed
For ESCON ports they are installed defined in contiguous groups of 8
For FICON Bridge ports, only one is defined in a group of 8. The other 7
ports addresses should not be defined as installed. For FICON the port
addresses will be modulo 8 minus 4.
Switch ID . . . . : AF Switch AF
---------------Connection---------------
/ Port H Name + Unit ID Unit Type O
_ 1C Y ________________________ CU 2401 3990-6 N
_ 1D Y ________________________ N
_ 1E Y ________________________ N
_ 1F Y ________________________ N
_ 20 Y ________________________ N
_ 21 Y ________________________ N
_ 22 Y ________________________ N
_ 23 Y ________________________ N
_ 24 Y ________________________ PR SCZP601 CHPID F5 9672-R76 N
_ 25 N ________________________ _
_ 26 N ________________________ _
_ 27 N ________________________ _
_ 28 N ________________________ _
_ 29 N ________________________ _
_ 2A N ________________________ _
_ 2B N ________________________ _
Installed ESCON Ports 1C-23
Installed FICON Port 24
Un-installed Ports 25-2B
2.13 9032-5 I/O Definition
The ESCON Director, like any other device in the I/O configuration, should be
defined in the IODF. This allows the ESCON Director to present errors against its
device number, to attached operating systems. It also provides a means for
ESCON Manager to communicate with the Director.
It is possible for the ESCON Director to be used to provide connectivity without its
CUP (Control Unit Port) device being defined to the operating system, but this is
not recommended.
There should be at least two paths defined to access the ESCON Director (CUP).
These paths should be attached to different quadrants or different port cards to
eliminate the quadrant and the port card as single points of failure for
communication with the Director CUP by the operating system.
Channel activity for communication with the ESCON Director is usually extremely
low. If ESCON Manager is not used there is virtually no channel activity, just the
very occasional error report. This means that the ESCON Director can share
paths with other I/O devices connected though the Director without adversely
impacting their performance. When the ESCON Director control unit is defined,
the destination link address for all paths must be FE. This is the port address
assigned to the Control Unit Port (CUP). The CUP is a logical port used for
communication with the Director.
Like many other ESCON devices, the unit address for the ESCON Director must
be set to 00. If this parameter is not specified the unit address will default to the
last 2 digits of the device number. The unit address is specified in both the control
9032-5 I/O Definition
An ESCON Director device should be defined to all systems
that have CHPID attached to the ESCON Director
This provides support for
Host error reporting
An ESCON Manager interface to the ESCON Director
ESCON manager allocates the ESCON Director device
At least 2 paths should be defined to the ESCON Director
control unit port (CUP)
CHPID connections should be supported by different port cards
CHPID connections should be supported by different quadrants
Dedicated paths are not required
Link Address for all channel paths to the CUP must be FE
This is the port address assigned to the Control Unit Port (CUP)
Unit Address for 9032 devices must be 00
For both the control unit and device definitions
Note: The 9032-5 does not use a CUADD definition
unit and the device definitions. If the unit address in the control unit definition and
the unit address in the device definition do not match, HCD will post an error
message to inform the user.
2.14 HCD I/O Definition - 9032-5 Control Unit and Device
This diagram shows some examples of the HCD Panels displaying the definition
of an ESCON Director control unit. In this case there are two paths defined from
each of the processors.
The arrows show the destination link address of FE for all of the channel paths
and the Control Unit unit address field set to 00.
The last display shows the Unit Address field for the ESCON CUP device set to
00, as is required.
Processor ---------------Unit Address . Unit Range---------------
ID 1----- 2----- 3----- 4----- 5----- 6----- 7----- 8-----
SCZP601 00
SCZP701 00
HCD I/O Definition - CU and Device
Control unit number . : 001F Switch AF
Control unit type . . : 9032-5 Serial number . . . : 0408699032
Connected to switches : AF
Ports . . . . . . . . : FE
Processor Logical --------Channel Path ID . Link Address---------
ID Address 1---- 2---- 3---- 4---- 5---- 6---- 7---- 8----
SCZP601 9B.FE AC.FE
SCZP701 9B.FE AC.FE
ESCON Director Control Unit and Device definition
panels showing:
Destination link address of FE
Unit Address of 00
No Logical Address (CUADD)
Device number . . : 001F Number of devices . : 1
Device type . . . : 9032-5 Preferred Explicit Device
/ Processor ID UA + Time-Out STADET CHPID + Candidate List
_ SCZP501 00 No Yes __ No
_ SCZP601 00 No Yes __ No
9032-5 Control Unit - Unit Address
9032-5 Device - Unit Address
2.15 Operating System 9032-5 Device Definition
The arrow shows the parameters and features for the 9032-5 definition to the
operating system. The feature of interest is the OFFLINE definition feature,
Device considered online or offline at IPL. This feature should be set to Yes so
that the ESCON Director will be offline at IPL. For operating systems without
ESCON Manager, the Director devices should remain offline. For operating
systems with ESCON Manager, the devices should be brought online when
ESCON Manager is started. This prevents access to the ESCON Directors
control unit CUP by unauthorized users or applications.
Operating System I/O Device Definition
9032-5 Device should be defined to Operating System
Configurations as offline at IPL
This prevents a wrong allocation exposure
Configuration ID . : L06RMVS1 Sysplex systems
Device number . . : 001F Number of devices : 1
Device type . . . : 9032-5
Parameter/
Feature Value P Req. Description
OFFLINE Yes Device considered online or offline at IPL
DYNAMIC Yes Device supports dynamic configuration
LOCANY No UCB can reside in 31 bit storage
2.16 ESCON Configuration Guidelines
So far, the discussion has centered around the ESCON Director and its
definitions and requirements. The ESCON Director is likely to be a critical
component in any system and it is important to ensure that it is used as effectively
as possible.
This diagram shows some guidelines that should be followed when deciding on a
suitable ESCON Director configuration. The aim of these guidelines is to reduce
the impact to operating systems if a failure occurs in a Director or any component
of a Director.
The ESCON Director port cards are divided into quadrants. Each quadrant
represents a potential failure boundary. Spreading connections from the same
system or from the same control unit across multiple quadrants reduces the
impact of a failure affecting a quadrant.
Note that the number of ports on a ESCON port card in the 9032-5 is eight, and
for a FICON Bridge card one port address is used. Eight ports are assigned to the
port card location that the FICON Bridge card is installed in, but only one port
address is used. The other seven port addresses are not useable.There are four
ESCON ports on a ESCON port card in the previous 9032 and 9033 models. The
ESCON port assignment methods used when designing a 9032-3 configuration
may not be suitable when designing a 9032-5 configuration. For example, in a
9032-3 environment the ESCON ports assigned to a DASD subsystem may be 84
and 88. This is not a suitable assignment of ports in a 9032-5 because these
ESCON ports are on the same ESCON port card.
ESCON Configuration Guidelines
Provide redundancy at the ESCON Director level:
Spread connections from the same system and from the same
control unit across multiple ESCON Directors
Provide redundancy at the ESCON Director quadrant level:
Spread connections from the same system and from the same
control unit across multiple quadrants in the ESCON Director
Provide redundancy at the ESCON Director port card level:
Spread connections from the same system or from the same control
unit across as many port cards as possible
To reduce the impact of an ESCON port card failure:
Try and attach channels to the a port on the same port card as their
destination ports
Prohibit connections that are not required
Reduces overhead in recovery
Simplifies problem determination
The final recommendation takes into consideration the planned connectivity
between channel and control unit ports. Where possible, channel and control unit
ports that communicate with each other should be supported by the same port
card. This will not always be possible because each port is likely to communicate
with several other ports. If this recommendation is followed the number of
connections affected by a port card failure can be significantly reduced.
ESCON ports that are not intended to communicate with each other should be set
to a Prohibit connection. This reduces overhead in recovery processing and in
some circumstances, simplifies problem determination.
2.17 ESCON and FICON I/O Definition Guidelines
This diagram lists some general guidelines for I/O definition in an ESCON
Environment.
HCD does validity checking based on the information provided by the user.
When defining CHPIDs in HCD it is necessary to enter a dynamic switch ID but
the switch entry port is not a required parameter for ESCON channels. If this
information is entered the value of HCD's validity checking is maximized. HCD is
able to verify that you do not intend to use the same port address on the same
switch twice. This also serves as a simple way to manage switch port allocation.
HCM users don't have to worry about managing Director port allocation - HCM's
graphic interface does it all without the need to input additional information.
ESCON I/O Definition Guidelines
Channel definition
Using HCD
Define the ESCON Director dynamic switch number - required
Define ESCON Director switch entry ports - optional
This will allow HCD to verify your configuration and ensure that you have
not used the same port twice
Using HCM
Graphic interface simplifies definition
Level of detail required ensures maximum benefit from HCD's
configuration validity checking
Externally connected Control Unit definitions
Try to make control unit definitions symmetrical
Use the same port address on different switches to access the same
control unit
This simplifies the definition and reduces the likelihood of errors
Define the Control Unit's ESCON Director connection ports - optional
This will allow HCD to verify your configuration and ensure that you have
not used the same port twice
Chapter 3. 9032-5 Console
This chapter describes the requirements for setting up the ESCON Director
Console. Hardware and software requirements and configuration options are
discussed in detail. Remote console access to the 9032-5 is also included in this
chapter.
IBM 9032 Model 5
ESCON Director
Consoles
3.1 Console Introduction
Console Introduction
The 9032-5 is supported by the ESCON Director Console Application which runs
on a PC attached to a Token-Ring LAN.
The console can be used to monitor and control up to 16 ESCON Directors.
Supported Directors are the 9032-3, 9033-4 and 9032-5.
The list shown in the diagram shows some of the functions for which the console
is required.
The ESCON Director console is not required for continuous operation of the
Directors, nor is it required to recover after a Director is powered off/on. One
matrix configuration file, the IPL file, is stored in the CTP card. If defaults are
accepted (Active = Saved option selected), this file will be the most recently
activated matrix configuration. After power off/on, the Director operation will be
restored and the matrix configuration stored in the CTP card will be active.
IBM recommends that the Director Console should always be attached to the
Director:
To maintain copies of matrix configuration files
To provide error reporting and log functions
To provide current status of the entire Director network
Console Introduction
The 9032-5 is supported by a WIN-OS/2-based ESCD
Console Application running on a Token-Ring attached PC
The console can monitor and control up to 16 ESCDs
The ESCON Director Console is required to:
Install the ESCON Director
Access Logs
Perform service actions
Perform upgrades and LIC changes
Save configuration matrix files independent of hosts
Manage ESCDs configurations (if ESCM is not installed)
Console is required for changes to be saved to disk even when changes
are made using ESCM
The 9032-5 may have a session with only one console
A backup console may be available but if connectivity to the 9032 is
available from the prime Console, the Console Application must first
be shut down on the prime console
Chapter 3. 9032-5 Console 39
Copies of all required matrix configurations should be stored on the ESCD
console disk. This facilitates recovery in the event of a failure in the CTP card.
The console is not required for activating matrix configuration changes from the
host using System Automation for OS/390 (SA/MVS) or ESCON Manager. The
use of ESCON Manager reduces the requirement for physical access to the
ESCON Director console, but it does not reduce the requirement for the console
to be available. The console is required if these matrix configuration changes are
to be saved to the HDD in the console PC.
For maximum availability, a backup console should be maintained if the Directors
provide access to critical system or application data. There are two options for
configuring the backup console:
1. Maintain a PC with all current configuration files but without attachment to the
LAN. This PC may have the same IP address as the primary Director Console.
In the event of a failure of the primary console, its LAN connection can be
transferred to the secondary console. This is referred to as a replacement
console.
2. Maintain a PC with all current configuration files and LAN attachment. An
additional unique IP address will be required for this PC. The ESCON Director
Console Application on the backup PC must not be active. In the event of a
failure of the primary console, the ESCON Director Console Application can
be started on the secondary console. This is referred to as a backup console.
3.2 Minimum Console Requirements
.
Console Minimum Requirements
Hardware
Color Monitor
Mouse
1.44/2.88 Diskette Drive
4/16 Mbps Token-Ring Adapter
card
32 MB RAM
270 MB fixed disk
CD-ROM drive
SCSI adapter
640 MB rewriteable optical
cartridge (ROC) drive
Pentium 166 MHz
Software
ESCD Console Application
TCP/IP Version 2.0 for OS/2
Base Kit
TCP/IP Version 2.0 for
OS/2:DOS/Windows
LANAID Version 2.21
OS/2 Version 4.0
Automatic backup system (PM
Timer)
Communications Manager/2
Version 1.1** (for SNA)
DCAF Version 1.32**
** Required for DCAF remote access
This diagram lists the minimum hardware and software requirements for a
console supporting the ESCD Console Application for a 9032-5.
These requirements are not the same as the requirements for 9032-3 and
9033-4. In most cases a console currently used for support of 9032-3 and/or
9033-4 will not be suitable for use with the 9032-5.
3.3 Console Platforms
This diagram shows the platforms available for supporting the 9032-5 ESCON
Director Console Application. These are shown in order of preference. As
previously discussed, the ESCON Director Console Application should be
available at all times. Although the HMC supports the ESCD Console Application,
it is not a recommended platform for the following reasons:
The HMC is used as an alerting tool. This function is effectively disabled while
an operator is using the ESCD application.
HMC operator functions are unavailable while an operator is using the ESCD
Application.
The ESCD Console Application must not be included in the HMC
STARTUP.CMD file. If the HMC is re-booted for any reason, the ESCD
Console Application will not be restarted without operator intervention.
The IBM-supplied PC is preferable to the customer-supplied PC because it is
pre-configured with all required hardware and software. If a customer-supplied
Console Platforms
The ESCON Director Console Application can exist on
three different platforms
An IBM PC supplied with the 9032-5
Order Feature Code 5900
Customer-supplied PC
Order Feature Code 5901, to install the Console Application code
Hardware Management Console
Order Feature Code 5901, to install the Console Application code
IBM strongly recommends using the IBM-supplied PC
Dedicated PC is more suitable because of the critical nature of
the application
IBM supplied PC is pre-configured with all required hardware and
software
PC is used, it should be dedicated as the ESCD console, with no additional
applications installed.
3.4 Console Configurations
The LAN to which the ESCON Director is connected may be dedicated, private or
public.
A dedicated LAN supports only the ESCON Directors and their consoles. It does
not have connectivity to any other network components or hardware. Because no
other connectivity is provided the IP addresses of the console and the ESCON
Directors need only be unique with respect to each other.
Private LAN refers to a LAN with tightly controlled access such as the typical
machine room LAN supporting S/390 Servers, HMCs and other critical
equipment.
Public LAN refers to the typical local LAN used to support all users in an area.
The security on a public LAN is generally less restrictive and the traffic is less
predictable.
It is possible for the ESCON Director and its console to be attached to different
LANs but still communicate through a bridge. The bridge must be configured to
allow TCP/IP protocol to flow. The 9032-5 does not support IP routing so the
connection between an ESCON Director on one LAN and the console on another
cannot involve routing.
Console Configurations
The ESCON Director Console can be located anywhere
up to the limit of the installed token ring
The console and 9032-5 may be attached to a dedicated,
private or a public LAN
IP routing is not supported by the 9032-5
If the console and the 9032-5 are attached to different
LANs, direct communication can be established through
a bridge
The bridge must be configured to allow TCP/IP protocol to pass
through
Remote access to the ESCON Director Console
Application may be provided through DCAF via a LAN
or modem connection
By using Distributed Console Access Facility (DCAF) Controller software, it is
possible to initiate a remote session with the ESCD console via a LAN connection
or a modem. The remote session has all the command privileges of the target
console. DCAF network protocol may be TCP/IP (with routing) or SNA.
Before a remote DCAF session can be established, the ESCON Director Console
Application must be set up to run in a WIN-OS/2 window rather than in WIN-OS/2
full-screen mode. WIN-OS/2 full-screen mode is not supported by DCAF.
3.5 Some Supported Console Configurations
This diagram shows some of the supported 9032-5 console configurations. It
does not cover all of the possible combinations and variations. In all cases remote
support is available, either via the corporate LAN or via a modem.
The diagram on the left-hand side shows the Director and the console attached to
a dedicated LAN. No other network equipment has access to this LAN. In this
example, remote access is provided via a modem.
This is the simplest console configuration. It is secure and easy to set up because
IP addresses can remain at their default values.
The configuration in the center of the page shows a private machine room LAN
with the ESCON Director Console Application residing on an HMC. In this case,
the HMC can be remotely accessed by DCAF via the corporate LAN. Other users
Some Supported Configurations
Token-Ring
LAN
ESCD
Console
Private LAN with
Dedicated Console
Private LAN
with HMC
Remote
Operator
HMC
HMC with
ESCD Console
Application
Token-Ring
LAN
D
C
A
F
Corporate
LAN
Remote
Operator
ESCD pic
Remote
Operator
ESCD
Console
Token-Ring
LAN
Dedicated LAN
D
C
A
F
ESCD pic
D
C
A
F
of the machine room LAN may include S/390 Servers, HMCs, Sysplex Timers and
Sysplex Timer consoles.
This configuration is also secure and provides for remote access, but the use of
the HMC to support the ESCD Console Application is a disadvantage, as
previously discussed.
The configuration on the right-hand side is a slight variation on the previous
configuration. Again, the machine room LAN is used but in this case, the ESCD
Console application is supported by a dedicated PC rather than the HMC. In this
case the Machine Room LAN cannot be accessed from the Corporate LAN, so
DCAF access is provided via a modem connection.
The use of a dedicated console is preferable to the use of the HMC.
3.6 More Supported Console Configurations
The console configuration on the left-hand side shows bridged LANs. The
ESCON Director and its console are attached to different LANs and the LANs are
connected through a bridge.
Using a bridge in this way is not recommended. Problem determination is more
difficult because failures in one LAN segment can impact the other.
The configuration on the right hand side shows the ESCON Director and a
dedicated console attached to a public LAN (corporate LAN).
More Supported Configurations
ESCD
Console
Other
Hardware
Corporate LAN
ESCD
Console
Bridge
Bridged LAN
Token-Ring
LAN
Token-Ring
LAN
Remote
Operator
Remote
Operator
HMC
HMC
D
C
A
F
Corporate
LAN
HMC
D
C
A
F
Corporate
LAN
Token-Ring
LAN
This may offer advantages in that the existing LAN infrastructure may be used,
but the security implications should be considered. Appropriate measures should
be taken to ensure that access to the ESCON Director console is not freely
available to all LAN users.
Another disadvantage of this configuration is that the traffic on a public LAN is
less predictable. There is potential for communication between the Director and
the console to be impaired by excessive traffic on the LAN.
3.7 Console Recommendations
This diagram lists some general recommendations for the ESCD console
configuration and setup.
Because of the critical nature of the ESCD console applications, a dedicated
console is preferred over a console shared with other applications such as the
HMC Application.
The ESCD Console Application should be available at all times. As previously
discussed, the console should be used as a repository for matrix configurations. If
a matrix change is activated when the console is not available, the only copy of
that change may be in the CTP card. If the Active=Saved option is not selected,
there may be no non-volatile copy of the active configuration.
Access to the ESCD console is required for maintenance and hardware upgrade
activities. Many of the console application facilities are also useful for problem
determination. For these reasons, there is a requirement for the console to be
located close to the ESCON Directors.
Console Recommendations
Use a dedicated PC to support the ESCD Console
Application
Install the console in close proximity to the 9032-5
Required for service activity and for problem determination
Connect the ESCD and the console to a private 9672
Machine Room LAN
Provide remote access to the ESCON Director Console
Application via DCAF
Implement security measures
Physical security
Password Protection within the ESCD Console Application
Restrict access using appropriate LAN security
DCAF password
The use of a private LAN is preferable to a public LAN because a private LAN is
likely to have tighter security controls implemented.The traffic on a private LAN is
also more likely to be controlled. As discussed, excessive traffic on a public LAN
may impair communication between he Director and its console.
The use of a private LAN is preferable to the use of a dedicated LAN because of
increased flexibility. In particular, it allows the use of DCAF for remote access via
the corporate LAN.
Security is an important consideration in the design of a suitable ESCD console
configuration.
The ESCON Director is likely to be a critical system component. Physical
access to the Director and its console should be restricted appropriately.
Password protection is provided within the ESCON Director Console
Application. There are three different levels of authority by default and this can
be increased if logical partitioning (port authorization) is implemented. The
operator is required to enter a password before any potentially disruptive
change can be activated.
The ESCON Directors and console are on LANs and may be open to access
by devices on the local LAN or from remote LANs. LAN security measures
should be implemented to meet the installation's requirement. Access to the
TCP/IP address associated with the ESCON Director console should be
limited to the required nodes only.
Remote access to the LAN may be provided through DCAF via a LAN or
modem connection. DCAF passwords should be implemented to prevent
unauthorized access.
3.8 Recommended Console Configuration
The diagram shows a recommended ESCON Director Console configuration.
The ESCON Director Console Application is supported by a dedicated PC.
The Director and consoles are attached to a private machine room LAN.
Remote access is provided through DCAF via the Corporate LAN.
A backup console is available in the event of a failure of the primary console.
Recommended Console Configuration
HMC
ESCD
Console
ESCD
Backup
Console
D
C
A
F
Machine Room
Private LAN
Corporate
LAN
Remote
Operator
Chapter 4. ESCON Matrix and Connectivity Management
This chapter reviews options for the management of ESCON Director matrix
configurations. This includes management of changes as well as the options
available for storage of matrix configuration data.
IBM 9032 Model 5
ESCON Director
Matrix Management
4.1 Matrix and Connectivity Management
ESCON Director connectivity changes can be made from the ESCON Director
Console Application or from the host.
Connectivity changes can only be made from the host through Systems
Automation for OS/390 (SA/MVS) or ESCON Manager.
There are 4 different repositories for ESCON Director Matrix configurations.
These are:
ESCON Director Console HDD
ESCON Manager Workstation HDD
ESCON Manager ISPF datasets
HCD IODF
Regardless of the chosen matrix configuration manager, copies of all required
matrix configurations should be stored on the ESCON Director Console HDD.
This ensures that the required configuration will be available independent of host
operating systems and applications.
In the following diagrams, matrix configuration management options will be
discussed.
Matrix/Connectivity Management
ESCON Director matrix connectivity changes can be
managed from:
The ESCON Director console
ESCON Manager
Commands at operating system console
ISPF or workstation interfaces
HCD
ESCON Manager required for retrieval of matrix data and for activation
ESCON Director matrix configurations can be stored in:
ESCON Director Console
ESCON Manager Workstation
ESCON Manager ISPF datasets
HCD IODF
Required matrix configurations should be stored in the
Chapter 4. ESCON Matrix and Connectivity Management 49
.
Changing Connectivity Attributes
This diagram shows the relationships between the various components which can
be involved in changing ESCON Director matrix attributes.
The solid lines with arrows toward the ESCON Director show the activation paths
- the ways in which the ESCON Director's connectivity attributes can be changed.
These activation paths include:
Activation of changes from the ESCON Director console
ESCON Manager commands at the operating system console
ESCON Manager commands (command builder) or matrix activation using the
ESCON Manager workstation interface
ESCON Manager commands or matrix activation using the ISPF interface
Matrix activation from HCD via ESCON Manager
The solid lines with arrows away from the ESCON Director show the paths
through which the ESCON Director's active matrix can be retrieved. The active
matrix can be retrieved from the ESCON Director's CTP card through:
The ESCON Director Console
The ESCON Manager workstation interface
The ESCON Manager ISPF interface
HCD using the migrate switch function.
Changing Connectivity Attributes
ESCON
Manager
HCD
HCD User
Operating System
Console
ESCON
Director
IODF
ESCM ISPF
OS/390 Environment
Activate
Save and Retrieve
Matrix Configurations
LEGEND
ESCM
Datasets
HDD
ESCM Workstation
HDD
Retrieve Active
Matrix
The broken lines show the paths through which an ESCON Director matrix can be
saved and a saved matrix retrieved.
The matrix repository for the ESCON Director Console Application is the HDD
in the ESCON Director console.
The matrix repositories for the ESCON Manager workstation are the HDD in
the workstation and the HDD in the ESCON Director console.
The matrix repositories for the ESCON Manager ISPF interface are its own
datasets and the HDD in the ESCON Director console.
The matrix repositories for HCD are the IODF and the HDD in the ESCON
Director console
The common element in all of this is the ESCON Director console's HDD. Matrix
configurations cannot be saved to the ESCON Director console unless the
ESCON Director Console Application is active and able to communicate with the
ESCON Director. The availability of the ESCON Director Console Application is
critical to effective matrix management.
4.2 ESCON Director Console Application as Matrix Manager
The ESCON Director Console application can be used to manage all ESCON
Director matrix changes.
Connectivity changes can be managed at the port or matrix level.
Matrix management at port level refers to minor changes that do not require
the creation of a new matrix configuration file. For example, an operator may
Password is required for activation of any matrix
change
No interaction with hosts for activation of connectivity
changes
System impact can result from human error
Changes can be made at port level or at matrix level
Individual port changes can be made at the active matrix and then
activated
A matrix can be created or selected by name and activated or
saved
Can store up to 16 matrix configurations for each
ESCON Director
Backup of configuration files is critical
ESCD Console as Matrix Manager
block a port at the request of a service representative in order to isolate a
failing component. This is a temporary condition and there is no requirement
to save a copy of the new matrix created.
Matrix management at the matrix level refers to changes that affect many
components in the director. For example, a new processor is to be installed
and a new matrix to support its connectivity has been built. The new matrix will
be activated when the new processor is implemented. If the processor
implementation is unsuccessful the old matrix can be reactivated.
The main disadvantage of using the ESCON Director Console Application to
manage matrix configurations is that changes are activated without any
interaction with attached operating systems. This means that there is potential to
impact system availability if the operator at the ESCON Director console makes
an error. The only requirement for activation of a change to proceed is the correct
password.
If the ESCON Director console application is used to manage matrix
configurations it will be the only repository for matrix configuration files. In this
environment it is particularly important to ensure that a backup of the console's
HDD is made regularly and every time a configuration change is made. The
9032-5 ESCON Director console can be set up to automatically back up files to
the ROC (rewritable optical cartridge) at user-specified intervals.
4.3 ESCON Director Console Application - Save Matrix
ESCD Console - Save Matrix
This diagram shows an example of the use of the ESCON Director Console
Application to save a matrix configuration. The name for the new matrix is
NEWP502 and a field is provided to give a description of this configuration.
Also displayed in this window are the details for one of the previously saved
matrix configurations, NEWP501. This shows the description of the configuration
as well as save details.
4.4 ESCON Manager as Matrix manager (1)
The use of ESCON Manager makes Director connectivity changes safe because
ESCON Manager will prevent the removal of the last path to an allocated device
on any of the hosts connected to the Director.
If ESCON Manager or SA/MVS is available on the host systems then it should be
used for all ESCON Director Matrix changes.
Operating System Console Interface to ESCON Manager
An operator can enter ESCON manager commands from an operating system
console to change any of the matrix attributes. The changes are activated at the
time when the commands are entered if all operating systems concur. The
commands entered can only affect connectivity to the port(s) targeted by the
command. It is not possible to activate or save a matrix configuration from the
operating system console.
The display shows the use of the ESCON Manager block command from the
operating system console. The command is prefixed with F IHV, where ihv is the
Provides high availability matrix connectivity
management
All systems with access to the switch are consulted before
changes are activated
ESCON Manager prevents removal of the last path to an allocated
device
Operating system console interface
Changes can be made at port level only
Matrix configurations cannot be activated or saved
Security provided by console authority
Utilizes OS/390 Modify command
ESCM as Matrix Manager (1)
F IHV,BLOCK (08) 001F
IHVR010I ESCM COMMAND ENTERED BY SYS OPER ON SC53IHV
IHVR011I BLOCK (08) 001F NOFORCE VARY BACKOUT
IHVC000I BLOCK COMMAND SUCCESSFUL
IHVO000I ESCM IS READY TO PROCESS OPERATOR COMMANDS
task name for ESCON Manager on this operating system. In this case the
command completed successfully.
4.5 ESCON Manager as Matrix Manager (2)
The ISPF and workstation interfaces to ESCON Manager allow for management
of the ESCON Director configuration at the matrix level.
ISPF Interface to ESCON Manager
A TSO user with appropriate authority can use the ESCON Manager ISPF
interface. All of the commands available to the operating system console user are
also available to the ISPF interface user.
In addition to this, the ISPF interface provides a view of the entire matrix. This
allows for a matrix to be built, activated and saved. The user has the option of
saving the configuration to an ISPF dataset or to the ESCON Director console
HDD.
Workstation Interface to ESCON Manager
The ESCON Manager workstation interface has all the capabilities of the IPSF
interface with a graphical user interface.
The workstation user has the option of saving matrix configurations to the
workstation's HDD or the ESCON Director's HDD
ESCM as Matrix Manager (2)
ISPF interface
Provides a text-based view of the port matrix
Changes can be made at port or matrix level
Matrix configurations can be saved to host datasets or the ESCD
console fixed disk
Security provided by system security product (RACF)
Workstation
Provides a graphic interface
Similar to the ESCON Director Console Application
Changes can be made at port (command builder) or matrix level
Matrix configurations can be saved to workstation .MAT files or
the ESCD console fixed disk
4.6 ESCON Manager ISPF Port Matrix Display
This diagram shows a sample matrix display from the ESCON Manager ISPF
interface. The user navigates through the matrix using the PFKeys. The map on
the right hand side indicates the current position within the matrix. Each X
represents a 32x32 port area of the matrix although only 16x16 ports are visible
on the screen. This means that it is necessary to move in the same direction
twice in order to see a change in the map position.
The PFKeys are also used to initiate the SAVE, ACTIVATE and RETRIEVE
options.
ESCM ISPF Port Matrix Display
------------ Matrix from NO SAVED , SWCH number 001F -------------------------
COMMAND ===> SCROLL ===> PAGE
Make changes, or enter COMMANDS or OPTIONS
Target SWCH Number ===> 001F SWCH Name: SWITCHAF
Port Name H B C 00 1 2 3 4 5 6 7 8 9 A B C D E F
_ 04 P601_CHP_9B __ _ __ \ a a a a P P P a a a a Map
_ 05 P601_CHP_29_CVC __ _ 06 a \ a a a a a a a a a a
_ 06 9034#5_PRT008 __ _ 05 a a \ a a a a a a a a a X.......
_ 07 9034#6_PRT006 O B __ a a a \ a a a a a a a a ........
_ 08 P701_CHP_29_CVC O _ __ a a a a \ a a a a a a a ........
_ 09 P601_CHP_8F __ _ __ P a a a a \ P P a a a a ........
_ 0A P601_CHP_93 __ _ __ P a a a a P \ P a a a a ........
_ 0B ________________________ L _ __ P a a a a P P \ a a a a ........
_ 0C 9034#7_PRT010 __ _ 0E a a a a a a a a \ a a a ........
_ 0D 9034#8_PRT310 O _ __ a a a a a a a a a \ a a ........
_ 0E P701_CHP_BC_CVC __ _ 0C a a a a a a a a a a \ a
_ 0F P601_CHP_BC_CVC __ _ __ a a a a a a a a a a a \
F1=HELP F2=SPLIT F3=END F4=REFRESH F5=SAVE F6=ACTIVATE
F7=UP F8=DOWN F9=SWAP F10=Left F11=Right F12=RETRIEVE
4.7 ESCON Manager Workstation Port Matrix Display
This is a view of the ESCON Director matrix using the ESCON Manager
workstation interface. The user navigates through the matrix using scroll bars.
Changes can be made by overtyping the required fields or by using the Edit
pulldown on the menu bar. Changes are activated using the File pulldown on the
menu bar.
From a matrix management perspective, the ESCON Manager workstation
interface is very similar to the ESCON Director Console Application.
ESCM Workstation Port Matrix Display
4.8 HCD as Matrix Manager
ESCON Director matrix configurations can be stored in an IODF and activated
using HCD. The active matrix configuration can also be retrieved from the
Director using the HCD Migrate Switch function. Saved matrix configurations at
the ESCON Director console can be retrieved using the same facility. This option
can only be used if ESCON Manager is available on the operating system. HCD
cannot communicate directly with the ESCON Directors and relies on ESCON
Manager to provide this interface.
Because ESCON Manager is used as the interface to the ESCON Directors,
ESCON Manager protection against the loss of the last path to an allocated
device is enforced.
One of the main advantages of using HCD as the manager and repository for
matrix configurations is that it creates a central repository, the IODF, for all
configuration data. This can also save a great deal of time and effort because
HCD provides port connection information based on channel and control unit
definitions.
An IODF can store multiple matrix configurations for each ESCON Director. HCD
allows activation of a switch matrix only from a production IODF. It is possible to
have several matrix configurations on the current production IODF and switch
between them seamlessly.
If there is a requirement to create a new matrix it will be necessary to build the
matrix in a work IODF. The work IODF must then be converted to a production
IODF before the matrix can be activated.
HCD as Matrix Manager
Changes activated at matrix level only
Requires ESCM to provide the interface to the ESCDs
ESCM protection provided for all matrix activation
Central repository for all configuration data (IODF)
IODF can contain multiple matrix configurations for each ESCD
Matrix configurations can only be changed in a Work IODF
Matrix configurations can only be activated from a Production IODF
Full matrix cannot be displayed in HCD
Intersection of ports 04-0F cannot be shown
ISPF limitation of 254 columns for a table
Attributes for this area are updated using the port list option
On the port matrix dynamic connections cannot be specified for the
intersection of 00-0F to 00-0F. Use the port list to do so.
This may present a problem in some environments if ESCON Director matrix
changes are made frequently. If a common IODF is used for all configuration
information, dynamic activation of the IODF across all systems will be required. In
most environments, changes to the ESCON Director matrix correspond to
changes in the hardware configuration so no additional IODF activation is
required.
It is possible to maintain a separate IODF just for ESCON Director Matrix
configurations but this defeats the purpose of using the IODF as a central
repository for configuration data.
From a user's perspective, there is a shortcoming in the way that the port matrix
is displayed in HCD. The intersection of ports 04-0F cannot be displayed on the
port matrix screen. This is due to an ISPF limitation of 254 columns for an ISPF
table.
Attributes for the intersection of these ports can be entered from a different
screen but the interface is less user-friendly.
4.9 HCD Matrix Manager Example
This diagram shows an example of the use of HCD to create and activate a new
ESCON Director matrix configuration.
In this installation there are two different matrix configurations used for Switch AF.
The activation of these matrix configurations is controlled using HCD.
HCD - Matrix Management Example
Two different matrix configurations used for Switch AF
AFCFG1 and AFCGF2
Both are defined in IODF01
New configuration required
AFCFG3
New IODF02 created with all three configurations defined
AFCFG1
AFCFG2
SYSn.IODF01 SYSn.IODF02.WORK
AFCFG1
AFCFG2
AFCFG1
AFCFG2
AFCFG3
AFCFG1
AFCFG2
AFCFG3
SYSn.IODF02 SYSn.IODF02.WORK
Edit
AFCFG1
Activate
Activate
Work
IODF
Production
IODF
SWITCH AF
AFCFG1
AFCFG2
AFCFG2
AFCFG3
When a requirement arises to create a new matrix configuration the steps shown
in the diagram must be taken.
1. The current production IODF (IODF01) is used to create a new Work IODF,
IODF02.WORK.
2. The new matrix configuration is built and saved in the Work IODF.
3. A production IODF, IODF02, is built from the Work IODF.
4. The new matrix configuration can be activated using IODF02.
4.10 HCD Port Matrix Screen
The diagram shows a sample of the HCD Port Matrix screen. There is a great
deal of similarity between this and the ESCON Manager ISPF interface. The user
moves around the matrix using the PFKeys but in this case a matrix map is not
provided. PF3 is used to save and exit.
Activation of a matrix configuration and saving to the ESCD console are
performed from the HCD Activate or Process Configuration Data menu.
HCD Port Matrix Screen
Port Matrix Row 1 of 248 More:
Command ===> _____________________________________________ Scroll ===> PAGE
Select one or more ports, then press Enter.
Switch ID . . . . . . . . : AF Switch AF
Switch configuration ID . : ESCD001F Default connection : Allow
Ded --Dynamic Connection Ports 1x--
/ Port Name B Con + 0 1 2 3 4 5 6 7 8 9 A B C D E F
_ 04 P601_CHP_9B N __ * * P P P P P P P P P P P P P P
_ 05 P601_CHP_29_CVC N 06 * * * * * * * * * * * * * * * *
_ 06 9034#5_PRT008 N 05 * * * * * * * * * * * * * * * *
_ 07 9034#6_PRT006 Y __ * * * * * * * * * * * * * * * *
/ 08 P701_CHP_29_CVC N __ * * * * * * * * * * * * * * * *
_ 09 P601_CHP_8F N __ * * P P P P P P P P P P P P P P
_ 0A P701_CHP_93 N __ P P P P P P P P P P P P P P P P
_ 0B ________________________ N __ P P P P P P P P P P P P P P P P
_ 0C 9034#7_PRT010 N 0E * * * * * * * * * * * * * * * *
_ 0D 9034#8_PRT310 N __ * * * * * * * * * * * * * * * *
_ 0E P701_CHP_BC_CVC N 0C * * * * * * * * * * * * * * * *
_ 0F P601_CHP_BC_CVC N __ * * * * * * * * * * * * * * * *
_ 10 ________________________ N __ \ P P P P P P P P P P P P P P P
_ 11 ________________________ N __ P \ P P P P P P P P P P P P P P
_ 12 ________________________ Y __ P P \ P P P P P P P P P P P P P
F1=Help F2=Split F3=Exit F4=Prompt F5=Reset F7=Backward
F8=Forward F9=Swap F10=Actions F12=Cancel F13=Instruct F19=Left
F20=Right F22=Command
4.11 Matrix Management Recommendations
This diagram lists some recommendations for high availability ESCON Director
matrix management.
The use of ESCON Manager to make any connectivity changes is strongly
recommended. ESCON Manager usage provides insurance against system
impact due to errors in matrix setup.
The ESCON Director console is a critical component in the ESCON environment.
Copies of all current matrix configurations should be stored on the ESCON
Director console's HDD. It is the only source of matrix configuration files with
independence from the host and ESCON Manager.
The use of HCD for matrix management is recommended because it allows all
configuration data to be stored in a central repository. It also reduces errors and
duplication of effort because data already entered in the I/O definition process is
available when the matrix is built. HCD tells you which unit is attached to each
port based on your previously entered definition data.
The only environment where this may not be suitable, as previously discussed is
an environment where matrix changes are made without a requirement for I/O
definition changes. This is likely to be a very rare occurrence.
Because of the requirement to go through the process of creating a new
production IODF to change a matrix configuration, it is recommended that
temporary changes be made using any of the ESCON Manager user interfaces.
Recommendations
Install ESCON Manager on all systems with attachment
to ESCON Directors
Do not make connectivity changes independent of ESCON
Manager
Regardless of matrix manager, always store copies of
all required matrix configurations in the ESCD console
Implement backup procedures for the ESCD console
Maintain a backup or replacement ESCD console
Use HCD to manage ESCD matrix configurations
Exception may be environments where frequent matrix changes
are required without I/O definition changes
Use ESCON manager for temporary port attribute
changes
Chapter 5. ESCON Director Terminology
In this chapter the terminology associated with ESCON Director and ESCON
Director matrix management are discussed. Choosing suitable naming
conventions and standards can simplify the operation and management of
ESCON Directors.
IBM 9032 Model 5
ESCON Director
Matrix Management
5.1 ESCON Director Console Application Terminology
This list shows the terms used by the ESCON Director. The term Director ID is
used only by the ESCON Director Console Application.
Terminology - ESCON Director
ESCON Director Console Application
Director ID
8-character name assigned when the 9032 is defined to a console
Appears in the Operator Panel LCD
IP Address
TCP/IP address assigned to the ESCON Director
Default CUP Name
Optional 24-character name
Used as a consistent name to assign to all matrix configurations for the
same Director
CUP Name
Name for the currently displayed configuration matrix
Default CUP name is used if CUP Name is not specified
Saved Configuration Matrix Name
8-character file name under which a matrix configuration is stored
Must be unique for each ESCON Director
Chapter 5. ESCON Director Terminology 63
5.2 ESCON Director Console Application Terminology Examples
This diagram shows examples of usage of the terms discussed in the previous
diagram.
The Director Definition window is used to define the ESCON Director to the
console at installation time. The required fields in this window are Director ID and
IP Address.
The lower window is the Select Saved Configuration Matrix window. This shows a
list of the matrix configuration files which have been previously saved for a 9032
with a Director ID of SWITCHAF.
ESCD Terminology Examples
Director Definition Window
Director ID required
Operator Panel LCD
IP address of ESCD required
Default CUP Name optional
Select Saved Configuration Matrix
Window
Director ID selection required
Saved Matrix Name selection required
5.3 HCD 9032-5 Terminology
This list describes the terminology used by HCD in the definition of the Director
and of control units with paths routed through the Director. The terms used in
support of matrix configuration management are also described.
Device Number
What the device is known as by the system operator and OS/390 when doing
I/O operations. For example, the operator issues Vary Path or Display Units
commands and quotes this device number. When OS/390 reports a problem
for this device it does so using the Device Number.
Switch ID
Unique 2 character identifier used in switch and channel path definition. This
switch ID is not used during the performance of an I/O operation to normal I/O
(DASD and Tape, etc.). It is used in the ESCOM Manager displays.
Reported as Logical Switch Number (LSN) by ESCON Manager
Reported as LSN by I/O Problem Determination facilities on IBM S/390
Servers and ES/9000 processors
Switch Configuration ID
An 8-character name under which a matrix configuration can be stored within
HCD
Must be unique for each switch configuration for the ESCON Director. Another
ESCON Director can have the same switch configuration name.
Terminology - HCD
HCD
Device Number
What the device is known as by the operator and OS/390 when doing I/O
Switch ID
Unique 2 character identifier used in switch and channel path definition
Reported as Logical Switch Number (LSN) by ESCON Manager
Reported as LSN by I/O Problem Determination facilities on IBM S/390
Servers and ES/9000 processors
8-character name under which a matrix configuration can be stored within
HCD
Must be unique for each switch configuration for the ESCON Director
ESCON Director File Name
Same as ESCON Director Saved Configuration Matrix Name
Used during migration of switch configurations from a saved ESCON
Director file
Used to save configuration files to the ESCON Director
ESCON Director File Name
Same as ESCON Director Saved Configuration Matrix Name
Used during migration of switch configurations from a saved ESCON Director
file
Used to save configuration files to the ESCON Director
5.4 HCD 9032-5 Terminology Examples
This diagram shows two examples of the use of the terms Switch ID and Switch
Configuration.
The first example is the Port Matrix screen which is used to build and save matrix
configurations within HCD.
The second is the Activate Switch Configuration screen which is used to identify
the matrix configuration to be activated.
HCD Terminology Examples
HCD Port Matrix and Activate Switch Configuration
screens showing the use of:
Switch ID
Matrix configurations are saved and referenced using these two
parameters
Switch ID . . . . . . . . : AF Switch AF
Switch configuration ID . : ESCD001F Default connection : Allow
Ded --Dynamic Connection Ports 1x--
/ Port Name B Con + 0 1 2 3 4 5 6 7 8 9 A B C D E F
_ 04 P401_CHP_9B_____________ N __ * * P P P P P P P P * * P P P P
_ 05 P401_CHP_29_CVC_________ N 06 * * * * * * * * * * * * * * * *
_ 06 9034#5_PRT008___________ N 05 * * * * * * * * * * * * * * * *
Activate Switch Configuration
Specify the following values
IODF name . . . . . . . . : 'SYS6.IODF22'
Switch ID . . . . . . . . . AF +
Switch configuration ID . . ESCD001F +
5.5 ESCON Manager Terminology
This list shows the terms used by ESCON Manager in its management of the
ESCON Director.
Note that the ESCON Manager Logical Switch Number (LSN) is the same as the
HCD Switch ID. ESCON Manager determines the relationship between device
number and Logical Switch Number or Switch ID when it allocates the switch
devices at startup.
Terminology - ESCON Manager
ESCON Manager
SWCH NMBR or Switch Device Number
Same as OS/390 device number
SWCH Name
Same as CUP Name
Activation of a matrix through ESCON Manager with an altered SWCH
Name will overwrite the CUP Name or Default CUP Name
Logical Switch Number (LSN)
Same as Switch ID in HCD
Saved Configuration Matrix Name - two occurrences
Saved Configuration Matrix Name for matrix saved to the Director
Console
Saved Configuration Matrix Name for matrix saved in ISPF
5.6 ESCON Manager Terminology Examples
This diagram shows some examples of the use of the previously described
ESCON Manager terminology.
The first example is the Select Switch screen showing the association between
the switch device number and the Logical Switch Number.
The second example shows the Select Saved Matrix screen that lists switch
configuration names by switch device number.
The last example shows the output from an ESCON Manager DISPLAY DEVICE
command for the ESCON Director device. This shows the use of the Switch
Device Number and the Logical Switch Number. It also shows the use of the
SWCH Name or ESCON Director CUP Name. This is displayed in the port name
field for the CUP port, FE.
ESCON Manager Displays
ESCM Terminology Examples
Sw Dev Config Config Save Save
S Number Name Description Date Time
- ---- -------- ------------------------ -------- --------
_ 001F IPL 13/19/02 00:00:00
_ 001F NEWP501 After R75 installation 09/25/97 21:53:50
Switch Number
Device of
S Number LSN Unique ID Ports Status
- ---- -- -------------------------- --- -------------
_ 001E AE 009032003IBM02000000020995 61 OPERATIONAL
_ 001F AF 009032005IBM02000000040000 249 OPERATIONAL
IHVC824I PORT
IHVC825I CHP SWCH STATUS
IHVC826I DEVN CHP TYPE DEVN LSN PORT H B C P PORT NAME
IHVC827I 001F 9B CNC_S 001F AF 04 P P401_CHP_9B
IHVC82AI CNTL UNIT DATA:001F AF FE SWITCHAF
Select Switch
Select Saved Matrix
Display Device 001F *
5.7 Terminology Recommendations
The previous diagrams have described the terms used by the ESCON Director
Console Application, HCD and ESCON Manager. It should be clear that there is
not full consistency in the terms used for various components in the ESCON
Director environment.
The recommendations presented on this diagram are meant to simplify the
operation and management of the ESCON Director by using consistent and
logical names for related components.
Terminology Recommendations
Choose a Switch ID, Director ID and Device Number that are
easily related
For example, Device Number FF0A - Switch ID 0A - Director ID SWCH0A
Make the CUP Name (ESCD)/SWCH Name (ESCM) the same
as the Director ID
Use the same CUP Name/SWCH Name for all matrix configurations
associated with the same Director
When HCD is used as the repository for switch matrix
configurations
Make the Switch Configuration ID (HCD) the same as the Saved
Configuration Matrix Name (ESCD)
When ESCON Manager is used as the repository for switch
matrix configurations
Make the Saved Configuration Matrix Names in ESCM the same as those
in the ESCD
Chapter 6. ESCON and FICON (FCV) Topology
This chapter reviews ESCON and FICON topology. This includes the types of
connections supported by the ESCON architecture and the FICON channel (in
FCV mode) as well as distance limitations for the supported ports and
connections.
IBM 9032 Model 5
ESCON Director
ESCON Topology
6.1 ESCON Point-to-Point
The ESCON Point-to-point topology is ESCON attachment without the use of
dynamic switching through an ESCON Director. The processor channel is
connected directly to an ESCON interface adapter in a control unit.
The maximum number of devices that can be supported on a channel using this
type of connection is equal to the maximum number of devices supported by the
control unit (up to a S/390 9672 ESCON limitation of 1024).
The ESCON channel can still address multiple control unit images (CUADD) in
the one physical CU.
An ESCON channel can be attached directly
to an ESCON-interfaced Control Unit
Each channel can provide a path to only one
physical Control Unit
In many cases this provides less connectivity
than a parallel channel
Example
An ESCON channel attached directly to an ESCON
interface in the DASD Control Unit
Topology - ESCON Point to Point
ESCON CU
S/390
ESCON Link
ESCON Channel in CNC mode
Chapter 6. ESCON and FICON (FCV) Topology 71
6.2 Switched Point-to-Point
The ESCON Director provides attachment and dynamic switching for ESCON
channels and control units using switched point-to-point topology.
When an ESCON channel or control unit sends a request, the ESCON Director:
Reads the address header in the ESCON frame and determines the
destination for the information
Transfers the information (in both directions)
Reads the trailers, breaks the physical connection (if specified) and waits for
the next communication
The ESCON Director can make and unmake multiple switch connections millions
of times per second.
Dynamic connections established between
ESCON Director ports during an I/O operation
Connection is established only for the duration
of command and data transfer
One ESCON (or FICON) channel port may dynamically
connect to any of the allowed ESCON Control Unit
ports
One ESCON Control Unit port may dynamically
connect back to any of the allowed ESCON or FICON
channel ports
Example
ESCON CNC Channel attached to Port 04
ESCON Control Units attached to Ports 05 and 06
Ports that are required to be dynamically connected
must NOT be:
Blocked
Connected (cannot use connect for FICON)
Prohibited from each other
Topology - Switched Point to Point
04
05 06
ESCON CU
9032-5
S/390
ESCON CU
6.3 ESCON Dedicated Connection (Static Connection)
The ESCON Director provides dedicated static port connectivity to support the
9034 ESCON converter and for the chaining of ESCON Directors. Both of these
situations require the use of dedicated connections.
When a dedicated connection exists between two ESCON ports, those two
ESCON ports in the 9032-5 are able to communicate only through each other.
If a dedicated connection is used other than for support of a converter or
chaining, the result is a version of ESCON point-to-point topology.
Dedicated or Static connection defined in
the ESCON Director matrix
Cannot use with FICON Bridge ports
Connected ESCON ports are only able to
communicate with each other
Dedicated connections are required when
9034 ESCON Converter paths are used
Example
ESCON CVC Channel attached to ESCON Port 04
Control Unit converter attached to ESCON Port 05
Statically connected ports must be
Connected
Not Blocked
Allow/Prohibit attributes are ignored
A dedicated connection is required in one
Director, when chaining Directors
Topology - Dedicated
04
05 06
Converter
ESCON CU Parallel CU
9032-5
S/390
6.4 Chained Directors
Director chaining refers to creating a connection between channel and control
unit that passes through (a supported maximum of) two ESCON Directors. The
only purpose of chaining this way is for the support of extended distances. The
maximum distance supported for a serial CTC connection between two
processors connected this way is 26 km.
In a chained configuration only one of the connections through the ESCON
Directors can be dynamic. The ESCON director providing dynamic connection
can be at either the channel end or the control unit end of the ESCON path. In
most configurations, using the dynamic connection in the Director at the control
unit end of the ESCON path (the director which the control unit connects to)
provides better connectivity. The dynamic and static connections that make the
chain are set up in the same way in the ESCON directors as any non-chained
dynamic and static connection.
A chained connection is one which goes through
2 ESCON Directors
Only one of the ESCON Director connections can
be dynamic
A dynamic ESCON connection may be made
through either switch, but MUST be the 1st
switch when the FICON Bridge is in the path
Chaining may be used to achieve greater
distances
Example
CNC Channel attached to SW1 ESCON Port 04
Control Units attached to SW2 ESCON Ports 05 and 06
SW1 ESCON Port 10 physically attached to SW2 Port 21
Static/Dedicated connection through SW1
Dynamic connections through SW2
All standard port attributes apply
Topology - Chained Directors
04
05
06
21
10
SW1 SW2
ESCON CU
9032-5
S/390
9032-5
ESCON CU
6.5 FICON (FCV) Connections - One Bridge Card Shown
The 9032-5 will support the installation of up to 16 FICON bridge cards. Each of
the FICON Bridge cards support 1 FICON port. A single FICON bridge port can
be used to establish up to 8 concurrent dynamic connections to any 8 different
ESCON ports in the same 9032-5 ESCON Director.
There can be up to a total maximum of 120 connections if there were 16 FICON
bridge cards installed in the 9032-5 ESCON director. This is a physical limitation
since, with 16 FICON bridge adapters installed in the 9032-5, there is only room
left to support 15 ESCON port cards, and each ESCON port card supports 8
ESCON ports, therefore 15 x 8 ESCON ports allows up to 120 connections.
A dedicated connection cannot be defined between the FICON Bridge card port
and any other port (FICON port or ESCON port) in the 9032-5 ESCON Director.
Connections from the FICON Bridge card port are always dynamic and to an
ESCON port. The connected to outgoing ESCON port can go to:
An ESCON-interfaced control unit
An ESCON CTC channel
Another ESCON director that is providing a static connection for this ESCON
path to an ESCON CU or an ESCON CTC channel
The FICON Bridge topology is always Switched Point-to-Point.
S/390 FICON channels in FCV mode operating with the
9032-5 FICON Bridge will support up to 8 concurrent I/O
operations
Topology - FICON (FCV) Connections
C4
FICON
Link
FICON
Bridge
9032-5
ESCON Links
S/390
ESCON CUs
ESCON CUs
FICON
Channel
FCV mode
6.6 ESCON and FICON - Valid and Invalid Topologies
This diagram shows which connections provide valid and invalid topologies.
ESCON can be point-to-point or switched point-to-point.
For an ESCON switched point-to-point connection there can only be one
dynamic switch in the ESCON path.
An ESCON CNC channel must connect to a ESCON port.
FICON (FCV) can only be switched point-to-point.
There can only be one dynamic switch in the channel to CU path.
The FICON (FCV) channel must connect to an FICON Bridge port.
Topology - Valid and Invalid
S/390 Processor
CNC CNC CNC FCV FCV FCV
CU CU CU CU CU CU
CNC CNC CNC FCV
CU CU CU CU
Point-to-
Point
ESCON
Director
Switched Point-to-Point
ESCON
Director
ESCON
Director
ESCON
Director
ESCON
Director
ESCON
Director
ESCON
Director
ESCON
Director
ESCON
Director
FICON
Bridge
ESCON Interfaces
Switched Point-to-Point
6.7 Connectivity Hierarchy
This diagram shows the hierarchy that applies when more than one connectivity
attribute has been applied to an ESCON port.
It is important for the ESCON Director user to understand this hierarchy. A lack of
understanding in this area can lead to misinterpretation of status information and
lengthy delays in problem determination, for example when a control unit runs out
of logical paths and you are trying to determine where the logical paths have
been established from.
In some cases an any-to-any matrix connection setup is nice (it provides freedom
to the system programmer) and in other cases it may lengthen the problem
determination time.
For FICON Bridge ports you cannot define a static connection from the FICON
port to any other port (FICON or ESCON).
Connectivity Hierarchy
Assigning more than one level of
connectivity control (attribute) to a
port creates this hierarchy
Is the port blocked?
If 'Yes' then Block is the overriding attribute
If not, is the connection between this
ESCON port and another dedicated?
If 'Yes' then Connect is the overriding
attribute
If not, is this port prohibited from
connecting with another port?
If 'Yes' then Prohibit is the overriding
attribute
If none of these apply then Allow is
honored
BLOCK
CONNECT
PROHIBIT
ALLOW
6.8 Port Attributes - Matrix Display
This diagram shows a portion of the active matrix window for a 9032-5. The
ESCON Director Console Application is operating in graphics mode.
Arrows point to examples of blocked and connected ports. These attributes are
shown in the Con column as well as by indicators in the matrix.
Examples of Prohibited and Allowed connections are also indicated by arrows.
These attributes have no effect if any other status is present in the Con column.
None of the connectivity attributes have any effect if there is an out-of-line status
displayed in the Hdwr column.
Port Attributes - Matrix Display
Prohibit
B
l
o
c
k
C
o
n
n
e
c
t
Allow
6.9 LED and XDF Links
This diagram shows the main differences between LED and XDF links.
LED links are also referred to as multi-mode links. They are supported by
62.5/125 micron fiber cables (for 3 km) or 50/125 micron fiber cables (for 2 km).
The first number refers to the diameter of the actual fiber and the second number
refers to the outer diameter of the fiber cladding. The fiber cable to support an
LED link is orange and the IBM duplex connectors are black.
XDF links are also referred to as single mode or laser links. They are supported
by 9/125 micron fiber. The fiber cable used to support XDF links is bright yellow in
color and may have either grey IBM duplex connectors or FCS connectors. The
9032-5 supports only FCS connectors.
The diagram shows the maximum supported distance (un-repeated) for CTC
communication between two processors, using two directors and using XDF links.
The supported distance for control units is dependent on the characteristics of
the CU, therefore refer to each control units characteristics manual or
specification manual. IBM control units do not support XDF interfaces.
LED and XDF Links
ESCON LED Multimode links
Maximum distance of 3 km using 62.5/125 micron MM fiber
Maximum distance of 2 km using 50/125 micron MM fiber
Support all topologies
ESCON XDF Single Mode Laser links
Support a maximum distance of 20 km using 9 micron SM fiber
Maximum distance for serial CTC, with chaining, is 60 km using repeaters
Maximum distance of many other control units, with chaining, is 43 km.
This distance is control unit dependent
Support all topologies
3 km 20 km 3 km
CNC CTC
ESCD ESCD
S/390 S/390
LED Link XDF Link LED Link
6.10 ESCON CNC to CU Configuration
This diagram shows a normal ESCON channel to ESCON CU connection using
paths through ESCON directors.
All the channel paths are ESCON, all the ESCON Director ports being used are
ESCON ports and the control unit interfaces are ESCON.
The distance for each ESCON link is 3 km and all the fiber cables shown are
62.5/125 multi-mode fiber, or if 50.0/125 fiber cables were used the supported
distances would be 2 km for each ESCON link.
ESCON CNC to CU Configuration
S/390 PROCESSOR
CNC
CNC
EMIF
LP1
LP2
LP3
SWITCH
02
SWITCH
01
MM
MM
MM
MM
CNC
CNC
Cable types
MM = Multi-mode
3 km 3 km
CU
CU
Cable types
MM = Multi-mode
MM
MM
MM
MM
6.11 FICON (FCV) Configuration
This diagram shows a FICON (FCV) channel to ESCON CU connection using
paths through ESCON directors that have FICON Bridge cards installed.
The channels are FICON in FCV mode and they are connected to the 9032-5
FICON Bridge cards. ESCON director ports are then used to connect to the
control unit ESCON interfaces.
The distance for each FICON (FCV) link is 10 km and requires single mode 9/125
fiber cables be used. An IBM RPQ can be requested to determine if a 20 km
distance can be supported by the FICON (FCV) link.
The distance for each of the ESCON links is 3 km and all the fiber cables shown
for the ESCN links are 62.5/125 multi-mode. If 50.0/125 fiber cables were used
the supported distances would be 2 km for each ESCON link.
FICON (FCV) Configuration
S/390 PROCESSOR
FCV
FCV
EMIF
LP1
LP2
LP3
SWITCH
02
SWITCH
01
SM
SM
SM
SM
Cable types
SM = Single mode
MM
MM
MM
MM
FCV
FCV
FICON
BRIDGE
Cable types
MM = Multi-mode
10 km
(20 km RPQ)
3 km
CU
CU
FICON
BRIDGE
FICON
BRIDGE
FICON
BRIDGE
6.12 ESCON (CNC) and FICON (FCV) Intermix
This diagram shows a FICON (FCV) channel to an ESCON CU connection using
paths through ESCON Directors that have FICON Bridge cards installed, and also
ESCON channels to ESCON CUs using ESCON ports. This is referred to as an
intermixed channel path configuration. All the channel paths are from the same
S/390 image to the same CU image. This is a supported configuration.
Some of the channels are FICON in FCV mode and they are connected to the
9032-5 FICON Bridge cards. ESCON director ports are then used to connect to
the control unit ESCON interfaces.
Some of the channels are ESCON, all the ESCON director ports being used for
these paths are ESCON ports, and the control unit interfaces are ESCON.
The distance for each FICON (FCV) link is 10 km and requires single mode 9/125
fiber cables be used. An IBM RPQ can be requested to determine if a 20 km
distance can be supported by the FICON (FCV) link.
The distance for each ESCON link is 3 km and all the fiber cables shown for the
ESCON links are 62.5/125 multi-mode. If 50.0/125 fiber cables were used the
supported distances would be 2 km for each ESCON link.
ESCON (CNC) and FICON (FCV) Configuration
S/390 PROCESSOR
FCV
CNC
EMIF
LP1
LP2
LP3
SWITCH
02
SWITCH
01
MM
SM
SM
MM
Cable types
SM = Single mode
MM= Multi-mode
MM
MM
MM
MM
FCV
CNC
Cable types
MM = Multi-mode
3 km
CU
CU
FICON
BRIDGE
FICON
BRIDGE
6.13 FICON (FCV) MCP Cables
IBMs direction is to provide S/390 channel connections that will increasingly
require the use of single mode 9 micron fiber cables. The new FICON channel
requires the use of 9 micron fiber cables. However with the use of Mode
Conditioner Patch cables it is possible for the customer to re-use already installed
62.5 micron or 50.0 micron fiber cables in the FICON (FCV) to FICON Bridge link.
Mode conditioner patch cables allow the transit of a FICON channel ports LASER
signal from a single mode fibre to a multi-mode fibre. The details of the MCP
construction are shown in the next diagram.
Two mode conditioner patch cables are required for the FICON (FCV) channel
link, one at each end of the link.
When MCP cables are used in the FICON channel link the distance is reduced
from 10 km to 550 meters.
It is recommended that the required MCP cables be ordered against the S/390
processor. The feature codes are:
Feature code 0106 - for a 62.5 micron MCP cable
Feature code 0103 - for a 50.0 micron MCP cable
FICON (FCV) Configuration and MCP Cables
FD
FCV
F8
FCV
A0
CNC
94
CNC
EMIF
LP1
LP2
LP3
SWITCH
02
C4
A3 B3
83
B3
A3 C4
83
SWITCH
01
Mode Conditioner
Patch cable
Mode Conditioner
Patch cable
Existing
62.5 um MM fiber
S/390
PROCESSOR
B
A
MC
MC
MM
A
B
IBM FC 0106 62.5 um
Note: Mode Conditioner Patch cable feature
code ordered must match the customers
installed fiber (fiber re-use)
550 meter
IBM FC 0106 62.5um
T
R
T
R
CU
CU
Fiber
twist
6.14 Mode Conditioner Patch (MCP) Cables
The single to multi-mode Mode Condition Patch cable construction permits the
transit of a LASER signal from a single mode fibre to a multi-mode fibre.
Mode Conditioner Patch (MCP) Cables
OFFSET FIBER FERRULES
TX RCV
Mode Conditioner
Patch cable
Mode Conditioner
Patch cable
Existing
62.5um MM Fiber
FICON
(Channel)
Single-mode fiber
Multi-mode fiber
550 meters maximum cabling distance
Mode Conditioning Patch cables for re-using ESCON Multi-mode fiber
2 Meters 2 Meters
IBM FC0106 62.5 um IBM FC0106 62.5 um
Cladding 125 um
Core 62.5 um
Core
9 um
Core
62.5 um
FICON
(Bridge)
Fiber cable internal
twist to connect
transmit FOSA to
receive FOSA
Light collecting lens
permits MM-to-SM
transition at FOSA
TX
RCV
FOSA
TX
RCV
FOSA
6.15 MCP Cables Invalid Use
A Mode Conditioning Patch cable must plug directly into the S/390 FICON
channel FOSA at the channel end and another mode conditioner patch cable
must plug directly into the FICON Bridge FOSA at the 9032-5 FICON Bridge end.
Single mode or multi-mode fiber cables must not be installed between the MCP
cables and either the FICON channel of FICON Bridge FOSA.
MCP Cables - Invalid Use and Connection
Mode Conditioner
Patch cable
Mode Conditioner
Patch cable
Existing
62.5 um MM Fiber
FICON
(Channel)
FICON
(Bridge)
The Mode Conditioner Patch cables must plug directly
into the Channel and Bridge FOSA
SM or MM jumper cables must not be installed between
the Mode Conditioner Patch cables and the FICON
channel FOSA or the FICON Bridge FOSA
Single Mode
Jumper Cable
Multi-Mode
Jumper Cable
TX
RCV
FOSA
TX
RCV
FOSA
No transition SM-to-MM
ferrule offset
No light collecting lens
for MM-to-SM transition
No light collecting lens
for MM-to-SM transition
Chapter 7. Error recovery and Reporting
In this chapter error reporting, recovery and problem determination for the 9032-5
are discussed.
IBM 9032 Model 5
ESCON Director
Recovery
7.1 Error Reporting and Recovery
A system operator will become aware of a problem associated with an ESCON
Director as the result of messages issued at the operating system console. There
is no requirement for an operator to monitor the ESCON Director console.
The ESCON Director generates sense data and sends it to one of the attached
operating systems. The data is sent over a channel path associated with the
ESCON Director Control Unit Port (CUP). This means that the channel path in
question has established a logical path to the CUP. The error data could be sent
to any operating system with a logical path established to the Director. The
operating system is responsible for interpreting the data and issuing the
appropriate messages at the operating system console.
The ESCON Director Console Application also maintains error information in
event logs at the console. The available logs are:
Director Event Log - for hardware and software incidents
Director LIN Log - for ESCON Link Incidents
Director Audit Log - for console operator activities
If the ESCD Console Application is not communicating with the ESCON Director
at the time of an event, the log data may be lost.
A subset of a record in the Director Event Log may be displayed at the operator
console. Only incidents associated with Director internal components are logged
in the operator panel.
Error Reporting and Recovery
The 9032-5 reports failures caused by both internal and
external components
Error messages are presented at the Operating System
console
No requirement to monitor the ESCON Director console
Error data is also logged in:
The ESCD Console if it is available
The ESCD Operator Panel (hardware failures only)
Token Ring
Operating
System
Console
Fiber Cable
ESCD Console
ESCD
Broken
Fiber
Chapter 7. Error recovery and Reporting 87
The diagram shows the flow of error data when a failure is detected by the
ESCON Director. The error information is sent to an operating system via an
ESCON link and to the console via the token-ring LAN. The system posts the
appropriate error message on the operating system console.
7.2 ESCON Director Component Failure
This diagram describes the actions that occur when the ESCON Director detects
a failure in an internal component.
The screen shows the error messages that are posted on the operating system
console.
The IOS000I message is the standard equipment check message associated with
hardware failures.
The IRD000E message is unique to ESCON Director error reporting. This
message shows the potential failing component(s) as well as an indication of the
operational status of the Director. This message is discussed in more detail in the
next diagram.
ESCD Component Failures
When a failure occurs in an ESCON Director component
The 9032 attempts to recover from the error
For example, by switching function to a redundant component
Sense data is sent to an operating system
An entry in created in the console's Director Event Log
A report is generated in the ESCD operator panel
The system error indicator on the operator panel is turned on
The operating system logs the error in Logrec, interprets
the sense data and issues the following message #s:
IOS000I 001F,9B,EQC,**,8200,,,*MASTER*, 533
1000E0000000000404002400000000000000000000000201000000270000700
*IRD000E 001F,9032-05 LEVEL=2 FRU(S)=FAN LIC=04.00 SPARE PORTS AVAILABLE
Message IOS000I displays the sense data describing the error
Message IRD000E summarizes the failing component/s and the
status of the switch
7.3 IRD000E Fields
This diagram details the fields displayed in the IRD000E message.
The Level field gives an indication of the operational status of the Director and
hence, the severity of the failure.
The FRU (Field Replaceable Unit) field indicates the component(s) that are most
likely to be the cause of the failure.
If a failure occurs in a component which has redundancy, the ESCON Director will
automatically switch the function of the failing component to the redundant
hardware.
If a port failure occurs, the switch to the spare ports card (if installed) cannot take
place without operator intervention. The IRD000E message prompts the operator
if spare ports are available so that appropriate action can be taken if a port failure
has occurred.
IRD000E Fields
Device number, machine type and model number are
displayed at the start of the message
Level field indicates the operational status of the ESCD
0 Dynamic switch is fully operational
1 A component failed, but redundant hardware makes the
dynamic switch fully operational
2 Dynamic switch is operational; a minor failure has occurred
3 Dynamic switch is operational; a major failure has occurred
4 Dynamic switch is not operational, and is not available to any
system
5 Dynamic switch's operational level is indeterminate
FRU indicates the Field Replaceable Unit that has failed
LIC indicates the currently active LIC level
Spare Ports Available
Spare port feature is installed and there is at least one spare port
available
7.4 Director Event Log
This is a display of the Director Event Log from the ESCD console. The
highlighted entry is the record that corresponds to the error reported on the
operating system console in the previous example.
Director Event Log
7.5 Failures External to the ESCON Director
The term "Failures external to the ESCON Director" refers to failures which occur
on the links attached to the ESCON Director.
The detection and reporting of these failures are very similar to the detection and
reporting of internal ESCON Director failures. The main differences are that the
errors are recorded in the Director LIN log rather than the Director Event Log, and
the error record is not posted on the operator panel.
An example of the error messages that are generated as a result of a link failure
is shown in the preceding diagram. The message in the shaded area is the
message that was generated from data provided by the ESCON Director. The first
message is the processor's report of the same failure.
The information provided in these messages is the node descriptor for the
component at each end of the failing link. The node descriptor is a unique
identifier associated with the ESCON adapter. In the case of an ESCON Director,
the node descriptor includes the machine type, model, serial number and port
number. The port number appears in the IF field. The same field is used to show
the CHPID number in the node descriptor for a processor.
In the past there was some inconsistency in the reporting of the interface field in
IOS581E messages. Sometimes the port address was reported and sometimes
the physical port number was reported. This was dependent on the initiator of the
link failure report. Each ESCD port has both a port address and a physical port
number and these may not necessarily be the same. The physical port number is
Failures External to the ESCD
External failures may be detected by the ESCD as failures
on its attached links
When the ESCD detects an error on one of its links:
An operating system is notified via a channel connected port
(ESCON or FICON Bridge) that has established a path to the CUP
The operating system creates a Logrec record and posts a message
on the operating system console
An entry is recorded in the ESCD Console Link Incident Log
IOS581E LINK FAILED REPORTING CHPID=9B 034
INCIDENT UNIT TM=009672/R75 SER=IBM02-046198 IF=009B IC=03
ATTACHED UNIT TM=009032/005 SER=IBM02-040000 IF=0048
ATTACHED UNIT LIF=4C
IOS581E LINK FAILED REPORTING CHPID=9B 124
INCIDENT UNIT TM=009032/005 SER=IBM02-040000 IF=0048 IC=03
INCIDENT UNIT LIF=4C
normally used only by the service representative. This inconsistency led to
confusion and lengthy problem determination.
This problem has been resolved for the 9032-5. There is a new field in the
IOS581E message, LIF, that shows the port address associated with the failing
link.
7.6 Director LIN Log
This is a display of the Director LIN Log from the ESCON Director Console
Application.
The highlighted record corresponds to the link incident example on the previous
diagram. The physical port number is shown in the first column and the port
address is shown in the second column.
Director LIN Log
7.7 Link Problem Determination
The ESCON Director Console Application provides some very useful problem
determination information.
The status of each port can be easily determined from the active matrix window.
This diagram shows the possible entries in the port hardware status field. The
first column shows the entries with graphics off and the second shows the entries
with graphics on. This information is dynamically refreshed as changes to port
status occur.
If a port status other than "Installed and Fully Operational" is displayed in the
hardware column, then all connectivity attributes are overridden by that status.
Link Problem Determination
The 9032-5 ESCD Console Application can provide
useful information for port problem determination
Port Status is shown in the Hdwr Column
Operator cannot directly change the status displayed in the Hdwr
column
Possible values are:
N or Notinst - Port is not Installed
M or Maint - Port is in maintenance mode
S or Service - Service is required
A or Invalid - Invalid Connection Attachment
L or Lnkfail - Link failure has occurred
O or Offline - Port is offline
(Blank) - Port is installed and fully operational
Status in the Hdwr column overrides all other
connectivity attributes for the port
7.8 Port Status Display with Graphics Off
This diagram shows the Active Matrix window with graphics off. The H column
shows a variety of status conditions.
The messages area in the status bar at the bottom of the window displays "The
hardware status field was updated" to indicate that the hardware status for at
least one port has changed since the active matrix window was opened.
Port Status - Graphics Off
The hardware status field was updated
7.9 Port Status Display with Graphics On
This diagram shows the Active Matrix window with graphics on. The Hdwr
column shows a variety of status conditions.
Once again, the hardware status for at least one port has been updated since the
active matrix window was opened, so the message "The hardware status field
was updated" is displayed in the status bar.
Port Status - Graphics On
The hardware status field was updated
7.10 ESCON Manager Port Status
As previously discussed, port status information that can be viewed from the
ESCD console can also be displayed at the host using System Automation for
OS/390 (SA/MVS) or ESCON Manager. The port status information is retrieved
from the ESCON Director at the time the command is entered. If the port status
information is viewed from the active matrix, then the information is retrieved with
the active matrix. The characters displayed in the port status columns are the
same as those displayed at the active matrix window with graphics off.
The display at the bottom of the diagram shows the ESCON Manager response to
a DISPLAY PORT command. The port displayed is port 12 and the status is the
same as the status that was displayed in the previous examples.
ESCM Port Status Display
Port status information can be displayed using SA/MVS
or ESCON Manager from any of the supported
interfaces
Port status information is retrieved from the ESCON
Director at the time the command is entered or the
active matrix is displayed
Displays the same characters as the ESCON Director
Console Application with Graphics Off
IHVR011I DISPLAY PORT (12) 001F
IHVR021I DISPLAY COMMAND SUCCESSFUL. RC 0, REASON CODE 40000004
IHVC999I ESCON MANAGER DISPLAY 250
IHVC844I PORT
IHVC845I SWCH STATUS I/O
IHVC846I PORT NAME DEVN LSN PORT H B C P DEF
IHVC847I 001F AF 12 M B P
7.11 ESCON Manager Device View - Console or ISPF
This diagram shows the output from an ESCON Manager DISPLAY DEVICE
command. The display shows how each of the paths to device 0CC0 are routed
through the ESCON Director.
This information is always reliable because ESCON Manager collects the
information from the ESCON Directors and the channel subsystem at the time the
command is entered. This is a far more effective method of determining device
configuration than relying on configuration diagrams, which are subject to human
error.
In order to gain a full understanding of the configuration for a shared device, it is
necessary to issue this command from each of the sharing systems.
This command is not only useful for determining the configuration of a device, but
is also a useful problem determination tool because it provides information about
the status of the components along each path to the device.
ESCM Device View - Console or ISPF
F IHV,D D 0CC0 *
IHVR010I ESCM COMMAND ENTERED BY SYS OPER ON SC53IHV
IHVR011I DISPLAY DEV 0CC0 *
IHVR021I DISPLAY COMMAND SUCCESSFUL. RC 0, REASON CODE 40000004
IHVC999I ESCON MANAGER DISPLAY 909
IHVC824I PORT
IHVC825I CHP SWCH STATUS
IHVC826I DEVN CHP TYPE DEVN LSN PORT H B C P PORT NAME
IHVC827I 0CC0 10 CNC_S 001A AA C9 9674_RY4_P401_CHPID_10
IHVC82AI CNTL UNIT DATA:001A AA E4 TO_3990WB0_'A'
IHVC827I 84 CNC_S 001B AB C5 9672_RY4-P401_CHPID_84
IHVC82AI CNTL UNIT DATA:001B AB E4 TO_3990WB1_'E'
IHVC827I A8 CNC_S 001C AC CF 9672_RY4_P401_CHPID_A8
IHVC82AI CNTL UNIT DATA:001C AC E4 TO_3990WB0_'B'
IHVC827I DC CNC_S 001D AD DA 9672_RY4_P401_CHPID_DC
IHVC82AI CNTL UNIT DATA:001D AD E4 TO_3990WB1_'B'
IHVO000I ESCM IS READY TO PROCESS OPERATOR COMMANDS
ESCON Manager provides a system view of device
connectivity, showing path routing information, from
the operating system console or ISPF interface
7.12 ESCON Manager Workstation Device Selection
The information available from the ESCON Manager DISPLAY DEVICE command
can be displayed in a graphical format at the ESCON Manager workstation. The
information can be displayed simply by selecting the Find option and entering the
device number of the device you wish to display. There is no requirement to
remember commands or how to interpret their output.
This diagram shows the Find window with an entry to display the configuration
and status of device number A80.
ESCM Workstation Device Selection
Device view can be displayed at the ESCM workstation
simply by selecting the device to find
SC53
7.13 ESCON Manager Workstation - Device Display
This diagram shows ESCON Manager's view of a device from the ESCON
Manager workstation.
This is the device view for device number A80, the device that was targeted for
Find in the previous diagram.
This display provides all of the information in the previous ESCON Manager
command output, but it is in a graphic display that is easy to understand even if
you are not familiar with ESCON Manager. Different colors are used to indicate
various status conditions for each of the components in the paths to the device.
The other advantage of the workstation is that it provides a multi-system view of
the device. Details and status are shown only for the Focus host, but the display
provides the operator with an awareness that other systems have connectivity to
the device. In order to see the details and status from another system's
perspective, the operator simply changes the focus to a different host.
ESCM Workstation Device Display
ESCON Manager workstation provides a multi-system
device view showing path routing information
SCPLEX
SC53
Systems
Control Unit Ports
ESCON Directors
Channel Ports
Chpids
Devices
Control Units
7.14 Node Descriptor
All components that connect to an ESCON interface must be self-describing. The
data that a component uses to describe itself is known as its node descriptor and
this data must be unique to that component.
When an ESCON adapter detects light, it attempts to initialize the link with
whatever is at the other end. Part of this initialization process is the exchange of
node descriptors.
Because there is always activity on an ESCON link, both ends of the link are
always aware of any change in the status of the link. In other words, nothing can
happen to the link without the components at either end having an awareness. If
the link is disturbed, the initialized status will be lost and if the link is reinstated,
the initialization process will be repeated. This means node descriptor information
is always up to date and accurate.
Node descriptor information can be displayed at the ESCON Director console.
Other products which support the display of node descriptor information are
S/390 Servers and ES/9000 Processors through the I/O Problem Determination
Facility. This information can also be retrieved from many control units.
ESCON Manager also supports the display of node descriptor information using
the ESCON Manager workstation.
Node Descriptor
The node descriptor is a unique identifier describing a
component attached to an ESCON link
Node descriptor information
Is gathered at ESCON link initialization time
Can be displayed at the ESCD Console
Can be displayed at the HMC
Can be displayed at the ESCON Manager workstation
Cannot be displayed at the operating system console
When a link is no longer initialized, the node descriptor
data becomes "not current"
Node descriptors are very useful for problem
determination because they tell you exactly who is, or
was, at the other end of a fiber cable
7.15 ESCON Director Node Descriptor Display (1)
This diagram shows ESCON Director Node Descriptor windows for two different
port addresses.
In the first case the link is operational and valid, so current node descriptor
information is displayed. In this case, port address 04 is attached to CHPID 9B of
a 9672 Model RY4 with serial number 45200.
In the second case, the validity of the node descriptor information is Valid, but
not current. This indicates that the subject port was previously attached to the
component described by this node descriptor, but the link is no longer initialized.
In this case, port address 0B was attached to CHPID 93 of a 9672 Model R75
with serial number 46198.
ESCD Node Descriptor Display (1)
7.16 ESCM Workstation Node Descriptor Display (2)
This diagram shows the node descriptor display generated by the ESCON
Manager workstation. All of the information available from the ESCON Director
Console Application's node descriptor display, including a validity indicator, is
available from ESCON Manager. The advantage of using ESCON Manager to
provide node descriptor information is that it has a view of the entire ESCON
environment. It can provide node descriptor information for any component in the
environment. In contrast, ESCON Directors, processors and control units can
only provide node descriptor information for directly attached components. For
example, a processor cannot provide the node descriptor information for a control
unit attached via a dynamic switch. It can only provide node descriptor
information for the component at the end of the link, in this case, the ESCON
Director.
ESCD Node Descriptor Display (2)
Chapter 8. Migration to the 9032-5
There may be many cases where a 9032-5, because of its increased capacity, is
used as a replacement for an earlier model ESCON Director. This chapter
describes some factors which should be considered when migrating to a 9032-5
from an earlier model ESCON Director.
IBM 9032 Model 5
ESCON Director
Migration
8.1 Migration Considerations
Although a 9032-5 can be used as a replacement for a 9032-3 or other models,
there are a number of differences which must be considered. Preparation and
planning before the migration will ensure a successful 9032-5 implementation.
Consoles
The ESCON Director Console used by the 9033-1 and the 9032-2 uses a different
interface and platform from the 9032-5 console PC. This console cannot be used
for the 9032-5. The 9032-3 and 9033-4 use the same console interface and a
similar console application to the 9032-5. The hardware requirements for the
9032-5 console, however, are not likely to be met by existing ESCON Director
consoles. 9032-5, 9032-3 and 9033-4 can share a console but that console must
meet the minimum requirements for the 9032-5. Hardware and software
requirements for 9032-5 consoles are discussed in Chapter 3, 9032-5 Console
on page 37. There is a migration procedure to transfer matrix configuration files
and other installation specific data from a 9032-3 or 9033-4 to the 9032-5.
Cabling
The amount of fiber cable required for cable routing internal to the 9032-5 is
greater than that required for any previous model of ESCON Director. Where the
9032-5 replaces a previous ESCON Director model, the existing fiber cables are
likely to be too short. This may necessitate repositioning the 9032-5 to a location
closer to the cable source or even replacement of existing cables.
Console
Existing 9032-3 or 9033-4 console is unlikely to meet the
requirements for the 9032-5
9032-3 matrix configurations and other installation-specific data can
be migrated for use on the 9032-5
Cabling
Existing fiber cables for any previous model ESCDs are likely to
be too short for use with the 9032-5
Port Addressing
The port address ranges differ across 9032/9033 models
If new port address are not the same as old port addresses
definition changes will be required
Configure for availability across quadrants and port cards
Migration Considerations
Chapter 8. Migration to the 9032-5 105
Configuration
The internal configuration of the 9032-5 is significantly different from the internal
configurations of previous ESCON Director models.
The 9032-5 is the only model with eight ports per card. All of the previous models
have four ports per card. A configuration designed for a Director with four ports
per card may not be suitable for a Director with eight ports per card. In order to
maximize availability in the event of a port card failure, connections from the
same system or from the same control unit should be attached to different port
cards.
Connections to the same system or control unit should also be spread across
different quadrants. Port addresses that were supported by different quadrants in
the 9032-3 may be part of the same quadrant in the 9032-5.
If you decide you want the 9032-5 to match an existing 9032-2 or 9032-3
configuration you can ensure that the port address on the 9032-5 will match your
existing configuration by ordering one of the migration feature codes. The feature
code for migrating from a 9032-2 is 5902 and the feature code for migrating from
a 9032-3 is 5903.
8.2 Port Address Support
.
This table shows the port address ranges available to each of the 9033 and 9032
models. If there is a plan to use an existing configuration on a new 9032-5 it is
necessary to ensure that the old port addresses exist on the new machine. This
may not be the case if the 9032-5 is not fully populated with port cards. If the port
Supported Address Ranges
Address Range 9033-1 9032-2 9032-3 9033-4 9032-5
04-0F
10-1F
20-2F
30-3F
40-4F
50-5F
60-6F
70-7F
80-8F
90-9F
A0-AF
B0-BF
C0-CF
D0-DF
E0-EF
F0-FB
addresses are different, then either port address or definition changes will be
required.
8.3 Port Address by Quadrant for the 9032-5 and 9032-3
These tables show the port addresses, by quadrant, used by the 9032-5 and the
9032-3. One of the previously mentioned availability considerations was that
connections to the same system or control unit should be attached to ports in
different quadrants. If this practice was followed for a 9032-3 and the
configuration is then migrated to a 9032-5, the requirement may no longer be
met. For example, a control unit may be attached to ports 80 and A0 in a 9032-3.
These ports are supported by different quadrants. When the configuration is
migrated to a 9032-5 these two ports will both be supported by Quadrant C.
9032-5 port addresses
Port Layout for 9032-3 and 9032-5
A Lower Right 04 - 43
B Lower Left 44 - 83
C Upper Right 84 - C3
D Upper Left C4 - FB
S1 - S4 (spare ports card)
A Lower Right 80 - 9F
B Lower Left A0 - BF
C Upper Right C0 - DF
D Upper Left E0 - FB
9032-3 port addresses
Chapter 8. Migration to the 9032-5 107
8.4 Port Card Layout for the 9032-5 and the 9032-3
This diagram shows the physical layout of port cards and quadrants in the 9032-5
and 9032-3. The arrows show the general direction of port address migration.
Migration from a 9032-3 to a 9032-5 is not quite as simple as the diagram may
suggest because the 9032-3 quadrants start on a "x0" boundary but the 9032-5
quadrants start on a "x4" boundary. This diagram also illustrates the requirement
for additional fiber cable length for internal routing in the 9032-5. The cables
plugged to ports in the upper quadrants are routed around the outer side edges to
the top of the frame and then down through strain relief into the port cards.
9032-3 to 9032-5 Port Migration
Quadrant
A
Quadrant
B
Quadrant
C
Quadrant
D
Quadrant
A
Quadrant
B
Quadrant
D
Quadrant
C
9032-5
9032-3
Appendix A. Special Notices
This publication is intended to help S/390 I/O configuration specialists to design,
configure and define a S/390 channel and I/O configuration that includes the IBM
9032-5 with ESCON and/or FICON (FCV) ports. The information in this
publication is not intended as the specification of any programming interfaces that
are provided by System Automation for OS/390. See the PUBLICATIONS section
of the IBM Programming Announcement for System Automation for OS/390 for
more information about what publications are considered to be product
documentation.
References in this publication to IBM products, programs or services do not imply
that IBM intends to make these available in all countries in which IBM operates.
Any reference to an IBM product, program, or service is not intended to state or
imply that only IBM's product, program, or service may be used. Any functionally
equivalent program that does not infringe any of IBM's intellectual property rights
may be used instead of the IBM product, program or service.
Information in this book was developed in conjunction with use of the equipment
specified, and is limited in application to those specific hardware and software
products and levels.
IBM may have patents or pending patent applications covering subject matter in
this document. The furnishing of this document does not give you any license to
these patents. You can send license inquiries, in writing, to the IBM Director of
Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact IBM Corporation, Dept.
600A, Mail Drop 1329, Somers, NY 10589 USA.
Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.
The information contained in this document has not been submitted to any formal
IBM test and is distributed AS IS. The use of this information or the
implementation of any of these techniques is a customer responsibility and
depends on the customer's ability to evaluate and integrate them into the
customer's operational environment. While each item may have been reviewed by
IBM for accuracy in a specific situation, there is no guarantee that the same or
similar results will be obtained elsewhere. Customers attempting to adapt these
techniques to their own environments do so at their own risk.
Any pointers in this publication to external Web sites are provided for
convenience only and do not in any manner serve as an endorsement of these
Web sites.
The following terms are trademarks of the International Business Machines
Corporation in the United States and/or other countries:
The following terms are trademarks of other companies:
C-bus is a trademark of Corollary, Inc. in the United States and/or other countries.
Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Sun Microsystems, Inc. in the United States and/or other countries.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States and/or other countries.
PC Direct is a trademark of Ziff Communications Company in the United States
and/or other countries and is used by IBM Corporation under license.
ActionMedia, LANDesk, MMX, Pentium and ProShare are trademarks of Intel
Corporation in the United States and/or other countries.
UNIX is a registered trademark in the United States and/or other countries
licensed exclusively through X/Open Company Limited.
SET and the SET logo are trademarks owned by SET Secure Electronic
Transaction LLC.
Other company, product, and service names may be trademarks or service marks
of others.
ACF/VTAM DFSMS
DFSMS/MVS Enterprise Systems Architecture/390
ES/9000 ESA/390
ESCON XDF ESCON
FICON IBM
MVS/ESA NetView
OS/2 OS/390
RMF S/370
S/390 S/390 Parallel Enterprise Server
Sysplex Timer System/360
System/370 System/390
S/390 Parallel Enterprise Server VM/ESA
VTAM
Appendix B. Related Publications
The publications listed in this section are considered particularly suitable for a
more detailed discussion of the topics covered in this redbook.
B.1 International Technical Support Organization Publications
For information on ordering these ITSO publications see How to Get ITSO
Redbooks on page 113.
FICON Introduction, SG24-5176
FICON Planning, SG24-5445
FICON Implementation, SG24-5169
B.2 Redbooks on CD-ROMs
Redbooks are also available on the following CD-ROMs. Click the CD-ROMs
button at http://www.redbooks.ibm.com/ for information about all the CD-ROMs
offered, updates and formats.
B.3 Other Publications
These publications are also relevant as further information sources:
FICON Physical Layer, SA24-7172
Planning for ESCON Links, GA23-0367
ESCON I/O Interface Physical Layer, SA23-0394
IBM Fiber Transport Services - Planning, GA22-7234
IOCP Users Guide, GC38-0401
HCD User's Guide, SC28-1848
IBM System/360, System/370, 4300, 9370 Processors Input/Output
Equipment Installation Manual - Physical Planning - GC22-7064.
HCD Planning, GC28-1750
HCM Users Guide, SC33-6595
HMC Operations Guide, GC38-0459
PR/SM Planning Guide, GA22-7236
CD-ROM Title Collection Kit
Number
System/390 Redbooks Collection SK2T-2177
Networking and Systems Management Redbooks Collection SK2T-6022
Transaction Processing and Data Management Redbooks Collection SK2T-8038
Lotus Redbooks Collection SK2T-8039
Tivoli Redbooks Collection SK2T-8044
AS/400 Redbooks Collection SK2T-2849
Netfinity Hardware and Software Redbooks Collection SK2T-8046
RS/6000 Redbooks Collection (BkMgr Format) SK2T-8040
RS/6000 Redbooks Collection (PDF Format) SK2T-8043
Application Development Redbooks Collection SK2T-8037
IBM Enterprise Storage and Systems Management Solutions SK3T-3694
IBM S/390 Parallel Enterprise Server - G5/G6 System Overview, GA22-7158
OS/390 System Commands, GC28-1781
S/360 - S/370 I/O Interface, GA22-6974
Coupling Links Physical Layer, SA23-0395
ESCON Reference Booklet (level 07), G326-0005 (available from VM at
MKTTOOLS)
How to Get ITSO Redbooks
This section explains how both customers and IBM employees can find out about ITSO redbooks, redpieces, and
CD-ROMs. A form for ordering books and CD-ROMs by fax or e-mail is also provided.
Redbooks Web Site http://www.redbooks.ibm.com/
Search for, view, download, or order hardcopy/CD-ROM redbooks from the redbooks Web site. Also read
redpieces and download additional materials (code samples or diskette/CD-ROM images) from this redbooks
site.
Redpieces are redbooks in progress; not all redbooks become redpieces and sometimes just a few chapters will
be published this way. The intent is to get the information out much quicker than the formal publishing process
allows.
E-mail Orders
Send orders by e-mail including information from the redbooks fax order form to:
Telephone Orders
Fax Orders
This information was current at the time of publication, but is continually subject to change. The latest information
may be found at the redbooks Web site.
In United States
Outside North America
e-mail address
usib6fpl@ibmmail.com
Contact information is in the How to Order section at this site:
http://www.elink.ibmlink.ibm.com/pbl/pbl
United States (toll free)
Canada (toll free)
1-800-879-2755
1-800-IBM-4YOU
Country coordinator phone number is in the How to Order section at
this site:
United States (toll free)
Canada
1-800-445-9269
1-403-267-4455
Fax phone number is in the How to Order section at this site:
IBM employees may register for information on workshops, residencies, and redbooks by accessing the IBM
Intranet Web site at http://w3.itso.ibm.com/ and clicking the ITSO Mailing List button. Look in the Materials
repository for workshops, presentations, papers, and Web pages developed and written by the ITSO technical
professionals; click the Additional Materials button. Employees may access MyNews at http://w3.ibm.com/ for
redbook, residency, and workshop announcements.
IBM Intranet for Employees
IBM Redbook Fax Order Form
Please send me the following:
We accept American Express, Diners, Eurocard, Master Card, and Visa. Payment by credit card not
available in all countries. Signature mandatory for credit card payment.
Title Order Number Quantity
First name Last name
Company
Address
City Postal code
Telephone number Telefax number VAT number
Invoice to customer number
Country
Credit card number
Credit card expiration date Signature Card issued to
Glossary
This glossary includes terms for the System/390
(S/390) channel, ESCON Director products, and the
FICON (FCV) environment.
A
active configuration. In an ESCON environment, the
ESCON Director configuration determined by the
status of the current set of connectivity attributes.
Contrast with saved configuration.
allowed. In an ESCON Director, the attribute that,
when set, establishes dynamic connectivity capability.
Contrast with prohibited.
American National Standards Institute (ANSI). An
organization consisting of producers, consumers, and
general interest groups, that establishes the
procedures by which accredited organizations create
and maintain voluntary industry standards in the
United States. (A)
ANSI. See American National Standards Institute.
APAR. See authorized program analysis report.
authorized program analysis report (APAR). A
report of a problem caused by a suspected defect in a
current, unaltered release of a program.
B
basic mode. A S/390 central processing mode that
does not use logical partitioning. Contrast with
logically partitioned (LPAR) mode.
blocked. In an ESCON Director, the attribute that,
when set, removes the communication capability of a
specific port. Contrast with unblocked.
C
CBY. Mnemonic for an ESCON channel attached to an
IBM 9034 convertor. The 9034 converts from ESCON
CBY signals to parallel channel interface (OEMI)
communication operating in byte multiplex mode (Bus
and Tag). Contrast with CVC.
chained. In an ESCON environment, pertaining to the
physical attachment of two ESCON Directors (ESCDs)
to each other.
channel. (1) A processor system element that controls
one channel path, whose mode of operation depends
on the type of hardware to which it is attached. In a
channel subsystem, each channel controls an I/O
interface between the channel control element and the
logically attached control units. (2) In the ESA/390
architecture, the part of a channel subsystem that
manages a single I/O interface between a channel
subsystem and a set of controllers (control units).
channel path (CHP). A single interface between a
central processor and one or more control units along
which signals and data can be sent to perform I/O
requests.
channel path identifier (CHPID). In a channel
subsystem, a value assigned to each installed channel
path of the system that uniquely identifies that path to
the system.
channel subsystem (CSS). Relieves the processor of
direct I/O communication tasks, and performs path
management functions. Uses a collection of
subchannels to direct a channel to control the flow of
information between I/O devices and main storage.
channel-attached. (1) Pertaining to attachment of
devices directly by data channels (I/O channels) to a
computer. (2) Pertaining to devices attached to a
controlling unit by cables rather than by
telecommunication lines.
CHPID. Channel path identifier.
cladding. In an optical cable, the region of low
refractive index surrounding the core. See also core
and optical fiber.
CNC. Mnemonic for an ESCON channel used to
communicate to an ESCON-capable device.
configuration matrix. In an ESCON environment, an
array of connectivity attributes that appear as rows and
columns on a display device and can be used to
determine or change active and saved configurations.
connected. In an ESCON Director, the attribute that,
when set, establishes a dedicated connection between
two ESCON ports. Contrast with disconnected.
connection. In an ESCON Director, an association
established between two ports that provides a physical
communication path between them.
connectivity attribute. In an ESCON Director, the
characteristic that determines a particular element of a
port's status. See allowed, blocked, connected,
disconnected, prohibited, and unblocked.
control unit. A hardware unit that controls the reading,
writing, or displaying of data at one or more
input/output units.
core. (1) In an optical cable, the central region of an
optical fiber through which light is transmitted. (E) (2)
In an optical cable, the central region of an optical fiber
that has an index of refraction greater than the
surrounding cladding material. See also cladding and
optical fiber.
coupler. In an ESCON environment, link hardware
used to join optical fiber connectors of the same type.
Contrast with adapter.
CTC. (1) Channel-to-channel. (2) Mnemonic for an
ESCON channel attached to another ESCON channel.
CVC. Mnemonic for an ESCON channel attached to an
IBM 9034 convertor. The 9034 converts from ESCON
CVC signals to parallel channel interface (OEMI)
communication operating in block multiplex mode (Bus
and Tag). Contrast with CBY.
D
DDM. See disk drive module.
dedicated connection. In an ESCON Director, a
connection between two ports that is not affected by
information contained in the transmission frames. This
connection, which restricts those ports from
communicating with any other port, can be established
or removed only as a result of actions performed by a
host control program or at the ESCD console. Contrast
with dynamic connection.
Note: The two links having a dedicated connection
appear as one continuous link.
default. Pertaining to an attribute, value, or option that
is assumed when none is explicitly specified.
destination. Any point or location, such as a node,
station, or a particular terminal, to which information is
to be sent.
device. A mechanical, electrical, or electronic
contrivance with a specific purpose.
device address. In the ESA/390 architecture, the field
of an ESCON device-level frame that selects a specific
device on a control-unit image.
device number. (1) In the ESA/390 architecture, a
four-hexidecimal-character identifier, for example
19A0, that you associate with a device to facilitate
communication between the program and the host
operator. (2) The device number that you associate
with a subchannel that uniquely identifies an I/O
device.
direct access storage device (DASD). A mass
storage medium on which a computer stores data.
disconnected. In an ESCON Director, the attribute
that, when set, removes a dedicated connection.
Contrast with connected.
disk drive module (DDM). A disk storage medium that
you use for any host data that is stored within a disk
subsystem.
distribution panel. (1) In an ESCON environment, a
panel that provides a central location for the
attachment of trunk and jumper cables and can be
mounted in a rack, wiring closet, or on a wall.
duplex. Pertaining to communication in which data or
control information can be sent and received at the
same time. Contrast with half duplex.
duplex connector. In an ESCON environment, an
optical fiber component that terminates both jumper
cable fibers in one housing and provides physical
keying for attachment to a duplex receptacle.
duplex receptacle. In an ESCON environment, a fixed
or stationary optical fiber component that provides a
keyed attachment method for a duplex connector.
dynamic connection. In an ESCON Director, a
connection between two ports, established or removed
by the ESCD and that, when active, appears as one
continuous link. The duration of the connection
depends on the protocol defined for the frames
transmitted through the ports and on the state of the
ports. Contrast with dedicated connection.
dynamic connectivity. In an ESCON Director, the
capability that allows connections to be established
and removed at any time.
Dynamic I/O Reconfiguration. A S/390 function that
allows I/O configuration changes to be made
non-disruptively to the current operating I/O
configuration.
E
EMIF. See ESCON Multiple Image Facility.
Enterprise Systems Architecture/390 (ESA/390). An
IBM architecture for mainframe computers and
peripherals. Processors that follow this architecture
include the S/390 Server family of processors.
Enterprise System Connection (ESCON). (1) An
ESA/390 computer peripheral interface. The I/O
interface uses ESA/390 logical protocols over a serial
interface that configures attached units to a
communication fabric. (2) A set of IBM products and
services that provide a dynamically connected
environment within an enterprise.
ESA/390. See Enterprise Systems Architecture/390.
ESCD. Enterprise Systems Connection (ESCON)
Director.
ESCD console. The ESCON Director display and
keyboard device used to perform operator and service
tasks at the ESCD.
ESCON. See Enterprise System Connection.
ESCON channel. A channel having an Enterprise
Systems Connection channel-to-control-unit I/O
interface that uses optical cables as a transmission
medium. May operate in CBY, CNC, CTC or CVC
mode. Contrast with parallel channel.
ESCON Director. An I/O interface switch that provides
the interconnection capability of multiple ESCON
interfaces (or FICON FCV (9032-5) in a distributed-star
topology.
ESCON Multiple Image Facility (EMIF). In the
ESA/390 architecture, a function that allows LPARs to
share an ESCON channel path (and other channel
types) by providing each LPAR with its own
channel-subsystem image.
F
117
FCS. See fibre channel standard.
fiber. See optical fiber.
fiber optic cable. See optical cable.
fiber optics. The branch of optical technology
concerned with the transmission of radiant power
through fibers made of transparent materials such as
glass, fused silica, and plastic. (E)
Note: Telecommunication applications of fiber optics
use optical fibers. Either a single discrete fiber or a
non spatially aligned fiber bundle can be used for each
information channel. Such fibers are often called
optical fibers to differentiate them from fibers used in
non communication applications.
fibre channel standard. An ANSI standard for a
computer peripheral interface. The I/O interface
defines a protocol for communication over a serial
interface that configures attached units to a
communication fabric. The protocol has four layers.
The lower of the four layers defines the physical media
and interface, the upper of the four layers defines one
or more logical protocols (for example, FCP for SCSI
command protocols and FC-SB-2 for FICON for
ESA/390). Refer to ANSI X3.230.1999x.
FICON. (1) An ESA/390 computer peripheral interface.
The I/O interface uses ESA/390 logical protocols over
a FICON serial interface that configures attached units
to a FICON communication fabric. (2) An FC4
proposed standard that defines an effective
mechanism for the export of the SBCON command
protocol via fibre channels.
field replaceable unit (FRU). An assembly that is
replaced in its entirety when any one of its required
components fails.
FRU. See field replaceable unit.
G
Giga bit. Usually used to refer to a data rate, the
number of Giga bits being transferred in one second.
H
half duplex. In data communication, pertaining to
transmission in only one direction at a time. Contrast
with duplex.
hard disk drive. (1) A storage media within a storage
server used to maintain information that the storage
server requires. (2) A mass storage medium for
computers that is typically available as a fixed disk or a
removable cartridge.
HDA. Head and disk assembly.
HDD. See hard disk drive.
head and disk assembly. The portion of an HDD
associated with the medium and the read/write head.
I
ID. See identifier.
Identifier. A unique name or address that identifies
things such as programs, devices or systems.
initial program load (IPL). (1) The initialization
procedure that causes an operating system to
commence operation. (2) The process by which a
configuration image is loaded into storage at the
beginning of a work day or after a system malfunction.
(3) The process of loading system programs and
preparing a system to run jobs.
input/output (I/O). (1) Pertaining to a device whose
parts can perform an input process and an output
process at the same time. (2) Pertaining to a functional
unit or channel involved in an input process, output
process, or both, concurrently or not, and to the data
involved in such a process. (3) Pertaining to input,
output, or both.
input/output configuration data set (IOCDS). The
data set in the S/390 processor (in the support
element) that contains an I/O configuration definition
built by the input/output configuration program (IOCP).
input/output configuration program (IOCP). A S/390
program that defines to a system the channels, I/O
devices, paths to the I/O devices and the addresses of
the I/O devices.The output is normally written to a
S/390 IOCDS.
interface. (1) A shared boundary between two
functional units, defined by functional characteristics,
signal characteristics, or other characteristics as
appropriate. The concept includes the specification of
the connection of two devices having different
functions. (2) Hardware, software, or both, that links
systems, programs, or devices.
I/O. See input/output.
I/O configuration. The collection of channel paths,
control units, and I/O devices that attaches to the
processor. This may also include channel switches (for
example an ESCON Director).
IOCP. See Input/Output configuration control program.
IODF. The data set that contains the S/390 I/O
configuration definition file produced during the
defining of the S/390 I/O configuration by HCD. Used
as a source for IPL, IOCP and Dynamic I/O
Reconfiguration.
IPL. See initial program load.
J
jumper cable. In an ESCON and FICON environment,
an optical cable having two conductors that provides
physical attachment between a channel and a
distribution panel or an ESCON Director port or a
control unit/devices, or between an ESCON Director
port and a distribution panel or a control unit/device, or
between a control unit/device and a distribution panel.
Contrast with trunk cable.
L
laser. A device that produces optical radiation using a
population inversion to provide light amplification by
stimulated emission of radiation and (generally) an
optical resonant cavity to provide positive feedback.
Laser radiation can be highly coherent temporally, or
spatially, or both.
LAN. See local area network.
LED. See light emitting diode.
licensed internal code (LIC). Microcode that IBM
does not sell as part of machine, licenses to the
customer. LIC is implemented in a part of storage that
is not addressable by user programs. Some IBM
products use it to implement functions as an alternate
to hard-wire circuitry.
light-emitting diode (LED). A semiconductor chip that
gives off visible or infrared light when activated.
Contrast Laser.
link. (1) In an ESCON environment, the physical
connection and transmission medium used between
an optical transmitter and an optical receiver. A link
consists of two conductors, one used for sending and
the other for receiving, thereby providing a duplex
communication path. (2) In an ESCON I/O interface,
the physical connection and transmission medium
used between a channel and a control unit, a channel
and an ESCD, a control unit and an ESCD, or, at times,
between two ESCDs.
link address. On an ESCON interface, the portion of a
source or destination address in a frame that ESCON
uses to route a frame through an ESCON director.
ESCON associates the link address with a specific
switch port that is on the ESCON director. See also
port address.
logical switch number (LSN). A two-digit number
used by the I/O Configuration Program (IOCP) to
identify a specific ESCON Director.
local area network (LAN). A computer network
located in a uses premises within a limited geographic
area.
logical partition (LPAR). A set of functions that create
a programming environment that is defined by the
ESA/390 architecture. ESA/390 architecture uses this
term when more than one LPAR is established on a
processor. An LPAR is conceptually similar to a virtual
machine environment except that the LPAR is a
function of the processor. Also LPAR does not depend
on an operating system to create the virtual machine
environment.
logically partitioned (LPAR) mode. A central
processor mode, available on the Configuration frame
when using the PR/SM facility, that allows an operator
to allocate processor hardware resources among
logical partitions. Contrast with basic mode.
LPAR. See logical partition.
M
megabyte (MB). (1) For processor storage, real and
virtual storage, and channel volume, 2
20
or 1 048 576
bytes. (2) For disk storage capacity and
communications volumes, 1 000 000 bytes.
multimode optical fiber. A graded-index or step-index
optical fiber that allows more than one bound mode to
propagate. Contrast with single-mode optical fiber.
N
National Committee for Information Technology
Standards. NCITS develops national standards and its
technical experts participate on behalf of the United
States in the international standards activities of
ISO/IEC JTC 1, information technology.
NCITS. See National Committee for Information
Technology Standards.
ND. See node descriptor.
NED. See node-element descriptor.
node descriptor. In an ESCON environment a node
descriptor (ND) is a 32-byte field that describes a
node, channel, ESCD port or a control unit.
node-element descriptor. In an ESCON environment
a node-element descriptor (NED) is a 32-byte field that
describes a node element.
O
OEMI. See original equipment manufactures
information.
open system. A system whose characteristics comply
with standards made available throughout the industry
and that therefore can be connected to other systems
complying with the same standards.
optical cable. A fiber, multiple fibers, or a fiber bundle
in a structure built to meet optical, mechanical, and
environmental specifications. See also jumper cable,
optical cable assembly, and trunk cable.
optical cable assembly. An optical cable that is
connector-terminated. Generally, an optical cable that
has been terminated by a manufacturer and is ready
for installation. See also jumper cable and optical
cable.
optical fiber. Any filament made of dialectic materials
that guides light, regardless of its ability to send
signals. See also fiber optics and optical waveguide.
optical fiber connector. A hardware component that
transfers optical power between two optical fibers or
bundles and is designed to be repeatedly connected
and disconnected.
optical waveguide. (1) A structure capable of guiding
optical power. (2) In optical communications, generally
119
a fiber designed to transmit optical signals. See optical
fiber.
original equipment manufactures information
(OEMI). A reference to an IBM guideline for a
computer peripheral interface. More specifically, refer
to IBM S/360 and S/370 Channel to Control Unit
Original Equipment Manufactures Information. The
interfaces uses ESA/390 logical protocols over an I/O
interface that configures attached units in a multi-drop
bus environment.
P
parallel channel. A channel having a System/360 and
System/370 channel-to-control-unit I/O interface that
uses bus and tag cables as a transmission medium.
Contrast with ESCON channel.
path. In a channel or communication network, any
route between any two nodes. For ESCON this would
be the route between the channel and the control
unit/device, or sometimes from the operating system
control block for the device and the device itself.
path group. The ESA/390 term for a set of channel
paths that are defined to a controller as being
associated with a single S/390 image. The channel
paths are in a group state and are on-line to the host.
path-group identifier. The ESA/390 term for the
identifier that uniquely identifies a given LPAR. The
path-group identifier is used in communication
between the system image program and a device. The
identifier associates the path-group with one or more
channel paths, thereby defining these paths to the
control unit as being associated with the same system
image.
port. (1) An access point for data entry or exit. (2) A
receptacle on a device to which a cable for another
device is attached. (3) See also duplex receptacle.
port address. In an ESCON Director, an address used
to specify port connectivity parameters and to assign
link addresses for attached channels and control units.
See also link address.
port name. In an ESCON Director, a user-defined
symbolic name of 24 characters or less that identifies a
particular port.
port card. In an ESCON environment, a
field-replaceable hardware component that provides
the optomechanical attachment method for jumper
cables and performs specific device-dependent logic
functions.
processor complex. A system configuration that
consists of all the machines required for operation; for
example, a processor unit, a processor controller, a
system display, a service support display, and a power
and coolant distribution unit.
program temporary fix (PTF). A temporary solution
or bypass of a problem diagnosed by IBM in a current
unaltered release of a program.
prohibited. In an ESCON Director, the attribute that,
when set, removes dynamic connectivity capability.
Contrast with allowed.
protocol. (1) A set of semantic and syntactic rules that
determines the behavior of functional units in
achieving communication. (2) In SNA, the meanings of
and the sequencing rules for requests and responses
used for managing the network, transferring data, and
synchronizing the states of network components. (3) A
specification for the format and relative timing of
information exchanged between communicating
parties.
PTF. See program temporary fix.
R
route. The path that an ESCON frame takes from a
channel through a ESCD to a control unit/device.
S
saved configuration. In an ESCON environment, a
stored set of connectivity attributes whose values
determine a configuration that can be used to replace
all or part of the ESCD's active configuration. Contrast
with active configuration.
self timed interface (STI). An interface that has one
or more conductors that transit information serially
between two interconnected units without requiring
any clock signals to recover that data. The interface
performs clock recovery independently on each serial
data stream and uses information in the data stream to
determine character boundaries and interconductor
synchronization.
service element (SE). A dedicated service processing
unit used to service a S/390 machine (processor).
Small Computer System Interface (SCSI). (1) An
ANSI standard for a logical interface to a computer
peripherals and for a computer peripheral interface.
The interface uses a SCSI logical protocol over an I/O
interface that configures attached targets and initiators
in a multi-drop bus topology. (2) A standard hardware
interface that enables a variety of peripheral devices to
communicate with one another.
subchannel. A logical function of a channel
subsystem associated with the management of a
single device.
subsystem. (1) A secondary or subordinate system,
or programming support, usually capable of operating
independently of or asynchronously with a controlling
system.
SWCH. In ESCON Manager, the mnemonic used to
represent an ESCON Director.
switch. In ESCON Manager, synonym for ESCON
Director.
T
trunk cable. In an ESCON environment, a cable
consisting of multiple fiber pairs that do not directly
attach to an active device. This cable usually exists
between distribution panels and can be located within,
or external to, a building. Contrast with jumper cable.
U
unblocked. In an ESCON Director, the attribute that,
when set, establishes communication capability for a
specific port. Contrast with blocked.
unit address. The ESA/390 term for the address
associated with a device on a given controller. On
ESCON interfaces, the unit address is the same as the
device address. On OEMI interfaces, the unit address
specifies a controller and device pair on the interface.
List of Abbreviations
AC Alternate Current
BTU British Thermal Units
CHPID Channel Path Identifier
CNC Connection Channel
(ESCON)
CTC Channel-to-Channel
CTP Control Processor (9032-5)
CU Control Unit
CUADD Control Unit Address
CUP Control Unit Port (9032-5)
CVC Converion Channel (ESCON)
DCAF Distributed Console Access
Facility
DC Direct Current
DVP Device Port (9032-5)
EAF Enhanced Availability Feature
(9032-5)
ESCD ESCON Director (9032-5)
ESCM ESCON Manager
ESCON Enterprise Connectivity
FCV Fiber Conversion
FICON Fiber Connectivity
FOSA Fiber Optic Subassembly
FTS Fiber Transport Services
HCD Hardware Configuration
Definition
HCM Hardware Configuration
Manager
HDD Hard Disk Drive
HMC Hardware Management
Console
IBM International Business
Machines Corporation
ID Identifier
IML Initial Machine Load
IODF Input Output Definition File
IPL Initial Program Load
ITSO International Technical
Support Organization
LAN Local Area Network
LED Light Emitting Diode
LCD Liquid Crystal Display
LIC Licensed Internal Code
LIN Link Incident
LSN Logical Switch Number
MAU Media Access Unit
MCP Mode Conditioning Patch
Cable
MXC Matrix Controller (9032-5)
MXS Matrix Switch (9032-5)
RCV Receive
TCP/IP Transmission Control
Protocol/Internet Protocol
TKRG Token Ring card
TX Transmit
XDF Extended distance feature
Index
Numerics
9032-3 4
9033-4 4
9034 ESCON converter 72
B
bridge 41, 43
C
cables 23
Fiber 21
Fiber (jumper) 22, 23
FTS 22
LAN 20
LED 78
trunk 21, 23
XDF 78
central cabinet 22, 23
chained connection 73
Comparison of 9032-5 4
configuration
console 41, 42
guidelines 35
matrix 38, 47
console
application 38
backup 20, 39
hardware requirements 40
matrix management 50
matrix storage 50
platforms 40
replacement 19, 39, 46
TCP/IP address 19
Control Processor (CTP) 9
cooling fan assemblies 11
CTP card 5, 8, 38
CUP (Control Unit Port) 32, 62
CUP name 62, 67
D
DCAF
LAN access 20, 42
modem access 42, 43
Modem access. 20
security 45
dedicated connection 72, 73
dedicated LAN 41, 42
device number 64, 66
Device Port (DVP) Cards 9
Director ID 62
distance limitations 78
dynamic connection 71, 73
E
Enhanced Availability Feature 5
CTP 6
MXC/MXS 6
TKRG card 6
environmental specifications 18
erep 87
ESCM
Software levels 27
ESCON configuration 79
ESCON Director Console Application 38
audit log 86
director definition 63
event log 86, 89
LIN log 86, 90, 91
matrix 63
port status 92
ESCON Manager
device view 96, 98
ISPF 53, 96
LCN (Logical Switch Number) 66
matrix storage 49
node descriptor 101
operating system console 52, 96
prerequisites 29
terminology 66
workstation 98, 101
ESCON Manager Console Application
node descriptor 100
ESCON port cards 8
F
Feature Codes 5
0103 82
0106 82
5240 5, 7
5245 5
5250 5, 7
5255 5
5260 5
5500 5
5600 5
5700 5
5701 5
5702 5
5703 5
5800 5
5901 40
5902 5
5903 5
6700 5
6701 5
6702 5
Fiber Cables 21
FICON
port card location 13
FICON (FCV) 80
FICON Bridge card 10
FICON port cards 8
FRU (Field Replaceable Unit) 88
FTS
Central cabinet 24
Central cabinets 22
Direct Attach feature 22
Trunking system 22
Zone cabinet 22, 24
H
Hardware Components 9, 10
Hardware Management Console (HMC) 40, 42
HCD
ESCON Director Control Unit definition 33
ESCON Director definition 32
IODF 50, 56
matrix management 49, 56
matrix storage 50, 56
migrate switch function 56
switch device number 64
switch ID 64
terminology 64
hierarchy 76
I
IODF 50, 56
IOS581E 90
J
Jumper cables 21, 22, 23
L
LAN
bridge 41, 43
cabling 20
DCAF 20
dedicated 41, 42
MAU 20
private 41, 42
public 41
security 45
laser links 78
LED links 78
LED port card 5
Logical Partitioning 14, 15
LOGREC 87
logs
director event log 89
director LIN 90
LSN (Logical Switch Number) 66
M
Maintenance 16
matrix
activation 49, 54
management
ESCD Console Application 49, 50
ESCM ISPF 49, 53
ESCM workstation 49
HCD 49, 56
operating system console 52
recommendations 59
retrieval 49, 54, 56
storage
CTP card 38
ESCD Console 50
ESCD console 49
ESCM ISPF 49, 53
ESCM workstation 49, 53
HCD IODF 49, 56
MAU 20
MCP 82
MCP cables 82
messages
IOS0001 87
IOS581E 90
IRD000E 87, 88
Mode Conditioner Patch cables 82
multi-mode links 78
MXC/MXS card set 5, 8
MXC/MXS card sets 11
N
node descriptor 90, 99
O
operator panel
IML button 9
Liquid Crystal Display (LCD) 9
location 9
Power-on LED 9
System Error LED 9
system error LED 87
OS/390 27
P
point-to-point 70
port address 90
Port addresses 12
port attributes 77
Port authorization 14
Port Card Layout 12
port card layout 107
Port cards 12
port status 92
Port swap 7
Power 18
Power supplies 8, 11, 18
private LAN 41, 42
production IODF 57
public LAN 41, 43
125
Q
Quadrants 8, 12
R
recommendations
console 44
terminology 68
S
SAMVS
Prerequisites 29
security
DCAF 45
ESCON Director Console Application 45
LAN 45
physical 45
Service clearance 18
single mode links 78
Software
ESCON Manager 27
SA for OS/390 27
Spare ESCON ports 8
Spare Ports 7
spare ports card 5, 10, 88
static connection 72, 73
switch
configuration ID 64
device number 64, 66
ID 64
name 66
switched point-to-point 71
system error LED 87
T
TCP/IP
console address 19
default addresses 19
director Address 19
director address 62
routing 41
TKRG card 5, 8
TKRG controller 11
topology
chaining 73, 78
dedicated 72
ESCON 81
FICON (FCV) 74, 80, 81
intermix 81
point-to-point 70
static connection 72
switched point-to-point 71
valid and invalid 75
Trunk
cables 21
U
Upgrades 16
W
work IODF 57
X
XDF links 78
XDF port card 5
Z
Zone cabinet 22
Zone cabinets 22, 23
ITSO Redbook Evaluation
SG24-2005-00
Your feedback is very important to help us maintain the quality of ITSO redbooks. Please complete this
questionnaire and return it using one of the following methods:
Use the online evaluation form found at http://www.redbooks.ibm.com/
Fax this form to: USA International Access Code + 1 914 432 8264
Send your comments in an Internet note to redbook@us.ibm.com
Which of the following best describes you?
_ Customer _ Business Partner _ Solution Developer _ IBM employee
_ None of the above
Please rate your overall satisfaction with this book using the scale:
(1 = very good, 2 = good, 3 = average, 4 = poor, 5 = very poor)
Overall Satisfaction __________
Please answer the following questions:
Was this redbook published in time for your needs? Yes___ No___
If no, please explain:
What other redbooks would you like to see published?
Comments/Suggestions: (THANK YOU FOR YOUR FEEDBACK!)
SG24-2005-00
Printed in the U.S.A.
I
B
M
E
S
C
O
N
D
i
r
e
c
t
o
r
9
0
3
2
-
5
P
r
e
s
e
n
t
a
t
i
o
n
S
G
2
4
-
2
0
0
5
-
0
0

9032 005 Presentation

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

9032 005 Presentation

Hochgeladen von

Copyright:

Verfügbare Formate

IBM ESCON Director 9032-5 Presentation

Ken Trowell, Helen Howard

Das könnte Ihnen auch gefallen