× 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.



Couldn't the 65-21 scenario be avoided by doing a manual IPL and looking in
SST to see what the console type is set to during the first boot process or
is it a guessing game whether you do a normal or manual IPL the first time.

On Thu, Sep 17, 2009 at 1:38 PM, <rob@xxxxxxxxx> wrote:

Good steps. Yes, get the latest service pack at
http://www-03.ibm.com/systems/i/software/access/windows/casp.html
Lack of that was a show stopper for me.
Yes, disable the firewall (until initial setup is done and the broadcast
data is done).
Didn't do the direct cable. Don't know if this is needed. But if
following these power on instructions EXACTLY prevents the 65-21 follies
I'm all for it. Oops, probably won't - I see your comments after step 17.
I got a reply off list that IBM shipped a lot of these systems configured
for HMC when they shouldn't have been. You can google as recommended by
Lukas but don't be afraid to call IBM and just have them step you through
it.


Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From:
Lukas Beeler <lukas.beeler@xxxxxxxxxxxxxxxx>
To:
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date:
09/17/2009 01:26 PM
Subject:
Re: Hooking up and starting a 520
Sent by:
midrange-l-bounces@xxxxxxxxxxxx



On Thu, Sep 17, 2009 at 19:00, James H. H. Lampert
<jamesl@xxxxxxxxxxxxxxxxx> wrote:
Can somebody point me to the manual I'm looking for?

Well, i'd be happy to. But using Google, i didn't a definitive guide
for all the steps required. All i can tell you is that the documents
that come with the system are not sufficient.

Here's my general plan on what you need to do get a machine up and
running.

1) Get the LAN Console PC into shape. Install System i Access V6R1,
apply the latest service pack. Disable the Windows Firewall -
important for getting BOOTP working. IBM doesn't seem to add the right
configuration entries to the Windows Firewall.

2) Configure the PC for a static IP adress. Add the appropriate LAN
console configuration, make sure to get the serial number and all that
stuff right.

3) Attach the PC to the Ethernet Port 1 of the System. NOT on the HMC
ports, but on the first port of the GX+ card. Ensure the PC is
directly connected to the system. The PC will not have link until
after i5/OS is being loaded, but make sure that the cable you have is
working. Crossover cabels are not needed.

4) Start the LAN console connection

5) Attach the UPS relay cable to the system. I believe it's serial
port number 2, but i'd have to have the system in front of me to tell.

6) Attach power to the system

7) Wait till the FSP has finished initialization (~2-5 minutes)

8) Press the white power button

9) When prompted on the LAN console PC, enter "11111111" as both
username and password

10) You should new see the logon prompt. Logon using QSECOFR/QSECOFR

11) Ensure that the system sees the UPS using DSPMSG QSYSOPR, it
should say something along the lines of "uninterruptible power supply
now attached"

12) Change QUPSDLYTIM to something sensible

13) Configure TCP/IP using GO TCPADM

14) Install all additionally needed license programs

15) Install latest Cum/group/hiper PTFs

16) Change QCCSID, QLOCALE, QDECFMT, QTIMZON etc.

17) Configure the NTP client using CHGNTPA

If after 8 the system hangs with a A900 2000 (i believe), you either
did something wrong or IBM shipped the system with the wrong console
configuration. Google for "procedure 65 + 21" for a solution.

--
Read my blog at http://projectdream.org
--
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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.