Thanks Allan, The OBEY picked up the new interface. My mistake was, OMP saw that and automatically added it as well, only with incomplete information OMP deemed it a Generic. Then when I tried to add the OSPF info, it already had the partial entry. Next step is to bounce OMPROUTE this weekend. We should be okay after that.
Sent from [Proton Mail](https://proton.me/mail/home) for iOS On Tue, Aug 13, 2024 at 7:46 AM, Allan Staller <[[email protected]](mailto:On Tue, Aug 13, 2024 at 7:46 AM, Allan Staller <<a href=)> wrote: > Classification: Confidential > > V tcpip,obey,dsn= (points to new info) or combined. TCPIP will sort it out > > -----Original Message----- > From: IBM Mainframe Discussion List <[email protected]> On Behalf Of > roscoe5 > Sent: Sunday, August 11, 2024 3:50 PM > To: [email protected] > Subject: Re: Fw: Multiple VIPAs > > [CAUTION: This Email is from outside the Organization. Unless you trust the > sender, Don't click links or open attachments as it may be a Phishing email, > which can steal your Information and compromise your Computer.] > > I thought I had an answer, but no. > (Hard to test; can't IPL) > > Trying to make this clearer. > > We currently have a single VIPA and two physical INTERFACE statements, let's > say ... > > INTERFACE VIPALINK1 DEFINE VIRTUAL IPADDR 7.7.7.7 > > INTERFACE LINK0010 > > DEFINE IPAQENET > > PORTNAME T0010 > > IPADDR 10.1.1.1/29 > > SOURCEVIPAINT VIPALINK1 > > ... > > and > > INTERFACE LINK0020 > > DEFINE IPAQENET > > PORTNAME T0020 > > IPADDR 10.1.1.2/29 > > SOURCEVIPAINT VIPALINK1 > > ... > > We would like to add a second VIPA, VIPALINK2, very much like the first, > except with IPADDR 7.7.7.8. > > Do I need to create more IPAQENET INTERFACES (with or without new ports) and > give them a SOURCEVIPAINT VIPALINK2? > > Or is there any way to simply use the current existing IPAQENET INTERFACEs > and associate them with VIPALINK2? > > The obvious challenge would be, how would the app/system know which VIPA to > use? Fair question. > > One of my peers suggested that as we expect the traffic would be inbound, it > would come in on 7.7.7.8. > > Further, any session created from inbound 7.7.7.8 should go back out on > 7.7.7.8. > > Beyond the above technical question, some may want to ask why? What is tobe > gained. > > The answeris,multiple applications are using 7.7.7.7 with most unsecured. > > We intend to require ALL traffic on 7.7.7.8 be AT-TLS encrypted. > > Then test and migrate apps, independently, on to 7.7.7.8. > > Thanking in advance, > > Bob > > Sent from [Proton Mail](https://proton.me/mail/home) for iOS > > On Mon, Aug 5, 2024 at 5:22 PM, roscoe5 <[[email protected]](mailto:On > Mon, Aug 5, 2024 at 5:22 PM, roscoe5 <<a href=)> wrote: > >> Never mind, I figured it out. >> As is too often, I was making it more complicated than necessary. >> >> Sent from [Proton >> Mail](https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%25 >> 2Fproton.me%2Fmail%2Fhome&data=05%7C02%7Callan.staller%40hcltech.com%7 >> C5dc79ee51a08492db43c08dcba474ab1%7C189de737c93a4f5a8b686f4ca9941912%7 >> C0%7C0%7C638590062585827025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMD >> AiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=nK >> AskkLB6nZBOi8vHMT8tHBTv9MA%2Bo01tbORWFdHmjw%3D&reserved=0) for iOS >> >> On Fri, Aug 2, 2024 at 6:43 PM, roscoe5 >> <[[email protected]](mailto:On Fri, Aug 2, 2024 >> at 6:43 PM, roscoe5 <<a href=)> wrote: >> >>> Sent from [Proton >>> Mail](https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F >>> %2Fproton.me%2Fmail%2Fhome&data=05%7C02%7Callan.staller%40hcltech.com >>> %7C5dc79ee51a08492db43c08dcba474ab1%7C189de737c93a4f5a8b686f4ca994191 >>> 2%7C0%7C0%7C638590062585832865%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLj >>> AwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sda >>> ta=%2BUxqv6lykZHinTxWR4h8q6P%2Bmc9AABwS34dAXk70Yv0%3D&reserved=0) for >>> iOS >>> >>>> ---------- Forwarded message ---------- >>>> From: roscoe5 <[email protected]> >>>> Date: On Fri, Aug 2, 2024 at 6:39 PM >>>> Subject: Fw: Multiple VIPAs >>>> To: [email protected] <[email protected]> >>>> Cc: >>>> >>>> Hello, >>>> In our TCP/IP (z/OS 3.1) we define OSA interfaces with IP addresses, and >>>> use the SourceVipaInt to refer to a Virtual IP address/interface. That >>>> much is working fine. >>>> I want to add another VIPA IP Address, where users can continue to use >>>> applications on (for example) 7.7.7.7 or get to the same services on the >>>> new 7.7.7.8 address. >>>> The plan is to use PAgent on the new address and enforce >>>> security/encryption. >>>> >>>> My question is, in the TCPIP Profile configuration, can I assign a native >>>> (not virtual) interface to two virtual interfaces (7.7.7.7 and 7.7.7.8)? >>>> Or do I need to duplicate the native interfaces with IPAQENET, PORTNAME, >>>> IPADDR, etc., and refer these new interfaces to the 7.7.7.8 virtual >>>> address? >>>> Thanks in advance, >>>> Bob >>>> >>>> Sent from [Proton >>>> Mail](https://apc01.safelinks.protection.outlook.com/?url=https%3A%252 >>>> F%2Fproton.me%2Fmail%2Fhome&data=05%7C02%7Callan.staller%40hcltech.c >>>> om%7C5dc79ee51a08492db43c08dcba474ab1%7C189de737c93a4f5a8b686f4ca994 >>>> 1912%7C0%7C0%7C638590062585837702%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC >>>> 4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7 >>>> C&sdata=aaCtyT45wPO5Uj3ggeja%2BW5HxP2n4re2Dql5GIYadJk%3D&reserved=0) >>>> for iOS >>> >>> --------------------------------------------------------------------- >>> - 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 > ::DISCLAIMER:: > ________________________________ > The contents of this e-mail and any attachment(s) are confidential and > intended for the named recipient(s) only. E-mail transmission is not > guaranteed to be secure or error-free as information could be intercepted, > corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses > in transmission. The e mail and its contents (with or without referred > errors) shall therefore not attach any liability on the originator or HCL or > its affiliates. Views or opinions, if any, presented in this email are solely > those of the author and may not necessarily reflect the views or opinions of > HCL or its affiliates. Any form of reproduction, dissemination, copying, > disclosure, modification, distribution and / or publication of this message > without the prior written consent of authorized representative of HCL is > strictly prohibited. If you have received this email in error please delete > it and notify the sender immediately. Before opening any email and/or > attachments, please check them for viruses and other defects. > ________________________________ > > ---------------------------------------------------------------------- > 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
