manualshive.com logo in svg

Ammasso 1100, User Manual, Page: 26 / 66

Share
Download
Ammasso 1100 User Manual Download Page 26

 

26 

4  The Ammasso MPI Library 

4.1  Overview 

MPICH is a portable implementation of the Message Passing Interface (MPI) standard.  
Currently the Ammasso 1100 supplies and supports the MPICH version 1.2.5 of MPI from 
Argonne National Labs. The Ammasso MPICH implementation is a fully supported port of 
MPICH over Ammasso’s RNIC verbs interface designed to take advantage of the Ammasso 
1100’s low latency and high throughput.  Additional information, full documentation, and 
manual pages for MPICH are available on the MPICH web site at:

 

http://www-unix.mcs.anl.gov/mpi/mpich/ 

 

Note that other MPI implementations have been qualified and tested to run over top of the 
Ammasso RNIC exploiting the advantages it provides.  See the specific MPI vendor’s web 
site as well as Ammasso’ support web site for details on those implementations. 
 
The following section provides some basic information about leveraging the Ammasso 
adapter with your MPI application using the Ammasso MPI implementation. Installation, 
configuration, and tuning examples are supplied.  The information provided is for reference, 
as there may be multiple ways to accomplish these tasks, depending on each development 
environment. 

4.1.1  Compiler Support 

The Ammasso 1100 is designed to work with the standard compiler suites available in the 
Linux community.  We have tested our MPI implementation with the GNU C and the F77 
suites that are bundled with the traditional Linux distributions such as Red Hat and SuSE.  
We have also tested our MPI implementation with the Intel Version 7x and 8x C/C++ and 
F90 suites.  As we progress, other compilers may be added to our test suite.  Please see the 
Ammasso support web site for details and specifics. 

 

4.2  Installation 

NOTE: In order to compile the Ammasso 1100 MPICH 1.2.5 Package, the AMSO1100 

package must be installed and built.  If you are updating from a previous release, please see 
the HOWTO_UPDATE.txt file for information on removing software from previous releases. 

 
1.  Unarchive the files in 

AMSO_MPICH.tgz 

into a working directory with: 

        # cd <work_dir> 
        # tar -zxf <path_to>/AMSO_MPICH.tgz 

 
2.  Change into the 

AMSO_MPICH

 directory, build Ammasso’s MPICH implementation, and 

capture the output to a logfile with: 

         

   

# cd ./AMSO_MPICH 

        # make install 2>&1 | tee make_install.logfile 

 

3.  Answer the configure questions for your specific needs.  Below is a description of the 

questions asked. 

 

Summary of Contents for 1100

Page 1: ...gh Performance Ethernet Adapter User s Guide Ammasso Inc 345 Summer St Boston MA 02210 Main 617 532 8100 Fax 617 532 8199 http www ammasso com Revision 1 2Update 1 July 22 2005 Copyright 2005 Ammasso Inc All rights reserved ...

Page 2: ...apter except as set forth in the license and warranty agreements The Ammasso 1100 High Performance Ethernet Adapter is the exclusive property of Ammasso Inc and is protected by United States and International copyright laws Use of the product is subject to the terms and conditions set out in the accompanying license agreements Installing the product signifies your agreement to the terms of the lic...

Page 3: ...2 SYSTEM HARDWARE REQUIREMENTS 12 2 3 ADAPTER HARDWARE INSTALLATION 12 2 3 1 CHOOSING A SLOT FOR INSTALLATION 12 2 3 2 TOOLS AND EQUIPMENT REQUIRED 12 2 3 3 ADAPTER INSERTION PROCEDURE 13 3 ADAPTER SOFTWARE INSTALLATION 14 3 1 SYSTEM SOFTWARE REQUIREMENTS 14 3 2 OVERVIEW 14 3 3 INSTALLING THE ADAPTER SOFTWARE PACKAGE 14 3 3 1 MAKEFILE TARGETS 16 3 3 2 MAKEFILE CONFIGURATION VARIABLES 17 3 4 DISTRI...

