Re: Replacing a LAN console

You can do it from sst if you've previously set the system security values
allowing this.

If they can get a console active then getting to dst is just a function 21
anyway.


On Wed, Apr 17, 2013 at 8:58 AM, Roberto José Etcheverry Romero <
yggdrasil.raiker@xxxxxxxxx> wrote:

When we talk about creating devices we are not talking at the OS-level, we
are talking at DST level, you must go to the DST (i'm almost sure you cant
do this from SST) and within the work with DST therein lies the option to
work with DST devices and you can create aditional QCONSOLEs.



On Tue, Apr 16, 2013 at 5:34 PM, Evan Harris <auctionitis@xxxxxxxxx>
wrote:

The QCONSOLE value in the profile on the PC indicates what service tools
device to use; it just happens to have the same name as the system value.

Create a QCONSOLE4 device in SST and change the profile on the new PC to
indicate QCONSOLE4 then try and connnect.

I still think you would be better served by following IBMs directions

than

trying to stumble on a solution via this list.


On Wed, Apr 17, 2013 at 7:59 AM, John McKee <jmmckee@xxxxxxxxxxxxxx>
wrote:

Based on what you have tried to get me yo understand, I would have
thought CRTDEVD, or possibly just copy the original. But, I am
looking at the description for QCONSOLE. It is attached to controller
QCTL, which is varied off. On our system, BCTL is the controlling
subsystem, and at the top of the list of workstations is DSP04, which
is the value of system value QCONSOLE.

So, how can this work? Original console can be brought up, however
briefly to look at things. Since new is to replace old, I used allt
he entries from the old console. So, how did the old one work? The
name QCONSOLE is in the profile on the pc.

I am guessing here. But, the lan console profile on the pc has
QCONSOLE in it. That gets connected to system value QCONSOLE, which
has DSP04 in it, which is vary on pending.

I thought I understood what I needed to do. But, it isn't making
sense. If I create QCONSOLE4 in SST, then recreate the console
profile on the pc to use QCONSOLE4, does that work? Is it that
simple?

John McKee

On Tue, Apr 16, 2013 at 2:26 PM, Evan Harris <auctionitis@xxxxxxxxx>
wrote:

You need to create the console in SST as it is a service tools

device.

There are a few dependencies to when/where/how you can do this

depending

on

how system values are set and what release you are on.

What device configuration command do you think you would use from any

old

workstation ?


On Tue, Apr 16, 2013 at 11:06 PM, <rob@xxxxxxxxx> wrote:

I do not think you need to go into SST to create devices and ID from

the

system console. You should be able to go into it from any

workstation

and

do this. Makes it easier when your console cannot connect. Allows

you

to

resolve the problem.


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: Evan Harris <auctionitis@xxxxxxxxx>
To: Midrange Systems Technical Discussion <

midrange-l@xxxxxxxxxxxx

,

Date: 04/16/2013 12:15 AM
Subject: Re: Replacing a LAN console
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Each PC that connects gets a "token" from the i when it connects -

this

is

meant to be a security mechanism; the system looks for this token

each

tmie
a connection is made to the same SST device.

The new PC can't connect because the security token that was

generated

and
placed on the old pc when it connected to the QCONSOLE device is not
available. When IBM reset the connection (the 65+21 stuff a week or

so

ago)
they cleared this out but it woudl have been re-created on the next
successful connection.

If the old pc is working, connect it up again and create some

additional

sst devices and sst users. Use the new device names and passwords on

the

new pc and all should be well. Henceforth use a new device name each

time

you need to create a new connection when a PC dies.




On Tue, Apr 16, 2013 at 2:16 PM, John McKee <jmmckee@xxxxxxxxxxxxxx

wrote:

This is only to be a simple replacement. One pc swapped out and
another swapped in. Last time i looked in SST, the single

QCONSOLE

was enabled. If I uncable the new pc and attach the network cable

to

the dying (not dead yet) pc, it works. Same Version of Windows.
Service pack is the same on the two computers. Same IP address -

only

one plugged in at a time. The dump taken with SST shows many

attempts

to connect with port 3100. No firewall on the pc. I keep

