Network installation of a JS20 blade

Using this scenario, you can install AIX® for the first time or overwrite an existing version of the operating system onto a JS20 blade.

The information in this how-to scenario was tested using specific versions of AIX. The results you obtain might vary significantly depending on your version and level of AIX.

In this scenario, you will do the following:
  • Gather the required TCP/IP information for your JS20 blade.
  • Prepare your Network Installation Management (NIM) environment.
  • Configure a NIM master.
  • Create NIM installation resources.
  • Define your JS20 blade as a NIM client.
  • Prepare your JS20 blade for a network installation.
  • Boot the JS20 blade off the network using a directed bootp or broadcast bootp method.

To perform a network install, you will need to configure a NIM master if you do not already have one configured. For instructions about how to create a NIM master, see Configuring NIM and other basic operations

Note: This procedure requires shutting down and reinstalling the base operating system. When you reinstall any operating system, schedule your downtime when it least impacts your workload to protect yourself from a possible loss of data or functionality. Before you perform a new and complete overwrite installation, ensure you have reliable backups of your data and any customized applications or volume groups. For instructions about how to create a system backup, see Creating system backups.

Performing a broadcast bootp network installation

To perform a broadcast bootp, ensure that the NIM server is on the same subnet as the JS20 blade that you are installing. During a broadcast bootp, the JS20 blade sends a broadcast bootp packet to its subnet. The NIM server receives and responds to this packet. The JS20 blade NIM client definition on your NIM master must include the MAC address of the JS20 blade's network adapter used during the installation, or the NIM server will not respond to a broadcast bootp. If your NIM master is on a different subnet, and you want to perform a broadcast bootp, then you must set up another system on the client's subnet to forward broadcast bootp packets.

To set up a system to forward broadcast bootp packets, complete the following steps:
  1. Add the IP address of your NIM server to the /etc/dhcprd.cnf file on the system that forwards the packets. For example, if your NIM server's IP address is 192.24.24.1, add server 192.24.24.1 to /etc/dhcprd.cnf
  2. Run startsrc -s dhcprd.
This system will now forward broadcast bootp packets to your NIM server that is on a different subnet. You must also install the latest firmware version onto your client for the client to correctly handle the bootp response from the system that is forwarding broadcast bootp packets.
Step 1: Prepare your NIM server

Performing a broadcast bootp is similar to a directed bootp. The steps are the same, except you that must obtain the MAC address of the JS20 blade's network adapter that you will use to network install.

  1. Obtain the MAC address from the MM Web interface by completing the following steps:
    1. Select Monitor > Hardware VPD .
    2. Scroll down to BladeCenter Server MAC Addresses.
    3. Find the JS20 blade that you plan to install and the MAC address that corresponds to the adapter you will use to perform the installation. Write this MAC address down.
  2. Specify the MAC Address when you define the JS20 blade as a NIM client. If you are using the smitty nim_mkmac command, specify the MAC address on the Network Adapter Hardware Address SMIT screen. Do not include the colons (":") when you are specifying the MAC address. If the client is already defined, you can change the MAC address with the smitty nim_chmac command.
  3. Set up your NIM master to install the JS20 blade, by completing the following steps:
    1. Run the smitty nim_bosinst command.
    2. Select the JS20 blade that is defined as your target .
    3. Select the type of install that you want to perform and select the installation resources that you want to use to install the JS20 blade.
    You can also prepare the JS20 blade to install using the bos_inst NIM operation on the command line. For more information on using the bos_inst operation, see Using the NIM bos_inst operation.
  4. Power off the JS20 blade. If you do not want the JS20 blade to reboot automatically, set Initiate reboot and installation now? to no in the SMIT screen and press Enter.
Step 2: Initiate the installation from the management module

The bootp protocol allows you to install through a directed bootp or broadcast bootp request.

  1. Ensure that the JS20 blade's boot list is set to install from the network in the MM Web interface by selecting Blade Tasks > Configuration and scroll down Boot Sequence.
  2. Click the JS20 blade that you are installing and ensure the first device listed is Network - BOOTP. When the JS20 blade boots, it will install from the first network adapter that receives a bootp response.
    Note: You should not have a serial over LAN connection open to the JS20 blade that you are attempting to install when you power on the JS20 blade.
  3. Click save.
  4. Power on the JS20 blade from the MM Web interface by selecting Blade Tasks > Power/Restart.
  5. Select the JS20 blade that you are installing and click Power On Blade.
If you do not have an serial over LAN connection to the JS20 blade, you can view the status of the installation by running the following command from your NIM master:
lsnim -l js20_nim_name
For example, if the JS20 blade was defined as JS20blade1, run the following command:
lsnim -l JS20blade1
Note: If you run the AIX bootlist command to set the IP parameters for a network adapter and reboot the system, the IP parameters will be stored in NVRAM. When you reboot the JS20 blade from the MM with the boot sequence set to Network-BOOTP, the JS20 blade attempts to use the IP parameters stored in NVRAM instead of performing a broadcast bootp. To perform a broadcast bootp, run the bootlist command specifying 0.0.0.0 for each IP parameter and reboot from AIX using the shutdown -Fr command. For example, to perform a broadcast bootp over ent1, run the following commands.
# bootlist -m normal ent1 client=0.0.0.0 bserver=0.0.0.0 gateway=0.0.0.0 hdisk0
# shutdown -Fr 
If you are unable to log into the AIX system, then follow the instructions for performing a directed bootp via the Open Firmware prompt, but specify "0.0.0.0" for each IP address. Once the JS20 blade installs successfully, the boot IP parameters are reset to "0.0.0.0".

Performing a directed bootp network installation

A directed bootp can be used to install a JS20 blade from a NIM server and does not require the NIM server to be on the same subnet as the JS20 blade.

