Re: McDATA switches, HCD, Cascaded FICON switches ...
Alan, According to the Redbook: FICON Implementation Guide, SG24-6497, dated: January 2006, Section 1.4.1 FICON support for cascaded Directors (Page 11), there is the following note: Keep in mind that once a 2-byte link address is defined to a channel path, all link addresses defined to be accessed from that same channel path must be 2- byte link addresses (regardless of whether there is only one switch in that link). We chose different channel paths for our cascaded vs. 'direct' FICON control units, however, I got hit by this restriction on the CHPID that had the directors CUP address. I have found it easier to just specify 2-byte link addresses for all control units on my FICON directors. It works and avoids confusion. HTH Glenn Miller -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: McDATA switches, HCD, Cascaded FICON switches ...
Field, Alan C. wrote: We are about to implement cascaded FICON switches. Right now we have two McDATA FICON switches with a number of DASD and TAPE devices connected. The devices are all local and use a single byte link id (chan.link e.g. 4A.30). We have to upgrade the McData's to allow cascading which apparently introduces a 2 byte link id (5B.6120) The question is: Can we mix one and two byte link ids or do we need to change ALL the existing definitions to use two byte ids? We don't know and we are getting conflicting answers from the various technical experts providing this solution for us. BTDT. AFAIR you don't need to change 'everything', but you have to change all the links connected to a given CU. However it's being done automagically - the only thing to do is to say OK. Disclaimer: I'm 90% sure of that. Only 90%. g -- Radoslaw Skorupka Lodz, Poland -- BRE Bank SA ul. Senatorska 18 00-950 Warszawa www.brebank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237 NIP: 526-021-50-88 Wedug stanu na dzie 01.01.2007 r. kapita zakadowy BRE Banku SA (w caoci opacony) wynosi 118.064.140 z. W zwizku z realizacj warunkowego podwyszenia kapitau zakadowego, na podstawie uchwa XVI WZ z dnia 21.05.2003 r., kapita zakadowy BRE Banku SA moe ulec podwyszeniu do kwoty 118.760.528 z. Akcje w podwyszonym kapitale zakadowym bd w caoci opacone. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
McDATA switches, HCD, Cascaded FICON switches ...
We are about to implement cascaded FICON switches. Right now we have two McDATA FICON switches with a number of DASD and TAPE devices connected. The devices are all local and use a single byte link id (chan.link e.g. 4A.30). We have to upgrade the McData's to allow cascading which apparently introduces a 2 byte link id (5B.6120) The question is: Can we mix one and two byte link ids or do we need to change ALL the existing definitions to use two byte ids? We don't know and we are getting conflicting answers from the various technical experts providing this solution for us. Alan -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
