Re: Remote access to Z14 ZR1 Support Element via HMC question
OK. I think we are making progress but I am not sure what the sysprogs are doing - seems to be suck it and see. We can now access the SE using SOO but we don't have the right credentials - appear to be just operators which isn't any good if we want to activate CBU's in a DR exercise. I suspect they didn't actually create the right accounts for us. I still think the HMC setup is not quite right. On OSA-ICC we could get to logon screens but go no further (session not bound or something). In an inspiration we snuck a look at SYS1.VTAMLST( MAJNODE) and it didn't look right in that the definitions for devices on the new Z14 didn't resemble existing zBC12 definitions. Since we are effectively outsourced, we cannot update this but I think one of our techs might have asked a casual question why the difference and a few hours later, lo and behold OSA-ICC started to work! No explanations yet but one could say, why argue with success! Export and import would have been much cleaner but I wonder if our support team have never had to do a skip release (12 to 14) and relied on the HMC's to copy information across when the Z14 is so much different and needs either a completely new OSA-ICC setup or export and import as you say, On Thu, Mar 28, 2019 at 8:13 PM Ravi Gaur wrote: > We recently moved to z14 and I exported the OSA-ICC existing configuration > via FTP to mainframe USS as below. > > Exporting OSA-ICC configuration file using OSA Advanced Facilities. > > To export the OSA-ICC configuration file, follow these steps: > > 1. Log on to the HMC, select the CPC you want to operate, and open the OSA > Advanced > Facility. > 2. Select the OSC CHPID to export the OSA-ICC configuration file. Next, > select Card > specific advanced facilities. Select Manual configuration options and > click OK > 3. The Manual Configuration Options window opens as below . Select Export > source > file and click OK. > 4. The task requests that hostname/username and mainframe Password is > entered with Unix file system to get the configuration in the USS > 6. The HMC displays the ACT2042 window (. Click OK. > 7. On Mainframe in USS you can see File should have been exported at the > given path. > > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Remote access to Z14 ZR1 Support Element via HMC question
Configuring from scratch could mean from text file. However the text file can be generated from old machine. BTW: I'm pretty sure I configured ICC using text file and the text file was sligthly modified version of exported one from older machine. -- Radoslaw Skorupka Lodz, Poland W dniu 2019-03-27 o 21:54, Laurence Chiu pisze: I'm wondering that too. The Redbook https://www.redbooks.ibm.com/redbooks/pdfs/sg248460.pdf Page 149 says when installing a new Z14 you must configure OSA-ICC from scratch and I wonder if they thought that could just copy the configuration from the zBC12 I hate to ask the techs these questions when I'm only the PM but it can't hurt I guess? On Wed, Mar 27, 2019, 8:50 PM Peter wrote: Could be client IP hasn't been defined in the session table.try adding it and check On Wed, 27 Mar, 2019, 11:47 AM Laurence Chiu, wrote: Well I don't know what the techs did but they managed to access the z14 HMC, copy across LPAR, IOCDS etc. and we've successfully IPL'ed a couple of LPARs from the same DS8870 that our zBC12 uses. That's progress, But now we are finding that we cannot access the OSA-ICC for remote access. The user gets the logon screen but cannot progress. I wonder if it's because the LU name or client IP hasn't been defined in the session table? On Mon, Mar 25, 2019 at 3:54 PM Mike Smith wrote: Laurence, The Top Guns are different for each region. The best way to get the proper one involved would be to contact the SSR directly or open a HW incident. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Laurence Chiu Sent: Sunday, March 24, 2019 5:58 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question hi Mike Your partially right. The tech support people want to access the hmc remotely because they are located almost 80 kilometres from the datacenter so that makes sense. The zBC12 and the Z14 sit alongside each other in the DR datacenter. Both are on the same LAN segment and subnet. However if they cannot even access the hmc locally in the same LAN segment the remote access is not really an issue. I'm not a technical person in this area but I think the goal is to somehow replicate the settings from the z12 hmc to the z14 since we basically want to maintain the same iocds LPAR configuration logon credentials etc. There seems to be a reluctance to use a USB drive because they want all the HMC's on the network to replicate credentials and settings from more one master copy. Using a USB drive would bypass that process. But it was certainly allow us to get the new Z 14 up and running. They are in the datacenter again today and I have not had an update so far. But should they still encounter connection problems who is this Top Gun Z you speak of? l to lists...@listserv.ua.edu with the message: INFO IBM-MAIN == Jeśli nie jesteś adresatem tej wiadomości: - powiadom nas o tym w mailu zwrotnym (dziękujemy!), - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś na dysku). Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać karze. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na 01.01.2018 r. wynosi 169.248.488 złotych. If you are not the addressee of this message: - let us know by replying to this e-mail (thank you!), - delete this message permanently (including all the copies which you have printed out or saved). This message may contain legally protected information, which may be used exclusively by the addressee.Please be reminded that anyone who disseminates (copies, distributes) this message or takes any similar action, violates the law and may be penalised. mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital City of Warsaw, 12th Commercial Division of the National Court Register, KRS 025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN 169,248,488 as at 1 January 2018. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Remote access to Z14 ZR1 Support Element via HMC question
We recently moved to z14 and I exported the OSA-ICC existing configuration via FTP to mainframe USS as below. Exporting OSA-ICC configuration file using OSA Advanced Facilities. To export the OSA-ICC configuration file, follow these steps: 1. Log on to the HMC, select the CPC you want to operate, and open the OSA Advanced Facility. 2. Select the OSC CHPID to export the OSA-ICC configuration file. Next, select Card specific advanced facilities. Select Manual configuration options and click OK 3. The Manual Configuration Options window opens as below . Select Export source file and click OK. 4. The task requests that hostname/username and mainframe Password is entered with Unix file system to get the configuration in the USS 6. The HMC displays the ACT2042 window (. Click OK. 7. On Mainframe in USS you can see File should have been exported at the given path. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Remote access to Z14 ZR1 Support Element via HMC question
There are some new fields in the OSA-ICC definitions. I have had success by importing the old definitions via a thumb drive, then editing them on the HMC. That will populate the new fields when you save the definition. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Laurence Chiu Sent: Wednesday, March 27, 2019 1:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question I'm wondering that too. The Redbook https://www.redbooks.ibm.com/redbooks/pdfs/sg248460.pdf Page 149 says when installing a new Z14 you must configure OSA-ICC from scratch and I wonder if they thought that could just copy the configuration from the zBC12 I hate to ask the techs these questions when I'm only the PM but it can't hurt I guess? On Wed, Mar 27, 2019, 8:50 PM Peter wrote: > Could be client IP hasn't been defined in the session table.try adding it > and check > > On Wed, 27 Mar, 2019, 11:47 AM Laurence Chiu, wrote: > > > Well I don't know what the techs did but they managed to access the z14 > > HMC, copy across LPAR, IOCDS etc. and we've successfully IPL'ed a couple > of > > LPARs from the same DS8870 that our zBC12 uses. That's progress, > > > > But now we are finding that we cannot access the OSA-ICC for remote > access. > > The user gets the logon screen but cannot progress. I wonder if it's > > because the LU name or client IP hasn't been defined in the session > table? > > > > On Mon, Mar 25, 2019 at 3:54 PM Mike Smith wrote: > > > > > Laurence, > > > > > > The Top Guns are different for each region. The best way to get the > > > proper one involved would be to contact the SSR directly or open a HW > > > incident. > > > > > > -Original Message- > > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On > > > Behalf Of Laurence Chiu > > > Sent: Sunday, March 24, 2019 5:58 PM > > > To: IBM-MAIN@LISTSERV.UA.EDU > > > Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question > > > > > > hi Mike > > > > > > Your partially right. The tech support people want to access the hmc > > > remotely because they are located almost 80 kilometres from the > > datacenter > > > so that makes sense. > > > > > > The zBC12 and the Z14 sit alongside each other in the DR datacenter. > > Both > > > are on the same LAN segment and subnet. > > > > > > However if they cannot even access the hmc locally in the same LAN > > segment > > > the remote access is not really an issue. > > > > > > I'm not a technical person in this area but I think the goal is to > > somehow > > > replicate the settings from the z12 hmc to the z14 since we basically > > want > > > to maintain the same iocds LPAR configuration logon credentials etc. > > > > > > There seems to be a reluctance to use a USB drive because they want all > > the > > > HMC's on the network to replicate credentials and settings from more > one > > > master copy. Using a USB drive would bypass that process. But it was > > > certainly allow us to get the new Z 14 up and running. > > > > > > They are in the datacenter again today and I have not had an update so > > far. > > > But should they still encounter connection problems who is this Top > Gun Z > > > you speak of? > > > > > > l to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Remote access to Z14 ZR1 Support Element via HMC question
I'm wondering that too. The Redbook https://www.redbooks.ibm.com/redbooks/pdfs/sg248460.pdf Page 149 says when installing a new Z14 you must configure OSA-ICC from scratch and I wonder if they thought that could just copy the configuration from the zBC12 I hate to ask the techs these questions when I'm only the PM but it can't hurt I guess? On Wed, Mar 27, 2019, 8:50 PM Peter wrote: > Could be client IP hasn't been defined in the session table.try adding it > and check > > On Wed, 27 Mar, 2019, 11:47 AM Laurence Chiu, wrote: > > > Well I don't know what the techs did but they managed to access the z14 > > HMC, copy across LPAR, IOCDS etc. and we've successfully IPL'ed a couple > of > > LPARs from the same DS8870 that our zBC12 uses. That's progress, > > > > But now we are finding that we cannot access the OSA-ICC for remote > access. > > The user gets the logon screen but cannot progress. I wonder if it's > > because the LU name or client IP hasn't been defined in the session > table? > > > > On Mon, Mar 25, 2019 at 3:54 PM Mike Smith wrote: > > > > > Laurence, > > > > > > The Top Guns are different for each region. The best way to get the > > > proper one involved would be to contact the SSR directly or open a HW > > > incident. > > > > > > -Original Message- > > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On > > > Behalf Of Laurence Chiu > > > Sent: Sunday, March 24, 2019 5:58 PM > > > To: IBM-MAIN@LISTSERV.UA.EDU > > > Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question > > > > > > hi Mike > > > > > > Your partially right. The tech support people want to access the hmc > > > remotely because they are located almost 80 kilometres from the > > datacenter > > > so that makes sense. > > > > > > The zBC12 and the Z14 sit alongside each other in the DR datacenter. > > Both > > > are on the same LAN segment and subnet. > > > > > > However if they cannot even access the hmc locally in the same LAN > > segment > > > the remote access is not really an issue. > > > > > > I'm not a technical person in this area but I think the goal is to > > somehow > > > replicate the settings from the z12 hmc to the z14 since we basically > > want > > > to maintain the same iocds LPAR configuration logon credentials etc. > > > > > > There seems to be a reluctance to use a USB drive because they want all > > the > > > HMC's on the network to replicate credentials and settings from more > one > > > master copy. Using a USB drive would bypass that process. But it was > > > certainly allow us to get the new Z 14 up and running. > > > > > > They are in the datacenter again today and I have not had an update so > > far. > > > But should they still encounter connection problems who is this Top > Gun Z > > > you speak of? > > > > > > l to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Remote access to Z14 ZR1 Support Element via HMC question
We did migrate profiles with USB stick, but OSA setup was done remotely. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Laurence Chiu Sent: Wednesday, March 27, 2019 12:46 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Remote access to Z14 ZR1 Support Element via HMC question Well I don't know what the techs did but they managed to access the z14 HMC, copy across LPAR, IOCDS etc. and we've successfully IPL'ed a couple of LPARs from the same DS8870 that our zBC12 uses. That's progress, But now we are finding that we cannot access the OSA-ICC for remote access. The user gets the logon screen but cannot progress. I wonder if it's because the LU name or client IP hasn't been defined in the session table? On Mon, Mar 25, 2019 at 3:54 PM Mike Smith wrote: > Laurence, > > The Top Guns are different for each region. The best way to get the > proper one involved would be to contact the SSR directly or open a HW > incident. > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Laurence Chiu > Sent: Sunday, March 24, 2019 5:58 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question > > hi Mike > > Your partially right. The tech support people want to access the hmc > remotely because they are located almost 80 kilometres from the > datacenter so that makes sense. > > The zBC12 and the Z14 sit alongside each other in the DR datacenter. > Both are on the same LAN segment and subnet. > > However if they cannot even access the hmc locally in the same LAN > segment the remote access is not really an issue. > > I'm not a technical person in this area but I think the goal is to > somehow replicate the settings from the z12 hmc to the z14 since we > basically want to maintain the same iocds LPAR configuration logon > credentials etc. > > There seems to be a reluctance to use a USB drive because they want > all the HMC's on the network to replicate credentials and settings > from more one master copy. Using a USB drive would bypass that > process. But it was certainly allow us to get the new Z 14 up and running. > > They are in the datacenter again today and I have not had an update so far. > But should they still encounter connection problems who is this Top > Gun Z you speak of? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Remote access to Z14 ZR1 Support Element via HMC question
I conferred with the person who did the work, but I see that the problem is solved. In all the years we've used CMOS/HMCs--most generations since the original 9672--I don't recall an architectural HMC communication failure, especially involving N/N-2. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Laurence Chiu Sent: Saturday, March 23, 2019 12:18 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Remote access to Z14 ZR1 Support Element via HMC question Out of interest how did you copy the data from the old hmcs to the new ones? I'm not sure my post got to the list but the approach our tech people are using is to use the HMC for the 12 to populate the HMCs for the 14 and so far the old HMC cannot discover the new one. That is a potential show stopper for us. On Sun, Mar 24, 2019, 4:19 AM Jesse 1 Robinson wrote: > We replaced two z12s late last year with a z14 and a z13s. I didn't do > the actual work, but all 'migratable' HMC data was copied over to the > new CECs ahead of the push-pull swap out. This includes profile data > and userids/passwords. The z14 includes some new options that need to > be set manually because they don't have counterparts on the z12, but > before the swap, all four CECs were able to communicate with each other. > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Parwez > Sent: Saturday, March 23, 2019 3:25 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: (External):Re: Remote access to Z14 ZR1 Support Element via > HMC question > > Just a thought. > > Although its possible to use some of the older HMC H/W (I think its FC > 0092 - zBC12 had this and FC 0095), even with the correct level of HMC > code, these do not support some of the HMC Enhancements (GA2) which > were delivered with System Driver level 36 and HMC/SE Level 2.14.1 > > Parwez > > > From: IBM Mainframe Discussion List on > behalf of Laurence Chiu > Sent: 21 March 2019 18:45 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question > > Thanks > > We did do a major HMC firmware upgrade across the complex recently and > that issue was checked during our diagnostic call but all HMCs are on > the same level. > > Hopefully it's the domain issue else will be at our wits end. For > some reason our support organisation does not want to copy the zBC12 > configuration information across to the new z14 using a USB drive but > really want the HMC for the zBC12 to connect to the z14 so the > configuration information is already loaded. > > On Thu, Mar 21, 2019, 8:07 PM Parwez wrote: > > > While I can't answer your specific Q. A general point - a HMC with > 'lower' > > level of HMC code can't control/access System requiring a 'higher' > > level of HMC code. A HMC with higher level code e.g the z14 ZR1 HMC > > can access/control Systems all the way back to z10 EC and BC. If > > your > > zBC12 HMC is at level 2.12.1 then this could be the issue. If your > > zBC12 HMC hardware is of the right spec, then there is nothing to > > stop you upgrading it to the same level code as the z14 ZR1 HMC. > > > > Regards > > Parwez > > > > ____________________ > > From: IBM Mainframe Discussion List on > > behalf of Laurence Chiu > > Sent: 21 March 2019 06:07 > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: Remote access to Z14 ZR1 Support Element via HMC > > question > > > > OK an update. We haven't solved the remote access issue yet but the > > guys wanted to do use the zBC12 HMC to discover the Z14 HMC. But > > despite all networking being fine (all the HMC's and the SE's are in > > the same LAN > > segment) the zBC12 HMC could not see the Z14 HMC. Yet if they logged > > onto the Z14 HMC it could see the Z14 SE fine. I asked the question > > (since one of my colleagues has done this before) since the new > > machine is a drop-in replacement using the same DS8K SAN, why don't > > they just copy the config from the zBC12 HMC to a USB drive and load > > it onto the Z14. I was told that wasn't standard practice, even > > though > it would work. > > > > Further diagnosis reveals a potential issue with the domain settings > > on > the > > new HMC's and SE's not matching those on the existing ones. The new > HMC's > > were setup with domain defaults I am told and they are probably not > > what the old HMC's were setup with. Something along the lines of " > > The “Current domain name” is displayed on the
Re: Remote access to Z14 ZR1 Support Element via HMC question
Could be client IP hasn't been defined in the session table.try adding it and check On Wed, 27 Mar, 2019, 11:47 AM Laurence Chiu, wrote: > Well I don't know what the techs did but they managed to access the z14 > HMC, copy across LPAR, IOCDS etc. and we've successfully IPL'ed a couple of > LPARs from the same DS8870 that our zBC12 uses. That's progress, > > But now we are finding that we cannot access the OSA-ICC for remote access. > The user gets the logon screen but cannot progress. I wonder if it's > because the LU name or client IP hasn't been defined in the session table? > > On Mon, Mar 25, 2019 at 3:54 PM Mike Smith wrote: > > > Laurence, > > > > The Top Guns are different for each region. The best way to get the > > proper one involved would be to contact the SSR directly or open a HW > > incident. > > > > -Original Message- > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > > Behalf Of Laurence Chiu > > Sent: Sunday, March 24, 2019 5:58 PM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question > > > > hi Mike > > > > Your partially right. The tech support people want to access the hmc > > remotely because they are located almost 80 kilometres from the > datacenter > > so that makes sense. > > > > The zBC12 and the Z14 sit alongside each other in the DR datacenter. > Both > > are on the same LAN segment and subnet. > > > > However if they cannot even access the hmc locally in the same LAN > segment > > the remote access is not really an issue. > > > > I'm not a technical person in this area but I think the goal is to > somehow > > replicate the settings from the z12 hmc to the z14 since we basically > want > > to maintain the same iocds LPAR configuration logon credentials etc. > > > > There seems to be a reluctance to use a USB drive because they want all > the > > HMC's on the network to replicate credentials and settings from more one > > master copy. Using a USB drive would bypass that process. But it was > > certainly allow us to get the new Z 14 up and running. > > > > They are in the datacenter again today and I have not had an update so > far. > > But should they still encounter connection problems who is this Top Gun Z > > you speak of? > > > > l to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Remote access to Z14 ZR1 Support Element via HMC question
Well I don't know what the techs did but they managed to access the z14 HMC, copy across LPAR, IOCDS etc. and we've successfully IPL'ed a couple of LPARs from the same DS8870 that our zBC12 uses. That's progress, But now we are finding that we cannot access the OSA-ICC for remote access. The user gets the logon screen but cannot progress. I wonder if it's because the LU name or client IP hasn't been defined in the session table? On Mon, Mar 25, 2019 at 3:54 PM Mike Smith wrote: > Laurence, > > The Top Guns are different for each region. The best way to get the > proper one involved would be to contact the SSR directly or open a HW > incident. > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Laurence Chiu > Sent: Sunday, March 24, 2019 5:58 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question > > hi Mike > > Your partially right. The tech support people want to access the hmc > remotely because they are located almost 80 kilometres from the datacenter > so that makes sense. > > The zBC12 and the Z14 sit alongside each other in the DR datacenter. Both > are on the same LAN segment and subnet. > > However if they cannot even access the hmc locally in the same LAN segment > the remote access is not really an issue. > > I'm not a technical person in this area but I think the goal is to somehow > replicate the settings from the z12 hmc to the z14 since we basically want > to maintain the same iocds LPAR configuration logon credentials etc. > > There seems to be a reluctance to use a USB drive because they want all the > HMC's on the network to replicate credentials and settings from more one > master copy. Using a USB drive would bypass that process. But it was > certainly allow us to get the new Z 14 up and running. > > They are in the datacenter again today and I have not had an update so far. > But should they still encounter connection problems who is this Top Gun Z > you speak of? > > l to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Remote access to Z14 ZR1 Support Element via HMC question
Laurence, The Top Guns are different for each region. The best way to get the proper one involved would be to contact the SSR directly or open a HW incident. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Laurence Chiu Sent: Sunday, March 24, 2019 5:58 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question hi Mike Your partially right. The tech support people want to access the hmc remotely because they are located almost 80 kilometres from the datacenter so that makes sense. The zBC12 and the Z14 sit alongside each other in the DR datacenter. Both are on the same LAN segment and subnet. However if they cannot even access the hmc locally in the same LAN segment the remote access is not really an issue. I'm not a technical person in this area but I think the goal is to somehow replicate the settings from the z12 hmc to the z14 since we basically want to maintain the same iocds LPAR configuration logon credentials etc. There seems to be a reluctance to use a USB drive because they want all the HMC's on the network to replicate credentials and settings from more one master copy. Using a USB drive would bypass that process. But it was certainly allow us to get the new Z 14 up and running. They are in the datacenter again today and I have not had an update so far. But should they still encounter connection problems who is this Top Gun Z you speak of? On Mon, Mar 25, 2019, 5:08 AM Mike Smith wrote: > Laurence, thanks for the earlier clarification. > > Just to make sure that I understand At this point, the zBC12 and the > ZR1 are sitting in the DR site, each with their own HMC (on the same > network). Right? If so I'd hazard a guess that the desire to do everything > remotely is because there is no technical staff at the DR site. > > Absolutely the easiest way to transfer the LPAR definitions, user info, > OSA ICC definitions and I/O definitions is via a USB drive The SSR > frequently does this as part of the install. (The SSR must do this if the > customer choses to replace the old HMC with the new HMC). Since the SSR > knows how to do it, I'd reach out to the SSR and see if he could copy these > definitions across for you. Alternately, if there is any staff at the DR > site, could someone insert a USB drive into the zBC12 HMC? Then the > information could be copied to the USB drive (via commands issued > remotely). Then a local staff person could move the USB drive to the new > HMC. Again, the information could be copied (imported in this case) via > commands issued remotely. Data transfer complete. > > If it is absolutely imperative that the two HMCs talk to each other, then > I recommend that you open a HW incident on the z14 to engage the SSR, then > ask him to involve the z Top Gun. > > I am curious about the process your technical team wants to follow to > transfer this information. Coul you obtain a copy of that process and > document it here? > > Regards, > > Mike > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Laurence Chiu > Sent: Saturday, March 23, 2019 12:18 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question > > Out of interest how did you copy the data from the old hmcs to the new > ones? I'm not sure my post got to the list but the approach our tech > people are using is to use the HMC for the 12 to populate the HMCs for the > 14 and so far the old HMC cannot discover the new one. That is a potential > show stopper for us. > > On Sun, Mar 24, 2019, 4:19 AM Jesse 1 Robinson > wrote: > > > We replaced two z12s late last year with a z14 and a z13s. I didn't do > the > > actual work, but all 'migratable' HMC data was copied over to the new > CECs > > ahead of the push-pull swap out. This includes profile data and > > userids/passwords. The z14 includes some new options that need to be set > > manually because they don't have counterparts on the z12, but before the > > swap, all four CECs were able to communicate with each other. > > > > -Original Message- > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > > Behalf Of Parwez > > Sent: Saturday, March 23, 2019 3:25 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: (External):Re: Remote access to Z14 ZR1 Support Element via HMC > > question > > > > Just a thought. > > > > Although its possible to use some of the older HMC H/W (I think its FC > > 0092 - zBC12 had this and FC 0095), even with the correct level of HMC > > code, these do not support some of the HMC Enhancements (GA2) w
Re: Remote access to Z14 ZR1 Support Element via HMC question
hi Mike Your partially right. The tech support people want to access the hmc remotely because they are located almost 80 kilometres from the datacenter so that makes sense. The zBC12 and the Z14 sit alongside each other in the DR datacenter. Both are on the same LAN segment and subnet. However if they cannot even access the hmc locally in the same LAN segment the remote access is not really an issue. I'm not a technical person in this area but I think the goal is to somehow replicate the settings from the z12 hmc to the z14 since we basically want to maintain the same iocds LPAR configuration logon credentials etc. There seems to be a reluctance to use a USB drive because they want all the HMC's on the network to replicate credentials and settings from more one master copy. Using a USB drive would bypass that process. But it was certainly allow us to get the new Z 14 up and running. They are in the datacenter again today and I have not had an update so far. But should they still encounter connection problems who is this Top Gun Z you speak of? On Mon, Mar 25, 2019, 5:08 AM Mike Smith wrote: > Laurence, thanks for the earlier clarification. > > Just to make sure that I understand At this point, the zBC12 and the > ZR1 are sitting in the DR site, each with their own HMC (on the same > network). Right? If so I'd hazard a guess that the desire to do everything > remotely is because there is no technical staff at the DR site. > > Absolutely the easiest way to transfer the LPAR definitions, user info, > OSA ICC definitions and I/O definitions is via a USB drive The SSR > frequently does this as part of the install. (The SSR must do this if the > customer choses to replace the old HMC with the new HMC). Since the SSR > knows how to do it, I'd reach out to the SSR and see if he could copy these > definitions across for you. Alternately, if there is any staff at the DR > site, could someone insert a USB drive into the zBC12 HMC? Then the > information could be copied to the USB drive (via commands issued > remotely). Then a local staff person could move the USB drive to the new > HMC. Again, the information could be copied (imported in this case) via > commands issued remotely. Data transfer complete. > > If it is absolutely imperative that the two HMCs talk to each other, then > I recommend that you open a HW incident on the z14 to engage the SSR, then > ask him to involve the z Top Gun. > > I am curious about the process your technical team wants to follow to > transfer this information. Coul you obtain a copy of that process and > document it here? > > Regards, > > Mike > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Laurence Chiu > Sent: Saturday, March 23, 2019 12:18 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question > > Out of interest how did you copy the data from the old hmcs to the new > ones? I'm not sure my post got to the list but the approach our tech > people are using is to use the HMC for the 12 to populate the HMCs for the > 14 and so far the old HMC cannot discover the new one. That is a potential > show stopper for us. > > On Sun, Mar 24, 2019, 4:19 AM Jesse 1 Robinson > wrote: > > > We replaced two z12s late last year with a z14 and a z13s. I didn't do > the > > actual work, but all 'migratable' HMC data was copied over to the new > CECs > > ahead of the push-pull swap out. This includes profile data and > > userids/passwords. The z14 includes some new options that need to be set > > manually because they don't have counterparts on the z12, but before the > > swap, all four CECs were able to communicate with each other. > > > > -Original Message- > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > > Behalf Of Parwez > > Sent: Saturday, March 23, 2019 3:25 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: (External):Re: Remote access to Z14 ZR1 Support Element via HMC > > question > > > > Just a thought. > > > > Although its possible to use some of the older HMC H/W (I think its FC > > 0092 - zBC12 had this and FC 0095), even with the correct level of HMC > > code, these do not support some of the HMC Enhancements (GA2) which were > > delivered with System Driver level 36 and HMC/SE Level 2.14.1 > > > > Parwez > > > > > > From: IBM Mainframe Discussion List on behalf > > of Laurence Chiu > > Sent: 21 March 2019 18:45 > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question > > > > Thanks
Re: Remote access to Z14 ZR1 Support Element via HMC question
Laurence, thanks for the earlier clarification. Just to make sure that I understand At this point, the zBC12 and the ZR1 are sitting in the DR site, each with their own HMC (on the same network). Right? If so I'd hazard a guess that the desire to do everything remotely is because there is no technical staff at the DR site. Absolutely the easiest way to transfer the LPAR definitions, user info, OSA ICC definitions and I/O definitions is via a USB drive The SSR frequently does this as part of the install. (The SSR must do this if the customer choses to replace the old HMC with the new HMC). Since the SSR knows how to do it, I'd reach out to the SSR and see if he could copy these definitions across for you. Alternately, if there is any staff at the DR site, could someone insert a USB drive into the zBC12 HMC? Then the information could be copied to the USB drive (via commands issued remotely). Then a local staff person could move the USB drive to the new HMC. Again, the information could be copied (imported in this case) via commands issued remotely. Data transfer complete. If it is absolutely imperative that the two HMCs talk to each other, then I recommend that you open a HW incident on the z14 to engage the SSR, then ask him to involve the z Top Gun. I am curious about the process your technical team wants to follow to transfer this information. Coul you obtain a copy of that process and document it here? Regards, Mike -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Laurence Chiu Sent: Saturday, March 23, 2019 12:18 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question Out of interest how did you copy the data from the old hmcs to the new ones? I'm not sure my post got to the list but the approach our tech people are using is to use the HMC for the 12 to populate the HMCs for the 14 and so far the old HMC cannot discover the new one. That is a potential show stopper for us. On Sun, Mar 24, 2019, 4:19 AM Jesse 1 Robinson wrote: > We replaced two z12s late last year with a z14 and a z13s. I didn't do the > actual work, but all 'migratable' HMC data was copied over to the new CECs > ahead of the push-pull swap out. This includes profile data and > userids/passwords. The z14 includes some new options that need to be set > manually because they don't have counterparts on the z12, but before the > swap, all four CECs were able to communicate with each other. > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Parwez > Sent: Saturday, March 23, 2019 3:25 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: (External):Re: Remote access to Z14 ZR1 Support Element via HMC > question > > Just a thought. > > Although its possible to use some of the older HMC H/W (I think its FC > 0092 - zBC12 had this and FC 0095), even with the correct level of HMC > code, these do not support some of the HMC Enhancements (GA2) which were > delivered with System Driver level 36 and HMC/SE Level 2.14.1 > > Parwez > > > From: IBM Mainframe Discussion List on behalf > of Laurence Chiu > Sent: 21 March 2019 18:45 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question > > Thanks > > We did do a major HMC firmware upgrade across the complex recently and > that issue was checked during our diagnostic call but all HMCs are on the > same level. > > Hopefully it's the domain issue else will be at our wits end. For some > reason our support organisation does not want to copy the zBC12 > configuration information across to the new z14 using a USB drive but > really want the HMC for the zBC12 to connect to the z14 so the > configuration information is already loaded. > > On Thu, Mar 21, 2019, 8:07 PM Parwez wrote: > > > While I can't answer your specific Q. A general point - a HMC with > 'lower' > > level of HMC code can't control/access System requiring a 'higher' > > level of HMC code. A HMC with higher level code e.g the z14 ZR1 HMC > > can access/control Systems all the way back to z10 EC and BC. If your > > zBC12 HMC is at level 2.12.1 then this could be the issue. If your > > zBC12 HMC hardware is of the right spec, then there is nothing to stop > > you upgrading it to the same level code as the z14 ZR1 HMC. > > > > Regards > > Parwez > > > > ____________________ > > From: IBM Mainframe Discussion List on > > behalf of Laurence Chiu > > Sent: 21 March 2019 06:07 > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question > > > > O
Re: Remote access to Z14 ZR1 Support Element via HMC question
Out of interest how did you copy the data from the old hmcs to the new ones? I'm not sure my post got to the list but the approach our tech people are using is to use the HMC for the 12 to populate the HMCs for the 14 and so far the old HMC cannot discover the new one. That is a potential show stopper for us. On Sun, Mar 24, 2019, 4:19 AM Jesse 1 Robinson wrote: > We replaced two z12s late last year with a z14 and a z13s. I didn't do the > actual work, but all 'migratable' HMC data was copied over to the new CECs > ahead of the push-pull swap out. This includes profile data and > userids/passwords. The z14 includes some new options that need to be set > manually because they don't have counterparts on the z12, but before the > swap, all four CECs were able to communicate with each other. > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Parwez > Sent: Saturday, March 23, 2019 3:25 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: (External):Re: Remote access to Z14 ZR1 Support Element via HMC > question > > Just a thought. > > Although its possible to use some of the older HMC H/W (I think its FC > 0092 - zBC12 had this and FC 0095), even with the correct level of HMC > code, these do not support some of the HMC Enhancements (GA2) which were > delivered with System Driver level 36 and HMC/SE Level 2.14.1 > > Parwez > > > From: IBM Mainframe Discussion List on behalf > of Laurence Chiu > Sent: 21 March 2019 18:45 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question > > Thanks > > We did do a major HMC firmware upgrade across the complex recently and > that issue was checked during our diagnostic call but all HMCs are on the > same level. > > Hopefully it's the domain issue else will be at our wits end. For some > reason our support organisation does not want to copy the zBC12 > configuration information across to the new z14 using a USB drive but > really want the HMC for the zBC12 to connect to the z14 so the > configuration information is already loaded. > > On Thu, Mar 21, 2019, 8:07 PM Parwez wrote: > > > While I can't answer your specific Q. A general point - a HMC with > 'lower' > > level of HMC code can't control/access System requiring a 'higher' > > level of HMC code. A HMC with higher level code e.g the z14 ZR1 HMC > > can access/control Systems all the way back to z10 EC and BC. If your > > zBC12 HMC is at level 2.12.1 then this could be the issue. If your > > zBC12 HMC hardware is of the right spec, then there is nothing to stop > > you upgrading it to the same level code as the z14 ZR1 HMC. > > > > Regards > > Parwez > > > > ____________________ > > From: IBM Mainframe Discussion List on > > behalf of Laurence Chiu > > Sent: 21 March 2019 06:07 > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question > > > > OK an update. We haven't solved the remote access issue yet but the > > guys wanted to do use the zBC12 HMC to discover the Z14 HMC. But > > despite all networking being fine (all the HMC's and the SE's are in > > the same LAN > > segment) the zBC12 HMC could not see the Z14 HMC. Yet if they logged > > onto the Z14 HMC it could see the Z14 SE fine. I asked the question > > (since one of my colleagues has done this before) since the new > > machine is a drop-in replacement using the same DS8K SAN, why don't > > they just copy the config from the zBC12 HMC to a USB drive and load > > it onto the Z14. I was told that wasn't standard practice, even though > it would work. > > > > Further diagnosis reveals a potential issue with the domain settings on > the > > new HMC's and SE's not matching those on the existing ones. The new > HMC's > > were setup with domain defaults I am told and they are probably not > > what the old HMC's were setup with. Something along the lines of " > > The “Current domain name” is displayed on the window. If NOT SET is > > displayed, it indicates that default domain security is in effect for > > this console." This is from the Hardware Management Console Operations > > Guide - Version 2.14.0 > > > > http://www-01.ibm.com/support/docview.wss?uid=isg23e9d1b6de8c163f98525 > > 8195006801cc > > pages 712 onwards > > > > Now if the existing HMC's have an actual domain name setting in them, > > then it make sense they cannot connect to a HMC with default domain > > security since there is a mismatch. > > > > That
Re: Remote access to Z14 ZR1 Support Element via HMC question
We replaced two z12s late last year with a z14 and a z13s. I didn't do the actual work, but all 'migratable' HMC data was copied over to the new CECs ahead of the push-pull swap out. This includes profile data and userids/passwords. The z14 includes some new options that need to be set manually because they don't have counterparts on the z12, but before the swap, all four CECs were able to communicate with each other. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Parwez Sent: Saturday, March 23, 2019 3:25 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Remote access to Z14 ZR1 Support Element via HMC question Just a thought. Although its possible to use some of the older HMC H/W (I think its FC 0092 - zBC12 had this and FC 0095), even with the correct level of HMC code, these do not support some of the HMC Enhancements (GA2) which were delivered with System Driver level 36 and HMC/SE Level 2.14.1 Parwez From: IBM Mainframe Discussion List on behalf of Laurence Chiu Sent: 21 March 2019 18:45 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question Thanks We did do a major HMC firmware upgrade across the complex recently and that issue was checked during our diagnostic call but all HMCs are on the same level. Hopefully it's the domain issue else will be at our wits end. For some reason our support organisation does not want to copy the zBC12 configuration information across to the new z14 using a USB drive but really want the HMC for the zBC12 to connect to the z14 so the configuration information is already loaded. On Thu, Mar 21, 2019, 8:07 PM Parwez wrote: > While I can't answer your specific Q. A general point - a HMC with 'lower' > level of HMC code can't control/access System requiring a 'higher' > level of HMC code. A HMC with higher level code e.g the z14 ZR1 HMC > can access/control Systems all the way back to z10 EC and BC. If your > zBC12 HMC is at level 2.12.1 then this could be the issue. If your > zBC12 HMC hardware is of the right spec, then there is nothing to stop > you upgrading it to the same level code as the z14 ZR1 HMC. > > Regards > Parwez > > > From: IBM Mainframe Discussion List on > behalf of Laurence Chiu > Sent: 21 March 2019 06:07 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question > > OK an update. We haven't solved the remote access issue yet but the > guys wanted to do use the zBC12 HMC to discover the Z14 HMC. But > despite all networking being fine (all the HMC's and the SE's are in > the same LAN > segment) the zBC12 HMC could not see the Z14 HMC. Yet if they logged > onto the Z14 HMC it could see the Z14 SE fine. I asked the question > (since one of my colleagues has done this before) since the new > machine is a drop-in replacement using the same DS8K SAN, why don't > they just copy the config from the zBC12 HMC to a USB drive and load > it onto the Z14. I was told that wasn't standard practice, even though it > would work. > > Further diagnosis reveals a potential issue with the domain settings on the > new HMC's and SE's not matching those on the existing ones. The new HMC's > were setup with domain defaults I am told and they are probably not > what the old HMC's were setup with. Something along the lines of " > The “Current domain name” is displayed on the window. If NOT SET is > displayed, it indicates that default domain security is in effect for > this console." This is from the Hardware Management Console Operations > Guide - Version 2.14.0 > > http://www-01.ibm.com/support/docview.wss?uid=isg23e9d1b6de8c163f98525 > 8195006801cc > pages 712 onwards > > Now if the existing HMC's have an actual domain name setting in them, > then it make sense they cannot connect to a HMC with default domain > security since there is a mismatch. > > That apparently is our next diagnostic step. Just wonder if other > folks on this list have ever encountered problems similar to this? > Thanks > > On Thu, Mar 21, 2019 at 2:55 PM Laurence Chiu wrote: > > > Thanks > > > > Looking at this list and the firewall requests that have been > > raised, it seems we're covered. > > > > Interesting as noted we have a zBC12 in the same room and there is > > no problem accessing it and the new HMC'S for the z14 are in the > > same subnet so should be covered by the same firewall rules. > > > > However nobody can tell if they've ever tried to access the SE on > > the > > zBC12 remotely because as another poster said, if your configuration > > is stable t
Re: Remote access to Z14 ZR1 Support Element via HMC question
Just a thought. Although its possible to use some of the older HMC H/W (I think its FC 0092 - zBC12 had this and FC 0095), even with the correct level of HMC code, these do not support some of the HMC Enhancements (GA2) which were delivered with System Driver level 36 and HMC/SE Level 2.14.1 Parwez From: IBM Mainframe Discussion List on behalf of Laurence Chiu Sent: 21 March 2019 18:45 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question Thanks We did do a major HMC firmware upgrade across the complex recently and that issue was checked during our diagnostic call but all HMCs are on the same level. Hopefully it's the domain issue else will be at our wits end. For some reason our support organisation does not want to copy the zBC12 configuration information across to the new z14 using a USB drive but really want the HMC for the zBC12 to connect to the z14 so the configuration information is already loaded. On Thu, Mar 21, 2019, 8:07 PM Parwez wrote: > While I can't answer your specific Q. A general point - a HMC with 'lower' > level of HMC code can't control/access System requiring a 'higher' level > of HMC code. A HMC with higher level code e.g the z14 ZR1 HMC can > access/control Systems all the way back to z10 EC and BC. If your zBC12 HMC > is at level 2.12.1 then this could be the issue. If your zBC12 HMC hardware > is of the right spec, then there is nothing to stop you upgrading it to the > same level code as the z14 ZR1 HMC. > > Regards > Parwez > > > From: IBM Mainframe Discussion List on behalf > of Laurence Chiu > Sent: 21 March 2019 06:07 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question > > OK an update. We haven't solved the remote access issue yet but the guys > wanted to do use the zBC12 HMC to discover the Z14 HMC. But despite all > networking being fine (all the HMC's and the SE's are in the same LAN > segment) the zBC12 HMC could not see the Z14 HMC. Yet if they logged onto > the Z14 HMC it could see the Z14 SE fine. I asked the question (since one > of my colleagues has done this before) since the new machine is a drop-in > replacement using the same DS8K SAN, why don't they just copy the config > from the zBC12 HMC to a USB drive and load it onto the Z14. I was told that > wasn't standard practice, even though it would work. > > Further diagnosis reveals a potential issue with the domain settings on the > new HMC's and SE's not matching those on the existing ones. The new HMC's > were setup with domain defaults I am told and they are probably not what > the old HMC's were setup with. Something along the lines of " The “Current > domain name” is displayed on the window. If NOT SET is displayed, it > indicates that default domain security is in effect for this console." This > is from the > Hardware Management Console Operations Guide - Version 2.14.0 > > http://www-01.ibm.com/support/docview.wss?uid=isg23e9d1b6de8c163f985258195006801cc > pages 712 onwards > > Now if the existing HMC's have an actual domain name setting in them, then > it make sense they cannot connect to a HMC with default domain security > since there is a mismatch. > > That apparently is our next diagnostic step. Just wonder if other folks > on this list have ever encountered problems similar to this? Thanks > > On Thu, Mar 21, 2019 at 2:55 PM Laurence Chiu wrote: > > > Thanks > > > > Looking at this list and the firewall requests that have been raised, it > > seems we're covered. > > > > Interesting as noted we have a zBC12 in the same room and there is no > > problem accessing it and the new HMC'S for the z14 are in the same subnet > > so should be covered by the same firewall rules. > > > > However nobody can tell if they've ever tried to access the SE on the > > zBC12 remotely because as another poster said, if your configuration is > > stable then there is little need to do that. > > > > That could certainly point to a firewall rule that's never been tested. > > > > Again back to my original point, why can't the support element > > configuration be done locally why we try to figure out the network issues > > for remote access > > > > > > > > On Thu, Mar 21, 2019, 3:10 AM Edgington, Jerry < > > jerry.edging...@westernsouthernlife.com> wrote: > > > >> Dana, > >> > >> Here is my "cheat sheet" for HMC ports and direction. However, I don't > >> know if they have changed for z14 ZR1, but they work for z13s. > >> > >> ○ H
Re: Remote access to Z14 ZR1 Support Element via HMC question
Sorry I don't know except that all HMC's are now at the same microcode level. As it's the weekend I will try to find out next week. That's when we are going to try again actually in the data centre to avoid any firewall issues. We didn't actually fix the firewall issue - that's still outstanding. We decided to work on that in parallel since we cannot see the Z14 HMC from the zBC12 HMC even in the same room on the same LAN segment. To clarify the situation. We are replacing an existing zBC12 with a z14 ZR1. All our HMC's, both in this location and in our primary DC are supposed to be at the same driver level and credentials sync from a master. Our tech folks plan was to use the zBC12 HMC to access the new z14 HMC so that they could populate all the details from the zBC12 to the Z14 (LPAR definitions, logon credentials, IOCDS etc.). So far that is not working. I am intrigued and somewhat concerned about your Top Gun's comment that a zBC12 HMC cannot see a Z14 HMC. If that is the case then we are barking up the wrong tree :-( Then sneakernet my well be the only way to copy the configuration across. The goal is to get the z14 up using the same IOCDS (well similar) to that on the zBC12 as it will be patched into the same DS8870 and want to get it IPL'ed and workload tested. I didn't see the new IP pors that need to be accessed through the firewall but we are asking for all the ports based on this document to be open. https://www-01.ibm.com/support/docview.wss?uid=isg229b0fe89af786b2885258194006dd308=1 Still if we can't see the HMC on the same subnet and VLAN in the same room, then firewall rule are not really relevant. On Sat, Mar 23, 2019 at 7:27 PM Mike Smith wrote: > What is the feature Code of the HMC on the zBC12? That will determine the > maximum driver level that can be applied, but I doubt that it's the same > driver level as the z14. In prior conversations with our Top Gun I was > led to believe that an HMC associated with a zBC12 will not see the HMC on > a z14. Of course, I could be wrong, but the only way it might work > would be if you got an extra HMC FC0082 or FC0083 with the z14 and replaced > the old zBC12 HMC. > > The earlier notes mentioned that you resolved the firewall issues so you > must have found the documentation relating to the additional ports that > need to be opened for a z14. Did you also see the information about the > new IP addresses that need to be accessed through your firewall so the z14 > can contact the new "Enhanced" Support Center? > > Regards, > > Mike > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Laurence Chiu > Sent: Thursday, March 21, 2019 11:46 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question > > Thanks > > We did do a major HMC firmware upgrade across the complex recently and that > issue was checked during our diagnostic call but all HMCs are on the same > level. > > Hopefully it's the domain issue else will be at our wits end. For some > reason our support organisation does not want to copy the zBC12 > configuration information across to the new z14 using a USB drive but > really want the HMC for the zBC12 to connect to the z14 so the > configuration information is already loaded. > > On Thu, Mar 21, 2019, 8:07 PM Parwez wrote: > > > While I can't answer your specific Q. A general point - a HMC with > 'lower' > > level of HMC code can't control/access System requiring a 'higher' level > > of HMC code. A HMC with higher level code e.g the z14 ZR1 HMC can > > access/control Systems all the way back to z10 EC and BC. If your zBC12 > HMC > > is at level 2.12.1 then this could be the issue. If your zBC12 HMC > hardware > > is of the right spec, then there is nothing to stop you upgrading it to > the > > same level code as the z14 ZR1 HMC. > > > > Regards > > Parwez > > > > ________________ > > From: IBM Mainframe Discussion List on behalf > > of Laurence Chiu > > Sent: 21 March 2019 06:07 > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question > > > > OK an update. We haven't solved the remote access issue yet but the guys > > wanted to do use the zBC12 HMC to discover the Z14 HMC. But despite all > > networking being fine (all the HMC's and the SE's are in the same LAN > > segment) the zBC12 HMC could not see the Z14 HMC. Yet if they logged onto > > the Z14 HMC it could see the Z14 SE fine. I asked the question (since one > > of my colleagues has done this before) since the new machine is a drop-in > > replacement using the same DS8K SAN, why don't the
Re: Remote access to Z14 ZR1 Support Element via HMC question
What is the feature Code of the HMC on the zBC12? That will determine the maximum driver level that can be applied, but I doubt that it's the same driver level as the z14. In prior conversations with our Top Gun I was led to believe that an HMC associated with a zBC12 will not see the HMC on a z14. Of course, I could be wrong, but the only way it might work would be if you got an extra HMC FC0082 or FC0083 with the z14 and replaced the old zBC12 HMC. The earlier notes mentioned that you resolved the firewall issues so you must have found the documentation relating to the additional ports that need to be opened for a z14. Did you also see the information about the new IP addresses that need to be accessed through your firewall so the z14 can contact the new "Enhanced" Support Center? Regards, Mike -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Laurence Chiu Sent: Thursday, March 21, 2019 11:46 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question Thanks We did do a major HMC firmware upgrade across the complex recently and that issue was checked during our diagnostic call but all HMCs are on the same level. Hopefully it's the domain issue else will be at our wits end. For some reason our support organisation does not want to copy the zBC12 configuration information across to the new z14 using a USB drive but really want the HMC for the zBC12 to connect to the z14 so the configuration information is already loaded. On Thu, Mar 21, 2019, 8:07 PM Parwez wrote: > While I can't answer your specific Q. A general point - a HMC with 'lower' > level of HMC code can't control/access System requiring a 'higher' level > of HMC code. A HMC with higher level code e.g the z14 ZR1 HMC can > access/control Systems all the way back to z10 EC and BC. If your zBC12 HMC > is at level 2.12.1 then this could be the issue. If your zBC12 HMC hardware > is of the right spec, then there is nothing to stop you upgrading it to the > same level code as the z14 ZR1 HMC. > > Regards > Parwez > > > From: IBM Mainframe Discussion List on behalf > of Laurence Chiu > Sent: 21 March 2019 06:07 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question > > OK an update. We haven't solved the remote access issue yet but the guys > wanted to do use the zBC12 HMC to discover the Z14 HMC. But despite all > networking being fine (all the HMC's and the SE's are in the same LAN > segment) the zBC12 HMC could not see the Z14 HMC. Yet if they logged onto > the Z14 HMC it could see the Z14 SE fine. I asked the question (since one > of my colleagues has done this before) since the new machine is a drop-in > replacement using the same DS8K SAN, why don't they just copy the config > from the zBC12 HMC to a USB drive and load it onto the Z14. I was told that > wasn't standard practice, even though it would work. > > Further diagnosis reveals a potential issue with the domain settings on the > new HMC's and SE's not matching those on the existing ones. The new HMC's > were setup with domain defaults I am told and they are probably not what > the old HMC's were setup with. Something along the lines of " The “Current > domain name” is displayed on the window. If NOT SET is displayed, it > indicates that default domain security is in effect for this console." This > is from the > Hardware Management Console Operations Guide - Version 2.14.0 > > http://www-01.ibm.com/support/docview.wss?uid=isg23e9d1b6de8c163f985258195006801cc > pages 712 onwards > > Now if the existing HMC's have an actual domain name setting in them, then > it make sense they cannot connect to a HMC with default domain security > since there is a mismatch. > > That apparently is our next diagnostic step. Just wonder if other folks > on this list have ever encountered problems similar to this? Thanks > > On Thu, Mar 21, 2019 at 2:55 PM Laurence Chiu wrote: > > > Thanks > > > > Looking at this list and the firewall requests that have been raised, it > > seems we're covered. > > > > Interesting as noted we have a zBC12 in the same room and there is no > > problem accessing it and the new HMC'S for the z14 are in the same subnet > > so should be covered by the same firewall rules. > > > > However nobody can tell if they've ever tried to access the SE on the > > zBC12 remotely because as another poster said, if your configuration is > > stable then there is little need to do that. > > > > That could certainly point to a firewall rule that's never been tested. > > > > Again back to my original point, why can't the
Re: Remote access to Z14 ZR1 Support Element via HMC question
Thanks We did do a major HMC firmware upgrade across the complex recently and that issue was checked during our diagnostic call but all HMCs are on the same level. Hopefully it's the domain issue else will be at our wits end. For some reason our support organisation does not want to copy the zBC12 configuration information across to the new z14 using a USB drive but really want the HMC for the zBC12 to connect to the z14 so the configuration information is already loaded. On Thu, Mar 21, 2019, 8:07 PM Parwez wrote: > While I can't answer your specific Q. A general point - a HMC with 'lower' > level of HMC code can't control/access System requiring a 'higher' level > of HMC code. A HMC with higher level code e.g the z14 ZR1 HMC can > access/control Systems all the way back to z10 EC and BC. If your zBC12 HMC > is at level 2.12.1 then this could be the issue. If your zBC12 HMC hardware > is of the right spec, then there is nothing to stop you upgrading it to the > same level code as the z14 ZR1 HMC. > > Regards > Parwez > > > From: IBM Mainframe Discussion List on behalf > of Laurence Chiu > Sent: 21 March 2019 06:07 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question > > OK an update. We haven't solved the remote access issue yet but the guys > wanted to do use the zBC12 HMC to discover the Z14 HMC. But despite all > networking being fine (all the HMC's and the SE's are in the same LAN > segment) the zBC12 HMC could not see the Z14 HMC. Yet if they logged onto > the Z14 HMC it could see the Z14 SE fine. I asked the question (since one > of my colleagues has done this before) since the new machine is a drop-in > replacement using the same DS8K SAN, why don't they just copy the config > from the zBC12 HMC to a USB drive and load it onto the Z14. I was told that > wasn't standard practice, even though it would work. > > Further diagnosis reveals a potential issue with the domain settings on the > new HMC's and SE's not matching those on the existing ones. The new HMC's > were setup with domain defaults I am told and they are probably not what > the old HMC's were setup with. Something along the lines of " The “Current > domain name” is displayed on the window. If NOT SET is displayed, it > indicates that default domain security is in effect for this console." This > is from the > Hardware Management Console Operations Guide - Version 2.14.0 > > http://www-01.ibm.com/support/docview.wss?uid=isg23e9d1b6de8c163f985258195006801cc > pages 712 onwards > > Now if the existing HMC's have an actual domain name setting in them, then > it make sense they cannot connect to a HMC with default domain security > since there is a mismatch. > > That apparently is our next diagnostic step. Just wonder if other folks > on this list have ever encountered problems similar to this? Thanks > > On Thu, Mar 21, 2019 at 2:55 PM Laurence Chiu wrote: > > > Thanks > > > > Looking at this list and the firewall requests that have been raised, it > > seems we're covered. > > > > Interesting as noted we have a zBC12 in the same room and there is no > > problem accessing it and the new HMC'S for the z14 are in the same subnet > > so should be covered by the same firewall rules. > > > > However nobody can tell if they've ever tried to access the SE on the > > zBC12 remotely because as another poster said, if your configuration is > > stable then there is little need to do that. > > > > That could certainly point to a firewall rule that's never been tested. > > > > Again back to my original point, why can't the support element > > configuration be done locally why we try to figure out the network issues > > for remote access > > > > > > > > On Thu, Mar 21, 2019, 3:10 AM Edgington, Jerry < > > jerry.edging...@westernsouthernlife.com> wrote: > > > >> Dana, > >> > >> Here is my "cheat sheet" for HMC ports and direction. However, I don't > >> know if they have changed for z14 ZR1, but they work for z13s. > >> > >> ○ HMC inbound IP ports from internal network > >> § Type Source Port Usage > >> ICMP8 Establish communication with > >> resources managed by HMC > >> TCP 58787 - 58788 Automatic discovery of > >> zServers > >> UDP 58788 Automatic discovery of zServers > >> UDP 9900HMC to HMC auto discovery > >> TCP 5
Re: Remote access to Z14 ZR1 Support Element via HMC question
While I can't answer your specific Q. A general point - a HMC with 'lower' level of HMC code can't control/access System requiring a 'higher' level of HMC code. A HMC with higher level code e.g the z14 ZR1 HMC can access/control Systems all the way back to z10 EC and BC. If your zBC12 HMC is at level 2.12.1 then this could be the issue. If your zBC12 HMC hardware is of the right spec, then there is nothing to stop you upgrading it to the same level code as the z14 ZR1 HMC. Regards Parwez From: IBM Mainframe Discussion List on behalf of Laurence Chiu Sent: 21 March 2019 06:07 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question OK an update. We haven't solved the remote access issue yet but the guys wanted to do use the zBC12 HMC to discover the Z14 HMC. But despite all networking being fine (all the HMC's and the SE's are in the same LAN segment) the zBC12 HMC could not see the Z14 HMC. Yet if they logged onto the Z14 HMC it could see the Z14 SE fine. I asked the question (since one of my colleagues has done this before) since the new machine is a drop-in replacement using the same DS8K SAN, why don't they just copy the config from the zBC12 HMC to a USB drive and load it onto the Z14. I was told that wasn't standard practice, even though it would work. Further diagnosis reveals a potential issue with the domain settings on the new HMC's and SE's not matching those on the existing ones. The new HMC's were setup with domain defaults I am told and they are probably not what the old HMC's were setup with. Something along the lines of " The “Current domain name” is displayed on the window. If NOT SET is displayed, it indicates that default domain security is in effect for this console." This is from the Hardware Management Console Operations Guide - Version 2.14.0 http://www-01.ibm.com/support/docview.wss?uid=isg23e9d1b6de8c163f985258195006801cc pages 712 onwards Now if the existing HMC's have an actual domain name setting in them, then it make sense they cannot connect to a HMC with default domain security since there is a mismatch. That apparently is our next diagnostic step. Just wonder if other folks on this list have ever encountered problems similar to this? Thanks On Thu, Mar 21, 2019 at 2:55 PM Laurence Chiu wrote: > Thanks > > Looking at this list and the firewall requests that have been raised, it > seems we're covered. > > Interesting as noted we have a zBC12 in the same room and there is no > problem accessing it and the new HMC'S for the z14 are in the same subnet > so should be covered by the same firewall rules. > > However nobody can tell if they've ever tried to access the SE on the > zBC12 remotely because as another poster said, if your configuration is > stable then there is little need to do that. > > That could certainly point to a firewall rule that's never been tested. > > Again back to my original point, why can't the support element > configuration be done locally why we try to figure out the network issues > for remote access > > > > On Thu, Mar 21, 2019, 3:10 AM Edgington, Jerry < > jerry.edging...@westernsouthernlife.com> wrote: > >> Dana, >> >> Here is my "cheat sheet" for HMC ports and direction. However, I don't >> know if they have changed for z14 ZR1, but they work for z13s. >> >> ○ HMC inbound IP ports from internal network >> § Type Source Port Usage >> ICMP8 Establish communication with >> resources managed by HMC >> TCP 58787 - 58788 Automatic discovery of >> zServers >> UDP 58788 Automatic discovery of zServers >> UDP 9900HMC to HMC auto discovery >> TCP 5 SSL communication from servers >> TCP 9920SSL HMC and zServers >> TCP 443 Remote user access to HMC >> TCP 9950-9959 Proxy Single Object >> Operations to server >> TCP 9960Java applet-based tasks (not >> required since v2.12.1) >> UDP 161 SMNP automation of the HMC >> TCP 161 SMNP automation of the HMC >> TCP 3161SMNP automation of the HMC >> TCP 6794SSL automation traffic, including >> HMC Mobile app >> TCP 61612 Web Services API message broker, >> flowing STOMP >> TCP 61617 Web Services API message broker, >> flowing OpenWire &g
Re: Remote access to Z14 ZR1 Support Element via HMC question
HMC auto discovery >> TCP 58787 - 58788 Automatic discovery of >> zServers >> UDP 58788 Automatic discovery of zServers >> TCP 5 SSL communication from servers >> TCP 9920SSL HMC and zServers >> TCP 443 Single Object Operations to >> server console >> TCP 9960Java applet-based tasks (not >> required since v2.12.1) >> TCP 25345 Single Object Operations to >> server console >> TCP X LDAP port to authenticate Users >> TCP 443 Call home requests RSF, and HMC >> mobile app >> TCP 3900AAM for zBX >> TCP 21 Load system software or utility >> programs >> TCP 22 SSH >> UDP 123 Connect to NTP server >> TCP 25 SMTP for email >> >> ○ SE inbound IP ports from internal network >> § Type Source Port Usage >> ICMP8 Establish communication with >> resources managed by HMC >> TCP 58787 Automatic discovery of zServers >> UDP 58787 Automatic discovery of zServers >> TCP 5 SSL communication from servers >> TCP 9920SSL HMC and zServers >> TCP 443 Call home requests RSF, and HMC >> mobile app >> TCP 9950-9959 Manage DataPower XI50z >> from HMC >> TCP 9960Java applet-based tasks (not >> required since v2.12.1) >> UDP 161 SMNP automation of the HMC >> TCP 161 SMNP automation of the HMC >> TCP 3161SMNP automation of the HMC >> UDP 123 Set the time of the servers >> UDP 520 Communications with routers from >> HMC >> TCP 22 Remote access by Product >> Engineering >> TCP 21 Inbound FTP requests >> TCP 3900-3909 AMM for zBX >> >> ○ SE outbound IP ports to internal networks >> § Type Source Port Usage >> ICMP8 Establish communication with >> resources managed by HMC >> UDP 9900HMC to HMC auto discovery >> TCP 58787 Automatic discovery of zServers >> UDP 58787 Automatic discovery of zServers >> TCP 5 SSL communication from servers >> TCP 9920SSL HMC and zServers >> TCP 443 Single Object Operations to >> server console >> TCP 9960Java applet-based tasks (not >> required since v2.12.1) >> TCP 25345 Single Object Operations to >> server console >> TCP X LDAP port to authenticate Users >> TCP 443 Call home requests RSF, and HMC >> mobile app >> TCP 3900AAM for zBX >> TCP 21 Load system software or utility >> programs >> TCP 22 SSH >> UDP 520 Communications with routers from >> HMC >> UDP 123 Set the time of the servers >> >> -Original Message- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On >> Behalf Of Dana Mitchell >> Sent: Wednesday, March 20, 2019 10:06 AM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question >> >> As far as firewall rules go, we can access SOO remotely so I'm looking >> back at some of my old firewall requests, and it looks like for a new HMC I >> requested ports 443,9960 and 2300 to be opened. But in the current doc, >> port 2300 is not referenced, so I don't recall what that was for. >> >> Your other question about accessing the SE's, I would say that wouldn't >> be neccessary very
Re: Remote access to Z14 ZR1 Support Element via HMC question
t; UDP 161 SMNP automation of the HMC > TCP 161 SMNP automation of the HMC > TCP 3161SMNP automation of the HMC > UDP 123 Set the time of the servers > UDP 520 Communications with routers from > HMC > TCP 22 Remote access by Product > Engineering > TCP 21 Inbound FTP requests > TCP 3900-3909 AMM for zBX > > ○ SE outbound IP ports to internal networks > § Type Source Port Usage > ICMP8 Establish communication with > resources managed by HMC > UDP 9900HMC to HMC auto discovery > TCP 58787 Automatic discovery of zServers > UDP 58787 Automatic discovery of zServers > TCP 5 SSL communication from servers > TCP 9920SSL HMC and zServers > TCP 443 Single Object Operations to server > console > TCP 9960Java applet-based tasks (not > required since v2.12.1) > TCP 25345 Single Object Operations to server > console > TCP X LDAP port to authenticate Users > TCP 443 Call home requests RSF, and HMC > mobile app > TCP 3900AAM for zBX > TCP 21 Load system software or utility > programs > TCP 22 SSH > UDP 520 Communications with routers from > HMC > UDP 123 Set the time of the servers > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Dana Mitchell > Sent: Wednesday, March 20, 2019 10:06 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question > > As far as firewall rules go, we can access SOO remotely so I'm looking > back at some of my old firewall requests, and it looks like for a new HMC I > requested ports 443,9960 and 2300 to be opened. But in the current doc, > port 2300 is not referenced, so I don't recall what that was for. > > Your other question about accessing the SE's, I would say that wouldn't > be neccessary very much at all once the machine is setup, perhaps for CHP > problem determination type of thing, but I can't think of normal day to day > requirements. > > Dana > > On Wed, 20 Mar 2019 22:02:21 +1300, Laurence Chiu > wrote: > > > > >Any thoughts from the group on this parallel approach. I have no idea > >how often the SE needs to be accessed but this is a fairly static > >environment so I would think not that often. > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Remote access to Z14 ZR1 Support Element via HMC question
Re: Cheat sheet. All this information plus lots of other stuff can be found in: Hardware Management Console Security Manual SC28-6987-01 Regards Parwez Hamid From: IBM Mainframe Discussion List on behalf of Edgington, Jerry Sent: 20 March 2019 14:10 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question Dana, Here is my "cheat sheet" for HMC ports and direction. However, I don't know if they have changed for z14 ZR1, but they work for z13s. ○ HMC inbound IP ports from internal network § Type Source Port Usage ICMP 8 Establish communication with resources managed by HMC TCP 58787 - 58788 Automatic discovery of zServers UDP 58788 Automatic discovery of zServers UDP 9900HMC to HMC auto discovery TCP 5 SSL communication from servers TCP 9920SSL HMC and zServers TCP 443 Remote user access to HMC TCP 9950-9959 Proxy Single Object Operations to server TCP 9960Java applet-based tasks (not required since v2.12.1) UDP 161 SMNP automation of the HMC TCP 161 SMNP automation of the HMC TCP 3161SMNP automation of the HMC TCP 6794SSL automation traffic, including HMC Mobile app TCP 61612 Web Services API message broker, flowing STOMP TCP 61617 Web Services API message broker, flowing OpenWire UDP 123 Set the time of the servers UDP 520 Communications with routers from HMC TCP 22 Remote access by Product Engineering TCP 21 Inbound FTP requests TCP 3900-3909 AMM for zBX ○ HMC outbound IP ports to network to internal network TypeSource Port Usage ICMP 8 Establish communication with resources managed by HMC UDP 9900HMC to HMC auto discovery TCP 58787 - 58788 Automatic discovery of zServers UDP 58788 Automatic discovery of zServers TCP 5 SSL communication from servers TCP 9920SSL HMC and zServers TCP 443 Single Object Operations to server console TCP 9960Java applet-based tasks (not required since v2.12.1) TCP 25345 Single Object Operations to server console TCP X LDAP port to authenticate Users TCP 443 Call home requests RSF, and HMC mobile app TCP 3900AAM for zBX TCP 21 Load system software or utility programs TCP 22 SSH UDP 123 Connect to NTP server TCP 25 SMTP for email ○ SE inbound IP ports from internal network § Type Source Port Usage ICMP 8 Establish communication with resources managed by HMC TCP 58787 Automatic discovery of zServers UDP 58787 Automatic discovery of zServers TCP 5 SSL communication from servers TCP 9920SSL HMC and zServers TCP 443 Call home requests RSF, and HMC mobile app TCP 9950-9959 Manage DataPower XI50z from HMC TCP 9960Java applet-based tasks (not required since v2.12.1) UDP 161 SMNP automation of the HMC TCP 161 SMNP automation of the HMC TCP 3161SMNP automation of the HMC UDP 123 Set the time of the servers UDP 520 Communications with routers from HMC TCP 22 Remote access by Product Engineering TCP 21 Inbound FTP requests TCP 3900-3909 AMM for zBX ○ SE outbound IP ports to internal networks § Type Source Port Usage ICMP 8 Establish communication with resources managed by HMC UDP 9
Re: Remote access to Z14 ZR1 Support Element via HMC question
d zServers TCP 443 Single Object Operations to server console TCP 9960Java applet-based tasks (not required since v2.12.1) TCP 25345 Single Object Operations to server console TCP X LDAP port to authenticate Users TCP 443 Call home requests RSF, and HMC mobile app TCP 3900AAM for zBX TCP 21 Load system software or utility programs TCP 22 SSH UDP 520 Communications with routers from HMC UDP 123 Set the time of the servers -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Dana Mitchell Sent: Wednesday, March 20, 2019 10:06 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Remote access to Z14 ZR1 Support Element via HMC question As far as firewall rules go, we can access SOO remotely so I'm looking back at some of my old firewall requests, and it looks like for a new HMC I requested ports 443,9960 and 2300 to be opened. But in the current doc, port 2300 is not referenced, so I don't recall what that was for. Your other question about accessing the SE's, I would say that wouldn't be neccessary very much at all once the machine is setup, perhaps for CHP problem determination type of thing, but I can't think of normal day to day requirements. Dana On Wed, 20 Mar 2019 22:02:21 +1300, Laurence Chiu wrote: > >Any thoughts from the group on this parallel approach. I have no idea >how often the SE needs to be accessed but this is a fairly static >environment so I would think not that often. > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Remote access to Z14 ZR1 Support Element via HMC question
As far as firewall rules go, we can access SOO remotely so I'm looking back at some of my old firewall requests, and it looks like for a new HMC I requested ports 443,9960 and 2300 to be opened. But in the current doc, port 2300 is not referenced, so I don't recall what that was for. Your other question about accessing the SE's, I would say that wouldn't be neccessary very much at all once the machine is setup, perhaps for CHP problem determination type of thing, but I can't think of normal day to day requirements. Dana On Wed, 20 Mar 2019 22:02:21 +1300, Laurence Chiu wrote: > >Any thoughts from the group on this parallel approach. I have no idea how >often the SE needs to be accessed but this is a fairly static environment >so I would think not that often. > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Remote access to Z14 ZR1 Support Element via HMC question
This is the situation We are replacing our zBC12 with a Z14 ZR1 which is DR machine. It will connect to the same SAN as the zBC12 and we want to run the same LPAR configuration and of course the same IOCDS. Our support folks are trying to do the work remotely(externally) and are getting stuck in complex firewall rules. In particular they can reach the HMC of the zBC12 but when they try to get to the Support Element on the Z14 and try SOO (Single Object Operations) they can't connect. Firewall rules are complex of course but my questions is, why can't the support folks do all the work they need to do actually in front of the Z14 and access the HMC and SE locally? Once that work is done the machine can be IPL'ed remotely and work could continue on fixing resolving the firewall rules. We are trying to meet a deadline where we can IPL the Z14 off the existing SAN, start up some workload and perform some acceptance testing. But it seems I've been advised that the resolution of the firewall rules is on the critical path whereas I think configuring the Z14 (LPARs IOCDS etc.) cloned from the zBC12 could be done locally and that would get us a machine we could IPL. The support folks are in the city and have already visited the data centre and proven they can access the HMC and SE locally. Any thoughts from the group on this parallel approach. I have no idea how often the SE needs to be accessed but this is a fairly static environment so I would think not that often. Thanks -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
