This section contains information about known problems and limitations, best practices, and hints and tips for using the Linux Scripting ToolkitServerGuide Scripting Toolkit, Linux Edition.
To perform a PXE deployment by using the Linux Scripting Toolkit, you must first configure the TFTP server on the source server and update the Toolkit Preferences page with the IP address of the TFTP server.
/tftpboot/
/tftpboot/lnxtoolkit
/tftpboot/lnxtoolkit/pxelinux.cfg
/tftpboot/lnxtoolkit/pxelinux.cfg/PXE_test
/tftpboot/lnxtoolkit/PXE_test
/tftpboot/lnxtoolkit/PXE_test/tc.zip
/tftpboot/lnxtoolkit/PXE_test/img2a
/tftpboot/lnxtoolkit/PXE_test/tcrootfs
/tftpboot/lnxtoolkit/PXE_test/img3a
/tftpboot/lnxtoolkit/bsb1.lss
/tftpboot/lnxtoolkit/pxelinux.0
/tftpboot/lnxtoolkit/bsb.msg
/tftpboot/pxelinux.cfg
prompt 0
default toolscenter
timeout 100
label toolscenter
display bsb.msg
kernel /PXE_test/img2a
append initrd=/PXE_test/img3a vga=0x317 root=/dev/ram0 rw ramdisk_size=100000
tftp_server=192.168.0.1 tftp_tcrootfs=/lnxtoolkit/PXE_test/tcrootfs
tftp_tczip=/lnxtoolkit/PXE_test/tc.zip debug_level=1
silent_boot=no boot_src=4 tftp_blksize=1420 media_boot=no
cp /tftpboot/lnxtoolkit/pxelinux.cfg/PXE_test /tftpboot/lnxtoolkit/pxelinux.cfg/default
if substring(option vendor-class-identifier, 0,9) = "PXEClient" {
filename "lnxtoolkit/pxelinux.0"; # file to be served
next-server 192.168.0.1; # This server's ipaddress
}
/tftpboot/
/tftpboot/lnxtoolkit
/tftpboot/lnxtoolkit/pxelinux.cfg
/tftpboot/lnxtoolkit/pxelinux.cfg/PXE_test
/tftpboot/lnxtoolkit/PXE_test
/tftpboot/lnxtoolkit/PXE_test/tc.zip
/tftpboot/lnxtoolkit/PXE_test/img2a
/tftpboot/lnxtoolkit/PXE_test/tcrootfs
/tftpboot/lnxtoolkit/PXE_test/img3a
/tftpboot/lnxtoolkit/bsb1.lss
/tftpboot/lnxtoolkit/pxelinux.0
/tftpboot/lnxtoolkit/bsb.msg
/tftpboot/pxelinux.cfg
prompt 0
default toolscenter
timeout 100
label toolscenter
display bsb.msg
kernel /PXE_test/img2a
append initrd=/PXE_test/img3a vga=0x317 root=/dev/ram0 rw ramdisk_size=100000
tftp_server=192.168.0.1 tftp_tcrootfs=/lnxtoolkit/PXE_test/tcrootfs
tftp_tczip=/lnxtoolkit/PXE_test/tc.zip debug_level=1
silent_boot=no boot_src=4 tftp_blksize=1420 media_boot=no
ln -s PXE_test 01-00-14-5e-b5-4a-7e
host mymachine {
hardware ethernet 00:14:5e:b5:4a:7e;
option domain-name-servers 192.168.0.1; # DNS server
fixed-address 192.168.0.2; # Target system IP
filename "lnxtoolkit/pxelinux.0"; # file to be served
next-server 192.168.0.1; # This server's IP
}
TK_DISTRO_HTTP_KERNEL_PKG
TK_DISTRO_HTTP_RELEASE_PKG
TK_DISTRO_HTTP_ISOLINUX
TK_DISTRO_HTTP_INITRD
TK_DISTRO_HTTP_VMLINUX
This example shows the values
for these variables for a Red Hat Enterprise Linux 5,
Update 4 x64 installation:TK_DISTRO_HTTP_KERNEL_PKG=Server/kernel-2.6.18-160.el5.x86_64.rpm
TK_DISTRO_HTTP_RELEASE_PKG=Server/redhat-release-5Server-5.4.0.2.x86_64.rpm
TK_DISTRO_HTTP_ISOLINUX=isolinux/isolinux.cfg
TK_DISTRO_HTTP_INITRD=isolinux/initrd.img
TK_DISTRO_HTTP_VMLINUX=isolinux/vmlinuz
To perform a clone of SUSE Linux Enterprise Server 11 with Altiris, you must use Altiris Deployment Solution 6.9 SP3. To deploy a cloned image of SUSE Linux Enterprise Server 11 from Altiris, refer to Altiris Knowledgebase article 48984 to enable the necessary support.
RapiDeploy provides native imaging support for EXT2 and EXT3 file systems. By default, SUSE Linux Enterprise Server 10 (SLES 10) uses the reiserfs file system when installing. To clone and redeploy a SLES 10 image using the Toolkit jobs, you must perform the original deployment using an EXT3 file system.
To change the file system prior to installation with the Toolkit, edit the sles10.xml AutoYast file provided by the Toolkit.
<partitioning config:type="list">
<drive>
<initialize config:type="boolean">true</initialize>
<use>all</use>
</drive>
</partitioning>
with the following partitioning section:<partitioning config:type="list">
<drive>
<initialize config:type="boolean">true</initialize>
<use>all</use>
<partitions config:type="list">
<partition>
<filesystem config:type="symbol">ext3</filesystem>
<format config:type="boolean">true</format>
<mount>/boot</mount>
<size>100mb</size>
</partition>
<partition>
<filesystem config:type="symbol">swap</filesystem>
<format config:type="boolean">true</format>
<mount>swap</mount>
<size>auto</size>
</partition>
<partition>
<filesystem config:type="symbol">ext3</filesystem>
<format config:type="boolean">true</format>
<mount>/</mount>
<size>auto</size>
</partition>
</partitions>
</drive>
</partitioning>
There are special considerations for using Linux X server with a Remote Supervisor Adapter (RSA) IIRSA II port. If you are using this configuration, consider the following items:
Install the operating system in text mode. Set the color depth to 16–bit and the screen resolution to 1024 x 768.
If SUSE Linux or Red Hat Enterprise Linux is already installed and configured to run in text mode, and will never use the X Window system, no additional configuration is required for the RSA II-EXA to function correctly.
The Remote Supervisor Adapter II-EXA requires a Video Electronics Standard Association (VESA) device driver. The VESA video device driver enables the remote control screen and the local screen to display the same information (clone mode).
When using power management, the video output might not return correctly from some power saving states. To correct this problem, use the xset command to disable DPMS: xset -dpms
For more information, see IBM® Remote Supervisor Adapter II-EXA Technical Update for Linux Operating Systems available from ftp://ftp.software.ibm.com/systems/support/system_x_pdf/88p9275.pdf.
sax2 -m 0=fbdev
When using power management, the video output might not return correctly from some power saving states. To correct this problem, use the xset command to disable DPMS as shown: xset -dpms
To boot from a USB key, the key must be configured for IBM ServerGuide Scripting Toolkit, Linux Edition deployment. For more information about configuring a USB key for deployments, see Creating bootable media from a workflow.
BIOS settings for booting from a USB key are system-specific. Refer to the documentation for your systems for the correct BIOS settings and procedures to boot from USB keys.
Some systems support booting from USB keys by pressing F12 during startup. This method is the recommended one to use to deploy the Linux Scripting Toolkit from a USB key. uEFI-based systems only support booting from a USB key by using F12.
Beginning in version 2.20, the Linux Scripting Toolkit provides support for locating operating system files on IPv6 network shares. To use operating system files located in a share on an IPv6 network, you must update the variable TK_DISTRO_PATH in the appropriate Altiris job.
When performing a network-based installation of SLES11 SP1 in a static IPv6 environment, you must use either ipv6=1, which accepts both IPv4 and IPv6 addresses, or ipv6only=1, which accepts only IPv6 addresses, as a boot parameter.
ipv6only=1 netdevice=eth0 hostip=2000::2dae:2390/64
ifconfig eth0 inet6 add 2000::2dae:2390/64
unzip /tftpboot/lnxtoolkit/PXE_test/tc.zip
prompt 0
default ibmchain
timeout 100
label ibmchain
kernel pxechain.com
append ::ibm/pxelinux.0
label your_other_pxe
kernel pxechain.com
append ::your_other_pxe/pxelinux.0
|-- ibm
| |-- img2a
| |-- img3a
| |-- pxelinux.0 <- IBM's modified pxelinux.0
| |-- pxelinux.cfg
| | `-- PXE_test <- The default file for Linux Scripting Toolkit created PXE Image
| |-- tc.zip
| `-- tcrootfs
|-- your_other_pxe
| |-- vmlinux
| |-- initrd.gz
| |-- pxelinux.0 <- your_other_pxe's pxelinux.0
| `-- pxelinux.cfg
| `-- default <- your_other_pxe's default
|-- pxechain.com <- pxechain.com from tc.zip (Step 1)
|-- pxelinux.0 <- pxelinux.0 from syslinux 3.72 (or later)
`-- pxelinux.cfg
`-- default <- default file for pxechain.com