10-10-2002
SAM executes a number of commands on the kernel (/stand/vmunix) to produce the output for the "Configurable Parameters" window. One of these steps may be failing on your server.
The best way to see what SAM is doing is to execute /usr/sam/bin/samlog_viewer -l C /var/sam/log/samlog. This will open a window which extracts the commands executed by SAM. Scroll to the bottom to see what it was doing when it attempted to list the "configurable Parameters" and hopefully it will give you clue as to where it is failing.
SAM does run a number of executables such as kmadmin, kmsystem, kmtune and get_sysfile - some of these on temporary files it creates. One of these may be failing, or it may be failing to generate a temporary file.
7 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I am having a problem on an HP box, where I am being told that there are too many open files. I am also being told I need to change a SAM file. Could some help me understand what a SAM files is and what it is used for.
Thanks. (2 Replies)
Discussion started by: kristian
2 Replies
2. HP-UX
hi, any idea how to get more info on the usage, unix equivalent of sam in hp-ux? thanks (7 Replies)
Discussion started by: yls177
7 Replies
3. UNIX for Advanced & Expert Users
I am having trouble getting restricted SAM to work by allocating Privileges to a "group". I can make it work by allocaing to the userid's, but would preferre to use the "group" option.
Running B.11.11
Tried the following....
1) Created a user group in /etc/group first
2) Used the... (1 Reply)
Discussion started by: Andrek
1 Replies
4. AIX
Hello,
On Aix 5.2, we changed the parameters tcp_keepinit, tcp_keepintvl and tcp_keepidle with the no command.
tunrestore -R is present in inittab
in the directory /etc/tunables we can clearly see the inclusion of parameters during reboot, including the file lastboot.log
... (0 Replies)
Discussion started by: dantares
0 Replies
5. UNIX for Dummies Questions & Answers
#!/bin/bash
function check_num_args()
{
if ; then
echo "Please provide a file name"
else
treat_as_file $*
fi
}
function treat_as_file()
{
numFiles=$#
for((i=1;i<=$numFiles;i++));do
echo $i
... (3 Replies)
Discussion started by: kikilahooch
3 Replies
6. Programming
I have
written some C++ code with documentation code for dOxygen as below. However the parameters are not showing up.
/// \file
///
///
#ifndef __VECT2_HH__
#define __VECT2_HH__
#include <iostream>
#include <assert.h>
#include <cmath>
#include "common.hh"
... (0 Replies)
Discussion started by: kristinu
0 Replies
7. HP-UX
I've just been on an HP Training Course for HPUXv11.31 and found out about the gui / web for SMH. I never did a course on HP11v23. On our two servers here in the UK that run 11.23 I'm pretty sure that when I typed in "sam" on the command line it went to a sort of smh. (There was a message saying... (2 Replies)
Discussion started by: markp1965
2 Replies
LEARN ABOUT SUSE
sg_reset
SG_RESET(8) SG3_UTILS SG_RESET(8)
NAME
sg_reset - sends SCSI device, bus or host reset; or checks reset state
SYNOPSIS
sg_reset [-b] [-d] [-h] [-V] DEVICE
DESCRIPTION
The sg_reset utility with no options (other than DEVICE) reports on the reset state (e.g. if a reset is underway) of DEVICE. When given a
-d, -b, or -h option it requests a device, bus or host reset respectively.
In the linux kernel 2.6 series this utility can be called on sd, sr (cd/dvd), st or sg device nodes; if the user has appropriate permis-
sions.
In the linux kernel 2.4 series support for this utility first appeared in lk 2.4.19 and could only be called on sg device nodes. Various
vendors made this capability available in their kernels prior to lk 2.4.19.
OPTIONS
-b attempt a SCSI bus reset. This would normally be tried if the device reset (i.e. option -d) was not successful.
-d attempt a SCSI device reset. If the device seems stuck, this is the first reset that should be tried. This assumes the linux scsi
mid level error handler is not already in the process of resetting DEVICE.
-h attempt a host adapter reset. This would normally be tried if both device reset (i.e. option -d) and bus reset (i.e. option -b) were
not successful.
-V prints the version string then exits.
NOTES
The error recovery code within the linux kernel when faced with SCSI commands timing out and no response from the device (LU), first tries
a device reset and if that is not successful tries a bus reset. If that is not successful it tries a host reset. Users of this utility
should check whether such a recovery is already underway before trying to reset with this utility. The "device,bus,host" order is also rec-
ommended (i.e. first start with the smallest hammer).
SAM-4 defines a hard reset (which includes a device power on and a transport reset), a logical unit reset and a I_T nexus reset. A LU reset
and an I_T nexus reset can be requested via task management function (and support for LU reset is mandatory). In Linux the SCSI subsystem
leaves it up to the low level drivers as to whether a "device reset" is only for the addressed LU or all the LUs in the device that con-
tains the addressed LU. The "bus reset" is a transport reset. A "host reset" attempts to re-initialize the HBA that the request passes
through on route to the DEVICE. Obviously a "host reset" and a "bus reset" can cause collateral damage.
This utility does not allow individual SCSI commands (or tasks as they are called in SAM-4) to be aborted. SAM-4 defines ABORT TASK and
ABORT TASK SET task management functions for that.
AUTHORS
Written by Douglas Gilbert.
COPYRIGHT
Copyright (C) 1999-2006 Douglas Gilbert
This software is distributed under the GPL version 2. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PUR-
POSE.
sg3_utils-1.23 December 2006 SG_RESET(8)