5221
Comment: RAID Controller setup added
|
4321
Informationsgewinnung per ipmi-Skript
|
Deletions are marked like this. | Additions are marked like this. |
Line 39: | Line 39: |
== MAC Address Retrieval == | == Host information Retrieval == |
Line 41: | Line 41: |
Log in to the Service Processor as root using ssh. Then: | The information is retrieved by the use of ipmitool. Here's the script that's called ipmi (it has to be called on a host where ipmitool is available, e.g. a): |
Line 43: | Line 43: |
=== Service Processor === Run `show SP/network` : |
|
Line 46: | Line 44: |
-> show SP/network | #!/bin/bash host=$1 shift |
Line 48: | Line 48: |
/SP/network Targets: Properties: commitpending = (Cannot show property) ipaddress = 141.34.42.159 ipdiscovery = Static ipgateway = 141.34.42.1 ipnetmask = 255.255.255.0 macaddress = 00:03:BA:F1:EC:95 pendingipaddress = 141.34.42.159 pendingipdiscovery = Static pendingipgateway = 141.34.42.1 pendingipnetmask = 255.255.255.0 |
ipmitool -I lan -H sp-$host -U root -P <password> $* |
Line 64: | Line 51: |
=== Onboard Gigabit NICS === The system has four onboard interfaces. IN the SP tree, these show up as two dual port controllers NET0 and NET1. The primary interface (recognized as eth0 under linux, and labelled NET0) is the one with the lowest MAC address shown. Only the lower MAC of each dual port card will show up in the SP output: |
=== System serial number === |
Line 68: | Line 54: |
-> show /SYS/MB/NET0 | for i in galaxy{25..30}; do serial=`ipmi $i fru | grep 'Product Serial' | head -n 2 | tail -n 1 | awk -F : '{print $2}' | sed 's| ||'` vamos_cmd -m host $i host.serial_number=$serial done }}} |
Line 70: | Line 60: |
/SYS/MB/NET0 Targets: |
=== SP mac address === |
Line 73: | Line 62: |
Properties: SEEPROM = Product Information: manufacturer name = INTEL product name = DUAL PORT GIGABIT ETHERNET CONTROLLER (COPPER) version = (no information) serial number = 00:14:4F:01:A9:9C part number = 82546EB |
{{{ for i in galaxy{25..30}; do mac=`ipmi $i fru | grep 'Product Serial' | head -n 1 | awk -F ' : ' '{print $2}'` vamos_cmd -m host sp-$i interface.ether=$mac done }}} |
Line 82: | Line 69: |
Commands: cd show |
=== System mac address (first nic) === |
Line 86: | Line 71: |
-> show /SYS/MB/NET1 /SYS/MB/NET1 Targets: Properties: SEEPROM = Product Information: manufacturer name = INTEL product name = DUAL PORT GIGABIT ETHERNET CONTROLLER (COPPER) version = (no information) serial number = 00:14:4F:01:A9:9A part number = 82546EB Commands: cd show |
{{{ for i in galaxy{25..30}; do mac=`ipmi $i fru | grep 'Product Serial' | head -n 4 | tail -n 1 | awk -F ' : ' '{print $2}'` vamos_cmd -m host $i interface.ether=$mac done |
Line 104: | Line 77: |
The primary interface in this example is ...:9A. The others are :9B (not shown), :9C (shown) and 9D (not shown). |
Documentation
There's almost no documentation coming with the system, it's all available online only:
http://www.sun.com/products-n-solutions/hardware/docs/Servers/Workgroup_Servers/x4100/index.html
Getting the ILOM going is described in the Servers Setup Guide which is coming in printed form, though.
ILOM (Service Processor) Setup
To get the IP interface going without having dynamic DHCP for it available, use the serial port:
- find a notebook or a system nearby with a 9-pin SUB-D serial port
- attach the adaptor coming with the server to this port
use an RJ45 cable (a normal patch cable works) to connect the adaptor to the serial management port of the server
- fire up the terminal emulation software (linux: minicom) and configure the port correctly:
- 9600,8N1 (on a notebook, the port ist /dev/ttyS0, on a server it may be ttyS1)
no flow control, neither hardware nor software
- you should now be able to log in as root (password: changeme)
- change the password (if you find out how this can be done...)
set the IP interface to a static address as described in the Servers Setup Guide:
cd /SP/network set pendingipaddress=141.34.42.xyz set pendingipnetmask=255.255.255.0 set pendingipgateway=141.34.42.1 set pendingipdiscovery=static set commitpending=true
The last step takes a couple of seconds and produces some error messages. Don't panic. Verify if it worked by pinging the service processor afterwards. You should now be able to log in with ssh or https. All other steps can be done from your desktop.See ["Remote Management"]. If you haven't changed the password until now, do this on the SP's Website (User Management -> Select "root" and click "Edit").
Host information Retrieval
The information is retrieved by the use of ipmitool. Here's the script that's called ipmi (it has to be called on a host where ipmitool is available, e.g. a):
host=$1 shift ipmitool -I lan -H sp-$host -U root -P <password> $*
System serial number
for i in galaxy{25..30}; do serial=`ipmi $i fru | grep 'Product Serial' | head -n 2 | tail -n 1 | awk -F : '{print $2}' | sed 's| ||'` vamos_cmd -m host $i host.serial_number=$serial done
SP mac address
for i in galaxy{25..30}; do mac=`ipmi $i fru | grep 'Product Serial' | head -n 1 | awk -F ' : ' '{print $2}'` vamos_cmd -m host sp-$i interface.ether=$mac done
System mac address (first nic)
for i in galaxy{25..30}; do mac=`ipmi $i fru | grep 'Product Serial' | head -n 4 | tail -n 1 | awk -F ' : ' '{print $2}'` vamos_cmd -m host $i interface.ether=$mac done
RAID Controller Setup
During the boot hit Ctrl-C when the LSI RAID controller is initializing. Select the first (and only) adapter, then choose Create IS Volume. If you don't need the data on the disks you can ignore the warning. Change RAID disk for both disks to YES to create a RAID 0 stripe. Commit with C. After that leave the controller setup.
BIOS
This server's BIOS has very many options, and most have not been explored or even understood yet.
Some that matter:
Legacy USB (default: enabled)BR Can be a problem under Linux if enabled (instability). If off, the keyboard (USB only, no PS/2 ports) will work in the BIOS, but not in the bootloader. This should probably be set to auto.
AC power loss recovery (This BIOS option does not exist)BR The 'Power Restore Policy' is set to 'always-off' anyway
Advanced -> Remote Access Configuration (default: 9600 baud on ttys0)BR Make sure that serial redirection is enabled, and all the speed settings match (by default, all are 9600, which works but is slow):
- serial redirection
- service processor serial port speed (external and internal)
- operating system parameters: grub and agetty
CF_CONMGR_TTY=ttyS0
CF_ConMgr_BaudRate=9600
System Serial Number Retrieval
Log into the SP as root, and run
-> show SYS/MB
Or use dmidecode. Or the web interface or ...