10 More Discussions You Might Find Interesting
1. Hardware
Hi all,
I have some problems with the fan FT0.F0, which looks like has a problem with the PROM/ALOM ( I am nor sure who).....but, in fact, the fan is working properly even in other V440 Sparc Server.
We checked HW comunication between Fan and the MotherBoard, and we think is a problem of... (8 Replies)
Discussion started by: proof_enrique
8 Replies
2. Solaris
Hi,
How to set ip address on eth0 for access ssh from ALOM? Is it possible? Now i cannot access it because don't have VGA.
I keep try to access using ssh. Please guide me.
Thanks. (16 Replies)
Discussion started by: mzainal
16 Replies
3. Solaris
Hi guys,
I'm new with solaris.
I just received sunfire T2000 server.
Problem:
ALOM keep hang/stuck/jammed.
Steps do before it hang :
1. Connect to T2000 (using RJ45 - DB9 cable)
2. Open putty, connect via serial.
3. Power on the server.
4. Its loading.
5. then, hang.
... (1 Reply)
Discussion started by: rajasraf
1 Replies
4. Solaris
Hello forum,
I have a SUN v250 at home that I have to practice Solaris. I currently have Solaris 9 installed and the ALOM Sun(tm) Advanced Lights Out Manager 1.5.2.
From the ALOM I want to access the console.
sc> console -f
Enter #. to return to ALOM.
after that there is no response.... (19 Replies)
Discussion started by: br1an
19 Replies
5. Solaris
Hi gurus,
I have a sun netra 240 server. I want to get to the ALOM but it always ask for login and password. Can anyone tell me how I can reset the ALOM it to default so I can be able to configure it?
Thanks lots. (2 Replies)
Discussion started by: cjashu
2 Replies
6. Emergency UNIX and Linux Support
Hi guys!
I need to upgrade the fw version of some T2000 servers, but unfortunately the image downloaded from the Oracle does not work...it seems that the image is not supported on the platform..
bash-3.00$ uname -a
SunOS adm01 5.10 Generic_141414-07 sun4v sparc SUNW,Sun-Fire-T200... (5 Replies)
Discussion started by: cecco16
5 Replies
7. Solaris
Hi guys,
I'm in trouble with a Sunfire T2000.
The OS (Solaris10) is up and running, but I can't log in the sc>I think the terminal server is crashed!
Does anyone know if I can reset the sc> from the OS?
How can I do that?
Thx (6 Replies)
Discussion started by: cecco16
6 Replies
8. Solaris
hello guys.... I'm newbie in solaris server / os, anybody know how disable alom server v240.
thank u (9 Replies)
Discussion started by: yanto85
9 Replies
9. Solaris
Hello Guys,
I am working with sunfire V480 and wants to know how to connect to alom. Can you please guide? (7 Replies)
Discussion started by: mokkan
7 Replies
10. UNIX for Advanced & Expert Users
No, its not a movie, its a command to get you from the sc> ALOM prompt back to the console or ok prompt.
You must log into the ALOM, then to jump back to the console enter "console -f".
Problem is that this leaves you logged in on the ALOM.
Question: is there an escape key sequence to get... (1 Reply)
Discussion started by: jsy
1 Replies
SG_RESET(8) SG3_UTILS SG_RESET(8)
NAME
sg_reset - sends SCSI device, target, bus or host reset; or checks reset state
SYNOPSIS
sg_reset [-b] [-d] [-h] [-t] [-V] DEVICE
DESCRIPTION
The sg_reset utility with no options (just a DEVICE) reports on the reset state (e.g. if a reset is underway) of DEVICE. When given a -d,
-t, -b or -h option it requests a device, target, bus or host reset respectively.
The ability to reset a SCSI target (often called a "hard reset" at the transport level) was added in linux kernel 2.6.27 . Low level driv-
ers that support target reset hopefully reset a logical unit only when given the device reset (i.e. -d) option. This should removed the
ambiguity of whether "device" meant LU or target that we have had in the past.
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.
-t attempt a SCSI target reset. This assumes the linux scsi mid level error handler is not already in the process of resetting the tar-
get that contains the given DEVICE.
-V prints the version string then exits.
NOTES
The error recovery code within the linux kernel when faced with a SCSI command timing out and no response from the device (LU), first tries
a device reset and if that is not successful tries a target reset. If that is not successful it tries a bus reset. If that is not success-
ful 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,target,bus,host" order is also recommended (i.e. first start with the smallest hammer). The above is a generalization
and exact details will vary depending on the transport and the low level driver concerned.
SAM-4 defines a hard reset, a logical unit reset and a I_T nexus reset. A hard reset is defined to be a power on condition, a microcode
change or a transport reset event. 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 contains the addressed LU (i.e. a target reset). The additional of the target reset (i.e.
option -t) should give more control in this area. The "bus reset" is a transport reset and may be a dummy operation, depending on the
transport. A "host reset" attempts to re-initialize the HBA that the request passes through en route to the DEVICE. Note that a "host
reset" and a "bus reset" may 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.
Prior to SAM-3 there was a TARGET RESET task management function. Several transports still support that function and many associated linux
low level drivers map the -t option to it.
AUTHORS
Written by Douglas Gilbert.
COPYRIGHT
Copyright (C) 1999-2009 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.28 July 2009 SG_RESET(8)