Page 4: ...INSTALLATION VERIFICATION 40 5 4 2 KDAPL INSTALLATION VERIFICATION 41 5 5 REMOVING THE AMMASSO DAPL INSTALLATION 41 5 6 AMMASSO DAPL COMPATIBILITY SETTINGS 41 5 6 1 CCAPI_ENABLE_LOCAL_READ 41 5 6 2 DAPL_1_1_RDMA_IOV_DEFAULTS 42 6 CLUSTER INSTALLATION 43 6 1 INTRODUCTION 43 6 2 STEPS ON THE INITIAL BUILD SYSTEM 43 6 2 1 PREPARE THE KERNEL 43 6 2 2 INSTALL AMSO1100 AND BUILD BINARY FOR CLUSTER DEPLO...

Page 5: ... TFTP SERVER 60 7 7 BUILDING PXELINUX 61 7 8 DISKLESS LINUX BOOT VIA PXE 61 7 8 1 CONFIGURE A ROOT FILE SYSTEM 62 7 8 2 CONFIGURE THE NFS SERVER 62 7 9 UPDATING THE AMMASSO 1100 OPTION ROM IMAGE 63 APPENDIX A SUPPORT 64 OBTAINING ADDITIONAL INFORMATION 64 CONTACTING AMMASSO CUSTOMER SUPPORT 64 RETURNING A PRODUCT TO AMMASSO 64 APPENDIX B WARRANTY 65 ...

Page 6: ...rect Memory Access technology and CPU offload RDMA moves data from the memory of one server directly into the memory of another server over a network without involving the CPU of either server CPU offload lowers the processing requirements on the host CPU when using RDMA increasing its efficiency Low latency assures that the time it takes for data to get from one application to the other is minimi...

Page 7: ...ased adapters The adapter supports sockets by maintaining a separate IP address within the card for sockets traffic and rapidly moving that traffic to the host network stack where it can be processed normally Having support for both a high performance path and sockets path allows a single cable connection and switch data port for all traffic types either sockets or fast path RDMA based simplifying...

Page 8: ... data into the host s memory without requiring operating system involvement at either end Since all of the information pertaining to the remote virtual memory address is contained in the RDMA message itself and host and remote memory protection issues were checked during connection establishment the operating systems do not need to be involved in each message For each RDMA command the Ammasso 1100...

Page 9: ...pen source distributions MPI is considered the de facto standard for writing parallel applications A version of the MPI library MPICH 1 2 5 is available that is compatible with the Ammasso 1100 adapter 1 2 4 What Is DAPL and Why Is It Used Direct Access Programming Library DAPL defines a single set of user APIs used in Database and Storage RDMA Enabled environments The DAPL API is defined by the D...

Page 10: ...APIs MPI Argonne National Labs MPICH Version 1 2 5 DAPL User Mode uDapl and Kernel Mode kDapl ver 1 2 BSD Sockets non RDMA 1 4 3 Operating Systems See http www ammasso com support 1 4 4 Platforms IA 32 and EM64T compatible systems AMD Opteron 32 64 compatible systems 1 4 5 Management Field upgradeable PXE boot 1 4 6 Standards Compliance IEEE Ethernet 802 3 802 3ab copper PCI PCI X 1 0 1 4 7 Hardwa...

Page 11: ...ment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense This is a Class A Product In a domestic environment this product may cause radio interference in which case the user may be required to take adequate measures Observe the following precautions when working with your Ammasso 1100 High Performance ...

Page 12: ...inserting the adapter use your system documentation to determine which slots support PCI X Be sure to set any jumpers correctly on the motherboard to ensure that the slot is correctly configured The Ammasso 1100 will not operate correctly in a slot that is running in PCI mode If a PCI device is attached to a PCI X bus the bus will operate in PCI mode The Ammasso 1100 Ethernet Adapter is designed t...

Page 13: ...it push the adapter gently but firmly into place until you feel its edge mate securely with the connector slot Make sure that the adapter aligns so that you can see the port through the back of the computer 8 Use a screw to attach the adapter to the chassis see system documentation for details 9 Replace the computer cover 10 Attach the RJ45 cable to the port on the adapter and plug the other end o...