wondering

if I have CA installed correctly. I can't recall the option I

took.

I think tomorrow, I will either uninstall/reinstall CA or look at
modifying it.

Nothing exceedingly simple has jumped out for IBM.

John McKee

On 4/15/13, Roberto José Etcheverry Romero <

yggdrasil.raiker@xxxxxxxxx>

wrote:

John, I find it strange. Lan console is a PITA sometimes, but

not

THAT

much.
Remember a few critical points:
Each and everyone of the PCS you choose to be Lan Console create

their

own

certificates and must use separate QCONSOLE devices.
Therefore, if you have access (even for a while) to a working

console

i

recommend you go to the DST and create a bunch of QCONSOLE with

default

passwords.
Then it should only be a matter of creating a connection, using

one

of

those new qconsole devices and it should work.
You cant share qconsole devices and i believe neither you can

share

IP

addresses.
Give it a try.

Best Regards,

Roberto


On Mon, Apr 15, 2013 at 7:58 PM, John McKee <

jmmckee@xxxxxxxxxxxxxx

wrote:

Today was another headscratcher. Still does not work. I

performed a

dump for Tony and sent it to him. One issue that sticks out is
difficulty with port 3001. I can't help but wonder if I failed

to

properly install something. I can't recall the option I

selected

for

the install. Could a missing piece cause a problem with port

3001?

There is no firewall on the pc and there are no port

restrictions

on

the network. This morning, the old dying pc was started and it
worked. Then, I removed the network cable from the old pc and
attached it to the new pc. Same IP address and net mask for

both

computers. Thus my wondering if I selected the wrong option or

needed

to install something else.

Anthony wants me to install CA on a laptop and connect to

connector

T5. Purpose is to prove the network is not the issue. But,

this

is

the same network cable, just moved from one computer to

another.

Any ideas?

John McKee

On Fri, Apr 12, 2013 at 9:30 AM, Jack Kingsley <

iseriesflorida@xxxxxxxxx>

wrote:

I will add this, if your going to use multiple PC's, then

make

sure

you

are

establishing some guidelines as it pertains to the usage of

QCONSOLE

and
service tools device ID's by PC.


On Fri, Apr 12, 2013 at 9:31 AM, Jerry C. Adams <

midrange@xxxxxxxx>

wrote:

Rob is right; you need more than one device (PC) with LAN

console

ability,

and it isn't necessary to IPL the System i to do this or to

set

it

to

dedicated mode.

Personally I have a very bad memory so I documented all of

the

steps.

If

you need/want copies, email me off-list.

Jerry C. Adams
IBM i Programmer/Analyst
Who the hell was that? -Winston Churchill after Frank

Sinatra

had

come

up

and shaken his hand.
--
Home Office: 615-832-2730
email: midrange@xxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John

McKee

Sent: Thursday, April 11, 2013 2:19 PM
To: Midrange Systems Technical Discussion
Subject: Re: Replacing a LAN console

I forgot one other little detail. Currently, the new and

old

broken

LAN
consol pcs are in a room next to the room containing the i.
Despite the detail that a ping from one to the other works,

he

wanted

me to

move the pc into the room with the i, and directly attach to

connector

T5.

Light in that room isn't the best. Used to be a flashlight

there

as

well.

I could not find a T5 connector. This was to rule out a

network

issue.
But, network worked just fine until original LAN console pc

died.

Did

his

suggestion have merit?

John McKee

On Thu, Apr 11, 2013 at 2:02 PM, <rob@xxxxxxxxx> wrote:

Yeah, IPLing your IBM i to resolve a console issue, and

then

find

out
you still don't have a functioning console, is one sure

way

to

muff

up
your Monday.


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: John McKee <jmmckee@xxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <

midrange-l@xxxxxxxxxxxx>,

Date: 04/11/2013 02:52 PM
Subject: Re: Replacing a LAN console
Sent by: midrange-l-bounces@xxxxxxxxxxxx



There is a pc in the computer room. Only has 5250

emulation

on

it.

When the mess happened before, it was sufficient, barely,

to

resolve

that issue. Boss said there would be no backup or IPL

