A Quick Ref guide to SUN OBP

 

Sorry for image, pdf file not accepted here.  i can provide .pdf file on request.hence

A TitBit info about Solaris kernel - good one

Solaris Kernel Tuning

sysdef -i reports on several system resource limits. Other parameters can be checked on a running system using adb -k :

adb -k /dev/ksyms /dev/mem
parameter-name/D
^D (to exit)

More information on kernel tuning is available in Sun's online documentation.

maxusers

maxusers is the most frequently tuned kernel parameter. Its original use (as an overall limit to the number of concurrent users on a system) is much less important than its role as a basis for calculating other kernel parameters. The default value is set to either the number of MB of physical memory or MAX_DEFAULT_MAXUSERS, whichever is lower.
For Solaris 2.5.1-7, MAX_DEFAULT_MAXUSERS is 1024. For Solaris 8-10, MAX_DEFAULT_MAXUSERS is 2048.
maxusers can be set explicitly in the /etc/system file, but is limited to 2x MAX_DEFAULT_MAXUSERS.
Several key kernel parameters are set when maxusers is set unless explicitly overridden in the /etc/system file. Some of these formulas differ between different versions of Solaris:

• max_nprocs: Number of processes = 10 + (16 x maxusers)
• ufs_ninode: Inode cache size = (17xmaxusers)+90 (Solaris 2.5.1) or 4x(maxusers + max_nprocs)+320 (Solaris 2.6-8). See the Disk I/O page for more information.
• ncsize: Name lookup cache size = (17xmaxusers)+90 (Solaris 2.5.1) or 4x(maxusers + max_nprocs)+320 (Solaris 2.6-8). See the Disk I/O page for more information.
• ndquot: Quota table size = (maxusers x 10) + max_nprocs
• maxuprc: User process limit = max_nprocs - 5

ptys

Solaris 8+ dynamically sizes the number of ptys available to a system, so you are less likely to run into pty starvation than was the case under Solaris 2.5.1-7. There are still hard system limits that are set based upon hardware configuration, and it may be necessary to increase the number of ptys manually as in Solaris 2.5.1-7. If the system is suffering from pty starvation, the number of ptys available can be increased by increasing pt_cnt above the default of 48. Solaris 2.5.1 and 2.6 systems should not have pt_cnt set higher than 3844 due to limitations with the telnet and rlogin daemons. Solaris 7 does not have this restriction, but there may be other system issues that prevent setting pt_cnt arbitrarily high. Once pt_cnt is increased, a reconfiguration boot (boot -r) is required to build the ptys.
If pt_cnt is increased, some sources recommend that other variables be set at the same time. Other sources (such as the Solaris2 FAQ) suggest that this advice is spurious and results in a needless consumption of resources. See the notes below before making any of these changes; setting the values too high may result in wasted memory. In any case, one form of these recommendations is:

• npty: Set to pt_cnt (see the note below)
• nautopush: Set to twice the value of pt_cnt
• sadcnt: Set to same value as pt_cnt

npty limits the number of BSD ptys. These are not usually used by applications, but may need to be increased on a system running a special service. In addition to setting npty in the /etc/system file, the /etc/iu.ap file will need to be edited to substitute the value npty-1 in the third field of the ptsl line. After both changes are made, a boot -r is required for the changes to take effect. Note that Solaris does not support any more than 176 BSD ptys in any case.
sadcnt sets the number of STREAMS addressable devices and nautopush sets the number of STREAMS autopush entries. nautopush should be set to twice sadcnt. Whether or not these values need to be increased as above depends on the types of activity on the system.

RAM Tuneables

See the Memory/Swapping page for a discussion of parameters related to RAM and paging.

Disk I/O Tuneables

See the Disk I/O page for a full discussion of disk I/O-related tuneables.

IPC Tuneables

Check the IPC Tuning page for InterProcess Communication-related resource parameters.

File Descriptors

See the File Descriptors page for more discussion regarding tuning issues. File descriptors are retired when the file is closed or the process terminates. Opens always choose the lowest-numbered file descriptor available. Available file descriptors are allocated as follows:

• rlim_fd_cur: It is dangerous to set this value higher than 256 due to limitations with the stdio library. If programs require more file descriptors, they should use setrlimit directly.
• rlim_fd_max: It is dangerous to set this value higher than 1024 due to limitations with select(). If programs require more file descriptors, they should use setrlimit directly.

(The cautionary notes on both of these items become less important as applications are re-written to use poll() rather than select(), or are developed as native 64-bit applications. Any changes should be tested in a non-production environment before deployment. The Solaris2 FAQ includes a discussion of this issue.)

Misc Tuneables

• dump_cnt: Size of dumps.
• rstchown: Posix/restricted chown enabled (default=1)
• ngroups_max: Maximum number of supplementary groups per user (default=32).