Page 14: ...SO_DAPL tgz is the DAPL package and requires the AMSO1100 package This package must be installed to enable DAPL applications over the Ammasso 1100 adapter These packages must be built and installed on each machine in your cluster The following instructions detail how to install on one node For cluster wide deployment on multiple nodes please also see chapter 6 Cluster Installation 3 3 Installing t...

Page 15: ...his point you have successfully installed the AMSO1100 package on your system If you are deploying the Ammasso software on many machines in a cluster please see chapter 6 for more details The various commands libraries and drivers are installed in the directory chosen in step 3 The commands are linked into usr bin The libraries are linked into usr lib or usr lib64 as required The man pages are lin...

Page 16: ...riables needed to build the product build Builds AMSO1100 depends on config target install Installs AMSO1100 depends on build target uninstall Uninstalls AMSO1100 if it is installed clean Deletes cleans the build objects from the source tree binary This will put together a binary that can be put on other machines with identical setups The resulting file ammasso1100 bin can be executed on each iden...

Page 17: ...ource tree for the kernel you are running KERNEL_CODE The release string for the kernel as returned by the uname r command O Path to alternate kernel build output directory BUILD_32LIBS If the AMSO1100 package is configured on a 64 bit distribution this variable will be set to y if 32 bit libraries should be built in addition to 64 bit libraries Here is a sample Config mk created by the make confi...

Page 18: ...ackages menu Development Tools Kernel Development Legacy Software Development and Compatibility Arch Support In addition under the Development Group menu select the following Compatibility Arch Development Support and Legacy Software Development Installing these packages will allow both 32 bit and 64 bit MPI applications to run on the 64 bit installed system 3 4 1 2 RedHat Kernel Source Tree Prepa...

Page 19: ...wing glibc packages glibc 32 bit shared libs and glibc 32bit devel packages 3 4 2 2 SuSE Kernel Source Tree Preparation First ensure the system has a clean source tree by doing a make mrproper cd usr src linux make mrproper Next edit the Makefile so that the version value matches the running kernel By default the variable EXTRAVERSION includes the string custom Change this variable to match the ru...

Page 20: ... an O option to specified This option tells kbuild where to put the configured kernel files If the kernel is configured with O then all external modules must be built with the same parameter If your kernel source was built using the O variable you must specify make install O path to kernel files when building the package ...

Page 21: ...ation amso_stat 8 Return operational information of the current running Ammasso 1100 installation amso_uninstall 8 Remove an Ammasso installation ccflash2 8 Ammasso firmware update utility cclog 8 Ammasso RNIC debug logging utility cconfig 8 Ammasso RNIC IP address configuration command ccons 8 The comand to connect to the Ammasso RNIC internal console ccping 8 Ammasso RNIC ping command ccregs 8 C...

Page 22: ..._dir data hostname s rnic_cfg For example usr opt ammasso data fred rnic_cfg contains the configuration for the host named fred NOTE This file can be located anywhere on your system The configuration file etc ammasso conf contains a variable that contains the path to the rnic_cfg file The amso_cfg 8 command is used to configure the running system based on the data found in the rnic_cfg 8 configura...

Page 23: ...se instance This is the instance number for a given definition This number starts counting from 0 Each instance is another IP address netmask etc definition for a given RNIC instance This allows having multiple IP addresses per RNIC ipaddr This is the specific IP address in network dotted quad notation to use for this interface mask This is the network mask netmask of the specific configuration mt...

Page 24: ... verify CCIL configuration you can use the ifconfig 8 command The CCIL interface is called ccilnet0 sbin ifconfig ccilnet0 ccilnet0 Link encap Ethernet HWaddr 00 0D B2 00 07 B2 inet addr 10 40 48 52 Bcast 10 40 63 255 Mask 255 255 240 0 inet6 addr fe80 20d b2ff fe00 7b2 64 Scope Link UP BROADCAST RUNNING MTU 1500 Metric 1 RX packets 0 errors 0 dropped 0 overruns 0 frame 0 TX packets 6 errors 0 dro...

