VSM - FICON RTD and CLINK Configuration Information

Asset ID:	1-71-1449264.1
Update Date:	2012-04-13
Keywords:

Solution Type Technical Instruction Sure

Solution 1449264.1 : VSM - FICON RTD and CLINK Configuration Information

Applies to:

Sun StorageTek VSM System - Version: 4 to 5C - Release: 4.0 to 5.0
Information in this document applies to any platform.

Goal

This document presents information on VSM Ficon RTD and CLINK Configuration

Solution

Determining the correct values to configure a FICON NEARLINK
It is not very clear in determining the correct values when configuring the
director and port values for a FICON channel RTD and or CLINK.
This tech tip will serve as a listing of considerations and correct values.

NOTE: This document uses the term RTD but configuring a CLINK uses the same steps.

GENERAL INFORMATION on the VCF card

The processor on the VCF card is called a FICON Channel Processor (FIP).
The FIP can control one RTD if it is directly connected or two, three, or four RTDs if a FICON
director is used.
The VCF card does support cascading directors. See configuration considerations noted below.
RTD configuration information is entered on the channel configuration screen.
DD = Director ID of the director that has the RTD attached to it.
AA = Port address that has the RTD attached to it.

CONFIGURATION CONSIDERATIONS:
General Director/Switch Considerations:
Perform any configuration actions in the director/switch before performing any configuration actions in the VTSS. Remember the entries in the director are decimal.
The ports for the VTSS and RTD ports need to be in a zone for communication to succeed.
At a high level, place all the ports into one zone.
The best plan would be to place the VTSS and the RTD ports into a separate zone to remove cross traffic.
When directors are linked together, the port mapping tables convert into one table.
Example: linking director 32 with director 37 creates one mapping table containing ports 32xx and ports 37xx.
VTSS Considerations:
All entries into the VTSS are in hex! The director/switch data is in decimal.
If the customer is giving you decimal numbers/values, you must convert to hex before proceeding!
The DD value is always the director that the RTD is connected to.
For single director configurations 90% of the time the DD value is not needed so it can be 00.
NOTE: One firm exception is Brocade DCX which requires the VTSS select the director.
As a general rule if the VTSS cannot find the RTD in a single director configuration, then add the director number and see if that helps.
For cascading directors, the DD value would be the director that the RTD is connected to.
It is the responsibility of the directors in the cascading configuration "the cloud" to
determine how to route the data from the VTSS to the RTD.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Configurations and how to enter them into the VTSS Section covering McDATA directors 3232,
6064, 6140
NOTE: 6140 port numbers 0x84 through 0x87 are reserved.
McData uses two terms to designate the port that the cable is connected to.
The connection can be called a port number or a port address.
The first port number is 0 (decimal).
The first port address is 0x04 (hex).
REMEMBER the two above values are the same physical port on the director!
HINT: If you are not sure if you have a hex or decimal number, try them both!
Single director configuration:
The DD (director) field is always 00 because the VTSS is not required to select a director
different than the one it and the RTD are connected to.
The AA field is the hex address value of the port with the RTD attached to it plus 4.
Examples:
If the RTD is on port 5, then AA field will be a 9 (5 + 4).
If the RTD is on port decimal 25, convert to hex 0x19 then add 4 for 1D. Enter the value 0x1D in
the VTSS for the port address.
Cascaded directors:
REMEMBER: The values entered into the VTSS all point to the director and port the RTD is
cabled to.
In the VTSS configuration screen, you must enter in a director value and a port number.
These values must be in HEX.
Cascaded Directors require the directors be run in "High Integrity Fabric" mode. This means the
"SANtegrity" feature must be purchased from the director vendor and installed in the directors.
In the director, the “Insistent” option must be selected.
Steps needed to calculate the values needed to enter into the VTSS channel screen:
Use the steps under the single director configuration process to calculate the port address value.
Get the Address or Domain ID from the customer.
Verify if this is a decimal or hex number.
If value is in decimal then convert value to hex.
The DD field is the Switch Address or Domain ID (in hex) + 0x60(hex).
The AA field is the hex value of port with the RTD plus 4.
Example of DD value:
Domain ID = 1 (decimal or hex), add hex 60 to value to come to the value you enter in the VTSS channel screen as the director value.
Another example:
Domain ID = 45 (decimal) then the DD field is 8D ( 0x2D + 0x60 ).
NOTE: If the customer gives you the port number as hex 7A then: 0x7A+ 0x60 = 0xDA

+++++++++++++++++++++++++++++++++++++
Helpful information on the EIRCOM 5100 (FICON) SWITCH
Security Attributes also called DSA must be installed and enabled for the VTSS to login to the director.
The following command must be run to turn on the security feature once it has been installed: fddcfg --fabwideset ”SCC:S”.
Also the use of decimal and HEX values must be observed.
The switch is numbered using decimal values which the VCF cards use hex values to address the same switch:
Examples:
Switch = 10 VCF = 0A,
Switch = 11 VCF = 0B,
Switch = 21 VCF = 15
+++++++++++++++++++++++++++++++++++++
Helpful information on the Brocade 4100 Switch
The use of decimal and HEX values must be observed.
The switch uses decimal numbers, the VTSS uses HEX.
No need to add any offset values to port or switch address values (other than converting decimal to hex). Port number = port address. Director number = director number.
Cascaded 4100 switches use an ISL (Intra-Switch Link) and must be run in High Integrity Fabric mode.
Here is everything needed to resolve a cascaded switch problem in detail.
This information might apply to other Brocade switches so all is included.
Brocade Switch information – Two Cascaded switches – Brocade 4100‟s at V6.2.0e FOS.
Zoning: Cascaded switches - One zone with all the ports from both switches in the active configuration. Both switches need to be in the same fabric. Fabricshow command can be used to verify this (see the Display section for an example).
Offset: Not used with Brocade.
Hex versus Decimal usage: HCD and VTSS entries are hex, while the switch entries are decimal. So a switch defined to HCD as switch x„20‟ would be domain 32 on the switch. A VTSS RTD entry for this switch (domain 32) would be x‟20‟ and the switch port the RTD is on
Licenses: Additionally the Extended Fabric Licenses is required on both switches.
Port Based Routing MUST be set to „1‟, „aptpolicy‟ to „1‟.
Set one of the switches to the Principle switch, „fabricprincipal‟ to „1‟.
Set the default zone to no access, „defzone –noaccess‟
Dynamic Load Sharing (DLS) MUST be disabled with the dlsReset command. Check „route.stickyRoutes‟ in supportshow, value should be „1‟.
In Order Delivery (IOD) MUST be enabled with the IODset command. Check „route.delayReroute‟ in supportshow, value should be „1‟.
Interopmode – „0‟ if two Brocade switches are being used. „2‟ for mixed vendor switches.
High Integrity fabric required: this means an SCC_Policy is active, and each switch has a unique Domain ID, and the Insistent Domain ID Mode was set to „yes‟ during switch configure on each switch.
To create a SCC_Policy, via CLI.
a. First create an SCC Policy: secPolicyCreate “SCC_POLICY”, “ * ”
b. Now add members to the SCC Policy: secPolicyCreate “SCC_POLICY”, “wwn;wwn; …” Or to add all switches already in the fabric, just use an „*‟ instead of each individual WWN: secPolicyCreate “SCC_POLICY”, “*” NOTE: Switches must be in the same fabric FIRST for this to work.
c. Now save the policy and activate it: secpolicysave; secpolicyactivate
d. To validate the policy: secpolicyshow (see Display section below for an example)
e. Enable ACL Fabric Wide Consistency Policy and enforce a strict SCC policy: fddcfg –-fabwideset “SCC:S; ”
Other things to remember:
FICON Channel connectivity to storage CU port must not exceed one hop.
CHPID Link path must be defined using two-byte format in IOCP.
Display Section:
fabricshow
Switch ID Worldwide Name Enet IP Addr FC IP Addr Name
-------------------------------------------------------------------------
32: fffc20 10:00:00:05:1e:34:f1:a9 xx.xx.xx.xx 0.0.0.0 >"ETSDFIC32"
37: fffc25 10:00:00:05:1e:02:f1:46 xx.xx.xxx.xx 0.0.0.0 "NAPFIC37"
islshow
1: 26-> 26 10:00:00:05:1e:02:f1:46 37 NAPFIC37 sp: 2.000G bw: 2.000G
2: 27-> 27 10:00:00:05:1e:02:f1:46 37 NAPFIC37 sp: 2.000G bw: 2.000G
secpolicyshow
____________________________________________________
ACTIVE POLICY SET
SCC_POLICY
WWN DId swName
--------------------------------------------------
10:00:00:05:1e:34:f1:a9 32 ETSDFIC32
10:00:00:05:1e:02:f1:46 37 NAPFIC37
____________________________________________________
DEFINED POLICY SET
SCC_POLICY
WWN DId swName
--------------------------------------------------
10:00:00:05:1e:34:f1:a9 32 ETSDFIC32
10:00:00:05:1e:02:f1:46 37 NAPFIC37
Zoning -
cfg.FC_tape_cfg:FC_tape_zone
zone.FC_tape_zone:32,0;32,1;32,2;32,3;32,4;32,5;32,6;32,7;32,8;32,9;32,10;32,11;32,12;32,13;32,14;
32,15;32,16;32,17;32,18;32,19;32,20;32,21;32,22;32,23;32,24;32,25;32,26;32,27;32,28;32,29;32,30;
32,31;37,0;37,1;37,2;37,3;37,4;37,5;37,6;37,7;37,8;37,9;37,10;37,11;37,12;37,13;37,14;37,15;37,16;
37,17;37,18;37,19;37,20;37,21;37,22;37,23;37,24;37,25;37,26;37,27;37,28;37,29;37,30;37,31
defzone:noaccess
enable:FC_tape_cfg
Problems and workarounds:
Invalid Attach shown in the Hardware Management Console (HMC) for a CHPID – Attempt to vary a cascaded CHPID online to MVS before the SCC_Policy is active. You will see this “invalid attach” in the HMC for that CHPID. If this condition exists for a CHPID you‟ll need to vary that CHPID offline/online from the HMC. Note: that an IPL will not clear this, nor will vary offline/online of that CHPID from MVS.
+++++++++++++++++++++++++++++++++++++
Brocade DCX
Firmware at least level 6.3.0d Do not mix FC and FICON on the same board.
Use a 32 port board for FICON connections (dedicated)
The 48 ports boards can be used for FC. You must put the director address in the VCF configuration even if not setting up a cascading director configuration. So always enter in: DDAA
DD is Director number/Domain name (in hex)
AA is port the RTD is connected to (in hex)

01/26/06 - BF Created
Attachments

This solution has no attachment