This option does not require that you have the MAC address of the network adapter on the JS20 blade. To perform a directed bootp, you need a serial over LAN connection to the blade so that you can specify the IP parameters to Open Firmware. Currently you must have 2 network adapters to perform a NIM installation if you are using serial over LAN. You cannot install AIX over the same adapter that is using serial over LAN.

Step 1: Prepare your NIM server
  1. Create a SPOT, lpp_source, and any other resources that you will need at the level of AIX that you want to install on your NIM server. Your NIM server is usually the NIM master, but you can also set up a NIM client as a NIM server. For instructions on how to create NIM resources, see Configuring the NIM master and creating basic installation resources.
  2. Ensure that you have the information in the following worksheet for your JS20 blade before proceeding with the installation:
    Table 1. Network Configuration Information Worksheet
    Network Attribute Value
    Network Interface (For example: ent1)
    Host Name  
    IP Address _______.________.________.________
    Network Mask _______.________.________.________
    Name server _______.________.________.________
    Domain Name  
    Gateway _______.________.________.________
  3. Define the JS20 blade as a NIM client on your NIM master by running the smitty nim_mkmac command on the NIM master. This command creates a client definition for your JS20 blade. You can also define the JS20 blade using the define NIM operation on the command line.
  4. If you want to set the JS20 blade's name server and domain name after the installation, use a resolv_conf resource. For more information on creating a resolv_conf resource, see Using the nim_script resource.
  5. Set up your NIM master to install the JS20 blade, by running the smitty nim_bosinst command. Select the JS20 blade that you defined earlier as your target. Then select the type of install that you want to perform and select the installation resources that you want to use to install the JS20 blade. You can also prepare the JS20 blade to install using the bos_inst NIM operation on the command line.
    Note:
    1. If the JS20 blade is powered off or has never been installed, set Initiate reboot and installation now? to no and press enter in the SMIT interface.
    2. If the JS20 blade is powered on and running AIX, set Initiate reboot and installation now? to yes in the SMIT interface. If you choose this option, a directed bootp is initiated by default and you can skip step 2. Before you run this command, ensure that the JS20 blade is a registered NIM client. To do this, run smitty niminit on the JS20 blade. Then specify the hostname of your NIM master and the interface you want to use for the installation. You can also initialize the JS20 blade using the niminit command on the command line.
Step 2: Specify a directed bootp from the JS20 blade
  1. Open a Web interface to the MM by navigating to the IP address or hostname of the MM using a Web browser.
  2. Enable serial over LAN to the JS20 blade from the MM Web interface by selecting Blade Tasks > Serial Over LAN .
  3. Select the JS20 blade that you are installing and click Enable Serial Over LAN.
  4. Power on the JS20 blade from the MM Web interface by selecting Blade Tasks > Power/Restart.
  5. Select the JS20 blade that you are installing and click Power On Blade.
  6. Open a serial over LAN connection to the JS20 blade by telnetting into the MM and running the console command. For example, if the JS20 blade is in slot 3, you would run the following command:
    console -T blade[3]
    The serial over LAN connection shows a series of LED numbers.
  7. Press 8 on the keyboard when you see E1F1 to go to the Open Firmware prompt.
  8. Run boot net:bootp,server_ip,,client_ip,gateway_ip to boot from the network.
    • If you are using a net type boot, you would run a command similar to the following:
      boot net:bootp,192.168.2.10,,192.168.1.11,192.168.1.1
    • If you are using ent1, then you would run a command similar to the following:
      boot /pci@8000000f8000000/pci@0/ethernet@1,1:bootp,192.168.2.10,,192.168.1.11,192.168.1.1
      Note: You must specify the full device path name with this command. To determine the full path to your device, list the device tree by running the ls command at the Open Firmware prompt. This command displays output similar to the following:
      0 > ls  
      000000c87f18: /ibm,serial 
      000000c88840: /chosen 
      000000c88a98: /packages 
      
      ... 
      000000d31488: /vdevice 
      000000d327a8:   /vty@0 
      000000d32f88:   /IBM,sp@4000 
      000000d33f10:   /rtc@4001 
      000000d34a18: /pci@8000000f8000000 
      000000d384d0:   /pci@0 
      000000d4bbd0:     /ethernet@1 
      000000d5af50:     /ethernet@1,1 
      000000d3be00:   /pci@3 
      000000d6a350:     /usb@0 
      000000d845f8:       /hub@1 
      000000d854b8:     /usb@0,1 
      000000d9f760:       /hub@1 
      000000d3f798:   /pci@1f 
      000000d45ed8:   /ide@4,1 
      000000d47b10:     /disk@0
      The highlighted items are the path to the second ethernet adapter. You would pass this information to the boot command to initiate a network boot from the second ethernet adapter
  9. After you run the boot command, then network installation begins. Output similar to the following is displayed on the serial over LAN connection:
    BOOTP: chosen-network-type = ethernet,auto,none,auto 
    BOOTP: server   IP =        192.168.2.10 
    BOOTP: requested filename = 
    BOOTP: client   IP =        192.168.1.11 
    BOOTP: client   HW addr =   0 d 60 1e c cb 
    BOOTP: gateway  IP =        192.168.1.1 
    BOOTP: device    /pci@8000000f8000000/pci@0/ethernet@1,1 
    BOOTP: loc-code  U8842.P1Z.23A0984-P1-T7   
    
    BOOTP R = 1 
    FILE: /tftpboot/js20blade1.austin.ibm.com 
    Load Addr=0x0000000000004000, Max Size=0x0000000000bfc000 
    FINAL Packet Count = 21131 
    FINAL File Size = 10818623 bytes. 
    load-base=0x4000 
    real-base=0xc00000  
    
    Elapsed time since release of system processors: 2 mins 28 secs 
    ...