Page 25: ... first example shows that issuing the ccping command to the local RDMA address will not result in a reply The second example shows that issuing the ccping command to a remote RDMA address will result in a reply ccping 0 10 40 32 52 pinging 10 40 32 52 via TCP SYN to port 1 10 40 32 52 no answer ccping 0 10 40 32 53 pinging 10 40 32 53 via TCP SYN to port 1 10 40 32 53 is alive 10 40 32 53 is alive...

Page 26: ...ence as there may be multiple ways to accomplish these tasks depending on each development environment 4 1 1 Compiler Support The Ammasso 1100 is designed to work with the standard compiler suites available in the Linux community We have tested our MPI implementation with the GNU C and the F77 suites that are bundled with the traditional Linux distributions such as Red Hat and SuSE We have also te...

Page 27: ...ption builds shared libraries so files for use by applications If this is left to the default of n only the static libraries a files are built Q7 Enter path to remote shell usr bin rsh Argonne MPICH from which Ammasso MPICH derives assumes the use of the BSD rsh 1 command hence Ammasso s choice to leave that as the default However best security practices recommend a stronger system such as Secure ...

Page 28: ...install procedure will check whether the environment variable LD_LIBRARY_PATH points to the lib directory of the FORTRAN 90 compiler If it does not the install will fail Q10 Build 32 bit mpich y or n no This question will only appear when Ammasso s MPICH implementation is built on a 64 bit machine By default Ammasso builds only one version of MPICH on any machine If the user wishes to have a 32 bi...

Page 29: ..._MPICH package A 32 bit binary file called image mpich 1 2 5 32 bin will also be generated if you are running on a 64 bit machine and have chosen to build the 32 bit version of Ammasso MPICH 4 2 2 Makefile Configuration Variables The configuration file Config has the following variables CC This is the path to the C compiler that will be used to build MPICH C programs CPP This is the path to the C ...

Page 30: ...RAN 90 compiler This gets set by the install utility automatically based on the FORTRAN 90 compiler selected PLATFORM This variable determines the platform on which to build Ammasso MPICH The currently supported options are native and x86_32 The latter is only necessary if you wish to build a 32 bit version of Ammasso MPICH on a 64 bit version of the native OS CUSTOM_CFLAGS This is a list of flags...

Page 31: ... Ammasso version of MPICH As an example to compile and link the cpi c program the following steps need to be performed on each system that will be used for running the program Since it is important that the path to the application is the same on all machines most sites use a distributed file system such as NFS Lustre etc to provide a single file name space for all files used by MPI Create an objec...

Page 32: ...ust either be a valid IP address or a host name that returns a valid IP address from the DNS NOTE the TCP IP address used for MPI control should not be confused with the RDMA IP Address which is used by MPI to move MPI data The TCP IP address traditionally would correspond to the AMSO_IPADDR found in the amso_ccil_0_0 function in the rnic_cfg file or a TCP IP address associated with another NIC e ...

Page 33: ...for startup of remote MPI processes This requires that each cluster node be accessible via rsh 1 or ssh 1 without the need to enter a password You can verify that this is the case by issuing a simple command e g rsh hostA hostname hostA The default remote execution service is selected during install To change the remote execution service dynamically set the environment variable P4_RSHCOMMAND For e...

Page 34: ...were saved usr opt ammasso mpich 1 2 5 32 share machines sample usr opt ammasso mpich 1 2 5 32 share machines LINUX 4 7 Ammasso MPI Tunable Parameters The following parameters can be used to tune the maximum amount of memory that will be consumed by the AMSO_MPICH RDMA driver Memory consumed by the driver is locked down or pinned and not available for application or even operating system use so at...

Page 35: ...pplication data The size of the vbuf structure including space for payload is 8360 bytes Thus the value 8360 is used below to compute memory utilization 4 7 1 VIADEV Environment Variables NOTE Shell environment variables are used to allow tuning memory consumption by the MPI RDMA driver These variables must be set in the user account used to execute the MPI run EG the bashrc file Further the value...

