Difference between revisions of "GettingStarted"

From MidrangeWiki
Jump to: navigation, search
(Step by Step)
(Step by Step)
Line 28: Line 28:
 
# Configure TCP/IP using GO TCPADM
 
# Configure TCP/IP using GO TCPADM
 
# Install all additionally needed license programs
 
# Install all additionally needed license programs
# Install latest CUM/Group/Hiper PTFs
+
# Install latest CUM/Group/Hiper PTFs, preferably using [[Image_Catalog Image Catalogs]]
 
# Change QCCSID, QLOCALE, QDECFMT, QTIMZON etc.
 
# Change QCCSID, QLOCALE, QDECFMT, QTIMZON etc.
 
# Configure the NTP client using CHGNTPA
 
# Configure the NTP client using CHGNTPA

Revision as of 02:05, 18 September 2009

Introduction

So you just got a new Power 520, and you don't know where to start?

A lot of things have changed, and with the current console options things aren't as simple anymore.

In this example, we'll assume that you have a machine that uses Operations Console LAN attached (vulgo: LAN console). This is usually specified when ordering the machine, so that IBM will preconfigure the machine correctly.

LAN console requires the machine to be on the same broadcast domain (hub/switch topology) in order to get initial configuration using BOOTP. It is a recommended best practice to do the initial LAN console configuration using a PC that is directly attached to the system. This will exclude several environmental factors from causing errors.

Step by Step

Here's a general rundown of steps to be taken:

  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. Plan for ASMI. If you have a DHCP server on your network, ensure that a network cable is attached to HMC Port 1 before powering on your system. This will ensure that the ASMI will obtain an IP address using DHCP. If not, manually configure an IP address for ASMI using a PC directly attached to HMC Port 1, which will listen to the IP address 169.254.2.147.
  3. 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.
  4. 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.
  5. Start the LAN console connection
  6. 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.
  7. Attach power to the system
  8. Wait till the FSP has finished initialization (~2-5 minutes). This is indicated by the green power light blinking slowly.
  9. Logon to ASMI. Either use the manually configured connection per the above step, or look into what IP address your DHCP server has distributed to the system. Logon using "admin" as both username and password. Immediately change the password and logon again. You should now see all ASMI options.
  10. Press the white power button
  11. When prompted on the LAN console PC, enter "11111111" as both username and password
  12. You should new see the logon prompt. Logon using QSECOFR/QSECOFR
  13. Ensure that the system sees the UPS using DSPMSG QSYSOPR, it should say something along the lines of "uninterruptible power supply now attached"
  14. Change QUPSDLYTIM to something sensible. 300 seconds is a good start if you use the default 1.5kVA UPS and only the Power 520 is attached to it.
  15. Configure TCP/IP using GO TCPADM
  16. Install all additionally needed license programs
  17. Install latest CUM/Group/Hiper PTFs, preferably using Image_Catalog Image Catalogs
  18. Change QCCSID, QLOCALE, QDECFMT, QTIMZON etc.
  19. Configure the NTP client using CHGNTPA

Troubleshooting

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.