Tivoli Provisioning Manager for OS Deployment Installation on W2003R2-NFS-MySQL

Transcription

1 This post is about the installation of IBM Tivoli Provisioning Manager for OS Deployment (TPMfOSD). Although the potential audience is small, I am sure that those who want to switch to use a MySQL database will appreciate... For short history, we have used for several years successfully a bunch of Rembo 0 Servers in our network infrastructure for operating system deployment. We have even written an open source application based on Rembo (how the time flies!). The small Rembo is gone since August 2006, bought by the mighty IBM. This document explains how to install a pair of PXE servers with TPMfOSD. The specific problems related to the installation on a Windows 2003 R2 server using NFS mounted shared file system and a third party server MySQL database have especially motivated this document's creation. The walkthrough servers are pxe1.mydomain.com and pxemydomain.com throughout this document Some part of this procedure was initiated by IBM's Jacques Fontignie's instructions, added with Microsoft NFS specific instructions and with the usage of the third party server MySQL database instead of the local database. 1. You must be logged on the W2003 R2 server, on the mydomain.com Active Directory domain as user "myad-dom\rembo", in our example. Install the TPMfOSD base package using the local drive for the server file system (C:) Make sure to install all the proposed options, such as language packages, otherwise the future bug fixes do not necessarily install correctly Accept the default settings for server files (on C:) HTTP server console settings: HTTP console port 80, HTTPS console port 443, Select Disable HTTPS console access (use only HTTP) If you do not get a questions about the server files and HTTP server console settings, you have probably an earlier installation at C:\Program Files\Common Files\IBM Tivoli. It contains a *.db file which memorizes all the previous settings. Cancel the installation. Rename the directory or remove it altogether and try again. Administrator name tivoli, Password mypassword Ignore Web interface extension user account (no images taken from the local system disk) Let the installation finish. At this point you should be able to access the server through the web based administration interface and log in after having accepted the license conditions. In Administrative Tools -> Services, verify that all the three services of the TPMfOSD have been started (IBM Tivoli OS Deployment, IBM Tivoli TCP to ODBC gateway and IBM Tivoli Web Interface Extension). Stop all the above three IBM Tivoli services for the bug fix installation. Install the latest bug fix of the TPMfOSD (note that if you have earlier bug fixes installed, they may have to be removed prior to installation of the latest bug fix). In Administrative Tools -> Services, verify that all the three services of the TPMfOSD have been started after the bug fix installation (IBM Tivoli OS Deployment, IBM Tivoli TCP to ODBC gateway and IBM Tivoli Web Interface Extension). 3. The basic installation is finished, using the local file system for shared files and Access driver, *.mdb file based database on the local disk. On Windows 2003 R2 server, map the network drive from the Net App server using NFS. NFS client is provided natively by W2003R2 (as with Vista). Additionally, we will install some supporting programs, provided by the SUA (SDK for Unix based Applications). Do not use the SFU [Support For Unix] package which is for W2000/XP and therefore discontinued. Configuring the system to be used as a NFS client consist two parts: Page 1

2 1) Windows / Unix user name mapping 2) instructing the native Microsoft NFS to use the selected name mapping method. Installation of the Microsoft NFS support : W2003R2 includes already a Windows Component called Microsoft Services for NFS. To get it activated, Control Panel -> Add or Remove Programs -> Add/Remove Windows Components -> Select Other Network File and Print Services -> Click Details button -> Select Microsoft Services for NFS -> Click Details button. You will see a list of subcomponents. In our case, we plan to run only the NFS client with local user name mapping we will make the following selection: (+) Client for NFS (+) Microsoft Services for NFS Administration (+) RPC External Data Representation (+) RPC Port Mapper (-) Server for NFS (+) Server For NSF Authentication (+) User Name Mapping Click Ok button and continue to the next step without starting the installation yet. Installation of the Microsoft SUA. SUA is a Windows Component which is not activated by default in W2003R If you do not have the Windows Component Wizard dialog open, Control Panel -> Add or Remove Programs -> Add/Remove Windows Components -> Select Subsystem for Unix-based Applications. You would need CD #2 of W2003R2 installation disk set. The process ask you to download the supporting cabinet file (a special version is available for W2003 R2). If you have already downloaded a copy, you do not need download it again but run the setup in the cabinet file later. The cabinet file setup can be executed with default options + SVR-5 when it asks for the installation options. Note: SUA is needed for local Windows / Unix based user name mapping. By default W2003R2 is relying on one of the two services which should be available in Active Directory Server: 1) Active Directory Lookup service or 2) User Name Mapping server. None of them is available on the domain mydomain.com when this is written and therefore we need to install SUA for local user name mapping. Additionally SUA provides us some Unixlike utilities that we can use to better view the file attributes in the remote, NFS-mounted file system. After the installation you should reboot the computer (to get the benefit of the newly installed NFS-utilities, such as mount). Note that they are located in C:\WINDOWS\msnfs (in the Path variable after reboot), and their Unix-like equivalents are in C:\WINDOWS\SUA\usr\sbin. Preparations for the NFS client mount operation: 1. Windows / Unix user name mapping Start the NFS management utility (Run -> nfsmgmt.msc, or Start -> Programs -> Administrative Tools -> Microsoft Services for Networked File Systems). Open User Name Mapping, Right click User Maps, select Create Map. You will see a dialog entitled Create Advanced User Mapping. Keep the Windows domain as MYAD-DOM and click the button List Windows Users. Select user (here REMBO). For Unix Account, select NIS domain name mydom and NIS server name mynis-srv.mydomain.com. Click List Unix Users button. Select user rembo (1234). Press button Add, then Close. Right click Group Maps, select Create Map. You will see a dialog entitled Create Advanced Group Mapping. Keep the Windows domain as MYAD-DOM and click the button List Windows Groups. Select group (here user rembo belongs to group GRP MYGRP). For Unix Account, select NIS domain name Page 2

3 mydom and NIS server name mynis-srv.mydomain.com. Click List Unix Groups button. Select group mygrp (123). Press button Add, then Close. Configuring the Microsoft NFS client, telling it to use the selected name mapping method While still on the NFS management utility (see point 1), Right click on the Client for NFS, select Properties. Transport Protocol UDP (TCP will lead to illegal port number error on Unix side) Mount Type Use soft mount, retries 1, Interval 0.8s Read/Write Buffers 64 kb File Permissions 775 (RWX, RWX, RX) Right click on Microsoft Services for NFS, select Properties. User Name Mapping Server: IP address of the PXE server that you are installing (ex ). String localhost does not work. Note: with the arrival of Vista this is likely to change and there may be a dedicated User Name Mapping Server installed on your domain later on. Make sure that the Active Directory Lookup checkbox is unchecked and click OK button. Using File Explorer, move to directory C:\WINDOWS\msnfs. Right click on the.maphosts file, select Properties, uncheck Read only. Edit the.maphosts file adding the IP address of the PXE server that you are installing (ex ) on the last line of the file. Save the file. Right click on the.maphosts file, select Properties, check Read only. Open the Services management (in Administrative Tools -> Services), restart User Name Mapping and Client For NFS services. Test the NFS mount operation from NetApp server. Open a command prompt window and type, for example mount pxe1srv.mydomain.com:/vol/vol0/qt_pxe1 Z: From Start -> Programs -> Subsystem for Unix-based Applications start a Korn Shell session. From the command prompt, give commands df cd /dev/fs/z ls -al (verify that the owner/group attributes are REMBO/GRP MYGRP) touch test.txt mv test.txt xxx.txt rm xxx.txt 4. Prepare the installation of a MySQL database on a third party server, if not already available, In our case, we are using standard MySQL 4 server package on mysqlsrv1-1.mydomain.com. The database server is activated with command /etc/init.d/mysqld start Make the database start activation permanent with command chkconfig --level 345 mysqld on verify with command chkconfig --list mysqld The database is best managed with phpmyadmin. It has been installed on /var/www/html/phpmyadmin. The configuration is simple: cp config.sample.inc.php config.inc.php modify the password cookie line as follows Page 3

4 5. $CF['blowfish_secret'] = 'myseedgoeshere'; Now the MySQL installation can be managed through the web browser interface, ex. After the initial installation there is no password required. But following the general practice and administration user account will be set with the usual password. Create a database called tpmfosddb and two users, both named tivoli, one from pxe1.mydomain.com and the other from pxemydomain.com host. The two users' privileges should be set for the created database. Create also a third user, tivolibackup with only SELECT and LOCK TABLE rights, on localhost, for backup purposes. Prepare the ODBC connection to MySQL database server You need MySQL Connector for ODBC ( when this is written) for Windows 32-bit platform. It can be downloaded from the MySQL product catalog. Once the MySQL connector is installed, test the connection. Open Administrative Tools -> Data Sources (ODBC) Tab "System DSN" 6. button Add, select MYSQL ODBC 3.51 Driver from the list Data Source Name tpmfosddb, Description for IBM Tivoli Provisioning Manager, Server mysqlsrv1-1.mydomain.com, User tivoli, Password mypassword, Database tpmfosddb Click the Test button. You should get a successful connection message. Note that this local definition is not actually used for the database access from TPMfOSD but let's leave it because it indicates that the connection exists and it can be used for the functional testing of the connection. Prepare to switch from local disk shared file repository to remote NFS disk shared file repository and from local *.mdb file database to remote MySQL database: 1. Open a command line (cmd) prompt at C:\Program Files\Common Files\IBM Tivoli cp rembo.conf rembo_nfs.conf Modify rembo_nfs.conf by following line (example mount, change as needed) DataDir "//pxe1srv.mydomain.com/vol/vol0/qt_pxe1/tpmfos Files" You can mount it for temporary access, if you are not on pxe1.mydomain.com with command mount pxe1srv.mydomain.com:/vol/vol0/qt_pxe1 Y: net stop remboserver Cut and Paste (move) C:\TPMfOS Files to Z:\TPMfOS Files (NFS network drive, the target directory should not exists) Give command rembo -d -v 4 -c rembo_nfs.conf The service starts in the foreground but you will get error messages about the missing database connection. This will handled next. In Administrative Tools -> Services, verify that IBM Tivoli TCP to ODBC gateway and IBM Tivoli Web Interface Extension have been started. If not, start them both manually. Leave the IBM Tivoli OS Deployment Server (= RemboServer) halted. Prepare the new database connection instructions for the RemboServer's next startup: From pxe1srv.mydomain.com:/vol/vol0/qt_pxe1/esrf Configurations you will find file named config.csv with the following type of contents: Page 4

