Installing SLES10 via network with no DHCP available

In our current fight against the BladeCenter switches, we’re currently facing the problem that the blades ain’t able to send/receive DHCP-traffic.

So in order to move forward, we had to use static IP addresses. And since SLES10 ain’t straight forward on that, I had to look it up. Now, here’s for me (and everyone else tired of searching) how to do it:

Setting up the BladeCenter H

Well, we finally had our maintenance window today, in which we planned the hardware exchange for our current Dell Blade Chassis (don’t ask!). The exchange went fine, but as we started exploring the components (like the IBM BladeCenter SAN switches — which are in fact Cisco MDS 9100) we hit a few road blocks.

First, the default user name/password combo for the Cisco MDS 9100 for the BladeCenter is USERID/PASSW0RD (just as the rest of the password combinations).

Next, we started tinkering around with the Catalyst Switch modules. A hint to myself:

Whenever setting up the switch via the WebGUI, make sure you setup both passwords. The password for the switch itself (when prompted by the WebGUI, enter “admin” as well as the password you just entered.

Now, you should be able to connect to the switch with telnet and be able to access the EXEC mode (and unlike me who struggled ~30 minutes till one of my trainees told me to enter a switch password — out of curiosity).

Now, here the list of commands I needed to setup the switch’s “basics”:

Updating path information for TSM

As I did some switching today (between the new lin_tape version by IBM and our own lin_tape version), I ended up writing those lines a dozen times. Here is (just for me, if you don’t care .. skip ahead) on how to generate a list of commands:

which should get you a list like this:

Sidenote: Amount of Slots per Virtual Tape Library

Well, I just stumbled about this again (and I don’t know right now whether or not this is documented inside a RedBook or not) today, so I thought maybe I’m gonna write it down.

Slot-Amount Property of a Virtual Tape Library
Slot-Amount Property of a Virtual Tape Library

Please keep in mind, when creating the virtual library to think hard about the amount of slots you might need. It ain’t that bad, you just can’t decrease the amount anymore.  So if you think about creating 50 different virtual tape libraries with 500 slots each on your TS7530, think again. The current software level only supports 25.000 slots on a global level.

Working with IBM’s Virtualization Engine Console

Recently, we got the recommendation from our system partner to use static allocated tape cartridges instead of dynamic allocated ones. Apparently using dynamic allocating cartridges comes with a performance penalty if more than a few nodes are backing up a large amount of data at once.

And yet again, I noticed that the IBM Virtualization Engine Console (aka Falconstor Software) is really error prone.

In order to change the allocation type, we had to shred the old cartridges first (500 x ~100M up till now), chance the allocation type at the virtual tape library level, and then recreate the 500 cartridges with a fixed size (500x 102400MB). Now, as I was kinda optimistic, I decided to create all 500 cartridges at once.

Failure during the initiation of 500 virtual catridges

So I ended up creating the 500 cartridges in steps of 45. Which isn’t that big of a deal. But, as we do have two separate logical virtual tape libraries (basically the whole TS7530 is partitioned into two tape libraries), we had to do it for the second one too. But I told myself “Come on, try the maximum amount again!” … And guess what:

Successful initiation of 510 virtual catridges

That worked ❓ Please, don’t ask me why the hell it’s working for one virtual tape library on the same system (well, different virtualization engine), but ain’t for the other one … 😯

Sunday afternoon playtime

Well, it’s yet again Sunday afternoon. And I had (again I might add) the urge to play around with all the stuff I have at home.

So at first, I “fixed” the ground wire off my NAS box.

Ground wire for he CPU fan

Afterwards, I went back upstairs. Hooked my Philips up to my notebook and figured I *really* need a wireless keyboard. Because typing with the Windows on-screen keyboard is a huge pain in the ass (as well as a pain for the mouse-hand)!

Samsung R70 hooked up to my Philips TFT

Automatic updates on SUSE Linux Enterprise 10

I had the problem, that the automatic update function of YaST doesn’t work like I want it to. I just wanted it to install only those updates, that ain’t interactive, don’t need a service restart and don’t need a reboot.

YaST does only feature an online update that skips “interactive” updates (I’ve never even encountered an interactive update up till now). So I went ahead and wrote a (hackish) script, that achieves what I need.

And just for me, the crontag entry:

Opsview installation reviewed

Well, I recently (well, yesterday) built the opsview RPM’s for SLES10, and started fiddeling about with it today. Alex “recommended” I should rather look at Opsview instead of Centreon, but boy was there a surprise waiting for me …

Opsview has the advantage that it at least lets you use the package manager. But, it also needs *a lot* of handy work (just like Centreon, which I really dislike since it’s real error prone).

I started doing the setup, but gave up halfway through … ❗ Dude, and they expect people to pay money for training ?!?

I mean, come on .. you can do a better job at making this thing fit a bit better into the system, and even make the install a bit more straight forward.

Building opsview for SUSE Linux Enterprise 10

Disclaimer: I don’t take any responsibility for faults within the software, I just provide the RPM’s! Feel free to ask me about stuff concerning these RPM’s, but I ain’t accountable if your stuff goes kaboom

Well, I just looked at opsview again (haha, thanks Alex :-P). Only trouble is, the people over at opsview don’t distribute RPM’s for that … After registering for their site, to download the SRPM’s (or to download anything), I got the RPM’s and started looking at them.

Well, the only things I needed to adjust in opsview-base, opsview-core and opsview-perl were the dependencies. I also needed to rebuild a RPM for perl-Version from Dag Wieers, since opsview-perl required them to even build.

  1. opsview 2.14.1 (build 1695-1)
    • opsview-agent (i586, x86_64)
    • opsview-base (i586, x86_64)
    • opsview-core (noarch)
    • opsview-perl (i586, x86_64)
    • opsview-reports (noarch)
    • opsview-slave (i586, x86_64)
    • opsview-web (noarch)
  2. opsview 3.0.0 (beta, build 1895-1)
    • opsview-agent (i586, x86_64)
    • opsview-base (i586, x86_64)
    • opsview-core (noarch)
    • opsview-perl (i586, x86_64)
    • opsview-reports (noarch)
    • opsview-slave (noarch)
    • opsview-web (noarch)

Installation order is like this:

  1. opsview-base
  2. opsview-perl
  3. opsview-web
  4. opsview-core
  5. opsview-reports

If you are looking for older versions, try the respective directory on (for example i586 for SLES10).

If you encounter a missing link (either striked or just missing), please note that older builds aren’t available anymore.