RE: Switching ID's -- MIDRANGE-L

I don't believe that CA even cares about the CHGNETA system name
anymore.

Instead, TCP/IP name is what it's all about.  For that, look at:

1) CHGTCPDMN.
2) Host table entries on the i5.
3) DNS server entries on all DNS servers.
4) Host table entries on the clients (hopefully you don't any anything
here ;-)

If you change SystemB's IP address and TCP/IP name to duplicate SystemA,
then you won't have anything else to do to the clients.  But you won't
be able to bring SystemA back up until you've renamed it or reset
SystemB back to its original name.

You could also consider making use of the capabilities of DNS.  For (a
simplified) example:
DNS entry for SystemA at 192.168.1.2
DNS entry for SystemB at 192.168.1.3
DNS entry for PRODSYS, alias for SystemA.

All clients use the name PRODSYS to connect to the i5.

If SystemA goes down, you change the DNS alias PRODSYS to be an alias
for SystemB instead of SystemA.

When the clients try to connect again, they will get a connection to
SystemB; as long as the clients are configure to always do a DNS lookup.


HTH,

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx 
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry Adams
Sent: Monday, October 16, 2006 10:03 AM
To: Midrange-L
Subject: Switching ID's

We have two [2] 520's.  One is production; the other is our backup 
system.  Both are single partition.  There are 20 - 30 
workstations and 
about the same number of printers.  The workstations are 
primarily PC's 
using iSeries Access for Windows; we have a few twinax workstations 
(including the system console).

So far we (knock on wood) haven't had to use the backup system for 
production.  Someone had the radical idea, however, that we actually 
needed a disaster recovery plan.  I need a little (?) help with an 
aspect of the plan.

For this phase we are assuming that the damage is isolated to the 
production box (SystemA); that there is no structural damage to the 
environs; that everything else is copasetic.  I port the 
configuration 
from SystemA to SystemB (the backup) in a save file (SAVCFG) 
automatically every night.  (Forget to mention: Both boxes 
are supposed 
to be identical in all regards.)  Security data (SAVSECDTA) is, also, 
pushed to the backup in a save file.

My question relates to user access via iSeries Access for 
Windows.  Each 
PC user's IAW is configured to identify SystemA as the system 
to which 
they will access programs and data.  Even though there are 
"only" about 
20 PC's attached this way, I would rather not set up a connection to 
SystemB and, then, change each PC to access the backup 
system.  Instead, 
I would rather change the identifier on the system (520) itself.

It looks like CHGNETA can be used to rename the systems.  Is this all 
that I need to do?  Or do I, also, need to change the IP 
address for the 
box?  I seem to remember that there is a server somewhere 
that says, "IP 
address 10.0.0.4 = SystemB" etc.  Is that the Domain Name 
Server (DNS)?  
And would I need to change that, too?

Thanks.
-- 
      * Jerry C. Adams
*IBM System i5/iSeries Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
      615.995.7024
fax
      615.995.1201
email
      jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>

-- 
This is the Midrange Systems Technical Discussion 
(MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.