×
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.
CFGTCP from a 5250 session, 1. Work with TCP/IP interfaces You can add
new interfaces and NOT activate. When the time comes you can activate
the new interface and deactivate the old interface. Make sure you
deactivate the old system interface before you activate the new system
interface.
** or **
Operations Navigator / New System / Network / TCPIP / IPv4 or IPv6 if
you are running that / Interfaces. Add the new interface / IP address
but do not start until you shut down the old system. (On the old system
you can do the same thing.)
Nice thing = create / add IP address but not activate them. On the old
box, turn on the new IP address and end the old IP address. Then on the
new box, turn on the new IP address and turn off the old IP address.
Some things to look out for, SMTP binding to a particular IP address, IP
SEC restrictions, and other services binding to a particular IP address.
You should also update the local host tables with the new IP address /
Name of the system.
Are you running any SNA?
What I have done in the past is:
1. Reserve and create new IP address for the new and old server.
2. Start using these new IP address for all of my connections. (Don't
publish these temporary IP's.)
3. When the time comes, Old Machine, connect on new IP and shut down Old
IP.
4. New Machine, connect on temp IP and turn on new IP that used to be on
Old machine.
5. Connect new machine using old machine IP and verify everything in
working, shut down temp IP that you have been using.
Next is to get the system name with the correct IP address into DNS and
stop using local host table. You should be running an internal DNS
server for all of your clients and servers to use.
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
IWilson@xxxxxxxxxxxxxxxxxx
Sent: Wednesday, August 08, 2007 2:59 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Change The IP Address OF Our iSeries
Hi All
Firstly I hope I have the correct forum for this post.
Please bear in mind that you are advising a relatively inexperienced
administrator when it comes to iSeries administration ( I inherited the
job from the person who left - you know the scenario,)
"Who's left now that Fred has gone ?" said the finance controller (he
manages the MIS dept);
"AAhh You will do" he said pointing to me.
"But, I have no idea about and iSeries and iSeries Administration. I am
just a programmer".
"No problem" he says. "You can learn as you go along. When can you have
the new iSeries up and running live to replace the old one".
Hence this question.
Can anyone advise me on how I would go about changing the ip address of
our new i520 Express.
It has 2 IP Addresses
XXX.XXX.XXX.221 - The LAN Console
XXX.XXX.XXX.222 - This is the IP address that we use to connect all
5250
connections to and is the one we want to change.
When the time comes I wil turn the old Model 820 off, change the IP
address on teh new Model i520 and IPL it.
This will save us having to run around about 250 PC's changing host
files
and also a lot of software processes that have IP addresses embedded
into
them (DNSless ADO connections).
Any help will be most gratefully acceptedchris
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.