FatMin

Solaris Package Management Cheat Sheet

Basic Package Management Commands Show description about <pkg>	pkginfo -l <pkg>
Install <pkg-file>	pkgadd -d <pkg-file>
Remove <pkg>	pkgrm <pkg>
Find package which owns <file>	pkgchk -l -p <file>
List files in installed <pkg>	pkgchk -l <pkg>|awk '/^Pathname/ {print $2}'
List files in <pkg-file>	pkgchk -l -d <pkg-file>|awk '/^Pathname/ {print $2}'
List all installed packages	pkginfo
Verify integrity of installed files from <pkg>	pkgchk <pkg>
Verify integrity of install files from all packages	pkginfo|awk '{print $2}'|xargs pkgchk

Changing a Solaris Server's IP Address

The following steps may be used to change the IP address of a Solaris system.

1. Change the host's IP in /etc/hosts for the change to take effect after reboot. If you are using Solaris 10, you must also change the host's IP in /etc/inet/ipnodes for the change to take effect after reboot.

2. Run ifconfig interface ip_address netmask broadcast_address for the IP address change to take effect immediately. The netmask and broadcast_address should be specified if you are using variable length subnet masks (VLSM), but may be omitted otherwise.

3. If you are using variable length subnet masks (VLSM), add the host's network number and subnet mask to /etc/netmasks.

If the new IP address places the system on a different network:

4. Place the host's new default gateway in /etc/defaultrouter, place new netmask in /etc/netmasks

5. Run route add default new_gateway for the new default gateway to take effect immediately.

6. Run route delete default old_gateway to delete the old default gateway from the routing table.

Veritas Volume Manager Upgrade Solaris 8

I've been told by some that this process is overkill, and have been told by others that this process is the cleanest way to go. PLease procede at your own risk.

QuickNotes: vxlicrep -e will allow you view your veritas license along with lot of additional information.

Step 1. Backup any file systems that are part of rootdg

This particular system is running Veritas 3.5 which requires a rootdg. This system has 3 file systems that are part of this dg. They are seen below. Comment any rootdg entries out of the /etc/vfstab.

/dev/vx/dsk/rootdg/home 1048576 35232 950055 4% <mountpoint>

/dev/vx/dsk/rootdg/disk 1048576 467462 544827 47% <mountpoint>

/dev/vx/dsk/rootdg/disk 1048576 55289 932147 6% <mountpoint>

These systems are located on this disk slice.

7 unassigned wm 5566 - 14086 41.35GB (8521/0/0) 86709696

First step is to back these 3 file systems up locally where ever there is room or over NFS mount.

Step 2: Export & Unmount

Unmount any veritas filesystems and export and disk groups.

Step 3. Break Mirrors.

At this point I need to break the submirrors off that are on the second system disk. In this case c1t1d0.

Use the format below

metadetach mirror submirror 

for example:

metattach d1 d21

Step 4. Keep Veritas from Starting up on Reboot.

Touch /etc/vx/reconfig.d/state.d/install-db to prevent Veritas from starting up with the box.

Step 5. Reboot in Single User mode, Verify that you are booting of off the primary disk. Init 0, boot -s

Step 6. Remove the current Veritas packages in the order listed below. (You may encounter addition packages not listed here. If this occurs add these packages to the removal order after VRTSvcsvr and before VRTSvxfs)

1. VRTSvmdoc

2. VRTSfsdoc

3. VRTSvmman

4. VRTSvrdoc

5. VRTSvrw

6. VRTSweb

7. VRTSobgui

8. VRTSvmpro

9. VRTSfspro

10. VRTSob

11. VRTSspc

12. VRTSvcsvr

13. VRTSordoc (Should be Database Edition Only)

14. VRTSorgui (Should be Database Edition Only)

15. VRTSdbed (Should be Database Edition Only)

16. VRTSvxmsa

17. VRTSvxfs

18. VRTSvxvm

19. VRTSvxlic

Step 7: Install San Foundation kit, (Sol8), make sure that you reconfigure reboot in single user mode

Step 8: devfsadm -Cv, change to runlevel 2 before next step.

Step 9: Install new veritas and patch with maint pack 2, then reboot again.

Step 10: Upgrade disk groups and file systems.

Upgrading Disk Groups:

To determine what DG version you are running, you can use the following command

vxdg -q list <my-dg> | grep version.

Import your disk groups, and run the following command on each DG, the -T is optional.

vxdg [ -T version ] upgrade diskgroup.

Upgrading File Systems:

To determine what FS version you are running, you can use the command below.

fstyp -v /dev/vx/dsk/dev/device

Mount your filesystems and then run the following command

vxupgrade -n 6 /mountpoint

Step 11: Use the format command to create new slices (on disk0) for the 3 file systems listed in step one. Basically split the 41.35gb contained in Slice 7 across Slice 5-7.

5 unassigned wm 0 0 (0/0/0) 0

6 unassigned wm 0 0 (0/0/0) 0

7 unassigned wm 5566 - 14086 41.35GB (8521/0/0) 86709696

Step 12: Mount the new slices and copy data from the original mount points to the new mounts.

Step 13: Load the partition table from disk one onto disk two.

Step 14: Reattach Mirrors.

Solaris Soft and Hard Limits

Hard limits are a kernel-configurable item, and users can't exceed them.

Soft limits are the user defaults, and users can change that using the 
ulimit program or the limit/unlimit builtins.

Basically, soft limits can be changed to anything up to the hard limit.
  
Think of soft limits as the warning barrier. When a user reaches 
the soft limit they will get an warning message but are still allowed 
to use more space up to the hard limit. Also, you can configure the 
system to set expiration times for users who have exceeded their soft limit.

You can set both soft and hard limits. The system will not allow a user
to exceed his or her hard limit. However, a system administrator may 
set a soft limit (sometimes referred to as a quota), which the user can temporarily
exceed. The soft limit must be less than the hard limit. 

Use ulimit -a to check soft limits, and ulimit -Ha to check hard limits.

These values will display as open files.

You can set these values by placing the following entries in /etc/system.

This will require a reboot

set rlim_fd_max=8192
set rlim_fd_cur=256 

rlim_fd_max is the hard limit, and rlim_fd_cur is the current limit (or soft limit)

Solaris Network Connection Performance Part I

Monitoring Solaris Ethernet Performance

Netstat -i

This option is used to diagnose the network problems when  the connectivity is there but  it is slow in response .

Values to look at:

    * Collisions (Collis)
    * Output packets (Opkts)
    * Input errors (Ierrs)
    * Input packets (Ipkts)

Network collision rate = Output collision counts / Output packets

Network-wide collision rate greater than 10 percent  will indicate

    *  Overloaded network,
    *  Poorly configured network,
    *  Hardware problems. 

Input Packet Error Rate = Ierrs / Ipkts.

If the input error rate is high (over 0.25 percent), the host is dropping packets. Hub/switch cables etc needs to be checked for potential problems. 

Name  Mtu  Net/Dest   Address    Ipkts     Ierrs Opkts     Oerrs Collis Queue
lo0   8232 loopback   localhost  43523390  0     43523390  0     0      0
hme0  1500 <hostname> <hostname> 561847305 886   483621617 0     0      0
qfe0  1500 <hostname> <hostname> 13480886  1     1521743   0     0      0

You can also use the following to determine the the ethernet interface link status,and speed on your interface. In the example below I am running these on hme0

ndd -set /dev/hme instance 0
ndd -get /dev/hme link_status
ndd -get /dev/hme link_mode
ndd -get /dev/hme link_speed

If you have only one ethernet interface, you can leave out the instance command. Otherwise, you can specify the hme instance number there. The results of the next three commands are either 1 or 0. In each case, the value means:

link_status:  0=down 1=up
link_mode:   0=half duplex  1=full duplex
link_speed:  0=10Mbps  1=100Mbps

You can also use the following netstat command. Replace ce0 with your ethernet adapter

>netstat -k ce0 | egrep 'link_speed|link_status|link_duplex'
lp_cap_asmpause 1 lp_cap_pause 0 link_T4 0 link_speed 1000
link_duplex 2 link_asmpause 0 link_pause 0 link_up 1 mac_mtu 1522

How to read this junk:
link_up - 0 down, 1 up
link_speed - speed in Mbit/s
link_duplex - 1 half duplex, 2 full duplex, 0 down

Sun RSC Configuration for the v480 & v490

Introduction

This page describes how to setup and manage a Sun RSC (Remote Serial Console) on the v480 and v490, as well as the e250 and e450. I omitted the latter two as those systems are ancient.

