Perfect, thank you! Thomas Ambros zEnterprise Operating Systems zEnterprise Systems Management 518-436-6433
-----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Tom Brennan Sent: Monday, October 17, 2022 18:26 To: [email protected] Subject: Re: z16 ETS setup question - where's the best documentation? WARNING: This email originated externally. Exercise caution. Think before clicking links or opening attachments. On a z16 I'm involved with I noticed the Customized Planning Aid has a section on ETS, including this paragraph: "External Time Source (ETS) IP network considerations: For redundancy and resiliency, The IP addresses ETS1 and ETS2 must be configured on different subnets. When planning the Ethernet based External Time Source network, it is required that two separate subnets corresponding to ETS1 and ETS2 are routable to the desired NTP/PTP time source(s)." And maybe there's more in that chapter that might help. To get the planning aid (if you don't know), logon to Resource Link, go to the z16 section, find "Customized planning aids" and there you have to order the document for your machine and download it an hour or so later. On 10/17/2022 1:03 PM, Ambros, Thomas wrote: > We've been looking but haven't been finding. > > What has us puzzled is the ETS/STP interface setup on the SE. The machine is > on a /24 vlan. If we try to define each ETS LAN Adapter with an IP address > and interface subnet mask where the IP addresses are in the same subnet there > is an address conflict and the second configuration can't be saved. So we > defined subnet masks that worked as a subset of the /24 vlan and keeping the > two IP addresses in their own range we were able to save the ETS LAN Adapter > configs: > > ETS1 10.xx.xx.2 mask 255.255.255.0, ETS2 10.xx.xx.3 mask 255.255.255.0, > conflict. > > ETS1 10.xx.xx.2 mask 255.255.255.192, ETS2 10.xx.xx.66 mask 255.255.255.192, > no conflict. > > That sort of makes sense. I probably will go back in and change the subnet > mask so we move the second IP address nearer the first just to be tidy but it > isn't necessary because there's nothing on that entire vlan except the z > machines. > > However, there is a single selection for the default gateway - you can choose > ETS1 or ETS2. It made sense that we'd use ETS1 and the default gateway of > 10.xx.xx.1 which matches up to the vlan. That works. Just for fun we > changed off that definition and sure enough the STP network's ETS > connectivity test failed. Default gateway must match the vlan. > > The single interface for the default gateway leaves us puzzled. If ETS1 > fails for some reason, we think we're going to have to go in and reconfigure > ETS2 to maintain our timer network. We can't be thinking right. > > Has anybody encountered good documentation on the setup, better than Redbooks > like the Server Time Protocol setup guide that mention in passing that things > have changed but don't specify how? The z16 Tech Guide doesn't appear to > have any good info, either, unless I am totally overlooking it. > > Thomas Ambros > > > > > KeyCorp Public > > This communication may contain privileged and/or confidential information. It > is intended solely for the use of the addressee. If you are not the intended > recipient, you are strictly prohibited from disclosing, copying, distributing > or using any of this information. If you received this communication in > error, please contact the sender immediately and destroy the material in its > entirety, whether electronic or hard copy. This communication may contain > nonpublic personal information about consumers subject to the restrictions of > the Gramm-Leach-Bliley Act. You may not directly or indirectly reuse or > redisclose such information for any purpose other than to provide the > services for which you are receiving the information. > > 127 Public Square, Cleveland, OH 44114 > > If you prefer not to receive future e-mail offers for products or services > from Key, send an email to mailto:[email protected] with 'No Promotional > E-mails' in the SUBJECT line. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
