ITEM: BW3767L

How to clone a 43p to a C20 using sysback



Question:

 ENV:
  AIX 4.1.4
  RISC 43p and C20
  sysback 3.3.3.x

 PROBLEM:
  How to clone a 43p to a C20 using sysback

*ACTION TAKEN:

CLONING A 43p TO A C20
-------------------------

Install these filesets on your 43p, reboot it and build 
the full-system backup tape.  Either use smitty or from 
the command type line:   
                  sysback -f /dev/rmt\# -T rs6k -k up

========
KERNELS
========
bos.rte.up
  UniProcessor Support

===================
Base Device Drivers
===================

devices.base 
      Common and Uniprocessor Base System Device Software 

devices.mca.dee6 
     Standard I/O (dee6) Adapter Software 

devices.mca.df5f 
      Standard I/O (df5f) Adapter Software 

devices.mca.fed9 
      Standard I/O (fed9) Adapter Software 

devices.mca.f6fe 
      Standard I/O (f6fe) Adapter Software 

devices.mca.f6f8 
      MCA Keyboard & Mouse Adapter (f6f8) Software 

devices.mca.8d77 
      8-bit SCSI I/O Controller Software 

devices.mca.8efc 
      16-bit SCSI I/O Controller Software 

devices.mca.8fba 
      Standard NCR53C720 SCSI Software 

devices.mca.8ff4 
      Standard NCR53C700 SCSI Software 

devices.scsi.disk 
      SCSI CD-ROM, Disk, Read/Write Optical Device Software 

devices.scsi.tape 
      SCSI Tape Device Software 

devices.sio.fda 
      Diskette Adapter Software 

devices.sio.ktma 
      Keyboard Tablet & Mouse Device and Adapter Software 

devices.sys.mca 
      Micro Channel Bus Software 

*********************************************
PICK WHICH GRAPHIC ADAPTER YOUR C20 IS USING
AND INSTALL THAT
*********************************************

=======================================
Graphics and Audio/Video Device Drivers
=======================================

devices.buc.00004007 
      GXT155L Graphics Adapter Software 

devices.buc.00004006 
      GXT150L Graphics Adapter Software 

devices.buc.00004005 
      GXT150 Graphics Adapter Software 

devices.buc.00004002 
      GXT500 Graphics Adapter Software 

devices.buc.00004001 
      GXT100 Graphics Adapter Software 

devices.graphics 
      Graphics Adapter Common Software plus VOO and Stereo Software 

devices.mca.dfe5 
      AIX Ultimedia Services RISC Audio Device 

devices.mca.edd5 
      Graphics Input Adapter Software 

devices.mca.efc6 
      BBLMCA Graphics Adapter Software 

devices.mca.e555 
      Digital Trunk Adapter (e555) Software 

devices.mca.e556 
      Digital Trunk Dual Adapter (e556) Software 

devices.mca.8ee3 
      Gt3/Gt4 Graphics Adapter Software 

devices.mca.8ee4 
      Color Graphics Display Adapter Software 

devices.mca.8ee5 
      Grayscale Graphics Display Adapter Software 

devices.mca.8fbc 
      GXT1000 Graphics Adapter Software 

devices.mca.8ffd 
      High-Speed 3D Graphics Adapter Software 

devices.mca.8f9a 
      GXT150M Graphics Adapter Software 

devices.mca.8f96 
      AIX Ultimedia Services Video I/O Adapter 

devices.mca.8787 
      5085/86/88 Attachment Adapter Software 

devices.serial.gio 
      Serial Graphics Input Adapter Software 

devices.serial.sb1 
      6094-030 Spaceball 3-D Input Device Software 

devices.serial.tablet1 
      Serial Tablet Input Device Software 

devices.sys.sga 
      Gt1 Graphics Adapter Software 

devices.sys.sgabus 
      Special Graphics Slot Software 

devices.sys.wga 
      Gt1x Graphics Adapter Software 

LED 000 -- bootinfo -B command failed
           This command will usually fail due to missing device drivers
           to support the client's hardware from the boot image.
           When booting from a tape drive, the problem usually is caused
           from missing scsi support.  When booting over the network from
           a network boot image, it is missing device support for either
           the token-ring, ethernet or FDDI adapter.  You will need to
           install the approriate device support on the server system 
           reboot the server and remake the tape or network boot image.

LED 609 -- Failed to tftp the file /tftp/\.sbinfo file
           from the server system during a network boot.

         1.  The \.sbinfo does not have read permissions for other
         2.  The file does not exist
         3.  On a pci based system, you cannot use the leading zero's 
             for any of the ipaddress in the sms menu.  Even though the 
             first tftp works the second one run will fail.  

Try readding the client again

smitty sb_cfgnetboot
   rebuild the boot images

 smitty sb_cfgbootclient
   readd your client, make sure all the values are correct.
   the values are correct.


LED 610 --  Hanging on the nfs mount of /usr from the server during a network
            boot.

            The /etc/exports file does not have permissions for the client
            to mount /usr

            To verify this type  exportfs

            Example of output
            /usr -ro,root=gonzo.aix.dfw.ibm.com

           smitty sb_cfgbootclient
   readd your client, make sure all the values are correct.
              Make sure the servers IPaddress is correct for the type of
              network interface being use.  Make sure you have the correct
              Gateway and subnet mask for the client as well.


LED 611 --  Failed to nfs mount /usr during a network boot from the server.

            It can mean that /usr was not exported to the client
            correctly.  Run a exportfs command on the server to verify
            this is correct.   See LED 610

            Known bug at AIX 4.1.4 that will effect NIM as well as sysback.
            Fixed with APAR: IX54851 or  Filesets:
            bos.adt.prof 4.1.4.5
            bos.rte.libc 4.1.4.5
            bos.net.nfs.client 4.1.4.4
            bos.sysmgt.quota 4.1.3.1
            bos.net.tcp.client 4.1.4.4
            Install the software
            Once the software has installed without errors reboot the server.
            You will need to remake the network boot image on the server
            from the sysback menu again.  Reboot your client and try the process
            again.

LED 511 then BLANK -- Failure on the cfgcon command
                      This will occur, because of missing device support
                      for either the graphic adapter or standard I/O slot for
                      ascii monitors.  You will need to install the 
                      approriate device support on the server system
                      reboot the server and remake the tape or network boot 
                      image.

LED 622 then BLANK  -- Failure on the cfgcon command
                       See LED 511

LED 0xb05 (backwards C05) -- Failure on the cfgcon command
                             See LED 511

LED 666 --  Failed in phase 2 of cfgmgr -p2 -v
            This is caused during a network boot from the server where
            /usr has been exported without 'root' permissions.

            How to correct led 666 hang
            ----------------------------
            cd /etc
            vi exports

            CHANGE:
            -------
            /usr                 -ro,root=node1,node2:access=node3,node4

            TO:
            ---
            /usr                 -ro,root=node1,node2,node3,node4

            exportfs -u
            exportfs -a
            exportfs  (verify the change took place)


*ACTION PLAN:
  Closing with customer approval



Support Line: How to clone a 43p to a C20 using sysback ITEM: BW3767L
Dated: March 1997 Category: N/A
This HTML file was generated 99/06/24~13:30:19
Comments or suggestions? Contact us