Before You Begin

Assign an IP address, netmask and gateway to the server. You must download the RSC utilities version 2.2.3 or later to the server and run the utilities before you can configure the server's RSC.

Steps

• Log in as root to the V490 or V890 manageable server.
• Download the RSC version 1.2.3 utilities zip file.Go to http://www.sun.com/servers/rsc.html. Download the zip file appropriate for the Solaris operating system installed on the server:

Solaris 9 or later: rsc2.2.3_packages_s9.zip Solaris 8: rsc2.2.3_packages_s8.zip When the download has completed, unzip the file to a temporary directory, and then change directory to the temporary directory.

• Install the RSC version 2.2.3 packages on the manageable server.

Install the following packages on the server using the pkgadd command: SUNWrsc - the RSC base package for installation on the host machine SUNWrscd - the RSC documentation package SUNWrscj - the RSC GUI package to display the RSC GUI

If you are asked whether to install conflicting files, type Y to override the existing version.

Redirecting the Console to the RSC

After RSC software is installed and configured, the system console is still available as on any normal Sun machine. To enable RSC as the system console device instead, you must access the server console, shut down the system, and type the following commands at the ok prompt:

ok diag-console rsc

ok setenv input-device rsc-console

ok setenv output-device rsc-console

RSC Commands

The RSC commands are located in the following path:
/usr/platform/SUNW,Sun-Fire-V490/rsc

rsc-config /usr/platform/SUNW,Sun-Fire-V490/rsc/rsc-config

The command above can be used to configure the RSC.

The rscadm command has many options see below.

rscadm - COMMAND DETAILS
  rscadm help => this message
  rscadm date [-s] | [[mmdd]HHMM | mmddHHMM[cc]yy][.SS] => print or set date
  rscadm set <variable> <value> => set variable to value
  rscadm show [variable] => show variable(s)
  rscadm resetrsc [-s] => reset RSC (-s soft reset)
  rscadm download [boot] <file> => program firmware or [boot] monitor
  rscadm send_event [-c] "message" => send message as event (-c CRITICAL)
  rscadm useradd <username> => add RSC user account
  rscadm userdel <username> => delete RSC user account
  rscadm usershow [username] => show user details
  rscadm userpassword <username> => set user password
  rscadm userperm <username> [cuar] => set user permissions
  rscadm shownetwork => show network configuration
  rscadm loghistory => show RSC event log
  rscadm version => show RSC version

Below is the SHOW option

mail_enabled="false"
ip_mode="config"
ppp_enabled="false"
tpe_link_test="true"
serial_baud="9600"
serial_parity="none"
serial_stop="1"
serial_data="8"
customerinfo=""
ip_addr="xxx.xx.xxx.xxx"
ip_netmask="255.255.xxx.x"
ip_gateway="0.0.0.0"
mailhost=""
mailuser=""
ppp_local_ip_addr="0.0.0.0"
ppp_remote_ip_addr="0.0.0.0"
hostname="xxxxxx"
escape_char="~"

 

 

Handy Crontab Header

# minute (0-59),
# |      hour (0-23),
# |      |       day of the month (1-31),
# |      |       |       month of the year (1-12),
# |      |       |       |       day of the week (0-6 with 0=Sunday).
# |      |       |       |       |       commands
3       2       *       *       0,6     /some/command/to/run
3       2       *       *       1-5     /another/command/to/run

Solaris Printing and You!

I hardly ever have a request to add a printer to a Solaris box, but every one and a while a developer needs me to add one. Not that I have any idea what they are printing...

Below are my notes...

Adding a Printer:
In the example below we are adding a printer with the -p option for the printer name, the -s for the print server, and -D for the description.

# lpadmin -p luna -s saturn 
# lpadmin -p luna -D "Room 1954 ps" 
# lpadmin -d luna 
# lpstat -p luna 


Verify you can print with the following command
$ lp -d printer-name filename

Solaris Volume Manager

