09-19-2016
That's not much information...
You will need to create a vdsdev in your vds service. this vdsdev can be used as a vdisk for your ldom. within the ldom you will need to add this disk to the volume(s) for your /u02... and that will depend on your volume manager... ZFS? VxVM?
gP
9 More Discussions You Might Find Interesting
1. 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
2. Solaris
I have viewed a few previous posts regarding this, but none of them quite described or worked with my issue.
I am out of local disk space on my LDOM Manager but still have plenty of SAN vCPU and Memory available so I am trying to install a new LDOM OS on SAN.
I have exposed the SAN to the... (0 Replies)
Discussion started by: MobileGSP
0 Replies
3. Solaris
Solaris for Sparc 11.1 with the latest patches. Created a Guest LDOM with two vnet's net0 and net1, installed a guest whole root, ip exclusive zone that I want to be able to utilize DHCP. I have been able to create the zone but unable to get it to boot because I am unable to assign an anet to it.... (4 Replies)
Discussion started by: os2mac
4 Replies
4. Solaris
Host System: SPARC S7-2 Server; 2x8-core CPUs; 128Gb RAM; 2x600Gb HDD. running Solaris 11.3.
Last login: Tue Sep 19 14:42:42 2017 from xxx.xxx.xxx
Oracle Corporation SunOS 5.11 11.3 June 2017
$ uname -a
SunOS sog01 5.11 11.3 sun4v sparc sun4v
$
Original physical systems: Sun... (0 Replies)
Discussion started by: apmcd47
0 Replies
5. Solaris
Generally, this is what we do:-
On primary, export 2 LUNs (add-vdsdev).
On primary, assign these disks to the ldom in question (add-vdisk).
On ldom, created mirrored zpool from these two disks.
On one server (which is older) we have:-
On primary, create mirrored zpool from the two LUNs.... (4 Replies)
Discussion started by: psychocandy
4 Replies
6. Solaris
Hi! Quick background for the question...
I have Solaris 11.4 control/primary zone with some LDOM's on top of it. I have some raw iSCSI LUN's presented to the control zone/primary zone from a NetApp, which I then pass up to the LDOM's via the VDS/vdisk. So basically the LDOM VM's see the disk as... (1 Reply)
Discussion started by: rtmg
1 Replies
7. Solaris
hello to everyone. im new member here.
i have a problem with a guest ldom on solaris 11 sparc in a T8. I need to access to disk vds assigned to guest domain but from control domain.
I want to modify a parameter in inittab of the guest domain because start guest domain give me problems... (2 Replies)
Discussion started by: Liam_
2 Replies
8. UNIX for Beginners Questions & Answers
I'm really stuck here. I've created an LDOM on a SPARC T4-1 with Solaris 11.4 to run a copy of Linux for SPARC. I got the Linux ISO installed and Linux itself installed and booted OK. The only thing is is that there's no networking available in the Linux guest.
This question is basically the... (7 Replies)
Discussion started by: Michele31416
7 Replies
9. Solaris
I have a guest LDOM running Solaris 10U11 on a Sun T4-1 host running Solaris 11.4. The host has a disk named bkpool that I'd like to share with the LDOM so both can read and write it. The host is hemlock, the guest is sol10.
root@hemlock:~# zpool list
NAME SIZE ALLOC FREE CAP DEDUP ... (3 Replies)
Discussion started by: Michele31416
3 Replies
LEARN ABOUT HPUX
cmvxserviced
cmvxserviced(1m) cmvxserviced(1m)
NAME
cmvxserviced - monitor VxVM and CVM volumes for a high availability package.
SYNOPSIS
cmvxserviced [-h|-v] [-O log_file] [-D log_level] [-t poll_interval] volume_path...
DESCRIPTION
cmvxserviced monitors VxVM and CVM volumes. It runs as a service within a package that depends on the monitored storage. When a monitored
volume fails or becomes inaccessible (see Scope of Monitoring), the service will exit, causing the package to fail on the current node.
The package's failover behavior depends on its configured settings.
cmvxserviced periodically probes each volume named by volume_path, which must identify a block device file.
Scope of Monitoring
The VxVM Volume Monitor detects the following failures:
o Failure of the last link to a storage device or set of devices critical to volume operation
o Failure of a storage device or set of devices critical to volume operation
o An unexpected detachment or disablement of a volume
The VxVM Volume Monitor does not detect the following failures:
o Failure of a redundant link to a storage device or set of devices if a functioning link remains
o Failure of a mirrored plex within a volume (assuming at least one plex is functional)
o Corruption of data on a volume which VxVM or CVM regards as enabled and active
Options
cmvxserviced supports the following options:
-h Displays the usage, as listed above, and exits.
-v Displays the monitor version and exits.
NOTE Do not include the -h or -v parameters in your service command; this will result in immediate package failure
at runtime.
-O log_file Specifies a file for logging (log messages are printed to the console by default).
-D log_level Specifies the log level. The level of detail logged is directly proportional to the numerical value of the log
level. That is, a log level of 7 will provide the greatest amount of log information. The default log level is 0.
-t poll_interval Specifies the interval between volume probes.
You can specify a polling interval of as little as 1 (one second), but bear in mind that a short polling interval
(less than 10 seconds) may impair system performance if you are monitoring a large number of volumes. HP recom-
mends a polling interval of at least 10 seconds if 50 or more volumes are being monitored by a single service com-
mand.
The default polling interval is 60 seconds.
EXAMPLES
/usr/sbin/cmvxserviced -O /pkg1/monlog.log -D 3 /dev/vx/dsk/cvm_dg0/lvol2
This command monitors a single volume, /dev/vx/dsk/cvm_dg0/lvol2, at log level 3, with a polling interval of 60 seconds, and prints all log
messages to the file /pkg1/monlog.log.
There should be a one to one relationship between monitoring services and log files. This provides a means to correlate log messages with
the originating monitor.
/usr/sbin/cmvxserviced /dev/vx/dsk/cvm_dg0/lvol1 dev/vx/dsk/cvm_dg0/lvol2
This command monitors two volumes at the default log level of 0, with a polling interval of 60 seconds, and prints all log messages to the
console.
/usr/sbin/cmvxserviced -t 10 /dev/vx/dsk/cvm_dg2/lvol3
This command monitors a single volume at log level 0, with a polling interval of 10 seconds, and prints all log messages to the console.
AUTHOR
cmvxserviced was developed by HP.
Requires Optional Serviceguard Software cmvxserviced(1m)