Re: operations console via lan

[Jack Kingsley <iseriesflorida@xxxxxxxxx>]

Eventually it will time out, after you have reconfigured everything have you
attempted to reboot the i5.

On Tue, Feb 9, 2010 at 4:18 PM, Jacob Anderson <jwa@xxxxxxxxxxxxx> wrote:

> I am the same ASMI guy.
>
> It is in T5.
>
> I don't know what the 65+21 sequence is.
>
> In manual mode, I do not have option 65. My front console only goes up to
> 43
> when in manual mode.
>
> I am aware of the isolated network configuration for the operations console
> and have chosen an IP address and subnet appropriately.
>
> I am using a direct connection to the T5 port on the iSeries.
>
> My Win2k8 is NOT configured for connection sharing and it does not have a
> DHCP role installed.
>
> Netstat shows that port 67 and 68 are operational:
>
>  UDP    0.0.0.0:67             *:*
>  UDP    0.0.0.0:68             *:*
>
> This is globbing on any interface though. So operations console doesn't
> bind
> a specific interface when it initiates the bootp protocol.
>
> -- Jake
>
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Massiello
> Sent: Tuesday, February 09, 2010 12:01 PM
> To: 'Midrange Systems Technical Discussion'
> Subject: RE: operations console via lan
>
>  Put it in T5.
>
>        Do the 65+21 sequence on the bezel to make sure that you have the
> A6xx500y where the xx is "03" for Lan Console.  Also, then keep going till
> I
> think it is an "E1" to enable Internal Ports.  Otherwise you won't get
> connected.
>
>        Now, I don't know if this is the same guy with all the ASMI issues
> last week, but you need to understand that console connection is NOT the
> same TCP/IP address that your PC Clients will connect to.
>
>        I highly recommend when doing this that you have a DIRECT cable from
> the PC to the T5 port.  This way, as you boot your 520 you can see the
> Ethernet connection on the PC going up and down (Connecting at 100mb, then
> connecting at 1G, etc).  This will know you are connected, especially when
> you have the dreaded C6004031 (looking for console).
>
>        I don't know if Windows Server is supported for Operations Console,
> I remember a while back that it wasn't.  You are the same guy, as you keep
> referring to Eth0 and that is what keeps confusing everyone on your last
> posts, as that is an HMC port name, and you will continue to confuse people
> if you use that term on this iSeries list.
>
>        The PC running Operations Console and the T5 on the iSeries must
> (REPEAT MUST) be on the same subnet during the BOOTP process when the
> client
> sends down the config to the T5 port, and the T5 ports accepts this.
>
>        Good Luck.
>
>        Pete
>
> Pete Massiello
> iTech Solutions
> http://www.itechsol.com
>
> Add iTech Solutions on Facebook:
> http://www.facebook.com/group.php?gid=126431824120
> Add iTech Solutionw on LinkedIn:
> http://www.linkedin.com/groups?gid=2206093
>
>
>
>
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jacob Anderson
> Sent: Tuesday, February 09, 2010 2:04 PM
> To: 'Midrange Systems Technical Discussion'
> Subject: operations console via lan
>
> Hello,
>
> I am trying to do the initial operations console setup for my 520 power 5.
>
> Windows Server -> v6r1 Client Access, op console version 6.1.0.0 490.6
>   LAN IP: 192.168.16.20
>   iSeries Target IP: 192.168.16.30
>   iSeries Service Name: matches the service name found in the ASMI via
> serial connection
>
> Here is what I have done:
>
> 1. Powerdown the iSeries
> 2. Unplug power
> 3. Plug in RJ45 cat6 cable from LAN port on Win server directly into T6
> (LAN
> eth0) on iSeries
> 4. Start operations console on win server
> 5. Click "connect" on my iSeries node
> 6. Plugin power to iSeries
> 7. Wait for front console panel to show SRC codes for boot, happy
> 8. Return to Win server and wait for op con to respond
>
> Nothing. Op console always says "connecting" but nothing happens. There is
> no firewall enabled on the Win server and the cables are directly attached
> and properly labeled/configured.
>
> I've tried it on both of the LAN Ethernet ports for the iSeries with the
> same result.
>
> I have waited the "20 minutes" as recommended in the op con operations
> manual (pg 51 of 128).
>
> Is there something else I need to do to setup the LAN ports, or even get
> started, so that I can run the op con on the iSeries?
>
> Note that I have mistakenly plugged in a DHCP managed network in to the
> iSeries LAN Ethernet port (eth0) in prior configuration attempts.
>
> Thanks
>
> -- Jake
>
>
>
>
> --
> 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.
>
>
> --
> 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.
>
> --
> 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.