Asset ID:	1-75-1020019.1
Update Date:	2011-04-25
Keywords:

---

Solution Type  Troubleshooting Sure

Solution  1020019.1 :   Troubleshooting LDOM jumpstart issues  


PreviouslyPublishedAs
250929

Description
This document would explain the details of required steps to troubleshoot LDOM jumpstart issues
Symptoms:

One or more of the following are observed or described when LDOM jumpstart issues are seen:

    *  Confirm network settings are correct
    *  Verify Ethernet  address for LDOM
    *  Disk Configuration
    *  Right cpu architecture is specified
    *  Appropriate LDOM resources are assigned to domains

Purpose/Scope:

This document describe in the context during guest domain creation. Adding of resources to an active domain can also fail due to lack of additional resources to be assigned to a domain. The corrective actions are the same as described here.

Related Documents:

For more information on creation of LDoms guest domains, please refer to following references:

- Beginners Guide to LDOMs (820-0832) availabe at http://www.sun.com/blueprints.
- Logical Domains (LDoms) X.X.X Administration Guides, which are available on http://www.oracle.com/technetwork/documentation/vm-sparc-194287.html .

Additional information specific to the software release is available in the LDOMs Release Notes.

Up to date information on LDoms is available at Oracle VM for SPARC Documentation


Steps to Follow
Please validate that each troubleshooting step below is true for your
environment. The steps will provide instructions or a link to a document, for
validating the step and taking corrective action as necessary. The steps are
ordered in the most appropriate sequence to isolate the issue and identify the
proper resolution. Please do not skip a step
Before attempting the following steps, please ensure the user account used has the appropriate RBAC profiles for LDOMs Management. The user either has to have to "LDoms Management" profile or just login as root. For more information on user authorization, please refer to the Security chapter of the LDoms Administration Guide.

Step 1. Network configuration issue.

See <Document: 1020018.1> Confirm network settings are correct.

Step 2. Ethernet mac address

See <Document: 1020017.1> Verify Ethernet  address for LDOM.

Step 3. Disk Configuration.

See <Document: 1020008.1> Steps to verify Disk configuration.

Step 4. Wrong Architecture
See <Document: 1019984.1> Steps to confirm the right cpu archictecture is specified when Jumpstarting Txxxx (sun4v) server

Step 5. Verify that VCPU/MAU resources are available for binding to the domain.

See <Document: 1019983.1> Steps to ensure proper binding of resources to LDOM domains.

At this point, if you have validated that each troubleshooting step above is true for your environment, and the issue still exists, further troubleshooting is required. Provide an Explorer output and open a Service Request. See <Document: 1020212.1> Data Collection for troubleshooting LDom issues.   


Product
Logical Domain Manager 1.0.1
Sun Fire T2000 Server
Sun Fire T1000 Server
Sun Netra T2000 Server
Sun Netra T5220 Server
Sun Netra T5440 Server
Netra T5220 AC
Sun SPARC Enterprise T5220 Server
Sun SPARC Enterprise T5240 Server
Sun Blade T6300 Server Module
Sun Blade T6320 Server Module
Sun SPARC Enterprise T5120 Server
Sun SPARC Enterprise T5140 Server
Sun Blade T6340 Server Module
Sun SPARC Enterprise T2000 Server
Sun SPARC Enterprise T5440 Server
Sun SPARC Enterprise T1000 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:

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

Normalized, ldom, ldm, guest , domain, network, issues, vnet, vsw, vswitch, virtual network interface, hyrbrid I/O, DHCP, audited

Attachments

This solution has no attachment