church of default


[jim@ssh ~]$ ssh admin@<your-loadbalancer>
Password:
Last login: Tue Nov 10 13:16:15 2009 from 10.10.24.62
[type ? for help]
AX>en
Password:
AX#conf
AX(config)#backup config tftp://<yourserver>/a10_backup.tar.gz
System files backup succeeded
AX(config)#

Notice you want to supply the .tar.gz suffix yourself.

Then on the receiving server server there’s a slight trick to unpacking it: its actually a tarball *within* a tarball thats then gzipped. It also doesn’t create a subdirectory for itself so it’ll explode all over the dir you’re in when you type the tar command.

[root@nas tftpboot]# ll
total 12
-rw-rw-rw- 1 nobody nobody 11046 Nov 10 15:14 a10_backup.tar.gz
[root@nas tftpboot]# file a10_backup.tar.gz
a10_backup.tar.gz: gzip compressed data, from Unix, last modified: Tue Nov 10 15:14:00 2009
[root@nas tftpboot]# tar zxvf a10_backup.tar.gz
backup_system.tar
[root@nas tftpboot]# tar xvf backup_system.tar
a10data/aflex/
a10data/aflex/mdot-redirect.arl
a10data/bwlist/
a10data/cert/
a10data/cert/mycorp-wildcard.crt
a10data/cert/entrust-L1B-chain.crt
a10data/crl/
a10data/hm/
a10data/hm/bin/
a10data/key/
a10data/key/mycorp-private.key
etc/release
etc/a10_platforms
a10data/etc/enable-passwd.pri
a10data/etc/enable-passwd.sec
a10data/etc/a10enable-passwd
a10data/etc/passwd.pri
a10data/etc/passwd.sec
a10data/etc/a10passwd
a10data/etc/startup-config.pri
a10data/etc/startup-config.sec
a10data/etc/startup-config.profile
a10data/etc/network/ifconfig.eth0
a10data/etc/sysconfig/network
a10data/etc/timezone
a10data/config/
a10data/config/start
a10data/web/partition_logo/
a10data/web/partition_logo/title_logo.png
mnt/cf/a10data/cert/
mnt/cf/a10data/hm/
mnt/cf/a10data/hm/bin/
mnt/cf/a10data/key/
mnt/cf/a10data/etc/enable-passwd.pri
mnt/cf/a10data/etc/enable-passwd.sec
mnt/cf/a10data/etc/a10enable-passwd
mnt/cf/a10data/etc/passwd.pri
mnt/cf/a10data/etc/passwd.sec
mnt/cf/a10data/etc/a10passwd
mnt/cf/a10data/etc/startup-config.pri
mnt/cf/a10data/etc/startup-config.sec
mnt/cf/a10data/etc/startup-config.profile
mnt/cf/a10data/etc/network/ifconfig.eth0
mnt/cf/a10data/etc/sysconfig/network
mnt/cf/a10data/etc/timezone
mnt/cf/a10data/config/


DO NOT DO THIS
turns out the multipath.conf example from xone is all sorts of wrong, it effectively gets ignored and you’re using the defaults (which it turns out work ok-ish). hopefully I’ll update here when I have two days to blow on the phone support game.

Well if you wanted to you could read the official xiotech docs which in turn reccomend you the redhat docs.  That would be a great way to kill a day in frustration while sifting through a lot of noise.  Here’s how to get a very basic example working quickly:

1.) make sure you have device-mapper-multipath installed

[jim@sql1 ~]$ rpm -qa | grep multi
device-mapper-multipath-0.4.7-23.el5_3.4

if you do, doesn’t hurt to yum update it. if not, install it.

2.) edit /etc/multipath.conf

first comment out the blacklist lines near the top

#blacklist {
#        devnode "*"
#}

then append this to the bottom

devices {
        device {
                vendor                  "XIOTECH "
                product                 "ISE1400         "
                path_grouping_policy    multibus
                getuid_callout          "/sbin/scsi_id -g -u -d /dev/%n"
                path_checker            tur
                prio_callout              "none"
                path_selector           "round-robin 0"
                failback                    immediate
                no_path_retry           12
                user_friendly_names yes
        }
}

3.) setup and prod multipath

[jim@sql1 ~]$ sudo /sbin/chkconfig multipathd on
[jim@sql1 ~]$ sudo /etc/init.d/multipathd start
Starting multipathd daemon:
[jim@sql1 ~]$ sudo /sbin/multipath -v2

notice it returns nothing, the redhat docs say it should, but it doesn’t. its just scanning the paths, if you want to see what it has discovered/conifgured run this:

[jim@sql1 ~]$ sudo /sbin/multipath -ll
mpath1 (36001f93000a63000019b000200000000) dm-2 XIOTECH,ISE1400
[size=100G][features=0][hwhandler=0][rw]
\_ round-robin 0 [prio=1][active]
 \_ 2:0:0:1 sdb 8:16  [active][ready]
\_ round-robin 0 [prio=1][enabled]
 \_ 3:0:0:1 sdc 8:32  [active][ready]

take note of the “mpath1″ part there

4.) filesystem stuff time

format the disk (I’m not bothering with fdisk/partitions or lvm in this example, complicate as you see fit)

[jim@sql1 ~]$ sudo /sbin/mkfs.ext3 /dev/mapper/mpath1
<snip>
[jim@sql1 ~]$ sudo mkdir /mnt/xio
[jim@sql1 ~]$ sudo vi /etc/fstab

and stick this line on the bottom

/dev/mapper/mpath1      /mnt/xio                ext3         defaults,noatime        1 1

then you’re pretty much set, mount it

[jim@sql1 ~]$ sudo mount /mnt/xio
[jim@sql1 ~]$ cd /mnt/xio/
[jim@sql1 xio]$ ls
lost+found
[jim@sql1 xio]$ sudo dd if=/dev/zero of=./foo bs=8k count=1310720
1310720+0 records in
1310720+0 records out
10737418240 bytes (11 GB) copied, 24.9054 seconds, 431 MB/s
[jim@sql1 xio]$

There are (hypothetically) two ways:

in the bios: caps lock + num lock + scroll lock + alt-f

you have to be on the kvm for this to work, or at least I assume, because it didn’t work over idrac for me

jumper shuffle

shut down the blade, pull it out of the chassis, open it up, find the nvram_clr jumper (see picture), toggle it, put it all back together, boot up, watch for the “restoring factory defaults” message (or something like that, I didn’t get to see it, colo hands-and-eyes guy did), power the blade down again, pull it out, open it up, flip the jumper back, put it together again, re-rack, power up and hit F1… done.