The Thin Console does not connect to i5/OS at all. It is plugged into an
Ethernet port on the Service Processor Card (where you can also access
the ASMI Web Interface).
The ports are labeled HMC1 and HMC2, and as their names imply they're
also used for HMC connections. You'll also have to configure i5/OS to
use a HMC Console when you're using the Thin Console.
(I still think that the TC is a rather poorly done product, since it
doesn't offer remote access).
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
Sent: Tuesday, July 10, 2007 1:30 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Denying TCP connections based on IP
<snip>
Hmmm I don't suppose either of you have ever entered a packet rule that
disallows access from a LAN Console by any chance ?
</snip>
You are correct that the LAN console runs on a "short stack" that is not
the same one as the full i5/OS TCP/IP stack, that said, one or both of
Larry's and Tom's solutions should be in place when testing. The Thin
Console device IBM is selling now also utilizes that "short stack".
(Very cool console for those who don't have an HMC) This is a great
reason for a tech support sandbox LPAR. Push comes to shove, restore
it. ;-) .....
midrange.com