Solaris Volume Manager (formerly known as Online: DiskSuite, and later Solstice DiskSuite is a software package for creating, modifying and controlling RAID disks in Solaris. The process below outlines steps that you need to take to setup basic root disk mirroring.

Adding a new Disk? Create your Partition Table for your Mirror:

Using the format command, select your initial disk. Then select par, then name to save off you partition table to disk.

Then switch to the other disk and label the other disk with the saved partition table.

Md.tab -- add mirror information:

The file /etc/md.tab is basically a map file where you define your metadevices and the physical devices that they represent. In the example below the metadevice d0 has two submirrors, d10 and d20.

For Example:
 

d0      -m              d10

d10             1 1     /dev/dsk/c0t0d0s0

d20             1 1     /dev/dsk/c0t1d0s0

#swap mirror

d1      -m              d11

d11             1 1     /dev/dsk/c0t0d0s1

d21             1 1     /dev/dsk/c0t1d0s1

#var mirror

d4      -m              d14

d14             1 1     /dev/dsk/c0t0d0s4

d24             1 1     /dev/dsk/c0t1d0s4

Add Meta Databases:

bash-3.00# metadb -c 3 -f -a /dev/dsk/c5t0d0s3
bash-3.00# metadb -c 3 -f -a /dev/dsk/c5t4d0s3

Make sure that you create them on the correct slice. The normal standard that I follow, has me creating them on slice 3. In the example above you are creating 3 metadbs on the mirror disk. Not sure if you need the -f option on the second db, but it does not seem to cause any issues.

Initialize your Mirrors:

In the example below you are initializing your one way mirror. These are the entries from the md.tab. Here I am initializing each side of the mirror. Note that you do not need to specify "d10 1 1 c5t0d0s0" if you have added this information to the md.tab Use the '-f' switch when the filesystem on that slice is currently mounted.

EXAMPLE for Slice 0:

bash-3.00# metainit -f d10 1 1 c5t0d0s0
d10: Concat/Stripe is setup
bash-3.00# metainit d20 1 1 c5t4d0s0
d10: Concat/Stripe is setup

.

Attach your First Submirror:

The example below shows how attach your one way mirror to your metadevice. Once this step is complete. You will want to reboot, and attach the other side of the mirror. You can then edit the /etc/fstab with the new metadevices.

EXAMPLE:

metainit d0 -m d10

Metaroot to Create root mirror in fstab:

The metaroot command is used to modify the /etc/fstab

metaroot d0

Then modify any other entries.

Attach Secondary Mirror:

metattach d20

Other Helpful Commands:

How to Delete Metadbs:

If you need to start over, you can use the command below to remove metadatabases.

metadb -d -f /dev/dsk/diskname

Inpect your Metadbs:

# metadb -i
        flags           first blk       block count
     a        u         16              8192            /dev/dsk/c0t0d0s7
     a        u         16              8192            /dev/dsk/c0t1d0s7
     a        u         16              8192            /dev/dsk/c0t2d0s7

How to Detach Mirrors:

metadetach mirror submirror

metadetach d0 d20

after completing the step above you should clear the concat/stripe

metaclear d20

Metastat:

Metastat gives you the status of your mirrors

# metastat
d7: RAID
    State: Initializing
    Initialization in progress: 12.2% done		<== not done yet
    Interlace: 32 blocks
    Size: 208618176 blocks (99 GB)
Original device:
    Size: 208627648 blocks (99 GB)
        Device     Start Block  Dbase        State Reloc  Hot Spare
        c0t0d0s7      10506       Yes Initializing   Yes
        c0t1d0s7      10506       Yes Initializing   Yes
        c0t2d0s7      10506       Yes Initializing   Yes

 

Solaris HBA Notes

Below is a cheat sheet that I put together that are helpful for managing HBAs on Solaris

Helpful Commands

---

luxadm probe

luxadm -e port

devfsadm

 

  More Helpful Commands

---

To show Sun/Qlogic HBA's
luxadm qlgc

 

To show all vendor HBA's
luxadm fcode_download -p

 

Found Path to 0 FC100/S Cards

  Complete

  Found Path to 5 FC100/P, ISP2200, ISP23xx Devices

  Opening Device: /devices/pci@9,600000/SUNW,qlc@2/fp@0,0:devctl

  Detected FCode Version:       ISP2200 FC-AL Host Adapter Driver: 1.14 01/11/20

  Opening Device: /devices/pci@8,700000/SUNW,qlc@5,1/fp@0,0:devctl

  Detected FCode Version:       ISP2312 Host Adapter Driver: 1.14.09 03/08/04

  Opening Device: /devices/pci@8,700000/SUNW,qlc@3,1/fp@0,0:devctl

  Detected FCode Version:       ISP2312 Host Adapter Driver: 1.14.09 03/08/04

  Opening Device: /devices/pci@8,700000/SUNW,qlc@3/fp@0,0:devctl

  Detected FCode Version:       ISP2312 Host Adapter Driver: 1.14.09 03/08/04

  Opening Device: /devices/pci@8,700000/SUNW,qlc@5/fp@0,0:devctl

  Detected FCode Version:       ISP2312 Host Adapter Driver: 1.14.09 03/08/04

  Complete

  Found Path to 0 JNI1560 Devices.

  Complete

Another Method
prtpicl -v > filename

 

To show link status of card
luxadm -e port

To see the WWN's (using address given to you from previous commands), it is the last one that specifies it is a HBA, so the port WWN here is 210000e08b100d16

# luxadm -e dump_map /devices/pci@1f,0/pci@1/SUNW,qlc@1/fp@0,0:devctl

Pos Port_ID Hard_Addr Port WWN Node WWN Type

0 10600 0 224100015d210900 220000015d210900 0x1f (Unknown Type)

1 10700 0 210000e08b103417 200000e08b103417 0x1f (Unknown Type)

2 10800 0 210000e08b100d16 200000e08b100d16 0x1f (Unknown Type,Host Bus Adapter

 

Configuring storage online

cfgadm -al

# 

Ap_Id Type Receptacle Occupant Condition

c0 scsi-bus connected configured unknown

c0::dsk/c0t0d0 disk connected configured unknown

c0::dsk/c0t2d0 CD-ROM connected configured unknown

c1 fc-fabric connected unconfigured unknown

c1::210000e08b103417 unknown connected unconfigured unknown

c1::224100015d210900 unknown connected unconfigured unknown

c2 fc-fabric connected unconfigured unknown

c2::210100e08b303417 unknown connected unconfigured unknown

c2::223100015d210900 unknown connected unconfigured unknown

So we're going to run

# cfgadm -f -c configure c1 c2

you can now run devfsadm

Example cfgadm -al

c1                             fc-private

c1::21000020379cb9bb           disk         connected    configured   unknown

c4                             fc-fabric    connected    unconfigured unknown

c5                             fc           connected    unconfigured unknown

C1 is a 280r internal controller
C4 is a HBA attached to a switch with no targets
C5 is a HBA that has nothing connected

 This Might Help

---

1) The command cfgadm -al
2) look for the fc-fabric

