Re: Question: Operations Console via TCPIP?

[Roberto José Etcheverry Romero <yggdrasil.raiker@xxxxxxxxx>]

Another nice detail is that if you have a non-broken system which has lan
console configured and you do a type D IPL, it will take the console
without problems.
Also, DO setup the LAN console from the DST BEFORE changing console types.
i found out the hard way that 65+21 DOESNT  EXIST on v5r2 800's (I had one
configured like that and attempted to change the console to another PC; no
panel options for me).

Best Regards,



On Mon, Jul 8, 2013 at 12:28 PM, DrFranken <midrange@xxxxxxxxxxxx> wrote:

> Rene,
>
>    This connection is generally VERY reliable, much more so than the old
> serial connection. Because it depends on TCP/IP on the PC side Microsoft
> updates haven't been known to break it like with operations console.
> Additionally the same PC can be the console for many servers or
> partitions with LAN console but only 1 with the serial cable.
>
>    Remember you do not need a separate CARD for LAN console, if you have
> two ports you can use the first (upper) port on the card for LAN console
> and the second (lower) port on the card for the regular IBM i TCP/IP
> stack. Just remember the card must be a 1GbE adapter.
>
>    I do recommend that you switch to LAN console on the current
> partition before reloading.  The only issue I have had 'fun' with is if
> the system today is using Twinax or Ops Console and you try a fresh
> install using LAN console you will spend a fair amount of time on the
> front panel with 65-21 and friends because the service processor will
> try to use the current console setting. Switching NOW lets you do that
> with SST so the reload will start out assuming LAN console and you're in
> much better shape then.
>
>          - Larry "DrFranken" Bolhuis
>
> www.frankeni.com
> www.iDevCloud.com
> www.iInTheCloud.com
>
> On 7/8/2013 5:49 AM, Rene K. wrote:
> > Hi DrFranken,
> >
> > thanks for this info, gives a nice insight into the innards of i5/OS.
> > I didn't know there were two different IP stacks!
> >
> > Regarding the Operations Console over LAN: what is your experience with
> > this setup? Easy and dependable to setup, or does it require
> > voodoo-magic and planet alignment like the Direct Access method?
> > I plan to do a fresh install from D M IPL (already have the licensekeys
> > on paper), so I'm thinking about adding a second Ethernet card to the
> > system, and perform the install / administration from LAN console.
> >
> > regards,
> >
> > Rene.
> >
> >
> >
> > ------------------------------------------------------------------------
> > *From:* DrFranken <midrange@xxxxxxxxxxxx>
> > *To:* Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> > *Cc:* Rene K. <kraats@xxxxxxxxx>
> > *Sent:* Friday, July 5, 2013 4:04 PM
> > *Subject:* Re: Question: Operations Console via TCPIP?
> >
> > The thing you probably don't understand is that there is a second TCP/IP
> > stack in the system. The one we use every day all day is up in IBM i and
> > that runs as a collection of jobs mostly in QSYSWRK subsystem. Clearly
> > when the system is in restricted state due to ENDSBS *ALL or ENDSYS then
> > that subsystem is down and that TCP/IP stack is shut down. If the
> > console was connected this way it would disconnect. So now what?
> >
> > The Second TCP/IP Stack is in the Licensed Internal Code (LIC) It
> > doesn't have all the capability of the primary one and doesn't support a
> > suite of servers like FTP, DHCP, SMTP etc. It also has a limited list of
> > supported network adapters (all the ones that at GbE capable are on the
> > supported list) and it doesn't do Jumbo Frames for example.
> >
> > So as you would expect this second stack requires it's own Ethernet
> > port. It doesn't need an entire card, just one port from it. If the
> > system is partition this Ethernet card muse be required by the
> > partition. It also needs it's own IP address that is different from IBM
> > i. Generally it is in the same subnet although that's up to you.
> >
> >    To configure this first identify the port that you want to use and
> > make sure it has no Ethernet line description attached to it in IBM i
> > and certainly not varied on!  Record the Resource Name for the "Ethernet
> > Port" from WRKHDWRSC *CMN that you will use for the console connection.
> > Now enter Service Tools, take option 8 (Service tools user IDs and
> > Devices) and then press F13 (Select STS LAN adapter) If one is already
> > configured it will have a "*" in the selected column. If so you'll need
> > to understand why that is already there. Now select your adapter (option
> > 1) and enter the IP address for it as well as the mask and gateway. The
> > Host Name for Servie Tools should match what you'll use on the PC side
> > when configuring the LAN console connection.
> >
> >    One entered press F7 to store and then F14 to activate. Once activated
> > (takes about 30 seconds for some reason) you should be able to PING this
> > address from the PC you want to use for LAN console.
> >
> >    So now you have a separate TCP/IP connection to the LIC that doesn't
> > reach up into IBM i. This connection is used primarily for two things:
> > 1) The console as you're learning and 2) Virtual Optical media that are
> > hosted by another IBM i system. You can imagine that this virtual
> > optical, like the console, might need to work when the system is in
> > restricted state and over this connection it does!
> >
> >    To tell the system you intend a LAN console you'll want to next take
> > option 3 to select the console type and chose option 3 from Work with
> > Service Tools User IDs and Devices menu, Ops Console(LAN)
> >
> >    Switching from "other" to LAN console is best done this way rather
> > than playing the front panel games. This way you can assure the port is
> > available, the IP address is assigned, the network is connected, and
> > there is no mystery to switching. With the front panel you'll likely
> > have at least a couple tries at it before you get it going.
> >
> >
> >          - Larry "DrFranken" Bolhuis
> >
> > www.frankeni.com
> > www.iDevCloud.com
> > www.iInTheCloud.com
> >
> > On 7/5/2013 4:53 AM, Rene K. wrote:
> >
> >  > Hi All,
> >  >
> >  > can someone tell me how Operations Console via TCP/IP works?
> >  > I've read the PDF's, but I'm still a bit unsure about how this setup
> > works.
> >  >
> >  > Suppose I use the control panel to '65+21' the console to a LAN
> > connection, and use a 'D M' mode IPL to start from the BASE_01 CD.
> >  > Does the system then automatically present it's console via the LAN
> > card? (it's in the right slot, i checked). When trying to connect to it
> > from Operations Console, will it then use a preset TCP/IP address, or
> > does it need an DHCP server for that?
> >  >
> >  > Thanks,
> >  >
> >  > Rene.
> >  >
> --
> 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.