Difference between revisions of "GettingStarted"
From MidrangeWiki
(Initial page creation) |
(→Step by Step) |
||
| Line 12: | Line 12: | ||
Here's a general rundown of steps to be taken: | Here's a general rundown of steps to be taken: | ||
| − | # Get the LAN Console PC into shape. Install System i Access V6R1, | + | # 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. |
| − | apply the latest service pack. Disable the Windows Firewall - | + | # 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. |
| − | important for getting BOOTP working. IBM doesn't seem to add the right | + | # 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. |
| − | configuration entries to the Windows Firewall. | ||
| − | |||
| − | # 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. | ||
| − | |||
| − | # 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. | ||
| − | |||
# Start the LAN console connection | # Start the LAN console connection | ||
| − | + | # 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. | |
| − | # 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. | ||
| − | |||
# Attach power to the system | # Attach power to the system | ||
| − | + | # Wait till the FSP has finished initialization (~2-5 minutes). This is indicated by the green power light blinking slowly. | |
| − | # Wait till the FSP has finished initialization (~2-5 minutes) | ||
| − | |||
# Press the white power button | # Press the white power button | ||
| − | + | # When prompted on the LAN console PC, enter "11111111" as both username and password | |
| − | # When prompted on the LAN console PC, enter "11111111" as both | ||
| − | username and password | ||
| − | |||
# You should new see the logon prompt. Logon using QSECOFR/QSECOFR | # You should new see the logon prompt. Logon using QSECOFR/QSECOFR | ||
| − | + | # Ensure that the system sees the UPS using DSPMSG QSYSOPR, it should say something along the lines of "uninterruptible power supply now attached" | |
| − | # Ensure that the system sees the UPS using DSPMSG QSYSOPR, it | ||
| − | should say something along the lines of "uninterruptible power supply | ||
| − | now attached" | ||
| − | |||
# Change QUPSDLYTIM to something sensible | # Change QUPSDLYTIM to something sensible | ||
| − | |||
# 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 | ||
| − | |||
# Change QCCSID, QLOCALE, QDECFMT, QTIMZON etc. | # Change QCCSID, QLOCALE, QDECFMT, QTIMZON etc. | ||
| − | |||
# Configure the NTP client using CHGNTPA | # Configure the NTP client using CHGNTPA | ||
| − | |||
== Troubleshooting == | == Troubleshooting == | ||
Revision as of 06:58, 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:
- 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.
- 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.
- 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.
- Start the LAN console connection
- 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.
- Attach power to the system
- Wait till the FSP has finished initialization (~2-5 minutes). This is indicated by the green power light blinking slowly.
- Press the white power button
- When prompted on the LAN console PC, enter "11111111" as both username and password
- You should new see the logon prompt. Logon using QSECOFR/QSECOFR
- Ensure that the system sees the UPS using DSPMSG QSYSOPR, it should say something along the lines of "uninterruptible power supply now attached"
- Change QUPSDLYTIM to something sensible
- Configure TCP/IP using GO TCPADM
- Install all additionally needed license programs
- Install latest Cum/group/hiper PTFs
- Change QCCSID, QLOCALE, QDECFMT, QTIMZON etc.
- 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.
