Steps to verify LDOM services are started.

Asset ID:	1-75-1020054.1
Update Date:	2011-03-14
Keywords:

Solution Type Troubleshooting Sure

Solution 1020054.1 : Steps to verify LDOM services are started.

Applies to:

Sun Blade T6320 Server Module - Version: Not Applicable and later   [Release: N/A and later ]
Sun Netra T2000 Server - Version: Not Applicable and later    [Release: N/A and later]
Sun Netra T5220 Server - Version: Not Applicable and later    [Release: N/A and later]
Sun Netra T5440 Server - Version: Not Applicable and later    [Release: N/A and later]
Sun Fire T1000 Server - Version: Not Applicable and later    [Release: N/A and later]
All Platforms

Purpose

This document refers to different services associated with LDOMs and to check whether it is started or not.

Symptoms

Unable to start ldom

unable to create ldom

unable to get the console of the ldom

Purpose/Scope:

This document provides steps to verify which are all the services needs to be running for a LDOM to start.

Last Review Date

January 3, 2011

Instructions for the Reader

A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.

Troubleshooting Details

Available Documents:

Please note that Primary domain is also referred as Control domain. Please check the "LDom Administration Guide" and the LDoms release notes at http://download.oracle.com/docs/cd/E19608-01/index.html

Steps to Follow

Below are two basic services needs to be running for the ldom to start/work properly.
Below are two basic services needs to be running for the ldom to start/work properly

1. svc:/ldoms/ldmd:default
2. svc:/ldoms/vntsd:default

From the above services we can see the ldmd is ldom service and vntsd is the virtual console service.

The state of the service should be online, rather than disabled /maintenance

If the State of the service is disabled we can try restarting it using /usr/sbin/svcadm (1M) command.

If the state of the service is in maintenance check the

/var/svc/log/ldoms-ldmd:default.log for the ldm logs
/var/svc/log/ldoms-vntsd:default.log for the vntsd logs

Also check in the /var/adm/messages file.

Use the ps (1M) command to check the process list whether the ldmd and vntsd is there in the process list or not

The below is the default configuration of the ldmd service and the vntsd service

svc:> select ldoms/ldmd
svc:/ldoms/ldmd> listprop
ldmd                                    application
ldmd/debug                              integer 0
ldmd/hops                               integer 0
ldmd/nocfg                              boolean false
ldmd/xmpp                               boolean false
fmd_config                              application
fmd_config/fmd_to_ldmd_init_timeout     integer 20
fmd_config/fmd_to_ldmd_running_timeout integer 10
filesystem                              dependency
filesystem/entities                     fmri     svc:/system/filesystem/local
filesystem/grouping                     astring require_all
filesystem/restart_on                   astring none
filesystem/type                         astring service
general                                 framework
general/action_authorization            astring solaris.smf.manage.ldoms
general/entity_stability                astring Unstable
general/single_instance                 boolean true
start                                   method
start/exec                              astring /opt/SUNWldm/bin/ldmd_start
start/timeout_seconds                   count    120
start/type                              astring method
stop                                    method
stop/exec                               astring :kill
stop/timeout_seconds                    count    60
stop/type                               astring method
tm_common_name                          template
tm_common_name/C                        ustring "Logical Domain Manager"

svc:> select ldoms/vntsd
svc:/ldoms/vntsd> listprop
vntsd                     application
vntsd/listen_addr         astring localhost
vntsd/timeout_minutes     integer 0
vntsd/vcc_device          astring virtual-console-concentrator@0
network                   dependency
network/entities          fmri     svc:/milestone/network
network/grouping          astring optional_all
network/restart_on        astring error
network/type              astring service
syslog                    dependency
syslog/entities           fmri     svc:/system/system-log
syslog/grouping           astring optional_all
syslog/restart_on         astring none
syslog/type               astring service
general                   framework
general/entity_stability astring Unstable
start                     method
start/exec                astring /lib/svc/method/svc-vntsd
start/timeout_seco

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

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:

Solairs[TM] OS Domain Feedback Alias : [email protected]

Normalized, ldom, ldm, vntsd

Attachments

This solution has no attachment