this

weekend,

to avoid a potential additional headache. The headache of

the

unknown.

John McKee

On Thu, Apr 11, 2013 at 1:22 PM, Jerry C. Adams

<midrange@xxxxxxxx

wrote:

If your boss doesn't like complications, he should love

the

multi-console

capability that Rob mentioned. We had three [3] PCs

capable

of

being

the

console at a previous employer. My boss or I could

start a

process

on

the

console and the other one would take it over right in the

middle.

Easy.

The third PC was, as Rob mentioned, mostly for backup (or

because

I

was

in

the CFO's office one day and didn't want to walk to the

other

side

of

the

building to access the console, I forget).

Short of an HMC, this is the best option available.

Jerry C. Adams
IBM i Programmer/Analyst
I think that the free-enterprise system is absolutely too

important

to

be

left to the voluntary action of the market place. -

Congressman

Richard Kelly (FL)
--
Home Office: 615-832-2730
email: midrange@xxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of

John

McKee

Sent: Wednesday, April 10, 2013 2:01 PM
To: Midrange Systems Technical Discussion
Subject: Re: Replacing a LAN console

I gathered I could, based on the screen inquiring if I

wanted

to

take
control. Issue then becomes a matter of communication.

The

system

is almost totally unmonitored. No dedicated people to

serve

as

"operators".

So even knowing who will be operating is a bit of a

challenge.

The boss would not want to complicate things too much.

He

also

functions as

an operator every other weekend doing backups. It is all

very

strange.

But, this is on a prolonged death spiral. May be running

another

year.

I was wondering about the sequence of buttons I pushed to

clear

"something"

on the i that prevented the current console from

connecting

after

I

trashed

the config and rebuilt it exactly as it was. Whay was

that

an

issue?

What

was going on? Will multiple consoles cause a repeat?

The

last

is

important

especially since I have no idea who will be using the

console.

John McKee

On Wed, Apr 10, 2013 at 1:50 PM, <rob@xxxxxxxxx> wrote:

Did you know that you can have more than one device be

your

Lan

Console? I strongly recommend loading it on more than

one

PC.

This
way if one dies, you can use the other. Or, if you're a

two

person
IT shop, load it on both you and your coworker's laptop.
Granted, with HMC, it's been awhile since I've used Lan

Console.

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: John McKee <jmmckee@xxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion

<midrange-l@xxxxxxxxxxxx>,

Date: 04/10/2013 02:43 PM
Subject: Replacing a LAN console
Sent by: midrange-l-bounces@xxxxxxxxxxxx



I used the wrong term last week. It was NOT an OPS

console.

It

is
LAN console.

After getting the thing to work last week, I come in

this

morning

to
see that the thing had died. I don't know why it needed

to

be

rebooted, but Windows had a problem finding a DLL. Many

reboots

later, I saw that different pieces were mysteriously

"missing".

For the moment, it is working. It is an MPC. Looks

like

a

bloated
LCD display, but it is computer built into a monitor. I

tried

to

get into BIOS setting, with intent of running SpinRite.

I

believe

I
will pass on that.

Boss wants it replaced, and there is a much newer

computer

available.

Point of this post, if somebody reading this has not

given

up,

is

confusion I have. After I deleted the LAN configuration

from

the

pc, which Windows had no problem doing, I built a new

console

,

per
request from IBM. Initially, Windows would not allow

the

new

configuration to be stored. Had no issue with me

deleting a

configuration. Seems odd. But, anyway, new

configuratio

was

finally stored. Console would not connect to the i.

But,

this

time, an error popped up which Tony knew how to fix. It

involved

going to the i front panel and entering a number of

codes.

I

can't
remember what they were. Seem to remember one sequence

being

repeated maybe eight times.

Ok, during start of the current LAN console, there is a

point

where
the option to take control is presented.

My issue is what the heck was I clearing on the i and is

that

a

factor in replacing the console computer?

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


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

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

--

Regards
Evan Harris
--
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.

--

Regards
Evan Harris
--
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.

--

Regards
Evan Harris
--
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.

--

Regards
Evan Harris
--
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.