Sponsored Content
Operating Systems Solaris Help required with Solaris LDoms Post 303002910 by garydeena on Tuesday 5th of September 2017 01:15:01 AM
Old 09-05-2017
Hi. I lost the mother board on my Sparc server running Solaris 10 and lost the SP.
the below restored everything. Very easy as long as you have backups.

ldm list-spconfig
factory-default - should be current. ( next startup )

Will not restore primary if spconfig and ldom-db.xml differ

mv /var/opt/ldom-db.xml /var/opt/ldom-db.xml-orig

reboot

ldm init-system -r -i primary-ldomname.xml

ldm add-domain -i ldomname.xml

bind ldomname
ldm start-domain ldomname

That's it. Then ldm add-spconfig latest
 

8 More Discussions You Might Find Interesting

1. Solaris

Info required zones in solaris

Can anyone explain me what is the use of zones in solaris. Also how to find whether it is a local or global zone. (1 Reply)
Discussion started by: rogerben
1 Replies

2. Solaris

Ldoms on T5220 with existing solaris 10 OS

Hi I;ve a T5220 box running solaris 10 update 6 with 6 zones on it and zfs SAN file systems is it possible to configure Control domain on this box without removing the exisinting OS and zones ? (1 Reply)
Discussion started by: fugitive
1 Replies

3. Solaris

Immediate Help Required for Patch Installation on Solaris 10

Hi All, I am new to Solaris. I have to install some latest patches on my SPARC Machine running Solaris 10. I have installed the required patches. Please guide me through the rest of the process. Please include even minute details so that I don't face any problems while doing this activity. ... (0 Replies)
Discussion started by: kamaldeep1986
0 Replies

4. UNIX for Advanced & Expert Users

Immediate Help Required for Patch Installation on Solaris

Hi All, I am new to Solaris. I have to install some latest patches on my SPARC Machine running Solaris 10. I have installed the required patches. Please guide me through the rest of the process. Please include even minute details so that I don't face any problems while doing this activity.... (3 Replies)
Discussion started by: kamaldeep1986
3 Replies

5. Solaris

Migrating Solaris 8, 9 to Guest Domains (LDOMs)

Hi Everyone, one question is it possible to migrate a physical standalone Solaris 8 or 9 OS to Guest Domain (LDOMs). If yes, can someone please provide steps to migrate these OS to LDOMs. Thanks, Kartheek. (1 Reply)
Discussion started by: bobby320
1 Replies

6. Solaris

Booting Solaris LDOMS Control Domains

We are having a discussion on what order LDOMS and control domains should be booted. I think it should be LDOMS first then Control. Can anyone tell me why I am wrong or why I am right. Thanks, :confused: (6 Replies)
Discussion started by: aeroforce
6 Replies

7. Solaris

Install LDoms in T2000 running Solaris 11.2

Hi, im trying a lab with Solaris 11.2 in SunFire T2000 I read about know problem with ldomsmanager version. Solaris 11 comes with ldomsmanager 2.2 and T2000 needs 1.2. I need to install ldomsmanager version 1.2 but i donīt know why... i canīt find it at oracle site. I found oracle VM for SPARC... (0 Replies)
Discussion started by: MuziKizuM
0 Replies

8. Solaris

Oracle DBA licensing on Solaris 11 LDOMS

My understanding is that Oracle DB licensing is based on number of cores etc. If you use virtual machines (e.g.ldoms) you need to partition it properly otherwise, in theory you have to pay based on the host machine. Can anyone confirm I'm right here? And explain it in bit more detail (i.e.... (8 Replies)
Discussion started by: psychocandy
8 Replies
vntsd(1M)						  System Administration Commands						 vntsd(1M)

NAME
vntsd - virtual network terminal server daemon for Logical Domains SYNOPSIS
/usr/lib/ldoms/vntsd DESCRIPTION
The vntsd daemon is a server that supports connections to the Logical Domains (LDoms) console by using telnet(1). When a telnet session starts, vntsd sends telnet options to the client indicating a willingness to remotely echo characters and to suppress go ahead. Consoles are organized into groups by the LDoms Manager. Each console group is assigned a unique group name and TCP port number. vntsd uses the group's port number to export access to the consoles within that group. To establish a connection with a console or console group, a user starts a telnet(1) session with the corresponding group's port number. Depending on the number of consoles within that group, vntsd does one of two things: o If there is only one console in the group, vntsd connects a session to that LDoms console. o If there are multiple consoles in the group, vntsd prompts the user to select the console to which they would like to connect, as shown in "Multiple-Console Options," below. For each console, vntsd provides write access only to the first user connecting to the console. Subsequent users connecting to the console are allowed only to read from the console and wait for write access. When the first user disconnects, write privileges are transferred to the next user waiting in the queue. If a user who does not have write privileges attempts to write to a console, the vntsd displays the following message: You do not have write access A user who has no write access can acquire write access forcibly by using the ~w special console command, described in "Special Console Commands," below. vntsd can be invoked only with superuser privileges or by someone in the Primary Administrator role. OPTIONS
The options for vntsd are divided into multiple-console options and console commands. Multiple-Console Options The options listed below are supported when there are multiple LDoms consoles in a group. The syntax for the use of these options is: <hostname>-vnts-<group-name>: <option> For example: myhost-vnts-salesgroup: h The h option invokes help, as described below. h Display the following help text: h -- this help l -- list of consoles q -- quit c{id}, n{name} -- connect to console of domain {id} or domain name l List all consoles in the group. For example: DOMAIN ID DOMAIN NAME DOMAIN STATE 0 ldg1 online 1 ldg2 connected ... ... ... The two domain states and their meanings are: online No one is connected to the console. connected At least one user is already connected to the console. q Disconnect from vntsd. c{id}, n{name} Connect to specified console. Upon connection, the following message is displayed: Connecting to console <domain-name> in group <group-name> Press ~? for control options .... Special Console Commands A tilde (~) appearing as the first character of a line is an escape signal that directs vntsd to perform a special console command. The tilde-tilde (~~) sequence outputs a tilde. In conjunction with the initial tilde, vntsd accepts the following special console commands: ~. Disconnect from the console or console group. ~w Force write access to the console. ~p Disconnect from this console, and connect to the console that precedes this console in the list of consoles. ~n Disconnect from this console, and connect to the console that follows this console in the list of consoles. ~# Send break. ~? Display vntsd help, as follows: ~# - Send break ~. - Exit from this console ~w - Force write access ~n - Console next ~p - Console previous ~? - Help FILES
/usr/lib/ldoms/vntsd Binary executable vntsd file. /usr/lib/ldoms/vntsd.xml Service management facility (smf(5)) manifest file for vntsd. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWldoms | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
telnet(1), svccfg(1M), usermod(1M), auth_attr(4), attributes(5), smf(5) NOTES
The vntsd is managed by the service management facility, smf(5), under the service identifier: svc:/ldoms/vntsd You can change the following properties using the svccfg(1M) command: vntsd/vcc_device Set an instance of the virtual console concentrator (vcc) driver to which vntsd is connected. vntsd/listen_addr Set the IP address to which vntsd listens, using the following syntax: vntsd/listen_addr:"xxx.xxx.xxx.xxx" ...where xxx.xxx.xxx.xxx is a valid IP address. The default value of this property is to listen on IP address 127.0.0.1. Users can con- nect to a guest console over a network if the value is set to the IP address of the control domain. Note - Enabling network access to a console has security implications. Any user can connect to a console and for this reason it is disabled by default. vntsd/timeout_minutes Set timeout in minutes. vntsd will timeout (close) telnet connection if there is no activity (input or output) on the console. The default value is 0, which disables timeout. vntsd/authorization Enable the authorization checking of users and roles for the domain console or consoles that are being accessed. The default value of this property is false to maintain backward compatibility. To enable authorization checking, use the svccfg(1M) command to set the property value to true. While this option is enabled, vntsd listens and accepts connections on localhost. If the listen_addr property specifies an alternate IP address when this option is enabled, vntsd ignores the alternate IP address and continues to listen on local- host. Connections that are initiated from other hosts will also fail. Authorizations are available to access all consoles or console groups, or to access specific consoles or console groups. When the vntsd service is enabled, the following authorization is added to the authorization description database, auth_attr(4): solaris.vntsd.consoles:::Access All LDoms Guest Consoles:: Add any fine-grained authorizations based on the name of the console group. For example, if the name of the console group to be autho- rized is ldg1, add the following entry to the auth_attr(4) file: solaris.vntsd.console-ldg1:::Access Specific LDoms Guest Console:: By default, the authorization to access all consoles is assigned to the root user or role. The Primary Administrator (superuser) can use the usermod(1M) command to assign the required authorization or authorizations to other users or roles. The following example gives user user1 the authorization to access all domain consoles: # usermod -A "solaris.vntsd.consoles" user1 The following example gives user user1 the authorization to access the console group named ldg1: # usermod -A "solaris.vntsd.console-ldg1" user1 SunOS 5.11 13 Feb 2009 vntsd(1M)
All times are GMT -4. The time now is 09:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy