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 transaction arrives for it, TCP on the second LPAR will see the primary host and dynamically route the transaction to the server on the second LPAR. By making it dynamic we don't hae to worry about automation moving the VIPA, we can let TCP do that.
The second LPAR will be in the same subset as the first. Youi comment about OMPROUTE is noted. Thanks On Wed, Oct 18, 2023 at 1:05 AM John S. Giltner, Jr. <gil...@gmail.com> wrote: > 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 addresses? > > With certain setups you may need to run OMPROUTE configured for OSPF. > > I think if both LPAR's are on the same CEC and they share OSA's and the > VIPA addresses are in the same subnet as the OSA's, there is not much to > do, but to configure both TCPIP stacks with the same VIPA range and then > with PORT definitions assign what VIPA address you want that application to > use. > > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