5 "HostName";"Interfaces";"DbName";"DbUser";"DbPass";"MasterIP";... "pxe1.mydomain.com";" ";"[driver={mysql ODBC 3.51 Driver};.. "pxemydomain.com";" ";"[driver={mysql ODBC 3.51 Driver};.. Use the file as it is or modify it accordingly if the different hosts are concerned. More information about the config.csv configuration format can be found at rs=3176&uid=swg &loc=en_us&cs=utf-8=en Open another command line (cmd) prompt at C:\Program Files\Common Files\IBM Tivoli Copy the config.csv file into the TPMfOSD's shared file system with commands netclnt open localhost cd rad put config.csv exit Stop the foreground RemboServer with Ctrl-C Start the RemboServer again from the command line, with rembo -d -v 4 The service founds that the database connection has changed in RAD configuration. It will shut down and ask to be restarted (if the service is not shutting down, there is probably a problem with IBM Tivoli TCP to ODBC gateway service not running): rembo -d -v 4 It will create now all the tables in the remote tpmfosddb MySQL database. You can use the phpmyadmin web interface on the remote MySQL server to verify that this is the case. If the MySQL database did not exist before, the service founds that the RAD ID of the system has changed, because of the new database. It will shut down and ask to be restarted (for the second time): rembo -d -v 4 The foreground job gets up until a point where it says: VM > Waiting for activities on BomID 2 Log in using the web based administration interface and check that the system configuration (NFS-based shared repository) and log messages (MySQL database server) makes sense. Stop the foreground server with Ctrl-C In Administrative Tools -> Services, select IBM Tivoli OS Deployment service, Properties Select tab "Log On", select radio box "This account" mydomain.com\rembo give password twice Click "Apply" to verify Back to tab "General", click "Start" button The service should start, did it? Select Startup type: "Manual" 7. Click "OK" 14. Check the service "IBM Tivoli Web Interface Extension". If it is running, Restart it. Otherwise Start it. In C:\WINDOWS\ESRF\Scripts write a startup script named rembosrv.bat, for example Page 5

6 C:\WINDOWS\msnfs\mount.exe pxe1srv.mydomain.com:/vol/vol0/qt_pxe1 Z: net start remboserver Start Group Policy Object (GPO) Editor Start -> Run -> gpedit.msc Open Computer Configuration -> Windows Settings -> Scripts (Startup/Shutdown) Open Startup object by double clicking it. In the dialog box, select Add and in the field Script Name write C:\WINDOWS\ESRF\Scripts\rembosrv.bat Reboot the system and check that the service Rembo Server has started without login on the system through the remote desktop: Check that you can access the administrative TPMfOSD console from your browser Note: When the system starts, in My Computer the qt_pxe1 (Z:) disk may say that it is a Disconnected Network Drive? But it is not: open the network drive and you will notice that you can create files in it. The Rembo server is not complaining, either. Installation of the secondary PXE server, a.k.a. pxemydomain.com: Repeat the installation as with the installation of the primary PXE server explained above. The NFS mount point is different: \\pxe2srv.mydomain.com\vol\vol1\qt_pxe2 Once logged on the secondary server's web interface, move to Server parameters -> Configuration, Edit Boot module, set Seconds to wait before sending DHCP/BINL answers to 2 (two seconds). Activate servers replication from the master server to the secondary server: About backups: On the master server's web interface, Server parameters -> Configuration -> Servers replication. You will see the secondary server (ex. pxemydomain.com) in the list of standalone servers, while the master server (ex. pxe1.mydomain.com) is on the list of synchronized servers. Select the secondary server. In Other actions select Make this server a slave server. You will be shown the IP address of the master server (ex ). Click on the Make this server a slave of the selected master. With the secondary server (ex. pxemydomain.com) selected, select Synchronization - >Schedule -> edit. Daily, Schedule every 1 days, Start time 22:00. (verify the synchronization logs on the next day). 1. It is necessary to backup the \\pxe1srv.mydomain.com NetApp file system. Since the backup daemon runs outside the W2003 server, the RemboServer process is not stopped and it does not flush its file system prior to backup process. But we can suppose that it does so when it is synchronizing the remote (pxe2) server. Make an exercise where you stop the RemboServer, use the shared file system restored from TiNa and then restart the RemboServer with rembo.exe -d -v 4 in order to see will there be any fatal errors. MySQL database must be backed up as well. It is better done by dumping the database in SQL text format into a file within a file system that is backed up with TiNa (in our example). Put the following in the /etc/crontab # Backup IBM TPMfOSD MySQL database on this server Page 6

7 # 11 3 * * * root /usr/bin/mysqldump tpmfosddb -utivolibackup >/dist/tpmfosd/mysql/ # end of installation instructions. Page 7