Source : http://www.princeton.edu/~unix/Solaris/troubleshoot/kerntune.html

Usage of Uadmin command.

What are all the options we can use  to uadmin.

This command should not use for normal purpose. its special command for internal purpose.

Refer man page for information.


uadmin 2 0 sync the filesystems and drops system to ok prompt
uadmin 2 1 sync the filesystems and reboots to multi-user mode 
uadmin 2 2 sync the filesystems and reboots interactively                   
uadmin 2 3 sync the filesystems and reboots to single-user mode 
uadmin 2 6 sync the filesystems and powers off the system

uadmin 1 0 do not sync filesystems and drops system to ok prompt
uadmin 1 1 do not sync filesystems and reboots to multi-user mode 
uadmin 1 2 do not sync filesystems and reboots interactively                   
uadmin 1 3 do not sync filesystems and reboots to single-user mode 
uadmin 1 6 do not sync filesystems and powers off the system

How to get WWN on solaris

World Wide Name (WWN) are unique 8 byte (64-bit) identifiers in SCSI or fibre channel similar to that of MAC Addresses on a Network Interface Card (NIC).
Talking about the WWN names, there are also
World Wide port Name (WWpN), a WWN assigned to a port on a Fabric which is what you would be looking for most of the time.
World Wide node Name (WWnN), a WWN assigned to a node/device on a Fibre Channel fabric.

To find the WWN numbers of your HBA card in Sun Solaris, you can use one the following procedures

For Solaris 10 :Below all commnads will provide you WWN #'s

# fcinfo hba-port      {OR}

# prtconf -vp | grep -i wwn    {OR}

# scli -i   {OR}
# prtpicl -v | grep wwn
# luxadm -e port  ( get the full device_path)

   #luxadm -e dump_map /devices/pci@6000/pci@0/pci@7/SUNW,qlc@0/fp@0,0:devctl
# If its third party card, use to install the driver and run the commands, (ex: lpfc tool)

 For Solaris 8/9
All commands as above except fcinfo,


Kindly post if anyone has different ways to get.

Thanks

GRUB Boot Archive With SVM troubleshoot - Useful

GRUB Boot Archive With SVM, A Better Approach

By Julien Gabel 

• boot
• failsafe
• GRUB
• SVM

In a previous discussion about the GRUB boot archive and how it can be regenerated in Failsafe mode, I mentioned that it will not be as easy as it can be when the root file system use the md driver. I previously show a method to do this which necessitate to unmirror one or more file systems when the root file system is build upon a SVM mirror. This was not very optimal since a lot of of manipulations are involved, which may lead to human error(s), and may seems to be a little complicated.
This method was build on Performing System Recovery from the Solaris Volume Manager official documentation, which show up last month on the Sun-Managers mailing list.
Note: Although this test case was done using Solaris 10 10/08 under a virtual machine build upon VirtualBox on latest OpenSolaris release, the instructions must be valid for Solaris 10 1/06 and later.

Initial setup

As we saw before, the system use only a root file system, and a swap device. Both are encapsulated with SVM:

# df -k -F ufs
Filesystem     kbytes    used   avail capacity  Mounted on
/dev/md/dsk/d0 6147798 3455578 2630743      57%  /
# swap -l
swapfile             dev  swaplo blocks   free
/dev/md/dsk/d1      85,1       8 4194288 4194288
# metastat -c d0 d1
d0               m  6.0GB d10 d20
    d10          s  6.0GB c0d0s0
    d20          s  6.0GB c1d1s0
d1               m  2.0GB d11 d21
    d11          s  2.0GB c0d0s1
    d21          s  2.0GB c1d1s1

Regenerate the GRUB boot archive

The idea is to boot on the GRUB Failsafe mode, get the md configuration from local root file system, and load manually the md module, hence properly configured. The main advantage is to be fully self hosted from the Failsafe mode, and not have to manipulate SVM more than necessary, especially when breaking the mirror, loosing redundancy for a time.

[...]
Booting to milestone "milestone/single-user:default".
Configuring devices.
Searching for installed OS instances...
/dev/dsk/c0d0s0 is under md control, skipping.
/dev/dsk/c1d1s0 is under md control, skipping.
No installed OS instance found.

Starting shell.
# mount -F ufs -o ro /dev/dsk/c0d0s0 /a
# cp -p /a/kernel/drv/md.conf /kernel/drv
# umount /a
# update_drv -f md
devfsadm: mkdir failed for /dev 0x1ed: Read-only file system
# metainit -r
# metasync d0
# fsck /dev/md/rdsk/d0
# mount -F ufs /dev/md/dsk/d0 /a
# bootadm update-archive -R /a
# umount /a
# reboot

Really interesting!


Source  & Find more info at http://blog.thilelli.net/tag/SVM