08-02-2013
My methodology would differ slightly depending on OS version
If Solaris 10:
build and patch the ABE for each Client LDOM. Then the Primary. Once all are complete, activate the client ABE's and shutdown the client LDOMs.
after that is complete, activate the Primary ABE and then reboot. If the Primary comes up OK on the alternate BE, Start and boot each Client one at a time to ensure they are coming up ok. Then proceed with any zones you have configed.
This is assuming of course that you don't have anything set to auto boot.
If Solaris 11:
Patch at will, just ensure you shutdown your guests prior to rebooting the Primary.
4 More Discussions You Might Find Interesting
1. Solaris
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
2. Solaris
I have a T5220 with following configuration of hypervisor and OS
# ldm -V
Logical Domains Manager (v 2.1)
Hypervisor control protocol v 1.7
Using Hypervisor MD v 1.3
System PROM:
Hypervisor v. 1.10.4 @(#)Hypervisor 1.10.4 2011/11/17 15:00\015
... (1 Reply)
Discussion started by: fugitive
1 Replies
3. Solaris
Hi Folks,
I am used to writing scripts to get info by running commands at local zones level from their respective global zone by using zlogin <localzone> "command>" while remaining at the global zone level.
Can the same be done with Guest LDoms while remaining at the control LDOM level?
... (4 Replies)
Discussion started by: momin
4 Replies
4. Solaris
System: SPARC S7-2 Server; 2x8-core CPUs; 128Gb RAM; 2x600Gb HDD.
I am trying to figure out how to run these is multiple Virtual Machines (LDoms). Unfortunately I cannot find a tutorial so am using the Oracle VM Server for SPARC 3.4 Administration Guide; which is frustrating because it assumes a... (4 Replies)
Discussion started by: apmcd47
4 Replies
LEARN ABOUT CENTOS
net::ldap::control::syncstate
Net::LDAP::Control::SyncState(3) User Contributed Perl Documentation Net::LDAP::Control::SyncState(3)
NAME
Net::LDAP::Control::SyncState - LDAPv3 Sync State control object
SYNOPSIS
See Net::LDAP::Control::SyncRequest
DESCRIPTION
"Net::LDAP::Control::SyncState" provides an interface for the creation and manipulation of objects that represent the "Sync State Control"
as described by RFC 4533.
CONSTRUCTOR ARGUMENTS
In addition to the constructor arguments described in Net::LDAP::Control the following are provided.
state
entryUIID
cookie
METHODS
As with Net::LDAP::Control each constructor argument described above is also available as a method on the object which will return the
current value for the attribute if called without an argument, and set a new value for the attribute if called with an argument.
SEE ALSO
Net::LDAP, Net::LDAP::Control, Net::LDAP::Control::SyncRequest, Net::LDAP::Control::SyncDone, http://www.ietf.org/rfc/rfc4533.txt
AUTHOR
Mathieu Parent <math.parent@gmail.com>
Please report any bugs, or post any suggestions, to the perl-ldap mailing list <perl-ldap@perl.org>
COPYRIGHT
Copyright (c) 2008 Mathieu Parent. All rights reserved. This program is free software; you can redistribute it and/or modify it under the
same terms as Perl itself.
perl v5.16.3 2013-06-07 Net::LDAP::Control::SyncState(3)