Re: Dev LPAR is down

Images are stripped. What is the alarm code, A900 something?


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
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: Richard Reeve <rjrjr64@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 01/13/2016 11:21 AM
Subject: Re: Dev LPAR is down
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Dev still shows an alarm (Contact lost with device).

[image: Inline image 1]

Thanks for being so patient. I truly appreciate it.

On Wed, Jan 13, 2016 at 11:10 AM, <rob@xxxxxxxxx> wrote:

Someone may have configured a virtual lan connecting these two lpars
together without having to go through the wire.
There's a lot of benefits to that:
- Backbone ethernet speeds.
- Reduced load on the lan
- Security of the data is not compromised by flowing through the office.
and more
The drawback in our shop is that if we drop PROD and production is now
running on MIMIX then it's harder to get DEV to recognize this new

route.

But I think that varying on the line, starting the interface, etc should
all apply the same.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
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: Richard Reeve <rjrjr64@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 01/13/2016 10:56 AM
Subject: Re: Dev LPAR is down
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



The message was received when trying to pass thru to dev from prod.

Does this offer a clue as to what is wrong?

[image: Inline image 1]

I checked everything that you suggested and it all looked good. How

would

I attempt to make the line active for DEV?


On Wed, Jan 13, 2016 at 10:44 AM, <rob@xxxxxxxxx> wrote:

Where are you getting "Route to specified location not found"?

On your production lpar trying to get to your development lpar?
On your development lpar trying to get to your production lpar?

Normally when you get such a message you should check
CFGTCP
2. Work with TCP/IP routes

At a bare minimum you should have something like
Route Subnet Next Preferred
Destination Mask Hop Interface
*DFTROUTE *NONE 10.17.6.1 *NONE

where '10.17.6.1' is a router on the same subnet as your 'from' lpar.

For

example if DEV is 10.17.6.45 and PROD is 10.10.8.121 then I should

have

a

default route on DEV for 10.17.6.1 and a default route on PROD of
10.10.8.1 providing I follow the naming conventions of having the

router

be a '1' on that subnet.
It is highly unlikely that an IPL removed this route from the table.
What MAY be happening is that the line is down, or your default

interface

is not started.
Let's take option 5 on that *DFTROUTE.
See "Preferred binding interface . . . . . : *NONE"?
Now let's try
NETSTAT *IFC

One, these should be active
Internet Network Line Interface
Address Address Description Status
10.17.6.178 10.17.6.0 LANLIN Active
127.0.0.1 127.0.0.0 *LOOPBACK Active

And, two, WRKCFGSTS *LIN should show the line active and TCP doing
'something' with that line
Description Status -------------Job--------------
LANLIN ACTIVE
LANLINET ACTIVE
LANLITCP ACTIVE QTCPWRK QSYS 202283

If not, you've got one muffed up startup program. You need to get tcp
started and disks varied on at startup.
You might want to forego the dream of that AS/400 that was stuck in a
closet and ran for years and think about IPLing on a periodic basis

just

so you can remember the startup procedures. Be a good time to apply

PTF's

and whatnot also.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
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: Richard Reeve <rjrjr64@xxxxxxxxx>
To: Midrange Systems Technical Discussion

<midrange-l@xxxxxxxxxxxx>

Date: 01/13/2016 10:33 AM
Subject: Re: Dev LPAR is down
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Thanks for that piece of advise Rob. The drives have been varied on

and

I'm now getting 'Route to specified location not found'.

Any ideas?

Thanks again.

Rich

On Wed, Jan 13, 2016 at 10:16 AM, <rob@xxxxxxxxx> wrote:

I understand you had a recent IPL.
Is your development lpar hosted by your production lpar? If so, you

may

wish to do the following on your production lpar:
WRKCFGSTS *NWS
And varyon the support for the disk drives on your development lpar.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
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: Richard Reeve <rjrjr64@xxxxxxxxx>
To: Midrange Systems Technical Discussion

<midrange-l@xxxxxxxxxxxx>

Date: 01/13/2016 10:02 AM
Subject: Dev LPAR is down
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



All,

I am not able to communicate with my DEV LPAR and am at a loss

as

to

what to do. The ref code is telling me to do the following;

*If you are working from the HMC:*

1. These need to be updated for the new HMC UI....
2. In the Navigation Area, open the Service Applications folder.
3. Select Service Focal Point.
4. In the contents area, select Service Utilities.
5. In the Service Utilities window, select the system you are

working

on.
6. Select Selected > Operator Panel Service Functions.
7. Select the logical partition, and then select Partition

Functions.

8. Select Disk Unit IOP Reset/Reload (67).
9. Wait 10 minutes.

My concern is that resetting the disk unit IOP may affect my

production

LPAR. On top of that, I don't see a Service application folder.

Do any of you have any thoughts on this. I am just hesitant to do
anything
as I am not familiar with the HMC. Does the managing system show an
attention light because the DEV LPAR does?

Thanks for any advise/help that you may offer.

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.


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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.


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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.


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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.


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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.