source: MondoRescue/branches/2.2.9/mindi/README.ProLiant@ 3320

Last change on this file since 3320 was 3320, checked in by Bruno Cornec, 9 years ago
  • Re-add (thanks git BTW) the 2.2.9 branch which had been destroyed in the move to 3.0
File size: 3.5 KB
Line 
1$Id$
2
3-------------------------------------------------------------------------------------
4
5If you have a ProLiant system you first need to get the hp-scripting-tools, hponcfg and hpacucli packages. Due to licenses issues, mindi cannot provide those tools itself. You need to get them from http://downloads.linux.hp.com/SDR/downloads/ProLiantSupportPack/
6
7wget http://downloads.linux.hp.com/SDR/downloads/ProLiantSupportPack/RedHat/6Server/x86_64/8.72/hpacucli-8.70-8.0.noarch.rpm
8yum install -y (or worst case rpm -Uvh) hpacucli-8.70-8.0.noarch.rpm
9(will install hpacuscripting under /usr/sbin)
10wget http://downloads.linux.hp.com/SDR/downloads/ProLiantSupportPack/RedHat/6Server/x86_64/8.72/hponcfg-3.1.1-0.noarch.rpm
11yum install -y (or worst case rpm -Uvh) hponcfg-3.1.1-0.noarch.rpm
12(will install hponcfg under /usr/sbin)
13wget http://downloads.linux.hp.com/SDR/downloads/ProLiantSupportPack/RedHat/6Server/i386/8.72/hp-scripting-tools-8.70-52.rhel6.i386.rpm
14yum install -y (or worst case rpm -Uvh) hp-scripting-tools-8.70-52.rhel6.i386.rpm
15(will install hp-conrep under /sbin)
16
17You're now ready to check your configuration by running:
18mindi-bkphw /var/cache/mindi /etc/mindi
19[First parameter is the directory where files will be generated,
20 Second parameter is the configuration directory of the file deplist.d/ProLiant.conf is located]
21
22-------------------------------------------------------------------------------------
23Some of these tools are also provided as part of the Smart Start Scripting Toolkit. You can get it from http://www.hp.com/servers/sstoolkit and use the following:
24cd /tmp
25wget ftp://ftp.hp.com/pub/softlib2/software1/pubsw-linux/p1221080004/v63551/ss-scripting-toolkit-linux-8.70.tar.gz
26mkdir ssstk
27cd ssstk
28tar xvfz ../ss-scripting-toolkit-linux-8.70.tar.gz
29cp -a utilities/conrep /usr/sbin
30cp -a utilities/conrep.xml /usr/share/conrep/conrep.xml
31cp -a utilities/hponcfg /usr/sbin
32cp -a utilities/hpacucli/hpacuscripting /usr/sbin
33cp -a utilities/hpacucli/.hpacuscripting /usr/sbin
34
35# For versions <= 1.90
36cp -a utilities/cpqacuxe/cpqacuxe /usr/local/bin
37cp -a utilities/cpqacuxe/bld /usr/local/bin
38mv /usr/local/bin/bld/*.so /usr/local/lib
39echo /usr/local/lib >> /etc/ld.so.conf
40ldconfig
41
42-------------------------------------------------------------------------------------
43Older URL:
44wget ftp://ftp.hp.com/pub/softlib2/software1/pubsw-linux/p308169895/v40154/ss-scripting-toolkit-linux-1.70.tar.gz
45wget ftp://ftp.hp.com/pub/softlib2/software1/pubsw-linux/p308169895/v43548/ss-scripting-toolkit-linux-1.81.tar.gz
46wget ftp://ftp.hp.com/pub/softlib2/software1/pubsw-linux/p308169895/v44247/ss-scripting-toolkit-linux-1.90.tar.gz
47-------------------------------------------------------------------------------------
48If you're making a backup with mondoarchive on a ProLiant system that you want to be able to restore using the Virtual Media function of ProLiants, then you have to ensure that the required drivers will be available at restore time.
49In order to ensure that, you may want to do on 2.2.x (x < 5) versions:
50- Edit your /usr/sbin/mindi script
51- Look for declaration of the variable FORCE_MODS.
52- Change it to FORCE_MODS="usb-storage sr_mod"
53
54Those drivers will then be available at restore time, and your virtual media thus detected and supported.
55As the CD-ROM emulated is a USB one, it will be a slower restore than using a real CD, or the network, but can be an easy way to load the mindi boot image e.g. and launch the rest of the restore through the network.
56
57With latest versions of mindi, those modules are already included and you don't have to do anything to have it work.
Note: See TracBrowser for help on using the repository browser.