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.