Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1019984.1
Update Date:2010-08-09
Keywords:

Solution Type  Technical Instruction Sure

Solution  1019984.1 :   Steps to confirm the right cpu archictecture is specified when Jumpstarting Txxxx (sun4v) server.  


Related Items
  • Sun Fire T2000 Server
  •  
  • Sun Fire T1000 Server
  •  
  • Sun Netra T2000 Server
  •  
Related Categories
  • GCS>Sun Microsystems>Servers>NEBS-Certified Servers
  •  
  • GCS>Sun Microsystems>Servers>CMT Servers
  •  

PreviouslyPublishedAs
250249


Description
The machine hardware class for the UltraSPARC(R) Txxxx series is called sun4v. When performing a Jumpstart[TM] install, the right machine hardware class has to be specified.
Symptoms:

Jumpstarting with the incorrect machine architecture specified can lead to the following observations:

- Jumpstart panic
- Panic during Jumpstart
- Panic with illegal instruction fault
- trap 10
- Jumpstart failed


Purpose/Scope:

This document provide steps to ensure the correct machine architecture is specified when performing a network Jumpstart install of a Tx000 machine.


Related Documents:

The general Jumpstart troubleshooing, please refer to <Document: 1018557.1> Troubleshooting a failed Jumpstart.

Comprehensive guide in setting up and using Jumpstart is described in the Solaris[TM] 10 Installation Guide: Custom Jumpstart and Advanced Installations manual available at http://docs.sun.com .


Steps to Follow
The following provides steps to ensure that sun4v architecture is specified when Jumpstarting sun4v clients.

When performing a network Jumpstart for a sun4v machine, regardless of whether it is the primary domain or guest domain, the machine architecture of sun4v has to be specified.

The add_install_client(1M) man page specified the following synopsis where platform_group argument is to be replaced with sun4v when setting up a sun4v Jumpstart client.

media-mnt-pt/Solaris_XX/Tools/add_install_client
[-i IP_address]
[-e Ethernet_address] [-s server_name : path]
[-c server_name : path]
[-n [server ] : name_service [( netmask]]
[-p server_name : path]
[-t install_boot_image_path] host_name platform_group
media-mnt-pt/Solaris_XX/Tools/add_install_client -d
[-s server_name:path]
[-c server_name:path] [-p server_name:path]
[-t install_boot_image_path] [-f boot_file_name]
platform_name platform_group
media-mnt-pt/Solaris_XX/Tools/add_install_client -d
[-s server_name:path]
[-c server_name:path] [-p server_name:path]
[-t install_boot_image_path] [-f boot_file_name] -e Ethernet_address
[-b property=value] platform_group

For example.:

On the Jumpstart server, issue the following add_install_client(1M) command for a client named t2000-node1:

     # ./add_install_client t2000-node1 sun4v


Product
Logical Domain Manager 1.0.1
Sun Fire T2000 Server
Sun Fire T1000 Server
Sun Netra T2000 Server


Internal Comments
This document contains normalized content and is managed by the the Domain Lead(s) of the respective domains. To notify content owners of a knowledge gap contained in this document, and/or prior to updating this document, please contact the domain engineers that are managing this document via the "Document Feedback" alias(es) listed below:

Normalization Lead: global-systems-tsc-domain-engineers@Sun.COM

Normalized, sun4v, jumpstart, ldom

Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback