Check in outq qezjoblog to see why the management central job is failing,
Maybe you aren't using QSECOFR as the user? Whenever we have management
central issues it is an expired qsecofr password.



From:
Jerry Adams <Jerry@xxxxxxxxxxxxxxx>
To:
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date:
09/09/2009 03:28 PM
Subject:
RE: Management Central Endpoint System Not Responding
Sent by:
midrange-l-bounces@xxxxxxxxxxxx



Bill,

I just double-checked and signed on to Servo with QSECOFR so it's good.

What you did is what I did - except it only half worked. The endpoint
system (Servo) won't connect under MC, but it will under the My
Connections tab.

Thanks.

Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
William.Epperson@xxxxxxxxxxxxxxxxxxxxxxxx
Sent: Wednesday, September 09, 2009 2:54 PM
To: Midrange Systems Technical Discussion
Cc: 'Midrange Systems Technical Discussion';
midrange-l-bounces@xxxxxxxxxxxx
Subject: RE: Management Central Endpoint System Not Responding


I have a similar issue when my QSECOFR password expires. I can't launch
Management Central tab. A while back I changed Management Central to
another server because my other server's Management Central job needed to
be restarted so often. So I changed servers and have been running fine
ever since.
Still no idea why it was flaky so often.

Bill Epperson Jr.
Systems Communications Analyst
Memorial Health System
(719) 365-8831





"Pete Massiello" <pmassiello-ml@xxxxxxxxxxxx>

Sent by: midrange-l-bounces@xxxxxxxxxxxx To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc
09/09/2009 12:54 PM
Subject
RE:
Management Central Endpoint System Not Responding
Please respond to
Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxx>






Jerry,

Do you have IP addresses for your Systems in the host file,
that looked like the IP address of the "Console" on each machine.

Also, check that the user profile QSECOFR has a password and
is enabled.

Pete

Pete Massiello
iTech Solutions
http://www.itechsol.com

Add iTech Solutions on Facebook:
http://www.facebook.com/group.php?gid=126431824120

Add iTech Solutions on LinkedIn:
http://www.linkedin.com/groups?gid=2206093


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry Adams
Sent: Wednesday, September 09, 2009 2:22 PM
To: Midrange-L (midrange-l@xxxxxxxxxxxx)
Subject: Management Central Endpoint System Not Responding

I cannot get one of the endpoint systems in Management Central to respond.

I noticed the other day that some iNav (Management Central) collection
jobs weren't running. Odd because they used to; I'd see the Collection
Started / Finished windows when I'd log into my PC some mornings.

Trying to fix this I went to Management Central, but it could not connect
to the central system (Servo). Again, odd because I'm sure I did that
last week. It could, however, find the system under the "My Connections"
tab; right clicking and selecting 'System Status' worked.

Okay, so I decided to change the central system to our other box (Crow).
And now I can get into Management Central. But the Endpoint for Servo
still did not work; i.e., any collection timed-out; checking PM status
fails, etc.

Okay, so I decided to delete Servo as an endpoint system. The first time
it didn't delete; the second time (an hour later) it did. Then did a
discovery of systems in the network, which is supposed to add any new ones
it finds to the Endpoint tab. Discovery did not find Servo. So I added
it manually.
Checked the Properties (right click the endpoint system name) and it shows
the correct IP address, but still no luck starting collections or viewing
the PM status on Servo. Crow, the new central point system, works fine in
Management Central.

I checked the archives and found that Vern had a similar problem back
almost exactly seven years ago. Except that in his case the IP addresses
of the systems had been changed, which is not true in my case. And I did
not see any eventual resolution to the problem. I did check the HOSTS
file in \Windows\System32\drivers\etc, which has

127.0.0.1 localhost
10.0.0.18 CROW_CONSOLE
10.0.0.19 SERVO_CONSOLE

which are our LAN consoles for the two boxes. If there's another HOSTS
file somewhere, Windows Search didn't find it.

The "Verify Connection" for Servo under the "My Connections" section
verified. No such option (that I can find) under Management
Central...Endpoint Systems...Servo. There is one for Management Central
itself, but it only verifies the central system.

The Management Central server under TCP has been started under both
systems, but just to be sure I stopped the one on Servo and restarted it.
Once via iNav and later via green screen commands.

Is there anything under CFGTCP or in iNav that I can check? Anything
else?

Thanks.

Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email: 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.




--
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 thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].