×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On Tue, Jun 9, 2009 at 22:54, Jeff Crosby<jlcrosby@xxxxxxxxxxxxxxxx> wrote:
So ops con has it's own TCP/IP stack?
It's indipendent from the OS, part of the LIC..
Theoretically, could my PC have a 2nd NIC, a cat5 direct to a port on the
520 (like T5), and be the console; then, if my PC takes a powder, any other
PC could take over the console so long as the ops con portion of i Access is
loaded, even if that PC has only 1 NIC?
No need for multiple NICs. It's best to use a dedicated network
connection for the initial setup (which uses BOOTP), but after that
you're free to do what you want. I usually wire the console into the
customer's management LAN, if he has one.
In case of Power6 520's, you can even share the LAN console port with
the operating system, which you can't do on systems without HEAs.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.