===== SGI support =====
[[https://support.sgi.com/apps]]
username stedwar1
password 3397156
password Mooney12!
===== ericjohnson =====
August, 2010 Suse Activation problems again.
Engineer assigned: David Boise (without the ee sound at the end), 800 800 4744 Case 2825646
===== Base OS Install (Suse 11) =====
==== Novell ====
[[http://www.novell.com]]
username stedwar1
password name and number
To get the SLES installation media, go to
[[http://download.novell.com]]
In the product search drop-down, select Suse Linux Enterprise Server
=== connecting to the serial console ===
== Serial port configuration ==
Baud rate: 38400,N,8,1
minicom port: /dev/ttyS0
Don't use a Tripp-lite cable!
== xterm to serial port ==
I used SL5.3 on a laptop.
cu is needed on the client terminal
yum install uucp
with the serial cable connected to the laptop,
xterm -sb -en UTF-8 -geometry 130x40 -e "cu -s 38400 -l /dev/ttyS0"
Reboot the altix and during the boot process, select
EFI Shell[Built-in]
Shell> fs0:
fs0:\> cd efi\boot
fs0:\efi\boot> bootia64
On the SuSE Linux Itanium Edidtion, Make Your Choice menu, leave "Installation" selected and enter the following for a console install:
console=ttySG0,38400n8
or for VNC (prefered)
console=ttySG0,38400n8 vnc=1
or for ssh
console=ttySG0,38400n8 usessh=1
For both remote methods, enter a temporary password to be used to access the systems, then set up a manual network connection
128.173.188.36/23
nothing else is needed if using a 128.173.188. address
for VNC,
Yum install tightvnc
vncviewer
128.173.188.36:1
for ssh
ssh -X root@128.173.188.36
then run
yast
=== Novell Suse Updates ===
Mirror Credentials
STEVE-EDWARDS-VT-EDU (6498173)
The username and password below can be used in automated mirroring scripts or to manually download updates. This credential is unique to the products for the STEVE-EDWARDS-VT-EDU (6498173) account. Access to each product's update channel will expire if/when your product expires.
Credentials
Username : 6498173
Password : 1725cdf144
Channels
https://nu.novell.com/repo/$RCE/SLE10-Debuginfo-Updates/
https://nu.novell.com/repo/$RCE/SLE10-SDK-SP1-Online/
https://nu.novell.com/repo/$RCE/SLE10-SDK-SP1-Updates/
https://nu.novell.com/repo/$RCE/SLE10-SDK-SP2-Online/
https://nu.novell.com/repo/$RCE/SLE10-SDK-SP2-Pool/
https://nu.novell.com/repo/$RCE/SLE10-SDK-SP2-Updates/
https://nu.novell.com/repo/$RCE/SLE10-SDK-Updates/
https://nu.novell.com/repo/$RCE/SLE10-SP1-Debuginfo-Updates/
https://nu.novell.com/repo/$RCE/SLE10-SP2-Debuginfo-Updates/
https://nu.novell.com/repo/$RCE/SLE10-SP2-SMT-Updates/
https://nu.novell.com/repo/$RCE/SLE11-Debuginfo-Pool/
https://nu.novell.com/repo/$RCE/SLE11-Debuginfo-Updates/
https://nu.novell.com/repo/$RCE/SLE11-HAE-Pool/
https://nu.novell.com/repo/$RCE/SLE11-HAE-Updates/
https://nu.novell.com/repo/$RCE/SLE11-SDK-Pool/
https://nu.novell.com/repo/$RCE/SLE11-SDK-Updates/
https://nu.novell.com/repo/$RCE/SLE11-SMT-Updates/
https://nu.novell.com/repo/$RCE/SLES10-SP1-Online/
https://nu.novell.com/repo/$RCE/SLES10-SP1-Updates/
https://nu.novell.com/repo/$RCE/SLES10-SP2-Online/
https://nu.novell.com/repo/$RCE/SLES10-SP2-Pool/
https://nu.novell.com/repo/$RCE/SLES10-SP2-Updates/
https://nu.novell.com/repo/$RCE/SLES10-SP3-Online/
https://nu.novell.com/repo/$RCE/SLES10-SP3-Pool/
https://nu.novell.com/repo/$RCE/SLES10-SP3-Updates/
https://nu.novell.com/repo/$RCE/SLES10-Updates/
https://nu.novell.com/repo/$RCE/SLES11-Extras/
https://nu.novell.com/repo/$RCE/SLES11-Pool/
https://nu.novell.com/repo/$RCE/SLES11-Updates/
Please note that the trailing slash (/) on these URLs must be included for proper access.
==== configuration ====
nis
Start up "/sbin/portmap" if it is not already running.
Start ypbind
# ypbind (start up /usr/sbin/ypbind)
Start NFS
# service nfs start
Start autofs
# service autofs start
==== firmware upgrade ====
Steve,
If you are flashing from the "L3" here's the procedure:
* cd to /usr/cpu/firmware/sysco
* ./flashsc - -l2 l2-inferno (or which ever System you want to
flash L2) -p ./l1.bin all
Then,
* * reboot_l1 new
* This will reboot all the l1s to the new image
* Then repeat the procedure for the other image (there are two on
each l1)
* ./flashsc - -l2 l2-inferno (or which ever System you want to
flash L2) -p ./l1.bin all
Please call me if you have any other problems.
Sincerely,
Michael J. Riojas
Systems Support Engineer
SGI-Federal
East Branch Support Team
(240)328-2796
But, We don't have L3:
Steve,
It's going to be a little more complicated than I earlier
thought (but doable). I have put a file on
shell.sgi.com:/collect/mriojas called CD.tar Download that linux file
onto the linux box you have and install the rpm. Then,
To flash the L1 firmware from the L3 controller, perform the following
procedure:
Establish a serial connection from the Linux box to the L1. Type the
following command at the L3 prompt:
Name of your Linux box> cu -l ttyS0 -s 38400
Type the following command at the L1 prompt to check which version of
microcode is currently running on all L1 controllers:
L1> flash status
In a L3 window, change to the /usr/cpu/firmware/sysco directory.
L3> cd /usr/cpu/firmware/sysco
Type the following command at the L3 prompt:
L3> ./flashsc --dev /dev/ttyS0 l1.bin
Type the following command to verify that the procedure has been
successful.
L1> flash status
Reboot the L1 controller.
L1> reboot_l1 new
Then do it again for the other image. If you should have any issues,
please let me know. I can also come out and do it for you. You have that
type of support. Just let me know.
Sincerely,
Michael J. Riojas
Systems Support Engineer
SGI-Federal
East Branch Support Team
(240)328-2796
Still, no L3!
on the Linux box do the following variation on the instructions in the email:
use the CD.tar from Mike Riojas
[linuxbox]# cd //CD/
[linuxbox]# ./install
*note* When done with all upgrades, uninstall with
./install -uninstall
[linuxbox]# yum install uucp
Hook up the serial line from a linux box to the brick to flash.
from minicom, verify the flash status of the brick. for L1.
L1> l1
L1> flash status
get back into terminal mode and
leave minicom
[linuxbox]# cd /usr/cpu/firmware/sysco
[linuxbox]# ./flashsc --dev /dev/ttyS0 l1.bin local
Check the flash status. Sometimes minicom spits some garbage out. Hit enter and try again. Then move to the next box and go back to check flash status and proceed.
Reset the L1's. From the main brick,
L!> * reboot_l1 new
==== PROM upgrade ====
fs1:
fs1:\> flash -V snprom.bin
fs1:\> flash -R
fs1:\> flash -a snprom.bin
SGI PROM Flashing Utility
Version of prom image in file 3.32
Verify that the current PROM on the system is older
with the following command:
fs0:\> flash -R
Running PROM version: 3.25
step 4: Flash all the nodes with the latest PROM image:
fs0:\> flash -a snprom.bin
==== L1 Commands ====
==rename brick==
plug serial into specific brick
brick slot 4
reboot_l1
== serial number ==
* serial
* serial all
==get log report==
log
==Prom version==
* promver
* ver
==Prom upgrade==
* install RPM for firmware snxsc
fs0:
/boot/efi/sgi/snprom
flash