Page 36: ...h 1 process on each node NC 16 LP 1 NP 16 RP 15 the memory used for receive buffers would be 240 8360 15 30096000 bytes 28 70 MB 4 7 1 3 VIADEV_SQ_DEPTH This parameter specifies the Send Queue SQ depth for each RDMA Queue Pair QP This depth acts as a flow control mechanism between the MPI application and the local RNIC adapter Each SQ entry when doing a particular IO operation RDMA SEND will consu...

Page 37: ...unt of memory should be determined based on how much memory your MPI application needs for doing computation Given you can actually determine that you can then adjust these parameters to reduce the amount of memory used by the MPI RDMA driver A few guidelines are offered here Try reducing VIADEV_NUM_RDMA_BUFFERS first The default for this parameter doesn t particularly scale well or evenly as your...

Page 38: ...releases 1 Untar AMSO_DAPL tgz into a working directory cd work_dir tar zxf path_to AMSO_DAPL tgz 2 Change into the AMSO_DAPL directory build dapl and capture the output in a logfile cd AMSO_DAPL make install 2 1 tee make_install logfile 3 Answer the configure questions for your specific needs Below is a description of the questions asked Q1 Enter the AMSO1100 build path This is the full path to t...

Page 39: ...entical setups The resulting file image dapl 1 2 bin can be executed on each identical system in a cluster to install and configure the AMSO_DAPL package 5 2 2 Makefile Configuration Variables The configuration file Config has the following variables STARCORE This is the path to the AMSO1100 source tree It must be an absolute path PLATFORM The target build platform Possible values are x86_32 and x...

Page 40: ...fying DAPL Installation Once the DAPL software has been installed sample programs are available to verify the installation These programs can be found in install_dir dapl 1 2 bin The sample programs are client server programs Two nodes are required in order to run these examples One node must start the server program first then the second node can start the client program Test scripts are availabl...

Page 41: ...l RDMA Write 0 00 MB 0 00 MB Sec DT_cs_Client End of Work Client Exiting This test will take a few minutes to complete 5 5 Removing the Ammasso DAPL Installation Use the dapl_uninstall command to remove the AMSO_DAPL installation etc ammasso conf INSTALL_DIR dapl 1 2 dapl_uninstall Uninstall dapl found at usr opt ammasso dapl 1 2 y or n no y Dapl in usr opt ammasso dapl 1 2 has been removed 5 6 Am...

Page 42: ...e been defined to allow the consumer application to specify a maxmimum IOV depth for RDMA Read and RDMA Write DTO requests Version 1 1 of the DAT API only specified the maximum IOV depth for SEND DTO requests With the dapl 1 2 release from Ammasso if a consumer application does _not_ specify these new attributes when creating a DAT endpoint they will default to zero thus disabling RDMA Read and Wr...

Page 43: ...ining systems in the cluster will be referred to as the cluster nodes 6 2 1 Prepare the Kernel 1 If this is the first time this system has been used to build AMSO1100 prepare the kernel This step needs to be done as the root user A full make is needed for SuSE 9 1 since kernel_dir arch x86_64 kernel vmlinux lds s is only created after a full make vmlinux lds s is different from vmlinux lds S It is...

Page 44: ... ammasso You may remove the software without destroying any of the node configuration data such as RDMA CCIL IP addresses Is it ok to remove any previously installed files y or n y Re installing to usr opt ammasso Saving stored data in usr opt ammasso data app64 01 The Amso1100 software installed in usr opt ammasso has been removed The installer has detected usr opt ammasso data app64 01 rnic_cfg ...

Page 45: ...em Note the file rnic_cfg which is used to set the IP settings of the RNIC This file will be used as a template for the cluster nodes Before building MPICH and DAPL the next step is to create the binary image file for installation on the cluster nodes 3 Build a binary image for install on the cluster nodes This step can also be done at a later time and after a reboot provided the AMSO1100 build di...

Page 46: ...ally using the make requirements order Although the config step does not need to be done by the root user the install does so doing this step as a user with root privileges is recommended make config Enter the AMSO1100 build path tmp AMSO1100 Base directory to install mpich usr opt ammasso Enter path to c compiler usr bin gcc Enter path to c compiler usr bin g Enter path to fortran 77 compiler usr...