c2                             fc-fabric    connected    

c3                             fc-fabric    connected    

3) and then cfgadm -cconfigure c2 c3

4) Now you see the LUN

 

  A Magical File

---

/kernel/drv/sd.conf

 

  Checking IO on Fibre Cards

---

iostat -xcn 5

  San Foundation Kit

---

You get this from Sun, install it after you install the drivers
There is no SAN foundation kit for Solaris 10. Installing the SAN foundation kit will do bad things. It's only for Solaris 8 and Solaris 9.

 

  Get the WWN

---

• Method 1

$ luxadm probe
$ luxadm -e port

$ luxadm -e dump_map <xyz> where xyz= your connected port.

 

• Method 2

bash-2.03# cat /var/adm/messages | grep -i WWN

Sep 20 18:23:28 alautpnc003 qlc: [ID 657001 kern.info] Qlogic qlc(0) WWPN=210000e08b934ead : WWNN=200000e08b934ead

Sep 20 18:23:39 alautpnc003 qlc: [ID 657001 kern.info] Qlogic qlc(1) WWPN=210100e08bb34ead : WWNN=200100e08bb34ead

• Method 3

#modinfo | grep SunFC

46 10274e94 20010 172 1 fcp (SunFC FCP v20050926-1.86)

47 10269923 8204 - 1 fctl (SunFC Transport v20050926-1.36)

51 1028b850 15e28 171 1 fp (SunFC Port v20050926-1.53)

53 10300f09 c5024 175 1 qlc (SunFC Qlogic FCA v20051013-2.08)

This example is SFS 4.4.8 from 2005.

All of above assumes Sun-QLogic (qlc) not QLogic (qla).

• Method 4

 cfgadm -o show_FCP_dev -al 

• Method 4

 prtconf -pv | grep -i wwn | grep -i port