Rob,
Yes, I did, and it worked. What's funny is that I actually saw that page
from my "Googling" for a solution. I just missed that line, twice. The
second time was when you suggested that page. I looked it over when you
suggested it and then sent my first email. I went back and scanned it more
closely and caught it the third time through. It would be nice to
highlight that line a little more boldly in the future. Put a header on
that field since it doesn't have anything to do with the section above it.
Thank you,
William G. Epperson Jr.
Systems Communications Analyst II
2420 East Pikes Peak
Colorado Springs, CO 80909
Office: 719-365-8831
E-mail: william.epperson@xxxxxxxxxxxxxxxxxxxxxxxx
Website: www.memorialhealthsystem.com
From: rob@xxxxxxxxx
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 09/16/2011 10:35 AM
Subject: Re: Screwy Central System connection...
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Did you do this from the wiki?
Fix your Management Central server by CALL QSYS/QYPSCONFIG
PARM('QYPS_HOSTNAME' 'aa.xx.yy.zz') where 'aa...' is your new IP address.
Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: William.Epperson@xxxxxxxxxxxxxxxxxxxxxxxx
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 09/16/2011 11:53 AM
Subject: Re: Screwy Central System connection...
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Rob,
I did hard code it the with the correct IP information on my desktop. It's
not in DNS, it's only a temporary thing while I decommission the old
server. I did not want to put it in DNS, so I added it to my hosts file
on
my XP desktop to map via name. I've even tried mapping to that server via
IP only and I get the same result. Which is how I had it originally,
until
I hard coded the name/IP in my local hosts file. I thought it might have
been something stuck in my iSeries access suite, so I reinstalled that as
well.
I checked everything from your first email as well. I've ran through all
of the TCP/IP config's and DSPNETA all shows the new name. The old IP
doesn't even exist as an interface anymore. The only thing that still
exists is the original MAC address that was previously assigned to that
original IP. But that changed back in May to the new system. Like I
said,
I have crawled through this system and through iSeries access suite, and I
cannot figure out why it insists on pulling down the wrong IP during the
verification phase. I have checked the server that's listed at Memo2 and
it is in fact the old system. It just does not like the verification to
make it the central system. I've added it into WRKRDBDIRE so that I can
test BRMS information between the systems. That's all working fine. We
had considered making this another test system, so that's why I did that
portion. The verification IP info is the only error I can find that is
pointing me to why it will not let me run *MGTC correctly and make it a
Management Central server. I can't find it in the job log, because
everything shows that it was started fine, at least it looks right to me.
Thank you,
William G. Epperson Jr.
Systems Communications Analyst II
2420 East Pikes Peak
Colorado Springs, CO 80909
Office: 719-365-8831
E-mail: william.epperson@xxxxxxxxxxxxxxxxxxxxxxxx
Website: www.memorialhealthsystem.com
From: Jack Kingsley <iseriesflorida@xxxxxxxxx>
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxx>
Date: 09/16/2011 07:28 AM
Subject: Re: Screwy Central System connection...
Sent by: midrange-l-bounces@xxxxxxxxxxxx
You don't have this on your desktop hard coded in a host file possibly.
On Fri, Sep 16, 2011 at 7:47 AM, <rob@xxxxxxxxx> wrote:
There's a tip specifically for Management Central at
http://wiki.midrange.com/index.php/Change_IP_Address
Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: William.Epperson@xxxxxxxxxxxxxxxxxxxxxxxx
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 09/15/2011 07:45 PM
Subject: Screwy Central System connection...
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Anyone,
I have the weirdest problem with a Management Central server. I am
trying
to configure an older system, that I had to change names and IP's on.
This
old i520 was replaced with a new Power720. The system was cut over to
the
new hardware and the new system kept the old IP and hostname. Now I'm
trying to grab graphs and run a backup off of this older box before
powering it off. When I try and verify Central System Connection. I
get
the following lines:
Successful - 10.7.10.59 is at release V6R1M0.
Successful - System i Navigator is at release V7R1M0.
Successful - the Management Central server is running.
Successful - host name: 10.7.10.29 IP address: 10.7.10.29 was verified.
Successful - ...you get the idea.
It completes without issue. Why is this system insisting on keeping
it's
old IP for Management Central configuration. I have removed and
reinstalled my iSeries Access for Windows installation. I have crawled
through the configuration on the old i520, and no where does it still
have
10.7.10.29 on it anywhere. The name is different, IP controllers are
different. I've deleted the old TCP connections using 10.7.10.29 on it.
Where is this configuration stuck at. I have searched the web up and
down
and I cannot find this "hidden" configuration that is plaguing me. I'm
now
wishing I hadn't canceled my maintenance on this stupid thing last
month.
This server is getting closer and closer to getting an "Office Space"
going
away party.
Thank you,
William G. Epperson Jr.
Systems Communications Analyst II
2420 East Pikes Peak
Colorado Springs, CO 80909
Office: 719-365-8831
E-mail: william.epperson@xxxxxxxxxxxxxxxxxxxxxxxx
Website: www.memorialhealthsystem.com
--
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.
--
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.
--
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.
--
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.
--
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.
midrange.com
