Solaris

Solaris fault manager overview One of the coolest features in Solaris 10 in the fault management service. Fault management allows system software to send telemetry data to the fmd(1m) daemon, which then diagnoses the problem, and takes action (e.g., offlining a faulty components and logging an error with FMRI/UUID information to syslog) based on the

The vntsd service defaults to listening for connections on localhost (IP address 127.0.0.1), so you canonly access domain consoles from the control domain by telnet to localhost. However, by changing the service con?guration you can enable remote access. This example recon?gures the console service for remote access: #svccfg svc:>select  ldoms/vntsd svc:/ldoms/vntsd> listprop vntsd    application vntsd/timeout_minutes  

Preparation Install Solaris 10 5/08 or higherNOTE : If you install Solaris 10 8/07,you need patch 127111-01 or higher Download Solaris 8 Container Software Download Solaris 9 Container Software Installation The following procedure is for Solaris 8 containers only. Follow the same steps to install Solaris 9container Step 1 Install Solaris 10 5/08 # cat

1) First find the right controller.  You can use the built in device alias.   Tip:  Use ‘devalias’ to show the devices to find the scsi controllers: {0} ok> devalias disk7 /pci@400/pci@2/pci@0/pci@4/scsi@0/disk@p3 disk6 /pci@400/pci@2/pci@0/pci@4/scsi@0/disk@p2 disk5 /pci@400/pci@2/pci@0/pci@4/scsi@0/disk@p1 disk4 /pci@400/pci@2/pci@0/pci@4/scsi@0/disk@p0 cdrom /pci@400/pci@2/pci@0/pci@4/scsi@0/disk@p6 scsi1 /pci@400/pci@2/pci@0/pci@4/scsi@0 disk3 /pci@400/pci@1/pci@0/pci@4/scsi@0/disk@p3 disk2 /pci@400/pci@1/pci@0/pci@4/scsi@0/disk@p2 disk1 /pci@400/pci@1/pci@0/pci@4/scsi@0/disk@p1 disk0 /pci@400/pci@1/pci@0/pci@4/scsi@0/disk@p0 disk /pci@400/pci@1/pci@0/pci@4/scsi@0/disk@p0 scsi0 /pci@400/pci@1/pci@0/pci@4/scsi@0 2)

First you have to have created a zone with memory capping enabled. This would be done during the zonecfg setup: zonecfg:s8-zone-solar97> add capped-memory zonecfg:zone:capped-memory> set physical=50m zonecfg:zone:capped-memory> set swap=100m zonecfg:zone:capped-memory> set locked=30m zonecfg:zone:capped-memory> end Once you zone is configured installed and running, you can view the resources of a zone: # /bin/prctl -n zone.max-swap `pgrep

If you have ever tried to mount a Linux NFS share on a Solaris workstation you may have seen the below error. solaris1# mount t3-61.abc.com:/exports/homes /mnt nfs mount: mount: /mnt: Not owner This may be caused by the Solaris system attempting to mount the exported file system running NFS version 4 instead of version 3.

number of physical cpu: “psrinfo -p” number of cores: “kstat cpu_info|grep core_id|sort -u|wc -l” number of threads: “psrinfo -pv” Code: # echo “`psrinfo -p` socket(s)” 2 socket(s) Code: # echo “`kstat -m cpu_info|grep -w core_id|uniq|wc -l` core(s) ” 8 core(s) Code: # echo “`psrinfo|wc -l` logical (virtual) processor(s)” 64 logical (virtual) processor(s) so (core(s) with

The Solaris volume manager, SVM, comes with the latest version of Solaris, Solaris OE 9. This is know as Solstice DiskSuite[tm] from previous versions of Solaris. Several new features are present: soft partitions, monitoring active disks, access via SMC. I will provide a simple guide how you can create a RAID 0 concatenation or stripe,