Beruflich Dokumente
Kultur Dokumente
The procedures described are not necessarily suited for field use and are not intended to be performed by customers. Access to 3Com internal networks and accounts on restricted servers may be required. Failure to follow all procedures exactly may result in a VCX server which does not work properly and may not be supported by 3Com.
1 Overview.......................................................................................................................................................2 2 FTP Server/File Locations.............................................................................................................................3 3 Starting the Installation (non-W1).................................................................................................................4 4 Starting the Installation (W1 only)................................................................................................................6 5 Installation Procedure....................................................................................................................................9 6 Booting & Configuration.............................................................................................................................10 7 VCX Installation..........................................................................................................................................12 8 Odds and Ends.............................................................................................................................................13 9 Appendix A: Building a FRU disk..............................................................................................................14 Revision History 24-Jan-2006 Brett B. Bonner 08-Feb-2006 18-Oct-2006 Brett B. Bonner Brett B. Bonner
Created based on VCX 7.0 Disk Build HOWTO Add boot options for 306/346 Knoppix 4.0.2, reference UPS Monitoring feature & functional spec Add x3650 support information
1 Overview
This document describes how to build a VCX system disk, including installation of the OS and VCX components. These instructions are suitable for use in building Master Disks for use by customers, as well as for building systems for internal use. In addition, Appendix A describes the procedure for building a FRU disk. A FRU (Field Replaceable Unit) disk is a different form of master disk, which has the ability to be configured to any supported software version and configuration type in the field.
The x306m has faster PCI/X slots - this doesn't matter to VCX as we do not use any PCI cards. Starting with VCX Linux version 5.5.0, VCX is also supported on the IBM x3650 hardware platform. This is a new IBM model which replaces the x346. The chosen model for VCX is a 7979-51U. The x3650 compares to the x346 as follows: The 3650 offers one or two, dual core, Intel Xeon 5140 Woodcrest processors, with a much faster 1333MHz FSB. This offers the potential of up to four processing cores. The global workhorse model which we are using for VCX uses 2.33GHz processors, but the dual cores, faster FSB, and architecture changes should provide improved performance over the x346. The system uses DDR2-667 PC2-5300 fully buffered memory. Disk drives are SAS (Serial Attached SCSI) instead of U320-SCSI. Note that although some models of x3650 support 2.5 SAS drives, the -51U model uses 3.5 disks. There is no built in floppy disk. There is a different Ethernet controller (Broadcom 5708 NetXtreme II) The system no longer offers legacy PS/2 keyboard and mouse connectors, but expects use of a USB keyboard and mouse. The may affect some users; however, a serial port is still available and will be configured as the default console for customers. As with the x346 and x306m, a BMC (baseboard management controller) with IPMI support is included. See the notes on IPMI under the x306m section, above.
Although the base unit has basic hardware RAID (0/1/10) capability, we do not plan on supporting this for VCX at this time, since the existing VCX RAID implementation offers good performance and the benefit of consistency across all platform types.
Other differences, such as PCI slot configuration, exist but are not relevant to VCX usage. VCX Linux and VCX are, of course, still supported on prior platforms including the x306, x346, x345, and V6000 (W1). However, VCX 7.1 will ship on new systems only on the x306m, x346, and V6000. A transition from x346 to x3650 will occur in late 2006/early 2007.
2.2 Oracle
The standard location for Oracle files is : ftp://usand006w2k.ne.3com.com/vcx/oracle/ ftp://mselvarag.wan.3com.com/var/ftp/pub/oracle/ Within this directory may be multiple Oracle rpms. Be sure to retrieve the correct version for your installation. (Typically this is the highest-numbered version.)
Note that VCX Linux 4.2.0 and newer also include an erasePartitionTable command that can be used to zero the partition table in place of the dd command above.
For the curious, these options do the following: knoppix26 Selects the Linux 2.6 kernel, which is needed to support newer hardware lang=us Selects US keyboard layout atapicd Needed so that Knoppix works properly with an IDE CDROM under the 2.6 kernel nodma Disables dma, which causes issues on certain systems 2 Selects runlevel 2, which does not start the Knoppix GUI (X Windows) VCX 7.1 Disk Build HOWTO Page 5 of 16
If you are uncertain of the values to use, please contact your network administrator for assistance. If your network has a DHCP server, DHCP may be used during VCX Linux installation. However, in most cases, you will still want a static IP for the installed system. While VCX Linux for VCX 6.0 and later does support DHCP as an option, the implementation is designed for a specific use case and requires special server configuration. Unless you are testing something related to this, it is almost certainly the case that you should use a static IP address. The Knoppix 3.6 CD also includes a utility, network-setup, which can be used to set up networking for purposes of performing the rest of the installation. If you choose to use this, select the netcardconfig option and follow the prompts.
4.1.1 Setting Up
Check that power is off on both the W1 you will be using as a host (well call this W1-A) and the W1 whose disk you need to build (W1-B). Wear a grounding wrist strap while working on the W1. The units are very sensitive to ESD and are easily damaged. Loosen the 2 screws and 2 thumbscrews holding the disk in W1-B and pull out the disk module. Remove the blank cover plate on the 2nd disk slot of W1-A (youll find this next to the installed disk, on the back of the unit). Install the disk module in this slot.
4.1.2 Installation
Boot W1-A and login as root. Note: if the W1-B disk previously had VCX installed on it, strange errors may be seen at boot, including messages about duplicate labels, read-only partitions, various [FAILURE] messages, and a long pause while starting syslog. These are the result of the two disks having duplicate partition labels. If this occurs, erase the partition table on the W1-B disk using the command: dd if=/dev/zero of=/dev/hdc bs=512 count=1 and then reboot. Ensure that networking is operational. If not, configure it. cd to the /tmp directory and proceed with the installation as documented in section 5. Be very certain that you specify the correct device this should be /dev/hdc in this case. This instructs the script to install the new VCX Linux version on the 2nd drive, and will not disturb the version already installed on /dev/hda (on which the system is running).
When asked if this is a W1, say yes. Do not reboot once the OS is installed. When Reboot now? is asked, say no and then do a shutdown h now to shut the system down.
4.1.3 Post-installation
Once the OS is installed, remove the W1-B disk module from W1-A and reinstall it in W1-B, being sure to wear your grounding strap. The W1 should now be able to boot from the disk and you can carry on with the rest of the VCX installation.
4.2.3 Booting
Enter the BIOS and ensure that the drives are configured to allow booting from the CDROM and access to the IDE bus you have connected the W1 to. The details will vary depending on the PC used! Boot the Knoppix CDROM. If you are not sure which options to use, section 3.4.1 may provide a useful starting point. Configure networking following the instructions in section 3.5.
4.2.4 Installation
Follow the instructions in section 5. The installation device to use varies depending which IDE bus you connected the drive to. If you used the first or primary bus, it is /dev/hda; the secondary bus is /dev/hdc.
When asked if this is a W1, say yes. Do not reboot onto the disk once the OS is installed. When Reboot now? is asked, say no and then do a shutdown h now to shut the system down.
Run the command diskCopy, specifying /dev/hda as the source and /dev/hdc as the destination drives. In the event your system has an older version of VCX Linux which does not provide the diskCopy command, download the diskCopy.sh script from: usand006w2k.ne.3com.com/vcx/vcx-linux/utils/diskCopy.sh mselvarag.wan.3com.com/var/ftp/pub/vcx-linux/utils/diskCopy.sh The disk copying process will take most of an hour to complete.
5 Installation Procedure
This procedure uses a shell script which prompts for some minimal information, and takes care of all of the other steps needed to install VCX Linux automatically. It is suited for installing VCX Linux on SATA, IDE, or SCSI based systems which are dedicated to VCX. It must not be used on a development or other system which has partitions that must be preserved, as it will completely repartition and reformat the disk.
If you get a message about the device not existing, you probably forgot to initialize the disk from the SAS controller BIOS. See section 3.3. 2 This is not a typo. SATA disks appear as virtual SCSI devices. VCX 7.1 Disk Build HOWTO Page 9 of 16
IBM x305, Intellistation Z Pro 6221/10U, most IDE W1 (using another W1 as host) W1 (using a PC as host) device depends on which bus was used for connection
If you specify a nonexistent device the script will give an error and let you retry. If you specify a device that exists but cant be installed to (for example, the CDROM drive) then you will get an error when the script tries to partition it, and you can simply start over if that occurs. If installing to an IDE device, you will be asked if this installation is for a V6000 (W1). Answer yes or no as appropriate. The script will then partition your disk, format the partitions, and prepare to download the VCX Linux image. You will be given a menu of choices of FTP servers. Select one or choose none of these and enter the IP address of the remote server. For the predefined FTP servers you will then be prompted with a default path. Press Enter, or if using some other server, enter the ftp path to retrieve the image. If the remote server does not support anonymous downloads the script will prompt for a user name and password. Note: If downloading from a server within the pvt domain, including usand006w2k, specify the username as pvt\myusername. The password is, of course, your PVT password. The image will then be retrieved and installed to the correct partition. When partimage completes, a dialog will appear indicating that the operation succeeded. Press Enter to continue. The installer will then label the partitions and install the boot loader. If installing a W1 additional modifications will be made automatically. The serial port is used as the console by default and MUST be used for any master disk being built for customer use. If installing to anything other than a W1, you will be asked whether you wish to use the serial port as the console; the default answer is yes. If you say no, then the system will be reconfigured to use the PCs vga/keyboard ports as the console. This should be done only on systems for internal use. If on a SCSI, SAS, or SATA system, fstab will be updated appropriately. Note for those familiar with previous VCX installs: The installer will no longer prompt for whether the installation device is SATA, because the Knoppix 3.6 CD has SATA support and so devices appear by their correct names. You do not need to do anything special here for SATA systems any more. At the end, you will be asked if you want to reboot. Say yes. Note that Hyper-threading must be enabled on systems that support this feature in order for the OS install to complete successfully. To check this: Hit F1 to enter setup when the system starts back up. Select Advanced Setup Select Processor Control If the item Hyper-Threading Technology is available, set it to Enabled.
Exit setup When the system reboots, be sure that the CD is not in the drive.
vcx-setup was formerly called (and is still available as) setup. It was renamed for consistency with other vcx- scripts. VCX 7.1 Disk Build HOWTO Page 10 of 16
Select the configuration type which this system is to provide Configure networking using vcx-config-network Write a configuration file for the installed VCX components using vcx-config-services Apply the configuration file to the components (firstboot configuration)
Start up VCX In order to ensure consistent results and proper testing of the entire first-time-setup sequence, all systems should be built as though they are customer disks.
6.4 Log in
<hostname> login: root Password: pvadmin
/sbin/route add default gw 192.168.1.254 Complete installation of the rest of VCX as documented below. Because the wizard was not run, and the network values were changed interactively rather than by editing configuration files, the system will retain its default values and will come up in a fully-installed but completelyunconfigured state, as it should.
7 VCX Installation
This section contains instructions for installing the rest of the VCX system so that it is ready for initial configuration and use. Because single SKU support means that selection of configuration type is done at first time setup, there are no longer separate instructions for different config types. All systems should use the instructions listed here.
A disk space check is performed prior to installing any packages. Nothing will be installed if there is not enough space for the new RPMs. Note that it is not necessary to reboot after VCX applications are installed.
Beep codes are generated only for first-time setup, not upgrades, even on remotely managed branch offices. Continuous beeping indicates a failure of automatic setup. Logging in will stop the beeping. A beep-beep-pause-pause sequence repeated several times indicates successful automatic setup.
8.2.1 No HTTPD
The Apache (httpd) web server is not started when no assembly is present. During the boot sequence (or if /etc/init.d/httpd start is invoked manually) a message is printed which says: Starting httpd: (no active VCX version not started) This is normal behavior. HTTPD will be started when a config type is chosen.
8.2.4 vcx-showconfigtype
If vcx-showconfigtype is called, instead of printing a config type code (or unknown) it detects the unconfigured state and reports: not-selected : 6 available (Where 6 is the number of possible config types, e.g. selectable VSBOM files.) Once an assembly is made the behavior reverts to normal.
9.3.4 setupFruDisk.sh
setupFruDisk.sh is, like vcxSetup.sh, a separate script which is downloaded and run to perform disk configuration. It takes care of setting up everything necessary on a FRU disk. This script contains release specific information (e.g. which releases are to be put on the FRU disk). Like the DESCRIPTION file, the intention is to update it periodically (but not weekly) during the 7.0 development cycle. setupFruDisk.sh is posted at the following location: ftp://usand006w2k.ne.3com.com/vcx/vcx-linux/utils Download the script and run it with the command: sh setupFruDisk.sh It will be necessary to provide a username and password when prompted, so that the script can access usand006w2k. W1 does not support any release prior to 7.0. If setupFruDisk.sh is run on an IDE system it will ask whether the disk is for a W1. If yes, then no releases before 7.0 will be put on the disk. Once the script has completed the FRU disk is ready for use.