Unix ,Solaris,Veritas,Oracle, interview questions

2012-05-25T23:20:00.001-07:00

SOLARIS QUICK REFERENCE SOLARIS # uname –a  Gives all details about the system # uname –m  Displays H/W platform (sun4u) # uname –p  Machine processor architecture (sparc or i386) # uname –i  Machine model architecture (SUNW, Ultra 5_10) # uname –X  Detailed description # mkdir –p /data/dir  Creates directory and sub directory in one shot # rmdir –r /data  Deletes the directory and all its subdirectory and files # cp –r /data /data1  It copies the directory # echo $MANPATH : /usr/local/samba/man: # echo $PATH  Shows environmental path /usr/sbin:/usr/bin Grep Command Options -i  Searches for both upper & lower case characters -l  Lists the names of files with matching lines -n  Proceeds each line with the relative line number in the file -v  Inverts the search to display lines that do not match the pattern -w  Searches for the expression as a complete word. # find /kris –name file1  Searches for file file1 in /kris directory # find /ris –name file1 –exec ls –l {} \;  Search and display # find /kris –type f –size 0 –exec ls –l {} \;  Search for the file with size 0 # find /kris –user user1  Shows file used by user ‘user1’ $ PATH=$PATH:/usr/ccs/bin:/usr/ucb:  It will get appended to the existing path # ln –s  Creating symbolic link # ln  Creating hard link Unix File Permission r – 4, w – 2, x – 1 _rw_ r_ _ r_ _ (644)  Default file permission drwx r_x r_x (755)  Default directory permission O G O  Permission categories # ls –n /var/adm drwxrwxr_x 5 4 4 512 nov 15 14:55 file1 5 - No of hard link to the file or directory 4 – The UID of the owner 4 – The GID of the group 512 – Size # chmod –R 755  For inherit permission VI Editor Inserting and Appending Text a - Append text after the cursor A - Appends text at the end of the line i - Inserts text before the cursor I - Inserts text at the beginning of the line o - Opens a new line below the cursor O - Opens a new line above the cursor :r Inserts text from another file into the current file Key Sequence for the VI Editor n, left arrow or backspace Left one characters j or down arrow Down one line k or up arrow Up one line l, right arrow or spacebar Right one character w Forward one word b Back one word e To the end of the current word $ To the end of the line 0 (zero) To the beginning of the line ^ To the first non whitespace character on the line Return Down to the beginning of the next line G Goes to the last line of the file 1G Goes to the first line of the file :n Goes to the line n nG Goes to the line n Ctrl F Pages forward one screen Ctrl D Scroll down one half screen Ctrl B Pages back one screen Ctrl U Scrolls up one half screen Ctrl L Refreshes the screen Editing files using the VI editing commands R Overwrites or replace characters to the right of the cursor C Changes or overwrites characters to the end of the line s Substitute a string for a character at the cursor x Deletes a character at the cursor dw Deletes a word or part of the word to the right of the cursor dd Dletes the line containing the cursor D Deletes the line from the cursor to the right end of the line :n,nd Deletes the line n through n Using the Text Changing Commands u Undoes the previous command U Undoes all changes to the current line . Repeats the previous command Search and Replace Command /string Searches forward for the string ?string Searches backward for the string n Searches the next occurrence of the string N Searches for the previous occurrence of the string :%s/old/new/g Searches for the old string and replace it with the new string globally Using the text copying and Text Pasting Commands yy Yanks a copy of a line p Puts yanked or deleted text under the line containing the cursor P Puts yanked or deleted text before the line containing the cursor :n,n co n Copies lines n through n and puts them after line n :n,n m n Moves lines n through n to line n File Archives # tar –cvf bkp.tar file1 file2  Will archive file1 & file2 # tar –tvf bkp.tar  Shows the table of content # tar –xvf bkp.tar  It extracts file from the tar archive # jar –cvf bkp.tar # jar –tvf bkp.jar # jar –xvf bkp.jar # compress bkp.tar  To compress tar archive # ls bkp.tar.z # uncompress bkp.tar.z  To uncompress tar archive # gzip bkp.tar  To create gzip file bkp.tar.gz # gunzip bkp.tar.gz  To extract the tar archive by gunzip bkp.tar # zip out.zip bkp.tar  To create zip archive # unzip out.zip  To extract the zip archive Module – 1  Introducing the Solaris OE Directory Hirerarchy /bin Symbolic link to /usr/bin contains binary files of standard system commands /kernel Platform independent lodable kernel modules /platform Platform dependable lodable kernel modules /sbin Single user bin directory contains essential executables /usr Contains programs, scripts and libraries that are used by all system users Unix System Resources /var Directory of varying files, includes temporary, logging, or status files /dev/cua Dial out device files for UUCP & PPP /dev/dsk Block disk devices /dev/rdsk Raw disk devices /dev/pts Psuedo terminal devices /dev/md Metadisk devices /dev/term Serial devices /dev/sound Audio device files /dev/rmt Raw magnetic tape devices /etc/cron.d Config info for cron utility /etc/default Default info for various prog. /etc/inet Config files - network services /etc/init.d Scripts to stop & start services /etc/lp Config info for printer /etc/nfs Config info for NFS server logging /etc/rc#.d Scripts for various run levels /etc/skel Default shell initialization files /usr/bin Standard system command /usr/sbin System administration commands /usr/kernel Platform independent lodable kernel module devfsadm – Solaris 8 & 9 drvconfig – Solaris 2.x through 2.7 Module – 2  Disk Slices 0 / 1 swap 2 Entire Disk 5 /opt 6 /usr 7 /export/home /dev – Logical Device Names /devices – Physical Device Names /etc/path_to_inst  For each device, the system records its physical and instance name # prtconf  Shows system information including memory size # devfsadm  Will search and configure new devices added. # devfsadm –c disk # devfsadm –i # devfsadm –v  To print changes made to the /dev and /devices directory # devfsadm –c  To invoke cleanup routines that remove unreferenced symbolic links for devices # format Format> label  To store partition details. Format> fdisk  To create partitions Format> verify  Display partition details Format> partition  To get into partition menu Format> save  Saving new disk and partition :/etc/format.dat Partition> 0  Change 0 partition select  Select a predefined table modify  Modify a predefined partition table name  Name the current table print  Displays the current table label  Write partition map and label to the disk # prtvtoc /dev/rdsk/c1t0d0s2  To view disk table # prtvtoc /dev/rdsk/c1d0s2 > /in  To save disk partition details to /in file # fmthard –s /in /dev/rdsk/c1d0s2  To load partition detail from file to disk Module – 3  Managing the Solaris OE File System ufs – Unix FS hsfs – High Sierra FS pcfs – PC FS for DOS FAT32 FS udfs – Universal Disk Format FS nfs - Network FS Pseudo FS – Memory based FS tmpfs swapfs procfs mntfs VTOC present in the first sector in the raw disk area. VTOC - 512 sector Boot Block - 1-15 sector Super Block - 16-31 First Cylinder Group - 32 Creating File Systems # newfs /dev/rdsk/c1d0s0  Creating FS # newfs –i 16384 /dev/rdsk/c1d0s0  Creating FS with data block size 16KB # mount /dev/dsk/c1d0s0 /p1  Mounting partition in /p1 directory # fstyp –v /dev/rdsk/c1d0s0 | grep minfree minfree 6%  To know the reserved disk space # tunefs –m 2 /dev/rdsk/c1d0s0  This will reduce the reserved space to 2% # umount /p1  To umount a partition.  Never run the fsck command on a mounted FS. The /, /usr and /var FS should have the fsck command run on them on single user mode # fsck /dev/rdsk/c0td0s7  To check the FS in interactive mode # fsck –o f,p /dev/rdsk/c0t0d0s7  f – forces p – preen or Non interactive mode # fsck –y /dev/rdsk/c0t0d0s7  It answers that to all questions we said yes with –y option # newfs –N /dev/rdsk/c0t0d0s7  To view the locations of alternative backup superblocks # fsck –o b=32 /dev/rdsk/c0t0d0s7  Will retrieve the corrupted partition. # dd if=/dev/zero of=/dev/rdsk/c0d0s7 bs=512 count=32  It will corrupt the partition # df  Shows disk detail in blocks # df –k (in KB) # df –h  Displays disk allocation in MB & GB # df –e  Points only the number of files free # du –k  Displays disk use in KB # du –s  Displays only the summary in 512 bytes blocks. Using the s and k options together shows summary in KB # du –h /opt  Shows the disk usage by the directory # quot –a  Reports on all mounted file systems # quot –f  Include the number of files # quot –h /export/home  Shows disk usage userwise in the particular directory Module – 4  Mounts & Unmounts # mount  Lists all of the mounted FS in the /etc/mnttab file VFSTAB  Virtual File System Tab /etc/vfstab device to mount device to fsck mount point FS type fsck pass mount at boot mount options  /etc/mnttab file is an mntfs file that provides read-only info about mounted FS on the local host  The /etc/vfstab file lists all the FS to be automatically mounted at system boot time, with the exception of the /etc/mnttab and /var/run FS # mount /dev/dsk/c0t0d0s7 /export/home Mount Options : read/write, setuid, intr, nologging and largefiles, xattr and onerror. # mount –o option,option,… device_name mount_point # mount -o ro /dev/dsk/c0d0s7 /p3  Mount the partition read only. # mount –o ro,nosuid /dev/dsk/c0t0d0s7 /export/home  Prohibit execution of setuid pgm. In solaris 2GB is the large file limit. Use of nolargefiles option fails if the FS to be mounted contains large files. # mount -o nolargefiles,noatime /dev/dsk/c0d0s7 /p3 nolargefiles  Won’t allow large files in this partition noatime  Modification time stamp won’t get updated. # mountall  Mounted local FS listed in the /etc/vfstab file # mountall –l  If any FS has entry in the fsck pass field as – or 0 then it will get mounted without fsck checking. Otherwise fsck carried out before mounting # fstype /dev/rdsk/c0t0d0s7  To know the FS type # mount –F hsfs –o ro /dev/dsk/c0t6d0s0 /cdrom  To mount CD-Drive # mount –F pcfs /dev/diskette /pcfs # umount /export/home or umount /dev/dsk/c0t0d0s7 # umountall  Will unmount local FS listed in /etc/mnttab except /, /usr, /proc, /dev/fd, /var, /var/run & /tmp # umountall –l  To verify the FS listed in the /etc/mnttab # fuser –c /p3  Will show the process running on the partition # fuser –ck /p3  Will kill the user processes # umount –f /p3  Force the partition to unmount # TERM=sun # export TERM  Executes this 2 command to enable the VI editor to work properly # ps –ef | grep vold Vold is the daemon taking care of auto mounting CD-Rom. # volcheck  Will check any media present in CD-Rom or Floppy drive # /floppy/floppy0  Floppy get mounted here automatically # /cdrom/cdrom0  CD-Rom get mounted here automatically # /etc/init.d/volmgt stop (or) start # eject cdrom  Will eject the CD-Rom if the vold is running # fdformat –t dos /dev/rdiskette  To format a floppy with DOS mode # fdformat  To format the floppy in Solaris Format. Module – 5  Installation Solaris 9 OE Installation and Upgrade options Solaris suninstall program Solaris Web Start Installation software Custom Jumpstart procedure Solaris Web Start Flash Installation Standard upgrade Solaris Live Upgrade method # grep METACLUSTER /var/sadm/system/admin/.clustertoc  To know cluster config # cat /var/sadm/system/admin/CLUSTER  To know the installed cluster config CLUSTER=SUNWCXall Module – 6  Package Administrtaion /var/sadm/install/contents file has all the details about installed packages. # grep showrev /var/sadm/install/contents  Will show whether showrev package is installed or not  /var/sadm/pkg directory maintains a record of all installed packages # pkginfo | more  Will show all installed packages # pkginfo –l SUNWman  Shows information about SUNWman package # pkginfo –d /cdrom/cdrom0/s0/Solaris_9/Product | more  To view info about pkg in CD # pkgadd –d /cdrom/cdrom0/Solaris_9/Product SUNWxip  # pkgchk SUNWman  If the pkgchk command doesn’t display a message, it indicates the package was installed successfully # pkgchk –v SUNWzip  To list the files contained in a software package # pkgchk –p /etc/shadow  To determine if the contents and attributes of a file have changed since it was installed with its software package # pkgchk –l SUNWman  Lists info about selected diles that make up a package # pkgrm SUNWzip  Will remove the SUNWzip package # pkgadd –d /cdrom/cdrom0/Solaris_9/Product –s spool SUNWzip It will dump the SUNWzip package to /var/spool/pkg folder. Alternate path can be given instead of spool like /pkg etc., # pkgrm –s spool SUNWman  Will delete the dumped SUNWman package from spool directory # admintool &  Tool (GUI) used to add users, printers, groups, softwares etc., # prodreg &  Tool (GUI) to view installed packages as well as to install & uninstall packages. Module – 7  Managing Software Patches Solaris9/PatchReport A summary of all patches for the solaris 9 OE release 9_Recommended.README Instruction for how to intall the recommended patch. # showrev –p (or) # patchadd –p  Will show installed patches  /var/sadm/patch - Info about all patches that are currently installed. Patch Name 6 digit number-revision number (117753-01) # /usr/bin/zcat 105050-01.tar.z | tar xvf - # cd /var/tmp # patchadd 105050-01  Will add patch  When you remove a patch, the patchrm command restores all files that were modified or replaced by that patch, unless  The patch was installed with the patchadd –d option (Which instructs the patchadd command not to save copies of files being updated or replaced)  The patch is required by the another patch  The patch has been obsoleted by a later patch # patchrm 105050-01  Will remove patch Installing Patch Cluster # cd 9_Recommended # ./install_cluster  /var/sadm/install_data/Solaris_9_Recommended_log Module – 8  Executing Boot PROM Commands # /usr/platform/’uname –m’/sbin/prtdiag –v  To know the OpenBoot version Stop+D  Press this keys when system power is turned ON to switch to diagnostic mode This key sequence is not available on a serial port terminal Stop+N  Press while the system is turned ON to set the NVRAM parameters to default Stop+A  To get into boot PROM  /etc/default/kbd - Remove the comment for the line KEYBOARD_ABORT=disable to turn off Stop+A function inside OS. Then issue the command kbd –I ok go  To comeout of PROM prompt ok banner  Shows system configuration ok printenv  Shows all variables ok reset-all  Will save the changes and clear the buffer & reboot the system ok .registers  Displays the contents of the registers ok show-devs  Shows all device with physical path ok devalias  Shows currently available devices  In sparc if we change values. There is no option to come out without saving. ok probe-ide  Shows ide details and device connected ok probe-scsi  Shows scsi details and device connected ok probe-scsi-all  Identifies devices on all all SCSI buses ok probe-fcal-all  Identifies devices on all fibre channel loops ok nvalias /pci@if,...................... ok nvunalias  To delete alias name ok show-disks  Desplays and allows a selection of device paths ok show-ttys ok show-displays ok show-nets ok show-tapes ok help  Shows list of help ok help floppy eject ok test  Runs self-test on specified systems ok sync  Manually attempts to flush memory and synchronize FS ok boot  Boot the system ok boot –r  Detect new devices (Reconfiguration boot) ok boot –s  Single user mode ok boot –v  Verbose mode – boot the system and shows the background details ok boot –a  Interactive mode. Prompt user for user input for all the process at boot time ok boot –rv (or) –sv ok printenv auto-boot? auto-boot?=false ok printenv boot-device  To know the variable details boot-device=disk ok setenv auto-boot? True  To change value to true for “auto-boot?” variable auto-boot?=true ok printenv diag-switch? Diag-switch?=false ok setenv diag-switch? True ok set-defaults  Reset all settings to factory default ok setenv boot-device disk cdrom net ok set-default boot-device  Will reset the default value of boot-device variable ok power-off  Will switch off the system immediately Inside OS # eeprom  Equivalent to printenv # eeprom auto-boot Auto-boot?=true # eeprom auto-boot?=false # eeprom diag-switch?=true Module – 9  Performing Boot and Shutdown Procedures Run Levels 0  ok mode s or S Solaris OE single user mode with critical FS mounted 1  Single user administrative state with access to all FS available 2  Multiuser can access the system . All sys daemons are running except NFS 3  Multiuser operations with NFS & N/W resource available 4  Reserved 5  Poweroff 6  Reboot # who –r  Shows current run level Boot Sequence 1. Boot PROM phase 2. Boot program phase 3. Kernel initialization phase 4. init phase /etc/inittab  id(S3) rstat(3) action(wait) Contains details about init levels /etc/vfstab /etc/inittab /etc/system  Important Files /etc/system  moddir root device and root FS config exclude forceload set  Always make a copy of /etc/system file before you edit the same. In case of problem , issue the interactive boot command : boot –a. When prompting for system file. Enter the path of backup file for /dev/null for a null configuration file. /etc/init.d  Directory contains many process or services like volume management /sbin  Each run level has an associated rc scripts located in this directory (eg /sbin/rc0) The RC scripts rc0, rc5 & rc6 are hard linked to each other. Run control scripts are located in /etc/init.d directory and these files are hard-linked to corresponding run control sctipts in the .etc.rc#.d directories. Creating New Run Control Scripts Create the script in the /etc/init.d directory and create links in the appropriate /etc/rc#.d directory for the run level in which the service is to be started and stop. # vi /etc/init.d/filename # chmod 744 /etc/init.d/filename # chgrp sys /etc/init.d/filename # cd /etc/init.d # ln filename /etc/rc#.d/S##filename # ln filename /etc/rc#.d/K##filename # /etc/init.d/filename start  To test the filename # init 2  Switch the run level to 2 # shutdown  Will moves to maintenance mode # shutdown –y –g300 –i6 “The system is being rebooted”  Reboots after 300 seconds. Default is 60 sec # shutdown –i0 (or) i5 (or) –i6 # halt  Shutdown the system immediately to ok prompt # poweroff  Equivalent to init5 # reboot  Equivalent to init6  These 3 commands won’t ececute rc0 kill scripts. Module – 10  Performing User Administration /etc/passwd  7 fields loginID:x:UID:GID:comment:home_dir:login_shell 0 - 99 UID  Reserved system user accounts 100 – 60000  UID for users range 0  Root 60001  Reserved for the nobody account 60002  Reserved for noaccess account  To generate error message 65534  nobody4 The anoynomous user account /etc/shadow  9 fields loginID:password:lastchg:min:max:warn:inactive:expire:reserved /etc/group  groupname:group-pwd:GID:user-list /etc/default/passwd  Set values for the following parameters MAXWEEKS MINWEEKS PASSLENGTH(valid entries are 6,7 & 8) WARNWEEKS 1970 –-> V4 1986  Sun released first OS (sunos1.0) # useradd –u –g –G GID,GID,.. –d /export/home/user300 –m –s /bin/ksh –c “Regular User” user300 # passwd user300 # useradd –d /export/home/user305 –m user305 # useradd user306 # usermod [-u uid [-o]] [-g gid] [-G gid] [-d dir] [-m] [-s shell] [-c comment] [-l newloginname] loginname # usermod –l –d /export/home/ –m # usermod –u user301  Change uid to 905 # usermod –s /bin/csh user301 # userdel user301  Delete the user account not the home dir # userdel –r user301  Delete user id & home dir # groupadd [-g gid [-o]] groupname # groupadd –g # groupmod [-g gid [-o]] [-n name] groupname # groupmod –n # groupmod –g 400 class  Change GID to 400 for the group class # groupdel group1 /etc/profile  The Bourne, Korn and BASH shells execute this initialization file /etc/.login  The C shell looks for and executes this initialization file during logon. There are no default global initialization files for the Z or TC shells Bourne /etc/profile $HOME/.profile /bin/sh /etc/skel/local.profile Korn /etc/profile $HOME/.profile /bin/ksh /etc/skel/local.profile $HOME/.kshrc C /etc/.login $HOME/.cshrc /bin/csh /etc/skel/local.cshrc $HOME/.login /etc/skell/local.login Setting Environment Variables Bourne or Korn shell VARIABLE=value; export VARIABLE For example: PS1=”$HOSTNAME”; export PS1 C setenv variable value For example: setenv LPDEST laserprinter # id user301  Shows UID of the user & primary group # id –a user301  Shows secondary group details also # groups user300  Shows the users groups # chown –R :grpname # pwconv  To sync passwd and shadow files. /etc/skel  Template files get copied once user id is created.  By default /etc/skel/.profile file don’t have any content. Profile Order /etc/motd file  Message of the day /etc/profile /$HOME/.profile Module – 11  Performing System Security # who  List of users currently logged in to the local system. The command refers /var/adm/utmpx to obtain information # who –m  Info about only the current terminal window # rusers -l  Displays a list of the users logged in on local and remote hosts. # finger –m usera  Displays info about the user and host name of user login session # last  Displays a record of all logins and logouts (/var/adm/wtmpx) # last –n 5 reboot  To view the last five system reboot times only Recording Failed Login Attempts # touch /var/adm/loginlog  File to log incorrect login. If a user tries to login 5 times (default) with wrong password a entry is created here. # chown root:sys /var/adm/loginlog # chmod 600 /var/adm/loginlog # /usr/ucb/whoami  Current login name # who am i  Login name of the original user Monitoring su Attempts /etc/default/su  File monitoring su login info CONSOLE VARIABLE # CONSOLE=/dev/console  Remove the comment (#) symbol. So that root can login remotely by su command. SULOG VARIABLE SULOG=/var/adm/sulog  Specifies the file location of the log file Controlling System Access # /etc/default/login file CONSOLE=/dev/console  This line should be commented to login as root from remote system PASSREQ=YES  Enforces that each user should have password to login /etc/ftpd/ftpusers  Lists names of users prohibited from connecting to system through FTP /etc/ftpusers  Solaris 8 /etc/hosts.equiv & $HOME/.rhosts  Files to determine if a remote user is allowed to access the local host, with the identity of a local user. This procedure first check /etc/hosts.equiv and then $HOME/.rhosts hostname hostname username + If a uses local host’s /etc/hosts.equiv file contains the host name ofa a remote host, then all regular users of that remote host are trusted and do not need to supply a password to login to the local host. Wherease the /rhosts file applies to a specific user /etc/inetd.conf  File used to control all services # svcadm disable (or) enable ftp (or) telnet  in solaris 10 # rsh 140.40.40.151 # rcp 140.40.40.151:/test/file1 .  To copy remote system file to local # rcp $HOME:/file1 140.40.40.151:/tmp  To copy local files to remote system # chown user2 file7  To change owner of a file # chown –R user2 dir4  To change ownership for folder and all its subfolders # chown user3:class file7  Changing both the individual and group ownership in one shot # chgrp class file4  To change the group ownership of a file or directory Setuid Permission on Executable Files When the setuid permission is set on an executable file, a user or process that runs this executable file is granted access based on the owner of the file. # ls –l /usr/bin/su _ rs r_xr_x 1 root sys …………. The setuid permission displays as an “s” in the owners executable field. You should disallow the use of setuid programs or at least restrict their use # chmod 4555  To set setuid permission on a executable. # find / -perm –4000  To search for setuid files Setgid Permission on Executable Files When the process runs, it runs as if it were a member of the same group in which the file is a member. Also access is granted based on the permission assigned to that group # ls –l /usr/bin/write _ r _ r_sr_x 1 root ………….  Displays as “s” in the group’s execute field # chmod 2555 # chmod g+s  To set setgid for a directory # find / -perm –2000  To search for setgid files Sticky Bit Permission on Public Directories If the directory permission have the sticky bit set, a file can be deleted only by the owner of the file/directory or the root user. # ls –ld /tmp drwxrwxrwt 6 root sys ……  Displays as “t” in the execute field for other. # chmod 1777 # find / -type d –perm –1000  To search for sticky bit directory Module – 12  Configuring Printer Services /etc/lp  Directory contains a hierarchy of LP server configuration directories and files /var/spool/lp  Directory contains a list of current requests that are in the print queue. /var/lp.logs  On going history of print requests /var/lp/logs/requests  Completed print request job $HOME/.printers file to set default printer (_default printername) /etc/printers.conf  Contains entry for printers # lpadmin –p printerB –c  Creating and adding printer class # lpadmin –p printerD –c bldg2  Adding printerD to bldg2 class # accept  To queuing print request # lpstat –t  To check the status of the new printer class # lp –d myfile  To print myfile to printer class # lpadmin –d printername (or) printer_classname  To set it as default # lpstat –d  To check the system’s default printer # lpadmin –d bldg2  To change the default printer # lpadmin –x printername  To remove a client’s printer configuration # /usr/sadm/admin/bin/printmgr &  Print Manager Removing a Server’s Printer Configuration # reject printerD  Stop queuing print requests # disable printerD  Stop the printer # lpadmin –x printerD  Delete the printer config from the /etc/lp/printers and /etc/printers.conf # /usr/lib/lpsched  Print services started # /etc/init.d/lp start  Starting by script # /usr/lib/lpshut  Stop print services # /etc/init.d/lp stop  Stopping by script Module – 13  Using Print Commands # /usr/bin/lp filename  Print to default printer # /usr/bin/lp –d printername filename # /usr/ucb/lpr filename # /usr/ucb/lpr –p printername filename LP Print Service Administration Command # /usr/sbin/accept printerD  Permits print requests to be queued # /usr/sbin/reject –r “Replacing cartridge” printerD  Stop queuing print requests # /usr/bin/enable printerD  Activates the specified printers # /usr/bin/disable  Deactivates the specified printers # lpmove printerC printerA  Moves print requests from one printerC to printerA # lpstat –o  Viewing print queue # lpstat –a printerA  To check whether it accepting print jobs # lpmove printerC –32 printerC –33 printerA  Moving individual print requests Module – 14  Controlling System Processes # /usr/dt/bin/sdtprocess &  GUI tool for process monitoring # prstat  Displays info about active process (5 sec refresh interval) Options for prstat command -c . Continuously prints new reports below previous reports -n nproc  Restricts the number of output lines -p pidlist  Reports only on process that have PID -t  Reports total usage summary for each users -u euidlist  Reports only processes that have an EUID in the given list -U uidlist  Reports only processes that have a real UID in the given list # kill –signal PID # pkill –signal process # pgrep –l mail  To know PID # pkill sendmail  To kill sendmail process # ps –e | grep mail  To know PID # kill 314  To kill mail process # kill signal PID PID PID # pkill signal process process Default signal is 15 1 SIGHUP Hnagup  Stop & start with the same pid 2 SIGNT Interrupt  9 SIGKILL Kill  Kill forcibly 15 SIGTERM Terminate  Kill properly # pkill -1 (or) –HUP sendmail # kill –SIGTERM (or) -15 # kill –SIGKILL (or) -9 # kill –SIGHUP (or) -1 (or) –HUP # renice –n -10 195  To change priority -20  Highest priority for a process 0  Neutral priority +20  Least priority # psrinfo  shows how long the system is running # ps –e  Shows all system process # ps –ef  Default process details with command or service name # ps –ef | grep cron  To view specific process # at 9:00 pm at> find /export/home/user2 –name core rm {} \; at> Ctrl+D # at now at> banner “welcome” > /dev/pts/4 at> ctrl+d # # at –l 1016078400.a  Reports jobs schedule # atq  Shows the at jobs queue # ls –l /var/spool/cron/atjobs  Directory contains the at jobs # at –r 1016078400.a  To remove the at job /etc/cron.d/at.deny  We can add username to this file to deny access to at jobs /etc/cron.d/at.allow  We can add username to this file to allow access to at jobs If neither file at.allow & at.deny file does not exist only the root user can use the at command. Crontab File Format 0-59 0-23 1-31 1-12 1-7 Min Hour Date Month Days # crontab –l  View content of user crontab file # crontab –e  Editing the file 30 17 * * 5 /usr/bin/banner “Time to go!” > /dev/console # crontab –r username  Remove a crontab file /etc/cron.d/cron.deny  Users in this file will deny access to use crontab command /etc/cron.d/cron.allow  Users in this file will allow access to use crontab command If we type only crontab as the command. It will go to process so if we press Ctrl+c then it won’t save the file but existing data will be present. When we press Ctrl+D then all the content will get deleted. # crontab /root_cron  To use a backup file for cron jobs. # /etc/init.d/cron stop (or) start # /var/spool/cron/crontabs  Directory where users crontab schedule files are getting stored. # /var/spool/cron/atjobs  Directory where AT jobs get saved # svcadm enable (or) disable cron Module – 15  Performing File System Backups /dev/rmt/#hn  h – Tape Density (l,m,h,c,u) n – no rewind mt –f tape-device-name command count mt status  Displays status info about the drive mt offline  Rewind the tape and if appropriate takes the drive unit offline mt rewind  Rewinds the tape mt fsf count  Moves the tape forward count records # mt –f /dev/rmt/0n fsf 2  Positions the tape at the beginning of the third tape record Level 0 Monthly M T W Th F 3 4 5 6 2 3 4 5 6 2 3 4 5 6 2 /etc/dumpdates  Each line shows the FS that was backed up and the level of the last backup. Also shows the date, and the time of the backup (eg) /dev/rdsk/c0t2d0s6 0 fri jan 4 19:12:27 2005 When an incremental backup is performed the ufsdump command consults the /etc/dumpdates file. It looks for the date of the next lower level backup. Then the ufsdump command copies to the backup media all of the files that were modified or added since the date of that lower-level backup. When the backup is complete, the /etc/dumpdates file records a new wntry that describes this backup. The new entry replaces the entry for the previous backup at that level Options for the ufsdump command 0.9 Backup levels v Verify, After the tape is written for any discrepancies occur s Size estimate l Autoload, you use this option with an autoloading tape drive o Offline, When the backup is complete. Takes offline, rewinds, and if possible eject u Updates the /etc/dumpdates file n Notify. Sends messages to the logged-in users terminals who are member of sys group f device Specify the device Tape Backup Become root user, switch to single user mode, and unmount the FS # /usr/sbin/shutdown –y –g300 “System is being shutdown for backup” # umount /export/home # fsck /dev/rdsk/c0t0d0s7 # ufsdump 0uf /dev/rmt/0 /dev/rdsk/c0t0d0s7 Remote Backups To perform remote backups across the network, the system with tape drive must have an entry in its /.rhosts file for every system that uses the tape drive # ufsdump 0uf host2:/dev/rmt/0 /export/home Module – 16  Performing File System restores The ufsrestore command copies files to the disk, relative to the current working directory from backup tapes that were created by the ufsdump command. Options for the ufsrestore Command t Lists the table of the backup media r Restores the entire FS from the backup media x file1 file2 Restores only the files named on the command line i Invokes an interactive restore v Specifies verbose mode. Displays details of the restore operation on the screen f device Specifies the tape drive name restoresymtable  System creates this file when you restore an entire FS. The ufsrestore command uses this file for check=printing or passing information between incremental restores. You can remove this file when the restore is complete. Restoring the /opt FS # newfs /dev/rdsk/c0t0d0s5 # mount /dev/dsk/c0t0d0s5 /opt # cd /opt # ufsrestore rf /dev/rmt/0 # rm restoresymtable # cd / # umount /opt # fsck /dev/rdsk/c0t0d0s5 # ufsdump 0uf /dev/rmt/0 /dev/rdsk/c0t0d0s5 Always restore a FS by starting with the level 0 backup tape, continue with the next lower level tape and continue through the highest level tape. Restoring /usr FS ok boot cdrom –s # newfs /dev/rdsk/c0t0d0s6 # mount /dev/dsk/c0t0d0s6 /a # cd /a # ufsrestore rf /dev/rmt/0 # rm restoresymtable # cd / # umount /a # fsck /dev/rdsk/c0t0d0s6 # ufsdump 0uf /dev/rmt/0 /dev/rdsk/c0t0d0s6 # init 6 Performing a special case Recovery of the /(root) FS ok boot cdrom -s # newfs /dev/rdsk/c0t0d0s0 # mount /dev/dsk/c0t0d0s0 /a # cd /a # ufsrestore rf /dev/rmt/0 # rm restoresymtable # cd /usr/platform/’uname –m’/lib/fs/ufs # installboot bookblk /dev/rdsk/c0t0d0s0 # cd / # umount /a # fsck /dev/rdsk/c0t0d0s0 # ufsdump 0uf /dev/rmt/0 /dev/rdsk/c0t0d0s0 # init 6 Invoking an Interactive Restore # cd /var/tmp # ufsrestore ivf /dev/rmt/0 ufsrestore> ls  Display the contents of the directory structure on the backup tape ufsrestore> cd directory1 ufsrestore> ls ufsrestore> add file1 file2  Add the files you want to be restore to the extraction list ufsrestore> delete file1  to delete a file from the extraction list ufsrestore> marked  To view the marked extraction files ufsrestore> extract  To restore the selected files from the backup tape The ufsrestore command has to find the selected files. If you used more than one type for the backup, first insert the tape with the highest volume number and type the appropriate number at this point. Set directory mde, owner, and times Set owner/mode for ‘.’?[yn] n  Answering y sets ownership and permission of the temp directory to those of the directory structure on the tape ufsrestore> quit Move/copy the restored files to their original or permanent directory and delete from the temp directory Performing an Incremental Restore Always start with the last volume and towards the first. The system uses info in the restoresymtable file to restore incremental backups on top of the latest full backup. # more /etc/dumpdates | grep c0t0d0s7 # newfs /dev/rdsk/c0t0d0s7 # mount /dev/dsk/c0t0d0s7 /export/home # cd /export/home # ufsrestore rvf /dev/rmt/0 Load the next lower level tape into the tape drive and issue the following command # ufsrestore rvf /dev/rmt/0 Alternate Steps (5 & 6) # ufsrestore iv /dev/rmt/0 ufsrestore> ls ufsrestore> add * ufsrestore> extract ufsrestore> q Load the next tape and perform the below operation # ufsrestore iv ufsrestore> ls ufsrestore> add* ufsrestore> extract ufsrestore> q Module – 17  Backup up a Mounted FS with a UFS Snapshot /usr/sbin/fssnap –F FsType –V –o special-options(s) mount-point | special Options for the fssnap command -d Deletes the snapshots associated with the given FS. If –o unlink option was used when you built the snapshot, the backing store file is deleted together otherwise it has to be deleted manually -F FsType Specifies the FS type to be used -i Displays the state of an FSType snapshot -v Echos the complete command line, but does not execute the command -o Enables you to use special options. Such as the location & size of bs file # fssnap –F ufs –o bs=backing_store_path /file_system # fssnap –F ufs –o bs=/var/tmp /export/home /dev/fssnap/0 backing store file  The snapshot subsystem saves FS data in this file. The fssnap command creates the backing-store file and two read-only virtual devices. The block virtual device, /dev/fssnap/0, can be mounted as a read-only FS. The raw virtual device, /dev/rfssnap/0. You can limit the size of the backing-store file by using the –o maxsize=n option. If the backing-store file runs out of disk space, the system automatically deleted the ufs snapshot. # fssnap –F ufs –o bs=/var/tmp,maxsize=500m /export/home # fssnap –I  Displays a list of all the current UFS snapshots on the system 0 /export/home 1 /usr 2 /database # /usr/lib/fs/ufs/fssnap –I /export/home  Shows the details for the /export/home snapshot Performing a backup of a UFS Snapshot # mkdir –p /backups/home.bkp  Creating an empty directory # mount –F ufs –o ro /dev/fssnap/0 /backups/home.bkp  Mounting the block virtual device # cd /backups/home.bkp # tar cvf /dev/rmt/0 (or) # ufsdump 0uf /dev/rmt/0 /dev/rfssnap/0 # ufsrestore tf /dev/rmt/0  To verify Performing an Incremental Backup of a UFS Snapshot Use ufsdump with the N option to create an incremental UFS snapshot. Which writes the name of the device being backed up, rather than the name of the snapshot device to the /etc/dumpdates file # ufsdump 1ufN /dev/rmt/0 /dev/rdsk/c1t0d0s0 /dev/rfssnap/0 # ufsrestore tf /dev/rmt/0  To verify # fssnap –d /extra(Source FS)  To remove a snapshot # rm /var/tmp/snapshot0 Restoring Data from a UFS Snapshot Backup The backup created from a virtual device is a backup of the original FS when the UFS snapshot was taken. You can restore a UFS snapshot from a backup tape in the same manner as you would the backup of an original FS # cd /usr # ufsrestore if /dev/rmt/0 ufsrestore> add demo ufsrestore> extract ufsrestore> quit Deleting a UFS Snapshot # umount /dev/fssnap/0 # fssnap 0d /export/home # rm /backing_store_file Module – 1  Describing Interface Configuration To know MAC Address of NIC Card ok banner # ifconfig –a 8:0:20:93:c9….  Sun manufacturing NIC card Hme0 qfe0 eri0 leo0 Sun NIC card types # ifconfig hme0 down  To down the NIC # ifconfig hme0 up  To up the NIC # ping –s 140.40.0.123  Continuous pinging # snoop  To display incoming & outgoing packets. Press Ctrl+c to stop the snoop utility # snoop IP1 IP2  To capture communication between two systems # snoop –a dhcp  To turn on audible clicks for all network traffic related to a dhcp boot # snoop –V  Summary verbose output # snoop –v  Detailed verbose output # snoop –o filename  Redirects the snoop utility output to filename in summary mode # snoop –i filename  Displays packets that were previously captured in filename /etc/hosts  Link file to /etc/inet/hosts /etc/inet/hosts  Should contain IP & hostname  32 virtual interdace is possible  Hme0:1 hmeo:2 ….. hme0:32 Configuring IPv4 Interfaces at Boot Time /etc/rcS.d/S30network.sh - file # cat /etc/hostname.hme0 Sys41 (or) 192.168.30.41 # cat /etc/inet/hosts 192.168.30.41 sys41 plumb  To sync the IP and the config files Changing the System Hostname /etc/nodename  File to change hostname /etc/hostname.xxn /etc/inet/hosts /etc/net/tictls/hosts /etc/net/ticots/hosts /etc/net/ticotsord/hosts The /etc/net/tic* directories contains a host file. These files contain config info for transport independent network services. If these files become corrupted, unpredictable results can occur. # sys-unconfig  For total reconfiguration Module – 2  Describing the Client Server Model inetd  (Internet Service Daemon) Responsible for On-Demand services eg. Telnetd, ftpd /etc/inetd.conf  Config file for inetd daemon To turn-off a service, add a symbol to the beginning of the corresponding to that service in the /etc/inet.conf file, and send a HUP request. # pkill –HUP inetd  Restarting the inetd services /etc/inet/services  Services file /etc/inet/protocols  Registered protocols are listed here Network Ports  Well-known ports & ephemeral (short-lived) ports Port Assignment  Central Authority (Well-known) & Dynamic Binding (ephemeral) Central Authority Ports  0 – 1024 Dynamic Binding  1024 – 65000 Starting Services that use a Well-Known Port 1. Services that start by default at system boot time (eg. Sendmail) 2. Services start on-demand (eg. telnet) Starting RPC Services 1. Services that start by default at system boot time 2. Services start on-demand The rpcbind process (Daemon) associates RPC program numbers with port numbers. /etc/rc2.d/S71rpc script initializes the rpcbind service (port 111) rpcbind - 111 port number - Resposible for rpc services /etc/rpc  Config file for rpc services # grep rpcbind /etc/services sunrpc 111/udp rpcbind sunrpc 111/tcp rpcbind # rpcinfo –p  rpcbind information Prog No Version Protocol Port Service Name # rpcinfo –d 1002(Prog No) 1(Version)  Deleting RPC service registration Module – 3  Customizing the SMC # /etc/init.d/init.wbem status (or) stop (or) start  SMC Service (port 898) # smc  Starting the console # smc edit  Starting the toolbox editor http://hostname:898/toolboxes/smc/smc.tbx Module – 4  Managing swap configuration Virtual Memory = RAM + Disk Space Swap Slice | Swap File | RAM } Swap Space # swap –s  Summary of virtual swap space # swap –l  Lists the details of systems physical swap (eg. Swap file) Adding Swap Space # vi /etc/vfstab /dev/dsk/c1t0d0s3 - - swap - no - # swap –a /dev/dsk/c1t0d0s3  To add swap space from HDD slice. Adding Swap File # mkfile 20m /export/data/swapfile  Swap file allocation # swap –a /export.data.swapfile # swap –l  To list the details of the modified system swap space # swap –s  List a summary of the modified system swap space # vi /etc/vfstab /export/data/swapfile - - swap - no - Removing Swap Space # swap –d /dev/dsk/c1t0d0s3  Also remove entry from vfstab Removing Swap File # swap –d /export/data/swapfile # rm /export/data/swapfile  Also remove entry from vfstab Module – 5  Managing Crash Dumps & Core Files When an OS has a fatal error, it generates a crash dump file (crash dump). When a process has a fatal error, it generates a core file. If the Solaris OE kernel encounters a problem or when an unexpected hardware fault occurs, the panic routine is executed. Where memory contents are copied to a disk partition defined as a dump device. When an OS crashes, the savecore command is automatically executed during a boot. The savecore command retrieves the crash dump from the dump device and the writes the crash dump to a pair of files in your FS. It places kernel core info in the /var/crash/nodename/vmcore.X file It places name list info & table info in the /var/crash/nodename/unix.X file By default, the dump device is a swap partition. The swap partition contains temp data, therefore permanent data is overwritten by the crash dump. # dumpadm  To view the current dump configuration Dump Content : Kernel pages (or) Application Pages (or) All Dump device : /dev/dsk/c0t0d0s1 (swap) Savecore directory : /var/crash/host1 Savecore enabled : yes # cat /etc/dumpadm.conf  Content of dumpadm command Changing the Crash Dump configuration /usr/sbin/dumpadm [-nuy] [-c content-type] [-d dump-device] [-m mink | minm \ min%] [-r root-dir] [-s savecore-dir] -n Modifies the dump config so it does not run the savecore command automatically on reboot -u Forcibly updates the kernel dump config based on the contents of /etc/dumpadm.conf -y Modifies the dump config so that the savecore command is run automatically on reboot. This is default -c content-type The content type can be kernel, all, or curproc. The curproc includes the kernel, memoty pages and the memory page of the currently executing process -d dump-device The dump device cab be an absolute path of swap -m mink | minm | min% Creates a minfree file in the current savecore-dir -r root-dir Specifies an alternative root directory relative to which dumpadm command should create files. The default root dir “/” is used. -s savecore-dir To mention savefiles dir. The default is /var/crash/hostname Managing Core File Behavior A core file is a point-in-time copy (snapshot) of the RAM allocated to a process. The copy is written to a more permanent medium, such as a HDD. A core file is useful in analyzing why a particular program crashed. When a core file occurs, the OS generated two possible copies of the core files, one copy known as the global core file and the other copy known as per process core file. All depends on options in effect. Global core file is created in mode 600 and is owned by the superuser. Ordinary per-process core files are created in mode 600 under the credentials of the process. # coreadm  Displays the currnet core file config global core file pattern :  Identifies the name to use for core files placed in global directory init core file pattern : core  Identified the default name that per-process core files must use global core dumps : disabled  Indicates global core files are disabled per-process core dumps : enabled global setid core dumps : disabled per-process setid core dumps : disabled global core dump logging : disabled # cat /etc/coreadm.conf  Content of coreadm command You can enable or disable two configurable core file paths, per-process and global, separately. If a global core file path is enabled and set to /corefiles/core, for eg. Then each process that terminates abnormally produces two core files: One in the current working directory, and one in the /corefiles/core directory. coreadm [-p pattern] [pid]……….  Users can run this command coreadm [-g pattern] [-I pattern] [-d option……] [-e option…..]  only root user can run -i pattern Sets the per-process core file name pattern from init to pattern -e option Enables the specified core file option global Enables core dumps by using the global core pattern process Enables core dumps by using the per-process core pattern global-setid Enables setid core dump by using the global core pattern proc-setid Enables setid core dumps by using the per-process core pattern log Generates a syslog (3) message when a user attempts to generate a global core file -d option Disables the specified core file option. See the –e option for possible options -u Updates system-wide core file options from the config file /etc/coreadm.conf. -g pattern Sets the global core file name pattern to pattern. The pattern must start with a / -p pattern Sets the per-process core file name pattern to pattern. Pattern options for the coreadm Command %p PID %u EUID %g EGID %f Executable file name %n System node name (uname –n) %m Machine hardware name (uname –m) %t The time in seconds since midnight jan 1 1970 %% Literal % # coreadm –p core.%f.%p $$  When executed from a users $HOME/.profile (or) .login file sets the core file name pattern for all processes run during the login session. The $$ variable is the PID of the currently running shell. The per-process core file name pattern is inherited by all child processes. # coreadm –p $HOME/corefiles/%n.%f.%p $$  This command places all of the user’s core files into the corefiles subdirectory of users home directory, differentiated by the system node name. # coreadm –g /var/core/core.%f.%p –e global  This sets system-wide parameters that add the executable filename and PID to the name of any core file that is created. # coreadm  to verify that this parameter is now part of the core file configuration # coreadm 278 5678  Search for the core dump file. Only the owner of a process or the superuser can query a process by using the coreadm command with a list of PIDs. Module – 6  Configuring NFS NFS Server Files /etc/dfs/dfstab Lists the local resources to share at boot time /etc/dfs/sharetab Lists the local resources currently being shared. /etc/dfs/fstypes Lists the default FS types for remote FS /etc/rmtab Lists FS remotely mounted by NFS clients /etc/nfs/nfslog.conf Lists info of the location of config logs used for NFS server logging /etc/default/nfslogd Lists config info describing the behavior of the nfslogd daemon # cat /etc/dfs/dfstab share –F nfs –o ro /export.sys44_data # cat /etc/dfs/sharetab /export/sys44_data - nfs ro # cat /etc/dfs/fstypes nfs NFS Utilities autofs AUTOFS Utilities cachefs CACHEFS Utilities # cat /etc/rmtab sys42:/export/sys44-data #sys41:/usr/share/man #sys43:/export/sys44_data  The # entries are removed by the mountd daemon during a system startup NFS Server Daemons To start the NFS server daemons or to specify the number of concurrent NFS requests that can be handled by the nfsd daemon, use the /etc/rc3.d/S15nfs.server script mountd Handles FS mount requests from remote systems, and provides access control nfsd Handles client FS requests statd Works with the lockd daemon to provide crash recovery functions for the lock manager lockd Supports record locking operations on NFS files nfslogd Provides operational logging # /etc/init.d/nfs.server start  To start NFS server daemon # /etc/init.d/nfs.server stop  To stop NFS server daemon NFS Server Commands # share  To share directory and also displays the contents of the /etc/dfs/sharetab file # unshare /test  Unshare the share # shareall  Shares all resources listed in the /etc/dfs/dfstab file # unshareall /export/sys44_data  Unshare currently shared file resources listed in the /etc/dfs/sharetab file # dfshares  Displays currently shared resources by using the NFS dameon mountd # dfshares 140.40.40.160  Lists available shared resources in remote system # dfmounts  Displays a list of NFS resources that are currently mounted and client list # dfmounts sys42  Displays NFS resources of sys42 that are currently mounted & clients share [-F nfs] [-o options] [-d description] [pathname] # share –o ro /export/sys44_data  By default resources available with RW. Access decision is based on a comparison of the UID of the client and the owner. The Share Command Options ro Informs clients that the server accepts only read requests rw Allows the server to accept read and write requests from the client root=client Informs client that the root user on the specified client system or systems can perform superuser-privileged requests on the share resource. ro=access-list Allows read requests from the specified access list rw=access-list Allows RW requests from the specified access list Access List Options access-list=client:client Allows access based on a colon-separated list of clients access-list=@network Allows access based on a network number (eg @192.168.100 or a network name eg. @mynet.com). The network name must be defined in the /etc/networks file access-list=.domain Allows access based on a DNS domain access-list=netgroup_name Allows access based on a config net group (NIS) or (NIS+) anon=n Sets n to be the effective user ID (EUID) of anonymous users. By default, anonumous users are given the EUID 6001-nobody user. If n is set to –1, access is denied. # share –F nfs –o r0 direcctory  Restricts access to read-only access. # share –F nfs –o r0,rw=client1 directory  Restricts access to read-only, however, the NFS server accepts both read & write requests from the client client1 # share –F nfs –o root=client2 directory  Allows the root user on the client named client2 to have superuser access to the NFS mounted resources # share –F nfs –o ro,anon=0 directory  By setting the option anon=0, the EUID for access to shared resources by an anonymous user is set to 0. The access is also set to read only. # share - /export/sys44_data ro “” Managing the NFS Client NFS Client Files /etc/vfstab Defines FS to be mounted locally /etc/mnttab Lists currently mounted FS including automounted directories. /etc/dfs/fstypes Lists the default FS types for remote FS NFS Client Daemons The NFS client daemons are started using the /etc/rc2.d/S73nfs.client script statd Works with the lockd daemon to provide crash recovery functions lockd Supports record-locking operations on NFS files /etc/init.d/nfs.client start (or) stop NFS Client Commands dfshares Lists available shared resources from a remote or local NFS server mount Attach a file resource to a specified local mount point umount Unmounts a currently mounted file resources mountall Mounts all file resources or a specified group of file resources listed in the /etc/vfstab file with a mount at boot value of yes umountall Unmounts all non-critical local and remote file resources dfmounts Displays a list of currently mounted NFS server directories mount [-F nfs] [-o options] server:pathname mount-point # mount sys44:/export/sys44_data /export/remote-data # mount –o ro sys45,sys43,sys41:/multi_home_data /remote_shared_data  When mounting a read-only remote resources, you can specify a comma separated list of sources for the remote resources. Which are then used as a list of failover resources # umount /export/remote-data  Unmounting remote FS from the client # mountall –r  To limit the action of this command to remote file resources. # umountall –r  To unmount all remote file systems Mounting Remote Resources at Boot Time Enter appropriate entries in the client’s /etc/vfstab file to mount the remote file resources at boot time. # vi /etc/vfstab sys44:/export/sys44_data - /export/remote-data nfs - yes soft,bg Mount Command Options rw | ro Read/Write or read-only. The default is read/write bg | fg Retry to mount in background or foreground. The default is to retry in the foreground soft | hard Soft option reports an error on the request, and stop trying when retrans=n reach. Whereas hard option prints a warning message and continue to try. Default is hard mount intr | nointr Enables or disabled the use of KB interrupts to kill aprocess that hangs on a hard-mounted FS. The default is intr. suid | nosuid Indicates whether to enable setuid execution. Default is setuid execution timeo=n Sets the timeout to n tenth of a second. The default timemout is 11, measures in one-tenth of a second for UDP and 600 tenths of a second for TCP. retry=n Sets the no of times to retry the mount operation. Default is 10,000 times retrans=n Sets the number of NFS retransmission to n. The default is 5 for UDP. Enabling the NFS Server Logging nfslogd daemon responsible for NFS logging The /etc/nfs/nfslog.conf file defines the path, file names, and type of logging that the nfslogd daemon must use. There is a taq corresponding to each definition. Eg. Of nfslog.conf file # NFS server log configuration file global defaultdir=/var/nfs \ log=nfslog fhtable=fhtable buffer=nfslog_workbuffer defaultdir=dir_path  Specifies the default parent directory log=logfile_pat  Specifies relative or absolute path and the filename for the ASCII log file fhtable=table_path  Specifies path and the filename for the file-handle-to-path DB file buffer=buffer_path  Specifies path and the filename for the raw buffer file log format=basic | extended  Specifies the format when creating user-redable log files To easily identify the log files for different shared resources, place them in separate dir. For eg. # cat /etc/nfs/nfslog.conf global defaultdir=/var/nfs \ log=nfslog fhtable=fhtable buffer=nfslog-workbuffer public defaultdir=/var/nfs/public \ log=nfslog fhtable=fhtable buffer=nfslog-workbuffer Create the /var/nfs/public directory before starting NFS server logging Specify a tag by entering the tag to use with the log=taq option in the /etc/dfs/dfstab file. Use the log option without specifying a taq, which mean use the default global tag share –F nfs –o ro,log /export/sys44_date /etc/default/nfslogd  The config info file controls the logging behavior of the nfslogd daemon. Module – 7  Configuring AutoFS The automount facility contains three components The AutoFS FS The automountd daemon The automount command The AutoFs map types Master Map The auto_master map associates a directory, also called a mount point, with a map. Direct Map Lists the mount points as absolute path names. This map explicitly indicates the mount point on the client. Indirect Map Lists the mount points as relative path names. This map uses a relative path to establish the mount point on the client. Special Provides access to NFS servers by using their host names # cat /etc/auto_master +auto_master /net -hosts -nosuid,nobrowse /home auto_home -nobrowse /xfn -xfn Syntax Mount point map name(direct or indirect map) mount options(similar to standard mount options. But nobrowse option is an AutoFS specific mount option The plus(+) symbol at th beginning of the +auto_maser line directs the automountd daemon to look at the NIS, NIS+, or LDAP databases before it reads the rest of the map. If this line is commented out, only the local files are searched unless the /etc/nsswitch.conf file specifies that NIS, NIS+, or LDAP should be searched. The two mount points for special maps are –hosts map & -xfn map The –hosts map Provide access to all resources shared by NFS servers. The resources being shared by a server are mounted below the /net/hostname directory, or if only the server’s IP address is known below the /net/IPaddress directory. The server doesn’t have to be listed in the hosts database for this mechanism to work. The –xfn map Provides access to resources acailable through the Federated Naming Service (FNS). Resources associated with FNS mount below the /xfn directory Direct Map # cat /etc/auto_master . . /- auto_direct -ro The /- mount point is a pointer that informs the automount facility that the full path names are defined in the file specified by map-name(the /etc/auto_direct file in this example) # cat /etc/auto_direct # Super User created direct map for automounter /apps/frame -ro,soft server1:/export/framemaker /opt/local -ro,soft server2:/export/unbundled /usr/share/man -ro,soft server3,server4:/usr/share/man Indirect Map The /home entry defines a mount point for an indirect map. The map auto_home list relative path names only. The Solaris 2.6 through Solaris 9 OE support browsing of indirect maps and special maps with the –browse option. The –nobrowse option disables the browsing of indirect maps. The default option is –browse # cat /etc/auto_home +auto_home steven hosts5:/export/home/steven mary mars:/export/home/marry Reducing the auto_home map to a single line * server1:/export/home/& The client remotely mont the /export/home/loginID directory from the NFS server server1 onto the local mount point /home/loginID. Wildcard character(*) to match any key. The substitution character (&) at the end of the location is replaced with the matched key field. Run the automount command when making changes to the master map or creating a direct map to make the changes effective. You do not have to stop and restart the automountd daemon after making changes to existing entries in a direct map. Automount [-t duration] [-v] -t Specifies a time in seconds, the FS remains mounted when not in use. Default is 600 sec. When to run the automount command Automount Map Run if entry is added/deleted Run if entry is modified Master map yes yes Direct map yes no Indirect map no no # cat /etc/mnttab -hosts /net autofs indirect,nosuid,ignore,nobrowse dev=4300001|1008255810 auto_home …………. -xfn …………. # /etc/init.d/autofs start (or) stop Module – 8 & 9  Solaris volume Mangement metadb –a [-f] [-c n] [-l nnnn] disk_slice -a Adds a stale database replica -f Force the creation of the initial replica, even if no replica exist. -c n Specifies the number of replicas to add to the slice -l nnnn Specifies the size of the new replica in blocks disk_slice Specifies the name of the disk_slice that will hold the replica # metadb –a –f c0t0d0s4 c0t0d0s5 c1t0d0s0 c1t0d0s1  To create metadb # metadb  Reports the status of all replicas RAID 0 Config # metainit d10(name d0-dn) 3(total disk/slice) 1 c0t1d0s0 1 c0t1d0s1 1 c0t1d0s3 # newfs /dev/md/rdsk/d10 # metaclear d10  Delete the volume # metainit d0(partition name) –p d10(volume name) 1000m  Creating partition # metattach d0 999m  To increase partition size # growfs –M /m1(mount point) /dev/md/rdsk/d0  To create FS for extra space added # metattach d10(volume) c0t1d0s4  To increase space for volume RAID 5 Config # metainit d20 –r(raid 5 option) c0t1d0s0 c0t1d0s1 c0t1d0s3 # metadb –d –f c0t1d0s7  To delete metadb RAID 1 Config # metainit d10 –m d0  To create mirror Then reboot # metattach d10 d1  Attaching another disk to mirror # metastat  To check the status of mirror disk Building a Mirror of the Root (/) File System metainit –f concat/stripe numstipes width components…… # metainit –f d0 1 1 c0t0d0s0 d0 concat/stripe is setup # metainit d1 1 1 c0t1d0s0 d1 concat/stripe is setup metainit mirror –m submirror [read_options] [write_options] [pass_num] read_options -g  Enables the geometric read option, which results in faster performance on sequential reads -r  Directs all reads to th first submirror. Use this option, when the devices that comprise the first submirror are substantially faster than those of the second mirror. You cannot use –r option with the –g option. If neither the –g nor –r options are specified, reads are made in a round-robin order from all submirros in the mirror. This process enables load balancing across the submirros. write_options S  Performs serial write to mirrors. The default setting for this option is parallel write Pass_num  A number (0-9) at the end of an entry defining a mirror that determines the order in which that mirror is resynchronized during a reboot. The default is 1. If 0 used resync is skipped. # metainit d10 –m d0 d10 : Mirror is setup # metaroot d10  Updates /etc/system file also /etc/vfstab # grep md /etc/vfstab /dev/md/dsk/d10 /dev/md/rdsk/d10 / ufs 1 no - The metaroot command also updates the /etc/system file to contain the forceload statement that loads the kernel modules that support the logical volumes. # tail /etc/system forceload : misc/md_hotspares forceload : misc/md_sp forceload : misc/md_stripe forceload : misc/md_mirro forceload : drv/pcipsy . . . rootdev:/pseudo /md@0.10.blk You must reboot the system before attaching the secondary submirror # init 6 # metattach d10 d1 d10: Submirror d1 is attached # ls –l /dev/dsk/c1t0d0s4 Record the path that follows the /devices directory: /pci@if,0/pci@1/scsi@4...................... ok nvalias backup_root /pci@if,0/pci@1/scsi@4,1/disk@2,0:b ok printenv boot-device boot-device=disk net ok setenv boot-device disk backup_root net boot-device=disk backup_root net ok boot backup_root  To test the secondary submirror Unmirroring the Root (/) File System # metastat d10  To verify that status of the mirror # metadetach d10 d1  To make a one-way mirror d10: submirror d1 is detached # metaroot /de/dsk/c0t0d0s0  To change entries in /etc/vfstab and /etc/system # init 6 # metaclear –r d10  To clear the mirror and submirror. The –r deletes metadevices d10: Mirror is cleared d0: Concat/Stripe is cleared # metaclear d1 d1: Concat/Stripe is cleared Module - 10  ACL entry-type:[UID or GID]:perm Introducing ACL Commands getfacl [-a] [-d] filename(s)  Displays ACL entries for files -a  Displays the filename, file owner, file group, and ACL entries for the specified file -d  Displays the filename, file owner, file group, and default ACL entries setfacl –m acl_entries filename  Creats or modify ACL entries on files setfacl –s acl_entries filename  Substitute new ACL entries for old ACL entries setfacl –d acl_entries filename  Deletes one or more ACL entries on files setfacl –f acl_file filename  Specifies an ACL configuration file that contain ACL entries to set on other files setfacl –r filename  Recalculate the ACL mask baed on the ACL entries. When used with –m or –s option $ ls –l _rw_r__r__+ 1 userc staf 0 Jan 2 13:40 file2  A plus sign appears for files contains ACL permission There are no effective permission listed for a file’s owner or “others’ users. However, the file’s group and any other specific users or groups present in the ACL list have effective permissions. When no ACL mask is specifically set o a file or directory, the ACL mask has the same permissions as the group permissions for that file or directory. $ getfacl file1  No ACL entries present file : file1 owner : userc group : sysadmin user::rw_ group::r__ # effective:r__ mask:r__ other:r__ $ getfacl file2  Custom ACLentry present file : file2 owner : userc group : sysadmin user::rw_ user::usera:rwx # effective:r__ group::r__ # effective:r__ mask:r__ other:r__ The effective permission shows which permissions are allowed. When you compute the intersection (a Boolean logical AND operation) of the ACL entry and the ACL mask. $ setfacl –m u:userb:7 file2  Set special permission to userb(username) $ getfacl file2 file : file2 owner : userc group : sysadmin user::rw_ user::usera:rwx # effective:r__ user:userb:rwx # effective:r__ group::r__ # effective:r__ mask:r__ other:r__ $ setfacl –d u:usera file2  Removing special permissions $ getfacl file2 file : file2 owner : userc group : sysadmin user::rw_ user:userb:rwx # effective:r__ group::r__ # effective:r__ mask:r__ other:r__ setfacl –s u::perm,g::perm,o:perm,m:perm,[u:UID:perm],[g:GID:perm] filename $ setfacl –s u::rwx,g::rw_,o:r__,m:rw_,u:usera:rwx file1 $ getfacl file1 file : file1 owner : userc group : sysadmin user::rwx user:usera:rwx # effective:rw_ group::rw_ # effective:rw_ mask:rw_ other:r__ $ setfacl –s u::7,g::6,0:4,m:6,u:usera:7 file2 $ setfacl –r –m u:usera:7 file1  Change the umask value as well as to the user(Recalculating an ACL mask) $ getfacl file1 file : file1 owner : userc group : sysadmin user::rwx user:usera:rwx # effective:rwx group::rw_ mask:rwx other:r__ getfacl filename1 | setfacl –f – filename2 $ getfacl file1 | setfacl –f – file3  Copying an ACL List You can set default ACL entries only on directories. You must set default ACL entries for the user, group, other, and ACL mask before you set a default ACL entry for an additional user of group. $ pwd /export/home/userc $ mkdir dir1 drwxr_xr_x 2 userc sysadmin 512 Apr 29 17:11 dir1 $ getfacl dir1 # file:dir1 # owner:userc # group:sysadmin user::rwx group::r_x # effective:r_x mask:r_x other:r_x $ setfacl –m d:u::rwx,d:g::r_x,d:o:r_x,d:m:r_x dir1 $ setfacl –m default:user:usera:rwx dir1 $ getfacl dir1 # file:dir1 # owner:userc # group:sysadmin user::rwx group::r_x # effective:r_x mask:r_x other:r_x default:user:rwx default:user:usera:rwx default:group:r_x default:mask:r_x default:other:r_x Effect of Default ACLs on New Subdirectories When a directory contains a default ACL, the permissions granted to the user, group, and other categories for the directory represent the intersection of mode 777, which is the UNIX default for directories without umask influence. When a subdirectory/file created, the permissions on the newly created subdirectory/file are generated according to the intersection between the default ACL entries and the permissions set initially during creation. $ mkdir dir1/subdir1 $ ls –l dir1 drwxr_xr_x+ 2 userc sysadmin 512 Apr 30 08:01 subdir1 $ getfacl dir1/subdir1 $ getfacl dir1/subdir1 # file:dir1/subdir1 # owner:userc # group:sysadmin user::rwx group::r_x # effective:r_x mask:r_x other:r_x default:user:rwx default:user:usera:rwx default:group:r_x default:mask:r_x default:other:r_x If default ACL entries changed for the dir1 it won’t affect the ACL of dir1/subdir1. But if we create new subdirectory the new ACL of the dir1 will get inherited. $ setfacl –m d:group::rwx,d:group::rws,d:other:rwx,d:mask:rwx dir1 $ mkdir dir1/subdir2 $ getfacl dir1/subdir2 user::rwx group::rwx # effective:rwx mask:rwx other:rwx default:user::rwx default:user:usera:rwx default:group::rwx default:mask:rwx default:other:rwx $ cd dir1/subdir2 $ touch filea $ ls –l _rw_rw_rw_+ 1 userc sysadmin 0 Apr 30 13:34 filea $ getfacl filea user::rw_ user:usera:rwx # effective:rw_ group::rw_ # effective:rw_ mask:rw_ other:rw_ The permission granted to the user, group, and other categories for filea represents the intersection of mode 666(default for files without umask influence) with the default entries associated with the directory are set to rwx, the example of intersection is clear. The mask value doesn’t exceed the permissions assigned to the group. Eventhough the /dir1/subdir2 directory lists rwx as the default mask value inherit only upto rw_. The entry for usera was applied as a standard ACL entry and not as a default entry, because only directory replicate default entries. Module – 11  RBAC (Role Based Access Control) /etc/user_attr  The extended user attributes database, which associates users and roles with authorizations and right profiles in addition to the /etc/passwd, /etc/group, and /etc/shadow files /etc/security/prof_attr  The rights profile attributes database, which defines profiles, lists the profile’s assigned authorizations and any nested rights profiles, and identifies the associated help files. /etc/security/exec_attr  The execution attributed database, which defines the privileged commands and scripts assigned to a profile. /etc/security/auth_attr  The authorization attributes database, which defines authorizations and their attributes. This database also identifies the associated help file. /etc/security/policy.conf  File provides system default authorizations for users The /etc/user_attr Database user:qualifier(reserved):res1(reserved):res2(reserved):attr attr : An optional list of semicolon separated (;) key value pairs that describe the security attributes to be applied when the user runs commands. type  Can be normal or role. A role is assumed after the user has logged in. auths  Specifies a list of authorization chosen from names defined in the auth_attr DB profiles  Specifies a list of profile names chosen from the /etc/security/prof_attr DB roles  Specifies a list of role names defined in the same /etc/user_attr DB. Roles are indicated by setting the type value to role. Roles cannot be assigned to other roles. sysadmin::::type=role;profiles=Device Management,Filesystem Management,Printer Management johndoe::::type=normal;auth=solaris.system.date;roles=sysadmin The /etc/security/prof_attr Database profname:res1:res2:desc(description):attr attr : The security attrinutes to apply to the object upon execution. You can specify zero or more key. The two valid keys are help and auths. # grep ‘Printer Management’ /etc/security/prof_attr Printer Management:::manage Printers, daemns, \ ……………………;auths=solaris.admin.printer.read, \ The Printer Management profile, which is defined in the /etc/security/prof_attr DB, is assigned to the sysadmin role in the /etc/user_attr DB. The Printer management profile is defined in the prof_attr DB as having all authorizations, beginning with the solaris.admin.printer.string, assigned to it. These authorizations are defined in the /etc/security/auth_attr DB. solaris.admin.printer.read:::view printer information::\ The /etc/security/exec_attr Database name:policy:type:res1:res2:id:attr name  Name of the profile policy  The security policy associated with this entry. The suser (superuser policy model) is the only valid policy entry. type  The type of entity. Whose attributes are specified. The only valid type is cmd id  a string identifying the entity. Command should have full path or a path with wildcard attr  euid and uid | egid and gid Printer Management:suser:cmd:::/usr/sbin/accept:euid=lp The /etc/security/auth_attr Database You can assign authorization directly to users or roles in the /etc/user_attr DB. You can also assign authorizations to rights profiles, which are assigned to roles. authname:res1:res2:short_desc:long_desc:attr authname  A unique character string that identifies the authorization in the prefix.suffix[.] format. The /etc/security/policy.conf file This file lets you grant specific rights profiles and authorization to all users. Two types of entries in the file are AUTHS_GRANTED=authorizations PROFS_GRANTED=right_profiles # cat policy.conf AUTHS_GRANTED=solaris.device.cdrw PROFS_GRANTED=Basic Solaris Users # roleadd –m –d /export/home/tarback –m –c “Privileged tar backup role” –p “Media Backup, Media Restore” tarback -A authorization and -p profile  Assign authorization and profiles respectively to the role. # rolemod –A auth1,auth2 –p profile1,profile2 role1 Additional Commands Used to Perform RBAC Functions auths Displays authorizations for a user makedbm Makes a dbm file nscd Identifies the name service. Useful for caching the 4 RBAC DB details pam_roles Identifies the role account management module for password authentication module (PAM) pfexec Identifies the profile shells used to execute commands with attributes specifies in exec_attr policy.conf Identifies the config file for the security policy. Lists granted authorization profiles Displays profiles for a specified user roles Displays roles granted to a user roleadd Adds a role account to the system rolemod Modifies the role’s account info in the system roledel Deletes a role’s account from the system Example Profile  Privilege to profile  Creating Role  Role to profile  Role to user /etc/security/prof_attr  Contains profile details Creating profile in prof_attr uadd::Profile for user admin init:::Profile for init process /etc/security/exec_attr  Privilege to profile uadd:suser:cmd:::/usr/sbin/useradd:euid=0 uadd:suser:cmd:::/usr/sbin/usermod:euid-0 init:suser:cmd:::/usr/sbin/init:euid=0 init:suser:cmd:::/usr/sbin/shutdown:euid=0 Creating Role # roleadd –d /export/home/role1 –m role1 # passwd role1 Role to Profile # rolemod –P uadd,init role1 Adding role to user # usermod –R role1 user1 /etc/user_attr  Details about role & user to role  Login as normal user  Switch to role profile & use the privilege command /etc/security/auth_attr  Authorization file  Config file for users & this roles Module – 12  Performing Smartcard Authentication # /usr/dt/bin/sdtsmartcardadmin &  To start smartcard console ATR – Answer to reset Number (unique) # smartcard –c disable  Disabling smartcard operation # smartcard –c admin  Display the current client and server configuration # /etc/smartcard/opencard.properties  Config File Module – 13  Configuring System Messaging The syslog system messaging features track system activities and events. You can manually generate log messages by using the logger command. The syslog function, the syslogd daemon, and input from the /etc/syslog.conf file work together to facilitate system messaging for the solaris 9 OE. The /etc/syslog.conf file This file consists of two tab-separated fields: selector and action. The selector field has two components, a facility and a level written as facility.level. Facility represent categories of system processes that can generate messages. Levels represent the severity or importance of the message. The action field determines whether to send the message. *.err /var/adm/messages  Error messages for all facilities are sent to the /var/adm/messages Only use tabs as white space in the .etc.syslog.conf file. The Solaris OE accesses the /usr/include/sys/syslog.h file to determine the correct facility.level sequencing order. Selector Fields (facility) Options kern Messages generated by the kernel user Messages generated by user processes and don’t have default priority for messages daemon System daemon, such as the in.ftpd and the telnetd daemon auth The authorization system, including the login, su, and ttymon commands syslog Messages generated internally by the syslogd daemon lpr The line printer spooling system, such as the lpr and lpc commands news Files reserved for the USENET network news system uucp The UNIX to UNIX copy (uucp) system does not use the syslog function cron The cron and at facilities, including crontab, at, and cron local0-7 Fields reserved for local use. mark The time when the message was last saved and produced by the syslogd daemon * All facilities, except the mark facility. You can use the asterisk (*) to select all facilities (for eg. *.err); however, you cannot use * to select all levels of a facility (for eg. Kern.*) The levels in descending order of severity Selector Fields (level) Options Level Priority Description emerg 0 Panic conditions that are normally broadcast to all users alert 1 Conditions that should be corrected immediately crit 2 Warnings about critical conditions, such as hard device errors err 3 Errors other than hard device errors warning4 Warning messages notice 5 Non-error conditions that might require special handling info 6 Informational messages debug 7 Messages that are normally used only when debugging a program none 8 Messages are not sent from the indicated facility to the selected file Not all levels of severity are implemented for all facilities in the same way. Action Field  The action field defines where to forward the message. This field can have any one of the following entries /filename The targeted file @host The @sign denoted that messages must be forwarded to a remote host. Messages are forwarded to the syslogd daemon on the remote host user1, user2 The user1 and user2 entries receive messages if they are logged in * All logged in users will receive messages You must restart the syslogd daemon whenever you make any changes to /etc/syslog.conf file # /etc/init.d/syslog stop (or) start # pkill –HUP syslogd  Syslogd started  It’s starting the M4 Macro Processor  M4 will read the /etc/syslog.conf file. Configuring syslog Messaging The inetd daemon uses the syslog command to record incoming network connection requests made by using TCP. You can modify the behavior of the inetd daemon to log TCP connections by using the syslogd daemon. The daemon facility and the notice message level are supported by inetd. Use the –t option as an argument to the inetd daemon to enable tracing of TCP services. When you enable the trace option for the inetd daemon, it uses the daemon.notice to log the client’s IP address and TCP port number, and the name of the service. Add the –t option to the entry which activated the inetd daemon in the inetsvc script located in the /etc/init.d directory # grep inetd /etc/init.d/inetsvc /usr/sbin/inetd –s –t  You must restart the inetd daemon for the new option to take effect # grep daemon.notice /etc/syslog.conf *.err;kern.debug;daemon.notice;mail.crit /var/adm/messages Monitoring a syslog File in Real Time The tail –f command holds the file open so that you can view messages being written to the file by the syslogd daemon. # tail –f /var/adm/messages  Press Ctrl+c to exit Adding One-Line Entries to a System Log File logger [-i](logs PID) [-f file] [-p priority] [-t tag] [message] # logger system rebooted  If the user.notice field is configured in the /etc/syslog.conf file, the message is logged to the file designated for the user.notice selector field # logger –p user.err system rebooted  Changing the priority of the messages to user.err route the messages to the /var/adm/messages file as indicated in the /etc/syslog.conf file # logger –i –p2 “crit” /dev/sysmsg  Console Module – 14  Using Name Services Name Services  DNS, NIS, NIS+, LDAP /etc/rc2.d/S72inetsvc script  Starts DNS during system boot. /etc/rc2.d/S71rpc script  Starts NIS & NIS+ during system boot /etc/rc2.d/S72directory script  Starts iPlanet Server during system boot. Name Service Feature Summary Feature DNS NIS NIS+ LDAP_____ Namespace Hierarchical Flat Hierarchical Hierarchical Data Storage Files/Resoruce Two column Multicolumn Directories records maps tables (varied) Server Types Master/Cache/ Master/ Root Master/ Master/ Cache only/ Slave non-root mast. Consumer Forwarding Replica Transport TCP/IP TCP/IP TCP/IP TCP/IP Scale WAN LAN LAN WAN _______________________________________________________________________ The name service switch file determines which services a system users to search for information and in which order the name services are searched. All Solaris OE systems uses the /etc/nsswitch.conf file as the name service switch file. The nsswitch.conf is loaded with the contents of a template file during the installation of the Solaris OE depending on the name service that is selected. Name Service Name Service Template Local Files /etc/nsswitch.files DNS /etc/nsswitch.dns NIS /etc/nsswitch.nis NIS+ /etc/nsswitch.nisplus LDAP /etc/nsswitch.ldap Configuring the Name Service Cache Daemo (nscd) The nscd daemon is a process that provides a cache for the most common name service requests. The /etc/nscd.conf file controls the behavior of the nscd daemon. The nscd daemon provides caching for passwd, group, hosts, ipnodes, exec_attr, prof_attr and user_attr databases. Each line specifies either an attribute and a value or an attribute, a cache name, and a value. # /etc/init.d.nscd stop (or) start The getent command provides generic retrieval interface to search many name service database. As a system administrator, you can query name service information sources with tools, such as the ypcat NIS namespace nslookup DNS ldaplist LDAP Bt these tools are not consulting nsswitch.conf file. Whereas getent command searches the information sources in the order in which they are configured in the name service switch file. So if there is any error in the file will be identified with this command. getent database [key]….. database  The name of the database to be examined. This name can be passwd, group, hosts, ipnodes, services, protocols, ethers, networkds, or netmasks. # getent passwd lp lp:x:71:8:Line Printer Admin:/usr/spool/lp: # getent group 10 staff::10: # getent hosts sys44 192.168.38.44 sys44 loghost (loghost will be absent if the NIS is searched first) Module – 15  Configuring Name Service Clients Configuring a DNS Client The client resolver code is controlled by the following files /etc/resolv.conf  Contains directive to specify the scope of a query /etc/nsswitch.conf  Contains the reference to DNS for the hosts entry Configuring the DNS Client During Installation  Select DNS  Give Domain Name  Enter IP Address  Enter search Domains  Confirm Editing DNS Client Configuration Files # vi /etc/resolv.conf domain digigeeks.com nameserver 140.40.40.152 search digigeeks.com  List the local domain as the first argument to the search Copying the /etc/nsswitch.dns File to the /etc/nsswitch.conf # cp /etc/nsswitch.dns /etc/nsswitch.conf # cat /etc/nsswitch.conf ……… hosts files dns …….. If you want to add DNS name resolution to a system currently running a name service, such as NIS or NIS+. You must place the dns keyword on the hosts line in the specific location, along with other keywords. # cat /etc/nsswitch.conf ….. hosts: nfs files dns ….. Setting up an LDAP Client The LDAP server cannot be a client of itself. Getting this configuration to work properly requires changes to the LDAP server and the LDAP client. The ldap_cachemgr daemon is responsible for maintaining and updating the changes to the client profile information. Configuring LDAP Client During Installation  Select LDAP  Enter Domain Name  Enter Profile Name & Profile Server IP Address  Confirm Initializing the Native LDAP Client You execute the ldapclient command on the client system once to initiate the client as a native LDAP client. The ldapclient command creates two files in the ./var/ldap directory on the LDAP client. These files contain info that the LDAP client use when binding to and accessing LDAP data. /var/ldap/ldap_client_cred  The proxy agent info that the client uses for LDAP authentication /var/ldap/ldap_client_file  The config info from the client profile in the LDAP server DB # ldapclient init –a proxy password=proxy –a proxy DN=cn=proxyagent, ou=profile, dc=suned.com, dc=sun –a domainname=suned.com 192.168.0.100 # ldapclient list Copying the /etc/nsswitch.ldap to the /etc/nsswitch.conf During LDAP client initialization the /etc/nsswitch.ldap file is copied over the /etc/nsswitch.conf file # ldaplist  To list naming info from LDAP server # ldapclient uninit  Unconfiguring LDAP Client Module – 16  NIS Master Server Config NIS maps are located in /var/yp/domainname directory(where domainname is the name of the NIS domain). There are two files (.pag and .dir files) for each map in this directory. Eg. /var/yp/training/hosts.byname.pag file /var/yp/training/hosts.byname.dir file /var/yp/training/hosts.byaddr.pag file /var/yp/training/hosts.byaddr.dir file The syntax for the NIS map is map.key.pag and map.key.dir Ypcat [-k] mname  To retrieve values from NIS name service map, mname can be either a map name or a map nickname # ypcat hosts localhost 127.0.0.1 localhost sysprint 192.168.30.70 sysprint sys44 192.168.30.44 sys44 loghost ypmatch [-k] value mname  Prints values associated with one or more keys from the NIS name services map specified by the mname argument. # ypmatch sys44 hosts sys44: 192.168.30.44 sys44 loghost # ypmatch usera passwd usera: usera:LojyTdiQev5i:3001:10::/export/home/usera:/bin/ksh NIS Domain Contains One NIS Master Server NIS Slave Servers (Optional) NIS Clients The NIS Master Server Contains the original /etc/ASCII files used to build the NIS maps Contains the NIS maps generated from the ASCII files Provides a single point-of control for the entire NIS domain NIS Slave Servers Do not contain the original /etc/ASCII files Contains copied of the NIS maps copied from the NIS Master Server Provides a a backup repository for NIS map information Provides redundancy in case of server failure Provides load sharing on large networks NIS Clients Do not contain original /etc/ASCII files Do not contain any NIS maps Bind to the master server or to a Slave Server to obtain access to the administrative file information contained in that server’s NIS maps Dynamically rebind to another server in case of server failure Make all appropriate system calls aware of NIS NIS Processes The main daemons involved in the running of an NIS domain are The ypserv daemon  Responds to client information requests The ypbind daemon  Client to server binding The rpc.yppasswd daemon  Password change update in master server The ypxfrd daemon  Push the map to slave servers (sync) The rpc.ypupdated domain  Update NIS maps using the config stored in /var/yp/updates The NIS Slave Server contains upserv and ypbind daemon The NIS Clients contains only ypbind daemon The three most common search orders are Search files and then NIS Search NIS and then files Forward hosts lookup requests from NIS to DNS Introducing NIS Security The /var/yp/securenets file to restrict access to a single host or to a subnetwork, and using the passwd.adjunct file to limit access to the password information across the network. The /var/yp/securenets File If exist on an NIS server, the server only answers queries or supplies maps to hosts and networks whose IP Address exist in the file. The server must be part of the subnet to access itself. # cat /var/yp/securenets # Two methods of giving access to a system. Using the netmask followed by the IP Address # or host keyword followed by the IP Address host 127.0.0.1 255.255.255.0 150.10.1.0 host 13.13.14.1 host 13.13.14.2 If you modify entries in the /var/yp/securenets file. You must kill and restart the ypserv and ypxfrd daemons. # /usr/lib/netsvc/yp/ypstop (or) ypstart The passwd.adjunct File Encrypted password are normally hidden from the user in the /etc/shadow file. With the default NIS configuration, however the encrypted password string is shown as part of passwd maps. This file prevents unauthorized users from seeing the encrypted passwords. # ypmatch –k usera passwd usera: usera:LojyTdiQev512:3001:10:/export/home/usera:/bin/ksh The passwd.adjunct file contains the account name preceded by ## in the password field. Subsequent attempts to gain account ino, using the ypcat or ypmatch commands, returnds the password entry from the passwd adjunct file. # ypmatch –k usera passwd usera: usera:##usera:3001:10:/export/home/usera:/bin/ksh Configuring NIS Domain To locate the source file in another directory, modify the /var/yp/Makefile file: Change the DIR=/etc line to DIR=Your choice Change the PWDIR=/etc line to PWDIR=/your-choice Before you make any modification to the /var/yp/Makefile, save a copy of the original Makefile file. The NIS configuration script /usr/sbin/ypinit and the make utility generate NIS maps. The ypinit command reads the Makefile for source file locations, and converts ASCII scource files into NIS maps.The /etc/defaultdomain file sets the NIS domain name during system boot. Important files on the NIS Master (Part 1)  hosts, passwd & shadow Important files on the NIS Master (Part 2) The /var/yp/domainname directory is the repository for the NIS maps created by the ypinit script. The /var/yp/binding/domainname directory contains the ypservers file where the names of NIS Master server and NIS Slave server are stored. Important files on the NIS Master (Part 3)  The /usr/netsvc/yp directory contains the ypstop and ypstart commands that stop and start NIS services respectively # /usr/sbin/ypinit –m  This command prompts for a list of other machies to become NIS slave servers. Configuring the NIS Master Server Core, End User or Developer software configuration cluster do not have all necessary files in the /usr/lib/netsvc/yp directory to allow a host to function as an NIS server. 1. Copy the /etc/nsswitch.nis file to the /etc/nsswitch.conf file. If necessary, modify the file 2. Enter the domainname command to set the local NIS domain # domainname classroom.central.sun.com 3. Create an /etc/defaultdomain file with the domain name 4. If the files do not already exist, use the touch command to create zero-length files. /etc/ethers, /etc/bootparams, /etc/locale, /etc/timezone, /etc/netgroup and /etc/netmasks. These files are necessary for the creation of the complete set of NIS maps. 5. Install and update Makefile file in the /var/yp directory. 6. Create or populate the /etc/locale file, and make an entry for each domain on your network using the following format domainname locale eg. Classroom.central.sun.com en_us 7. Initialize the master server by using the local /etc files # ypinit –m  Provide slave server names and Ctrl+D to save the details. Press n for “Terminate it on the first fatal error” Note: If you have to restart the ypinit program, You are prompted to destroy the /var/yp/domainname directory. Answer Y 8. # /usr/lib/netsvc/yp/ypstart Testing the NIS Service $ ypcat hosts  Prints value from an NIS map # ypmatch sys41 localhost hosts 192.168.30.41 sys41 127.0.0.1 localhost loghost $ ypwhich  To identify the master server sys41 Configure the NIS Client 1. Copy the /etc/nsswitch.nis file to the /etc/nsswitch.conf file 2. Edit the /etc/inet/hosts file to ensure NIS master and slave servers have been defined. 3. # domainname domainname  To set the local NIS domain 4. Create and populate the /etc/defaultdomain file with the domain name 5. # ypinit –c  To initialize the system as an NIS client 6. Enter the names of the NIS Master and all Slave Servers 7. # /usr/lib/netsvc/yp/ypstart 8. # ypwhich –m  To test the functionality Configuring NIS Slave Server Follow the client configuration steps and perform the below command # ypinit –s master  Command to initialize the system as an NIS slave server. Where master is the name of the NIS master. Start the service and test the functionality Updating the NIS Map 1. Updates the text files in your source directory (typically /etc, unless it was changed in the Makefile file) 2. # cd /var/yp 3. # /usr/ccs/bin/make  Refresh the NIS database maps using the make utility Updating NIS Password Map If the NIS master is running the rpc.yppasswdd daemon, any client system can update the NIS password map by using the yppasswd or passwd commands. 1. Run the rpc.yppasswdd daemon on the NIS master server # /usr/lib/netsvc/yp/rpc.yppassed /$PWDIR/passwd –m passwd Updating the NIS Slave Server Map The following steps manually update the NIS timezone map on the master server and propagate all maps to the slave servers 1. Edit the source file on the NIS Master # vi /etc/timezone 2. Remake and push the NIS maps to slave servers # cd /var/yp; /usr/ccs/bin/make 3. If the push fails. Manually pull only the timezone map from the master server by performing the below command in Slave server # /usr/lib/netsvc/yp/ypxfr timezone.byname # ypinit –s nis_master  To pull all of the maps at once Sometimes maps fail to propagate, and you must manually use the ypxfr command to retrieve new map information. You can use shell scripts to run cron jobs for automatic update. The Solaris OE provides several template scripts in the /usr/lib/netsvc/yp directory that you can use and modify to meet your local site requirement. ypxfr_lperhour script  To sync NIS Slave Servers passwd map ypxfr_lperday script  To sync NIS Slave Servers NIS maps for the group, protocols, networks, services, and upservers keys. Ypxfr_2perday script  To sync NIS Slave servers nIS maps for the hosts, ethers, netfroups keys, and mail aliases. Quick Reference # domainname digit.com  Create domain name # domainname > /etc/defaultdomain  Creating domainname file # cp /etc/nsswitch.nis /etc/nsswitch.conf # /var/yp/Makefie  Config file Makefile 4 parts 1 – Declaration 2 – Details of centralization 3 – Coding for mapping 4 – Declaration of original path # cd /var/yp # ypinit –m  Initializing the master server # ypinit –s  Initializing the slave server # ypinit –c  Initializing the client Ctrl+D  To save the file Is this correct? [y/n] y Non fatal error [y/n] n  If there is any error follow the below procedure # cd /etc # touch ethers bootparams netgroup netmasks timezone # cd /var/yp # ypinit –m # /usr/lib/netsvc/yp/ypstart  To start the daemons # ypwhich  Shows the map server details Solaris # ypwhich –m  Full details of map  A directory will be created with domain name # cd /var/yp/digit.com  Contains all config file with .pag & .dir extensions # ypcat to read the file # ypcat –k passwd  With arguments print keys as well as values # ypmatch –k root passwd NFS Config # vi /etc/dfs/dfstab share /export/home share /usr/man.orig # /etc/init.d/nfs.server stop # /etc/init.d/nfs.server start # useradd –d /export/home/Chennai1 –m Chennai1 # useradd –d /export/home/Chennai2 –m chennai2 # passwd chennai1 # passwd Chennai2  Remove the /export in the /etc/passed file for user chennai1 & chennai2. So the home dir is /home/chennai1 Autofs Config # vi /etc/auto_master comment +auto_master to search in WW /home auto_home -nobrowse / auto_direct - # vi /etc/auto_direct /usr/share/man 140.40.40.151:/usr/share/man.orig # vi /etc/auto_home comment +auto_home chennai1 140.40.40.151:/export/home/chennai1 chennai2 140.40.40.151:/export/home/chennai2 # automount –v # cd /var/yp # /usr/ccs/bin/make  To update the map after any config change  Include auto direct in Makefile in 2, 3, & 4 section # /usr/lib/netsvc/yp/ypstop #/usr/lib/netsvc/yp/ypstart NIS Client Config # domainname digit.com # domainname > /etc/defaultdomain # vi /etc/hosts 140.40.40.151 Solaris # cp /etc/nsswitch.nis /etc/nsswitch.conf # ypnit –c Give master server name Solaris # /usr/lib/netsvc/yp/ypstart rpcbind done – client has only ypbind daemon  Slave server has ypserve & ypbind daemon NIS Slave Config # ypinit –s Solaris (Master Server)  Before configuring slave, client config should be done. Module – 17  JumpStart Four Main Services Boot Services Identification Services Configuration Services Installation Services Implementing a Basic Jumpstart Server 1. Spool the OS image 2. Edit the sysidcfg file 3. Edit the rules and profile files 4. Run the check script 5. Run the add_install_client scripts 6. Boot the client # cd /export # mkdir config # mkdir sol_dump # cd /cdrom/cdrom0/s0/Solaris_9/Misc/Jumpstart_sample/ # cp –r * /export/config/ # cd /cdrom/cdrom0/s0/Solaris_8/Tools # ./setup_install_server /export/home/sol_dump  Copying solaris dump to local directory # cd /cdrom/cdrom0/Solaris_9/Tools/ # ./add_to_install_server /export/home/sol_dump  Appending 2nd CD content # cd /etc # vi ethers 8:0:20:a6:aa:2b ultra5 (hostname) # vi /etc/hosts 140.40.40.154 ultra5 # vi /etc/timezone Asia/Calcutta ultra5 # cd /export/config/ # vi rules hostname ultra5 - host_class finish_script - Pre Install script host_class  Config details like partition finish_script  Post install scripts # vi host_class install_type initial_install system_type standalone partitioning explicit Cluster SUNWXall filesys c0t0d0s0 10000 / filesys c0t0d0s1 550 swap filesys c0t0d0s7 free /export/home # vi finish_script touch /a/noaushutdown rm /a/etc/defaultdomain rm –r /a/var/yp/digit.com cp /a/etc/nsswitch.files /a/etc/nsswitch.conf # vi sysidcfg  System identification & configuration. Timezone can also be given here security_policy=none name_service=none network_interface=primary [netmask=255.255.0.0 protocol_ipv6=no] timezone= Asia/Calcutta system_locale=en_US  Time zone are listed in the directory structure below the /usr/share/lib/zoneinfo directory.  Locales are listed in the /usr/lib/locale directory # chmod 755 finish_script # ./check  To check the config # vi /etc/dfs/dfstab share –o anon=0 /export/home/sol_dump share –o anon=o /export/config # cd /var/yp # /usr/ccs/bin/Make # cd /export/home/sol_dump/solaris_9/Tools # ./add_install_client –c 140.40.40.151:/export/config –p 140.40.40.151:/export/config ultra5(hostname) sun4u # update the NIS file with make command From Client ok boot net –install  Will search the network and start the installation automatically  Before a Jumpstart client can boot and obtain all of the NFS resourctes it requires, every directory listed as an argument to the add_install_client script must be shared by the server on which it resides. Setting Up a Boot-Only Server A boot server responds to RARP, TFTP, and bootparams requests from jumpstart clients and provides a boot image using the NFS service. 1. Running the setup_install_server script with the –b option to spool a boot image from CD-Rom or DVD 2. Running the add_install_client script with options and argument that shows a list of servers and the identification config, and installation services that they provide. Executing the setup_install_server script # mkdir /export/install # cd /cdrom/cdrom0/s0/Solaris_9/Tools # ./setup_install_server –b /export/install Executing the add_install_client script Before you run the script, update the hosts and ethers information for the jumpstart client /etc/inet/hosts 192.10.10.4 client1 /etc/ethers 8:0:20:9c:88:5b client1 The boot server must have entry in /etc/inet/hosts file for each server you specify while you run add_install_client script. # cd /export/install/Solaris_9/Tools # ./add_install_client –c server1:/export/config –p server1:/export/config client1 sun4u Configuring NIS for Jumpstart Procedures Configuring NIS to support jumpstart procedures involves editing files and running commands on the NIS master server in use. Info supplied in the sysidcfg file overrides any information you make available in NIS. A change to any file that is represented by a map in an NIS domain requires that you complete the following steps on the NIS master server # vi /etc/inet/hosts 192.10.10.4 client1 # vi /etc/ethers 8:0:20:88:5b client1 # vi locale client1 en_US # cd /var/yp # vi Makefile 1. Add the text after the existing *.time entries. Duplicate the timezone entry, and replace timezone with locale Add/Append the word locale to the line beginning with the word all Add the following line after the auto.home: autohometime entry Locale: locale.time Save the file and exit the editor # cd /var/yp # /usr/ccs/bin/make 2. On any slave servers that exist in the NIS domain, run the ypxfr command to transfer the locale.byname map for the first time. # /usr/bin/netsvc/yp/ypxfr locale.byname 3. On the NIS master server, again update the NIS maps by running the make command # cd /var/yp # /usr/ccs/bin/make # vi /etc/timezone US/Mountain client1 US/Mountain Central.sun.com # cd /var/yp # /usr/ccs/bin/make # /vi /etc/netmasks 192.9.200.0 255.255.255.0 # cd /var/yp # /usr/ccs/bin/make  Each time you run the add_install_client script on a boot server to provide boot support for a jumpstart client, the script checks the /etc/nsswitch.conf file for the bootparams entry. Begin Script Profile Finish Script  Use can use CD/DVD soruces as boot source instead of spooled Solaris OE Image. Also you can use a Flash source as an alternative installation service. Identifying Log Files Jumpstart clients retain the following log files during the installation process: /tmp/begin.log /tmp/finish.log /tmp/install_log /var/sadm/system/logs/sysidtool.log Jumpstart clients retain a corresponding set of log files after the installation process completes and the system reboots /var/sadm/system/logs/begin.log /var/sadm/system/logs/finish.log /var/sadm/system/logs/install_log /var/sadm/system/logs/sysidtool.log Module – 18  Flash # flarcreate –n flash_archive –R / -C –x /flash /flash/flash_archive flash_archive  Any name can be given -R  To mention root path -C  To compress the archive file -x  To exclude folders while creating archive image -t  Create an archive on a tape device Administering a Flash Archive flare –i archive  Retrievs info about the archive flare –c archive  Combines the individual sections that make up an existing archive into a new archive flare –s archive  Splits an archive into one file for each sections of the archive /etc/ethers  Mac address and hostname /etc/hosts  IP Address and hostname # cd /export/config # vi rules  Same as Jumpstart content # vi host_class  Same as Jumpstart content except few options install_type flashinstall archive_location nfs 140.40.40.160:/flash/flash_archive partitioning …. …. … # vi finish_script  Same as Jumpstart content # vi sysidcfg  Same as Jumpstart content # ./check  To check the config # cd /export/home/sol_dump/solaris_9/Tools # ./add_install_client –c 140.40.40.160:/export/config –p 140.40.40.160:/export/config ultra5(hostname) sun4u NFS Shares  /flash folder /export/config folder

solaris -10

2009-05-29T12:40:00.001-07:00

1.Tell me the files used in Custom Jump Start?
2.What is the signal while killing process?
3.How to install boot block in solaris?
4.What is state database(SVM Solaris)?
5.How you create state database?
6.How to grow the file system(steps)?
7.If root file system filled what you do?
8.How you check the logs solaris?
9.Raid 1 Mirroring(Explain Mirroring)?
10.uptime,top output?
11.How to check processor information?
12.If password file get corrupted how you restore?

1. rules, sysidcfg, profile: 3 main files. After that we run addtoinstallclient script with few parameters and it updates /etc/ethers and /etc/bootparams. In the beginning we create a dump of installation CDs using setup_server_install script. These scripts are available in Tools dir on installation media's 1st CD.
2. SIGKILL/SIGTERM and many others.
3. installboot bootblk /dev/rdsk/c0t0d0s0--set parameters acc.
4. Which carry state of various mirroring setups done by us.
5. metadb
6. growfs
7. create another RAID concatenated partition and attach it to the root partition and then run metaroot.
8. /var/adm/messages. Application servers have their own log dir. Other things can be set using /etc/syslog.conf
9. What ever data any ctrl gets it duplicates it on both or multiple HD.
10. uptime: time since m/c is up. top: a list in ascending order in which CPU is being consumed by various processes.
11. psrinfo
12. one we believe u had taken backup. Else create all users and set their passwds.

Solaris Interview -10

2009-05-29T12:39:00.001-07:00

Interview questions (Solaris -10)

2009-05-29T12:10:00.000-07:00

veritas netbackup interview question with answer

2009-04-22T09:09:00.000-07:00

1 .What is a master server & media server?

The master server manages backups, archives, and restores. The master server is responsible for media and device selection for NetBackup. Typically, the master server contains the NetBackup catalog. The catalog contains the internal databases that contain information about NetBackup backups and configuration.

Media servers provide additional storage by allowing NetBackup to use the storage devices that are attached to them.

During a backup or archive, the client sends backup data across the network to a NetBackup server. The NetBackup server manages the type of storage that is specified in the backup policy.
During a restore, users can browse, then select the files and directories to recover. NetBackup finds the selected files and directories and restores them to the disk on the client.

2)What is volume pools & volume Groups?

Volume pool contains pool of backup medias and volume group contains location of volumes.

3 What is media multiplexing?

Its nothing but distributing the data across multiple media for a backup job.

5)What does these status codes mean- 216, 256,298,50?

216 - failed reading retention database information
256 - An internal Vault error occurred.
298 - This error occurs if the robotic library is not in a state to support ejecting media.
50 - The client backup terminated abnormally. For example, this error occurs if a NetBackup master or media server is shut down or rebooted when a backup or restore is in progress.

6)What is the process of importing images and why do we import images?

When you need to restore a backup which is expired from the netbackup catalog you have to import the image.

7)What does it mean by inventoring a robot?)What is media multiplexing?

Inventory robot is done to recognize new tapes inserted into the library.

veritas netbackup error code troubleshooting guide

2009-04-22T08:02:00.000-07:00

Veritas Status Codes and Messages

This document lists all the status codes and messages provided by NetBackup.

10 | 20 | 30 | 40 | 50 | 60 | 70 | 80 | 90 | 100 | 110 | 120 | 130 | 140 | 150 | 160 | 170 | 180 | 190 | 200

210 | 220 | 230 | 240 | 250 | 260 |

1 2 3 4 5 6 7 8 9

Status Code: 0 Top

Message: "the requested operation was successfully completed"

Explanation: There were no problems detected with the requested operation.

Recommended Action:

None, unless this was a database backup performed through a database extension product (for example, NetBackup for Oracle or NetBackup for SQL Server). In those instances, code 0 means the backup script that started the backup ran without error. However, you must check other status as explained in the related NetBackup manual to see if the database was successfully backed up.

Status Code: 1 Top

Message: "the requested operation was partially successful"

Explanation: A problem that may require corrective action was detected during the requested operation.

Recommended Action:

Check the All Log Entries report and also the progress log (if there is one).

Some of the problems that can show up under Status Code 1 are:

· A file or directory path that is more than 1023 characters long.

· Could not open a file.

· On a UNIX system, NetBackup could not get the link name of a file.

· On a UNIX system, NetBackup could not process a sparse file.

· Read error encountered in a file.

· File is of an unknown type.

· On a UNIX system, the lstat system call fails on a file that is eligible to be backed up. This may be a permission problem.

· On UNIX, a file could not be locked that has mandatory locking enabled.

Status Code: 2 Top

Message: "none of the requested files were backed up"

Explanation: A backup or archive could not back up any of the files in the file list.

Recommended Action: Verify that the files exist and you have read access to them.

· On UNIX clients, check to see if the files or directories would be excluded because of an entry in /usr/openv/netbackup/exclude_list.

· On PC clients, check the exclude list per the instructions in the user's guide for the client.

· On Windows NT clients, verify that the account used to start the NetBackup Client service has read access to the files.

If you are backing up a network drive or a UNC (universal naming convention) path, use the Services application in the Windows NT Control Panel to verify that the NetBackup Client service does not start under the SYSTEM account. The SYSTEM account cannot access network drives.

To back up network drives or UNC paths, change the NetBackup Client service startup to log in as a user that has permission to access network drives.

Status Code: 3 Top

Message: valid archive image produced, but no files deleted due to non-fatal problems

Explanation: The backup portion of the archive command reported problems so the files were not deleted.

Recommended Action: Examine the progress log of the archive on the client to determine if you need to retry the archive after correcting the problem. If the problem is not serious and the files were backed up, you can manually delete the files. To verify which files were backed up, use the NetBackup client-user interface in restore mode and browse the files in the archive.

A possible cause for files not being deleted is that you do not have the necessary permissions. NetBackup cannot delete files unless you are either the user that owns the files, a superuser on UNIX, or an administrator on Windows NT.

Status Code: 4 Top

Message: archive file removal failed

Explanation: The backup portion of the archive completed was successful but the delete failed.

Recommended Action: Verify that you have permission to delete the files and that the read-only flag is not set for the files. On UNIX clients, verify that you have write permission to the directories that contain the files. Since the backup was successful, you can delete the files that were backed up (or have the system administrator delete the files if you do not have the necessary permissions).

Status Code: 5 Top

Message: the restore failed to recover the requested files

Explanation: There were errors that caused the restore to fail.

Recommended Action:

1. Examine the progress log on the client for messages on why the restore failed. Also, check the All Log Entries report on the server.

2. On Windows NT and UNIX, check ownership and permission on directories where files will be restored.

3. Correct problems that you find and retry the restore.

Status Code: 6 Top

Message: the backup failed to back up the requested files

Explanation: Errors caused the user backup to fail.

Recommended Action:

1. Verify that you have read access to the files. Check the progress log on the client for messages on why the backup failed. Correct problems and retry the backup.

2. On Windows NT clients, verify that the account used to start the NetBackup Client service has read access to the files.

3. On Macintosh clients, this code can be due to multiple backups being attempted simultaneously on the same client. Some possible solutions are:

o Adjust the backup schedules.

o If the client is only in one class, set the general class attribute, Maximum Jobs per Class, to 1.

o Set the NetBackup global attribute, Maximum Jobs Per Client, to 1 (note that this limits all clients in all classes).

4. For a UNIX database extension client (for example, NetBackup for Oracle), this can mean a problem with the script that is controlling the backup.

Check the progress report on the client for a message such as "Script exited with status code = number" (the number will vary). The progress log also usually names the script.

Check the script for problems. Also, check the troubleshooting logs created by the database extension. See the NetBackup guide that came with the database extension for information on the scripts and troubleshooting logs.

Status Code: 7 Top

Message: the archive failed to back up the requested files

Explanation: Errors caused the user archive to fail.

Recommended Action:

Verify that you have read access to the files. Check the progress log on the client for messages on why the archive failed. Correct problems and retry the archive.

On Windows NT clients, verify that the account used to start the NetBackup services has read access to the files.

Status Code: 8 Top

Message: unable to determine the status of rbak

Explanation: On DomainOS clients, rbak is used to do restores. If rbak does not exit with a status message, NetBackup cannot determine whether the restore worked or not.

Recommended Action: Check for a new core file to see if rbak aborted. Check the ps output to see if rbak is hung. If so, kill it and try again. Check the progress log for any unusual messages from rbak.

Status Code: 9

Message: an extension package is needed but was not installed

Explanation: A NetBackup extension product is required in order to perform the requested operation.

Recommended Action: Install the required extension product.

11 12 13 14 15 16 18 19 Top

Status Code: 10 Top

Message: allocation failed

Explanation: Allocation of system memory failed because there is insufficient system memory available. This could be caused by the system being overloaded with too many processes and not enough physical or virtual memory.

Recommended Action: Free up memory by terminating unneeded processes that consume memory. Add more swap space or physical memory.

Status Code: 11 Top

Message: system call failed

Explanation: A system call failed. This status code is used for a generic system call failure that does not have its own status code.

Recommended Action:

1. Check the All Log Entries and Problems reports to determine which system call failed and other information about the error.

2. A frequent cause is that the server's file system is full. For example, if you see a message similar to the following in the Problems report or bpdbm activity log:

06/27/95 01:04:00 romb romb db_FLISTsend failed: system call failed (11)

06/27/95 01:04:01 romb romb media manager terminated by parent process

06/27/95 01:05:15 romb romb backup of client romb exited with status 11 (system call failed)

On UNIX systems, run a df command on the /usr/openv/netbackup/db directory.

If the df command does not reveal the problem, check the bpdbm activity logs or do a grep for the message system call failed

in /usr/openv/netbackup/db/error/*

On Windows NT systems, verify there is room in the disk partition where NetBackup is installed.

3. Verify that the system is not running out of virtual memory. If virtual memory is the problem, shut down unused applications or increase the amount of virtual memory.

To increase virtual memory on Windows NT, 98, and 95:

a. Display the Control Panel.

b. Double-click System.

c. On the Performance tab, set Virtual Memory to a higher value.

4. Check for a semaphore problem. This error can be caused by the system not having enough semaphores allocated. This is most commonly seen on Solaris 2 servers when an RDBMS is also running.

The symptoms of the problem vary. In some cases, error messages in the NetBackup log indicate a backup failure due to an error in semaphore operation; another symptom is the inability of the NetBackup Device Manager service Media Manager device daemon, ltid, to acquire a needed semaphore (this is the NetBackup Device Manager service on Windows NT).

System requirements vary; thus, no absolute recommendations can be made. One customer running both NetBackup and ORACLE on their Solaris server made the following changes to their /etc/system file and then rebooted the system (boot -r); the changes were found to be adequate:

set semsys:seminfo_semmni=300
set semsys:seminfo_semmns=300
set semsys:seminfo_semmsl=300
set semsys:seminfo_semmnu=600

Set these attributes to a value great enough to provide resources to all applications on your system.

5. Check for a shared memory problem. This error can occur if the system cannot allocate enough shared memory. This usually occurs when you use multiplexing, which increases the shared memory requirements. A symptom is an entry similar to the following in a NetBackup log (or report) could not allocate enough shared memory

If you see this type of message, refer to the vendor documentation for your platform for instructions on increasing the amount of shared memory on your system.

Because system requirements vary, we can make no absolute recommendations, other than to use values great enough to provide resources to all applications. Although, in at least one instance, the following was found to be adequate on a Sun platform:

set shmsys:shminfo_shmmax=8388608
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=10
set semsys:seminfo_semmnu=600
set semsys:seminfo_semmns=300

After making the changes to the /etc/system file on the Sun platform and rebooting with boot -r, the problem was resolved. Note that in the above, shminfo_shmmin must be less than or equal to 100 for NetBackup processes to run.

6. Examine other activity logs or the progress log on the client.

7. If a backup on a Windows NT NetBackup client fails with status code 11 and the client is using Open Transaction Manager (OTM) for open file management, it is possible that the error was caused by the OTM cache file being full. If this is the case and bpbkar activity logs are turned on, a message similar to the following should appear at the end of the backup:

04/28/99 11:27:56 AM: [216]: ERR - OTM Error:0xe0001005
04/28/99 11:27:59 AM: [216]: INF - OTM Terminate - disabled for all processes
04/28/99 11:27:59 AM: [216]: FTL - Backup operation aborted!

If this error is encountered, you may need to increase either the initial OTM cache size or the maximum OTM cache size, depending on the requirements of your installation and your usage of OTM.

Status Code: 12 Top

Message: file open failed

Explanation: An open of a file failed.

Recommended Action: Check the NetBackup Problems report. Try to determine the file and why the error occurred. A possible cause is a permission problem with the file. For detailed troubleshooting information, create an activity log directory for the process that returned this status code. Then, retry the operation, and check the resulting activity log.

Status Code: 13 Top

Message: file read failed

Explanation: A read of a file or socket failed. Possible causes include:

· I/O error reading from the file system.

· Read of an incomplete or corrupt file.

· Socket read failing. A socket read failure can be caused by a network problem or a problem with the process that is writing to the socket.

Recommended Action:

1. Check the NetBackup Problems report for clues on where and why the problem occurred.

2. For a FlashBackup client, check the /var/adm/messages log for errors like the following:

Mar 24 01:35:58 bison unix: WARNING: sn_alloccache: cache /dev/rdsk/c0t2d0s3 full - all snaps using this cache are now unusable

This indicates that the cache partition is not large enough. If possible, increase the size of the cache partition. Or, if multiple backups are using the same cache, either reduce the number of concurrent backups by rescheduling some of them or reschedule the entire backup to a time when the file system is less active.

3. For detailed troubleshooting information, create an activity log directory for the process that returned this status code, retry the operation, and check the resulting activity log.

Status Code: 14 Top

Message: file write failed

Explanation: A write to a file or socket failed.

Recommended Action:

Check the NetBackup Problems report for clues on where and why the problem occurred. For detailed troubleshooting information, create an activity log directory for the process that returned this status code, retry the operation, and check the resulting activity log.

The following are some possible causes:

· I/O error writing to the file system

· Write to a socket failed. This can be caused by a network problem or a problem with the process reading from the socket.

· Writing to a full disk partition.

Status Code: 15 Top

Message: file close failed

Explanation: A close of a file or socket failed.

Recommended Action: Check the NetBackup Problems report for clues on where and why the problem occurred. For detailed troubleshooting information, create an activity log directory for the process that returned this status code, retry the operation, and check the resulting activity log.

Status Code: 16 Top

Message: unimplemented feature

Explanation: The specified operation is unimplemented. This error should not occur through normal use of NetBackup.

Recommended Action: Save all error information and call customer support.

Status Code: 18 Top

Message: pipe close failed

Explanation: Close of a pipe failed, when one process tries to start a child process.

Recommended Action: Check the NetBackup Problems report for clues on why the failure occurred. For detailed troubleshooting information, create an activity log directory for the process that returned this status code, retry the operation, and check the resulting activity log.

Status Code: 19 Top

Message: getservbyname failed

Explanation: A call to getservbyname() failed. The getservbyname() function uses the name of the service to find a service entry in the services file (or NIS services map on UNIX if it is configured).

Recommended Action:

1. Check the NetBackup Problems report for clues on why the failure occurred.

2. On a UNIX system, check that /etc/services and NIS services map (if applicable) have entries for the NetBackup services: bpcd, bpdbm, and bprd.

3. On a Windows NT system, verify that the %SystemRoot%\system32\drivers\etc\services file shows the correct entries for the NetBackup internet processes: bpcd, bpdbm, and bprd.

Ensure that the NetBackup Client Service Port Number and NetBackup Request Service Port Number on the Network tab in the NetBackup Configuration dialog box match the settings in the services file. To display this dialog box, start the Backup, Archive, and Restore interface and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57). The values on the Network tab are written to the services file when the NetBackup Client service starts. Also, see "Verifying Host Names and Services Entries" on page 31.

4. Check the level of network activity. An overloaded network can cause this error.

5. If the above actions do not reveal the problem, create an activity log directory for the process that returned this status code, retry the operation, and check the resulting activity log.

21 22 23 24 25 26 27 28 29 Top

Status Code: 20 Top

Message: invalid command parameter

Explanation: One or more command parameters were not valid. This error can occur when a master and its slave servers or a master server and a client have different levels of NetBackup installed. For example, if a NetBackup master server has NetBackup 3.2 and the slave server has NetBackup 3.0. This error can also occur if the wrong parameters are used when executing a command line.

Recommended Action:

1. Check the NetBackup Problems report for clues.

2. If the error occurs when executing a command on the command line, verify that the parameters are valid.

3. Compare the NetBackup version level on the server to that on the clients:

o On UNIX NetBackup servers and clients, check the /usr/openv/netbackup/bin/version file.

o On Windows NT NetBackup servers, check the install_path\netbackup\version.txt file or the About NetBackup command on the Help menu.

o On Microsoft Windows clients, check the About NetBackup command on the Help menu.

o On NetWare target clients, check the Version entry in the bp.ini file. If the client software is earlier than 3.0, verify that the client is in a Standard type class.

o On Macintosh clients, check the version file in the bin folder in the NetBackup folder in the Preferences folder.

4. If the above actions do not reveal the problem, create an activity log directory for the process that returned this status code, retry the operation, and check the resulting activity log.

Status Code: 21 Top

Message: socket open failed

Explanation: A socket open failed.

Recommended Action:

1. Check the NetBackup Problems report for clues on where and why the failure occurred. If you cannot determine the cause from the Problems report, create activity log directories for the processes that returned this status code. Then, retry the operation and check the resulting activity logs.

2. On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the NetBackup Release Notes - UNIX).

3. On Windows NT, verify that the recommended service packs are installed.

Status Code: 22 Top

Message: socket close failed

Explanation: A socket could not be closed.

Recommended Action:

1. Check the NetBackup Problems report for clues on where and why the failure occurred. If you cannot determine the cause from the Problems report, create activity log directories for the processes that could have returned this status code. Then, retry the operation and check the resulting activity logs.

2. On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the NetBackup Release Notes - UNIX).

3. On Windows NT, verify that the recommended service packs are installed.

Status Code: 23 Top

Message: socket read failed

Explanation: A read operation from a socket failed.

Recommended Action:

1. Check the NetBackup Problems report for clues on where and why the failure occurred. If you cannot determine the cause from the Problems report, create activity log directories for the processes that could have returned this status code. Then, retry the operation and check the resulting activity logs.

2. Corrupt binaries are one possible cause for this error. For example, in one instance, the following was seen in the bpsched activity log.

get_num_avail_drives: readline failed: socket read failed (23)

get_stunits: get_num_avail_drives failed with stat 23

Loading a fresh bptm from the install media resolved the problem.

3. On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the NetBackup Release Notes - UNIX).

4. On Windows NT, verify that the recommended service packs are installed.

Status Code: 24 Top

Message: socket write failed

Explanation: A write operation to a socket failed.

Recommended Action:

1. Check the NetBackup Problems report for clues on where and why the failure occurred. If you cannot determine the cause from the Problems report, create activity log directories for the processes that could have returned this status code. Then retry the operation and check the resulting activity logs.

2. A possible cause could be a high network load. For example, this has been seen in conjunction with Cannot write to STDOUT when a Windows NT system that is monitoring network load has detected a high load and sent an ICMP packet to other systems that says the route being used by those systems was disconnected. The log messages were similar to the following:

01/31/96 14:05:23 ruble crabtree.null.com from client crabtree.null.com: ERR - Cannot write to STDOUT. Err no= 242: No route to host

01/31/96 14:05:48 ruble crabtree.null.com successfully wrote backup id crabtree.null.com_0823125016, copy 1, fragment 1, 440864 Kbytes at 628.538 Kbytes/sec

01/31/96 14:05:51 netbackup crabtree.null.com CLIENT crabtree.null.com CLASS Remote3SysFullW SCHED Sirius EXIT STATUS 24 (socket write failed)

3. On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the NetBackup Release Notes - UNIX).

4. On Windows NT, verify that the recommended service packs are installed.

Status Code: 25 Top

Message: cannot connect on socket

Explanation: A process timed out while connecting to another process for a particular operation. This problem can occur when a process tries to connect to the NetBackup request daemon (bprd) or database manager daemon (bpdbm) and the daemon is not running (On Windows NT, these daemons are the NetBackup Request Manager and NetBackup Database Manager services). It can also occur if the network or server is heavily loaded and has slow response time.

Recommended Action:

1. On a UNIX NetBackup master server, verify that the bprd and bpdbm processes are running. If these processes are not running, start them. On a Windows NT master server, verify that the NetBackup Request Manager and NetBackup Database Manager services are running. If these services are not running, start them.

If the above processes are running, examine the All Log Entries report for the time of the failure to determine where the failure occurred.

o If you cannot view the report, or you get a cannot connect on socket error when trying to view it, verify again that the NetBackup Database Manager daemon (or service) is running. Then, create an activity log directory for bpdbm, retry the operation, and check the resulting activity log.

o If you can view the report and have not found an entry related to this problem, create activity log directories for the related processes that were running when the error first appeared (this process will frequently be bpbrm). Then, retry the operation and check the resulting activity logs.

2. Verify that the server list specifies the correct master server.

o On Windows NT, 98, and 95 systems, the master server is designated as Current on the Servers tab in the NetBackup Configuration dialog box.

To display this dialog box, start the Backup, Archive, and Restore interface and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57).

o On UNIX, and Macintosh systems, the master server is the first SERVER entry in the bp.conf file.

o On NetWare target and OS/2 clients, the master server name is the first SERVER entry in the bp.ini file.

If you change the server list on a master server, stop and restart the NetBackup database manager and request daemons (UNIX) or the NetBackup Database Manager and NetBackup Request Manager services (Windows NT).

3. Check the services file.

On UNIX, verify that the /etc/services file (and NIS services if NIS is used) has entries for the NetBackup services: bpcd, bpdbm, and bprd. On Windows NT, verify that the %SystemRoot%\system32\drivers\etc\services file has the correct entries for bpcd, bpdbm, and bprd.

Also, verify that the NetBackup Client Service Port Number and NetBackup Request Service Port Number on the Network tab in the NetBackup Configuration dialog box match the settings in the services file. To display this dialog box, start the Backup, Archive, and Restore interface and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57). The values on the Network tab are written to the services file when the NetBackup Client service starts. Also, see "Verifying Host Names and Services Entries" on page 31.

4. On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the NetBackup Release Notes - UNIX).

5. On Windows NT, verify that the recommended service packs are installed.

Status Code: 26 Top

Message: client/server handshaking failed

Explanation: A process on the server encountered an error when communicating with the client. This error indicates that the client and server were able to initiate communications, but encountered difficulties in completing them. This problem can occur during a backup or a restore.

Recommended Action: Determine which activity encountered the handshake failure by examining the All Log Entries report for the appropriate time period. Determine the client and server that had the handshake failure.

For detailed troubleshooting information, create an activity log directory for the process that returned this status code, retry the operation, and check the resulting activity log.

Status Code: 27 Top

Message: child process killed by signal

Explanation: A child of the process reporting this error was killed. This can occur because the backup job was terminated or the child process was terminated by another error. This problem can also occur if a NetBackup process was terminated through Task Manager or another utility.

Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred. For detailed troubleshooting information, create an activity log directory for the process that you suspect of returning this status code. Then, retry the operation and check the resulting activity log.

Status Code: 28 Top

Message: failed trying to fork a process

Explanation: A fork of a child process failed (on UNIX) or a CreateProcess failed (on Windows NT). This may be due to:

· An overloaded system

· Insufficient swap space or physical memory

· Too many processes running on the system.

Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred. For detailed troubleshooting information, create activity log directories for the processes that you suspect of returning this status code. Then, retry the operation and check the resulting activity logs.

Status Code: 29 Top

Message: failed trying to exec a command

Explanation: A command could not be executed. This can occur because the permissions of the command do not allow it to be executed, or there is lack of system resources such as memory and swap space.

Recommended Action:

1. Check the NetBackup All Log Entries report for clues on where and why the failure occurred.

2. Check the permissions on the command to be executed.

3. For detailed troubleshooting information, create an activity log directory for the process that returned this status code, retry the operation, and check the resulting activity log.

31 32 33 34 35 36 37 38 39 Top

Status Code: 30 Top

Message: could not get passwd information

Explanation: Could not get the passwd entry for a user.

Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred. For detailed troubleshooting information, create an activity log for the process that you suspect of returning this status code. Then, retry the operation and check the resulting activity log.

Status Code: 31 Top

Message: could not set user id for process

Explanation: Could not set the user ID of a process to that of the requesting user. NetBackup executes client processes as the requesting user.

Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred. For detailed troubleshooting information, create an activity log directory for the process that you suspect of returning this status code. Then, retry the operation and check the resulting activity log.

Status Code: 32 Top

Message: could not set group id for process

Explanation: Could not set the group ID of a process to the requesting user group. NetBackup executes client processes with the group ID of the requesting user.

Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred. For detailed troubleshooting information, create an activity log directory for the process that you suspect of returning this status code. Then, retry the operation and check the resulting activity log.

Status Code: 33 Top

Message: failed while trying to send mail

Explanation: An E-mail notification of backup, archive, or restore results has failed. The E-mail could not be sent to the administrator's address as specified by the E-mail global attribute, or in the case of a UNIX client, an E-mail address specified with USEMAIL in the client's bp.conf file.

Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred. For detailed troubleshooting information, create an activity log directory for the process that you suspect of returning this status code. Then, retry the operation and check the resulting activity log.

Status Code: 34 Top

Message: failed waiting for child process

Explanation: The bpsched process encountered a failure while waiting for a child process to complete.

Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred. For detailed troubleshooting information, create an activity log for the process that you suspect of returning this status code. Then, retry the operation and check the resulting activity log.

Status Code: 35 Top

Message: cannot make required directory

Explanation: Could not create a required directory. Possible causes are:

· A process does not have permission to create the directory

· The path to the directory is not valid

· An IO error occurs

· There was no space available on the device containing the directory

Recommended Action:

1. Check the NetBackup All Log Entries report to determine which directory could not be created and why it could not be created. In particular, check for a full disk partition.

2. Check the permissions on the parent directory and verify that NetBackup services are started with a "Logon as" account that has permission to create the directory.

3. For detailed troubleshooting information, create an activity log directory for the process that returned this status code, retry the operation, and check the resulting activity log.

Status Code: 36 Top

Message: failed trying to allocate memory

Explanation: Allocation of system memory failed. This error occurs when there is insufficient system memory available. This could be caused by the system being overloaded with too many processes and there is not enough physical and virtual memory.

Recommended Action: Free up memory by terminating unneeded processes that consume a lot of memory. Add more swap space or physical memory.

Status Code: 37 Top

Message: operation requested by an invalid server

Explanation: A request was made to the NetBackup request daemon (bprd) or NetBackup database manager daemon (bpdbm) by an invalid slave server or Windows NT administration client. On Windows NT, these daemons are the NetBackup Request Manager and NetBackup Database Manager services.

Recommended Action:

Examine the NetBackup All Log Entries report for the time of this error to determine which system was trying to connect to the master server. If the server is a valid slave server, verify that the storage unit for the slave server is defined. Also, verify that the server or Windows NT administration client has a server list entry on the master server.

If necessary, update the server list. On a UNIX master server, add a SERVER = slave_server_name to the bp.conf file. slave_server_name is the host name of the slave server. On a Windows NT master server, start the Backup, Archive, and Restore interface. Then, click Configure on the Actions menu and add the slave server to the list on the Servers tab in the NetBackup Configuration dialog box (also, see "Using the Configure - NetBackup Window" on page 38).

If a server or Windows NT administration client has more than one host name (for example, if it has multiple network interfaces), verify that the master server has a server list entry for each of them.

If you change the server list on a UNIX master server, you must stop and then restart the NetBackup Request daemon (bprd) and NetBackup Database Manager daemon (bpdbm) for the changes to take effect. If you change the server list on a Windows NT master server, stop and then restart the NetBackup Request Manager and NetBackup Database Manager services.

Status Code: 38 Top

Message: could not get group information

Explanation: Could not get the group entry describing a UNIX user group.

Recommended Action: Check the NetBackup Problems report for clues on why the error occurred. For detailed troubleshooting information, create an activity log directory for the process that returned this status code, retry the operation, and check the resulting activity log.

Status Code: 39 Top

Message: client name mismatch

Explanation: The name that the client used in a request to the NetBackup server did not match the client name configured in the class on the server.

Recommended Action: Change either the NetBackup client name setting on the client (see the applicable NetBackup users guide) or the one in the class configuration on the server so the two match.

41 42 43 44 45 46 47 48 49 Top

Status Code: 40 Top

Message: network connection broken

Explanation: The connection between the client and the server was broken. This status code can also appear if the connection is broken between the master and slave server during a backup.

Recommended Action:

1. Try pinging the client from the server. If this is not possible, check for loose connections or other network problems.

2. Verify that the server list settings are correct on both the client and the server. If the backup involves a slave server, verify that these entries are correct on both the master and slave server. For example, if a slave server does not have a server list entry for the master, it does not accept connections from the master.

o On Windows NT, 98, and 95 systems, the master server is designated as Current on the Servers tab in the NetBackup Configuration dialog box. To display this dialog box, start the Backup, Archive, and Restore interface and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57).

o On UNIX, and Macintosh systems, the master server is the first SERVER entry in the bp.conf file.

o On NetWare target and OS/2 clients the master server name is the first SERVER entry in the bp.ini file.

If you change the server list on a UNIX master server, you must stop and then restart the NetBackup Request daemon (bprd) and NetBackup Database Manager daemon (bpdbm) for the changes to take effect. On Windows NT, stop and restart the NetBackup Request Manager and NetBackup Database Manager services.

3. Status code 40 can also be due to the operator denying a mount request.

Status Code: 41 Top

Message: network connection timed out

Explanation: The server did not receive any information from the client for too long a period of time.

Recommended Action:

1. On a UNIX or Windows NT clients, check for the following problems with the bpbkar client process.

o •The bpbkar client process is hung on a file that has mandatory locking set. For this case, add the following to the client's bp.conf file:

VERBOSE

and as root on the client execute:

touch /usr/openv/netbackup/bpbkar_path_tr

mkdir /usr/openv/netbackup/logs/bpbkar

Then retry the operation. The names of the files are logged in the activity log file in the /usr/openv/netbackup/logs/bpbkar directory before bpbkar processes them. The last file in the log will be the file that is causing problems.

Note: Also, use the above procedure for other, "unknown" bpbkar hangs. If the problem is due to mandatory file locking, you can have NetBackup skip the locked files by setting LOCKED_FILE_ACTION to SKIP in the /usr/openv/netbackup/bp.conf file on the client.

o •The bpbkar client process is not hung, but due to the files and directories it is scanning, it has not replied to the server within CLIENT_READ_TIMEOUT or CLIENT_CONNECT_TIMEOUT. This has been seen to occur during backups when directories have thousands of unmodified files; it has also been seen when backing up file systems or directories that reside on optical disk, which is considerably slower than magnetic disk.

For this case, try adding or modifying the CLIENT_READ_TIMEOUT and CLIENT_CONNECT_TIMEOUT values in the server's /usr/openv/netbackup/bp.conf file. The default for the CLIENT_READ_TIMEOUT and CLIENT_CONNECT_TIMEOUT is 300 seconds if unspecified.

Use your system's ps command and monitor CPU utilization to help decide which of the above conditions exist.

When you are through investigating the problem, delete the /usr/openv/netbackup/logs/bpbkar directory, since the log files can become quite large and are not deleted automatically. Also delete /usr/openv/netbackup/bpbkar_path_tr so you do not generate larger log files than needed the next time you create directory /usr/openv/netbackup/logs/bpbkar.

2. If the server cannot connect to the client, create bpcd or bpbkar (UNIX and Windows NT only) activity log directories on the client, retry the operation, and check the resulting logs. If these logs do not provide a clue, create a bpbrm activity log on the server, retry the operation again, and check the resulting activity log.

If the bpbrm log has entries similar to the following:

bpbrm hookup_timeout: timed out waiting during the client hookup

bpbrm Exit: client backup EXIT STATUS 41: network connection timed out

then the problem is in the routing configuration on the server. Verify that the client IP address is correct in the name service that is being used. On UNIX, if both NIS and DNS files are used, verify that they match. Also, see "Resolving Network Communication Problems" on page 21.

3. If you are using an AIX token ring adapter and the routed daemon is running, the timeout can occur because the token ring adapter creates dynamic routes, causing the routed daemon to crash.

4. For a FlashBackup client, this can happen if the file system being backed up is very large and has a very large number of files. It can also occur if a large number of concurrent data streams are active at the same time. The corrective action is to add CLIENT_READ_TIMEOUT to the /usr/openv/netbackup/bp.conf file and set it to increase the timeout interval.

Status Code: 42 Top

Message: network read failed

Explanation: An attempt to read data from a socket failed.

Recommended Action:

1. Verify that both the client and the server are operational.

2. Perform "Resolving Network Communication Problems" on page 21.

3. Check the Problems report for clues.

Status Code: 43 Top

Message: unexpected message received

Explanation: The client and server handshaking was not correct.

Recommended Action:

1. Verify that the correct version of software is running on the client and the server.

2. Enable detailed activity logging:

o On the server, create a bpbrm activity log directory.

o On clients, create a bpcd activity log directory (created automatically on Macintosh clients).

o Increase the amount of debug information included in the logs as explained in the activity log topics in Chapter 3, "Using the Logs and Reports."

3. Retry the operation and examine the logs.

Note: If you are using bpstart_notify scripts on UNIX or Windows NT clients, verify that messages are not being written to stdout or stderr.

Status Code: 44 Top

Message: network write failed

Explanation: An attempt to write data to a socket failed.

Recommended Action:

1. Check the Problems report for information about the error.

2. Verify that the client and servers are operational and connected to the network.

3. Create an activity log directory for the process that reported the problem and the operation. Examine the resulting activity log file for detailed troubleshooting information.

4. Perform "Resolving Network Communication Problems" on page 21.

Status Code: 45 Top

Message: request attempted on a non reserved port

Explanation: An attempt was made to access a client from a nonreserved port.

Recommended Action: Verify that the latest software is installed on the client and server.

· On UNIX NetBackup servers and clients, check the /usr/openv/netbackup/bin/version file.

· On Windows NT NetBackup servers, check the install_path\netbackup\version.txt file or the About NetBackup command on the Help menu.

· On Microsoft Windows clients, check the About NetBackup command on the Help menu.

· On NetWare target clients, check the Version entry in the bp.ini file.

· If this is a NetBackup for NetWare client and has a version of NetBackup earlier than 3.0, verify that the client is in a Standard type class.

· On Macintosh clients, check the version file in the bin folder in the NetBackup folder in the Preferences folder.

Status Code: 46 Top

Message: server not allowed access

Explanation: The server is trying to access the client but the server is not listed on the client as a valid server.

Recommended Action: If the server is a valid server, add its name to the client's server list:

· On Windows NT, 98, and 95 clients, add the server on the Servers tab in the NetBackup Configuration dialog box. To display this dialog box, start the Backup, Archive, and Restore interface on the client and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57).

· On UNIX, and Macintosh clients, add a SERVER entry in the bp.conf file. • On NetWare target and OS/2 clients add a SERVER entry in the bp.ini file.

If you continue to have problems, review "Resolving Network Communication Problems" on page 21 and "Verifying Host Names and Services Entries" on page 31.

Status Code: 47 Top

Message: host is unreachable

Explanation: An attempt to connect to another machine failed.

Recommended Action:

1. Verify that the name service (or services) being used by the client is configured to correctly resolve the host names of the NetBackup server.

2. Verify that the name service (or services) being used by the server is configured to correctly resolve the host name of the NetBackup client.

3. Try to ping the client from the server and the server from the client.

4. If you continue to have problems, perform "Resolving Network Communication Problems" on page 21.

Status Code: 48 Top

Message: client hostname could not be found

Explanation: The system function gethostbyname() failed to find the client's host name.

Recommended Action:

1. Verify that the client name is correct in:

o The NetBackup class configuration on the master server.

o The General and Clients tabs in the NetBackup Configuration dialog box on Microsoft Windows and NetWare nontarget clients. To display this dialog box, start the Backup, Archive, and Restore interface on the client and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57).

o The bp.conf file on UNIX and Macintosh clients.

o The bp.ini file on OS/2 and NetWare target clients.

2. On clients and servers, verify that the name service is set up to correctly resolve the NetBackup client names. On UNIX clients, verify that the client's host name is in the /etc/hosts file or the YP hosts file or NIS maps.

Status Code: 49 Top

Message: client did not start

Explanation: The client failed to start up correctly.

Recommended Action:

1. Verify that software is installed on the client and it is the correct version. If necessary, reinstall the client software.

2. Check for full file systems on the client.

3. Enable detailed activity logging on the client:

o Create bpcd and bpbkar (UNIX or Windows NT only) activity log directories.

o On a UNIX client, add the VERBOSE option to the /usr/openv/netbackup/bp.conf file.

o On PC clients, increase the debug or log level as explained in the activity log topics in Chapter 3, "Using the Logs and Reports."

4. Retry the operation and examine the resulting logs.

5. On UNIX systems, use the UNIX sum command to check for corrupt binaries.

51 52 53 54 55 56 57 58 59 Top

Status Code: 50 Top

Message: client process aborted

Explanation: The client backup aborted. One instance when this code appears is if a NetBackup master or slave server is shut down or rebooted when a backup or restore is in process.

Recommended Action:

1. Enable detailed activity logging:

o Create a bpbkar activity log directory (UNIX or Windows NT only).

o Create a bpcd activity log directory (this log is created automatically on Macintosh clients.

o On UNIX clients, add the VERBOSE option to the /usr/openv/netbackup/bp.conf file.

o On PC clients, increase the debug or log level as explained in the activity log topics in Chapter 3, "Using the Logs and Reports."

2. Retry the operation and examine the resulting logs.

3. On UNIX clients, check for core files in the / directory.

4. On UNIX clients, check the system log (/usr/adm/messages on Solaris) for system problems.

5. This problem can sometimes be due to a corrupt binary.

On UNIX clients, use the UNIX sum command to check the bpcd, bpbkar, and tar binaries, located in /usr/openv/netbackup/bin on the client. Reinstall them if they are not the same as in the client directory under /usr/openv/netbackup/client on the server.

On a Windows NT client, check the bpinetd.exe, bpcd.exe, bpbkar32.exe, and tar32.exe executables located in the install_path\NetBackup\bin folder on the client. Reinstall the client if these executables are not the same size as on other Windows NT clients or are not at the same release level or do not have the same NetBackup patches applied as other Windows NT clients.

Status Code: 51 Top

Message: timed out waiting for database information

Explanation: The database process did not respond within five minutes.

Recommended Action:

1. Verify that the NetBackup Database Manager daemon (service on Windows NT) is running.

2. Verify that there is space in the file system that contains the NetBackup databases.

3. Create bpbrm and bpdbm activity log directories on the server and retry the operation.

4. Look in the activity log files to find more information on the problem.

Status Code: 52 Top

Message: timed out waiting for media manager to mount volume

Explanation: The requested volume was not mounted before the timeout expired. This error can also occur if the volume happens to be a cleaning tape but was not specified as a cleaning tape.

Recommended Action:

1. Verify that the requested volume is available and an appropriate drive is ready and in the UP state.

2. If this occurs during a read operation (restore, duplicate, verify), the drives could be busy. Try increasing the media mount timeout specified by the NetBackup global attribute in order to allow more time for mounting and positioning the media.

3. Verify that the tape is not a cleaning tape that is configured as a regular volume.

4. When the robot is controlled by an Automated Cartridge System, verify that the ACSLS system is up.

5. If this is an initial installation, refer to "Common Configuration Problems" in chapter 2.

6. On Windows NT, check the Event Viewer Application log for error messages that indicate why the tape mount did not complete. On UNIX, check the system log.

Status Code: 53 Top

Message: backup restore manager failed to read the file list

Explanation: The backup and restore manager (bpbrm) could not read the list of files to back up or restore.

Recommended Action: Verify that the server software has been installed correctly on the master server and all slave servers. If that is not the problem:

1. Create bpbrm and bpsched activity log directories on the server.

2. On a UNIX NetBackup server, add the VERBOSE option to the bp.conf file. On a Windows NT NetBackup server, set the Verbose option on the Troubleshooting tab in the NetBackup Configuration dialog box. To display this dialog box, start the Backup, Archive, and Restore interface on the server and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57).

3. Retry the operation and check the resulting activity logs for detailed troubleshooting information.

Status Code: 54 Top

Message: timed out connecting to client

Explanation: The server could not complet e the connection to the client. The accept system call timed out after 60 seconds.

Recommended Action:

1. For a Macintosh or NetWare target client, verify that the server is not trying to connect when a backup or restore is already in progress on the client. These clients can handle only one NetBackup job at a time.

On a Macintosh, you can check for activity by examining the NetBackupListen file in the following folder on the startup disk of the Macintosh client: :System Folder:Preferences:NetBackup:logs:inetd:log.mmddyy

2. On a Sequent platform, verify that the system has the correct level of TCP/IP.

3. Perform "Resolving Network Communication Problems" on page 21.

4. On UNIX clients, verify that the /usr/openv/netbackup/bin/bpcd binary exists and that it is the correct size.

Status Code: 55 Top

Message: permission denied by client during rcmd

Explanation: The UNIX client does not have the server's name in its /.rhosts file.

Recommended Action: Add the server name to the /.rhosts file on the UNIX client.

Status Code: 56 Top

Message: client's network is unreachable

Explanation: The server got ENETUNREACH when trying to connect to the client.

Recommended Action: Try to ping the client from the server. Check the IP address for the client. If you still have problems, talk to your network administrator.

Status Code: 57 Top

Message: client connection refused

Explanation: The client refused a connection on the port number for bpcd. This can occur because there is no process listening on the bpcd port or there are more connections to the bpcd port than the network subsystem can handle with the listen() call.

Recommended Action:

1. For Windows NT NetBackup servers:

a. Verify that the bpcd and bprd port numbers in the %SystemRoot%\system32\drivers\etc\services file on the server matches the setting on the client.

b. Verify that the NetBackup Client Service Port Number and NetBackup Request Service Port Number on the Network tab in the NetBackup Configuration dialog box match the bpcd and bprd settings in the services file. To display this dialog box, start the Backup, Archive, and Restore interface on the server and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57). The values on the Network tab are written to the services file when the NetBackup Client service starts.

c. Verify that the NetBackup Client service is running.

2. For UNIX servers, verify that the bpcd port number on the server (either NIS services map or in /etc/services) matches the number in the client's services file.

3. For a Macintosh or NetWare target client, verify that the server is not trying to connect when a backup or restore is already in progress on the client. These clients can handle only one NetBackup job at a time.

4. Perform "Resolving Network Communication Problems" on page 21.

Status Code: 58 Top

Message: can't connect to client

Explanation: The server was unable to connect to the client.

Recommended Action: Perform "Resolving Network Communication Problems" on page 21.

Status Code: 59 Top

Message: access to the client was not allowed

Explanation: The master or slave server is trying to access the client, but the server is not recognized by the client as a valid server.

Recommended Action:

1. If the server is a valid server, verify that it is in the server list on the client. If necessary add it as follows:

o On Windows NT, 98, and 95 clients, add the server on the Servers tab in the NetBackup Configuration dialog box. To display this dialog box, start the Backup, Archive, and Restore interface on the client and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57).

o On UNIX, and Macintosh clients, add a SERVER entry in the bp.conf file.

o On NetWare target and OS/2 clients add a SERVER entry in the bp.ini file.

If you change the server list on a UNIX master server, you must stop and then restart the NetBackup Request daemon (bprd) and NetBackup Database Manager daemon (bpdbm) for the changes to take effect. On Windows NT, stop and restart the NetBackup Request Manager and NetBackup Database Manager services.

2. On Windows NT clients, enable bpinetd activity logging as follows:

a. Create a bpinetd activity log directory on the client.

b. Increase the debug or log level as explained in the activity log topics in Chapter 3, "Using the Logs and Reports."

c. Retry the backup and examine the resulting logs to determine the cause of the failure.

1. On all but Macintosh clients, enable bpcd activity logging as follows:

a. Create a bpcd activity log directory on the client.

b. On a UNIX client, add the VERBOSE option to the /usr/openv/netbackup/bp.conf file.

c. On PC clients, increase the debug or log level as explained in the activity log topics in Chapter 3, "Using the Logs and Reports."

d. Retry the backup and examine the resulting logs to determine the cause of the failure.

2. On Macintosh clients, check the inetd and bpcd activity logs. Both logs are created automatically.

o Check the inetd log to see if NetBackupListen is running.

o Check the bpbkar and tar messages in the bpcd log file. To increase the amount of information included in the logs, set the loglevel parameter in the mac.conf file to a higher value.

1. Check the bpcd activity log to determine the server's peername and what comparisons are being made. The bpcd process compares NetBackup server list entries to the peername of the server attempting the connection and rejects the connection if the names are different. If necessary, change the server list entry on the client to match the peername.

2. On Windows NT clients, check the following:

o Verify that NetBackup for Windows NT software was installed under a Windows NT administrator account.

If NetBackup is under another type of account, reinstall it under an administrator account. The installation will complete successfully under a non-administrator account but the NetBackup Client service is not added to Windows NT and the NetBackup server cannot access the client.

o Verify that the Windows NT TCP/IP service specifies the domain server that resolves names for the subnet that contains the NetBackup servers. UNIX and Windows NT clients are frequently not on the same subnet and use different domain servers. When this condition exists the NetBackup servers and Windows NT clients may be able to ping one another, but the server is still unable to access the Windows NT client.

3. If the preceding steps do not resolve this problem, see "Resolving Network Communication Problems" on page 21.

61 62 63 64 65 66 67 68 69 Top

Status Code: 60 Top

Message: client cannot read the mount table

Explanation: The backup process on the client could not read the list of mounted file systems.

Recommended Action:

1. Execute a df to see if the system can read the mount table.

2. On an SCO system, code 60 can occur because the mount-point path name exceeds 31 characters, which is the maximum allowed on an SCO system. The bpbkar activity log on the client will show a message similar to the following:

bpbkar build_nfs_list: FTL - cannot statfs net Errno: 42406

To eliminate these errors for future backups, create a mount point with a shorter name and symbolically link the long name to the short name.

3. For detailed troubleshooting information, create a bpbkar activity log directory, retry the operation, and examine the resulting log.

Status Code: 61 Top

Message: wbak was killed

Explanation: The wbak process on the Apollo was killed.

Recommended Action: Try the backup again.

Status Code: 62 Top

Message: wbak exited abnormally

Explanation: The wbak process on the Apollo exited abnormally.

Recommended Action: Try running wbak by hand to determine the source of the problem. Direct the output of the wbak command to /dev/null to avoid filling up your file system and use the following parameters:

-l -nhi -pdtu -stdout -nwla and -full or -af date

Status Code: 63 Top

Message: process was killed by a signal

Explanation: A kill signal was sent to the client process.

Recommended Action: This is usually caused by someone intentionally terminating a backup.

Status Code: 64 Top

Message: timed out waiting for the client backup to start

Explanation: The client did not send a ready message to the server within the allotted time.

Recommended Action:

1. 1. On all but Macintosh clients, enable bpcd activity logging as follows:

a. Create a bpcd activity log directory on the client.

b. On a UNIX client, add the VERBOSE option to the /usr/openv/netbackup/bp.conf file.

c. On PC clients, increase the debug or log level as explained in the activity log topics in Chapter 3, "Using the Logs and Reports."

2. 2. On Macintosh clients, check the inetd and bpcd activity logs. Both logs are created automatically.

o Check the inetd log to see if NetBackupListen is running.

o Check the bpbkar and tar messages in the bpcd log file. To increase the logging level, set the loglevel parameter in the mac.conf file to a higher value.

1. On a UNIX or Windows NT client, create the bpbkar activity log directory on the client.

2. On Windows NT clients, verify that the NetBackup Client service is running.

3. On a UNIX client, use the ps command to check for a client process that is using too much CPU time.

4. Retry the backup and examine the activity logs for clues on the cause of the failure.

Status Code: 65 Top

Message: client timed out waiting for the continue message from the media manager.

Explanation: The tape manager, bptm reported that the media did not load and position within the allotted time.

Recommended Action: Verify that the requested volume is available and the required device is in an UP state.

For detailed debug information:

1. Create a bptm activity log directory on the server.

2. On a UNIX NetBackup server, add the VERBOSE option to the bp.conf file. On a Windows NT NetBackup server, set the Verbose option on the General tab in the Master Server Properties dialog box (see "Using the Configure - NetBackup Window" on page 57).

3. Retry the operation and check the bptm activity log file for information on the drive, robot, and tape that is causing the timeout.

4. On a Windows NT NetBackup server (master or slave), check the Event Viewer Application log for error messages that indicate why the tape mount did not complete.

Status Code: 66 Top

Message: client backup failed to receive the CONTINUE BACKUP message

Explanation: The client bpbkar process did not receive the message from the server that indicates that the server is ready to continue.

Recommended Action:

Verify that the server did not crash. If that is not the problem and you need more information:

1. On UNIX and Windows NT clients, enable bpbkar activity logging.

a. Create a bpbkar activity log directory.

b. On a UNIX client, add the VERBOSE option to the bp.conf file. On a Windows NT client, set Verbose on the Troubleshooting tab in the NetBackup Configuration dialog box. To display this dialog box, start the Backup, Archive, and Restore interface on the client and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57).

2. On other PC clients except Macintosh, create an activity log directory for bpcd (the bpcd log is created automatically on Macintosh). To increase the amount of information that appears in the logs, see the logging topics in Chapter 3, "Using the Logs and Reports."

3. On the master server create bpsched and bpbrm activity log directories. If there are slave servers involved, create a bpbrm activity log directory on them.

4. Retry the operation and check the resulting activity logs.

Status Code: 67 Top

Message: client backup failed to read the file list

Explanation: The client could not read the list of files to back up.

Recommended Action: First, verify that the server did not crash. If that is not the problem and you need more information:

1. Set up activity logging:

a. On the server, create a bpbrm activity log directory.

b. On UNIX and Windows NT clients, create a bpbkar activity log directory.

c. On other PC clients except Macintosh, create an activity log directory for bpcd (the bpcd log is created automatically on Macintosh). To increase the amount of information that appears in the logs, see the logging topics in Chapter 3, "Using the Logs and Reports."

2. Retry the operation and check the resulting activity logs.

Status Code: 68 Top

Message: client timed out waiting for the file list

Explanation: The client did not receive the list of files to back up within the allotted time. This list comes from the server.

Recommended Action: First, verify that the server did not crash. If that is not the problem and you need more information:

1. Set up activity logging:

a. On the server, create a bpbrm activity log directory.

b. On UNIX and Windows NT clients, create a bpbkar activity log directory.

c. On other PC clients except Macintosh, create an activity log directory for bpcd (the bpcd log is created automatically on Macintosh). To increase the amount of information that appears in the logs, see the logging topics in Chapter 3, "Using the Logs and Reports."

2. Retry the operation and check the resulting activity logs.

Status Code: 69 Top

Message: invalid file list specification

Explanation: The file list received from the server had invalid entries.

Recommended Action: Check the class file list. If wildcards are used, verify there are matching bracket characters ([ and ]). If the file list contains UNC (Universal Naming Convention) names, ensure they are properly formatted.

71 72 73 74 75 76 77 78 Top

Status Code: 70 Top

Message: an entry in the file list expanded to too many characters

Explanation: The wildcards used in one of the file list entries caused too many files to be specified.

Recommended Action: Change the wildcards in the file list to specify fewer files.

Status Code: 71 Top

Message: none of the files in the file list exist

Explanation: The files in the file list did not match any of the files on the client. This error can occur when there is only one file in the file list and the file cannot be backed up due to an I/O error.

Recommended Action:

1. Verify that the correct file list is specified for this client.

2. On Windows NT clients, verify that the account used to start the NetBackup Client service has read access to the files.

If you are backing up a network drive or a UNC (universal naming convention) path, use the Services application in the Windows NT Control Panel to verify that the NetBackup Client service does not start under the SYSTEM account. The SYSTEM account cannot access network drives. To back up network drives or UNC paths, change the NetBackup Client service startup to log in as a user that has permission to access network drives.

3. Check the All Log Entries report for clues.

4. Set up activity logging:

o • On UNIX and Windows NT clients, create an activity log directory for bpbkar.

o • On other PC clients except Macintosh, create an activity log directory for bpcd (the bpcd log is created automatically on Macintosh).

To increase the amount of information that appears in the logs, see the logging topics in Chapter 3, "Using the Logs and Reports."

5. Retry the operation and check the resulting activity logs.

Status Code: 72 Top

Message: the client type is incorrect in the configuration database

Explanation: The class type attribute in the class configuration indicates that the client is one type, but the installed software is for another type.

Recommended Action: Verify that the class type attribute for the class is correct. Also, for UNIX, do not place Apollo and standard clients in the same class.

Status Code: 73 Top

Message: bpstart_notify failed

Explanation: The bpstart_notify script returned a nonzero exit code.

Recommended Action: Check the bpstart_notify script on the client to see if it performs as desired.

Status Code: 74 Top

Message: client timed out waiting for bpstart_notify to complete

Explanation: The bpstart_notify script on the client took too long.

Recommended Action: Try to speed up the bpstart_notify script or set the BPSTART_TIMEOUT on the server to a value that is larger than the default.Set BPSTART_TIMEOUT in the bp.conf file on a UNIX NetBackup server. On a Windows NT NetBackup server, use the Configure - NetBackup window to set Backup Start Timeout (see "Using the Configure - NetBackup Window" on page 57).

Status Code: 75 Top

Message: client timed out waiting for bpend_notify to complete

Explanation: The bpend_notify script on the client took too long.

Recommended Action: Try to speed up the bpend_notify script or set BPEND_TIMEOUT on the server to a value that is larger than the default. Set BPEND_TIMEOUT in the bp.conf file on a UNIX NetBackup server. On a Windows NT NetBackup server, use the Configure - NetBackup window to set Backup End Timeout.

Status Code: 76 Top

Message: client timed out reading file

Explanation: A fifo was specified in the file list and no data was produced on the fifo within the allotted time.

Recommended Action:

1. Verify that the process produces the data on the named fifo is started correctly.

2. Set the CLIENT_READ_TIMEOUT option on the server to a value that is larger than the default. The CLIENT_READ_TIMEOUT option is in the bp.conf file on a UNIX NetBackup server and in the registry on a Windows NT NetBackup server.

Status Code: 77 Top

Message: execution of the specified system command returned a nonzero status

Explanation: An immediate command returned a nonzero status.

Recommended Action:

1. Verify that the command is specified correctly.

2. Execute the command manually to see if the desired result is produced.

3. For detailed troubleshooting information, set up activity logging:

a. On UNIX and Windows NT clients, create an activity log directory for bpbkar.

b. On other PC clients except Macintosh, create an activity log directory for bpcd (the bpcd log is created automatically on Macintosh). To increase the amount of information that appears in the logs, see the logging topics in Chapter 3, "Using the Logs and Reports."

c. Retry the operation and check the resulting activity log.

Status Code: 78 Top

Message: afs/dfs command failed

Explanation: Indicates an AFS vos command failure.

Recommended Action:

1. Check the NetBackup Problems Report for additional information on why the command failed.

2. The bpbkar activity log shows the command that was executed. Create an activity log directory for bpbkar. Retry the operation and retry the resulting activity log.

3. Try executing the vos command manually to duplicate the problem.

81 82 83 84 85 86 87 88 Top

Status Code: 80 Top

Message: Media Manager device daemon (ltid) is not active

Explanation: If the server is UNIX, the The Media Manager device daemon,ltid, is not running. If the server is Windows NT, the NetBackup Device Manager service is not running.

Recommended Action:

1. On Windows NT, use the Activity Monitor or the Services application in the Windows NT Control Panel to see if the NetBackup Device Manager service is running. If it is not running, start it. To enable verbose logging, place VERBOSE on a line by itself in the install_path\Volmgr\vm.conf file before starting the service.

2. On UNIX, use vmps to see if ltid is running and if necessary start it in verbose mode with the following command:

/usr/openv/volmgr/bin/ltid -v

Or, add a VERBOSE entry to the Media Manager configuration file, /usr/openv/volmgr/vm.conf. Create the vm.conf file if necessary.

3. On UNIX, check the system logs to verify that ltid starts.

Note: ltid or the NetBackup Device Manager service is used only if devices are attached to the system.

Status Code: 81 Top

Message: Media Manager volume daemon (vmd) is not active

Explanation: The tape manager (bptm) could not communicate with the NetBackup Volume Manager service (Windows NT) or the Media Manager volume daemon (UNIX). This communication is required for most operations.

Recommended Action:

On UNIX:
Verify that the Media Manager device daemon (ltid) and the volume daemon (vmd) are running. Start them if necessary.

On Windows NT:
Verify that both the NetBackup Device Manager service and the NetBackup Volume Manager service are running. Start them if necessary.

Note: ltid or the NetBackup Device Manager service is used only if devices are attached to the system.

Status Code: 82 Top

Message: media manager killed by signal

Explanation: The tape manager (bptm) or disk manager (bpdm) was terminated by another process or a user.

Recommended Action: This should not occur in normal operation. If you want to terminate an active backup, use the NetBackup Activity Monitor (on Windows NT) or the job monitor (on UNIX).

When backing up a DomainOS client (for example, Apollo), this has been seen to occur after the server has not received anything on the socket for at least 300 seconds, thus causing a client read timeout and breaking the connection. The bpbkar activity log had an entry similar to the following:

13:22:49 [1347] <16> bpbkar: ERR - Extra output - - ECONNRESET

Connection reset by peer (UNIX/errno status)

Increasing the CLIENT_READ_TIMEOUT value (in this instance to 900) has resolved this problem.

Status Code: 83 Top

Message: media open error

Explanation: The tape manager (bptm) or disk manager (bpdm) could not open the device or file that the backup or restore must use.

Recommended Action:

1. For additional information, check the following:

o NetBackup Problems report

o System log (UNIX)

o Event Viewer Application log (Windows NT)

2. Typically, this status code indicates a drive configuration problem that allows more than one process at a time to open the device.

On UNIX, the problem could be due to:

o Two (or more) devices were configured that are really the same physical device (for different densities perhaps). Verify that none of the /dev files used for these devices have the same major or minor numbers.

o Links exist in the file system that are allowing users access to the drives.

o The physical configuration for the drives was modified (xdevadm, tpconfig, or vm.conf) and the Media Manager device daemon, ltid, was not restarted. Verify the configuration and start ltid.

On Windows NT, the problem could be that the Media Manager device configuration was modified but the NetBackup Device Manager service was not restarted. Verify the configuration and restart the NetBackup Device Manager service.

3. For detailed troubleshooting information:

a. Create an activity log directory for bpdm (if the device is disk) or bptm (if the device is tape).

b. On UNIX, restart ltid in the verbose mode by executing: /usr/openv/volmgr/bin/ltid -v

Or, add a VERBOSE entry to the Media Manager configuration file, /usr/openv/volmgr/vm.conf. Create the vm.conf file if necessary.

c. On Windows NT, enable verbose logging by adding VERBOSE on a line by itself in the install_path\Volmgr\vm.conf file. Then, stop and restart the NetBackup Device Manager service.

d. Retry the operation and check the resulting activity log files.

Status Code: 84 Top

Message: media write error

Explanation: The system's device driver returned an I/O error while NetBackup was writing to removable media or a disk file.

Recommended Action:

1. For additional information, check the following:

o NetBackup Problems report to determine the device or media that caused the error

o System and error logs for the system (UNIX)

o Event Viewer Application and System logs (Windows NT)

2. If NetBackup was writing backups to a disk file, verify that the disk has enough space for the backup.

For NetBackup database backup to a disk path on a UNIX system, you may be trying to write a image greater than two gigabytes. File sizes greater than two gigabytes is a limitation on many UNIX file systems. Tape files do not have this limit.

3. If the media is tape or optical disk, check for:

o A defective or dirty drive, in which case, clean it or have it repaired (refer to the tpclean command for robotic drives).

o The wrong media type. Verify that the media matches the drive type you are using. On an optical drive, the platters may not be formatted correctly.

o Defective media. If this is the case, use the bpmedia command to set the volume to the FROZEN state so it is not used for future backups.

o Incorrect drive configuration. Verify the Media Manager and system configuration for the drive.

For example, on UNIX the drive could be configured for fixed mode when it must be variable mode. See the Media Manager Device Configuration Guide for more information.

Status Code: 85 Top

Message: media read error

Explanation: The system device driver returned an I/O error while NetBackup was reading from tape, optical disk, or a disk file.

Recommended Action:

1. For additional information, check the following:

• NetBackup Problems report to determine the device or media that caused the error

• System and error logs for the system (UNIX)

• Event Viewer Application and System logs (Windows NT)

2. Check for the following:

• A defective or dirty drive. Clean it or have it repaired (see the tpclean command for cleaning).

• Incorrect drive configuration. Verify the Media Manager and system configuration for the drive.

For example, on UNIX the drive could be configured for fixed mode when it must be variable mode. See the Media Manager Device Configuration Guide for more information.

• Defective media. In this case, you may not be able to recover all the data on the media. Use the bpmedia command to set the volume to the FROZEN state so it is not used for future backups.

• The wrong media type. Verify that the media matches the drive type you are using.

Status Code: 86 Top

Message: media position error

Explanation: The system's device driver returned an I/O error while NetBackup was positioning media (tape or optical disk).

Recommended Action:

1. For additional information, check the following:

• NetBackup Problems report to determine the device or media that caused the error

• System and error logs for the system (UNIX)

• Event Viewer Application and System logs (Windows NT)

2. Check for the following:

• A defective or dirty drive. Clean it or have it repaired (see the tpclean command for cleaning).

• Incorrect drive configuration. Verify the Media Manager and system configuration for the drive.

For example, on UNIX the drive could be configured for fixed mode when it must be variable mode. See the Media Manager Device Configuration Guide for more information.

• Defective media. In this case, some data may be lost. Use the bpmedia command to set the volume to the FROZEN state so it is not used for future backups.

• The wrong media type. Verify that the media matches the drive type you are using.

Status Code: 87 Top

Message: media close error

Explanation: The system's device driver returned an I/O error while NetBackup was closing a tape or optical disk.

Recommended Action:

1. For additional information, check the following:

• NetBackup Problems report to determine the device or media that caused the error

• System and error logs for the system (UNIX)

• Event Viewer Application and System logs (Windows NT)

2. Check for the following:

• A defective or dirty drive. Clean it or have it repaired (see the tpclean command for cleaning).

• Defective media. In this case, some data may be lost. Use the bpmedia command to set the volume to the FROZEN state so it is not used for future backups.

Status Code: 88 Top

Message: Auspex SP/Backup failure

Explanation: NetBackup detected a problem when backing up an Auspex FastBackup client.

Recommended Action: Check the All Log Entries report. If more details are required, create bptm and bpbrm activity log directories on the server. Then, retry the operation and check the resulting log files. This error is usually due to a configuration problem.

91 92 93 94 95 96 97 98 99 Top

Status Code: 90 Top

Message: media manager received no data for backup image

Explanation: The tape manager (bptm) or disk manager (bpdm) received no data when performing a backup or archive. This can occur for incremental backups where no data was backed up because no files have changed.

Recommended Action:

1. For additional information, check the following:

• NetBackup Problems report to determine the device or media that caused the error

• System and error logs for the system (UNIX)

• Event Viewer Application log (Windows NT)

2. Verify the Media Manager and system configuration for the drive.

For example, on UNIX the drive may not be set for variable mode in a case where that mode is required by NetBackup. Check the Media Manager Device Configuration Guide for drive configuration information.

3. Verify that the Media Manager configuration for the backup device matches what is specified for the storage unit in the NetBackup class.

4. Verify that you are using the correct media in the drive.

5. For detailed debug information, create a bpdm or bptm activity log directory (whichever applies) on the server. If the client is Windows NT, also create a bpbkar activity log directory on the client. Retry the operation and check the resulting activity logs. Retry the operation. Check the resulting activity log file.

Status Code: 91 Top

Message: fatal NB media database error

Explanation: The tape manager (bptm) received an error while reading or updating its media database.

Recommended Action:

1. Check the All Log Entries report for more information.

2. Check the NetBackup Media Lists report to see if the database is intact. If the database is not intact, consider reloading it from the latest NetBackup database backup volume.

3. Verify that the disk partition on which the database resides has enough space.

4. If the above actions do not explain the problem, check the NetBackup Problems report.

5. For detailed troubleshooting information, create a bptm activity logdirectory on the server and retry the operation. Check the resulting activity log file.

6. Contact customer support and send appropriate problem and activity log sections.

Status Code: 92 Top

Message: media manager detected image that was not in tar format

Explanation: When performing a restore, the tape manager (bptm) or disk manager (bpdm) could not find a tar header at the offset it expected.

Recommended Action:

1. Perform a bpverify of the affected image to determine if it is written correctly.

2. Check the NetBackup Problems report for additional information about the error.

3. Verify the Media Manager and system configuration for the drive. For example, on some UNIX systems, for example, if you do not configure the drive for variable-mode block size writes, backup images written to the media produce this error when an attempt is made to restore the image. For example, you see the following sequence of events:

• Backup succeeds

• Verify succeeds

• Restore fails

The bptm activity log shows an error similar to

00:58:54 [2304] <16> write_data: write of 32768 bytes indicated only 29696 bytes were written, errno = 0

In this case, configure the drive for variable-mode block sizes and suspend media written on that device. See the NetBackup Device Configuration Guide.

The images written to those media may be restorable (this is platform dependent), but single file restores are almost guaranteed to fail. You can choose to expire these media and regenerate the backups, or you can attempt to duplicate the images on these media to another device and then expire the original copy.

4. Error code 92 has been encountered on some relabeled and value-added 8-mm tape drives where the drive's microcode incorrectly processes a "forward space record" SCSI command.

5. If the problem is not one of the above, create an activity log directory for either bpdm or bptm and retry the operation. Check the resulting activity log file.

Status Code: 93 Top

Message: media manager found wrong tape in drive

Explanation: When loading a volume for a backup or restore, the tape manager (bptm) found a volume loaded that did not have the expected tape header. This can indicate that volumes in a robot are not in the slots indicated in the Media Manager volume configuration.

Recommended Action:

• If the volume is in a robot and the robot supports barcodes, perform a Compare Contents with Volume Configuration (Verify Robot Contents on UNIX). The resulting report shows which media ID was found and validates its slot number with what is in the Media Manager volume configuration. Then, either change the physical location in the robot or change the volume configuration to show the correct slot.

• If the volume was mounted on a nonrobotic drive, verify that the correct volume was mounted and assigned.

Status Code: 94 Top

Message: cannot position to correct image

Explanation: When searching for a backup image to restore, the tape manager (bptm) did not find the correct backup ID at the expected position on the volume. This can indicate a drive hardware problem.

Recommended Action:

1. Try the restore on another drive if possible.

2. For additional information, check the following:

• NetBackup Problems report to determine the device or volume thatcaused the error

• System and error logs for the system

• Event Viewer Application and System logs (Windows NT)

3. For detailed troubleshooting information, create an activity log directory for bptm and retry the operation. Check the resulting activity log files.

Status Code: 95 Top

Message: requested media id not found in NB media database and/or MM volume database

Explanation: An operation was requested on a media ID for which NetBackup does not have a record. An example of this is using bpmedia to suspend or freeze a media ID that does not exist.

Recommended Action: Run a NetBackup Media List report to determine the valid media IDs. Then, retry the command with a valid media ID.

Status Code: 96 Top

Message: unable to allocate new media for backup, storage unit has none available

Explanation: The tape manager (bptm) could not allocate a new volume for backups. This indicates that the storage unit has no more volumes available in the volume pool for this backup.

Recommended Action:

Check the NetBackup Problems report to determine the storage unit that is out of media.

1. If the storage unit is a robot and there are empty slots, add more volumes (remember to specify the correct volume pool).

• If there are no empty slots, move some media to nonrobotic and then add new volumes.

• If you are having difficulty keeping track of your available volumes, try the available_media script:

On UNIX, this script is in:

/usr/openv/netbackup/bin/goodies/available_media

install_path\NetBackup\bin\goodies\available_media.cmd

This script lists all volumes in the Media Manager volume configuration, and augments that list with information on the volumes currently assigned to NetBackup.

2. If the storage unit and volume pool appear to have media, verify the following:

• Volume is not FROZEN or SUSPENDED.

Check for this condition by using the NetBackup Media List report. If the volume is frozen or suspended, use the bpmedia command to unfreeze or unsuspend it (if that is desired).

• Volume has not expired or exceeded its maximum number of mounts.

• Volume Database Host name for the device is correct.

If you change the Volume Database Host name, stop and restart the Media Manager device daemon, ltid, (if the server is UNIX) or the NetBackup Device Manager service (if the server is a Windows NT system).

• The correct host is specified for the storage unit in the NetBackup configuration.

The host connection should be the server (master or slave) that has drives connected to it.

• The Media Manager volume configuration has media in the correct volume pool and unassigned or active media is available at the required retention level.

Use the NetBackup Media List report to show the retention levels, volume pools, and status (active and so on) for all volumes. Use the NetBackup Media Summary report to check for active volumes at the correct retention levels.

3. In some configurations, the NetBackup bptm process is rejected when requesting media from the vmd process (NetBackup Volume Manager service on Windows NT) because that processcannot determine the name of the host that is making the request.

This can be due to incorrect network configuration involving:

• Multiple network interfaces

• /etc/resolv.conf on those UNIX systems that use it

• Running DNS and not having reverse addressing configured

4. Create bptm and vmd activity log directories and retry the operation.

5. Examine the bptm activity log to verify that bptm is connecting to the correct system. If an error is logged, examine the vmd log.

On UNIX, the vmd log is:

/usr/openv/volmgr/debug/daemon/log.xxxxxx

On Windows NT, the vmd log is:

install_path\Volmgr\debug\daemon\xxxxxx.log.

6. If this is a new storage unit, and this is the first attempt to use it, stop and restart NetBackup on the master server.

Note: The bptm activity logs (in verbose mode) usually show the NetBackup media selection process.

Status Code: 97 Top

Message: requested media id is in use, cannot process request

Explanation: An operation was requested on a media ID that is in use. An example of this is attempting to suspend or freeze a volume while it is being used for a backup or restore.

Recommended Action: Retry the command when the volume is not in use. Use the Device Monitor to determine if the volume is in use (on UNIX you can also use xdevadm).

Status Code: 98 Top

Message: error requesting media (tpreq)

Explanation: The tape manager and optical manager (bptm) received an error when requesting a media mount from the NetBackup Device Manager service on Windows NT or the Media Manager device daemon (ltid) on UNIX.

Recommended Action: Check the NetBackup Problems report to determine the reason for the failure. The most common cause is that the NetBackup Device Manager service on Windows NT or the Media Manager device daemon (ltid) on UNIX is not running. Start it if necessary.

Status Code: 99 Top

Message: NDMP backup failure

Explanation: None of the paths in your NDMP class file list were backed up successfully.

Recommended Action: Check the NetBackup All Log Entries report for more information. A possible cause for this error is that none of the backup paths exist on the NDMP host.

101 102 105 106 Top

Status Code: 100 Top

Message: system error occurred while processing user command

Explanation: A system call failed in bparchive, bpbackup, bplist, or bprestore.

Recommended Action:

1. Enable activity logging for bparchive, bpbackup, bplist, or bprestore (as appropriate) by creating activity log directories for them.

On UNIX, if a nonroot user is having problems, verify that the directory created has mode 666. Look for and correct any reported errors.

2. Retry the operation and check the resulting logs.

If the logs do not reveal the problem, use the command line version of the command and correct any problems that are reported on stderr.

Status Code: 101 Top

Message: failed opening mail pipe

Explanation: The process that attempts to send mail could not open the pipe to the server.

Recommended Action: Verify that mail is configured on the client. For detailed troubleshooting information, create a bpcd activity log directory and retry the operation. Check the resulting bpcd activity log.

Status Code: 102 Top

Message: failed closing mail pipe

Explanation: The process that sends mail could not close the pipe to the server.

Recommended Action: Verify that mail is configured on the client. For detailed troubleshooting information, create a bpcd activity log directory and retry the operation. Check the resulting bpcd activity log.

Status Code: 105 Top

Message: file pathname exceeds the maximum length allowed

Explanation: The path name built by using the current working directory exceeds the maximum path length allowed by the system.

Recommended Action: Shorten the current working directory path length.

Status Code: 106 Top

Message: invalid file pathname found, cannot process request

Explanation: One of the file paths to be backed up or archived is not valid.

Recommended Action: Verify that full path names are used (they start with / on UNIX), and they are less than the maximum path length for the system. Also, verify that the files exist and the permissions allow NetBackup to access them.

111 112 Top

Status Code: 110 Top

Message: /usr/openv/netbackup/bp.conf not found

Explanation: On Windows NT, NetBackup could not read the registry entries that were created during installation. On UNIX, /usr/openv/netbackup/bp.conf file does not exist.

Recommended Action: Reinstall NetBackup software on the client or create the /usr/openv/netbackup/bp.conf file with at least the following lines:

SERVER = server_name

CLIENT_NAME = client_name

Status Code: 111 Top

Message: SERVER was not specified in /usr/openv/netbackup/bp.conf

Explanation: On UNIX, the SERVER = server_name line is missing in the bp.conf file. On Windows NT, the server list contains no entries. Recommended Action:

• On a UNIX client, add the following line to the top of the /usr/openv/netbackup/bp.conf file:

SERVER = server_name

• On a Microsoft Windows or nontarget NetWare client, add the server name on the Servers tab in the NetBackup Configuration dialog box. To display this dialog box, start the Backup, Archive, and Restore interface on the client and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57).

• On an OS/2 or NetWare target client, add the server name to the bp.ini file.

• On a Macintosh client, add the SERVER = server_name line to the bp.conf file in the NetBackup folder in the Preferences folder.

Status Code: 112 Top

Message: no files specified in the file list

Explanation: A restore was requested with no files in the file list.

Recommended Action: Specify at least one file to be restored.

121 122 123 124 125 126 127 Top

Status Code: 120 Top

Message: cannot find configuration database record for requested NB database backup

Explanation: The program that backs up the NetBackup internal databases (called catalogs on Windows NT) could not find the attributes that indicate which media IDs to use or paths to back up. This error should not occur under normal circumstances.

Recommended Action:

1. Check the NetBackup Problems report for additional information about the error.

2. For detailed troubleshooting information, create admin and bpdbm activity log directories and retry the operation. Check the resulting activity logs.

3. Contact customer support and send appropriate problem and activity log sections detailing the error.

Status Code: 121 Top

Message: no media is defined for the requested NB database backup

Explanation: NetBackup attempted to back up its internal databases (called catalogs on Windows NT) and there were no media IDs defined in the database backup configuration (called catalog backup on Windows NT).

Recommended Action: Add the media IDs to the NetBackup database backup configuration. Verify that the media IDs are in the NetBackup volume pool.

Status Code: 122 Top

Message: specified device path does not exist

Explanation: The NetBackup internal databases (called catalogs on Windows NT) were backed up by using the bpbackupdb command line and specifying a raw device file that does not exist.

Recommended Action: Retry the command using a valid device file name.

Status Code: 123 Top

Message: specified disk path is not a directory

Explanation: NetBackup attempted to back up its internal databases (called catalogs on Windows NT) and the backup attributes were set to dump to a disk. However, the disk file path already exists and is not a directory.

Recommended Action: Specify a different disk path for the database backup or delete the file that already exists.

Status Code: 124 Top

Message: NB database backup failed, a path was not found or is inaccessible

Explanation: One or more of the paths specified in the database backup configuration could not be backed up (the databases are called catalogs on Windows NT).

Recommended Action:

1. Check the NetBackup Problems report for additional information about the error. Some possible causes are:

• The path does not exist.

• On a UNIX system, there is a symbolic link in one of the paths.

2. After determining which path could not be accessed, correct the path names in the database backup configuration.

Status Code: 125 Top

Message: another NB database backup is already in progress

Explanation: Only one NetBackup database backup may be active at any given time.

Recommended Action: None.

Status Code: 126 Top

Message: NB database backup header is too large, too many paths specified

Explanation: Too many paths were specified in the NetBackup database backup configuration to fit in a fixed-size media header. This error should not occur under normal circumstances.

Recommended Action: Delete some of the paths from the database backup configuration.

Status Code: 127 Top

Message: specified media or path does not have a valid NB database backup header

Explanation: The bprecover command was issued and the media ID specified does not have valid database backup data.

Recommended Action: Validate that the correct media ID is being used.

131 133 135 Top

Status Code: 130 Top

Message: system error occurred

Explanation: An error occurred that prevents the product from operating in a consistent fashion. This error is usually related to a system call.

Recommended Action:

1. Check the NetBackup Problems report for additional information about the error.

2. Check the system log for reported problems.

3. For detailed troubleshooting information, create bpdbm, bpsched, bptm, and bprd activity log directories on the master server and retry the operation. Check the resulting activity logs.

Status Code: 131 Top

Message: client is not validated to use the server

Explanation: The client name, as determined from the connection to the server, did not match any client name in the NetBackup configuration and there was no altnames configuration for this client on the master server. A client and server that have multiple network connections can encounter this problem if the name by which the client is configured is not the one by which its routing tables direct connections to the server.

Recommended Action:

1. Examine the NetBackup Problems report.

2. Create an activity log directory for bprd and retry the operation. Check the resulting activity log to determine the connection and client names.

Depending on the request type (restore, backup, and so on.), you may need or want to:

• Change the client's configured name.

• Modify the routing tables on the client.

• On the master server, set up an altnames directory and file for this client (see the NetBackup System Administrator's Guide - UNIX).

or

• On a UNIX master server, create a soft link in the NetBackup image database.

3. Review "Verifying Host Names and Services Entries" on page 31.

Status Code: 133 Top

Message: invalid request

Explanation: One of two explanations exist.

• A request was made that is unrecognized. This usually results from different versions of NetBackup software being used together.

• If a client receives this error in response to a list or restore request, it means that the DISALLOW_CLIENT_LIST_RESTORE or DISALLOW_CLIENT_RESTORE option exists in the bp.conf file on a UNIX NetBackup server or registry on a Windows NT NetBackup server. These options deny list and restore requests from all NetBackup clients.

Recommended Action:

1. If you suspect that the software versions are the problem, verify that all NetBackup software is at the same version level.

• On UNIX NetBackup servers and clients, check the /usr/openv/netbackup/bin/version file.

• On Windows NT NetBackup servers, check the install_path\netbackup\version.txt file or the About NetBackup command on the Help menu.

• On Microsoft Windows clients, check the About NetBackup command on the Help menu.

• On NetWare target clients, check the Version entry in the bp.ini file. If the client software is earlier than 3.0, verify that the client is in a Standard type class.

• On Macintosh clients, check the version file in the bin folder in the NetBackup folder in the Preferences folder.

2. If the server is denying list and restore requests, remove the DISALLOW_CLIENT_LIST_RESTORE and DISALLOW_CLIENT_RESTORE options from the bp.conf file on a UNIX NetBackup server or registry on a Windows NT NetBackup server. Then, stop and restart the NetBackup request daemon (UNIX) or NetBackup Request Manager service (Windows NT).

3. For detailed troubleshooting information, create bpdbm, bprd, and admin activity log directories. Then, retry the operation and check the resulting activity logs.

Status Code: 135 Top

Message: client is not validated to perform the requested operation

Explanation: This is usually caused by a request to restore files to a client other than the one that made the request and the request did not come from the root user (administrator on Windows NT) on a NetBackup server.

Recommended Action: Retry the operation as a root user (administrator on Windows NT) on the master server. Also see status code 131.

141 142 143 144 145 146 147 148 Top

Status Code: 140 Top

Message: user id was not superuser

Explanation: The process was started by a user or process that did not have root privileges (on UNIX) or administrator privileges (on Windows NT).

Recommended Action: If desired, give the user or process administrator privileges (on Windows NT) or root privileges (on UNIX) and retry the operation.

Status Code: 141 Top

Message: file path specified is not absolute

Explanation: The file specification must be an absolute path.

Recommended Action: Correct the file specification and retry the command.

Status Code: 142 Top

Message: file does not exist

Explanation: This code is reserved for future use.

Recommended Action: None.

Status Code: 143 Top

Message: invalid command protocol

Explanation: An ill-formed request was made to the NetBackup request daemon (UNIX) or Request Manager service (Windows NT). This can be due to mismatched versions of the product, corrupted network communication, or to a non-NetBackup process sending data across the port for the daemon or service.

Recommended Action: Examine the NetBackup error logs to determine the system that was the source of the data and on that system determine the process that initiated the request. If it was a NetBackup process, verify that the process or command is compatible with the version of software on the server.

Status Code: 144 Top

Message: invalid command usage

Explanation: This status code is due to a NetBackup process being started with improper options or an incompatibility in the product.

Recommended Action: Either correct the command or verify that all NetBackup binaries are at the same version level.

Status Code: 145 Top

Message: daemon is already running

Explanation: There is another copy of the process executing.

Recommended Action: Terminate the current copy of the process and then restart the process.

Status Code: 146 Top

Message: cannot get a bound socket

Explanation: The daemon (service on Windows NT) could not bind to its socket. A system call failed when the daemon UNIX) or service (Windows NT) attempted to bind to its configured port number. This is usually caused by another process having acquired the port before the daemon or service started.

Recommended Action:

1. Examine the NetBackup Problems and All Log Entries reports.

2. Create bprd and bpdbm activity log directories and retry the operation.

Check the resulting logs to see the system error message resulting from the attempt.

If another process has the port, use other system commands to determine the process. Based on this research, either change the port number in your services file or map or terminate the process that has acquired the port.

On UNIX, another possible cause for this error is terminating bprd or bpdbm with the kill command. The recommended way to stop bprd is with the terminate options in, xbpadm. To stop bpdbm, use the /usr/openv/netbackup/bin/bpdbm -terminate command. Using the kill command to stop these processes can leave them unable to bind to their assigned ports the next time they are started.

To identify a bprd or bpdbm problem, look for lines similar to the following in the activity log for the respective process:

<16> getsockbound: bind() failed, Address already in use (114)

<32> listen_loop: cannot get bound socket. errno = 114

<4> terminate: termination begun...error code = 146

Similar entries can appear in the reports.

3. If the problem persists longer than ten minutes, it is possible that it will be necessary to reboot the server.

Status Code: 147 Top

Message: required or specified copy was not found

Explanation: The requested copy number of a backup or archive image cannot be found.

Recommended Action: Correct the request to specify a copy number that does exist.

Status Code: 148 Top

Message: daemon fork failed

Explanation: A NetBackup service could not create a child process due to an error received from the system. This is probably an intermittent error based on the availability of resources on the system.

Recommended Action:

1. Restart the service at a later time and investigate system problems that limit the number of processes.

2. Check the Event Viewer Application and System logs (Windows NT).

151 152 153 154 158 159 Top

Status Code: 150 Top

Message: termination requested by administrator

Explanation: The process is terminating (or has terminated) as a direct result of a request from an authorized user or process.

Recommended Action: None.

Status Code: 151 Top

Message: Backup Exec operation failed

Explanation: The Global Data Manager console has reported that a Backup Exec job (backup, archive, or restore) did not complete normally.

Recommended Action: Consult the Backup Exec job history on the Backup Exec server for details.

Status Code: 152 Top

Message: required value not set

Explanation: An incomplete request was made to the bpdbm process (NetBackup Database Manager service on Windows NT). This usually occurs because different versions of software are being used together.

Recommended Action:

1. Verify that all software is at the same version level.

2. For detailed troubleshooting information, create bpdbm and admin activity log directories and retry the operation. Check the resulting activity logs.

Status Code: 153 Top

Message: server is not the master server

Explanation: This status code is reserved for future use.

Recommended Action: None.

Status Code: 154 Top

Message: storage unit characteristics mismatched to request

Explanation: A backup was attempted and the storage unit selected for use had characteristics that were not compatible with the backup type.

Recommended Action: Verify that the characteristics of the storage unit involved are appropriate for the backup attempted:

• For an NDMP class type, verify that a storage unit of type NDMP is defined and the NDMP host value matches the host name of the client. For example, if the NDMP class specifies toaster as the client, the configuration for the storage unit must specify toaster as the NDMP host.

• For a class type other than NDMP, verify that the class specifies a Media Manager or Disk type storage unit.

Status Code: 158 Top

Message: failed accessing daemon lock file

Explanation: The process could not lock its lock file because an error was received from a system call. This lock file synchronizes process activities (for example, preventing more than one daemon from executing at a time).

Recommended Action:

1. Examine the NetBackup error log to determine why the system call failed and correct the problem. It could be a permission problem.

2. If the error log does not show the error, create an activity log directory for bprd, bpdbm, or bpsched (depending on which process encountered the error) and retry the operation. Examine the resulting activity log.

Status Code: 159 Top

Message: licensed use has been exceeded

Explanation: This status code is reserved for future use.

Recommended Action: None.

164 165 166 167 168 169 Top

Status Code: 160 Top

Message: authentication failed

Explanation: A problem was encountered when two systems were attempting to authenticate one another.

Recommended Action: See the NetBackup System administrator's Guide - UNIX for more information on the files and commands mentioned here.

1. Ensure that the authentication libraries exist:

Windows NT, 98, 95:

install_path\NetBackup\lib\libvopie.dll

install_path\NetBackup\lib\libnoauth.dll

UNIX (except HP-UX):

/usr/openv/lib/libvopie.so

/usr/openv/lib/libnoauth.so

UNIX (HP-UX only):

/usr/openv/lib/libvopie.sl

/usr/openv/lib/libnoauth.sl

Macintosh:

:System Folder:Extensions:libvopie.dll

:System Folder:Extensions:libnoauth.dll

2. Check the methods_allow.txt files on the systems that are having problems to ensure that authentication is enabled. The files are in the following locations:

Windows NT, 98, 95:

install_path\NetBackup\var\auth

UNIX:

/usr/openv/var/auth

Macintosh:

:System Folder:Preferences:NetBackup:var:auth

3. On the systems that are having the authentication problem, remove the remote host that is not being authenticated from the methods_allow.txt file.

For example, if hosta and hostb are having the problem, remove hosta from the file on hostb and vice versa.

Retry the operation.

• If the problem still exists, it indicates connection problems not related to authentication.

• If connections are now successful, proceed to the next step.

4. Execute bpauthsync -vopie on the master server to resynchronize the key files on the systems.

On Windows NT:

install_path\NetBackup\bin\admincmd\bpauthsync -vopie -servers

-clients

On UNIX:

/usr/openv/netbackup/bin/admincmd/bpauthsync -vopie -servers

-clients

5. Add back the names removed in step 3 and retry the operation.

6. Create activity log directories for the processes involved in authentication between NetBackup systems. These include:

• On the server, create activity log directories for bprd, bpdbm, bpcd.

• On the client, create activity log directories for bpbackup, bprestore,

bpbkar (Windows NT only).

Retry the operation and check the logs.

Status Code: 164 Top

Message: unable to mount media because it is in a DOWN drive or misplaced

Explanation: A restore was attempted and the volume required for the restore was in a DOWN drive in a robot. Or, the slot that should contain the volume is empty.

Recommended Action:

• If volume is in a DOWN drive, remove it and place it in its designated slot. Then, retry the restore.

• If the volume is in the wrong slot, use a robot inventory option to reconcile the contents of the robot with the Media Manager volume configuration.

Status Code: 165 Top

Message: NB image database contains no image fragments for requested backup id/copy number

Explanation: A restore was attempted and NetBackup has no record of fragments associated with the backup ID that has the files.

Recommended Action: Check the NetBackup Problems report for additional information about the error. For detailed troubleshooting information, create an activity log directory for either bpdm or bptm (whichever applies) and retry the operation. Check the resulting activity log.

Status Code: 166 Top

Message: backups are not allowed to span media

Explanation: An end of media (EOM) was encountered while the backup image was being written. The backup was terminated because the NetBackup DISALLOW_BACKUPS_SPANNING_MEDIA option was present in bp.conf on UNIX or the registry on Windows NT. The backup will be retried automatically with a different volume if this is allowed by the backup tries attribute in the NetBackup global attribute configuration.

Recommended Action: None.

Status Code: 167 Top

Message: cannot find requested volume pool in Media Manager volume database

Explanation: A backup to a nonrobotic drive was attempted and the tape manager (bptm) could not find or add the specified volume pool.

Recommended Action: Verify the Media Manager volume configuration. Check the NetBackup Problems report for more information about the error. For detailed troubleshooting information, create a bptm activity log directory and retry the operation. Check the resulting activity log.

Status Code: 168 Top

Message: cannot overwrite media, data on it is protected

Explanation: A database backup was attempted to a volume that could not be overwritten because it contains data that NetBackup, by default, does not overwrite (tar, cpio, ANSI, and so on).

Recommended Action: Replace the volume with a new one or set the NetBackup ALLOW_MEDIA_OVERWRITE option to the appropriate value.

Status Code: 169 Top

Message: media id is either expired or will exceed maximum mounts

Explanation: A backup or database backup was attempted and the volume selected for use has reached its maximum number of mounts as specified in the Media Manager volume configuration. For a regular backup, the volume is automatically set to the SUSPENDED state and not used for further backups. For a NetBackup database backup, the operation terminates abnormally.

Recommended Action: If the volume was suspended, wait until it expires and then replace it. For NetBackup database backups, replace the media.

171 172 173 174 175 176 177 178 179 Top

Status Code: 171 Top

Message: media id must be 6 or less characters

Explanation: An operation, such as using bpmedia to suspend or freeze a media ID was attempted and the media ID specified was longer than six alpha-numeric characters.

Recommended Action: Retry the command with a valid media ID.

Status Code: 172 Top

Message: cannot read media header, may not be NetBackup media or is corrupted

Explanation: When loading a volume for a backup or restore, the tape manager (bptm), did not find the expected tape header. This can mean that a volume in a robotic device is not in the slot number shown in the Media Manager volume configuration or that a read error (I/O error) occurred.

Recommended Action:

1. If the volume is in a robot that supports barcodes, verify the robot contents by using a Media Manager robot inventory option.

2. If the volume was mounted on a nonrobotic drive, verify that the correct volume was mounted and assigned.

3. Check the NetBackup Problems report. If a fatal read error occurred, attempt the operation again using another drive, if possible.

Status Code: 173 Top

Message: cannot read backup header, media may be corrupted

Explanation: When searching for a backup image to restore, the tape manager (bptm) could not find the correct backup ID at the position on the media where NetBackup expected it to be. This can indicate a drive hardware problem.

Recommended Action:

1. Check the NetBackup Problems report for clues as to what caused the error.

2. Try the restore on another drive if possible.

3. For detailed troubleshooting information, create an activity log directory for bptm and retry the operation. Check the resulting activity log.

Status Code: 174 Top

Message: media manager system error occurred

Explanation: An abnormal condition occurred causing a tape manager (bptm) or disk manager (bpdm) failure. This should not occur under normal circumstances.

Note: If this occurs on a Sequent platform and you are attempting to back up more than four gigabytes of data, save all your logs and call VERITAS technical support. For other platforms perform the recommended actions described below.

Recommended Action:

1. Check the NetBackup Problems report to see if it shows the cause of the problem. If you see a Problems report message similar to "attempting to write 32767 bytes, not a multiple of 1024" save all logs and call VERITAS customer support.

2. On UNIX, if this occurs during a restore, it may be that the tape drive is incorrectly configured to write in fixed length mode when it should write in variable length mode.

Verify your drive's configuration, comparing it to what is recommended in the Media Manager Device Configuration Guide (also see Step 7 of this procedure).

If your configuration incorrectly specifies fixed length mode, change the configuration to specify variable length mode and suspend media that were written on that device. The images written to those media may be restorable (this is platform dependent), but single file restores are almost guaranteed to fail.

3. If you see the problem with only one client, verify that the client binaries are correct, especially those for bpcd.

4. Can you read or write any other images on this media?

If so, the check the following reports for clues:

• Images on Media report

• Media Contents report

5. Verify the following:

• The media by using the NetBackup image verify option.

• That you are using the correct media type for the device.

6. Check the system or console log for errors (on UNIX) or the Event Viewer Application log (on Windows NT).

7. For detailed debug information, create an activity log directory for either bptm or bpdm (whichever applies) and retry the operation. Check the resulting activity log.

If the bptm activity log shows an error similar to

00:58:54 [2304] <16> write_data: write of 32768 bytes indicated only 29696 bytes were written, errno = 0

it may be that the tape drive is configured to write in fixed length mode rather than variable length mode, and the image being written encountered the end-of-media.

Take the corrective action suggested in Step 2.

Status Code: 175 Top

Message: not all requested files were restored

Explanation: When restoring files from an image, the bptm or bpdm process detected a fatal error condition and terminated the restore before it completed. This should not occur under normal circumstances.

Recommended Action:

1. Check the NetBackup Problems report and the progress log on the client for additional information about the error

2. For detailed troubleshooting information, create an activity log directory for either bptm or bpdm (whichever applies) and retry the operation. Check the resulting activity log.

Status Code: 176 Top

Message: cannot perform specified media import operation

Explanation: The tape manager (bptm) detected an error condition when attempting to import a specific backup image. Possible reasons for this are:

• Media ID is already active in the NetBackup media database on this server

• Media ID is not in the Media Manager volume configuration

•Fatal t ape manager ( bptm) error occurred

• Total image was not obtained from Phase 1 of import

Recommended Action:

1. Check the NetBackup Problems report to find the exact cause of the failure.

2. Try the following:

• If the media ID is already active, duplicate all images on the original media ID to another volume. Then, manually expire the original media and redo the import.

• If the media ID is not present in the Media Manager volume configuration, add it.

• If a fatal bptm error occurred, verify that the Media Manager volume daemon (vmd) is active on UNIX or the NetBackup Volume Manager service is active on Windows NT.

• If the entire image is not present, perform import phase 1 on the media IDs that have the remainder of the image.

Status Code: 177 Top

Message: could not deassign media due to Media Manager error

Explanation: The tape manager (bptm) could not successfully deassign a media ID.

Recommended Action:

1. Check the NetBackup Problems report for the cause of the problem.

2. Verify that the Media Manager volume daemon (vmd) is active on UNIX or the NetBackup Volume Manager service is active on Windows NT.

3. For detailed troubleshooting information, create an activity log directory for bptm and retry the operation. Check the resulting activity log.

Status Code: 178 Top

Message: media id is not in NetBackup volume pool

Explanation: NetBackup attempted a backup of its databases and the media ID specified for the database backup was not in the NetBackup volume pool. Volumes for database backups must be in the NetBackup volume pool.

Recommended Action: Check the Media Manager volume configuration to verify that the media IDs are present and in the NetBackup volume pool.

Status Code: 179 Top

Message: density is incorrect for the media id

Explanation: An operation such as "list contents" was attempted on an invalid media ID, such as a cleaning tape. Another possibility is that a media ID in the NetBackup database backup configuration does not match the media type entered in the Media Manager volume configuration.

Recommended Action: Check the volume configuration and the NetBackup database backup configuration and correct any problems found.

181 182 183 184 185 186 189 Top

Status Code: 180 Top

Message: tar was successful

Explanation: tar returned a successful exit status.

Recommended Action: None.

Status Code: 181 Top

Message: tar received an invalid argument

Explanation: One of the parameters passed to tar was not valid. Recommended Action:

On a UNIX client:

• Ensure that the tar command in /usr/openv/netbackup/bin is the one provided by NetBackup. If you are in doubt, reinstall it.

•Check /usr/openv/netbackup/bin/version on the client to verify that the client is running the correct level software. If the software is not at the correct level, update the software per the directions in the NetBackup release notes.

On a Windows NT client, create a tar activity log directory, retry the operation, and check the log.

On a Macintosh client, check the version file that is in the bin folder in the NetBackup folder in the Preferences folder. If the software is not at the correct level, install the correct software as explained in the installation guide.

Status Code: 182 Top

Message: tar received an invalid file name

Explanation: tar cannot write to the file that is specified with the -f parameter.

Recommended Action:

1. Create a bpcd activity log directory on the client (on a Macintosh NetBackup creates the log automatically).

2. On a Windows NT client, create a tar activity log directory.

3. Increase the logging level on the client:

• On a UNIX client, add the VERBOSE option to the /usr/openv/netbackup/bp.conf file.

• On PC clients, increase the debug or log level as explained in the activity log topics in Chapter 3, "Using the Logs and Reports."

4. Rerun the operation, check the resulting activity logs for the parameters passed to tar and call customer support.

Status Code: 183 Top

Message: tar received an invalid archive

Explanation: The data passed to tar was corrupt.

Recommended Action:

• If the problem is with a UNIX client, create a /usr/openv/netbackup/logs/tar activity log directory on the client and rerun the operation.

a. Check the tar activity log file for error messages that explain the problem.

b. Reboot the client to see if this clears the problem.

c. When you are through investigating the problem, delete the /usr/openv/netbackup/logs/tar directory on the client.

• If the problem is with a Microsoft Windows, NetWare, or Macintosh client:

a. Create a bpcd activity log directory on the client (on a Macintosh NetBackup creates the log automatically).

b. On a Windows NT client, create a tar activity log directory.

c. Increase the debug or log level as explained in the activity log topics in Chapter 3, "Using the Logs and Reports."

d. Rerun the operation and check the resulting activity logs.

e. Reboot the client to see if it clears the problem.

Status Code: 184 Top

Message: tar had an unexpected error

Explanation: A system error occurred in tar.

Recommended Action:

• If the problem is with a UNIX client, create a /usr/openv/netbackup/logs/tar activity log directory on the client and rerun the operation.Create a /usr/openv/netbackup/logs/tar directory on the client and rerun the operation.

a. Check the tar activity log file for error messages that explain the problem.

b. Reboot the client to see if this clears the problem.

c. When you are through investigating the problem, delete the /usr/openv/netbackup/logs/tar directory on the client.

• If the problem is with a Microsoft Windows, NetWare, or Macintosh client:

a. Create a bpcd activity log directory on the client (on a Macintosh NetBackup creates the log automatically).

b. Increase the debug or log level as explained in the activity log topics in Chapter 3, "Using the Logs and Reports."

c. On a Windows NT client, create a tar activity log directory.

d. Retry the operation and check the resulting activity logs.

e. Reboot the client to see if it clears the problem.

Status Code: 185 Top

Message: tar did not find all the files to be restored

Explanation: There were files in the tar file list that were not in the image.

Recommended Action:

• If the problem is with a UNIX client:

a. Enable bpcd activity logging by creating the /usr/openv/netbackup/logs/bpcd directory on the client.

b. Rerun the operation, check the resulting bpcd log file for the parameters passed to tar, and call customer support.

• If the problem is with a Microsoft Windows, NetWare, or Macintosh client: a. Create a bpcd activity log directory on the client (on a Macintosh NetBackup creates the log automatically).

b. Increase the debug or log level as explained in the activity log topics in Chapter 3, "Using the Logs and Reports."

c. On a Windows NT client, create a tar activity log directory.

d. Retry the operation.

e. Check the resulting activity logs for the parameters passed to tar and call customer support.

Status Code: 186 Top

Message: tar received no data

Explanation: The media manager did not send data to tar.

Recommended Action:

1. Retry the operation and check the progress log on the client for error messages that reveal the problem.

2. Verify that the tape is available and readable.

3. Verify that that the drive is in an UP state. Use the Device Monitor (on UNIX xdevadm can also be used)

4. For detailed troubleshooting information:

a. Create a bptm activity log on the server.

b. On a Windows NT client, create a tar activity log.

c. Retry the operation and check the resulting activity logs.

Status Code: 189 Top

Message: the server is not allowed to write to the client's filesystems

Explanation: The client is not allowing writes from the server.

Recommended Action:

Perform the following to perform restores or install software from the server.

• On a UNIX client, delete DISALLOW_SERVER_FILE_WRITES from the /usr/openv/netbackup/bp.conf file.

• On a Microsoft Windows or NetWare nontarget client, select Allow Server Directed Restores on the General tab in the NetBackup Configuration dialog box. To display this dialog box, start the Backup, Archive, and Restore interface on the client and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57).

• On a Macintosh client, delete DISALLOW_SERVER_FILE_WRITES from the bp.conf file in the NetBackup folder in the Preferences folder.

• On a NetWare target client, set ALLOW_SERVER_WRITE to yes in the bp.ini file.

191 194 195 196 197 198 199 Top

Status Code: 190

Message: found no images or media matching the selection criteria

Explanation: A verify, duplicate, or import was attempted and no imagesmatching the search criteria were found in the NetBackup database.

Recommended Action: Change the search criteria and retry.

Status Code: 191 Top

Message: no images were successfully processed

Explanation: A verify, duplicate, or import was attempted and failed for all selected images.

Recommended Action: Check the NetBackup Problems report for the cause of the error. To obtain detailed troubleshooting information, create an admin activity log directory and retry the operation. Check the resulting activity log.

Status Code: 194 Top

Message: the maximum number of jobs per client is set to 0

Explanation: The NetBackup Maximum Jobs per Client global attribute is currently set to 0. Setting the value to 0 disables backups and archives.

Recommended Action: To enable backups and archives, change the global attribute value to the desired nonzero setting.

Status Code: 195 Top

Message: client backup was not attempted

Explanation: A backup job was in the NetBackup scheduler's worklist but was not attempted.

Recommended Action:

1. Retry the backup either immediately with a manual backup or allow the normal scheduler retries.

2. For additional information, check the All Log Entries report. For detailed troubleshooting information, create a bpsched activity log directory on the master server. After the next backup attempt, check the activity log. Some actions to perform are:

• Verify that the vmd and ltid daemons (UNIX) or the NetBackup Volume Manager and NetBackup Device Manager services (Windows NT) are running.

• Look for a problem in an earlier backup that made the media or storage unit unavailable.

Status Code: 196 Top

Message: client backup was not attempted because backup window closed

Explanation: A backup or archive operation that was queued by the backup scheduler was not attempted because the backup window was no longer open.

Recommended Action:

• If possible, change the schedule to extend the backup window for this class and schedule combination so it does not occur again.

• If the backup must be run, use the Manual Backup command on the Class menu in the Backup Policy Management window to perform the backup. Manual backups ignore the backup window.

• If the backup must be run, use the NetBackup administration interface command for manual backups to perform the backup. Manual backups ignore the backup window.

Status Code: 197 Top

Message: the specified schedule does not exist in the specified class

Explanation: A user backup or archive request has specified the exact class and schedule to use when performing a backup. The class exists but does not contain the schedule.

· On Microsoft Windows and NetWare nontarget clients, you can specify a class or schedule on the Backups tab in the NetBackup Configuration dialog box. To display this dialog box, start the Backup, Archive, and Restore interface on the client and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57).

· On UNIX and Macintosh clients, you can specify a class or schedule by using the bp.conf options, BPBACKUP_CLASS or BPBACKUP_SCHED. • On NetWare target clients, you can specify a class or schedule in the bp.ini file.

Recommended Action:

1. Check the client progress log (if available) to determine the class and schedule that were specified.

2. Check the configuration on the master server to determine if the schedule is valid for the class. If the schedule is not valid, either add the schedule to the class configuration or specify a valid schedule on the client.

Status Code: 198 Top

Message: no active classes contain schedules of the requested type for this client

Explanation: A user backup or archive has been requested, and this client is not in a class that has a user backup or archive schedule.

Recommended Action:

Determine if the client is in any class that has a schedule of the appropriate type (either user backup or archive).

• If the client is in such a class, check the general class attributes to verify that the class is set to active.

• If the client is not in such a class, either add a schedule of the appropriate type to an existing class that has this client or create a new class that has this client and a schedule of the appropriate type.

Status Code: 199 Top

Message: operation not allowed during this time period

Explanation: A user backup or archive has been requested and this client is not in a class that has a user backup or archive schedule with an open backup window. This error implies that there is an appropriate class and schedule combination for this client.

Recommended Action: Determine the classes to which this client belongs that also have a schedule of the appropriate type (either user backup or archive).

· If possible, retry the operation when the backup window is open.

· If the backup window is not open during appropriate time periods, adjust a backup window for a schedule in one of the classes.

201 202 203 204 205 206 207 208 209 Top

Status Code: 200 Top

Message: scheduler found no backups due to run

Explanation: When checking the class and schedule configuration, the NetBackup scheduler process (bpsched) did not find any clients to back up. This could be due to:

• No backup time windows are open (applies only to full and incremental schedules).

• Classes are set to inactive.

• The clients were recently backed up and are not due for another backup (based on Frequency setting for the schedules).

• Classes do not have any clients.

Recommended Action: Usually, this message can be considered informational and does not indicate a problem. However, if you suspect a problem:

1. Examine the NetBackup All Log Entries report to see if there are any messages in addition to one indicating that the scheduler found nothing to do.

2. Examine the class configuration for all classes or the specific class in question and determine if any of the reasons mentioned in the Explanation section above apply.

3. To obtain detailed troubleshooting information, create a bpsched activity log directory on the master server and retry the operation. Check the resulting activity log.

Status Code: 201 Top

Message: handshaking failed with server backup restore manager

Explanation: A process on the master server encountered an error when communicating with the media server (either the master or a slave server). This error means that the master and media server processes were able to initiate communication, but encountered difficulties in completing them. This problem can occur during a backup, restore, or media list in a single or multiple server configuration.

Recommended Action:

1. Determine the activity that encountered the handshake failure by examining the NetBackup All Log Entries report for the appropriate time period. If there are slave servers, determine if:

• The handshake failure was encountered between the master and a slave server.

or

• Only the master server was involved.

2. If necessary, create the following activity log directories for the following:

• bpcd on the NetBackup media server (either master or slave).

• If the error was encountered during a backup operation, bpsched on the master server.

• If the error was encountered during a restore operation, bprd on the master server.

• If the error was encountered during a media list operation, admin in the NetBackup logs/admin directory on the master server.

3. Retry the operation and examine the resulting activity logs for information on why the error occurred.

Status Code: 202 Top

Message: timed out connecting to server backup restore manager

Explanation: A process on the master server timed out while trying to initiate communications with the media server (either the master or a slave server). This problem can occur during a backup or restore in either a single or multiple server configuration.

Recommended Action: Determine which activity encountered the connection timeout failure by examining the All Log Entries report for the appropriate time period. If there are slave servers, determine if the timeout occurred between the master and a slave or if only the master was involved.

1. Verify that the schedule specifies the correct storage unit.

2. Execute the ping command from one host to another by using the following combinations:

• From the master server, ping the master and all slave servers by using the host names found in the storage unit configuration.

• From each of the slave servers, ping the master server by using the host name specified in the NetBackup server list. On a UNIX server, this is the first SERVER entry in the bp.conf file. On a Windows NT server, the master is designated as the Current server on the Servers tab in the NetBackup Configuration dialog box. To display this dialog box, start the Backup, Archive, and Restore interface on the server and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57).

3. Verify that the master server can communicate with bpcd on the host that has the storage unit.

After each backup, the scheduler checks the storage unit to see how many drives are available (in case the backup caused a drive to be automatically downed). If bpsched cannot communicate with bpcd, it sets the number of available drives in that storage unit to 0 and further backups to that storage unit fail.

The available drives remain at 0 until the scheduler is initialized again. Therefore, even if bpcd seems to be operating correctly now, check the bpsched and bpcd activity logs (see below) for records of an earlier failure.

4. See "Testing Slave Server and Clients" on page 18 and "Resolving Network Communication Problems" on page 21.

5. If necessary, create activity log directories for the following processes and retry the operation. Then, check the resulting activity logs on the master server:

• If the error occurred during a backup operation, check the bpsched activity logs. Also, check the bpcd activity logs.

• If the error occurred during a restore operation, check the bprd activity logs.

Status Code: 203 Top

Message: server backup restore manager's network is unreachable

Explanation: A process on the master server could not connect to a particular host on the network when trying to initiate communication with the media server for a particular operation. This problem can occur during a backup or restore in either a single or multiple server configuration.

Recommended Action: Determine which activity encountered the network unreachable failure by examining the All Log Entries report for the appropriate time frame. If there is more than one NetBackup server (that is, one or more slave servers) determine if the network unreachable failure was encountered between the master and a slave server or if only the master server was involved. Execute the ping command from one host to another by using the following combinations:

1. From the master server, ping the master and all slave servers by using the host names in the storage unit configuration.

2. From each of the slave servers, ping the master server host by using the host name specified in the NetBackup server list. On a UNIX server, this is the first SERVER entry in the bp.conf file. On a Windows NT server, the master is designated as the Current server on the Servers tab in the NetBackup Configuration dialog box. To display this dialog box, start the Backup, Archive, and Restore interface and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57).

3. See "Testing Slave Server and Clients" on page 18 and "Resolving Network Communication Problems" on page 21.

4. If necessary, create activity log directories for the following processes and retry the operation. Then, check the resulting activity logs on the master server:

• If the error occurred during a backup, check the bpsched activity logs.

• If the error occurred during a restore, check the bprd activity logs.

Status Code: 204 Top

Message: connection refused by server backup restore manager

Explanation: The media server refused a connection on the port number for bpcd. This error can be encountered during a backup or restore.

Recommended Action: Execute the ping command from one host to anotherby using the following combinations: Note: Also, see "Resolving Network Communication Problems" on page 21.

1. From the master server, ping the master and all slave servers by using the host names in the storage unit configuration.

2. From each of the slave servers, ping the master server by using the name specified in the NetBackup server list. On a UNIX server, this is the first SERVER entry in the bp.conf file. On a Windows NT server, the master is designated as the Current server on the Servers tab in the NetBackup Configuration dialog box. To display this dialog box, start the Backup, Archive, and Restore interface on the server and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57).

3. On UNIX servers, verify that the bpcd entries in /etc/services or NIS on all the servers are identical. Verify that the media server is listening on the correct port for connections to bpcd by running one of the following commands (depending on platform and operating system):

netstat -a | grep bpcd
netstat -a | grep 13782 (or the value specified during the install)
rpcinfo -p | grep 13782 (or the value specified during the install)

On UNIX servers, you may have to change the service number for bpcd in /etc/services and the NIS services map and send SIGHUP signals to the inetd processes on the clients.
/bin/ps -ef | grep inetd
kill -HUP the_inetd_pid
or
/bin/ps -aux | grep inetd
kill -HUP the_inetd_pid

Note: On a Hewlett-Packard UNIX platform, use inetd -c to send a SIGHUP to inetd.

4. On Windows NT servers:

a. Verify that the bpcd entries are correct in:
%SystemRoot%\system32\drivers\etc\services

b. Verify that the NetBackup Client Service Port Number and NetBackup Request Service Port Number on the Network tab in the NetBackup Configuration dialog box match the settings in the services file. To display this dialog box, start the Backup, Archive, and Restore interface and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57). The values on the Network tab are written to the services file when the NetBackup Client service starts.

c. Stop and restart the NetBackup services.

5. See "Testing Slave Server and Clients" on page 18 and "Resolving Network Communication Problems" on page 21.

6. If necessary, create activity log directories for the following processes and retry the operation. Then, check the resulting activity logs on the master server:

o If the error occurred during a backup operation, check the bpsched activity logs.

o If the error occurred during a restore operation, check the bprd activity logs.

Status Code: 205 Top

Message: cannot connect to server backup restore manager

Explanation: A process on the master server could not connect to a process on a host on the network while trying to initiate communication with the server that has the storage unit for a particular operation. This problem can occur during a backup or restore in either a single or multiple server configuration. This can also occur when the scheduler process (bpsched) is building its list of available storage units to use during backups.

Recommended Action: Execute the ping command from one host to another by using the following combinations:

Note: Also, see "Resolving Network Communication Problems" on page 21.

1. From the master server, ping the master and all slave servers by using the host names in the storage unit configuration.

2. From each of the slave servers, ping the master server by using the name specified in the NetBackup server list. On a UNIX server, this is the first SERVER entry in the bp.conf file. On a Windows NT server, the master is designated as the Current server on the Servers tab in the NetBackup Configuration dialog box. To display this dialog box, start the Backup,Archive, and Restore interface and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57).

3. On a UNIX server, verify that the bpcd entry in /etc/services or NIS on all the servers are identical. Verify that the media server is listening on the correct port for connections to bpcd by running one of the following commands (depending on platform and operating system):

netstat -a | grep bpcd
netstat -a | grep 13782 (or the value specified during the install)
rpcinfo -p | grep 13782 (or the value specified during the install)

4. On Windows NT servers:

a. Verify that the bpcd entries are correct in the services file:
%SystemRoot%\system32\drivers\etc\services

b. Verify that the NetBackup Client Service Port Number and NetBackup
Request Service Port Number on the Network tab in the NetBackup Configuration dialog box match the settings in the services file. To display this dialog box, start the Backup, Archive, and Restore interface and click Configure on the Actions menu (also see "Using the Configure-NetBackup Window" on page 57). The values on the Network tab are written to the services file when the NetBackup Client service starts.

c. Stop and restart the NetBackup services.

5. See "Testing Slave Server and Clients" on page 18 and "Resolving Network Communication Problems" on page 21.

6. Create a bpcd activity log directory on the server that has the storage unit and retry the operation. Then, check for additional information in the resulting activity log.

Status Code: 206 Top

Message: access to server backup restore manager denied

Explanation: The master server is trying to start a process on another server (or itself) and the master server does not appear in the Netbackup server list on that server. On a UNIX server, the master is the first SERVER entry in the bp.conf file. On a Windows NT server, the master is designated as the Current server on the Servers tab in the NetBackup Configuration dialog box.

To display this dialog box, start the Backup, Archive, and Restore interface and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57).

Recommended Action:

1. Verify that the master server appears as a server in its own server list as well as being listed on all slaves.

If you change the server list on a master server, stop and restart the NetBackup database manager and request daemons (UNIX) or the NetBackup Database Manager and NetBackup Request Manager services (Windows NT).

2. If necessary, create activity log directories for the following processes and retry the operation. Then, check the resulting activity logs on the master server:

o If the error occurred during a backup operation, check the bpsched activity logs.

o If the error occurred during a restore operation, check the bprd activity logs.

Status Code: 207 Top

Message: error obtaining date of last backup for client

Explanation: An error occurred when the backup scheduler (bpsched) tried to obtain the date of the last backup for a particular client, class, and schedule combination.

Recommended Action:

1. Verify that the NetBackup database manager (bpdbm) process (NetBackup Database Manager service on Windows NT) is running.

2. Examine the All Log Entries report for the appropriate time frame to gather more information about the failure.

3. For detailed troubleshooting information, create activity log directories for bpsched and bpdbm on the master server and retry the operation. Then, check the resulting activity logs.

Status Code: 208 Top

Message: failed reading user directed file list

Explanation: An error occurred when the backup scheduler (bpsched) attempted to read the list of files requested for a user backup or archive. This error indicates either a client-server communication problem, or a system problem on the master server where the NetBackup scheduler process (bpsched) is running.

Recommended Action: For detailed troubleshooting information, create activity log directories for bpsched and bprd on the master server and retry the operation. Then, check the resulting activity logs.

Status Code: 209 Top

Message: error creating or getting message queue

Explanation: An error occurred when the backup scheduler (bpsched) attempted to create an internal message queue construct for interprocess communication. This error indicates a problem on the master server and is most likely due to a lack of system resources for System V interprocess communication.

Recommended Action: Create a bpsched activity log directory on the master server and retry the operation. Then, determine the type of system failure by examining the error message in the bpsched activity log.

On UNIX servers, also gather the output of the ipcs -a command to see what system resources are currently in use.

211 212 213 214 215 216 217 218 219 Top

Status Code: 210 Top

Message: error receiving information on message queue

Explanation: An error occurred when one of the backup scheduler (bpsched) processes attempted to receive a message from another bpsched process on an internal message queue construct. This error indicates a problem on the master server and is likely due to problems with or a lack of system resources for System V interprocess communication.

Recommended Action: Create a bpsched activity log directory on the master server and retry the operation. Then, determine the type of system failure by examining the error message in the bpsched activity log on the master server. On UNIX servers, also gather the output of the ipcs -a command to see what system resources are currently in use.

Status Code: 211 Top

Message: scheduler child killed by signal

Explanation: A backup scheduler (bpsched) child process, which interacts with the backup restore manager (bpbrm) on the media server, was terminated. This can occur because of system administrator action.

Recommended Action: Create an activity log directory for bpsched on the master server and retry the operation. Then, to determine the cause of the child termination, examine the messages in the bpsched activity log.

Status Code: 212 Top

Message: error sending information on message queue

Explanation: The backup scheduler (bpsched) encountered an error when attempting to attach to an already existing internal message queue construct for interprocess communication. This error indicates a problem on the master server and is likely due to a lack of system resources for System V interprocess communication.

Recommended Action: Create a bpsched activity log directory on the master server and retry the operation. Then, determine the type of system failure by examining the error message in the bpsched activity log. On a UNIX server, also, gather the output of the ipcs -a command to see what system resources are currently in use.

Status Code: 213 Top

Message: no storage units available for use

Explanation: The NetBackup scheduler process (bpsched) did not find any of its storage units available for use. Either all storage units are unavailable or all storage units are configured for "on demand only" and the class and schedule does not require a specific storage unit.

Recommended Action:

1. Examine the Backup Status and All Log Entries report for the appropriate time period to determine the class or schedule that received the error.

2. Verify that the storage unit's drives are not down or waiting for media from a previous operation that did not complete.

3. Examine the storage unit configuration to verify that all the storage units do not have their "Concurrent Jobs" attribute set to 0.

4. Verify that the robot number and host name in the storage unit configuration matches the Media Manager device configuration.

5. Determine if all storage units are set to "On Demand Only" for a class and schedule combination that does not require a specific storage unit. If this is the case, either specify a storage unit for the class and schedule combination or turn off "On Demand Only" for a storage unit.

6. If the storage unit is on a UNIX NetBackup slave server, it could indicate problem with bpcd. Check /etc/inetd.conf on the slave server to verify that the bpcd entry is ok. If the storage unit is on a Windows NT NetBackup slave server, verify that the NetBackup Client service has been started on the Windows NT NetBackup slave server.

7. For detailed troubleshooting information, create a bpsched activity log directory on the master server and retry the operation. Then, check the resulting activity log.

Status Code: 214 Top

Message: regular bpsched is already running

Explanation: The NetBackup scheduler (bpsched) performs periodic checking of the class and schedule configuration to determine if there are new backups due. Error 214 indicates that when a new instance of NetBackup starts, it finds that a scheduler process is already checking the class and schedule configuration.

Recommended Action: Usually, no action is required for this condition. However, NEVER kill bpsched before doing some checking. For example, bpsched could be calling bpdbm (NetBackup Database Manager service on Windows NT) to clean up and compress the databases. To determine what the running bpsched is currently doing, examine the bpsched activity log on the master server. If necessary, enable bpsched activity logging by creating a bpsched activity log directory on the master server and retrying the operation. To check for backups do the following:

On a UNIX master server:

1. Check for active or queued backups by using the job monitor.

2. Check for active bp processes with bpps. This reveals if there are bpbrm or bptm processes running and a backup is active.

3. If there is no reason for bpsched to be running, then use kill -HUP to terminate it.

On a Windows NT NetBackup master server:

Status Code: 215 Top

Message: failed reading global config database information

Explanation: During the periodic checking of the NetBackup configuration, the NetBackup scheduler process (bpsched) was unable to read the global configuration parameters.

Recommended Action:

1. On a UNIX master server, verify that the NetBackup database manager (bpdbm) process is running. On a Windows NT master server, verify that the NetBackup Database Manager service is running.

2. Attempt to view the global configuration settings by using the the NetBackup administration interface.

3. For detailed troubleshooting information, create activity log directories for bpsched and bpdbm on the master server and retry the operation. Then, check the resulting activity logs.

Status Code: 216 Top

Message: failed reading retention database information

Explanation: During its periodic checking of the NetBackup configuration, the NetBackup scheduler process (bpsched) could not read the list of retention levels and values.

Recommended Action:

1. On a UNIX master server, verify that the NetBackup database manager (bpdbm) process is running. On a Windows NT master server, verify that the NetBackup Database Manager service is running.

2. For detailed troubleshooting information, create activity log directories for bpsched and bpdbm on the master server and retry the operation. Then, check the resulting activity logs.

Status Code: 217 Top

Message: failed reading storage unit database information

Explanation: During its periodic checking of the NetBackup configuration, the NetBackup scheduler process (bpsched) could not read the storage unit configuration.

Recommended Action:

1. On a UNIX server, verify that the NetBackup database manager (bpdbm) process is running. On a Windows NT server, verify that the NetBackup Database Manager service is running.

2. Attempt to view the storage unit configuration by using the NetBackup administration interface.

3. For detailed troubleshooting information, create activity logs for bpsched and bpdbm on the master server and retry the operation. Then, check the resulting activity logs. Ensure that the correct master server is being specified for the connection.

Status Code: 218 Top

Message: failed reading class database information

Explanation: During the periodic checking of the NetBackup configuration, the NetBackup scheduler process (bpsched) could not read the class (backup policy) configuration.

Recommended Action:

1. On a UNIX server, verify that the NetBackup database manager (bpdbm) process is running. On a Windows NT server, verify that the NetBackup Database Manager service is running.

2. Attempt to view the class configuration by using the NetBackup administration interface.

3. For detailed troubleshooting information, create activity log directories for bpsched and bpdbm on the master server and retry the operation. Then, check the resulting activity logs. Ensure that the correct master server is being specified for the connection.

Status Code: 219 Top

Message: the required storage unit is unavailable

Explanation: The class or schedule for the backup requires a specific storage unit, which is currently unavailable. This error also occurs for other attempts to use the storage unit within the current backup session.

Recommended Action: Examine the Backup Status and All Log Entries report for the appropriate time period to determine the class or schedule that received the error. Then, examine the specific class and schedule configuration to determine the required storage unit.

1. Verify that the schedule specifies the correct storage unit and the storage unit exists.

2. Verify that the Media Manager device daemon (ltid) is running (if the server is UNIX) or the NetBackup Device Manager service is running (if the server is a Windows NT system). Use bpps on UNIX and the Activity Monitor on Windows NT.

3. Verify that the Number of Drives attribute for the storage unit is not set to 0.

4. If the storage unit is a tape or optical disk, verify that at least one of the drives is in the UP state. Use the Device Monitor (on UNIX xdevadm can also be used).

5. Verify that the robot number and host in the storage unit configuration matches what is specified in the Media Manager device configuration.

6. Verify that the master server can communicate with the bpcd process on the server that has the storage unit.

a. Verify that bpcd is listening on the port for connections.
On a UNIX server, executing
netstat -a | grep bpcd
should return something similar to the following:
*.bpcd *.* 0 0 0 0 LISTEN
Do this on the server where the storage unit is connected.
On a Windows NT NetBackup server, executing
netstat -a
prints out several lines of output. If bpcd is listening, one of those lines is similar to the following:
TCP myhost:bpcd 0.0.0.0:0 LISTENING
Do this on the server where the storage unit is connected.

b. If bpcd seems to be operating correctly, create bpsched and bpcd activity log directories and retry the operation. Check the resulting activity logs for records of an earlier failure.
After each backup, the scheduler checks the storage unit to see how many drives are available (in case the backup caused a drive to be automatically downed). If bpsched cannot communicate with bpcd, it sets the number of available drives in that storage unit to 0 and further backups to that storage unit during this backup session will fail. The number of available drives remains at 0 until the scheduler is initialized again.

7. c. If the cause of the problem is not obvious, perform some of the steps in "Resolving Network Communication Problems" on page 21.

221 222 223 224 225 226 227 228 229 Top

Status Code: 220 Top

Message: database system error

Explanation: The bpdbm process (NetBackup Database Manager service on Windows NT) could not create a directory path for its configuration databases due to the failure of a system call. This is usually due to a permission problem or an "out of space" condition.

Recommended Action: Create an activity log directory for bpdbm and retry the operation. Check the resulting activity log for information.

Status Code: 221 Top

Message: continue

Explanation: This status code is used in coordinating communication between various NetBackup processes and normally does not occur. If the logs show that it is associated with a subsequent error, it usually indicates a communication problem. In this case, concentrate your troubleshooting efforts on the subsequent error.

Recommended Action: Determine the cause of the status code that follows this one.

Status Code: 222 Top

Message: done

Explanation: This status code is used in coordinating communication between various NetBackup processes and is normally not seen. If the error logs show that it is associated with a subsequent error, it usually indicates a communication problem. In this case, concentrate your troubleshooting efforts on the subsequent error.

Recommended Action: Determine the cause of the status code that follows this one.

Status Code: 223 Top

Message: an invalid entry was encountered

Explanation: A request to the bpdbm process (NetBackup Database Manager service on Windows NT) had invalid or conflicting information. This is usually a result of using software from different versions together, but can also be caused by incorrect parameters on a command.

Recommended Action: Verify that all NetBackup software is at the same version level and the command parameters are specified correctly. If neither of these is the problem, obtain detailed troubleshooting information by creating a bpdbm activity log directory and retrying the operation. Check the resulting activity log.

Status Code: 224 Top

Message: there was a conflicting specification

Explanation: A request to the bpdbm process (NetBackup Database Manager service on Windows NT) had conflicting information. This is usually a result of using software from different version levels together.

Recommended Action: Verify that all NetBackup software is at the same version level. If that is not the problem, obtain detailed troubleshooting information by creating bpdbm and admin activity log directories and retrying the operation. Check the resulting activity logs.

Status Code: 225 Top

Message: text exceeded allowed length

Explanation: A request containing text that exceeds a buffer size was made to the bpdbm process (NetBackup Database Manager service on Windows NT). This is usually a result of using software from different version levels together.

Recommended Action: Verify that all NetBackup software is at the same version level. If that is not the problem, create activity log directories for bpdbm and admin. Then, retry the operation and examine the resulting activity logs.

Status Code: 226 Top

Message: the entity already exists

Explanation: The configuration already has an entity with the same name or definition. For example, you see this status if you try to add a new class when an existing class has the same name or definition (attributes, clients, and so on).

Recommended Action: Correct your request and re-execute the command.

Status Code: 227 Top

Message: no entity was found

Explanation: The item requested was not in the database. For example, the entity could be a file or class information.

Recommended Action: A common cause for this problem is a query that has no matching images. Specify different parameters or options for the operation and try it again.

Status Code: 228 Top

Message: unable to process request

Explanation: An inconsistency exists in the database or a request was made that would be improper to satisfy.

Recommended Action:

1. If this involves a slave server, verify that its server list specifies the correct master server. On a UNIX server, the master server is the first SERVER entry in the bp.conf file. On a Windows NT server, the master is designated as the Current server on the Servers tab in the NetBackup Configuration dialog box. To display this dialog box, start the Backup, Archive, and Restore interface and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57).

2. For detailed troubleshooting information, create a bpdbm activity log directory and retry the operation. Then, check the resulting activity log.

Status Code: 229 Top

Message: events out of sequence - image inconsistency

Explanation: A request was made which, if satisfied, would cause the image database to become inconsistent.

Recommended Action: Obtain detailed troubleshooting information by creating an activity log directory for bpdbm. Then, retry the operation, save the resulting activity log, and call customer support.

231 232 233 234 235 236 237 238 239 Top

Status Code: 230 Top

Message: the specified class does not exist in the configuration database

Explanation: The specified class name does not exist.

Recommended Action: Correct your parameters or options and retry the operation.

Status Code: 231 Top

Message: schedule windows overlap

Explanation: The start and duration times specified for one day of the schedule overlap with another day of the schedule.

Recommended Action: Correct the schedule to eliminate the overlapping backup windows.

Status Code: 232 Top

Message: a protocol error has occurred

Explanation: This is an intermediate status code that usually precedes another status code. It indicates that either the bpdbm process (NetBackup Database Manager service on Windows NT) or the process communicating with it has received unexpected information.

Recommended Action: Create an activity log directory for bpdbm. Then, retry the operation, save the activity log, and call customer support.

Status Code: 233 Top

Message: premature eof encountered

Explanation: This is an intermediate status code that usually precedes another status code and is associated with a problem in network communication.

Recommended Action: During a restore, this means that tar (on the client) received a stream of data that was not what it expected. If this is a new configuration, verify that the tape drive is configured for variable mode (see the Media Manager Device Configuration Guide).

If the communication failure is not due to an interrupt on a client system, save all error information and call customer support.

Status Code: 234 Top

Message: communication interrupted

Explanation: This is an intermediate status code that usually precedes another status code and is associated with a problem in network communication. A process, either server or client, received an interrupt signal.

Recommended Action: Save all error information and call customer support.

Status Code: 235 Top

Message: inadequate buffer space

Explanation: This code usually indicates a mismatch between server and client software versions.

Recommended Action:

1. Verify that all NetBackup software is at the same version level. Update earlier versions of NetBackup software.

· On UNIX NetBackup servers and clients, check the /usr/openv/netbackup/bin/version file.

· On Windows NT NetBackup servers, check the install_path\NetBackup\version.txt file or the About NetBackup command on the Help menu.

· On Microsoft Windows clients, check the About NetBackup command on the Help menu.

· On NetWare target clients, check the Version entry in the bp.ini file. If the client software is earlier than 3.0, verify that the client is in a Standard type class.

· On Macintosh clients, check the version file in the bin folder in the NetBackup folder in the Preferences folder.

2. If the problem persists, save all error information and call customer support.

Status Code: 236 Top

Message: the specified client does not exist in an active class within the configuration database

Explanation: A client name was not specified or the specified client does not exist.

Recommended Action: Activate the required class, correct the client name, or add the client to a class that meets your needs. After making the correction, retry the operation.

Status Code: 237 Top

Message: the specified schedule does not exist in an active class in the configuration database

Explanation: The specified schedule does not exist in the NetBackup configuration.

Recommended Action: Activate the required class, correct the schedule name, or create a schedule in a class that meets your needs. After making the correction, retry the operation.

Status Code: 238 Top

Message: the database contains conflicting or erroneous entries

Explanation: The database has an inconsistent or corrupted entry.

Recommended Action: Obtain detailed troubleshooting information for bpdbm (NetBackup Database Manager service on Windows NT) by creating an activity log directory for it. Then, retry the operation, save resulting activity log, and call customer support.

Status Code: 239 Top

Message: the specified client does not exist in the specified class

Explanation: The specified client is not a member of the specified class.

Recommended Action: Correct the client name specification, specify a different class, or add the required client name to the class. After making the correction, retry the operation.

241 242 243 244 245 246 247 248 249 Top

Status Code: 240 Top

Message: no schedules of the correct type exist in this class

Explanation: The appropriate schedule was not found in the specified class. For example, a user backup specified a class name but no user backup schedule exists in that class.

Recommended Action: Specify a different class or create a schedule of the needed type in the class. After making the correction, retry the operation.

Status Code: 241 Top

Message: the specified schedule is the wrong type for this request

Explanation: The schedule that was specified for an immediate manual backup is not for a full nor an incremental backup. It must be one of these.

Recommended Action: Specify only full or incremental schedules for manual backups. If one does not exist in the class, create one.

Status Code: 242 Top

Message: operation would cause an illegal duplication

Explanation: Processing the request would cause a duplicate database entry. This is usually due to a mistake in specifying media IDs for NetBackup database backups.

Recommended Action: Check the error reports to determine the specific duplication that would occur. Correct the settings for the operation and retry it.

Status Code: 243 Top

Message: the client is not in the configuration

Explanation: The specified client name was not in the database.

Recommended Action: Either correct the client name or add the client to the desired class.

Status Code: 244 Top

Message: main bpsched is already running

Explanation: A bpsched process tried to become the main backup scheduler but another process is currently in this mode.

Recommended Action: None.

Status Code: 245 Top

Message: the specified class is not of the correct client type

Explanation: A user backup specified a class that is not the type required for the client.

Recommended Action: Retry the operation by specifying a class that is the correct type for the client. If such a class does not exist, create one.

Status Code: 246 Top

Message: no active classes in the configuration database are of the correct client type

Explanation: A user backup request was not satisfied because no active classes were the type required for the client.

Recommended Action: Create or activate an appropriate class so the user backup request can be satisfied.

Status Code: 247 Top

Message: the specified class is not active

Explanation: Backups for the specified class are disabled because the class is inactive.

Recommended Action: Activate the class and retry the operation.

Status Code: 248 Top

Message: there are no active classes in the configuration database

Explanation: No active class was found that would satisfy the request.

Recommended Action: Activate the appropriate class and retry the operation.

Status Code: 249 Top

Message: the file list is incomplete

Explanation: The server timed out while waiting for the client to finish sending the file list, or a sequencing problem occurred.

Recommended Action: Obtain additional information by first creating activity logs and then attempting to recreate the error. The activity logs to create are as follows:

· On the server, bptm, bpbrm, and bpdbm.

· On UNIX and Windows NT clients, bpbkar.

· On other clients, bpcd.

To increase the amount of information included in the logs. See "Activity Logs on PC Clients" on page 67.

251 254 Top

Status Code: 250 Top

Message: the image was not created with TIR information

Explanation: This is an internal error and should not be seen by customers. Recommended Action: Obtain detailed troubleshooting information by creating activity logs for bptm and bpdbm on the server. Then, retry the operation and check the resulting activity logs.

Status Code: 251 Top

Message: the tir information is zero length

Explanation: For a true-image backup, the client sent no file information to the master server. NetBackup discovered this condition when it attempted to write the TIR information to media.

Recommended Action:

1. Check the file list for the class and the exclude and include lists on the client to verify that the client has files that are eligible for backup. For example, this status code can appear if the exclude list on the client excludes all files.

2. To obtain detailed troubleshooting information, create activity logs for bptm and bpdbm on the server. Then, retry the operation and check the resulting activity logs.

Status Code: 254 Top

Message: server name not found in the bp.conf file

Explanation: This error should not occur through normal use of NetBackup.

Recommended Action: Save all error information and call customer support.

veritas netbackup tricks and commands

2009-04-22T06:11:00.000-07:00

Netbackup Tips and Tricks (Unix)

Glossary
Term Definition
CLI Command Line Interface
GUI Graphical User Interface
Media Server
Master Server

Starting and Stopping Netbackup
Stopping Netbackup
• /usr/openv/netbackup/bin/K77netbackup --> graceful shutdown
• /usr/openv/netbackup/bin/bpps -a --> check for any remaining processes
• /usr/openv/netbackup/bin/goodies/bp.kill_all ---> kills all remaining netbackup processes, not necessarily graceful
• /usr/openv/netbackup/bin/bpps -a --> check for any remaining processes
• kill -9 for any remaining. NOTE: unkillable processes may require a reboot
Starting Netbackup
• /usr/openv/netbackup/bin/S77netbackup --> after bp.kill_all, to restart
• /usr/openv/volmgr/bin/vmd
Common Tasks
Starting the Administration GUI
• java from the windows client
• x-windows from the server - /usr/openv/netbackup/bin/xnb &
Checking Backup Status
• Activity Monitor or
• /usr/openv/netbackup/bin/admincmd/bpdbjobs -report
Cleaning a tape manually
• Identify the drive name to be cleaned
o tpclean -L
• Manually clean the drive:
o tpclean -C
Determining what tapes were used for a backup
• GUI
o Backup and Restore --> Find the file system --> Preview Media Button
• CLI
o Find the correct backup images
 bpimagelist -U -client -d -e
o Find the media used for those images
 bpimagelist -U -client -d -e -media
Listing the files in a backup

Find the tape(s) used (above procedure using bpimagelist)
cd /usr/openv/netbackup/db/jobs/done
Run the following script and redirect it's output to a text file:
for file in `grep MOUNTING *|grep |awk '{print $1}'|sed 's/:MOUNTING//'`
do
echo $file
grep PATH_WRITTEN $file|awk '{print $3}'
echo " "
echo "==========================================End of Image======================================"
echo " "
done

This process works for NBU V3.4:
• cd /usr/openv/netbackup/db/images/
• ls -ltr --> this will identify the directory with the proper date
• verify directory with "bpdbm -ctime
• cd
• ls -ltr --> lists all of the backups for this client on this date
• cat __.f | awk '{print $10}' --> this prints out the files in the backup

For NBU > V3.4
• bpflist --help --> undocumented netbackup command to list files from a binary .f file

Inventory the Robot
• Inventory Robot --> /opt/openv/volmgr/bin/vmcheckxxx -rt robot_type -rn robot_number -list (where robot_type is tld, acs, . . .)
• Inventory Robot and Update Configuration --> /opt/openv/volmgr/bin/vmupdate -rt robot_type -rn robot_number -list (where robot_type is tld, acs, . . .)
Listing Properties of the Volume Pools
• vmpool -listall
Scratch Tapes
• Count scratch tapes: /usr/openv/volmgr/bin/vmquery -pn Scratch | grep -c "robot slot"
• Moving tapes to the scratch pool
o If Needed - Expire the tape
 bpexpdate -ev -d 0 -force -host
o Move the tape
 vmchange -p 2 -m
Checking Drive Usage
• /usr/openv/volmgr/bin/vmoprcmd
Taking a drive down or up
• /usr/openv/volmgr/vmoprcmd -down
• /usr/openv/volmgr/vmoprcmd -up

Performing a Restore
• From the GUI
o user backup & restore --> configuration --> client
o user backup & restore --> configuration --> client to restore
o directory to search
o directory depth
o date range
o file --> browse backups for restore
Adding New Tapes to the Library
• Using the GUI
o Media Management --> Actions --> New --> Single Volume . . -->
o Media Type (ie DLT)
o Robot Type (ie TLD)
o Media ID (from Inventory)
o Slot Number (from Inventory)
o Robot Number (ie 0)
o Volume Group
o Volume Pool (ie Scratch)
• Using the CLI
o vmadd -m -mt -verbose -rt -b -rn -rc1 -p -mm
 vmpool -listall --> lists all pools, both name and number
o For example: vmadd -m 000151 -mt dlt -verbose -rt tld -b 000151 -rn 0 -rc1 8 -p 2 -mm 0
Re-using Tapes from other systems or older Netbackups
• Expire the media
o bpexpdate -ev MEDIA_ID -d 0 -force -host HOST
• Deassign the media
o vmquery -deassignbyid MEDIA_ID 4 0
• Move to the scratch pool
o vmchange -m MEDIA_ID -p POOL#
• Relabel the media
o bplabel -ev CIM572 -d dlt -p Scratch
Changing the attributes of media
• Changing the barcode
o vmchange -barcode CYM100D -m CYM100
• Changing the Volume Pool
o vmchange -m MEDIA_ID -p POOL#

To expire media
• bpexpdate -ev -d 0 -force -host
To unfreeze media
• List the frozen media
o /usr/openv/netbackup/bin/goodies/available_media | grep -i FROZEN
• Unfreeze the media
o bpmedia -unfreeze -ev -h
To relabel a tape
• bplabel -ev -d -p
• bplabel -ev 000687 -d dlt -p TriVrgt_OFFSITE
To remove media from the Netbackup database
• Verify that there are no images on the tape
o bpimmedia -mediaid 000687 -L
• Expire the tape
o bpexpdate -ev 000687 -d 0 -host scorpius -force
• Get the status and pool number of the tape
o vmquery -m 000687
• Deassign the tape
o vmquery -deassignbyid
o vmquery -deassignbyid 000687 4 0x0
• Delete the tape
o vmdelete -m 000687

Installing the Netbackup Client
• /update_clients -ForceInstall -ClientList /tmp/clients.lst
o requires that TMPDIR and TEMPDIR be set correctly
Excludng files from backup on a client
• Create /usr/openv/netbackup/exclude_list
• Put the file specifications of the files/directories to be excluded
o /mnt/directory/*
Displaying Information about a Tape
• vmquery -m --> Displays attributes about a particular tape
• bpmedialist -U -mcontents -ev 000687 --> Displays media contents
• bpmedialist -U -mlist --> List of all media
• bpmedialist -U -mlist -ev CYM966 --> Listing of a particular media id
• bpimmedia -mediaid 000687 -L --> Listing of images on a tape
Robtest Commands
• Starting robtest
o robtest
o 1 --> to select TLD 0
• Getting help
o ?
• Looking at contents of the tape drives
o s d
• Looking at the contents of the library
o s s
• Moving a tape from a drive to a library slot
o s d --> to identify drive number that has tape (Contains Cartridge = yes, Barcode=XXXXXX)
o s s --> to identify an empty slot in the tape library (Netbackup will need to be re-inventoried)
o m d# s# --> from from drive # to slot #
o s d --> verify the tape drive is empty
o s s --> verify the library slot has the tape

Configuration Files
/usr/openv/netbackup/bp.conf
• configuration file, sets backup server and backup clients
• force statement must be correct
• client to browse from
• client to restore to
/usr/openv/volmgr/vmconf
Logfiles
To utilize logfiles, create the corresponding directory in /usr/openv/netbackup/logs

Server Logfile directories:
• admin - adminstrative commands
• bpbrm - backup and restore manager
• bpcd - client daemon
• bpdbjobs - database manager program process
• bpdm - disk manager process
• bpjava-msvc - Java application server authentication service
• bpjava-usvc - process that services Java requests
• bprd - request daemon process
• bpsched - scheduler process that runs on master servers
• bptm - tape/optical media management process
• user-ops - required directory for use by Java programs
• xbpadm - X based administration utility
• xbpmon - X based job monitor process
Client Logfile directories:
• bp - client user interface process
• bparchive - archive program
• bpbackup - backup program
• bpbkar - program that generates golden images
• bpcd - client daemon
• bpjava-msvc - Java application server authentication service
• bpjava-usvc - process that services Java requests
• bplist - program that lists backed up and archived files
• bpmount - program that determines local mountpoints and wildcard expansion for multiple streams
• bphdb - Oracle database backup program start process
• db_log - database specific extension log
• tar - tar process log during restores
• user_ops
Media Manager logging automatically goes to the system log using syslogd logging facility
.Logging will only occur if these directories are created. These directories will generate a lot of data and should be deleted when no longer necessary.

To increase the amount of logging information set VERBOSE=2 in /usr/open/netbackup/bp.conf (default is VERBOSE=1)
Processes
ltid
acsd
vmd

Useful Commands

bpcllist - list classes
bpclinfo -L --> displays info about a class
vmpool - volume pools
vmpool -listall
vmpool -listscratch
bplabel -ev -d hcart
bpbackup db --> backs up the catalog
bpclclients --> lists the clients for a particular policy (class)
Troubleshooting
bperror -statuscode <-- displays information about the netbackup error.

No Backups are running:
• Check system log file for error messages
• Stop and restart all the netbackup processes
• Look for a downed drive
o /usr/openv/volmgr/bin/vmoprcmd
o /usr/openv/volmgr/bin/vmoprcmd -up 0 --> this will bring up drive 0 if it's control shows as down
• Look for pending requests
o /usr/openv/volmgr/bin/vmoprcmd or gui --> device management
o If there is a pending request either re-assign it to a drive, or deny the request
Downed drive does not come back up or does not stay up
• Check for a hardware problem by looking for messages on the tape library
• Make sure there is not a tape stuck in the drive
o Use robtest (described above) to look at the drives
 If there is a tape stuck in the drive, try to remove it using robtest
 If robtest fails, then you must manually remove it.
Verify the Client is communicating properly:
• bpclncmd -ip --> from both client and server
• bpclntcmd -hn --> from both client and server
• bpclntcmd -pn --> from client only

Device Actions
Device Management --> info about tape drives
• dlt
• hcart (ultrium)
Media Actions
Media id must agree with # of the tape
Create a media id
• actions -->new-->single volume-->dlt cart (not dlt2)
• put it into the "netbackup" volume pool
Netbackup Client

To check things out do this:

It could be a couple things. Mostly DNS, bp.conf, or something stupid. On
the client run this command

/usr/openv/netbackup/bin/bpclntcmd -pn

/usr/openv/netbackup/bin/bpclntcmd -server "server name"

/usr/openv/netbackup/bin/bpclntcmd ip "ip_address"

One of these usually fails and your able to fix it right off

1074 ./bpclntcmd -hn corpbu1
1075 ./bpclntcmd -ip 10.194.1.129
1076 ping 10.194.1.129
1077 ./bpclntcmd -hn corpldv1
1078 ./bpclntcmd -hn corpbu1.corporate.vox.net
1079 ping corpldv1
1080 ./bpclntcmd -ip 10.194.1.120

Must be able to resolve correctly from the master server and the client or it will not work!!!

Netbackup Command
Master Server Daemons/Processes
Request daemon bprd
Scheduler bpsched (started with bprd)
Netbackup database manager bpdbm (started with bpsched)
Job Monitor bpjobd (started with bpdbm)
Media Server Daemons/Processes
Communications daemon bpcd
Backup and restore manager bpbrm (started with bpcd)
Tape Manager bptm (started with bpbrm)
Disk Manager bpdm (started with bpbrm)
Media Manager ltid
Bar code reader avrd (started with ltid)
Remote device management/ controls volume database vmd (started with ltid)
Roboticdaemon (one on each media server) talks to tldcd tldd (started with ltid)
Robotic control daemon talks to the robot directl via scsi tldcd (started with ltid)
Catalogs
Master Server
Information about backed-up files image - /opt/openv/netbackup/db
Storage Unit, Global Configuration, Catalog backup configuration. config - /opt/openv/netbackup/db
Backup Policy information class - /opt/openv/netbackup/db
Job status information jobs - /opt/openv/netbackup/db
Netbackup logs with error and status information error - /opt/openv/netbackup/db
Information on volumes, volume pools, scratch pool and volume groups volume - /opt/openv/volmgr/database
Media Server
Tracks assigned volumes (media that has data them) media - /opt/openv/netbackup/db
Information about devices managed by the media server device - /opt/openv/volmgr/database
Log and Information Files
Netbackup and Patch versions /opt/openv/netbackup/bin/version
Media Version /opt/openv/volmgr/version
Patch Level history /opt/openv/netbackup/patch/patch.history
Buffer size /opt/openv/netbackup/db/config/SIZE_DATA_BUFFERS
Number of buffers /opt/openv/netbackup/db/config/NUMBER_DATA_BUFFERS
Network Buffer Size /opt/openv/netbackup/NET_BUFFER_SZ (default = 32)
Java GUI authorisation /opt/openv/java/auth.conf
Catalog type (binary or ASCII) /opt/openv/netbackup/db/config/cat_format.cfg
Netbackup and media manager parameter files /opt/openv/netbackup/bp.conf
/opt/openv/volmgr/vm.conf
Corrupt Database image files (5.0 and above) /opt/openv/netbackup/db.corrupt
Server Commands
Check license details /opt/openv/netbackup/bin/admincmd/get_license_key
Start Netbackup netbackup start

/opt/openv/netbackup/bin/initbprd (master)
/opt/openv/volmgr/bin/vmd (media)
Stop Netbackup (does not disconnect GUI sessions) netbackup stop
/opt/openv/netbackup/bin/admincmd/bprdreq -terminate (master)
/opt/openv/netbackup/bin/bpdbm -terminate (master)
Stop Netbackup and kill all GUI sessions /opt/openv/netbackup/bin/goodies/bp.kill_all
Start the GUI /opt/openv/netbackup/bin/jnbSA
Scan for tape devices sgscan (solaris)
ioscan (HPUX)
Display all Netbackup processes bpps -a
lists servers errors bperror -U -problems -hoursago
bperror -U -backstat -by_statcode -hoursago
display information on a error code bperror -statuscode [-recommendation]
Reread bp.conf file without stopping Netbackup bprdreq -rereadconfig
Check database consistency bpdbm -consistency 1
bpdbm -consistency 2
Check for the below lines:
Bad image header
Does not exist
Netbackup Recovery
Device catalog is intact bprecover -l -m -d dlt (listing)
bprecover -r -m -d dlt (recovering)
Device catalog is gone or corrupted bprecover -l -tpath (listing)
bprecover -r -tpath (recovering)
Disk backups bprecover -l -dpath (listing)
bprecover -r -dpath (recovering)
Volume Commands
Tape Drive and Inventory Commands
List drive status, detail drive info and pending requests vmoprcmd
List the tape drive status vmoprcmd -d ds
List the pending requests vmoprcmd -d pr
Control a tape device vmoprcmd [-reset][-up][-down]
List all changes in the robot(but do not update) vmupdate -recommend -rt tld -rn 0
vmcheckxxx -rt tld -rn 0 -recommend
Empty the robot and re-inventory (using barcodes) vmupdate -rt tld -rn -rh -vh -nostderr -use_barcode_rules -use_seed -empty_ie
Tape Media Commands
List all pools vmpool -listall -bx
List tapes in pool vmquery -pn -bx
List all tapes in the robot vmquery -rn 0 -bx |grep 'TLD' | sort +4
List cleaning tapes vmquery -mt dlt_clean -bx
List tape volume details vmquery -m
Delete a volume from the catalog vmdelete -m
Change a tapes expiry date vmchange -exp 12/31/06 23:59:58 -m
Change a tape's media pool vmchange -p -m
Media commands
List the storage units bpstulist -U
Freeze or unfreeze media bpmedia [-freeze][-unfreeze] -ev
List media details bpmedialist -ev
List media contents bpmedialist -U mcontents -m
List backup Image Information bpimagelist -backupid
Expire client images bpimage -cleanup -allclients
Expire a tape bpexpdate -d 0 -ev -force
List all netbackups jobs bpdbjobs -report [-hoursago]
Move media from one media server to another bpmedia -movedb -newserver -oldserver
Tape/Robot commands
List tape drives tpconfig -d
List cleaning times on drives tpclean -L
clean a drive tpclean -C
change a drives cleaning frequency tpclean -F
set a drives cleaning time to zero tpclean -M
Move tapes within robot using robtest robtest
commands that can be used are as follows:

s s (show slots)
s d (show drives)
s i (show load port)
m s250 d5 (move tape from slot 250 into drive 5)
uload d5 (unload tape from drive 5)
m d5 s250 (move tape from drive 5 to slot 250)
m s250 i1 (mov tape from slot 250 to load port 1)

List load port tapes echo "s i q" | tldtest -r /dev/sg/c0t4l0
List all slot contents echo "s s q" | tldtest -r /dev/sg/c0t4l0
List tape drive contents echo "s d q" | tldtest -r /dev/sg/c0t4l0
Move a tape in s100 to drive 1 echo "m s100 d1" | tldtest -r /dev/sg/c0t4l0
Move a tape to load port 1 echo "m s100 i1" | tldtest -r /dev/sg/c0t4l0
Archiving Commands
list archive info bpcatlist -client all -before Jul 01 2006
bpcatlist -client all -before Aug 01 2006
archive and remove images bpcatlist -before Jul 01 2006 | bpcatarc | bpcatrm
restore archive files bpcatlist -before Jul 01 2006 | bpcatres
Client commands
test client connectivity bpclntcmd [-ip ]
bpclntcmd [-hn ]
bpclntcmd [-pn]
bpclntcmd [-sv]

1.To expire the tape

rakshak:/usr/openv/netbackup/bin/admincmd [23] > ./bpexpdate -m SVOB06 -d 0

rakshak:/usr/openv/volmgr/bin [40] > ./vmdelete -m SVOB02

/var/adm [1] >> media

/var/adm [2] >> bpps -a
NB Processes
------------
root 536 1 0 Dec 23 ? 0:00 /bin/sh /usr/openv/netbackup/bin/admincmd/nbdbdmon --user=root
root 548 536 0 Dec 23 ? 0:00 /usr/openv/db/bin/nbdbd --basedir=/usr/openv/db --datadir=/usr/openv/db/var --u
root 441 1 0 Dec 23 ? 0:17 /usr/openv/netbackup/bin/bprd
root 476 1 0 Dec 23 ? 3:23 /usr/openv/netbackup/bin/bpdbm
root 12691 441 0 23:30:19 ? 0:12 /usr/openv/netbackup/bin/bpsched -ppid 441
/var/adm [12] >> bpps -a to kill the GUI of rakshak

root 11142 11120 0 09:25:25 pts/4 1:06 /usr/openv/java/jre/bin/java -Dvrts.NBJAVA_CONF=/usr/openv/java/nbj.conf -Djava
root 27301 27279 0 Jan 11 pts/2 5:31 /usr/openv/java/jre/bin/java -Dvrts.NBJAVA_CONF=/usr/openv/java/nbj.conf -Djava

To check the media list

/usr/openv/netbackup/bin/admincmd [15] > media

Netbackup reboot
Hi Jerome,

Following timing where I am going to run the backup: ( Please check the below ones, because it's full backup and I have not run from last 2 months )

ZIN05VIEW01:10:15 Sat morning
ZIN05VIEW02:10:30 Sat morning
ZIN05VIEW03:10:45 Sat morning

Rakshak:23:00 Sat night
ZIN05VOB03:23:00 Sat Night

Check the below steps , If you rebooting the vobserver and veiew servers.

A. Telnet to rakshak
B. Set the display
C. Go to /usr/openv/netbackup/bin and then run ./jnbSA &
D. Gui will open then on the password tab give the rakshak root passowrd.
E. Check any active job is running by clicking activity monitor.
F. If at all any jobs pertaining to critical servers are running, then select the jobs and cancel.

If you are rebooting
VIEW01
VIEW02
VIEW03
VOB03
Then check the follwing process are running or not

1. Go to /usr/openv/volmgr/bin/sgscan

zin05view01:/usr/openv/volmgr/bin # ./sgscan
#
#WARNING: detected StorEdge Network Foundation connected devices not in
# SG configuration file:
#
# Device World Wide Port Name 21000004cf277475
# Device World Wide Port Name 21000004cf9b645a
# Device World Wide Port Name 21000004cfa17ac8
# Device World Wide Port Name 5080020000197169
# Device World Wide Port Name 21000004cfa17b08
# Device World Wide Port Name 500000e010136591
# Device World Wide Port Name 21000004cfa17211
# Device World Wide Port Name 21000004cf9b61fb
# Device World Wide Port Name 21000004cf9b6ada
# Device World Wide Port Name 21000004cf9b6aee
# Device World Wide Port Name 21000004cf9b6898
# Device World Wide Port Name 21000004cf9b61df
# Device World Wide Port Name 22000004cf9b645a
# Device World Wide Port Name 22000004cf277475
# Device World Wide Port Name 22000004cfa17ac8
# Device World Wide Port Name 508002000019716a
# Device World Wide Port Name 22000004cf9b61fb
# Device World Wide Port Name 22000004cfa17211
# Device World Wide Port Name 22000004cf9b6ada
# Device World Wide Port Name 22000004cf9b6aee
# Device World Wide Port Name 22000004cf9b6898
# Device World Wide Port Name 22000004cf9b61df
# Device World Wide Port Name 22000004cfa17b08
# Device World Wide Port Name 500000e010136592
#
# See /usr/openv/volmgr/MediaMgr_DeviceConfig_Guide.txt chapter
# "Special configuration for "Sun StorEdge Network Foundation" HBA/Driver"
# for information on how to use sg.build and sg.install to
# configure these devices
#

/dev/sg/c0tw2100001086103bacl0: Changer: "ATL M2500"
/dev/sg/c0tw2100001086103bacl1: Tape (/dev/rmt/3): "QUANTUM SDLT320"
/dev/sg/c0tw2100001086103bacl2: Tape (/dev/rmt/2): "QUANTUM SDLT320"
/dev/sg/c0tw2100001086104420l0: Tape (/dev/rmt/1): "QUANTUM SDLT320"
/dev/sg/c0tw2100001086104420l1: Tape (/dev/rmt/0): "QUANTUM SDLT320"

If it's not showing then do

/etc/rc2.d/S99M2500 start

Again run the sgscan command

2. go to /usropenv/netbackup/bin/bpps -a

NB Processes
------------
root 27315 1 0 Sep 22 ? 0:00 /bin/sh /usr/openv/netbackup/bin/admincmd/nbdbdmon --user=root
root 27327 27315 0 Sep 22 ? 0:00 /usr/openv/db/bin/nbdbd --basedir=/usr/openv/db --datadir=/usr/openv/db/var --u

MM Processes
------------
root 29066 28896 0 Sep 22 ? 0:00 avrd
root 27238 1 0 Sep 22 ? 0:01 vmd
root 28896 1 0 Sep 22 ? 0:02 /usr/openv/volmgr/bin/ltid
root 29064 28896 0 Sep 22 ? 0:00 tldd
root 526 27238 0 Sep 22 ? 0:01 rdevmi -sockfd 6 -r
root 29903 27238 0 Sep 22 ? 0:01 rdevmi -sockfd 6 -r
root 66 27238 0 Sep 22 ? 0:01 rdevmi -sockfd 6 -r
root 15380 27238 0 11:07:44 ? 0:00 rdevmi -sockfd 6 -r

If it's not running then go to the below path to start the netbackup service.

/usr/openv/netbackup/bin/goodies/netbackup

3. On vob03 check vxtask list whether the flashsnap is running or not.

Hope you will understand my problem....

Regards,

Ragha.....

To freeze the tapes you need to login to the respective media servers

cd /usr/openv/netbackup/bin/admincmd
zin05view03:/usr/openv/netbackup/bin/admincmd # ./bpmedia -freeze -m SVEW03

To check the media list 2 methods

1. avilable media it will displays only what all the media available and which media which belongs
2.bpmedialisd give all the information about what all the media availbles and media which belongs to the pools and when it allocated and expiration last date updated and read etc.. with respect to media servers.

1.rakshak:/ [1] > cd /usr/openv/netbackup/bin/admincmd/
rakshak:/usr/openv/netbackup/bin/admincmd [2] > ./bpmedialist

Server Host = rakshak

id rl images allocated last updated density kbytes restores
vimages expiration last read <------- STATUS ------->
--------------------------------------------------------------------------------
DMON01 8 100 06/14/2004 15:13 N/A dlt2 2212471 0
MPX 10/19/2005 16:19 11/03/2004 19:13 IMPORTED

SDEL01 24 395 04/23/2004 09:45 12/09/2004 17:29 dlt2 211914147 2
MPX 12/07/2014 17:29 12/29/2004 12:18

SDLY01 5 2611 08/26/2004 21:05 01/12/2005 21:57 dlt2 323247463 0

Server Host = zin05view01

id rl images allocated last updated density kbytes restores
vimages expiration last read <------- STATUS ------->
--------------------------------------------------------------------------------
SVEW02 8 3 12/31/2004 23:37 01/12/2005 23:30 dlt2 192245499 0
MPX 01/12/2006 23:30 N/A

SVEW06 8 317 12/22/2004 11:29 12/31/2004 23:37 dlt2 421554297 0
MPX 12/31/2005 23:37 N/A FULL

Server Host = zin05view02

id rl images allocated last updated density kbytes restores
vimages expiration last read <------- STATUS ------->
--------------------------------------------------------------------------------
SVEW01 8 3 01/01/2005 02:40 01/12/2005 23:54 dlt2 225510259 0
MPX 01/12/2006 23:54 N/A

SVEW13 8 229 12/18/2004 01:02 01/01/2005 02:40 dlt2 398799500 0
MPX 01/01/2006 02:40 N/A FULL

SVEW14 8 210 12/18/2004 01:02 12/25/2004 01:37 dlt2 408836258 0
MPX 12/25/2005 01:37 N/A FULL

SVEW15 8 1 12/25/2004 01:37 12/25/2004 01:37 dlt2 13287112 0

Server Host = zin05view03

id rl images allocated last updated density kbytes restores
vimages expiration last read <------- STATUS ------->
--------------------------------------------------------------------------------
SVEW03 8 2 01/11/2005 09:23 01/13/2005 00:55 dlt2 101592944
MPX 01/13/2006 00:55 N/A

SVEW10 8 14 12/18/2004 11:53 12/18/2004 12:04 dlt2 18070585 0
MPX 12/18/2005 12:11 N/A

SVEW11 8 44 12/18/2004 11:02 01/11/2005 09:23 dlt2 391753568 0
MPX 01/11/2006 09:23 N/A FULL

VxVm commands quick reference guide

2009-04-15T06:28:00.001-07:00

VERITAS Volume Manager
VM daemons
vxconfigd Maintains system configuration in the kernel & disk (private region). If the daemon is stopped it does not disable any configuration state loaded into the kernel, it only affects the ability to make configuration changes until vxconfigd is restarted.
It can be in three states:
Enable = Normal mode
Disable = Most operations cannot be be used
Booted = Normal startup while using boot disk group
vxrelocd Monitors for failure events and relocates failed sub disks
vxconfigbackupd Used to backup configuration changes, the files created can be used with vxmake to restore lost groups.
vxnotify Display VERITAS volume manager events used with the vxconfigd daemon
Kernel Info
Kernel States The kernel can be in three states:
Enabled - both private and public regions are accessible
Disabled - no private or public regions are accessible
Detached - only private regions are accessible

VM utilities
VxVM debug vxconfigd -k -m enable -x
-x log log to /var/vxvm/vxconfigd.log
-x logfile = log to filename
-x syslog log to syslog
-x timestamp date and timestamp every entry
-x tracefile=name log all possible tracing to file
vxiod The vxiod utility starts, stops, or reports on VERITAS Volume Manager (VxVM) I/O daemons. An I/O daemon provides a process context for performing I/O in VxVM.Manage extended disk i/o & handles dirty regions, logging
vxiod set = set number of running viod daemon
Note: when run on its own it displays # of vxiod daemons that are running.
vxdctl [option] The vxdctl utility manages aspects of the state of the volume configuration daemon vxconfigd and also manages aspects of configuration for bootstrapping the rootdg disk group.
mode = what mode the vxconfigd is running in
enable = enable the vxconfigd daemon (reread the db)
disable = disable the vxconfigd daemon
stop = kill the vxconfigd daemon (Use 'vxconfigd -k -m disable' to start again)
license [init] = print out license info or reread licenses
support = display version and components
list = display entries in /etc/vx/volboot
init [dmp] = recreate /etc/vx/volboot
Note: when is disabled or stop mode no VX commands will be able to run
vxinstall Install volume manger (use /etc/vx/disk to exclude any disks or controllers)
Disk Regions
Private This is were VERITAS holds the meta data regarding the disk. A copy of the configuration database is copied to each private region within the disk group. VERITAS will try and keep 5 copies of the configuration database.
Normally configured as slice 3
Public This is the area that will store the user’s data.
Normally configured as slice 4.
Disk Layouts
Sliced Disk layout private region and public region slices are on separate partitions (3 & 4), this type of disk is not suitable for moving between different O/S's but are suitable for boot partitions
Can be converted to CDS
CDS (Cross-platform Data Sharing) private and public regions are one slice (slice 7) , this type is suitable for moving between different O/S's but not suitable for boot partitions’.
Simple Private and public are the same partition but continuous (slice 3)
Can be converted to CDS
None None partitioning
VxVM Configuration Database
DB size vxdg list | grep permlen - the size of the configuration db
DB location vxdisk list | grep -i configs - db location
File Locations
vxinstall has not be run /etc/vx/reconfig.d/state.d/install-db
Host ID's /etc/vx/volboot
backup config files (vxconfigbackupd) /etc/vx/cbr/bk
delete or deported disk group config files /etc/vx/dgcfg/deport
All commands logs /var/adm/vx/veacmdlog
Licenses /etc/vx/licenses/lic
Imported disk groups info /var/vxvm/tempdb

Note: to clear the tempdb file:
vxconfigd -k -x cleartempdir - clear the /var/vxvm/tempdb
vxconfigd log file /var/vxvm/vxconfigd.log
Backup & Restore
Backup /usr/lib/vxvm/bin/vxconfigbackup -l /var/vxvm/backups
-l = location where to store backup
Restore (precommit/commit) vxconfigrestore -p
# either one of the below after the precommit
vxconfigrestore -d
vxconfigrestore -c
Note:
-p = when you want to check that the restore is correct (use vxprint to check)
-d = abort the precommit
-c = commit the precommit
Disks
Initialize disk vxdisksetup -i c2t0d0 privlen=768
vxdisksetup -i format=sliced - initialized a disk as a sliced disk
Note: format can be either sliced, simple, cdsdisk or none (see above - Disk Regions)
Uninitialize disk vxdiskunsetup -C c2t0d0
Disk Information vxdisk -g list
vxdisk -s list
Resize a LUN vxdisk -g resize length=8G
Add a disk slice to volboot vxdctl add disk type=simple
Add a disk slice vxdisk –f type=simple
Add a disk vxdiskadd c1t0d0 or c1 (all disk on controller)
vxdisksetup -i
Remove a disk totally from VM vxdisk rm
Remove a disk from a volume vxdg -g rmdisk
Remove a disk slice from VM vxdctl rm disk
Clear any host ID flags vxdisk clearimport
Renaming a disk vxedit -g rename
Move disk to different disk group vxdg move
Offline a disk vxdisk offline
Note: disk must not be in a disk group
Online a disk vxdisk online
Note: disk must have a private region otherwise you need to initialize the disk
Hot spare vxedit –g set spare=on
NoHotUse vxedit –g set nohotuse=on
Turn off failing flag vxedit -g set failing=off
Encapsulate a disk vxdisk define c0t0d0s0 type=nopriv
Reattach disk (SAN) vxreattach [-br | -c]
-b = Background process
-r = Recover volumes
-c = Checks to see if reattach is possible
Discover new disks vxdisk scandisks [new | fabric ]
Disk Comment vxedit -g set comment="......."

Disk Group
Create a disk group vxdg init group =
vxdg init = cds=off - initialize a non-cds disk group
Remove a group vxdg destroy
Add a disk to a group vxdg –g adddisk =
Remove a disk from a group vxdg –g rmdisk
Replace failed disk vxdg -k -g adddisk =
-k = forces vxvm to take media name of the failed disk & assign it to the new disk
Import a group vxdg import
vxdg -n import
vxdg -C import
Import group (clear any flags) vxdg import -C
-C - clears any exist host flags
Depot a group vxdg deport
vxdg -n deport
List no hot use on disk vxdg –g nohotuse
List spare space on disk vxdg –g spare
Display free space vxdg –g free
Backup disk group (vxvm 4.0) vxconfigbackup
Restore disk group (vxvm 4.0) vxconfigrestore [-p|-d|-c]
Diskgroup Version vxdg list | grep -i version
Upgrade disk version vxdg upgrade - upgrade to current version
vxdg -T 50 upgrade - upgrade to version 50
vxdg -T 50 init = - create new group @ version 50
Boot/Default DG vxdg bootdg
vxdg defaultdg

vxdctl defaultdg - set defaultdg

Volume
Adding mirror to root /etc/vx/bin/vxrootmir create rootvol, swap vol,
Create a simple volume vxassist make
vxassist -g make !ctrl:c2 - don't use controller 2
vxassist make layout=[stripe-mirror|concat-mirror|mirror-concat|mirror-stripe]
stripe-mirror = layered volume
concat-mirror = layered volume
mirror-concat = non-layered volume
mirror-stripe = non-layered volume
Mirror a simple volume vxassist mirror >disk>
vxassist -g remove mirror !disk01 - remove the disk01 mirror
Create a stripped volume vxassist make layout=stripe
vxassist -g -o ordered make layout=stripe ncol=3
Create mirrored volume with log vxassist make layout=mirror, log nmirror=# nlog=#
Create a raid volume vxassist make layout=raid5
Remove a volume vxedit –rf rm
vxassist -g remove volume
Note: you must disable the volume first
Initializing a volume vxvol init state [plex]state=clean,enable,active
Online Relayout vxassist -g relayout layout=stripe ncol=2
vxassist -g relayout layout=stripe ncol=+1
vxassist -g relayout layout=stripe ncol=-1
vxassist -g relayout layout=stripe stripe=32k ncol=5
vxassist -g relayout layout=raid5 stripeunit=32k ncol3
vxassist -g convert layout=stripe-mirror
# Display the relayout operation
vxrelayout -g [status|reverse|start]
vxtask list
Starting a volume vxvol start
Start a disabled volume vxrecover –sb
-s = start volume after recovery
-b = background the recovery task
Disable a volume vxvol stop
Evacuate a volume vxevac -g

Maintenance mode vxvol maint
Not clean vxmend mirror clean
No kernel state vxplex att
Extending a volume size vxresize
vxresize -g +100m - increase the volume by 100Mb
Shrinking a volume size vxresize
vxresize -g -100m - decrease the volume by 100Mb
add a DRL log to a volume vxassist addlog
remove a DRL log from a volume vxassist remove log
Extending log size vxvol set loglen = 2m
Detering volume size vxassit -g maxsize layout=mirror - the maximum size you can create a mirror
vxassist -g maxgrow - the maximum size the volume can grow too
Recover a volume Vxmend fix clean
Change volumes permissions vxedit -g set owner= group= mode=

Plexs
Creating a plex vxmake plex sd =_{Remove a plex vxplex –o rm dis
vxplex -g dis
vxedit -g -rf rm
Moving a plex vxplex mv
Copying a plex vxplex cp
Attaching a plex vxplex att
Detaching a plex vxplex det
Offlining a plex vxmend off vol01-02

Sub-disks
Creating sub-disk vxmake sd , offset, len
Removing sub-disk vxedit rm
Moving sub-disk vxsd mv
Associating with a plex vxmake plex sd=, …
i.e vxmake plex home-1 sd= disk02-01, disk02-00, disk02-02
Dissociating vxsd dis
Splitting vxsd –s split sd
Joining vxsd join
relocating a sub disk vxassist -g move !disk05 disk02
relocating a whole disk sub disks vxprint -g rootdg -se 'sd_orig_dmname="disk02"'
vxunreloc -g rootdg disk02

Volume Manager Information
Disks
Display all the physical disks vxdisk list
vxdisk -o alldgs list
Display detailed disk info vxdisk list
Check for disk failures vxstat –g –ff –d
Disk Group
Display group properties vxdg list
Display detailed group info vxdg list
vxinfo -p -g
Volume
Display volume info vxprint –Aht
Display volume properties vxprint –vl
Display unstartable volume vxinfo -g
Check for volume failures vxstat –g –ff -v
Plex
Display plex properties vxprint –vp
Check for plex failures vxstat –g –ff -p
Sub-Disks
Display sub-disk properties vxprint –st
Veritas Tasks
Display tasks vxtask list
vxtask monitor - continuously monitor
States:
r = running
p = pause
a = aborting
Statistics and Tracing
Iostats vxstat -g -r –d - reset all stats on disk
vxstat -g -d - display stats
vxstat -g -i 1 -d - display stats every 1 sec intervals for volume
vxstat -g -i 10 -c 5 -d - display 5 sets @ 10 secs intervals
Tracing vxtrace -d -o dev,disk
vxtrace -f -o dev,disk | more
Licensing
Add vxlicinst - versions greater than 3.5
vxlicense -c - versions below 3.5
View vxlicrep - versions greater than 3.5
vxlicense -p - versions below 3.5
Paths /etc/vx/licenses/lic - versions greater than 3.5
/etc/vx/elm - versions below 3.5
Reload new license vxdctl license init
VEA
Start/Stop /etc/init.d/isisd [start|stop|restart]
Status vxsvcctrl status
vxsvc [-m|-k|-v]
-m = status
-k = kill
-v = version
Daemons /opt/VRTSob/bin/vxsvc
/opt/VRTSob/bin/vxsvcctrl
Start VEA GUI /opt/VRTSob/bin/vea
You must have X-windows running
Logging
Logging help in recovery and can speed it up dramatically, the main form of logging in veritas is the DRL (dirty region log) which performs the following
• log keeps track of changed regions
• if system fails only the changed regions of the volume are recovered
Add vxassist -g addlog logtype=drl
vxassist -g addlog - used for raid logs (no type)
Remove vxassist -g remove log [nlog=n]
Volume Read Policy
Policies can be used if you have slower disks within a volume and you wish to use the faster disks.
Round Robin vxvol -g rdpol round
Preffered Plex vxvol -g rdpol prefer
Selected Plex vxvol -g rdpol select
Storage Expert (vxse)
Veritas have created some scripots that can check the integrity of the vxvm setup i.e mirrored volumes, spares, etc. The scripts are based on rules and there are a number of differents rules veritas has set, look in the rules directory to see all of them.
Display Description vxse_raid5log1 info
Check rules vxse_raid5log1 -g check
List spare rules vxse_spares list
Run spare run vxse_spares run
Note: you need to run "/etc/init.d/isisd start" to start the necessary daemons first
VXSE Paths
Rules /opt/VRTS/vxse/vxvm
Default Parameters /etc/default/vxse
VxDMP
see VxDMP for more information
Veritas links
Recovery features http://prefetch.net/articles/veritasrecoveryfeatures.html}

VxVm commands quick reference guide

2009-04-15T06:28:00.000-07:00

Veritas volume manager certification questions

2009-04-15T06:25:00.000-07:00

1. A Volume Manager disk can be divided into one or more ________.
• a. disk groups
• b. partitions
• c. slices
• d. subdisks
2. What does an active/passive array provide?
• a. load balancing using minimum I/O policy
• b. high availability in the event of a total array failure
• c. load balancing using the round robin I/O policy
• d. high availability in the event of a path failure
3. Which configuration step must be completed prior to assigning a new disk to a disk group?
• a. initialize the disk
• b. create subdisks
• c. assign disk space to volumes
• d. configure the volume disk pool
4. Which vxdisk command options display disk information and the disk group status?
• a. -o dg list
• b. -o alldgs list
• c. -o list alldgs
• d. -o list dg
5. If the datadg disk group has a disk group version of 50, what occurs when you run the vxdg upgrade datadg command with no other options?
1. a. The disk group is upgraded by one disk group version level, in this case, to version 60
2. b. You receive an error stating that the disk group version must be specified
3. c. The disk group is upgraded to the latest disk group version
4. d. The current disk group version is displayed and no further action is taken
6. Output from the vxprint command displays information stored in the _______.
• a. private region
• b. public region
• c. partition table
• d. dirty region log
7. Which command removes the datavol volume from the datadg disk group?
• a. vxassist -g datadg remove volume datavol
• b. vxremove -g datadg remove volume datavol
• c. vxassist -g datadg destroy volume datavol
• d. vxdg -g datadg destroy volume datavol
8. Which statement is true about the relationship between a Volume Manager volume and the corresponding file system?
• a. Starting the volume will start the file system
• b. The file system must be mounted to stop the volume
• c. The file system must be unmounted to stop the volume
• d. Starting the file system will start the volume
9. Which command forces the daemon to reread all the drives in the system?
• a. kill ?HUP vxiod
• b. vxdisk rescan
• c. vxdctl enable
• d. vxprint -voldstart
10. Which command can be used to remove a disk interactively?
• a. vxdiskadm option “remove a disk”
• b. vxdisk remove -f -i
• c. vxdisk relocate -f -i
• d. vxdiskadm option “relocate subdisks”
11. The datadg disk group contains four disks. A 100 MB volume named datavol is concatenated using two disks. There are no other volumes in the disk group. There are three processes performing random reads that are 512K in size on the volume. Output from a vxstat command indicates that all I/O activity occurred mostly on one of the two disks.

Which action will most evenly distribute the I/O across all disks in the disk group?
• a. Mirror the volume using the two unused disks
• b. Remove the two unused disks from the disk group
• c. Resize the volume to use all of the disks
• d. Stripe the volume across all four disks
12. Which layout options are available when using the vxassist command to create a layered volume? (Choose two)
• a. concat-mirror
• b. mirror-concatenate
• c. stripe-mirror
• d. mirror-stripe
• e. concatenate-stripe
• f. stripe-concatenate
13. Which menu option within the vxdiskadm utility can be used to create a new disk group?
• a. Add or initialize one or more disks
• b. Add or initialize one or more disk groups
• c. Make a disk available for hot-relocation use
• d. Enable access to (import) a disk group
14. What are the benefits of enclosure-based naming? (Choose three)
• a. easier fault isolation
• b. improved array availability
• c. device-name independence
• d. improved SAN management
• e. improved disk performance
15. Which command creates a 10 GB volume named datavol in the datadg disk group, assuming that the /etc/default/vxassist file does NOT exist on the system?
• a. vxvmvol -g datadg new 10g datavol
• b. vxvol -g datadg create 10g datavol
• c. vxassist -g datadg make datavol 10g
• d. vxdisk -g datadg 10g newvol datavol
16. Online resizing of a Volume Manager volume and file system requires that the file system is _____.
• a. in the bootdg disk group
• b. checked before the process
• c. shared across disk groups
• d. mounted during the process
17.Which command displays the contents of the volboot file?
• a. vxvolboot list
• b. vxcat volboot
• c. vxdctl list
• d. vxconfig volboot
18. What are the characteristics of a space-optimized snapshot? (Choose two)
• a. contains compressed primary data
• b. references the primary data
• c. requires less space than a full-sized point-in-time copy
• d. initially contains a complete copy of primary data
• e. performs an automatic atomic-copy resynchronization
19. Which Veritas Volume Manager command displays average volume read and write times?
• a. vxprint
• b. vxstat
• c. vxtrace
• d. vxinfo
20. What is the recommended next step to be performed after a failed disk has been physically replaced?
• a. Logically replace the disk in volume Manager
• b. Unrelocate any relocated Volume Manager subdisks to the new disk
• c. Synchronize any STALE plexes
• d. Ensure that the operating system can access the disk
21. Which commands can be used to manage dynamic multipathing? (Choose two)
• a. vxddladm
• b. vxdiskadm
• c. vxdmpadm
• d. vxpathadm
• e. vxassist
22. Which task related to protecting the Volume Manager configuration has the steps “precommit” and “commit” associated with it?
• a. restore
• b. backup
• c. replace
• d. remove
Answers: 1-d, 2-d,3-a, 4-b, 5-c, 6-a, 7-a, 8-c, 9-c,10-a,11-d, 12-a&c, 13-a, 14-a&c&d, 15-c, 16-d, 17-c, 18-b&c, 19-b, 20-d, 21-b&c, 22-a

Disk Group Version New Features Supported Previous Version Features Supported
90 • Cluster Support for Oracle Resilvering
• Disk Group Move, Split and Join
• Device Discovery Layer (DDL)
• Layered Volume Support in Clusters
• Ordered Allocation
• OS Independent Naming Support
• Persistent FastResync 20, 30, 40, 50, 60, 70, 80
80 • VERITAS Volume Replicator (VVR) Enhancements 20, 30, 40, 50, 60, 70
70 • Non-Persistent FastResync
• VERITAS Volume Replicator (VVR) Enhancements
• Unrelocate 20, 30, 40, 50, 60
60 • Online Relayout
• Safe RAID-5 Subdisk Moves 20, 30, 40
50 • SRVM (now known as VERITAS Volume Replicator or VVR) 20, 30, 40
40 • Hot-Relocation 20, 30
30 • VxSmartSync Recovery Accelerator 20
20 • Dirty Region Logging
• Disk Group Configuration Copy Limiting,
• Mirrored Volumes Logging
• New-Style Stripes
• RAID-5 Volumes
• Recovery Checkpointing

To list the version of a disk group, use this command:

Veritas Volume Manager Command Line Examples

Tags:
• Veritas VM

Volume Manager CLI examples:
---------------------------

display disk listings:

# vxdisk list

display volume manager object listings

# vxprint -ht

display free space in a disk group

# vxdg -g free

list all volume manager tasks currently running on the system

# vxtask list

add a disk to Volume Manager (devicename = cXtXdX) (prompt driven)

# vxdiskadd

designate/remove a disk as a hot-relocation spare

# vxedit set spare=on

# vxedit set spare=off

rename a disk

# vxedit rename

reserve/unreserve a disk (space won't be allocated unless specifically mentioned in vxassist)

# vxedit set reserve=on

# vxedit set reserve=off

take a disk offline (first remove the disk from its disk group) (devicename=cXtXdXs2)

#vxdisk offline

remove a disk

(first, stop any applications associated with the volume,
unmount the volume, stop the volume,
if you need the data on the disk, move the volumes to another disk or back up volume)

--removing the disk from its disk group:

# vxdg -g rmdisk

--remove the disk from volume manager control (devicename=cXtXdXs2)

# vxdisk rm

display multipath information

# vxdisk list

create a disk group

(see 'add a disk to volume manager - if the group does not exist, you will be prompted)

upgrade a disk group

--list disk group version

# vxdg list

--upgrade disk group to highest version currently running

# vxdg upgrade

destroy a disk group

# vxdg destroy

display disk group information

# vxdg list

# vxdg list

move a disk group

(stop any applications associated with all volumes in the disk group,
unmount and stop all volumes in the disk group:

--deport (disable local access) the disk group to be moved on first system

# vxdg deport

--import (enable local access) the disk group and its disks from the second system

# vxdg import

--start all volumes in the disk group on the second system

# vxrecover -g -sb

or # vxvol -g startall

estimating maximum volume size (any_valid_type = raid5, stripe, mirror)

# vxassist -g maxsize layout=

create a concatenated volume (length examples = 15g, 15m)

# vxassist -g make

create a striped volume (length examples = 15g, 15m)

# vxassist -g make layout=stripe \

create a raid5 volume (without logging) (length examples = 15g, 15m)

# vxassist -g make layout=raid5,nolog \

create a raid5 volume (with logging) (length examples = 15g, 15m)

# vxassist -g make layout=raid5,log \

create a mirrored volume (without DRL) (length examples = 15g, 15m)

# vxassist -g make layout=mirror,nolog \

create a mirrored volume (with DRL) (length examples = 15g, 15m)

# vxassist -g make layout=mirror,log \

mirror an existing volume

# vxassist mirror

mirror all volumes within a disk group

# vxmirror -g -a

mirror the root (boot) disk

EEPROM variable "use-nvramrc?" must be set to true

# vxrootmir -v

remove a mirror (use 'vxprint -g -ht' to get plexname)

# vxplex -o rm dis

add a log to an existing volume

# vxassist addlog

remove a log from an existing volume

# vxassist remove log

create a raid 0+1 volume (without DRL)

# vxassist -g make layout=mirror-stripe,nolog \
nmirror=# nstripe=#

create a raid 1+0 volume (without DRL)

# vxassist -g make layout=stripe-mirror,nolog \
nmirror=# nstripe=#

resize a volume

# vxassist -g growto

# vxassist -g growby

# vxassist -g shrinkto

# vxassist -g shrinkby

estimate how much a volume can grow

# vxassist -g maxgrow

remove a volume

(stop all applications associated with the volume,
unmount volume (remove /etc/vfstab entry))

--stop volume

# vxvol stop

-- remove volume (for raid 1+0, use 'rf-rm')

# vxedit -r rm

or # vxassist remove volume

change the volume read policy

# vxvol rdpol

# vxvol rdpol prefer

change volume attributes

# vxedit set =

resize a filesystem (ufs cannot be shrunk, only grown)

# vxresize -g +
# vxresize -g -

join subdisks (must be in the order of offset on disks)

# vxsd join

»
create a striped volume (length examples = 15g, 15m)
Submitted by Anonymous (not verified) on Wed, 07/16/2008 - 04:41.
The syntax is incorrect for:
create a striped volume (length examples = 15g, 15m)
# vxassist -g make layout=stripe \

It should be something like this:
# vxassist -g testdg make testdgvol1 285503488 layout=stripe alloc=disk1,disk2,disk3,disk4
This brings the credibility of the rest of this document into question; You have not specified which version of Veritas this applied to ;P
# vxdg list dgname
To upgrade a disk group to the highest version supported by the release of VxVM that is currently running, use this command:

# vxdg upgrade dgname
By default, VxVM creates a disk group of the highest version supported by the release. For example, VERITAS Volume Manager 3.2 creates disk groups with version 90.
It may sometimes be necessary to create a disk group for an older version. The default disk group version for a disk group created on a system running VERITAS Volume Manager 3.2 would be 90. Such a disk group would not be importable on a system running VERITAS Volume Manager 2.3, which only supports up to version 40. Therefore, to create a disk group on a system running VERITAS Volume Manager 3.0 that can be imported by a system running VERITAS Volume Manager 2.3, the disk group must be created with a version of 40 or less.
To create a disk group with a previous version, specify the -T version option to the vxdg init command. For example, to create a disk group with version 40 that can be imported by a system running VxVM 2.3, use the following command:

# vxdg -T 40 init newdg newdg01=c0t3d0

This creates a disk group, newdg, which can be imported by VERITAS Volume Manager 2.3. Note that while this disk group can be imported on the VxVM 2.3 system, attempts to use features from VERITAS Volume Manager 3.0 and later releases will fail.

solaris troubleshooting

2009-04-15T02:41:00.000-07:00

(7.0) TROUBLESHOOTING
(7.1) What can I do if Solaris won't boot?
You need to boot from your install CD. Insert the Solaris Software CD in your CDROM drive. If your CDROM drive/BIOS isn't bootable, first insert the "Device Configuration Assistant" (DCA) diskette. At the "Boot Solaris" menu, choose "CD."
At the "Type of Installation: Interactive or JumpStart" menu, type "b -s"
Or, after the video configuration, network, time and date you'll notice one of the menu's has a button: [Exit] Select Exit and, when it asks you again "do you want to exit?," just say yes.
Once you're at the UNIX root prompt #, you can mount the boot drive with "mount /dev/dsk/c0t0d0s0 /mnt"" and view anything wrong with the boot drive (omit the "t0" for ATAPI).
[Modified from Bob Palowoda's Solaris 2.4 x86 FAQ]

(7.2) How do I restore the Solaris boot block without reinstalling?
This may happen when installing a boot manager that comes with another operating system (such as LILO from Linux) or an after-market multi-OS boot manager. These sometimes trample's active partition, which in our case is Solaris. Also, moving the Solaris partition with a partition manager program such as Partition Magic requires reinstalling the Solaris boot block. Before taking these steps, first verify the Solaris partition is active. If it isn't, just make the Solaris partition active and reboot. Otherwise follow the steps below.
1. Boot from CD-ROM and get the root prompt, #, as described in the previous question, 7.1.
2. Determine the controller, disk number, and partition. The boot disk is /dev/rdsk/c?t?d?p? where ? is the controller #, target ID, and disk #, and partition #. Omit "t?" for ATAPI E.g., /dev/rdsk/c0d0p0
3. Verify it's the correct device correct with prtvtoc for the drive: This is VERY important; if it's wrong, you you may hose another partition: prtvtoc /dev/rdsk/c0t0d0p0 (omit "t0" for ATAPI, always use p0, which means the "entire drive"). The prtvtoc prints out the map for the Solaris partition on the hard drive, if found. The partitions shown on the output are actually "slices" within the Solaris partition.
4. Restore the boot block as follows:
/sbin/fdisk -b /usr/lib/fs/ufs/mboot (raw disk dev)
E.g., for SCSI it might be:
/sbin/fdisk -b /usr/lib/fs/ufs/mboot /dev/rdsk/c0t0d0p0
(omit "t0" for ATAPI)
5. Finally, remove your CDROM and diskette media and type "/sbin/shutdown -i6" to reboot. The Solaris Multiple Device Boot Menu should appear after rebooting. If not, you can always to an upgrade (re-)install.
Note: This procedure does NOT make your Solaris partition active again (sometimes needed after installing another operating system, such as Windows, on the same disk), it just writes to your bootblock IN your Solaris partition. To learn more about the Solaris boot process, read the boot(1M) man page.

(7.3) What can I do during the Solaris/x86 booting sequence?
Starting with Solaris 10 06/06, Solaris now uses GRUB to boot, making the answer below obsolete. That means you can boot to multiple partitions, with multiple instances of Solaris and other operating systems (such as Linux and Windows)
Step #1: Boot loader
If you have multiple partitions, the boot loader in the Solaris partition will come up and ask you which partition you want to boot. This partition must be the active partition, or at least be marked active by a third-party boot manager before this boot loader receives control (not all boot managers have this feature). If you don't answer in so many seconds, it boots Solaris.
This boot manager is pretty basic. It has no customization. You can't change the default boot partition to one other than Solaris, you can't change the timeout value, and you can't change the partition descriptions. But it gets the job done.
Step #2: Device Configuration Assistant (DCA)
This will ask you to press ESC if you want to change stuff. This is to make up for the fact that x86 machines don't have a nice OpenBOOT chip to sort out REAL "Plug and Play".
Basically, in Solaris x86, the Device Assistant seems to set up certain things in /boot/solaris. This is so the "real" OS has some common format to examine for devices, instead of having lots of nasty x86 hardware specific stuff. That way, Sun can keep the main OS somewhat hardware independent, and keep it very close to the Sparc version.
The "Assistant" can actually been of assistance. If you select "partial scan", then "Device tasks", and then "View/Edit Devices", it will tell you what Solaris THINKS your devices are, and where they are at. Quite useful, when Solaris gets completely lost, and you're wondering if it's your fault, or what.
Otherwise, it can give you a warm fuzzy feeling, if you select "Full Scan", and you see all your devices properly recognized.
Step #3: OS Boot
Well, actually, the "Boot Assistant". The interface is similar, but not identical, to SPARC Solaris' OpenBoot 'boot' command. The main differences I notice are:
• It's "b -r", not "boot -r", if you want to force reconfiguration. Why would you want to do that? Well sometimes, if your devices have changed a LITTLE, you might want to do this. You can also invoke it with a "touch /reconfigure" as root before rebooting with "/sbin/shutdown -i6".
• You don't have nice device aliases like you do with Sparc hardware. That being said, if you do nothing, it should autoboot into the actual OS in a few seconds. Or you can type something quickly within 5 seconds, and force a "reconfiguration boot", as mentioned earlier.
• The "Driver Assistant" or whatever, really looks for major changes, like adding or removing a card. However, if, say, you add another disk drive, you'll probably want to just do "b -r". Note that the Device Assistant will itself trigger a "b -r", after it has autodetected hardware changes.
Step #4: The Main OS: Solaris
You made it (I hope)!. Hopefully, you should now see a line with "SunOS5.8" or similar in it, and a little twirly text character spinner starting. You are now really in the classic Solaris environment. From here on in, your experience is almost identical to your brethren who work with SPARC Sun equipment.
To learn more about the the Solaris boot process, read the boot(1M) man page.
[Thanks to Phil at http://www.bolthole.com/solaris/]

(7.4) How do I logon as root if the password doesn't work anymore?
Regaining control of a Solaris x86 system where the root password has been lost can be accomplished by the following steps. Note that any savvy user can do this with the proper CD-ROM and diskette. Therefore, of course, physical security of a system is important for machines containing sensitive data.
1. Insert installation boot diskette and installation CD-ROM for Solaris x86.
2. Boot system from the installation floppy and select the CD-ROM as the boot device.
3. Type "b -s" (instead of typing 1 or 2 from the menu) and it'll drop you straight to a root shell, #, (and you'll be in single-user mode).
4. At the root prompt, #, key in the following commands, which will create a directory called hdrive under the /tmp directory and then mount the root hard drive partition under this temporary directory.
5. mkdir /tmp/hdrive
6. mount /dev/dsk/c0t0d0s0 /tmp/hdrive #SCSI; for ATAPI, omit "t0"
7. To use the vi editor, the TERM variable must be defined. Key in the following commands.
8. TERM=at386
9. export TERM
10. Start vi (or some other editor) and load /tmp/hdrive/etc/shadow file:
11. vi /tmp/hdrive/etc/shadow
12. Change the first line of the shadow file that has the root entry to:
13. root::6445::::::
14. Write and quit the vi editor with the "!" override command:
15. :wq!
16. Remove the floppy installation diskette, and reboot the system:
17. /sbin/shutdown -i6
18. When system has rebooted from the hard drive, you can now log in from the Console Login: as root with no password. Just hit enter for the password.
19. After logging in as root, use the passwd command to change the root password and secure the system.
Andreas Pfaffeneder has a simpler suggested to recover the password:
Choose the Failsafe-Boot option (which results in kernel/unix -s), answer "Yes" when you are prompted if / of the installed system should be mounted. Chroot into the system and change the password:
# chroot /a /bin/bash
# passwd
# /sbin/shutdown -i6
[Thanks to Lynn R. Francis of Texas State Technical College and Andreas Pfaffeneder]

(7.5) My licensed software fails because the host ID is 0. What's wrong?
Intel processor machines don't have an IDPROM, so Sun generates a serial number, hostid command or sysinfo()'s SI_HW_SERIAL, pseudo-randomly during installation. The number is stored in /kernel/misc/sysinit, whose only function, it appears, is to provide the serial number. If serialization information is tampered or sysinit fails to load, the host ID will be 0. If you reinstall Solaris, sysinit will be regenerated and your host ID will change. So be careful about reinstalling Solaris if you have licensed software that depends on your host ID. Backup your sysinit file.
To preserve the same ID (and therefore licenses), copy file /kernel/misc/sysinit to the replacement system. I understand the Sun Workshop/Sun ONE compiler manual says this is allowed twice per calendar year (please verify this yourself).
For more information, see the Sun NVRAM/hostid FAQ, available at http://www.squirrel.com/squirrel/sun-nvram-hostid.faq.html and elsewhere. This also has tools to fake hostids.

(7.6) How can I fix Netscape Communicator to render fonts correctly on S/x86?
This problem occurs with Solaris 2.6 and Netscape Communicator 4.0x, and has since been fixed. Apply patch 106248, which I'm told fixes this problem. A workaround is to add the following two lines to your ~/.xinitrc file:
xset +fp /usr/openwin/lib/X11/fonts/75dpi/
xset fp rehash
Another workaround, if you don't have these fonts, is to go into Netscape Preferences and change the font faces.
[Thank's to Alan Orndorff, Jeffrey Cook, and John Riddoch]

(7.7) Why doesn't Netscape run as root?
This is a bug in Netscape. Due to a Netscape 4.x bug (it thrashes the $HOME environment variable) the X11 library cannot find root's .Xauthority file in the root dir unless your current directory is /.
Large, complex programs (especially those taking input from & to the Internet) should not be run as root. Experienced users and Administrators run as root only for essential sysadmin tasks.
If you must run as root, try one of these tricks:
• Make sure you run Netscape with a current directory of / (so that the relative pathname '.Xauthority' works)
• Or start Netscape with HOME="/." (so that Netscape doesn't thrash the $HOME variable)
• Or start Netscape with an environment variable XAUTHORITY="/.Xauthority"
[Thanks to Jürgen Keil via John Groenveld]

(7.8) I moved my PCI host adapter to another slot and the system won't boot!
Don't move the adapter. It isn't a supported feature in Solaris and isn't easy to recover from. If you have any choice in the matter, move the controller back to it original slot.
The PCI device number is part of the device's basic ID, including its child disks. If you change slots, you've effectively removed that controller and its disks, and added an unrelated controller and disks. You need to fix up all of the references to the old disks to point to the new disks.
I've never come up with any strategy better than "boot, observe failure, fix failure, reboot" for recovering from this kind of change. For simple cases (single controller, in particular) it can be helpful to clear /dev/dsk/* and /dev/rdsk/* and run "disks", but that is perilous too.
Incidentally, changing motherboards is likely to trip exactly this problem, because motherboards generally number their slots differently.
To conclude, it's difficult and dangerous, and the general guidelines involves fixing:
1. /etc/vfstab or /dev or both
2. /devices to match one another
3. possibly removing lines from /etc/path_to_inst in order to make the right /devices nodes show up
The ultimate goal is to get back the same controller numbers as before.
[Sun FAQ 2576-02 at http://access1.Sun.COM/cgi-bin/rinfo2html?257602.faq]

(7.9) Why is Solaris always booting into the Device Configuration Assistant (DCA)?
This is usually caused by one of the following:
• You installed Solaris onto a disk other than the primary boot disk.
• You didn't remove your DCA boot diskette or if you didn't remove your installation CD-ROM if it's in a bootable CD-ROM drive.
• File /boot/solaris/bootenv.rc is corrupt or truncated, usually after a hard reboot or reset. This file is setup and used by DCA. It should contain several lines.
To change or set your default boot device, See Sun FAQ 2271-02 at http://access1.Sun.COM/cgi-bin/rinfo2html?227102.faq for instructions. To summarize:
• From the "Boot Solaris" screen, press F4 (Boot Tasks).
• On the "Boot Tasks" screen, press Enter to place an "X" in front of "View/Edit Autoboot Settings."
• In the "View/Edit Autoboot Settings" screen, note that the Default Boot Device will not be set to any valid device. Place an "X" in front of Set Default Boot Device and press F2 (Continue).
• On the Set Default Boot Device screen, place an X in front of the correct disk and press F2 (Continue).
• Arrow up to the Accept Settings and press Enter to mark with an "X". Press F2 (Continue) to return to the Boot Tasks screen.
• Press F3 (Back). It will load appropriate drivers after which you will be at the Boot Solaris screen. Press F2 (Continue) to continue booting.

(7.10) What is the equivalent of STOP-A for Solaris x86?
>I don't think so, because Stop-A allow you to go into open boot prom of >the SUN and on a x86 it's a different thing (BIOS) Unlike Solaris on Sparc (where STOP-A gets you the OpenBoot prompt), there is no PROM firmware to drop into on x86. You can boot your system under kadb and then use a similar keystroke to drop into kadb and obtain debugging information. To boot under kadb, type eeprom boot-file=kadb and then:
• Prior to Solaris 8, type CTRL-ALT-d to jump into kadb
• On Solaris 8 or later, type F1-a to jump into kadb
• At the Solaris x86 Boot Assistant prompt type "b kadb"
You can then type, for example:
$to force your system to panic and generate a crash dump (the equivalent of "sync" at the ok prompt on SPARC).
The Device Configuration Assistant (DCA) portion of the Intel boot process can be interrupted by hitting escape when prompted. This I feel is the Intel version of the Boot Prom Monitor. Of course, all the commands cannot be equated apples to apples because of the hardware differences!
If your console is a terminal, you can type "shift-break" or "ctrl-break" or "ctrl-\" (ctrl-backslash) or "" followed by "~" and "ctrl-break" on Solaris Sparc, but this, too, is not available for Solaris x86.
With Solaris 8 SPARC (but not Intel), there's a new feature to allow keyboard sequences to generate a break (bug 4147705). The 3-character sequence is , ~ (tilde), ^b. Each character must be entered between 0.5 to 2 seconds. This is enabled with the "kbd -a alternate" command.
Similarly a soft reset is , ~ (tilde), cntl-shift-R, XIR is , ~ (tilde), cntl-shift-X, and Power Cycle is , ~ (tilde), cntl-shift-P, I believe these commands are also available only on SPARC.
[Thanks to Ramit Luthra and Mike Shapiro]

(7.11) How can I reboot Solaris x86 without it asking me to to "press a key" before rebooting?
This works for me: become root and type "shutdown -i6 -g0 -y". Or: "/sbin/shutdown -i6 This is most useful when the system is remote with no console keyboard access. don't use reboot, halt, or poweroff as they bypass the shutdown scripts.
[Thanks to Charles J. Fisher]

(7.12) Help! I'm stuck in the "Boot Assistant" and can't boot. What do I do?
If you get a message similar to: Run Error: File not found. could not run s You probably typed "reboot -- -s" or "reboot -- -r" or similar. This works for Solaris SPARC, but not for Solaris on Intel--it's disastrous. It changes your "boot-file" eeprom variable to "-s", which errors out and puts you in an endless loop in B oot Assistant.
To undo this, type the following at the Boot Assistant prompt: "b kernel/unix" This boots with file /platform/i86/kernel/unix. If this doesn't help, your filesystem may be hosed. In that case, you have to reinstall. But make sure this is the case first.

(7.13) Help! I get error 2 or error 8 while applying patches. What do I do?
Don't do anything. Error 2 means you already have the same or newer code. Error 8 means you can't patch some optional packages that haven't been installed, even if you did "everything plus OEM" during the original installation. Other errors, usually from lack of disk space, are explained in the patchadd(1M) man page.
[Thanks to Paul Karagianis]

(7.14) How do I prevent kdmconfig from running on boot up when I know my keyboard, display, and mouse configuration has not changed?
Mike of Sun has this response (9/2002):
I recognized this as a bug that was fixed a while back, for one instance with older ATI cards. I mentioned it to the video developer that fixed the ATI bug and he mentioned that there is a workaround if you see this:
This problem occurs with certain hardware (keyboards, mice, video devices). During booting, a checksum is calculated based on some info obtained for each device. The checksum is compared to a checksum recorded in the OWconfig file. If the checksums don't match, kdmconfig thinks the device may have changed, and asks the user to check it.
On systems that exhibit this problem, the device info that is checksummed seems to change from boot to boot even though no hardware has changed. I've seen this happen with some old ATI video cards and some keyboards.
The easy workaround for the problem is to run kdmconfig and test and accept the desired configuration by clicking on the "Yes" button of the test display. Then edit the last line of the OWconfig file in /etc/openwin/server/etc. Change the "1" to "2", so that is says: TestedByUser="2"; This will cause kdmconfig to ignore checksum differences.
If you are upgrading from Solaris 8 or older to Solaris 9, check the ddxHandler line. It should say "ddxSUNWx86mouse.so.1", not "ddxSUNWmouse.so.1". Otherwise, X Windows won't start (no graphics).
[Thanks to Mike Riley]

(7.15) I get this error message: "can't get local host's domain name" or "The local host's domain name hasn't been set." What do I do?
This is a NIS message. The easiest way to fix it is to type the following as root:
domainname abc.com; domainname >/etc/defaultdomain
(replace abc.com with your NIS domain name, which is usually the same as the DNS domain name).

(7.16) My system doesn't boot due to superblock problems with the root filesystem. What do I do?
Normally, you reboot in single user mode and run /usr/bin/fsck as root and everything is OK. If you get a message about errors/problems on /dev/dsk/c0d0s0, are told to run fsck manually in single user mode, and get this message:
BAD SUPER BLOCK: BAD VALUES IN SUPERBLOCK USE AN ALTERNATIVE SUPERBLOCK to SUPPLY NEEDED INFORMATION e.g. fsck -F ufs -b=# [special].
then you may be able to recover from this if the disk isn't entirely corrupted. The superblock stores important information about the file system. Because it is so important it is duplicated in several places. Hopefully one of the backup superblocks isn't corrupted. To see duplicate locations of superblock, use newfs -Nv. For example, if your root slice is at /dev/dsk/c0d0s0, run this command:
# newfs -Nv /dev/dsk/c0d0s0 You must specify -Nv so you don't clobber your root slice with a new filesystem. Your output should look like this:
# newfs -Nv /dev/dsk/c0d0s0
mkfs -F ufs -o N /dev/rdsk/c0d0s0 614880 63 16 8192 1024 16 10 60 2048 t
0 -1 8
7 n
/dev/rdsk/c0d0s0: 614880 sectors in 610 cylinders of 16 tracks, 63
sectors
300.2MB in 39 cyl groups (16 c/g, 7.88MB/g, 3776 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 16224, 32416, 48608, 64800, 80992, 97184, 113376, 129568, 145760,
468576, 484768, 500960, 516128, 532320, 548512, 564704, 580896, 597088,
613280,
Note the numbers following "super-block backups." Use one of the numbers in fsck (e.g., 32) and use it with the fsck -F -o b= option:
# fsck -F ufs -o b=32
You may get a message FREE BLK COUNT(S) WRONG IN SUPERBLOCK SALVAGE? or FILE SYSTEM STATE IN SUPERBLOCK IS WRONG; FIX? In either case, type "yes" and press return. You should get a FILE SYSTEM WAS MODIFIED message. Reboot your system. If system complains about shutdown not being found do a halt -q. Now, hopefully, your system will boot up with out any problems.
[Thanks to Kevin Smith.]

(7.17) My system doesn't boot because the boot archive is corrupt. What do I do?
The boot archive contains the kernel modules and configuration files that are required to boot your machine. Boot up in Solaris failsafe mode. Your Solaris image should be mounted on /a. Type the following:
rm -f /a/platform/i86pc/boot_archive; bootadm update-archive -R /a

Solaris SPARC Boot Sequence

The following represents a summary of the boot process for a Solaris 2.x system on Sparc hardware.
Power On: Depending on the system involved, you may see some output on a serial terminal immediately after power on. This may take the form of a Hardware Power ON message on a large Enterprise server, or a "'" or "," in the case of an older Ultra system. These indications will not be present on a monitor connected directly to the server.
POST: If the PROM diag-switch? parameter is set to true, output from the POST (Power On Self Test) will be viewable on a serial terminal. The PROM diag-level parameter determines the extent of the POST tests. (See the Hardware Diagnostics page for more information on these settings.) If a serial terminal is not connected, a prtdiag -v will show the results of the POST once the system has booted. If a keyboard is connected, it will beep and the keyboard lights will flash during POST. If the POST fails, an error indication may be displayed following the failure.
Init System: The "Init System" process can be broken down into several discrete parts:
• OBP: If diag-switch? is set, an Entering OBP message will be seen on a serial terminal. The MMU (memory management unit) is enabled.
• NVRAM: If use-nvramrc? is set to true, read the NVRAMRC. This may contain information about boot devices, especially where the boot disk has been encapsulated with VxVM or DiskSuite.
• Probe All: This includes checking for SCSI or other disk drives and devices.
• Install Console: At this point, a directly connected monitor and keyboard will become active, or the serial port will become the system console access. If a keyboard is connected to the system, the lights will flash again during this step.
• Banner: The PROM banner will be displayed. This banner includes a logo, system type, PROM revision level, the ethernet address, and the hostid.
• Create Device Tree: The hardware device tree will be built. This device tree can be explored using PROM monitor commands at the ok> prompt, or by using prtconf once the system has been booted.
Extended Diagnostics: If diag-switch? and diag-level are set, additional diagnostics will appear on the system console.
auto-boot?: If the auto-boot? PROM parameter is set, the boot process will begin. Otherwise, the system will drop to the ok> PROM monitor prompt, or (if sunmon-compat? and security-mode are set) the > security prompt.
The boot process will use the boot-device and boot-file PROM parameters unless diag-switch? is set. In this case, the boot process will use the diag-device and diag-file.
bootblk: The OBP (Open Boot PROM) program loads the bootblk primary boot program from the boot-device (or diag-device, if diag-switch? is set). If the bootblk is not present or needs to be regenerated, it can be installed by running the installboot command after booting from a CDROM or the network. A copy of the bootblk is available at /usr/platform/`arch -k`/lib/fs/ufs/bootblk
ufsboot: The secondary boot program, /platform/`arch -k`/ufsboot is run. This program loads the kernel core image files. If this file is corrupted or missing, a bootblk: can't find the boot program or similar error message will be returned.
kernel: The kernel is loaded and run. For 32-bit Solaris systems, the relevant files are:
• /platform/`arch -k`/kernel/unix
• /kernel/genunix
For 64-bit Solaris systems, the files are:
• /platform/`arch -k`/kernel/sparcV9/unix
• /kernel/genunix
As part of the kernel loading process, the kernel banner is displayed to the screen. This includes the kernel version number (including patch level, if appropriate) and the copyright notice.
The kernel initializes itself and begins loading modules, reading the files with the ufsboot program until it has loaded enough modules to mount the root filesystem itself. At that point, ufsboot is unmapped and the kernel uses its own drivers. If the system complains about not being able to write to the root filesystem, it is stuck in this part of the boot process.
The boot -a command singlesteps through this portion of the boot process. This can be a useful diagnostic procedure if the kernel is not loading properly.
/etc/system: The /etc/system file is read by the kernel, and the system parameters are set.
The following types of customization are available in the /etc/system file:
• moddir: Changes path of kernel modules.
• forceload: Forces loading of a kernel module.
• exclude: Excludes a particular kernel module.
• rootfs: Specify the system type for the root file system. (ufs is the default.)
• rootdev: Specify the physical device path for root.
• set: Set the value of a tuneable system parameter.
If the /etc/system file is edited, it is strongly recommended that a copy of the working file be made to a well-known location. In the event that the new /etc/system file renders the system unbootable, it might be possible to bring the system up with a boot -a command that specifies the old file. If this has not been done, the system may need to be booted from CD or network so that the file can be mounted and edited.
kernel initialized: The kernel creates PID 0 ( sched). The sched process is sometimes called the "swapper."
init: The kernel starts PID 1 (init).
init: The init process reads the /etc/inittab and /etc/default/init and follows the instructions in those files.
Some of the entries in the /etc/inittab are:
• fs: sysinit (usually /etc/rcS)
• is: default init level (usually 3, sometimes 2)
• s#: script associated with a run level (usually /sbin/rc#)
rc scripts: The rc scripts execute the files in the /etc/rc#.d directories. They are run by the /sbin/rc# scripts, each of which corresponds to a run level.
Debugging can often be done on these scripts by adding echo lines to a script to print either a "I got this far" message or to print out the value of a problematic variable.

Sun CD ROM Troubleshooting
Many CD ROM problems are software rather than hardware problems. If your problem is hardware-related, you can look at our Hardware Diagnostics page. Our page on Hard Drive Connectivity may also be useful by analogy.
Some Sun patches resolve security holes in vold by commenting devices out of the /etc/rmmount.conf file. While this is effective, it also disables the devices that are commented out.
For vold to work with your CD ROM and floppy drives within CDE in the designed fashion, you should uncomment the following lines in your /etc/rmmount.conf:

ident hsfs ident_hsfs.so cdrom
ident ufs ident_ufs.so floppy cdrom pcmem
ident pcfs ident_pcfs.so floppy pcmem
action cdrom action_filemgr.so
action floppy action_filemgr.so
Note that this will allow mounted CDs and floppies to be mounted with SUID permissions. For systems where this is inappropriate, your /etc/rmmount.conf file should also contain the following:

mount * ufs -o nosuid
mount * hsfs -o nosuid
(Note that pcfs does not understand SUID, so pcfs does not pose a risk in the same way that hsfs and ufs do.)
The Solaris Volume Manager documentation contains substantial additional information about the operation of vold.

Solaris 2.x Core Dump Analysis
If you are having trouble getting a core dump, see the savecore page.
Several useful pieces of information can be found by running strings on the vmcore.# file and piping it through more or grep: strings vmcore.# | more. In particular, this will tell you the architecture of the system and the OS level. The message buffer is also near the top of the strings output, and may include messages that had not been written to the console or log files yet. (Note that the message buffer is a ring buffer, so the messages may not be in cronological order.)
If the system panic'ed due to a bad trap, adb can determine the instruction that was running at the time of the crash.
crash can also provide useful information, including lock and kernel memory allocation. crash output is notably less cryptic than adb output.
Some netstat, nfsstat and arp commands are also available for crash dumps. After running the command on the corefiles (eg netstat -d unix.# vmcore.#), compare the output to that on the live system, since some of the options do not report the crash dump statistics.
ipcs can also be used with crash dumps in the following format: ipcs -a -C vmcore.# -N unix.# See the IPC page for information on these facilities.

Changing a hostname
The following steps are required to change a Sun system's hostname.
• /etc/hosts.allow (to correct access permissions)
• /etc/dfs/dfstab on this system's NFS servers (to allow proper mount access)
• /etc/vfstab on this system's NFS clients (so they will point at the correct server)
• kerberos configurations
• ethers and hosts NIS maps
• DNS information
• Netgroup information
• cron jobs should be reviewed.
• Other hostname-specific scripts and configuration files.
Additional steps may be required in order to correct issues involving other systems.
Having said all that, the minumum number of changes required are:
• /etc/nodename
• /etc/hosts
• /etc/hostname.*
• /etc/net/*/hosts
Error Message interpretation
See below for a list of common error messages.
Traps and interrupts can be blocked by a kernel thread's signal mask, or they can trigger an exception handling routine. In the absence of such a routine or mask, the process is terminated.
Traps
Traps are syncronous messages generated by the process or its underlying kernel thread. Examples include SIGSEGV, SIGPIPE and SIGSYS. They are delivered to the process that caused the signal.
Trap messages can be discovered in a number of places, including error logs, adb output, and console messages. Sun provides a couple of files that can help determine the type of trap encountered:
• /usr/include/sys/trap.h (software traps)
• /usr/include/v7/sys/machtrap.h (hardware traps, 32 bit)
• /usr/include/v9/sys/machtrap.h (hardware traps, 64 bit)
ECC (Error Checking and Correcting) interrupts are reported as traps when a bit error is corrected. These, while they do not crash the system, are usually a signal that the memory chip in question needs to be replaced.
Critical errors include things like fan/temperature warnings or power loss that require immediate attention and shutdown.
Fatal errors are hardware errors where proper system function cannot be guaranteed. These result in a watchdog reset.
Bus Errors
A bus error is issued to the processor when it references a location that cannot be accessed.
• Illegal address: (usually a software failure)
• Instruction fetch/Data load: (device driver bug)
• DVMA: (on an Sbus system)
• Synchronous/asynchronous data store
• MMU: (Memory Management Unit: can be hardware or software, but frequently are system board problems.)
Interrupts
These notify the CPU of external device conditions that are asynchronous with normal operation. They can be delivered to the responsible process or kernel thread.
In Solaris, interrupts are handled by dedicated interrupt-handling kernel threads, which use mutex locks and semaphores. The kernel will block interrupts in a few exceptional circumstances, such as during the process of acquiring a mutex lock protecting a sleep queue.
• Device done or ready.
• Error detected.
• Power on/off.
Watchdog Reset
Watchdog resets can be caused by hardware or software issues. See the watchdog reset page for information on how to troubleshoot watchdog resets.
Error Message List
A complete (or even reasonably complete) listing of error messages on Solaris is beyond the scope of this site. For that matter, the nature of an evolving operating system may put it beyond the scope of any reasonably sized page. Maybe a wiki? If someone has such a resource, let me know and I will link to it.
Having said that, this page contains a list of several of the most common error messages. Where I have been able to identify a usual cause for an error message, I have included that.
There are several sources that contain listings of error messages that are useful for debugging purposes.
One of the best resources is the Solaris Common Messages and Troubleshooting Guide released by Sun with Solaris 8. Since this is a better resource than I could provide for Solaris up through 8, I have focused on Solaris 10. (There is obviously a lot of overlap.)
The SunSolve web site is available to anyone with a Sun service contract. Its search feature can be used to look up key words in an error message to look for current bug reports and patches that may resolve them. This page does not provide a listing of bug reports or patches to apply for given error messages in certain conditions. This page is intended as a supplement to Sunsolve, not a replacement.
The Intro(2) man page contains an introduction to system calls and error numbers. The information comes from the errno.h include file. Several include files contain at least basic information about different kinds of error messages:
• /usr/include/sys/errno.h (error messages, including abbreviations and numbers seen in truss output.)
• /usr/include/sys/trap.h (software traps)
• /usr/include/v7/sys/machtrap.h (hardware traps, 32 bit)
• /usr/include/v9/sys/machtrap.h (hardware traps, 64 bit)
These messages are alphabetized by the first non-variable portion of the message. Wording may vary slightly between Solaris versions or even patch levels. If you run across common messages not on this list, feel free to make a comment to the Solaris Troubleshooting blog.
• Accessing a corrupted shared library (ELIBBAD): exec(2) was unable to load a required static shared library. The most common cause for this is a corrupted library.
• Address already in use (EADDRINUSE): The protocol does not permit using an address that is already in use. This error indicates a software programming bug.
• Address family not supported by protocol family (EAFNOSUPPORT): The protocol does not support the requested address. This indicates a software programming bug.
• Arg list too long (E2BIG): The argument list includes both the argument list and the environment variable settings. The most common cause for this problem is that so many environment variables are set that it exceeds the size of the argument buffer used by exec(2). The easiest solution may be to unset some environment variables in the calling shell.
• Argument out of domain (EDOM): This error appears when an improper argument is submitted to a math package programming function. (For example, an attempt to take a square root of a negative number would probably yield this error.) It may be helpful to use matherr(3M) to diagnose the problem, or the programmer may need to implement argument-checking before the function is called.
• Arguments too long: This is a C shell message indicating that more than 1706 arguments follow a command. This may happen if globbing is applied to a large number of objects (eg rm * in a directory of more than 1706 objects). Temporarily switching to Bourne shell may resolve the problem, since Bourne shells dynamically allocate space for arguments.
• Assertion failed: This is a result of an assert(3C) debugging command that the programmer inserted into the program. The output will include an expression, a source file number and a code line number. The information may be useful in examining the source code.
• Attachment point not found: Use cfgadm to list available attachment points. Check the physical connection to the desired device.
• Attempting to link in more shared libraries than system limit (ELIBMAX): The executable requires more static libraries than the current system limit.
• authentication receive failed: Initiator unable to receive authentication information. Verify network connectivity to storage device and authentication server.
• authentication transmit failed: Initiator unable to transmit authentication information. Verify network connectivity to storage device and authentication server.
• Bad address (EFAULT): A function taking pointer argument has been passed an invalid address. This may result from supplying the wrong device or option to a command, or it may be the result of a programming bug.
• Bad file number (EBADF): The file descriptor references a file that is either not open or is open for a conflicting purpose. (eg, a read(2) is specified against a file that is open for write(2) or vice-versa.) This is a programming bug.
• Bad module/chip: This error message usually indicates a memory module or chip that is associated with parity errors. This is a hardware fault.
• BAD SUPER BLOCK: Check the Trap 3E entry below to see if there are possible hardware or SCSI configuration causes for this problem. It may be possible to boot from alternate super blocks. If there is no current backup, boot from a CD and back up the raw partition with ufsdump or another similar utility. Solaris 10's 6/06 release includes enhancements to fsck to automatically find and repair bad superblocks. This option should only be used to repair filesystems that were created with mkfs or newfs. For older systems, an alternate superblock can frequently be found with a
newfs -N /dev/rdsk/c#t#d#s#
command while booted from a CD. (Note the -N option. Running this command without this option may mess things up beyond repair.) fsck can be run against an alternate superblock with
fsck -o b=superblock /dev/rdsk/c#t#d#s#
If there is a lot of output, it may be necessary to choose the -y option to avoid having to answer a ton of prompts. We may need to try several alternate superblocks before finding a working one. Once we are done, we need to re-install the bootblock:
cd /usr/platform/`arch -k`/lib/fs/ufs
/usr/sbin/installboot ./bootblk /dev/rdsk/c#t#d#s#
• BAD TRAP: The causes for bad traps include system text errors, data access faults, data alignment errors or some types of user software traps. These can indicate either a hardware fault or a mismatch between the hardware and its software configuration. They may also indicate a CPU with an obsolete firmware. Bad traps usually result in a panic, sync, dump, reboot cycle. The kernel traceback message on the console will frequently indicate the hardware component that generated the bad trap. If the configuration for this component is correct, it will need to be replaced (or at least reseated).
• /bin/sh: ... too big: This Bourne shell message is a variant of Not enough space. Check that message for steps to take.
• Block device required (ENOTBLK): A raw device was specified where a block device is required.
• Broken pipe (EPIPE): No reading process was available to accept a write on the other end of a pipe. This can happen when the reading process (the process after the pipe) exits suddenly.
• Bus Error: I/O was attempted to a device that is unavailable or does not exist. See Bus Error above.
• Cannot access a needed shared library (ELIBACC): Either the library does not exist, the LD_LIBRARY_PATH variable does not include the library, or the user is not permissioned to use it. The library in question can usually be pinned down with truss.
• Cannot assign requested address (EADDRNOTAVAIL): The requested address is not on the current machine.
• Cannot exec a shared library directly (ELIBEXEC): You can't execute shared libraries directly. This error indicates a software bug.
• Cannot install bootblock: On an x86 system, this error typically appears when a newfs and restore operation was carried out without performing a installboot before installing the OS. It may be possible to install the bootblock from the CD drive in single-user mode (note that Sun does not guarantee this procedure):
cd /usr/platform/`arch -k`/lib/fs/ufs

installboot ./pboot ./bootblk /dev/rdsk/c#t#d#s#
• Cannot send after transport endpoint shutdown (ESHUTDOWN): The transport endpoint has been shut down, so data was unable to be sent. The solution is usually to restore the endpoint and re-run the transfer. (We may need to troubleshoot why the remote endpoint became unavailable.)
• can't accept: Initiator does not accept the specified data of the given format. Consult storage device documentation to look for compatibility information for the server hardware and OS.
• can't accept ... in security stage: Device responded with unsupported login information during login security phase. Verify storage device authentication settings. Consult storage device documentation to look for compatibility information for the server hardware and OS.
• can't find environment variable: The specified environment variable has not been set. Check for a typo and/or verify that the variable has been set.
• Can't invoke /etc/init: The init binary is missing or corrupted during a reboot. We may be able to complete the boot by copying init from a CDROM during a CDROM reboot.
• capacity of this LUN is too large: SCSI partitions must be less than 2TB.
• Channel number out of range (ECHRNG): A stream head attempted to open a minor device that is in use or does not exist. We need to make sure that the stream device exists, along with an appropriate number of minor devices, and that it matches the hardware configuration. It may be necessary to schedule jobs differently to allow for limited system resources.
• check boot archive content: If SMF does not start up on its own, this message in response to svcs -x may indicate a failure of svc:/system/boot-archive:default To resolve this problem, select the Solaris failsafe archive option in the GRUB boot menu during the next reboot. The failsafe boot option provides instructions for rebuilding the boot archive. Once that is complete, the boot can be continued by clearing the SMF boot archive with the svcadm clear boot-archive command.
• Command not found: This is a C shell error message that means exactly what it says. It typically means that the command was misspelled or does not live on the PATH.
• Communication error on send (ECOMM): The link between machines breaks after data is sent, but before the confirmation is received.
• Component system is busy, try again: failed to offline: cfgadm attempted to remove or replace a device with a mounted file system, swap area or configured dump device. Unmount the file system, remove the swap and/or disable the dump device, then retry the cfgadm command. See the cfgadm(1M) man page.
• Configuration operation invalid: invalid transition: The incorrect device may have been specified, or there may be a problem with the device or its seating. Use cfgadm to check the receptacle and its state. The card may need to be reseated.
• Connection refused (ECONNREFUSED): The target machine actively refused the connection. The service may not be active, or there may be restrictions on connections (such as the hosts.allow and hosts.deny in TCP wrappers).
• Connection reset (ECONNRESET): The target system forcibly closed an existing connection. This typically happens as a result of a reboot or a timeout.
• Connection timed out (ETIMEOUT): The target host is unreachable due to network problems or the system being down.
• Core dumped: A core file (image of software memory at the time of failure) has been taken. See Core File Management.
• Corrupt label: This happens if cylinder 0 has been overwritten, usually by a database using a raw partition including cylinder 0. The best solution is to back everything up and repartition the disk with cylinder 0 either not in any partition or at least in a partition with a filesystem (such as UFS) that respects cylinder 0.
• cpio: Bad magic number/header: The cpio archive has become corrupted. We can try to recover whatever we can by using the cpio -k command.
• Cross-device link (EXDEV): Hard links are not permitted across different filesystems. Use a soft link instead.
• Data access exception: Mismatch between the operating system and disk storage hardware. This can be due to mis-seated DIMMs or disk problems, so it makes sense to try to identify any hardware problems. Usually, the operating system (and perhaps filesystem) will need to be upgraded to deal with the newer hardware.
• DataDigest=... is required, can't accept: Device returned an improperly processed DataDigest. Verify that storage device digest settings are compatible with the initiator.
• Data Fault: This is a particular type of bad trap that indicates a configuration text or data access fault. See BAD TRAP above.
• Deadlock situation detected/avoided (EDEADLK): A potential deadlock over a system resource (usually a lock) was detected and avoided. The software should be examined to see if it can be made more resilient.
• Destination address required (EDESTADDRREQ): An address was omitted from an operation that requires one.
• /dev/fd/#: cannot open: Indicates that the file descriptor file system (fdfs) is not mounted correctly. In most cases, the problem is that it is mounted either nosuid or not at all. The file descriptor file system should have the following options in the vfstab:
fd - /dev/fd fd - no -
• Device busy (EBUSY): A hard drive or removable media failed to unmount or eject due to an active process using them. The fuser command allows us to see what processes are using the filesystem or even kill them with a command like:
fuser -ck /mountpoint
(Make sure that you know what processes are running on a filesystem before killing them.)
• DIMMs Manufacturer Mismatch: DIMMs in the system are not on the hardware compatibility list.
• Directory not empty: This is an error from rmdir which means exactly what it says. Non-empty directories cannot be removed. (If a process is holding a file open, it is possible to track down the culprit by looking for the inode of the file in question (ls -i filename) in pfiles output.)
• Disc quota exceeded (EDQUOT): A user's disk quota has been exceeded. Some of the user's files can be removed or the quotas can be increased with edquota.
• Disk# not unique: This error is displayed if there are multiple EEPROM devalias entries for a disk. At the ok> prompt, the values of the aliases can be shown with
ok> printenv
the aliases can be reset with
ok> nvunalias disk#
ok> nvalias disk# device-path
• dquot table full: The UFS quota table needs to be increased in size. This is done by increasing ndquot in /etc/system and rebooting. ndquot defaults to (maxusers x 40)/4 + max_nprocs
• dr in progress: This error may occur if a SCSI unconfigure operation fails while only partially completed. The controller may need to be reconfigured with cfgadm
• driver not attached: No driver currently attached to the specified device because no device exists at the node or the device is not in use. This may or may not mean that a proper driver is not installed. Make sure that the driver is installed and properly configured.
• empty RADIUS shared secret: The RADIUS shared secret needs to be set.
• Error 88 (EILSEQ): This is an illegal byte sequence error. Multiple characters have been provided where only one is expected.
• Error code 2: access violation: This error is due to a permissioning or pathing error on a tftp get.
• Error: missing file arg (cm3): A filename was not included in an sccs command that requires one.
• error opening dir: The specified path may not be a directory.
• error writing name when booting: /etc/nodename must contain exactly one line with the name of the system and no blanks or returns.
• esp0: data transfer overrun: This error appears when we attempt to mount a CD drive with an 8192 block size as opposed to the Sun-standard 512 block size. Check with the drive manufacturer to see if the block size can be switched.
• ether_hostton: Bad file number/Resource temporarily unavailable: These messages may be a result of a mis-matched nodename file. Make sure that the /etc/nodename entry matches the corresponding /etc/hostname.interface and /etc/inet/hosts files.
• Event not found: The shell reports that a command matching the request cannot be found in the history buffer for the shell session. The history command shows the current contents of the history buffer.
• Exec format error (ENOEXEC): This error usually means that the software was compiled for an architecture other than the one on which it finds itself. This may also happen if an expected binary compatibility package is not installed. The file command displays the expected architecture for the binary.
• Failed to initialize adapter: If the adapter has been correctly identified, this means that the configuration of the adapter is incorrect. In particular, make sure to check the DMA settings.
• Failed to receive login response: Initiator failed to receive a login Payload Data Unit (PDU) across the network. Verify that the network connection is working.
• Failed to transfer login: Initiator failed to transfer a login Payload Data Unit (PDU) across the network. Verify that the network connection is working.
• Fast access mmu miss: This is usually due to a hardware problem. Memory is a possible culprit, as are the system board and CPU. Check PROM Monitor Diagnostics for hardware diagnostics on OBP/Sparc systems.
• File descriptor in bad state (EBADFD): The requested file descriptor does not refer to an open file or it refers to a file descriptor that is restricted to another purpose. (For example, a read request is made to a file descriptor that is open for writing only.)
• File exists (EEXISTS): An existing file was targeted for a command that would have overwritten it improperly. For example, there may have been a request to overwrite a file while the csh noclobber option is set, or there may have been a request to set a link to the name of an existing file.
• File locking deadlock (EDEADLOCK): Two processes deadlocked over a resource, such as a lock. This is a software programming bug.
• File name too long (ENAMETOOLONG): The referenced file name is longer than the limit specified in /usr/include/limits.h.
• File system full: The file system is full. (Error messages sometimes mean what they say.) If the message occurs during a login, the problem is likely the filesystem that includes the utmpx file (usually /var).
• File too large (EFBIG): The file size has grown past what is allowed by the protocol or filesystem in question, or exceeds the resource limit (rlimit) for file size. The resource limit can be checked by running ulimit -a in Bourne or Korn shells or limit in C shell. Check the Resource Management page for additional information on managing resource limits.
• Giving up: In the context of a SCSI command, this means that the timeout has been exceeded. This is usually due to a hardware or connection problem, but it can be caused by contention on the SCSI channel, or even a mis-match in timeout settings between the OS and the device in question.
• Hardware address trying to be our address: Either we have two systems on our network with the same IP address, or we have snooping enabled on a device on the network.
• Host is down (EHOSTDOWN): A connection attempt failed because the target system was unavailable.
• HeaderDigest=... is required, can't accept: Device returned an improperly processed HeaderDigest. Verify that storage device digest settings are compatible with the initiator.
• Host name local configuration error: sendmail wants to have a fully qualified domain name for the local host. It is good practice to include a fully qualified domain name in the hosts file entry for the local server.
• Hypertransport Sync Flood occurred on last boot: Uncorrectable ECC error caused the last reboot. For x64 systems, check the service processor's System Event Log and BIOS log to identify the culprit.
• Identifier removed (EIDRM): There is a problem accessing a file associated with messaging, semaphores or shared memory. Check the msgctl(2), semctl(2) or shmctl(2) man page for more details.
• ieN Ethernet jammed: The number of successive failed transmission attempts has exceeded the threshold. Check whether the network is saturated or check for other network problems.

• ieN no carrier: The carrier detect pin died during a packet transmission, resulting in a dropped packet. Check for loose connections and otherwise check the network.
• If pipe/FIFO, don't sleep in stream head (ESTRPIPE): There is a problem with the STEAMS connection.
• ifconfig: bad address: Check /etc/hostname.* to make sure that the entries match the hosts file. When this error occurs early in the boot process, make sure that the filesystem containing hostname.* and hosts is online at that stage of the boot process. If “files” is not the first entry in the “hosts” line of /etc/nsswitch.conf, the hostname lookup will not be possible until the interface comes online.
• ifconfig: no such interface: Make sure that the /etc/hostname.interface file exists.
• Illegal instruction: This error message means exactly what it says. This may come about because the binary is not compiled for this architecture (see “Exec format error” above), or it may come as a result of trying to run a data file as a program. If this appears during a boot, it means that the system is trying to boot from a non-boot device, that the boot information has become corrupted, or that the boot information is meant for a different architecture.
• Illegal seek (ESPIPE): There is a problem with a pipe in the statement. A workaround suggested by Sun is to redirect the output of the source command to a scratch file, then process the file.
• Initiator could not be successfully authenticated: Verify CHAP and/or RADIUS settings, as appropriate.
• Initiator is not allowed access to the given target: Verify initiator name, masking and provisioning.
• initiator name is required: The initiator name is improperly configured.
• Interrupted system call (EINTR): An signal (like an interrupt or quit) was received before the system call had completed. (If we try to resume, we may error out as a result of this condition.)
• Invalid argument (EINVAL): System cannot interpret a supplied parameter. Depending on the context, this may be an indication that the object named by the parameter is not set up properly.
• Invalid null command: This may indicate that there were two pipes in a row (“||”) in the referenced command.
• I/O error (EIO): This references a physical I/O fault. Depending on the context, it makes sense to replace the removable media, check all connections, run diagnostics on the referenced hardware or fsck the filesystem. If this error occurs during a write, we must assume that the data is corrupt.
• Is a directory (EISDIR): We tried to treat a directory like a file.
• iSCSI service or target is not currently operational: Run diagnostics on the storage device hardware; check storage device software configuration.
• Kernel read error: savecore is unable to read the kernel data structures to produce a crash dump. This may indicate a hardware problem, especially a memory problem. This problem may accompany a BAD TRAP error.
• Killed: This may happen as a result of a memory allocation attempt where either there is insufficient swap space or the stack and data segment size are in conflict. A “Killed” message may also appear when a program is sent a SIGKILL by other means, such as a kill command.
• kmem_free block already free: This is a software programming bug, probably in a device driver.
• ld.so.1 fatal: can't set protection on segment: Sun reports a case where this error occurred due to a lack of swap space. ld.so.1 complained because there was no segment on which to set protections.
• ld.so.1 fatal: open failed: No such file or directory: The linker was unable to find the shared library in question. Make sure that LD_LIBRARY_PATH is set properly.
• ld.so.1 fatal: relocation error: referenced symbol not found: The symbol referenced by the specified application was not found. This error most frequently occurs after installations or upgrades of shared libraries. ldd -d on the application will show its dependencies. Depending on the nature of the conflict, it may be resolvable by changing the LD_LIBRARY_PATH or installing an appropriate version of the shared library.
• Link has been severed (ENOLINK): The connection to a remote machine has been severed, either by the remote process dying or a network problem.
• Login incorrect: This error means that an appropriate username and password pair was not entered. This may be due to a problem with the passwd and shadow file, the naming service, or the user forgetting login credentials.
• login redirection failed: Storage device attempted to redirect initiator to an invalid destination. Verify storage device redirection settings.
• Memory Configuration Mismatch: Can be caused by damaged or unsupported DIMMs, or by running non-identical DIMMs within the same bank.
• Message too long (EMSGSIZE): A message was sent that was larger than the internal message buffer.
• Miscellaneous iSCSI initiator errors: Check the initiator.
• Missing parameters (e.g, iSCSI initiator and/or target name): Verify that the initiator and target name are properly specified.
• mount: ...already mounted... (EBUSY): Either the filesystem is mounted elsewhere, an active process has its working directory inside the mount point or the maximum number of mounts has been exceeded.
• mount: giving up on...: The remote mount request was unsuccessful for more than the threshold number of retries. Check the network connection and make sure that the NFS server is sharing the directory to the client as expected.
• mount: mount-point...does not exist: The directory specified as the mount point does not exist.
• mount: the state of /dev/dsk/... is not okay: The filesystem should either be mounted read-only or fsck-ed.
• Network dropped connection because of reset (ENETRESET): The remote host crashed or rebooted.
• Network is down (ENETDOWN): A transport connection failed due to a dead network.
• Network is unreachable (ENETUNREACH): Either there is no route to the network, or negative status information was received from intermediate network devices.
• NFS getattr failed for server...RPC: Timed out: The NFS server has failing hardware. (For a server that is slow to respond, the NFS server not responding message would appear instead.)
• nfs mount: Couldn't bind to reserved port: The NFS server has multiple network cards bound to the same subnet.
• nfs mount: mount:...Device busy: An active process has a working directory inside the mount point.
• NFS mount:...mounted OK: A backgrounded mount completed successfully. This may be an indication that the server response is poor, since otherwise the mount would have completed immediately and not required backgrounding.
• NFS read failed for server: This is a permissions problem error message. In addition to checking the permissions on the NFS server, make sure that the permissions underneath the mount are acceptable. (Mount points should have 755 permissions to avoid odd permissioning behavior on mounted filesystems.)
• nfs_server: bad getargs: The arguments are unrecognized or incorrect. This may be an indication of a network problem, or it may indicate a software configuration problem on the client.
• NFS server ... not responding: The network connection to the NFS server is either slow or broken.
• NFS server ... ok: The network connection to the NFS server has been restored. This is a followup to NFS server ... not responding.
• nfs umount: ... is busy: An active process has a working directory inside the specified NFS mount. See the Device busy error message.
• NFS write error on host ... No space left on device: If an NFS mount runs out of space, attempts to write to files on the share may corrupt or zero out those files.
• NFS write failed for server ... RPC: Timed out: The filesystem is soft mounted, and response time is inadequate. Sun recommends that writable filesystems not be soft-mounted, as it can lead to data corruption.
• No carrier-cable disconnected or hub disabled?: This error may manifest due to a physical networking problem or a configuration issue.
• No child processes (ECHILD): An application attempted to communicate with a cooperating process that does not exist. Either the child exited improperly or failed to start.
• No default media available: Drives contain no floppy or CD media to eject.
• No directory! Logging in with home=/: The home directory either does not exist or is not permissioned such that the user can use it. If home directories are automounted, it may be necessary to troubleshoot the automounter.
• no driver found for device: A driver has been disabled while the device is still attached. Depending on the type of device, cfgadm, drvconfig, devfsadm or a reconfiguration reboot (boot -r) may be required. Check the System Administration Guide: Devices and File Systems document.
• No message of desired type (ENOMSG): Something attempted to receive a message of a type that does not exist on the message queue. See the msgsnd(2) and msgrcv(2) man pages.
• No record locks available (ENOLCK): Any of several different locking subsystems, including fcntl(2), NFS lockd and mail, may yield this message when no more locks are available.
• No route to host (EHOSTUNREACH): In practice, this message is not distinguishable from Network is unreachable.
• No shell Connection closed: The shell specified for the user is either unavailable or illegal. Make sure it is listed in /etc/shells and that it exists. It may be necessary to change the passwd entry for this user to assign a valid shell.
• No space left on device (ENOSPC): The disk, tape or diskette is full.
• No such device (ENODEV): An operation was attempted on an inappropriate or nonexistent device. Make sure that it exists in /devices and /dev. The drvconfig or boot -r commands can be used to regenerate many /devices entries.
• No such device or address (ENXIO): I/O has been attempted to a device that does not exist or that exists beyond the limits of the device. Make sure that the device in question is powered up and connected properly, including the correct SCSI ID.
• No such file or directory (ENOENT): The file or path name does not exist on the system. Make sure that the relevant filesystems are mounted and that the expected files and/or directories exist.
• No such process (ESRCH): The process does not exist on the system. It may have finished prior to the attempt to reference it.
• No such user ... cron entries not created: Even though a file exists in /var/spool/cron/crontabs for this username, the username is not present in the passwd database.
• No utmpx entry: The filesystem containing the utmpx file is full. This may need to be resolved in single-user mode, since logins will not be permitted.
• Not a data message (EBADMSG): Data has come to the head of a STREAMS queue that cannot be processed. See the man pages for read(2), getmsg(2) and ioctl(2).
• Not a directory (ENOTDIR): A non-directory was specified as an argument where a directory is required.
• Not a stream device (ENOTSTR): The file descriptor used as a target for the putmsg(2) or getmsg(2) is not a STREAMS device.
• Not a UFS filesystem: The boot device is improperly defined. For x86, boot the system with the Configuration Assistant/boot CD and identify the disk from which to boot. For PROM-based systems, set the boot-device properly in the PROM environment variables.
• Not enough space (ENOMEM): Insufficient swap space available.
• Not found: The specified command could not be found. Check the spelling and the PATH.
• Not login shell: Use exit to get out of non-login shells. (The logout command can only be used from login shells.)
• Not on system console: Direct root logins are only permitted on the system console unless otherwise specified in /etc/default/login.
• Not owner (EPERM): Action attempted that can only be performed by object owner or the superuser.
• Not supported (ENOTSUP): A requested application feature is not available in the current version, though it may be expected in a future release.
• Object is remote (EREMOTE): We tried to share a resource not on the local machine.
• Operation already in progress (EALREADY): An operation was already in progress on a non-blocking object.
• Operation canceled (ECANCELED): The asynchronous operation was canceled before completion.
• Operation not applicable (ENOSYS): No system support exists for this operation.
• Operation not supported on transport endpoint (EOPNOTSUPP): Tried to accept a connection on a datagram transport endpoint.
• Operation now in progress (EINPROGRESS): Operation in progress on a non-blocking object.
• Option not supported by protocol (ENOPROTOOPT): A bad option or level was specified.
• Out of memory: System is running out of virtual memory (including swap space). See “Not enough space” as well.
• Out of stream resources (ENOSR): No STEAMS queues or no STREAMS head data structures available during a STREAMS open.
• Overlapping swap volume: Make sure that the additional swap volumes have unique names.
• Package not installed (ENOPKG): The attempted system call belongs to a package that is not installed on this system.
• Paired DIMMs Mismatch: Checksum mismatch between two DIMMs in a pair. Can be caused by damaged or non-identical DIMMs.
• Panic – boot: Could not mount filesystem: (During a Jumpstart) The Jumpstart boot process is unable to get to the install image. Make sure that the Jumpstart configurations and file shares are correct.
• Panic ... valloc'd past tmpptes: May occur if maxusers is set to an absurdly high number. It should not be set past the number of MB of RAM or 4096, whichever is smaller.
• Permission denied (EACCES): The attempted file access is forbidden due to filesystem permissions.
• Protocol family not supported (EPFNOSUPPORT): The protocol has not been implemented on this system.
• Protocol not supported (EPROTONOSUPPORT): The protocol has not been configured for this system. Check the protocols database (/etc/inet/protocols by default).
• Protocol wrong type for socket (EPROTOTYPE): Application programming error or misconfigured protocols. The requested protocol does not support the requested socket type. Make sure that the protocols database matches with the corresponding entries in /usr/include/sys/socket.h.
• quotactl: open Is a directory: A directory named “quota” can cause edquota to fail. Such directories should be renamed.
• RADIUS packet authentication failed: Re-set the RADIUS shared secret.
• Read error from network: Connection reset by peer: The remote system crashed or rebooted during an rsh or rlogin session.
• Read-only file system (EROFS): We can't change stuff on filesystems that are mounted read-only.
• received invalid login response: Storage device response was unexpected. Verify initiator authentication settings.
• Requested iSCSI version range is not supported by the target: The initiator's iSCSI version is not supported by the target storage device. Check the compatibility lists. See if firmware or driver upgrades would be sufficient.
• Requested ITN does not exist at this address: The iSCSI target name (ITN) is not accessible. Verify the initiator discovery information and storage device configuration.
• Requested ITN has been removed and no forwarding address is provided: The requested iSCSI target name is no longer accessible. Verify the initiator discovery information and storage device configuration.
• Resource temporarily unavailable (EAGAIN): fork(2) cannot create a new process due to a lack of resources. These resources may include limits on active processes (see the Resource Management page) or a lack of swap space.
• Restartable system call (ESTART): The system call has been interrupted in a restartable state.
• Result too large (ERANGE): This is a programming or data input error. The result of a calculation is not representable in the defined data type. The matherr(3M) facility may be helpful in debugging the problem.
• ROOT LOGIN ...: Someone has just logged in as root or su-ed to root.
• RPC: Program not registered: Make sure that the requested service is available.
• rx framing error: This error usually indicates a problem with the network hardware. Framing errors are types of CRC errors, which are usually caused by physical media problems.
• SCSI bus DATA IN phase parity error: This is a problem related to SCSI hardware or connections. It may have to do with hardware that is not qualified for attachment to Sun servers, connections with cables that are flaky or too long (total length more than 6 meters), bad terminators or flaky power supplies. See the SCSI transport failed: reason 'reset' message as well.
• SCSI transport failed: reason 'reset': The system sent data that was never received due to a SCSI reset. This may occur due to conflicting SCSI IDs, hardware that is not qualified for attachment to Sun servers, connections with cables that are flaky or too long (total length more than 6 meters), bad terminators or flaky power supplies. These issues have also been observed on systems where the highest capacity DIMMs are not in the lowest numbered slots. Disk arrays wth read-ahead caches can sometimes also cause this problem; turn off the caching to see if the problem goes away. Non-obvious SCSI ID conflicts may be diagnosed using the PROM monitor probe-scsi-all command. (See OBP Command Line Diagnostics for more details.) These errors may also happen when the SCSI device and the server are set to different SCSI timeout thresholds.
• Segmentation Fault: These can be produced as a result of programming errors or improperly set rlimit resource settings. (See Resource Management for how to check and adjust resource settings.) Segmentation faults are an indication that the program has attempted to access an area of memory that is protected or does not exist. Programming causes for segmentation faults include dereferencing a null pointer and indexing past the bounds of an array.
• setmnt: Cannot open /etc/mnttab for writing: The system is unable to write to /etc/mnttab. This may be caused by the /etc directory being mounted read-only (which can happen during certain types of boot problems).
• share_nfs: /home: Operation not applicable: A local filesystem is mounted on /home, which is usually reserved for use by the automounter.
• skipping LIST command – no active base: A LIST command is present without an associated BASE command. (cachefspack)
• Socket type not supported (ESOCKTNOSUPPORT): The socket type's support has not been configured for this system.
• Soft error rate ... during writing was too high: The number of soft errors on a tape device have exceeded the threshold. It may be due to a dirty head, bad media or a faulty tape drive.
• Software caused connection abort (ECONNABORTED): The connection was aborted within the local host machine.
• Stale NFS file handle (ESTALE): The file or directory on the NFS server is no longer available. It may have been removed or replaced. A remount may be needed to force a renegotiation of file handles.
• statd: cannot talk to statd: statd has left remnants in the /var/statmon/sm and /var/statmon/sm.bak directories. Files named after inactive hosts should be removed, and statd and lockd should be restarted.
• su: No shell: The default shell for root is improper. It may have been set to a nonexistent program or an illegal shell. This problem has been known to occur when an extra space is appended to the “root” line of the passwd file. The passwd file will need to be repaired while booted from CDROM or network.
• syncing file system: The kernel is updating the superblocks before taking the system down or in the wake of a panic.
• System booting after fatal error FATAL: This can be caused by UPA address parity errors, Master queue overflows or DTAG parity errors. This is going to be due to a bad CPU or possibly a bad system board.
• tar: ...: No such file or directory: The specified target (which defaults to TAPE) is not available. This may be due to a hardware problem with the tape drive or connections, or to a misspecified target.
• tar: directory checksum error: The checksum of the files read from tape do not match the checksum in the header block. This may be due to an incorrectly specified block size or a bad piece of tape media.
• tar: tape write error: A physical write error has occurred on the tar target.
• Target hardware or software error: Run diagnostics on the storage device hardware; check storage device software configuration.
• Target has insufficient session, connection or other resources: Check storage device settings. Check with storage device vendor to see if resource settings can be increased or capacity can be otherwise increased.
• target protocol group tag mismatch: Initiator and target had a Target Portal Group Tag (TPGT) mismatch. Verify TPGT discovery settings on initiator and storage device.
• Text file busy (ETXTBSY): An attempt was made to execute a file that was open for writing.
• The SCSI bus is hung: The likely cause is a conflict in SCSI target numbers. See the SCSI transport failed: reason 'reset' message as well.
• Timeout waiting for ARP/RARP packet: Indicates a network connection problem while booting from the network. This problem can sometimes be observed on subnets containing multiple servers willing to answer a RARP request, which can result in a server without a bootparams file receiving a request. (We have had good luck moving Jumpstart targets to an isolated subnet for initial installations.)
• Timer expired: The timer for a STREAMS ioctl has expired. The cause is device specific, and may be related to a flaky hardware, driver failure or an inappropriately short timeout threshold.
• Too many links (EMLINK): A file has too many hard links associated with it. Use soft links instead.
• Too many open files (EMFILE): A process has exceeded the limit on the number of open files per process. (See the Resource Management page for methods to monitor and manage these limits.)
• Transport endpoint is already connected (EISCONN): Connection request made on an already connected transport endpoint.
• Transport endpoint is not connected (ENOTCONN): The endpoint is not connected and/or an address was not specified.
• Trap 3E: These are caused by a bad boot disk superblock. This may have been caused by a failing disk, faulty disk connections, software misconfiguration or duplicate SCSI addresses. Check the possible hardware and SCSI configuration issues before attempting to recover the superblock using the methods listed under BAD SUPER BLOCK above.
• Too Many Arguments: This is a variant of the C shell's Arguments too long message, except that this time the problem may be the number rather than the length of arguments.
• unable to connect to target: Initiator unable to establish a network connection. This message typically accompanied by an error number from /usr/include/sys/errno.h.
• unable to get shared objects: The executable may be corrupt or in an unrecognized format.
• unable to initialize authentication: Verify that initiator authentication settings are properly configured.
• unable to make login pdu: Initiator could not make a login Payload Data Unit (PDU) based on the initiator and storage device settings. Reset target login parameters and other settings as required.
• unable to schedule enumeration: Initiator unable to enumerate the LUNs on the target. LUN enumeration can be forced via the devfsadm -i iscsi command.
• unable to set [authentication|ipsec|password|remote authentication|username]: Verify that initiator authentication settings are properly configured.
• uname: error writing name when booting: /etc/nodename must contain exactly one line with the name of the system and no blanks or returns.
• Unknown service: Either the service is not listed in the services database (/etc/services by default), or the permissions for the services database are set so that the user cannot read it.
• Value too large for defined data type (EOVERFLOW): Argument improperly formatted for the structure allocated to it.
• WARNING: /tmp: File system full, swap space limit exceeded: Virtual memory has filled up. A reboot is recommended after we have figured out which process is hogging all the memory and/or swap, since the system may be in an unstable state.
• WARNING: TOD clock not initialized: It is likely that the system clock's battery is dead.
• Watchdog Reset: This usually indicates a hardware problem. (See the Watchdog Resets page for a complete discussion.)
• Window Underflow: These errors sometimes accompany a trap, especially at boot time. Some program attempted access of a register window that was not accessible from that processor. These errors may occur when differently sized DIMMs are improperly used together, or when cache memory has gone bad. If mismatched memory is not the problem, the CPU or system board will need to be replaced.
• wrong magic number: See “Corrupt label” above.
• you are not authorized to use: A configuration file (eg at.deny or cron.deny) forbids access to this service.
File Descriptors
A file descriptor is a handle created by a process when a file is opened. A new descriptor is created each time the file is opened. It is associated with a file object which includes information such as the mode in which the file was opened and the offset pointer where the next operation will begin. This information is called the context of the file.
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.
kmastat
Kernel memory size can be tracked using the sar -k command. The total of the "alloc" fields is the kernel memory size. If it appears to be growing without bound, you may have a memory leak. It should be noted that not all buckets are tracked by sar -k, so the reported memory size is not as accurate as that reported by crash.
On occasion there are problems related to memory leaks in the kernel or one of the associated modules. In these cases, kmastat can provide useful information pinpointing the source of the leak.
To check on kernel memory allocations on a running system, run a crash session as follows:

# crash
dumpfile = /dev/mem, namelist = /dev/ksyms, outfile = stdout
> kmastat
The first number on the "Total" line represents the total amount of memory allocated by the kernel. If this is a significant fraction of available system memory and growing, there is a problem.
The output from the kmastat command also contains information on a number of "buckets" or categories for memory allocation.
Additional information can be obtained via the kmausers command, but this requires that we load kadb prior to booting. To do this, reach the ok> prompt, then:

ok> boot kadb -d
kadb: (hit the "return" key)
kadb[0]: kmem_flags/W 01
kadb[0]: :c
Loading kadb this way means that kadb will only be effective for this current boot session.
Once the system is up, we can either force a core dump via STOP-A/ ok> sync, or we can examine the live system. In either case, inside the crash session we would type:

>kmausers bucket_name
The result will show memory allocations inside that bucket. The names of functions inside each allocation will be a tip-off to what is actually grabbing the memory allocation.
A script can be run from cron to capture this information. The format of this script would be something like:

#!/bin/sh
date >> log_file
echo "kmastat" | /usr/sbin/crash -w log_file
sleep 20
echo "kmausers kmem_alloc_2048" | /usr/sbin/crash -w log_file
Slab Allocator
Solaris 2.4+ uses a kernel memory allocator known as a slab allocator.
A kernel memory allocator performs the following functions:
• Allocate memory
• Initialize objects/structures
• Use objects/structures
• Deconstruct objects/structures
• Free memory
The structures in the memory objects include sub-objects such as linked list headers, mutexes, reference counts and condition variables. In the case of Solaris, the deconstruction step includes setting objects to their initial settings, which can save time when the memory objects have to be re-initialized.
A translation lookaside buffer (TLB) is an associative cache of recent address translations. When the MMU (memory management unit) cannot find a translation in the TLB, it lookus it up in the address maps and loads the address into the TLB. Entries in the TLB are replaced on a least recently used basis.
The slab allocator is organized as a collection of object caches. Each of these caches contains only one type of object (proc structures, vnodes, etc). The kernel is responsible for restoring each object to its initial state when it is released. When a cache requires additional space, the allocator gives a slab of memory from the page-level allocator and creates objects from it. The slab contains enough memory for several object instances. A small part of the slab is used by the cache to manage memory in the slab; the rest is divided into buffers that are the size of the object. The allocator then initializes these buffers with the appropriate constructor.
When the page-level allocator needs to recover memory, unused slabs are reaped by deconstructing the objects on slabs whose objects are all free, then removing the slab from the cache in question.
The structure for each slab includes unused space at the beginning of the slab (coloring area), the set of objects, more unused space (the amount left over after the maximum number of objects has been created), and a slab data area. Each object also includes a four byte area for a free list pointer. The slab data area includes a count of in-use objects, pointers for a doubly-linked list of slabs in the same cache, and a pointer to the first free area in the slab. The coloring areas are different sizes for each slab in a cache (where possible). This allows a balanced distribution of traffic on the hardware caches and memory busses by varying the offsets for the different slabs.
Large object slabs are slightly different in that management data is stored in a separate pool of memory, since large slabs are usually multiples of a page in size. A hash table is also maintained to provide lookups between the management area and the slabs.

Kernel Modules
• modinfo prints out information on all currently loaded kernel modules.
• modload loads kernel modules.
• modunload unloads kernel modules.
• forceload in the /etc/system file loads a module at boot time.
NFS Troubleshooting
Sun's web pages contain substantial information about NFS services; search for an NFS Administration Guide or NFS Server Performance and Tuning Guide for the version of Solaris you are running. The share_nfs man page contains specific information about export options.
If NFS is not working at all, try the following:
• Make sure that the NFS server daemons are running. In particular, check for statd, lockd, nfsd and rarpd. If the daemons are not running, they can be started by running /etc/init.d/nfs.server start. See Daemons below for information on NFS-related daemons.
• Check the /etc/dfs/dfstab and type shareall.
• Use share or showmount -e to see which filesystems are currently exported, and to whom. showmount -a shows who the server believes is actually mounting which filesystems.
• Make sure that your name service is translating the server and client hostnames correctly on both ends. Check the server logs to see if there are messages regarding failed or rejected mount attempts; check to make sure that the hostnames are correct in these messages.
• Make sure that the /etc/net/*/hosts files on both ends report the correct hostnames. Reboot if these have to be edited.
If you are dealing with a performance issue, check
• Network Issues
• CPU Useage
• Memory Levels
• Disk I/O
• Increase the number of nfsd threads in /etc/init.d/nfs.server if the problem is that requests are waiting for a turn. Note that this does increase memory useage by the kernel, so make sure that there is enough RAM in the server to handle the additional load.
• Where possible, mount filesystem with the ro option to prevent additional, unnecessary attribute traffic.
• If attribute caching does not make sense (for example, with a mail spool), mount the filesystem with the noac option. If nfsstat reports a high getattr level, actimeo may need to be increased (if the attributes do not change too often).
• nfsstat reports on most NFS-related statistics. The nfsstat page includes information on tuning suggestions for different types of problems that can be revealed with nfsstat.
If these steps do not resolve the issue, structural changes may be required:
• cachefs can be used to push some of the load from the NFS server onto the NFS clients. To be useful, cfsadmin should be used to increase maxfilesize for the cache to a value high enough to allow for the caching of commonly-used files. (The default value is 3 Mb.)
NFS Client
When a client makes a request to the NFS server, a file handle is returned. The file handle is a 32 byte structure which is interpreted by the NFS server. Commonly, the file handle includes a file system ID, inode number and the generation number of the inode. (The latter can be used to return a "stale file handle" error message if the inode has been freed and re-used between client file accesses.)
If a response is not received for a request, it is resent, but with an incremented xid (transmission ID). This can happen because of congestion on the network or the server, and can be observed with a snoop session between server and client.
The server handles retransmissions differently depending on whether the requests are idempotent (can be executed several times without ill effect) or nonidempotent (cannot be executed several times). Examples of these would include things like reads and getattrs versus writes, creates and removes. The system maintains a cache of nonidempotent requests so that appropriate replies can be returned.
Daemons
The following daemons play a critical role in NFS service:
• biod: On the client end, handles asynchronous I/O for blocks of NFS files.
• nfsd: Listens and responds to client NFS requests.
• mountd: Handles mount requests.
• lockd: Network lock manager.
• statd: Network status manager.

Solaris Processes
The process is one of the fundamental abstactions of Unix. Every object in Unix is represented as either a file or a process. (With the introduction of the /proc structure, there has been an effort to represent even processes as files.)
Processes are usually created with fork or a less resource intensive alternative such as fork1 or vfork. fork duplicates the entire process context, while fork1 only duplicates the context of the calling thread. This can be useful (for example), when exec will be called shortly.
Solaris, like other Unix systems, provides two modes of operation: user mode, and kernel (or system) mode. Kernel mode is a more privileged mode of operation. Processes can be executed in either mode, but user processes usually operate in user mode.
Per-process Virtual Memory
Each process has its own virtual memory space. References to real memory are provided through a process-specific set of address translation maps. The computer's Memory Management Unit (MMU) contains a set of registers that point to the current process's address translation maps. When the current process changes, the MMU must load the translation maps for the new process. This is called a context switch.
The MMU is only addressable in kernel mode, for obvious security reasons.
The kernel text and data structures are mapped in a portion of each process's virtual memory space. This area is called the kernel space (or system space).
In addition, each process contains these two important kernel-owned areas in virtual memory: u area and kernel stack. The u area contains information about the process such as information about open files, identification information and process registers. The kernel stack is provided on a per-process basis to allow the kernel to be re-entrant. (ie, several processes can be involved in the kernel, and may even be executing the same routine concurrently.) Each process's kernel stack keeps track of its function call sequence when executing in the kernel.
The kernel can access the memory maps for non-current processes by using temporary maps.
The kernel can operate in either process context or system (or interrupt) context. In process context, the kernel has access to the process's memory space (including u area and kernel stack). It can also block the current process while waiting for a resource. In kernel context, the kernel cannot access the address space, u area or kernel stack. Kernel context is used for handling certain system-wide issues such as device interrupt handling or process priority computation.
Additional information is available on the Process Virtual Memory page.
Process Context
Each process's context contains information about the process, including the following:
• Hardware context:
o Program counter: address of the next instruction.
o Stack pointer: address of the last element on the stack.
o Processor status word: information about system state, with bits devoted to things like execution modes, interrupt priority levels, overflow bits, carry bits, etc.
o Memory management registers: Mapping of the address translation tables of the process.
o Floating point unit registers.
• User address space: program text, data, user stack, shared memory regions, etc.
• Control information: u area, proc structure, kernel stack, address translation maps.
• Credentials: user and group IDs (real and effective).
• Environment variables: strings of the form variable= value.
During a context switch, the hardware context registers are stored in the Process Control Block in the u area.
The u area includes the following:
• Process control block.
• Pointer to the proc structure.
• Real/effective UID/GID.
• Information regarding current system call.
• Signal handlers.
• Memory management information (text, data, stack sizes).
• Table of open file descriptors.
• Pointers to the current directory vnode and the controlling terminal vnode.
• CPU useage statistics.
• Resource limitations (disk quotas, etc)
The proc structure includes the following:
• Identification: process ID and session ID
• Kernel address map location.
• Current process state.
• Pointers linking the process to a scheduler queue or sleep queue.
• Pointers linking this process to lists of active, free or zombie processes.
• Pointers keeping this structure in a hash queue based on PID.
• Sleep channel (if the process is blocked).
• Scheduling priority.
• Signal handling information.
• Memory management information.
• Flags.
• Information on the relationship of this process and other processes.
Kernel Services
The Solaris kernel may be seen as a bundle of kernel threads. It uses synchronization primitives to prevent priority inversion. These include mutexes, semaphores, condition variables and read/write locks.
The kernel provides service to processes in the following four ways:
• System Calls: The kernel executes requests submitted by processes via system calls. The system call interface invokes a special trap instruction.
• Hardware Exceptions: The kernel notifies a process that attempts several illegal activities such as dividing by zero or overflowing the user stack.
• Hardware Interrupts: Devices use interrupts to notify the kernel of status changes (such as I/O completions).
• Resource Management: The kernel manages resources via special processes such as the pagedaemon.
In addition, some system services (such as NFS service) are contained within the kernel in order to reduce overhead from context switching.
Threads
An application's parallelism is the degree of parallel execution acheived. In the real world, this is limited by the number of processors available in the hardware configuration. Concurrency is the maximum acheivable parallelism in a theoretical machine that has an unlimited number of processors. Threads are frequently used to increase an application's concurrency.
A thread represents a relatively independent set of instructions within a program. A thread is a control point within a process. It shares global resources within the context of the process (address space, open files, user credentials, quotas, etc). Threads also have private resources (program counter, stack, register context, etc).
The main benefit of threads (as compared to multiple processes) is that the context switches are much cheaper than those required to change current processes. Sun reports that a fork() takes 30 times as long as an unbound thread creation and 5 times as long as a bound thread creation.
Even within a single-processor environment, multiple threads are advantageous because one thread may be able to progress even though another thread is blocked while waiting for a resource.
Interprocess communication also takes considerably less time for threads than for processes, since global data can be shared instantly.
Kernel Threads
A kernel thread is the entity that is scheduled by the kernel. If no lightweight process is attached, it is also known as a system thread. It uses kernel text and global data, but has its own kernel stack, as well as a data structure to hold scheduling and syncronization information.
Kernel threads store the following in their data structure:
• Copy of the kernel registers.
• Priority and scheduling information.
• Pointers to put the thread on the scheduler or wait queue.
• Pointer to the stack.
• Pointers to associated LWP and proc structures.
• Pointers to maintain queues of threads in a process and threads in the system.
• Information about the associated LWP (as appropriate).
Kernel threads can be independently scheduled on CPUs. Context switching between kernel threads is very fast because memory mappings do not have to be flushed.
Lightweight Processes
A lightweight process can be considered as the swappable portion of a kernel thread.
Another way to look at a lightweight process is to think of them as "virtual CPUs" which perform the processing for applications. Application threads are attached to available lightweight processes, which are attached to a a kernel thread, which is scheduled on the system's CPU dispatch queue.
LWPs can make system calls and can block while waiting for resources. All LWPs in a process share a common address space. IPC (interprocess communication) facilities exist for coordinating access to shared resources.
LWPs contain the following information in their data structure:
• Saved values of user-level registers (if the LWP is not active)
• System call arguments, results, error codes.
• Signal handling information.
• Data for resource useage and profiling.
• Virtual time alarms.
• User time/CPU usage.
• Pointer to the associated kernel thread.
• Pointer to the associated proc structure.
By default, one LWP is assigned to each process; additional LWPs are created if all the process's LWPs are sleeping and there are additional user threads that libthread can schedule. The programmer can specify that threads are bound to LWPs.
Lightweight process information for a process can be examined with ps -elcL.
User Threads
User threads are scheduled on their LWPs via a scheduler in libthread. This scheduler does implement priorities, but does not implement time slicing. If time slicing is desired, it must be programmed in.
Locking issues must also be carefully considered by the programmer in order to prevent several threads from blocking on a single resource.
User threads are also responsible for handling of SIGSEGV (segmentation violation) signals, since the kernel does not keep track of user thread stacks.
Each thread has the following characteristics:
• Has its own stack.
• Shares the process address space.
• Executes independently (and perhaps concurrently with other threads).
• Completely invisible from outside the process.
• Cannot be controlled from the command line.
• No system protection between threads in a process; the programmer is responsible for interactions.
• Can share information between threads without IPC overhead.
Priorities
Higher numbered priorities are given precedence. The scheduling page contains additional information on how priorities are set.
Zombie Processes
When a process dies, it becomes a zombie process. Normally, the parent performs a wait() and cleans up the PID. Sometimes, the parent receives too many SIGCHLD signals at once, but can only handle one at a time. It is possible to resend the signal on behalf of the child via kill -18 PPID. Killing the parent or rebooting will also clean up zombies. The correct answer is to fix the buggy parent code that failed to perform the wait() properly.
Aside from their inherent sloppiness, the only problem with zombies is that they take up a place in the process table.
Kernel Tunables
The following kernel tunables are important when looking at processes:
• maxusers: By default, this is set to 2 less than the number of Mb of physical memory, up to 1024. It can be set up to 2048 manually in the /etc/system file.
• max_nprocs: Maximum number of processes that can be active simultaneously on the system. The default for this is (16 x maxusers) + 10. The minimum setting for this is 138, the maximum is 30,000.
• maxuprc: The default setting for this is max_nprocs - 5. The minimum is 133, the maximum is . This is the numberof processes a single non-root user can create.
• ndquot: This is the number of disk quota structures. The default for this is (maxusers x 10) + max_nprocs. The minimum is 213.
• pt_cnt: Sets the number of System V ptys.
• npty: Sets the number of BSD ptys. (Should be set to pt_cnt.)
• sad_cnt: Sets the number of STREAMS addressable devices. (Should be set to 2 x pt_cnt.)
• nautopush: Sets the number of STREAMS autopush entries. (Should be set to pt_cnt.)
• ncsize: Sets DNLC size.
• ufs_ninode: Sets inode cache size.
proc Commands
The proc tools are useful for tracing attributes of processes. These utilities include:
• pflags: Prints the tracing flags, pending and held signals and other /proc status information for each LWP.
• pcred: Prints credentials (ie, EUID/EGID, RUID/EGID, saved UID/GIDs).
• pmap: Prints process address space map.
• pldd: Lists dynamic libraries linked to the process.
• psig: Lists signal actions.
• pstack: Prints a stack trace for each LWP in the process.
• pfiles: Reports fstat, fcntl information for all open files.
• pwdx: Prints each process's working directory.
• pstop: Stops process.
• prun: Starts stopped process.
• pwait: Wait for specified processes to terminate.
• ptree: Prints process tree for process.
• ptime: Times the command using microstate accounting; does not time children.
These commands can be run against a specific process, but most of them can also be run against all processes on the system. See the above- referenced man page for details.

Process Virtual Memory
Each process maps either 2^32 or 2^44 bytes of memory (depending on whether the OS is running in 32 or 64-bit mode). This works out to 4GB or 16TB. Not all of this memory is allocated (used); the virtual memory is used as address space that can be mapped to actual memory resources.
Virtual memory structure for a process can be described as in this diagram:

Kernel

While this is part of the address space, it cannot be addressed directly by the process. It must be addressed via system calls.
Stack

Used by the program for variables and storage. It grows and shrinks in size depending on what routines are called and what their stack space requirements are. It is normally about 8MB in size.
Shared Libraries
Shared libraries are position independent so that they can be shared by all programs that want to use them. One common example is libc.so.
hole

This is the address space that is unallocated and unused. It does not tie up physical memory. For most processes, this is the largest portion of the virtual memory for the process.
heap

Used for some types of working storage. It is allocated by the malloc function.
BSS

Uninitialized variables. These are not part of the executable file and their initial value is set to zeros.
Data

Global variables, constants, static variables from the program.
Text

Set of instructions from the compiler-generated executable file.
The virtual memory map for a process can be displayed using the pmap command.
Additional information is available on the Processes page.

Solaris Filesystem Troubleshooting
Filesystem corruption can be detected and often repaired by the format and fsck commands. If the filesystem corruption is not due to an improper system shutdown, the hard drive hardware may need to be replaced.
ufs filesystems contain the following types of blocks:
• boot block: This stores information used to boot the system.
• superblock: Much of the filesystems internal information is stored in these.
• inode: Stores location information about a file--everything except for the file name. The number of inodes in a filesystem can be changed from the default if newfs -i is used to create the filesystem.
• data block: The file's data is stored in these.
fsck
The fsck command is run on each filesystem at boot time. This utility checks the internal consistency of the filesystem, and can make simple repairs on its own. More complex repairs require feedback from the root user, either in terms of a "y" keyboard response to queries, or invocation with the -y option.
If fsck cannot determine where a file belongs, the file may be renamed to its inode number and placed in the filesystem's lost+found directory. If a file is missing after a noisy fsck session, it may still be intact in the lost+found directory.
Sometimes the fsck command complains that it cannot find the superblock. Alternative superblock locations were created by newfs at the time that the filesystem was created. The newfs -N command can be invoked to nondestructively discover the superblock locations for the filesystem.
ufs filesystems can carry "state flags" that have the value of fsclean, fsstable, fsactive or fsbad (unknown). These can be used by fsck during boot time to skip past filesystems that are believed to be okay.
format
The analyze option of format can be used to examine the hard drive for flaws in a nondestructive fashion.
df
df can be used to check a filesystem's available space. Of particular interest is df -kl, which checks available space for all local filesystems and prints out the statistics in kilobytes. Solaris 10 also allows us to use df -h, which presents the statistics in a more human-friendly form that doesn't require counting digits to decide whether a file is 100M or 1G in size.
du
du can be used to check space used by a directory. In particular, du -dsk will report useage in kilobytes of a directory and its descendants, without including space totals from other filesystems.
Filesystem Tuning
Filesystem performance can be improved by looking at filesystem caching issues.
The following tuning parameters may be valuable in tuning filesystem performance with tunefs or mkfs/newfs:
• inode count: The default is based upon an assumption of average file sizes of 2 KB. This can be set with mkfs/newfs at the time of filesystem creation.
• time/space optimization: Optimization can be set to allow for fastest performance or most efficient space useage.
• minfree: In Solaris 2.6+, this is set to (64 MB / filesystem size) x 100. Filesystems in earlier OS versions reserved 10%. This parameter specifies how much space is to be left empty in order to preserve filesystem performance.
• maxbpg: This is the maximum number of blocks a file can leave in a single cylinder group. Increasing this limit can improve large file performance, but may have a negative impact on small file performance.
Filesystem Performance Monitoring
McDougall, Mauro and Gregg suggest that the best way to see if I/O is a problem at all is to look at the amount of time spent on POSIX read() and write() system calls via DTrace. If so, we need to look at the raw disk I/O performance.

iostat
As with most of the monitoring commands, the first line of iostat reflects a summary of statistics since boot time. To look at meaningful real-time data, run iostat with a time step (eg iostat 30) and look at the lines that report summaries over the time step intervals.
For Solaris 2.6 and higher, use iostat -xPnce 30 to get information including the common device names of the disk partitions, CPU statistics, error statistics, and extended disk statistics.
For Solaris 2.5.1 and earlier, or for more compact output, use iostat -xc 30 to get the extended disk and CPU statistics.
In either case, the information reported is:
• disk: Disk device name.
• r/s, w/s: Average reads/writes per second.
• Kr/s, Kw/s: Average Kb read/written per second.
• wait: Time spent by a process while waiting for block
(eg disk) I/O to complete. (See Notes on Odd Behavior below.)
• actv: Number of active requests in the hardware queue.
• %w: Occupancy of the wait queue.
• %b: Occupancy of the active queue with the device busy.
• svc_t: Service time (ms). Includes everything: wait time, active queue time, seek rotation, transfer time.
• us/sy: User/system CPU time (%).
• wt: Wait for I/O (%).
• id: Idle time (%).
Notes on Odd Behavior
The "wait" time reported by iostat refers to time spent by a process while waiting for block device (such as disk) I/O to finish. In Solaris 2.6 and earlier, the calculation algorithm sometimes overstates the problem on multi-processor machines, since it does not take into account that an I/O wait on one CPU does not mean that I/O is blocked for processes on the other CPUs. Solaris 7 has corrected this problem.
iostat also sometimes reports excessive svc_t (service time) readings for disks that are very inactive. This is due to the action of fsflush keeping the data in memory and on the disk up-to-date. Since many writes are specified over a very short period of time to random parts of the disk, a queue forms briefly, and the average service time goes up. svc_t should only be taken seriously on a disk that is showing 5% or more activity.

mpstat
mpstat reports information which is useful in understanding lock contention and CPU loading issues.
mpstat reports the following:
• CPU: Processor ID
• minf: Minor faults
• mjf: Major fault
• xcal: Processor cross-calls (when one CPU wakes up another by interrupting it). If this exceeds 200/second, the application in question may need to be examined.
• intr: Interrupts.
• ithr: Interrupts as threads (except clock).
• csw: Context switches
• icsw: Involuntary context switches (this is probably the more relevant statistic when examining performance issues.)
• migr: Thread migrations to another processor. If the migr measurement of mpstat is greater than 500, rechoose_interval should be sent longer in the kernel.
• smtx: Number of times a CPU failed to obtain a mutex.
• srw: Number of times a CPU failed to obtain a read/write lock on the first try.
• syscl: Number of system calls.
• usr/sys/wt/idl: User/system/wait/idle CPU percentages.

netstat
netstat provides useful information regarding traffic flow.
In particular, netstat -i lists statistics for each interface, netstat -s provides a full listing of several counters, and netstat -rs provides routing table statistics. netstat -an reports all open ports.
netstat -k provides a useful summary of several network-related statistics up through Solaris 9, but this option was removed in Solaris 10 in favor of the /bin/kstat command. Through Solaris 9, netstat -k provides a listing of several component kstat statistics.
Here are some of the issues that can be revealed with netstat:
• netstat -i: (Collis+Ierrs+Oerrs)/(Ipkts+Opkts) > 2%: This may indicate a network hardware issue.

• netstat -i: (Collis/Opkts) > 10%: The interface is overloaded. Traffic will need to be reduced or redistributed to other interfaces or servers.

• netstat -i: (Ierrs/Ipkts) > 25%: Packets are probably being dropped by the host, indicating an overloaded network (and/or server). Retransmissions can be dropped by reducing the rsize and wsize mount parameters to 2048 on the clients. Note that this is a temporary workaround, since this has the net effect of reducing maximum NFS throughput on the segment.

• netstat -s: If significant numbers of packets arrive with bad headers, bad data length or bad checksums, check the network hardware.

• netstat -i: If there are more than 120 collisions/second, the network is overloaded. See the suggestions above.

• netstat -i: If the sum of input and output packets is higher than about 600 for a 10Mbs interface or 6000 for a 100Mbs interface, the network segment is too busy. See the suggestions above.
• netstat -r: This form of the command provides the routing table. Make sure that the routes are as you expect them to be.

nfsstat
nfsstat can be used to examine NFS performance.
nfsstat -s reports server-side statistics. In particular, the following are important:
• calls: Total RPC calls received.
• badcalls: Total number of calls rejected by the RPC layer.
• nullrecv: Number of times an RPC call was not available even though it was believed to have been received.
• badlen: Number of RPC calls with a length shorter than that allowed for RPC calls.
• xdrcall: Number of RPC calls whose header could not be decoded by XDR (External Data Representation).
• readlink: Number of times a symbolic link was read.
• getattr: Number of attribute requests.
• null: Null calls are made by the automounter when looking for a server for a filesystem.
• writes: Data written to an exported filesystem.
Sun recommends the following tuning actions for some common conditions:
• writes > 10%: Write caching (either array-based or host-based, such as a Prestoserv card) would speed up operation.
• badcalls >> 0: The network may be overloaded and should be checked out. The rsize and wsize mount options can be set on the client side to reduce the effect of a noisy network, but this should only be considered a temporary workaround.
• readlink > 10%: Replace symbolic links with directories on the server.
• getattr > 40%: The client attribute cache can be increased by setting the actimeo mount option. Note that this is not appropriate where the attributes change frequently, such as on a mail spool. In these cases, mount the filesystems with the noac option.
nfsstat -c reports client-side statistics. The following statistics are of particular interest:
• calls: Total number of calls made.
• badcalls: Total number of calls rejected by RPC.
• retrans: Total number of retransmissions. If this number is larger than 5%, the requests are not reaching the server consistently. This may indicate a network or routing problem.
• badxid: Number of times a duplicate acknowledgement was received for a single request. If this number is roughly the same as badcalls, the network is congested. The rsize and wsize mount options can be set on the client side to reduce the effect of a noisy network, but this should only be considered a temporary workaround.
If on the other hand, badxid=0, this can be an indication of a slow network connection.
• timeout: Number of calls that timed out. If this is roughly equal to badxid, the requests are reaching the server, but the server is slow.
• wait: Number of times a call had to wait because a client handle was not available.
• newcred: Number of times the authentication was refreshed.
• null: A large number of null calls indicates that the automounter is retrying the mount frequently. The timeo parameter should be changed in the automounter configuration.
nfsstat -m (from the client) provides server-based performance data.
• srtt: Smoothed round-trip time. If this number is larger than 50ms, the mount point is slow.
• dev: Estimated deviation.
• cur: Current backed-off timeout value.
• Lookups: If cur>80 ms, the requests are taking too long.
• Reads: If cur>150 ms, the requests are taking too long.
• Writes: If cur>250 ms, the requests are taking too long.
p-Commands
In Unix, every object is either a file or a process. With the /proc virtual file system, even processes may be treated like files.
/proc (or procfs) is a virtual file system that allows us to examine processes like files. This means that /proc allows us to use file-like operations and intuitions when looking at processes. /proc does not occupy disk space; it is located in working memory. This structure was originally designed as a programming interface for writing debuggers, but it has grown considerably since then.
To avoid confusion, we will refer to the virtual file system as /proc or procfs. The man page for procfs is proc(4). proc, on the other hand, will be used to refer to the process data structure discussed in the Process Structure page.
Under /proc is a list of numbers, each of which is a Process ID (PID) for a process on our system. Under these directories are subdirectories referring to the different components of interest of each process. This directory structure can be examined directly, but we usually prefer to use commands written to extract information from this structure. These are known as the p-commands.
• pcred: Display process credentials (eg EUID/EGID, RUID/RGID, saved UIDs/GIDs)
• pfiles: Reports fstat() and fcntl() information for all open files. This includes information on the inode number, file system, ownership and size.
• pflags: Prints the tracing flags, pending and held signals and other /proc status information for each LWP.
• pgrep: Finds processes matching certain criteria.
• pkill: Kills specified processes.
• pldd: Lists dynamic libraries linked to the process.
• pmap: Prints process address space map.
• prun: Starts stopped processes.
• prstat: Display process performance-related statistics.
• ps: List process information.
• psig: Lists signal actions.
• pstack: Prints a stack trace for each LWP in the process.
• pstop: Stops the process.
• ptime: Times the command; does not time children.
• ptree: Prints process genealogy.
• pwait: Wait for specified processes to complete.
• pwdx: Prints process working directory.
prstat Example 1
CPU Saturation is can be directly measured via prstat. (Saturation refers to a situation where there is not enough CPU capacity to adequately handle requests for processing resources.) Saturation can be measured directly by looking at the CPU latency time for each thread reported by prstat -mL. (LAT is reported as a percentage of the time that a thread is waiting to use a processor.)
This example shows the prstat -mL output from a single-CPU system that has been overloaded. Notice the load average and LAT numbers.
PID USERNAME USR SYS TRP TFL DFL LCK SLP LAT VCX ICX SCL SIG PROCESS/LWPID
2724 root 24 0.2 0.0 0.0 0.0 0.0 2.2 74 284 423 361 0 gzip/1
2729 root 21 0.3 0.0 0.0 0.0 0.0 3.3 75 396 564 518 0 gzip/1
2733 root 20 0.3 0.0 0.0 0.0 0.0 5.3 75 391 514 484 0 gzip/1
2737 root 14 0.2 0.0 0.0 0.0 0.0 4.1 81 176 415 383 0 gzip/1
2730 root 3.3 0.3 0.0 0.0 0.0 0.0 96 0.7 602 258 505 0 gunzip/1
2734 root 2.9 0.3 0.0 0.0 0.0 0.0 92 4.5 522 280 457 0 gunzip/1
2738 root 2.7 0.2 0.0 0.0 0.0 0.0 93 3.9 377 147 370 0 gunzip/1
2725 root 2.4 0.2 0.0 0.0 0.0 0.0 95 2.4 495 179 355 0 gunzip/1
2728 root 0.1 1.4 0.0 0.0 0.0 0.0 97 1.7 769 11 2K 0 tar/1
2732 root 0.1 1.3 0.0 0.0 0.0 0.0 99 0.2 762 14 2K 0 tar/1
2723 root 0.0 1.1 0.0 0.0 0.0 0.0 99 0.1 564 7 1K 0 tar/1
2731 root 0.3 0.4 0.0 0.0 0.0 0.0 98 1.2 754 3 1K 0 tar/1
2735 root 0.3 0.4 0.0 0.0 0.0 0.0 98 0.9 722 0 1K 0 tar/1
2736 root 0.0 0.6 0.0 0.0 0.0 0.0 99 0.0 341 2 1K 0 tar/1
2726 root 0.3 0.3 0.0 0.0 0.0 0.0 98 1.0 473 145 1K 0 tar/1
2739 root 0.2 0.2 0.0 0.0 0.0 0.0 99 0.3 335 1 664 0 tar/1
2749 scromar 0.0 0.1 0.0 0.0 0.0 0.0 100 0.0 23 0 194 0 prstat/1
337 root 0.0 0.0 0.0 0.0 0.0 0.0 100 0.0 6 0 36 6 xntpd/1
2716 scromar 0.0 0.0 0.0 0.0 0.0 0.0 100 0.0 3 1 21 0 sshd/1
124 root 0.0 0.0 0.0 0.0 0.0 0.0 100 0.0 3 0 17 0 picld/4
119 root 0.0 0.0 0.0 0.0 0.0 0.0 100 0.0 21 0 63 0 nscd/26
Total: 51 processes, 164 lwps, load averages: 4.12, 2.13, 0.88
prstat Example 2
In this case, we sort prstat output to look for the processes with heavy memory utilization:
# prstat -s rss
PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP
471 juser 125M 58M sleep 59 0 4:26:46 0.6% java/17
200 daemon 62M 55M sleep 59 0 0:01:21 0.0% nfsmapid/4
18296 juser 116M 39M sleep 26 11 0:05:36 0.1% java/23
...
254 root 3968K 1016K sleep 59 0 0:00:03 0.0% sshd/1
Total: 47 processes, 221 lwps, load averages: 0.20, 0.21, 0.20
Other Usage Examples
# ps -ef | grep more | grep -v grep
root 18494 8025 0 08:53:09 pts/3 0:00 more
# pgrep more
18494
# pmap -x 18494
18494: more
Address Kbytes RSS Anon Locked Mode Mapped File
00010000 32 32 - - r-x-- more
00028000 8 8 8 - rwx-- more
0002A000 16 16 16 - rwx-- [ heap ]
FF200000 864 824 - - r-x-- libc.so.1
FF2E8000 32 32 32 - rwx-- libc.so.1
FF2F0000 8 8 8 - rwx-- libc.so.1
FF300000 16 16 - - r-x-- en_US.ISO8859-1.so.3
FF312000 16 16 16 - rwx-- en_US.ISO8859-1.so.3
FF330000 8 8 - - r-x-- libc_psr.so.1
FF340000 8 8 8 - rwx-- [ anon ]
FF350000 168 104 - - r-x-- libcurses.so.1
FF38A000 32 32 24 - rwx-- libcurses.so.1
FF392000 8 8 8 - rwx-- libcurses.so.1
FF3A0000 24 16 16 - rwx-- [ anon ]
FF3B0000 184 184 - - r-x-- ld.so.1
FF3EE000 8 8 8 - rwx-- ld.so.1
FF3F0000 8 8 8 - rwx-- ld.so.1
FFBFC000 16 16 16 - rw--- [ stack ]
-------- ------- ------- ------- -------
total Kb 1456 1344 168 -
# pstack 18494
18494: more
ff2c0c7c read (2, ffbff697, 1)
00015684 ???????? (0, 1, 43858, ff369ad4, 0, 28b20)
000149a4 ???????? (ffbff82f, 28400, 15000000, 28af6, 0, 28498)
00013ad8 ???????? (0, 28b10, 28c00, 400b0, ff2a4a74, 0)
00012780 ???????? (2a078, ff393050, 0, 28b00, 2a077, 6b)
00011c68 main (28b10, ffffffff, 28c00, 0, 0, 1) + 684
000115cc _start (0, 0, 0, 0, 0, 0) + 108
# pfiles 18494
18494: more
Current rlimit: 256 file descriptors
0: S_IFIFO mode:0000 dev:292,0 ino:2083873 uid:0 gid:0 size:0
O_RDWR
1: S_IFCHR mode:0620 dev:284,0 ino:12582922 uid:1000 gid:7 rdev:24,3
O_RDWR|O_NOCTTY|O_LARGEFILE
/devices/pseudo/pts@0:3
2: S_IFCHR mode:0620 dev:284,0 ino:12582922 uid:1000 gid:7 rdev:24,3
O_RDWR|O_NOCTTY|O_LARGEFILE
/devices/pseudo/pts@0:3
# pcred 18494
18494: e/r/suid=0 e/r/sgid=0
groups: 0 1 2 3 4 5 6 7 8 9 12
sar
The word "sar" is used to refer to two related items:
1. The system activity report package
2. The system activity reporter
System Activity Report Package
This facility stores a great deal of performance data about a system. This information is invaluable when attempting to identify the source of a performance problem.
The Report Package can be enabled by uncommenting the appropriate lines in the sys crontab. The sa1 program stores performance data in the /var/adm/sa directory. sa2 writes reports from this data, and sadc is a more general version of sa1.
In practice, I do not find that the sa2-produced reports are terribly useful in most cases. Depending on the issue being examined, it may be sufficient to run sa1 at intervals that can be set in the sys crontab.
Alternatively, sar can be used on the command line to look at performance over different time slices or over a constricted period of time:

sar -A -o outfile 5 2000

(Here, "5" represents the time slice and "2000" represents the number of samples to be taken. "outfile" is the output file where the data will be stored.)
The data from this file can be read by using the "-f" option (see below).

System Activity Reporter
sar has several options that allow it to process the data collected by sa1 in different ways:
• -a: Reports file system access statistics. Can be used to look at issues related to the DNLC.

o iget/s: Rate of requests for inodes not in the DNLC. An iget will be issued for each path component of the file's path.

o namei/s: Rate of file system path searches. (If the directory name is not in the DNLC, iget calls are made.)

o dirbk/s: Rate of directory block reads.

• -A: Reports all data.

• -b: Buffer activity reporter:

o bread/s, bwrit/s: Transfer rates (per second) between system buffers and block devices (such as disks).

o lread/s, lwrit/s: System buffer access rates (per second).

o %rcache, %wcache: Cache hit rates (%).

o pread/s, pwrit/s: Transfer rates between system buffers and character devices.

• -c: System call reporter:

o scall/s: System call rate (per second).

o sread/s, swrit/s, fork/s, exec/s: Call rate for these calls (per second).

o rchar/s, wchar/s: Transfer rate (characters per second).

• -d: Disk activity (actually, block device activity):

o %busy: % of time servicing a transfer request.

o avque: Average number of outstanding requests.

o r+w/s: Rate of reads+writes (transfers per second).

o blks/s: Rate of 512-byte blocks transferred (per second).

o avwait: Average wait time (ms).

o avserv: Average service time (ms). (For block devices, this includes seek rotation and data transfer times. Note that the iostat svc_t is equivalent to the avwait+avserv.)

• -e HH:MM: CPU useage up to time specified.

• -f filename: Use filename as the source for the binary sar data. The default is to use today's file from /var/adm/sa.

• -g: Paging activity (see "Paging" for more details):

o pgout/s: Page-outs (requests per second).

o ppgout/s: Page-outs (pages per second).

o pgfree/s: Pages freed by the page scanner (pages per second).

o pgscan/s: Scan rate (pages per second).

o %ufs_ipf: Percentage of UFS inodes removed from the free list while still pointing at reuseable memory pages. This is the same as the percentage of igets that force page flushes.

• -i sec: Set the data collection interval to i seconds.

• -k: Kernel memory allocation:

o sml_mem: Amount of virtual memory available for the small pool (bytes). (Small requests are less than 256 bytes)

o lg_mem: Amount of virtual memory available for the large pool (bytes). (512 bytes-4 Kb)

o ovsz_alloc: Memory allocated to oversize requests (bytes). Oversize requests are dynamically allocated, so there is no pool. (Oversize requests are larger than 4 Kb)

o alloc: Amount of memory allocated to a pool (bytes). The total KMA useage is the sum of these columns.

o fail: Number of requests that failed.

• -m: Message and semaphore activities.

o msg/s, sema/s: Message and semaphore statistics (operations per second).

• -o filename: Saves output to filename.

• -p: Paging activities.

o atch/s: Attaches (per second). (This is the number of page faults that are filled by reclaiming a page already in memory.)

o pgin/s: Page-in requests (per second) to file systems.

o ppgin/s: Page-ins (per second). (Multiple pages may be affected by a single request.)

o pflt/s: Page faults from protection errors (per second).

o vflts/s: Address translation page faults (per second). (This happens when a valid page is not in memory. It is comparable to the vmstat-reported page/mf value.)

o slock/s: Faults caused by software lock requests that require physical I/O (per second).

• -q: Run queue length and percentage of the time that the run queue is occupied.

• -r: Unused memory pages and disk blocks.

o freemem: Pages available for use (Use pagesize to determine the size of the pages).

o freeswap: Disk blocks available in swap (512-byte blocks).

• -s time: Start looking at data from time onward.

• -u: CPU utilization.

o %usr: User time.

o %sys: System time.

o %wio: Waiting for I/O (does not include time when another process could be schedule to the CPU).

o %idle: Idle time.

• -v: Status of process, inode, file tables.

o proc-sz: Number of process entries (proc structures) currently in use, compared with max_nprocs.

o inod-sz: Number of inodes in memory compared with the number currently allocated in the kernel.

o file-sz: Number of entries in and size of the open file table in the kernel.

o lock-sz: Shared memory record table entries currently used/allocated in the kernel. This size is reported as 0 for standards compliance (space is allocated dynamically for this purpose).

o ov: Overflows between sampling points.

• -w: System swapping and switching activity.

o swpin/s, swpot/s, bswin/s, bswot/s: Number of LWP transfers or 512-byte blocks per second.

o pswch/s: Process switches (per second).

• -y: TTY device activity.

o rawch/s, canch/s, outch/s: Input character rate, character rate processed by canonical queue, output character rate.

o rcvin/s, xmtin/s, mdmin/s: Receive, transmit and modem interrupt rates.

vmstat
The first line of vmstat represents a summary of information since boot time. To obtain useful real-time statistics, run vmstat with a time step (eg vmstat 30).
The vmstat output columns are as follows use the pagesize command to determine the size of the pages):
• procs or kthr/r: Run queue length.
• procs or kthr/b: Processes blocked while waiting for I/O.
• procs or kthr/w: Idle processes which have been swapped.
• memory/swap: Free, unreserved swap space (Kb).
• memory/free: Free memory (Kb). (Note that this will grow until it reaches lotsfree, at which point the page scanner is started. See "Paging" for more details.)
• page/re: Pages reclaimed from the free list. (If a page on the free list still contains data needed for a new request, it can be remapped.)
• page/mf: Minor faults (page in memory, but not mapped). (If the page is still in memory, a minor fault remaps the page. It is comparable to the vflts value reported by sar -p.)
• page/pi: Paged in from swap (Kb/s). (When a page is brought back from the swap device, the process will stop execution and wait. This may affect performance.)
• page/po: Paged out to swap (Kb/s). (The page has been written and freed. This can be the result of activity by the pageout scanner, a file close, or fsflush.)
• page/fr: Freed or destroyed (Kb/s). (This column reports the activity of the page scanner.)
• page/de: Freed after writes (Kb/s). (These pages have been freed due to a pageout.)
• page/sr: Scan rate (pages). Note that this number is not reported as a "rate," but as a total number of pages scanned.
• disk/s#: Disk activity for disk # (I/O's per second).
• faults/in: Interrupts (per second).
• faults/sy: System calls (per second).
• faults/cs: Context switches (per second).
• cpu/us: User CPU time (%).
• cpu/sy: Kernel CPU time (%).
• cpu/id: Idle + I/O wait CPU time (%).
•
vmstat -i reports on hardware interrupts.
vmstat -s provides a summary of memory statistics, including statistics related to the DNLC, inode and rnode caches.
vmstat -S reports on swap-related statistics such as:
• si: Swapped in (Kb/s).
• so: Swap outs (Kb/s).
(Note that the man page for vmstat -s incorrectly describes the swap queue length. In Solaris 2, the swap queue length is the number of idle swapped-out processes. (In SunOS 4, this referred to the number of active swapped-out processes.)
Solaris 8
vmstat under Solaris 8 will report different statistics than would be expected under an earlier version of Solaris due to a different paging algorithm:
• Page Reclaim rate higher.
• Higher reported Free Memory: A large component of the filesystem cache is reported as free memory.
• Low Scan Rates: Scan rates will be near zero unless there is a systemwide shortage of available memory.
vmstat -p reports paging activity details for applications (executables), data (anonymous) and filesystem activity.

System Configuration Files
For details about the files and commands summarized here, consult the appropriate man pages or http://docs.sun.com/

File Description
/etc/bootparams Contains information regarding network boot clients.
/etc/cron.d/cron.allow
/etc/cron.d/cron.deny Allow access to crontab for users listed in this file. If the file does not exist, access is permitted for users not in the /etc/cron.d/cron.deny file.
/etc/defaultdomain NIS domain set by /etc/init.d/inetinit
/etc/default/cron Sets cron logging with the CRONLOG variable.
/etc/default/login Controls root logins via specification of the CONSOLE variable, as well as variables for login logging thresholds and password requirements.
/etc/default/su Determines logging activity for su attempts via the SULOG and SYSLOG variables, sets some initial environment variables for su sessions.
/etc/dfs/dfstab Determines which directories will be NFS-shared at boot time. Each line is a share command.
/etc/dfs/sharetab Contains a table of resources that have been shared via share.
/etc/group Provides groupname translation information.
/etc/hostname.interface Assigns a hostname to interface; assigns an IP address by cross- referencing /etc/inet/hosts.
/etc/hosts.allow
/etc/hosts.deny Determine which hosts will be allowed access to TCP wrapper mediated services.
/etc/hosts.equiv Determines which set of hosts will not need to provide passwords when using the "r" remote access commands (eg rlogin, rsh, rexec)
/etc/inet/hosts
/etc/hosts Associates hostnames and IP addresses.
/etc/inet/inetd.conf
/etc/inetd.conf Identifies the services that are started by inetd as well as the manner in which they are started. inetd.conf may even specify that TCP wrappers be used to protect a service.

/etc/inittab inittab is used by init to determine scripts to for different run levels as well as a default run level.
/etc/logindevperm Contains information to change permissions for devices upon console logins.
/etc/magic Database of magic numbers that identify file types for file.
/etc/mail/aliases
/etc/aliases Contains mail aliases recognized by sendmail.
/etc/mail/sendmail.cf
/etc/sendmail.cf Mail configuration file for sendmail.
/etc/minor_perm Specifies permissions for device files; used by drvconfig
/etc/mnttab Contains information about currently mounted resources.
/etc/name_to_major List of currently configured major device numbers; used by drvconfig.
/etc/netconfig Network configuration database read during network initialization.
/etc/netgroup Defines groups of hosts and/or users.
/etc/netmasks Determines default netmask settings.
/etc/nsswitch.conf Determines order in which different information sources are accessed when performing lookups.
/etc/path_to_inst Contents of physical device tree using physical device names and instance numbers.
/etc/protocols Known protocols.
/etc/remote Attributes for tip sessions.

/etc/rmtab Currently mounted filesystems.
/etc/rpc Available RPC programs.
/etc/services Well-known networking services and associated port numbers.
/etc/syslog.conf Configures syslogd logging.
/etc/system Can be used to force kernel module loading or set kernel tuneable parameters.

/etc/vfstab Information for mounting local and remote filesystems.
/var/adm/messages Main log file used by syslogd.
/var/adm/sulog Default log for recording use of su command.
/var/adm/utmpx User and accounting information.
/var/adm/wtmpx User login and accounting information.
/var/local/etc/ftpaccess
/var/local/etc/ftpconversions
/var/local/etc/ftpusers wu-ftpd configuration files to set ftp access rights, conversion/compression types, and a list of userids to exclude from ftp operations.
/var/lp/log Print services activity log.
/var/sadm/install/contents Database of installed software packages.
/var/saf/_log Logs activity of SAF (Service Access Facility).

Important Header Files
Some of these header files contain important information that can be used when analyzing a core dump or setting parameter values.
Location Description
/usr/include/sys Most system header files.
/usr/include/vm Header files describing virtual memory structures.
/usr/include/sys/fs Header files describing file system structures and types.
/usr/platform/`arch -k`/include/sys Architecture dependent structures.
/usr/platform/`arch -k`/include/vm Architecture-dependent virtual memory structures.
/usr/include/[net, nfs, rpc, protocols, inet, netinet] Define networking data structures.

The /etc/inittab File
The /etc/inittab file plays a crucial role in the boot sequence.
For versions of Solaris prior to version 10, the /etc/inittab was edited manually. Solaris 10+ manages the /etc/inittab through SMF. The Solaris 10 inittab should not be edited directly
The default Solaris 10 inittab contains the following:
1. ap::sysinit:/sbin/autopush -f /etc/iu.ap
2. sp::sysinit:/sbin/soconfig -f /etc/sock2path
3. smf::sysinit:/lib/svc/bin/svc.startd >/dev/msglog 2<>/dev/msglog
4. p3:s1234:powerfail:/usr/sbin/shutdown -y -i5 -g0 >/dev/msglog 2<>/dev/...
The lines accomplish the following:
1. Initializes Streams
2. Configures socket transport providers
3. Initializes SMF master restarter
4. Describes a power fail shutdown
In particular, the default keyword is not used any more in Solaris 10. Instead, the default run level is determined within the SMF profile.
When the init process is started, it first sets environment variables set in the /etc/default/init file; by default, only TIMEZONE is set. Then init executes process entries from the inittab that have sysinit set, and transfers control of the startup process to svc.startd.
Solaris 8 and 9
The line entries in the inittab file have the following format:
id:runlevel:action:process
Here the id is a two-character unique identifier, runlevel indicates the run level involved, action indicates how the process is to be run, and process is the command to be executed.
At boot time, all entries with runlevel "sysinit" are run. Once these processes are run, the system moves towards the init level indicated by the "initdefault" line. For a default inittab, the line is:
is:3:initdefault:
(This indicates a default runlevel of 3.)
By default, the first script run from the inittab file is /etc/bcheckrc, which checks the state of the root and /usr filesystems. The line controlling this script has the following form:
fs::sysinit:/sbin/bcheckrc >/dev/console 2>&1 The inittab also controls what happens at each runlevel. For example, the default entry for runlevel 2 is:
s2:23:wait:/sbin/rc2 >/dev/console 2>&1 The action field of each entry will contain one of the following keywords:
• powerfail: The system has received a "powerfail" signal.
• wait: Wait for the command to be completed before proceeding.
• respawn: Restart the command.

solaris qucik sheet

2009-04-15T02:32:00.001-07:00

Solaris QuickSheet
Compatibility note: This document is based upon Sparc Solaris 10
OBP
All the following commands are to be run from the OBP and not
the OS. They are only valid on Sparc hardware that uses the openboot
rmware. The eeprom command can be used from the OS to view or
set openboot rmware variables.
Show the value of the auto-boot? variable
printenv auto-boot?
Set the system to not auto boot
setenv auto-boot? false
Restore the system default for auto boot
set-default auto-boot?
Show the default boot device
printenv boot-device
List the actual device path for the disk device alias
devalias disk
List all openboot variables, current, and default values
printenv
Show devices seen by openboot
show-devs
Show help on all OBP commands
help
Boot the system into single user mode from the CD ROM
boot cdrom -s
Boot the system into single user mode using the default device
boot -s
Reset the system
reset-all
Packages
Install the gcc package
pkgadd -d gcc-3.4.6-sol10-sparc-local
Check to see if gcc is installed on system
pkginfo SMCgcc /or/ pkginfo | grep gcc
Remove the gcc package
pkgrm SMCgcc
Check the installation of the gcc (SMCgcc) package
pkgchk SMCgcc
Show revisions of packages on system
showrev -p
Get expected le info and source package for a le
pkgchk -l -p /usr/sfw/bin/gcc
Verify all packages (and les) on the system
pkgchk
Display information about a package
pkgchk -l SMCgcc
Display version information about an installed package
pkginfo -x SMCgcc
List all patches on the system
showrev -p /or/ patchadd -p
List patches applied to the SUNWckr package
pkgparam SUNWckr PATCHLIST
smpatch and updatemanager can be used to manage system patches.
Devices
Scan for new devices to the system
devfsadm
List (verbosely) all attachment points (con gurable hardware)
List all disks on system
iostat -En
Tape unit { X = device number, n = no rewind
/dev/rmt/X n
The /dev directory contains links to /devices
(format) slice
ags are:
wm { Writeable Mountable (ie: A lesystem)
rm { ReadOnly Mountable
wu { Writeable Unmountable (ie: swap)
Networking
Show interfaces currently installed on system, speed, and duplex
dladm show-dev { (ndd can be used to adjust speed and duplex)
List network interfaces from the global zone only
ifconfig -aZ
Remove all host speci c con guration from the system (and restart)
sys-unconfig
Primary IP con guration les
/etc/hostname.interface
,! IP address for interface. Alternatively use ifconfig.
/etc/nodename
,! hostname for the system. Alternatively set with hostname.
/etc/defaultdomain
,! System domain name. (svcadm restart domain after change)
/etc/defaultrouter
,! gateway for the system. Alternatively set with route.
/etc/hosts
,! Linked to /etc/inet/hosts. For IPv4 addresses only.
/etc/inet/ipnodes
,! For IPv4 and IPv6 addresses. Should be in sync with hosts le.
/etc/netmasks
,! This is not a symlink to /etc/inet/netmasks.
Temporarily set IP address on hme0
ifconfig hme0 plumb up 192.168.1.17 netmask 255.255.255.0
Temporarily create an alias on hme0 (hme0:1)
ifconfig hme0:1 plumb up 192.168.1.18 netmask 255.255.255.0
Create permanent alias on hme0 interface
echo 192.168.1.18 > /etc/hostname.hme0:1
Temporarily set the default route
route add default 192.168.1.1
Permanently add the same route as above
echo 192.168.1.1 > /etc/defaultrouter
Turn o tra c on qfe3
ifconfig qfe3 down
Disable an Ethernet device (qfe3)
ifconfig qfe3 unplumb
List statistics on all interfaces on system
netstat -i
List all open ports on system
netstat -an | grep LIST
List all open TCP connections
netstat -f inet
Continuously ping a host
ping -s www.tablespace.net
Use the snoop command to capture network packets
User Management
Add a user wfavorit to system (& create home dir) using default options
useradd -m wfavorit
View the default settings for the useradd command
useradd -D
Change the default useradd setting for base directory
useradd -D -b /export/home
Delete the password for user wfavorit, force new password on login
List all user accounts that do not have passwords
logins -p
List le system usage of the /zones lesystem by user
quot /zones
Display login information for wfavorit
logins -x -l wfavorit
Change the default shell to ksh for user wfavorit
usermod -s /usr/bin/ksh wfavorit
Modify user accounts with usermod and delete accounts with userdel.
Create group accounts with groupadd, modify group accounts with
groupmod, and delete groups with groupdel.
Service Management Facility
List all services known to system and current status
svcs -a
Enable the webmin service (long FMRI)
svcadm enable svc:/application/management/webmin:default
Disable the webmin service (short name)
svcadm disable webmin
List details of the ssh(d) service
svcs -l ssh
Restart the ssh(d) service
svcadm restart ssh
Verify that the AutoFS service is running
svcs system/filesystem/autofs
Verify that the multiuser server milestone has been reached
svcs multi-user-server
Disable the telnetd service (Use -e for enable)
inetadm -d telnet
List services that the multi-user-server milestone is dependent on
svcs -d multi-user-server
List services that depend upon multi-user-server milestone
svcs -D multi-user-server
Files
/etc/vfstab { Filesystem mount table
/var/adm/loginlog { Log of login attempts
/etc/default/* { Important default settings
/etc/system { Kernel modules and con g
/var/adm/messages { Syslog location
/etc/auto * { Automounter con g les
/etc/inet/ipnodes { IPv4 & v6 host le (read before /etc/hosts)
Inspecting the system
Find the total physical memory in system
prtconf | grep Memory
Find the openboot rmware version
prtconf -V
List information on all processors in the system
psrinfo -v
Find the size of a disk
iostat -En (or use the format command)
Display info on dump device
dumpadm
List all swap devices
swap -l
Show swap usage
swap -s (Includes physical memory)
Show swap size (per device)
swap -l|grep -v swaplo|awk 'f print $1, $4/2048 "m"g'
Show swap used (per device)
swap -l|grep -v swaplo|awk 'f print $1, ($4-$5)/2048 "m"g'
Show information about a binary (bash in this example)
showrev -c /usr/bin/bash
List time of most recent reboots
last reboot

solaris qucik sheet

2009-04-15T02:32:00.000-07:00

solaris certification questions dump

2009-04-15T02:31:00.000-07:00

1) What two commands will display installed patches (choose 2)?

patchadd -p
uname -p
pkginfo -p
showrev -p

The 'showrev -p' and 'patchadd -p' commands show the current list of installed patches. 'pkginfo -p' displays information about partially installed packages, and the uname -p command is for displaying information about the current system.

2) The system currently has a umask value of 022. What effect will this have?

all directories will be created with the sticky bit
new normal files will be created with 644 permissions
new normal files will be created with 755 permissions
all files and directories will be created with 644 permissions

The umask is set in /etc/default/login and is used to determine the file permissions for newly created files. For newly created directories, the directory's permission is determined by subtracting the umask from 777, which means directories would have 755. Files subtract the umask from 666, which means they'd start out with 644.

3) When using FTP to download files, what option is used to turn off prompting when using mget?

-y
noprompt
-i
noask

The '-i' option is used when starting FTP to turn off interactive prompting for multi-file downloads. The other options are made up and do not exist.

4) What directory contains the path_to_inst file?

The 'path_to_inst' file is located in the /etc directory. The path_to_inst file records mappings of physical device names to instance numbers.

There are five Solaris 8 installation clusters for Sparc, and only four for Intel. Which one of the following exist for Sparc, but not Intel?

entire distribution plus OEM
developer system support
entire distribution
end-user

The Intel version does not include the "entire distribution plus OEM" software group.

5) What vi command will replace all instances of "Sun" in the current file with Sun Microsystems?

:r /Sun/Sun Microsystems/g
:s /Sun Microsystems/Sun/g
:%s /Sun/Sun Microsystems/g
:%r /Sun/Sun Microsystems/g

The answer is ':%s /Sun/Sun Microsystems/g'. When doing substitution in vi, you use either :s or :%s. :%s actually checks the whole file instead of the current line. The 'g' at the end indicates that this is a 'global' operation, which means that instead of replacing the words one at a time, it'll go through the file and make them all at once. The word to be replaced is specified first, and then the word(s) to replace it with.

6) How do you pass the '-r' option to the PROM boot command?

reboot -- -r
reboot -r >> boot
reboot -r | boot
no way to pass between OS & PROM

This is not a well known fact. Options can be passed to the PROM boot command using the 'reboot' command. The answer is 'reboot -- -r'. This would pass the -r option to the boot command, which would result in a boot -r (reconfiguration boot).

7) You just installed the SUNWypr package. How would you verify that it installed correctly?

showrev -v SUNWypr
pkginfo -v SUNWypr
pkgadd -v SUNWypr
pkgchk -v SUNWypr

The 'pkgchk' command is used to verify that a package is installed correctly. 'pkginfo -v' would be used to check the version, there is no -v option for showrev, and pkgadd -v is for tracing the scripts that get executed by pkgadd.

8) What subcommand of the format utility will provide information such as the disk manufacturer, product, and revision?

inquiry
select
label
print

The 'inquiry' menu option shows the vendor, product, and revision. 'label' saves the current disk label, 'select' is for selecting a saved disk label, and 'print' shows the current partition table.

9)Which of the following commands would allow you to make a level 5 dump on the default tape device and verify it--/dev/rmt/0n?

ufsdump 5fv /dev/rmt/0n
ufsdump -l 5 -v >> /dev/rmt/0n
ufsdump -lv 5 default
ufsdump -l 5 -v -f /dev/rmt/0n

'ufsdump 5fv /dev/rmt/0n' is the correct answer. Anything involving redirection in ufsdump is most likely a bogus answer. The 'l' option is for autoload, and has nothing to do with picking an incremental dump level.

10)Using grep, what command will search all files in the current working directory for all lines beginning with "A"?

grep "^A" *
grep * "$A"
grep * "^A"
grep "$A" *

To search all files in the current directory for "A", you would use 'grep "^A" *'. You specify the regular expression being used to search the files, in this case ^A, which indicates that the A needs to be at the beginning of the line.

11)What command creates logical links under the /dev directory which point to the corresponding special files under /devices?

drvconfig
diskscan
mkdskf
disks

The 'disks' command creates the links that point from /dev to the special files located under /devices. The files located under /devices are actually created by 'drvconfig'. The other two commands were made up.

12) Which three characters will take you to command mode from last line mode?

$
:
?
/

The colon, slash, and question mark all take you into last line mode. The dollar sign keeps you in command mode, and merely takes you to the end of the current line.

13) What command is similar in syntax and function to tar, except that it compresses files before creating the archive?

The answer is "gzip". The important thing to realize here is that tar combines everything into an archive, but it does not compress the files.

14) What PROM command allows you to remove a device alias?

devunalias
unset
nvunalias
unalias

The 'nvunalias' command allows you to remove a device alias. The 'unset' command is used from the shell to destroy variables. The 'unalias' and 'devunalias' commands do not exist.

15)Which of the following commands result in file compression? Choose three.

zcat
gzip
jar -c
compress

The 'zcat' command is used to uncompress a .Z file to standard output. The other three commands compress the contents of the files they are executed on. Just in case tar is an option on the actual exam, keep in mind that tar does not compress files, it merely bundles them up in an archive.

16)Given the following line from the process table listing:
root 4425 1381 0 17:07:40 ? 0:00 in.rlogind

How would you kill the in.rlogind process?

The 'PID' (process ID) is the first number in the line for that process in the process listing. In this case, the process ID is 4425, so to kill it, we could type kill 4425, or kill -9 4425. Simply typing 'kill 4425' would send the process the default signal, which is SIGTERM. This is not as powerful as the '-9' (SIGKILL) signal, which is the 'merciless' way of killing a process.

17)Which option to the useradd command will allow you to use a duplicate userid (i.e. -z)?

The '-o' option to the useradd allows a nonunique user id to be used. It is also available for usermod, groupadd, and groupmod. In the group commands, it allows duplicate group ids.

18)Which of the following is true about Solaris shells?

default root shell is ksh
spawned processes always run in the ksh shell
default shell for normal users is Bourne
C programmers must use csh

The answer is 'the default shell for normal users is Bourne'. Root's default shell is also bourne, not ksh. C programmers are not limited to csh; as a matter of fact, limitations in csh mean they often prefer not to use csh. Spawned processes do not always run in a specific shell; it depends on the shell specified for that particular script--otherwise Bourne is used.

19)Which of the following mount commands would not allow files larger than 2 GB to be created?

mount -o limit=2
mount -limit 2
mount -o nolargefiles
mount -o largefiles

The correct answer is 'mount -o nolargefiles'. 'mount -o largefiles' would allow files larger than 2 GB, and the other two answer choices are totally bogus.

20)A user is running csh, and his user directory is /home/bsmith. Which of the following configuration files would be read by csh during the boot and login process? (choose three)

/home/bsmith/.cshrc
/home/bsmith/.login
/etc/login
/etc/.login

CSH would read the /etc/.login, /home/bsmith/.cshrc, /home/bsmith/.login files if they all exist. There is no /etc/login file.

21)You want to perform a backup of filesystem /export/home on the local system. The backup device is located on host Mars and is /dev/rmt/0. What command do you run?

ufsdump 0f mars:/dev/rmt/0 -i /export/home
ufsdump 0c if=/export/home of=mars:/dev/rmt/0
ufsdump 0h mars /export/home
ufsdump 0f mars:/dev/rmt/0 /export/home

The answer is 'ufsdump 0f mars:/dev/rmt/0 /export/home'. When you reference a remote file, you specify the hostname:/filename. The same applies to a remote device. The '0' in 0f indicates that this is a level 0 dump being performed.

22)How do you view ACLs?

showfacl
getacl
getfacl
lsacl

The only real-life command out of the four choices is 'getfacl'. The ACL commands all end in 'facl'. The other 3 choices are all made up.

23)Which of the following commands will take you from command mode to edit mode in VI? (select 3)

I
g
a
A

The 'A', 'a', 'I' would all take you to insert mode. Other keys that will take you to insert mode are 'i', 'o', and 'O'.

24)Which of the following commands give the current run-level?

uname -r
init -r
who -r
last -r

The 'who -r' gives the current run level. 'uname -r' gives the OS revision level, and 'init -r' and 'last -r' give errors because there is no '-r' command for the init and last command.

25)Here are a few files located in rc0.d.
K50utmpd K55syslog K73volmgt
What do the 2 digits after the K indicate?

they do not indicate anything--each script merely requires a unique 2 digit number
They are equal to the PID of the script
they indicate the max number of spawned processes for that script
They indicate priority--what order the scripts will be run

These files are known as sequencer files. The two-digit numbers determine the order in which these scripts are executed. The lowest is run first, the highest number is run last. This is because certain scripts often require other scripts to be run before they can function.

26)Which of the following can you set during a customized install? Choose two.

filesystem layout
user disk quotas
printers
64-bit capability

User disk quotas and printers cannot be set up during a customized install. The answers are '64-bit capability' and 'filesystem layout'.

27)How would you remove the patch 105361-08?

patchadd -d 105361-08
patchdel 105361-08
patchrm 105361-08
patchinfo -d 105361-08

The 'patchrm' command is used to remove patches. Type 'patchrm 105361-08' to remove the 105361-08 patch. Please remember that the '-d' option to the patchadd command is used to make the patching process irreversible, by not creating backups of the files before they were patched. There is no patchinfo or patchdel command.

28)You have an account on host A and host B. How can you download a file from Host A while logged in on Host B without supplying a password?

add host A to your $HOME/.rhosts file on host B
add host B to your $HOME/.rhosts file on host A
have superuser modify the rusers file
add your username to /etc/hosts.equiv

The .rhosts file allows you to specify remote hosts from which a password is not required. The answer is 'add host B to your $HOME/.rhosts file on host A'. To explain this, let's use user bsmith. Adding host B to the .rhosts file in bsmith's home directory on host A means that whenever bsmith tries to use rcp or another 'r' command from host B on host A, he is not asked for a password.

29)Which of the following commands accept the -o option to allow a duplicate userid or group id to be used (select three)?

usermod
adduser
groupadd
useradd

The '-o' option allows duplicate user ids, or group ids to be used. The useradd, usermod, groupadd, and groupmod commands allow this. The adduser command does not exist.

30)What file must be modified to turn on ufs logging automatically for a filesystem when it is mounted?

The logging option must be added to the /etc/vfstab file to enable ufs logging for a filesystem.

31)Which subcommand for the partition menu under the format command loads a predefined label?

The 'select' command loads a predefined label.

32)Which of the following subcommands, from the initial menu for the format command, allows you to select a different disk?

new
disk
menu
current

The 'disk' command from the format menu is used to select a different "current disk". The 'new' command does not exist, and current describes the current disk. The 'menu' command also does not exist.

33)What option to the PROM boot comand is for reconfiguring your device tree?

You would type 'boot -r' to cause the system to boot up, and reconfigure the device tree, so the answer is '-r'. Another way to have the device tree reconfigured, is to type 'touch /reconfigure' from the shell, and then reboot.

34)What does the hash command in FTP result in?

a hash is printed when a block is written during a file transfer
the hash table is updated whenever a file transfer is made
it activates the "hash hotkey"
all transfer requests are stored and transferred in batches

The 'hash' command is a simple command for ftp that results in a hash (#) being printed every time one block of the transfer is complete. A block is typically 1024 bytes in FTP transfers.

35)What subcommand of the format utility will take you to the menu for making partition label changes?

The 'partition' subcommand of the format utility takes you to the partition menu, where you can change the current partition label configuration.

36)What command allows you to change your primary group?

The 'usermod' command allows you to change user information, to include their primary group. Keep in mind that the 'newgrp' command allows you to switch your "current group" temporarily, but does not affect what your primary group is.

37)You see a system administrator reboot one of the servers and then walk away, but all you catch is that he used the "shutdown" command. When you come back later, it is sitting at the ok prompt. What run-level did he shutdown to?

Shutting down to run level 0 is halting the system, and the end result is an ok prompt, so the answer is 0. Run level 5, which is often confused with run level 0, is power-down. Run level 6 would be for rebooting.

38)Which two characters allow you to move up and down in VI?

l
j
k
h

The 'j' and 'k' characters allow you to move 'down' and 'up' respectively. The 'h' and 'l' keys are used to move left and right.

39)What command would provide a list of the contents of the archive abc.tar without extracting the files?

tar cvf abc.tar
tar xvf . abc.tar
tar tvf . abc.tar
tar tvf abc.tar .

The 't' option to the tar command means 'table of contents'. This results in the contents of the file being displayed, instead of any action being taken on the file. The tar file must be specified first, and then the location, in this case '.' (the current directory). The answer is 'tar tvf abc.tar .'.

40)Consider the following command:
#chmod 2666 telephone
Choose 2 answers that are correct.

the assigned group has write permission for telephone
the telephone file is locked
no one has execute permission for telephone
setgid is enabled on telephone

The file "telephone" has been assigned octal permissions of 2666, which means setgid is set, and the assigned rights are read and write for everyone. We know setgid is set because 4000 represents setuid, 2000 represents setgid, and 1000 represents sticky bit. If setgid is set, that means that whenever this command is executed, it is executed as if it had been executed by the group which owns the file. Setuid would mean that it is executed as if the user who owns the file ran it.

41)How do you copy a local file to remotehost?

rcp localfile remotehost
rcp localfile remotehost:/filename
rcp localfile remohost/filename
rcp localfile remotehost:filename

When referencing remote files, use the format hostname:/filename. In this case, the correct answer would be 'rcp localfile remotehost:/filename'.

42)What command would extract the file my.file from the archive abc.tar?

tar xvf my.file abc.tar
tar xvf abc.tar my.file
tar tvf my.file abc.tar
tar cvf abc.tar my.file

The 'x' option to the tar command means 'extract'. This results in the contents of the file being extracted to the specified location. The tar file must be specified first, and then the file being extracted. The answer is 'tar xvf abc.tar my.file'.

43)What vi command copies the next 3 lines and pastes them above the current line, assuming that you are on line 2?

3yyp
3yyP
:2,5m1
3mU

The 'yy' command is for cutting. 'p' is for pasting at the current line, and 'P' is for pasting above the current line.

44)Where do you specify default init level?

The default init level is specified in the /etc/inittab, which is a file that controls process dispatching by init.

45)What command would restore a backup created with ufsdump from the default tape device?

ufsrestore cvx /dev/rmt/0n
ufsrestore << /dev/rmt/0n
ufsrestore -I /dev/rmt/0n
ufsrestore f /dev/rmt/0n

the 'ufsrestore f /dev/rmt/0n' command would be the correct choice. Redirection is not used with ufsrestore. The ufsrestore command is a fairly complex command, and it is recommended that you at least read the man page for it.

46)There is a cdrom connected to controller 0. Which of the following commands would mount the cdrom on mount point /mnt, assuming that the volume management daemon is not running?

mount /dev/dsk/c0t2d0s0 /mnt
mount cdrom /mnt
mount -F cdfs /dev/dsk/c0t6d0s0 /mnt
mount -F hsfs /dev/dsk/c0t6d0s0 /mnt

The answer is "mount -F hsfs /dev/dsk/c0t6d0s0". There are two important things to note here:
CD-ROM access in Solaris uses the HSFS (High Sierra File System) file system.
the CD-ROM is typically given a target address of 6, hence c0t6d0s0

47)Consider the following listing:
#ls -ld
drwxrwsrwx 2 root other 512 Aug 24 2000 test1
Which of the following would remove the setgid?

chmod 0777 telephone
chmod g-s telephone
chmod g-l telephone
chmod 0000 telephone

Looking at this listing, we see that there is an 's' where the 'x' bit for group permissions would normally be set. This tells us that setgid is turned on for this file. Setgid can be added using octal permissions (a value of 2000), but it can only be removed using symbolic permissions. Therefore, the correct answer is chmod g-s telephone. Please note that removing sticky bit or setuid does not have the same limitation.

48)Which of the following commands would you use to create a filesystem using a raw device?

newfs -r c0t0d0s0
newfs /dev/rdsk/c0t0d0s0
newfs /dev/dsk/c0t0d0s0
newfs c0t0d0s0,raw

First of all, newfs requires a raw device. Secondly, raw devices can be identified by their path; they are located in the /dev/rdsk directory. The correct answer is "newfs /dev/rdsk/c0t0d0s0"

49)Which two of the following commands would provide online information about /etc/vfstab?

man -s4 vfstab
man vfstab (5)
man /etc/vfstab
man vfstab

The two correct answers for this question are "man vfstab" and "man -s4 vfstab". 'man /etc/vfstab' would produce no result. Typing 'man -s4 vfstab' would result in the section 4 manpage for vfstab to be loaded. 'man vfstab (5)' is incorrect syntax for specifying the section.

50)What does the noatime option result in when set in the vfstab file?

access time for the file is not modified when the file is read
no restrictions are allowed on when files can be accessed
users cannot change the "last modified" time for a file
it does not allow file-read requests to be interrupted

The 'noatime' option is short for 'no access time' and means that access time for the file is not modified when a file from that filesystem is read.

51)The system is now at the boot prompt due to an interrupt. What command do you run to minimize file system damage?

fsck
sync
boot -r
park

The 'sync' command insures that all file modifications made up to that point are saved to the disk, by flushing all previously unwritten system buffers to disk. 'fsck' is used to diagnose bad disks, park is not a standard solaris command, and 'boot -r' is run when you want to reconfigure the device tree.

52)You want to put all files which were modified in the past 7 days into an archive on /dev/rmt/3. Which of the following cpio commands would do that?

cpio -icdB < /dev/rmt/3
find / -mtime -7 -cpio /dev/rmt/3
find . -cpio /dev/rmt/3
ls -lta | cpio -o 7 > /dev/rmt/3

Please be advised that the cpio command is a fairly complicated command, and you may want to do some reading on it. The correct answer in this case is find / -mtime -7 -cpio /dev/rmt/3. The find command looks for files with a modification time within the last 7 days, and then passes that on to cpio for archival.

53)What type filesystem would you specify when mounting an msdos floppy?

dosfs
fdfs
ufs
pcfs

To mount an MS-DOS floppy, you would use 'pcfs'. UFS is for hard disks, and 'dosfs' and 'fdfs' do not exist.

54)What is the default signal that is sent to the in.telnetd process when pkill is run on it?

TERM
HUP
INT
KILL

The default signal sent by either the kill or pkill command is TERM, also referred to as SIGTERM, or represented by a -15.

55)What single character represents zero or more characters in a regular expression?

In regular expressions, the '*' (asterisk) represents 0 or more characters.

56)Which subcommand for the partition menu under the format command allows you to modify the partition label and prompts you a slice at a time?

label
modify
select
customize

The 'modify' command allows you to modify a disk label, and it will prompt you for a slice at a time. The 'select' command is for loading a saved label, 'label' is for saving the current partition table, and 'customize' does not exist on the partition menu.

Introduction of Blog

2009-04-15T02:27:00.000-07:00

These blog is all for the people who looks for preparation material for certification in solaris ,veritas and also for the people who are looking for guidance and interview questions regarding these fields.Most of the posts have been taken from various sites.The purpose here is not coping the things,but to make all the things available at one place.