Re: V5R2 Console Recommendations -- MIDRANGE-L

No prob.

The console is in a subnet by itself with the iSeries, it's not part of any Ethernet or TokenRing stuff. That's why the addressing problem - if your internal addresses are 192.168.0.x, then your PC thinks there are 2 subnets with the same scheme. Like having 2 interfaces on iSeries that are defined the same - can't do it.

So recovery is not dependent on routers, etc. The problem of disconnecting the cable is, when you do this at the 400, it seems to lose touch with reality. Disconnect at the PC is not a problem - we actually use a 4-to-1 DB9 switchbox to go between our phone system,. DSL modem, and 2 OpsConsoles on the 270s.

To have 2 consoles to a system requires the LAN console, I think, which uses up a network card on the 400. Or you could try Remote Desktop (easy if the console PC is XP) or pcAnywhere, as Rob mentioned.

Also, you can use only 1 serial port for an OpsConsole. We can use 1 PC for this, because we have that switchbox. But we have to disconnect the one before starting the other.

HTH
Vern

At 03:22 PM 2/10/2004 -0500, you wrote:

Thanks for the info, Vern. Especially the tip about the addressing.

Does the console recover well (reliably and/or without human intervention)
from network problems (router, switch, etc)  between the console PC and the
iSeries, or would this fall under your note #2?

Can I have more than one console on a system, i.e. PC in the computer room
and PC at my desk?

Thanks,
-Marty

------------------------------

date: Tue, 10 Feb 2004 13:48:02 -0600
from: Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>
subject: Re: V5R2 Console Recommendations

Marty

I'm using the latest OpsConsole (V5R2) against our V5R1 and V5R2 270s. Also
using PCOMM's Async Console against our V3R7 150. Everything works great
now, once a couple things are done and observed.

1. If the iSeries is on your internal network (192.168.x.x type addresses),
make sure that you do NOT use 192.168.0.0 subnet mask 255.255.255.0 for
your internal network - OpsConsole insists on grabbing that whole thing. We
use 192.168.1.0

2. Try not to disconnect the cable - this can mess the thing up, I've used
a *FULL IPL to have the machine rebuild device info - don't know if that's
really what's going on, but it has worked.

HTH
Vern
_______________________________________________
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.