O.K. just saw you have made progress and know what you need to do.
One other think is to update your OSPF parameters so that any dynamically added
VIPA in the future is treated as a OSPF interface. That way you don't have to
update OSPF.
On Tue, 13 Aug 2024 07:14:32 -0500, John S. Giltner, Jr
The message means that OMPROUTE can't find the interface VIPALINK2, so I would
display your home address list to make sure that it shows up in the list as
address 7.7.7.8 and named VIPALINK2.
I would also need to see the OSPF definition for VIPALINK2.
On Mon, 12 Aug 2024 13:51:18 +, roscoe5
Classification: Confidential
Firewall isue?
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
roscoe5
Sent: Monday, August 12, 2024 8:51 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Multiple VIPAs
[CAUTION: This Email is from outside the Organization. Unless you
Just an FYI - lesson learned if anyone cares. I had planned to dynamically add
the new interface in both the PROFILE dataset and in OMPROUTE.
It turns out the order is very important, and I Assumed wrong.
I did the Obey on the Profile first, which caused OSPF to learn partial info.
It dynamically
My main problem was, I tried to use an OBEYFILE command to refresh OMPROUTE. I
believe I should be using a MODIFY. F OMPROUTE,RECONFIG
I’m not yet 100% there, but past my original questions.
Thanks for your help
Sent from [Proton Mail](https://proton.me/mail/home) for iOS
On Mon, Aug 12, 2024 a
HI
I use only one static Vipa / lpar
but we have some dynamic VIPAS for each application (FTP, CICS, DB2 and
so on..)
it works fine.
regards
Wolfgang
Am 12.08.2024 um 15:51 schrieb roscoe5:
Thanks again.
I understand it’s a routing issue and I added a matching OSPF_Interface where
the
Thanks again.
I understand it’s a routing issue and I added a matching OSPF_Interface where
the original one was defined, using the new IP and Destination Address.
But when I issue the OBEYFILE command I get “EZZ7871I NO MATCHING INTERFACE
STATEMENTS FOR 7.7.7.8 (VIPALINK2)”.
My gut instinct keep
O.K., that is a routing issue. You need to look at your OSPF parameters and
verify that you are setup to advertise 7.7.7.8 to your neighbors. If your
not, then you need to update you OSPF parameters to advertise it and go from
there. No matter what you may want to check with whomever handles
John,
Thanks for your time and the thorough response. I’m not too concerned about the
applications, but your comments confirmed what I thought in that area.
One quick test failed to work in the OSPF space (did not recognize the new IP
address). However, I think I’ll have another test opportunity
You should only need to add a new VIPA:
For all traffic that is initiated to your system, they just specify the
destination IP address 7.7.7.8, or create a DNS entry that resolves to that
address and have them use that host name.
For most of traffic the that you initiate outbound I would look
10 matches
Mail list logo
