Re: Twinax, IP and 5250 emulation..

Chris,

        Thank You for the response, and yes this might be a solution. But
because of the nature of the business this adds another failure point to the
network and therefore is not a good solution for THIS customer.  I am still
looking for the answer for this client.

        JMS

-----Original Message-----
From: Chris Bipes <ChrisB@cross-check.com>
To: 'MIDRANGE-L@midrange.com' <MIDRANGE-L@midrange.com>
Date: Thursday, June 24, 1999 7:58 PM
Subject: RE: Twinax, IP and 5250 emulation..


>If they go to LAN and blow away the twinax can use a virtual IP address
that
>a router would send to one of the systems.  That way is one system fails,
>the router switches the traffic to the other system.  The two AS400s have
>unique IP address and can communicate using them.  You can also reach the
>AS400s with there unique IP which would be useful for administration
>purposes.  You just have to have a powerful enough router to handle the
>traffic.  We use this for people coming in through the internet.  They
never
>know, or care, what system they are really attached to.  For local users
>using CA, they will have to restart their connection in case the primary
>system fails.  I don't know all the details for setting up or
>hardware/software required but a good network administrator can do that
>part.  Good Luck,
>
>
>Christopher K. Bipes mailto:ChrisB@Cross-Check.com
>Sr. Programmer/Analyst mailto:Chris_Bipes@Yahoo.com
>CrossCheck, Inc.    http://www.cross-check.com
>6119 State Farm Drive Phone: 707 586-0551 x 1102
>Rohnert Park  CA  94928 Fax: 707 586-1884
>
>
>
>-----Original Message-----
>From: Jeffrey Silberberg [mailto:jsilberberg@mindspring.com]
>Sent: Thursday, June 24, 1999 10:14 AM
>To: MIDRANGE-L@midrange.com
>Subject: Twinax, IP and 5250 emulation..
>
>
>
>Hey All,
>
>            Have a client with two AS/400 systems tied together in a
>redundant configuration with Mimix and LAN's and all the good stuff.
>Currently on V3R7 getting ready to do to V4R[3/4]..
>
>            As part of this configuration they have about 15 workstations
on
>Twinax and a BIG switch that moves the entire operation center from the B
>Twinax controller on system-A to the B Twinax Controller on system-B.  Now,
>the issue is that it is getting hard to find Twinax emulation support that
>does all of the newer functions, so they are looking at IP options, but I
>was first wondering what people are using today for this more traditional
>configuration on high speed PCI bus Win/[98/NT] workstations.  Synapse,
>Netsoft, Full CA/400, Other ??  and what PCI bus adapters out there are
ROCK
>SOLID ??
>
>            Second, with IP on Twinax available, has anyone used this in a
>failover environment where the SWITCH is thrown and the workstations just
>reconnect to the B system.   I would assume that both the A and B systems
>would have the same IP address, and that the fail over CLP control process
>would just bring the interface online/offline.  But what about route
entries
>?  Can the same IP address be quote active on both systems with the new
>HACMP support as long as the actual workstations in the subnet can only get
>to one of the controllers. AKA the BIG switch.
>
>            Third, with LPAR and HACMP functions in 4.4 what are the rules
/
>constraints for IP address definition and failover ? Are they documented
>some where, or better yet has anyone installed and tested such a
>configuration ?
>
>            TIA,
>            Jeff Silberberg..
>+---
>| This is the Midrange System Mailing List!
>| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
>| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
>| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
>| Questions should be directed to the list owner/operator:
david@midrange.com
>+---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---