|
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
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.