Page 47: ...s step can also be done at a later time and after a reboot provided the AMSO1100 and AMSO_MPICH build directories are still present The MPICH binary will install in the same base directory as specified in the make config step for MPICH If a local install has already been done via make install the make binary needs to re install to ensure a correct directory structure Therefore the make binary will...

Page 48: ...00 build directory allows the configuration to automatically find it cd tmp ls AMSO1100 tgz ICE unix YaST2 02308 zPffTu AMSO_MPICH tgz qt 3Ddiag Yp3238 gconfd root sysconfig update AMSO1100 hps test X11 unix AMSO_DAPL tgz tar zxf AMSO_DAPL tgz ls AMSO1100 tgz hps test X11 unix AMSO_MPICH ICE unix YaST2 02308 zPffTu 3Ddiag Yp3238 AMSO_MPICH tgz qt AMSO1100 gconfd root sysconfig update AMSO_DAPL tgz...

Page 49: ...tgz hps test X11 unix AMSO_MPICH ICE unix YaST2 02308 3Ddiag Yp3238 AMSO_MPICH tgz qt AMSO1100 gconfd root sysconfig update ammasso1100 bin image dapl 1 2 bin image mpich 1 2 5 bin rm rf AMSO The build system can now be rebooted 6 3 Steps on the cluster node systems Now that the AMSO1100 MPICH and DAPL packages have been built on the initial build system only installations are required on the rema...

Page 50: ...t be deleted by an amso_uninstall and will be reused by follow on ammasso1100 bin installs This step needs to be done as a user with root privileges Copy or transfer the rnic_cfg file from section 6 2 2 to the directory specified above In this example the directory is usr opt ammasso data app64 02 Edit this file with the new address settings pwd usr opt ammasso data app64 02 tail rnic_cfg function...

Page 51: ...6 On each cluster node install the DAPL software This step needs to be done as a user with root privileges Copy or transfer the image dapl 1 2 bin script to the tmp directory of the cluster node system This can be done for example using scp 1 or rcp 1 for example scp foo tmp image dapl 1 2 bin tmp cd tmp ls image dapl image dapl 1 2 bin tmp image dapl 1 2 bin Ammasso Dapl binary installer created ...

Page 52: ...loyment For deployment on a large number of clusters a cluster administrator will want to script an installation procedure with 1 an uninstall of previous Ammasso release software 2 an install of ammasso1100 bin image mpich 1 2 5 bin and image dapl 1 2 bin 3 place a new rnic_cfg for the system 4 reboot The script will need to utilize rsh 1 ssh 1 or perhaps expect 1 to access each cluster node ...

Page 53: ...t the filenames of a linux kernel and associated ramdisk PXELINUX then downloads them and finally boots the actual Linux kernel we wish to execute Once the kernel boots the network driver used by the PXE boot firmware is no longer available Therefore if you use the network early in your kernel boot process for instance to remotely mount you root filesystem via NFS the user either needs a network d...

Page 54: ... linux sys devccil obj_ uname r _release ccil o 2 6 Kernel AMSO1100 software host linux sys devccil obj_ uname r _release ccil ko The firmware and firmware loading utility can be copied anywhere into the ramdisk We recommend putting them into ccore The Ammasso kernel module needs to be copied into the network modules location of the ramdisk file system 4 The init scripts of the ramdisk file system...

Page 55: ... load that image At boot time the server will present the following Boot from N etwork or Q uit The default N is used if nothing on the keyboard is depressed causing the system to perform a network boot If Q is depressed the PXE boot code will be disabled and the system will boot normally 7 4 Building the RAMDISK The ramdisk contains programs that are used to help in the start up process When boot...

Page 56: ...rce directory build the BusyBox applications with cd BUSYBOX make dep make make install This places the BusyBox applications into the BUSYBOX _install directory 7 4 2 Building modutils or module init tools You only need the statically linked insmod 8 First configure modutils for 2 4 kernels or module init tools for 2 6 kernels cd MODUTILS configure disable insmod static enable combined enable stri...

