Steps to verify if the LDOM console is not working

Asset ID:	1-75-1020077.1
Update Date:	2011-05-11
Keywords:

Solution Type Troubleshooting Sure

Solution 1020077.1 : Steps to verify if the LDOM console is not working

Applies to:

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]
Sun Fire T2000 Server - Version: Not Applicable and later    [Release: N/A and later]
All Platforms

Purpose

This document refers to verify whether the ldom console is working properly or not

Symptoms:

Unable to start ldom
Unable to create ldom
Unable to get the console of the ldom

Purpose/Scope:
This document refers to the basic services and packages need to start the LDOM console properly.

Last Review Date

January 4, 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 LDOM release notes in http://download.oracle.com/docs/cd/E19608-01/index.html .

Steps to Follow
Below is the Steps To Verify The Virtual Console Concentrator Is Running Or Not.
In a Logical Domains environment, console I/O from all domains, except the primary domain, is redirected to a service domain running the virtual console concentrator (vcc) and virtual network terminal server (vntsd) services, instead of the systems controller.
The virtual console concentrator service functions as a concentrator for all domains, console traffic, and interfaces with the virtual network terminal server daemon and exports access to each console through a UNIX socket.

Creating the virtual console concentrator or VCC service is essential to providing console access to any logical domains created in the future. Only the primary domain can be reached directly via the hardware console; all other logical domains must be reached through the VCC service. When you create the VCC service, a range of TCP ports must be specified. Each of these ports can be bound to one LDom and can be accessed through the telnet command

# ldm add-vcc port-range=5000-5100 primary-vcc0 primary

It is important to note that instances of services or devices can be freely named. In the example here, our instance of the VCC service is called “primary-vcc0.”

The naming conventions used throughout this article take the form of -.

# ldm list-bindings
Name: primary
...
Vcpu: 4
...
Mau: 1
mau cpuset (0, 1, 2, 3)
Memory: 4G
...
Vds: primary-vds0
Vcc: primary-vcc0
port-range=5000-5100

Based on the above port numbers the Guest LDOM will be allocated a VCC port id.

# ldm start ldom1
# ldm list
Name State Flags Cons VCPU Memory Util Uptime
primary active -t-cv SP 4 4G 0.6% 4h 8m
ldom1 active -t—- 5000 4 4G 0.2% 2m

Now you can connect to the virtual console of your guest domain by using
telnet and the console number specified under the Cons column from above:
# telnet localhost 5000
Trying 127.0.0.1...
Connected to localhost.
Escape character is ‘^]’.
Connecting to console “ldom1” in group “ldom1” ....
Press ~? for control options ..

As in the above example the next Guest LDOM will be using the next available free port. Normally the ports are assigned in ascending order.

The service available for the Virtual Network Console is svc:/ldoms/vntsd

online 7:29:58 svc:/ldoms/vntsd:default

root 692 1 0 Feb 10 ? 0:00 /usr/lib/ldoms/vntsd -i virtual-console-concentrator@0 -p localhost -t 0

The vntsd is there in the /usr/lib/ldom directory and it comes as a part of the entire distribution + oem ( SUNWcxall)

Troubleshooting :

Check for the possible errors in the /var/svc/log/ldoms-vntsd:default.log.

Try to stop and start the vntsd service.

Make sure the firmware version is up-to-date as per the latest rev

Please read the Readme.info file in the firmware patch of the respective hardware for upgrade procedure

Make sure to backup the ldom configuration before doing the firmware upgrade as per the
DOC

If the above steps fail please contact Support with the following information:

- The latest explorer output using the latest version of explorer script.
- The if there is any specific error, please provide session log illustrating
the error concerned.

Please follow 1019720.1to collect the LDOM related logs.

Product
Logical Domain Manager
Sun Fire T2000 Server
Sun Fire T1000 Server
Sun Netra T2000 Server
Sun Netra T5220 Server
Sun Netra T5440 Server
Netra T5220 AC

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:

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

Normalized, ldom, ldm, vntsd

Attachments

This solution has no attachment