Re: TCP Problem with DR system

Kinda coming in the tail end but is this a "let's scratch the backup
system and rebuild it from the main system" kind of scenario?
Going to involve a DSPNETA and verifying EVERYTHING. Like page down to
the third screen of DSPNETA and check the value of "Network server
domain".
CFGTCP verify:
1. Work with TCP/IP interfaces. Are they using the IP addresses of the
primary, or backup machine? Are they 'active'?
2. Work with TCP/IP routes. In our standards, if your primary system is
10.17.6. something and your backup is 10.10.6.something then your default
route on the primary is going out 10.17.6.1 and the default route on your
backup is going out 10.10.6.1.
10. Work with TCP/IP host table entries

See also
http://wiki.midrange.com/index.php/Change_IP_Address

Make sure your WRKRDBDIRE entries are correct. Big time major thing with
remote journalling. And there's a real trick to setting this up and
having switches work and have odbc connections actually work during the
switch.





Rob Berendt