×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
heh, on our Mimix machines we have remote journalling all going through a
separate route. Very typical.
Line Type Text
LANLINMX *ELAN Mimix: GB Ethernet line
LANLINSYS *ELAN Lan line connecting GDISYS to others
CMN03 & CMN14
Internet Subnet Line Line
Address Mask Description Type
10.17.6.128 255.255.254.0 LANLINSYS *ELAN
10.17.6.129 255.255.254.0 LANLINSYS *ELAN
10.17.6.130 255.255.254.0 LANLINSYS *ELAN
10.17.6.131 255.255.254.0 LANLINSYS *ELAN
10.17.252.191 255.255.254.0 LANLINMX *ELAN
Route Subnet Next Preferred
Destination Mask Hop Interface
*DFTROUTE *NONE 10.17.6.1 *NONE
10.10.252.0 255.255.254.0 10.17.252.1 10.17.252.191
When you consider in a failover you want to drop the 'normal' IP addresses
in order to fail over the users to the backup machine but you want to
leave remote journalling going for catch up and be ready to do the switch
back.
And if you have two machines, PRIMARY and BACKUP and your users only know
them by the name PRODUCTION, but your client access sessions for high
level systems people like you go to PRIMARY and BACKUP instead of
PRODUCTION can you see how your sessions might work? You're going into
the backdoor for replication.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