Page 57: ... the kernel that will be PXE booted cp AMSO1100 software host linux sys devccil obj_ uname r _release ccil o INITRD modules net Depending on your kernel configuration you may need to copy additional drivers to the ramdisk These drivers can be found in lib modules uname r kernel With most RedHat installations we needed drivers to support NFS The modules we needed were sunrpc o ko lockd o ko and nfs...

Page 58: ...smod modules net sunrpc ko insmod modules net lockd ko insmod modules net nfs ko Load the RAW socket support driver insmod modules net af_packet ko Load the Ammasso 1100 firmware echo ccore ccos boot ccore ccos bin 0x cat ccore ccos bin_start ccore ccos boot ccore ccos bin 0x cat ccore ccos bin_start Load the ccilnet driver insmod modules net ccil ko Define the interface name export IFACE ccilnet0...

Page 59: ...d the ramdisk image may need to be larger dd if dev zero of PXEROOT initrd img bs 1024K count 16 Next format the ramdisk mke2fs F m0 b 1024 PXEROOT initrd img Then mount it and copy the data to it mkdir mnt initrd mount o loop PXEROOT initrd img mnt initrd tar cvf INITRD cd mnt initrd tar xvfp Lastly unmount it and compress it umount mnt initrd gzip 9 PXEROOT initrd img 7 5 Installing and Configur...

Page 60: ...linux 0 7 6 Installing and Configuring a TFTP Server You will need a TFTP Trivial File Transfer Protocol server that supports the tsize option The one we used is Peter Anvin s tftp server http www kernel org pub software network tftp tftp hpa 0 36 tar gz We recommend that you ensure that your external firewall blocks port 69 for both UDP and TCP since tftp has no security We made a world readable ...

Page 61: ...ITRD initrd img gz tftpboot Copy your kernel to tftpboot and copy the filesystem you want to use to tftpboot Create a config file named default for PXE It goes in the directory tftpboot pxelinux cfg Example KERNEL vmlinuz 2 4 20 6smp APPEND nfsdir 10 40 0 1 NFSroot client1 init sbin init initrd initrd img gz TIMEOUT 10 KERNEL specifies the kernel image APPEND needs the IP address of the NFS server...

Page 62: ...l NFS mounts in NFSROOT etc fstab have the nolock option turned on c Disable networking we set this up in the ramdisk over AMSO1100 usr sbin chroot NFSROOT sbin chkconfig del network d Create the following symbolic links since etc will be read only ln sf proc mounts NFSROOT etc mtab ln sf var resolv conf NFSROOT etc resolv conf More info on creating NFS root filesystems can be obtained at http www...

Page 63: ... HOWTO_UPDATE txt for more specifics on updating the software and hardware Ammasso provides utilities which allow this image to be updated by the user The ccflash2 utility can be used to update images on the Ammasso 1100 network adapter In order to update the option ROM image the pxe flag should be used The following is an example of updating the option ROM ccflash2 t pxe 0 AMSO1100 verbatim fw am...

Page 64: ...nce contact your Ammasso supplier Ammasso Customer Support can be reached using the following contact information E mail support ammasso com Telephone 617 532 8110 Fax 617 532 8199 http www ammasso com Post mail Ammasso Inc 345 Summer St Boston MA 02210 Returning a Product to Ammasso Ammasso requires its customers to obtain a RMA number from Support to return a product Once received the customer i...

Page 65: ...either to the reseller from whom you purchased it with an explanation of any deficiency If you ship the adapter product you must assume the risk of damage or loss in transit You must use the original container or the equivalent and pay the shipping charge Ammasso may replace or repair the adapter product with either new or reconditioned parts and any adapter product or part thereof replaced by Amm...

Page 66: ...censee or Sublicensees and such use is entirely at the user s risk Licensee agrees to defend indemnify and hold Ammasso harmless from and against any and all claims arising out of use of the adapter product in such applications by Licensee or Sublicensees Software Software provided with the adapter product is not covered under the hardware warranty described above If the Software has been delivere...

Reviews:

No comments