AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DVIPA question
[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.]
Some situations m
On Mon, 23 Oct 2023 11:51:04 +, Allan Staller wrote:
>I agree, the secondary application must be running on the other LPAR.
Don't say "must" because every situation is different and every situation has
defined limitations. The OP said their app cannot run in standby mode.
The majority of
nal Message-
>From: IBM Mainframe Discussion List On Behalf Of
>Jon Perryman
>Sent: Friday, October 20, 2023 11:41 AM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: DVIPA question
>
>[CAUTION: This Email is from outside the Organization. Unless you trust the
>sende
nt: Friday, October 20, 2023 11:41 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DVIPA question
[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 compr
On Fri, 20 Oct 2023 11:55:17 +, Allan Staller wrote:
> The difference iis n starting/stopping the application is a service
> interruption to the end user.
> The DVIPA activate/deactivate would be seamless to the end user
DVIPA activate/deactivate isn't seamless. First, it would require the
FYI, this is more than the OP needs to know to solve his problem.
On Fri, 20 Oct 2023 06:06:33 -0500, John S. Giltner, Jr.
wrote:
>Correct, it's not a "full router", it can route traffic to a specific LPAR if
>the IP address as been registered.
IBM says "not a full router" because they
Mainframe Discussion List On Behalf Of Jon
Perryman
Sent: Thursday, October 19, 2023 1:28 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DVIPA question
[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
Correct, it's not a "full router", it can route traffic to a specific LPAR if
the IP address as been registered. If it has not been registered any packets
received when a non-registered (unknown to any LPAR) address it will be
dropped, unless you have defined one of the OSA's as a "PRIMARY
On Thu, 19 Oct 2023 06:59:43 -0500, John S. Giltner, Jr.
wrote:
>There is a Share presentation called "Getting the most out of your OSA (Opens
>Systems Adapter)"
> that does a much better job of describing how the OSA works than I can.
I only did a quick scan of the presentation. It says
On Thu, 19 Oct 2023 12:08:04 +, Allan Staller wrote:
>That is not correct. The DVIPA and be started/stopped in a specific TCPIP
>instance.
>IIRC, the commad is something like V TCPIP,,SYSPLEX,ACTIVATE,DVIPA=xx.xx.xx.xx
>There is also a DEACTIVATE parameter as well.
John Giltner says he
and it has been
several years since I have been in the environment.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Jon
Perryman
Sent: Wednesday, October 18, 2023 10:58 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DVIPA question
[CAUTION: This Email is from outside
There is a Share presentation called "Getting the most out of your OSA (Opens
Systems Adapter)" that does a much better job of describing how the OSA works
than I can.
On Wed, 18 Oct 2023 22:58:15 -0500, Jon Perryman wrote:
>On Wed, 18 Oct 2023 17:18:33 +, Allan Staller
>wrote:
>
On Wed, 18 Oct 2023 17:18:33 +, Allan Staller wrote:
>Agreed, however it seems the OP is operating in a "toggle-plex" i.e. either
>LPAR A is running or LPARB is running. In this case, the DVIPA would be
>deactivated on one of the LPARS and switched manually via the V TCPIP command
>to
On Wed, 18 Oct 2023 11:50:21 -0500, John S. Giltner, Jr.
wrote:
>When TCPIP on z/OS allocates a IP address that address is registered in the
>OSA
> so that the OSA has a list of every IP address that is open and which LPAR it
> is opened on.
This tells us that in addition to SNA, the OSA
M-MAIN@LISTSERV.UA.EDU
Subject: Re: DVIPA question
[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.]
If the VIPA is set correctly,
I'll try to explain this as best as I can, but this can get confusing and this
is based on my understanding. We do have DB2 setup in Data Sharing and
configured using SYSPLEX distributor, which some of the configuration is
similar.
When TCPIP on z/OS allocates a IP address that address
On Wed, 18 Oct 2023 08:45:52 +1300, Laurence Chiu wrote:
>That is exactly the situation, The second LPAR will be on the same CEC as
>the first, share OSA adapters and be in a sysplex with XCF being the
>mechanism to share the VIPA information.
Since I've never seen an OSA, I must assume that
the message traffic.
Art Zeigler
From: IBM Mainframe Discussion List on behalf of
Laurence Chiu
Sent: Tuesday, October 17, 2023 3:45 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DVIPA question
That is exactly the situation, The second LPAR will be on the same
That is exactly the situation, The second LPAR will be on the same CEC as
the first, share OSA adapters and be in a sysplex with XCF being the
mechanism to share the VIPA information. From my reading of the docs, when
the server application on the primary LPAR is shutdown, and an incoming
In addition to everything Jon has stated a few other questions may help figure
out what needs to be done, or not done.
Are both LPARS on the same CEC?
If both LPARS are on the same CEC, do they share OSA's?
Are the IP addresses you plan to use as VIPA's in the same subnet as the OSA's
IP
On Tue, 17 Oct 2023 16:00:56 +1300, Laurence Chiu wrote:
>We have one LPAR with static IP
You are saying:
LPAR 1 has static IP address 192.168.40.70
LPAR 2 has static IP address 192.168.40.71
> and a server on that LPAR
"on that LPAR" is wrong. You actually mean:
You have a server
I am probably not understanding it correctly either.
We have one LPAR with static IP and a server on that LPAR that supports
both internal and external clients. We want to duplicate that server
application on a second LPAR and they will be in a sysplex. If the first
LPAR goes goes down, we want
You're confusing dynamic IP addresses with dynamic VIPA. I've never seen DVIPA
use dynamic IP addresses.
A static IP address is an address that doesn't change. Many people incorrectly
assume it's assigned to a specific machine. You decide how this IP address is
used.
Talk with your IBM
I am having a debate with a network person (but not z/OS) how DVIPA works.
We have a LPAR with static IP which many hosts and firewalls know about it.
I want to make this host part of a sysplex and so need to make certain IP
addresses/ports dynamic so they can be switched to the second LPAR if the
24 matches
Mail list logo
