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
tsalarm(7D) Devices tsalarm(7D)
NAME
tsalarm - Alarm device driver
SYNOPSIS
tsalarm@0:ctl
DESCRIPTION
The tsalarm driver is a Multi-threaded, loadable non-STREAMS pseudo driver that manages ALOM alarms. The tsalarm driver provides an inter-
face through which alarm relays can be controlled on SUNW,Netra-240 and SUNW,Netra-440 platforms.
HARDWARE INTERFACE
The alarm hardware differs depending on platform. The Netra 240 and 440 platforms features four dry contact alarm relays which are
controlled by ALOM. You can set each alarm to "on" or "off" by using ioctl interfaces provided from the host. The four alarms are labeled
as "critical," "major," "minor," and "user." The user alarm is set by a user application depending on system condition. LED's in front of
the box provide a visual indication of the four alarms. The number of alarms and their meanings/labels may vary across platforms.
IOCTLS
The interface provided by the tsalarm driver comprises ioctls that enable applications to manipulate the alarm module. The alarm module is
accessed via two device nodes: i) /dev/lom and /dev/tsalarm:ctl.
The following ioctls are supported by the /dev/lom and /dev/tsalarm:ctl devices:
TSIOCALCTL - Turn an alarm on or off.
The argument is a pointer to the ts_aldata_t/lom_aldata_t structure. This structure is described below. alarm_no member is an integer
which specifies the alarm to which the command is to be applied. The alarm_state/state structure member indicates the state to which
the alarm should be set (where 0 == off). An error (EINVAL) is returned if either an invalid alarm_no or invalid alarm_state is pro-
vided.
TSIOCALSTATE - Get the state of the alarms.
The argument is a pointer to the ts_aldata_t/lom_aldata_t structure. This structure is described below. alarm_no member is an integer
which indicates the alarm to which the command will be applied. The alarm_state member holds the alarm's current state and is filled
in by the driver. A zero indicates that the alarm is off. An error (EINVAL) is returned if an invalid alarm_no is provided. The struc-
tures and definitions for the values are defined below.
Alarm values:
The following old style values are defined in <lom.io.h>
#define ALARM_NUM_0 0 /* number of zero'th alarm */
#define ALARM_NUM_1 1 /* number of first alarm */
#define ALARM_NUM_2 2 /* number of second alarm */
#define ALARM_NUM_3 3 /* number of third alarm */
Alarm values defined in <lom.io.h>
#define ALARM_OFF 0 /* Turn off alarm */
#define ALARM_ON 1 /* Turn on alarm */
Alarm Data Structure:
This structure is defined in <lom.io.h>
typedef struct {
int alarm_no; /* alarm to apply command to */
int alarm_state; /* state of alarm (0 == off) */
} ts_aldata_t;
Use the following LOM interfaces to get and set the alarms. These definitions are included in <lom_io.h>
#define ALARM_CRITICAL 0 /* number of critical alarm */
#define ALARM_MAJOR 1 /* number of major alarm */
#define ALARM_MINOR 2 /* number of minor alarm */
#define ALARM_USER 3 /* number of user alarm */
The following alarm data structure is provided in <lom_io.h>:
typedef struct {
int alarm_no;
int state;
} lom_aldata_t;
ERRORS
An open() will fail if:
ENXIO The driver is not installed in the system.
An ioctl() will fail if:
EFAULT There was a hardware failure during the specified operation.
EINVAL The alarm number specified is not valid or an invalid value was supplied.
ENXIO The driver is not installed in the system or the monitor callback routine could not be scheduled.
EXAMPLES
How to set an alarm:
#include <sys/unistd.h>
#include <fcntl.h>
#include <stdio.h>
#include <lom_io.h>
#define LOM_DEVICE "/dev/lom"
int
main()
{
lom_aldata_t lld;
int fd = open(LOM_DEVICE, O_RDWR);
if (fd == -1) {
printf("Error opening device: %s0, LOM_DEVICE);
exit(1);
}
lld.alarm_no = ALARM_CRITICAL; /* Set the critical alarm */
lld.state = ALARM_ON; /* Set the alarm */
if (ioctl(fd, LOMIOCALCTL, (char *)&lld) != 0)
printf("Setting alarm failed");
else
printf("Alarm set successfully");
close(fd);
}
FILES
/dev/lom
LOM device.
/dev/tsalarm:ctl
Alarm control device.
/platform/platform/kernel/drv/sparcv9/tsalarm
Device driver module.
/platform/SUNW,Netra-240/kernel/drv/tsalarm.conf
Driver configuration file.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcarx.u |
+-----------------------------+-----------------------------+
|Architecture |SPARC |
+-----------------------------+-----------------------------+
SEE ALSO
attributes(5)
Writing Device Drivers
SunOS 5.11 16 Mar 2004 tsalarm(7D)