Sponsored Content
Full Discussion: SunFire T2000 ipmievd error
Operating Systems Solaris SunFire T2000 ipmievd error Post 302524885 by hergp on Wednesday 25th of May 2011 02:52:04 AM
Old 05-25-2011
Niagara Servers starting with the T5xxx series are equipped with ILOM - first as alternative to ALOM, then, since the T3 systems arrived, ILOM is the only management interface. Maybe Netra T2000 are equipped with ILOM too (found some references). The original T2000 only supports ALOM.
 

10 More Discussions You Might Find Interesting

1. Solaris

Network Path Not Found Error "Sunfire V100"

I recently got this new old server from a friend. I just installed a fresh version of Solaris 10 on it. I have put a static IP of 192.168.100.10 the server. Their is no subnetting scheme on the network. And I made the hostname "SunServ." And I also changed the folder "/etc/inet/hosts" because I... (4 Replies)
Discussion started by: louisd11
4 Replies

2. Solaris

Resolution error sunfire v245

Hi all, I am getting the below error on Solaris sunfire v245 server Error: can not display this video mode optimum resolution 1024x768 60Hz i am not able to resolve this .plz help me out ? (1 Reply)
Discussion started by: saurabh84g
1 Replies

3. Solaris

T2000 - Fault at MB/FF_POK

Hi all, I have a T2000 server which does not seem to respond when I power it on. Looking on the console I see the following: SC Alert: Host Power Failure: MB_DC_POK Fault SC Alert: Host system poweron failed due to fault at MB/FF_POK. SC Alert: VOLTAGE_SENSOR at MB/V_VCORE has exceeded... (4 Replies)
Discussion started by: jambalaya
4 Replies

4. Solaris

T2000 Hardware RAID

Hi, I have a root with hardware RAID on c0t0d0 and c0t2d0. I would like to set the boot device sequence in OBP for both hdds. I have checked in ls -l /dev/rdsk/ for the path of c0t2d0 but it does not exist. Can anyone shed some lights on this? AVAILABLE DISK SELECTIONS: 0.... (12 Replies)
Discussion started by: honmin
12 Replies

5. Solaris

Error while trying to boot from cdrom on Sun Fire T2000

Hi Guyz, I recently downloaded sol-10-u6-ga1-sparc-dvd.iso from Sun. I burned the disk as cd .iso. When trying to boot at the ok> boot cdrom i get the following error: ----------------------------------------------------------------------- Boot device:... (2 Replies)
Discussion started by: Mwamba
2 Replies

6. Solaris

SunFire V890 error -256 when boot

Hi all! I've a machine - SunFire V890, it've been failed by OS error for 2 weeks ago, and now, I must reinstall OS (Solaris 10 2009), the progress was successful, but when I reboot, it displayed the error like : Error -256: Last trap memory ... access aligned Error -256: Last trap memory... (1 Reply)
Discussion started by: trantuananh24hg
1 Replies

7. Solaris

Memory problems on a -sunfire T2000

I work with a network management tool, which, for various reasons, is installed on a solaris server.This is a Sunfire T2000 server with 16 CPUs and 8GB of RAM. I have installed a Solaris 10 ZFS and 8GB swap. From the beginning I had problems with memory occupation that it rises progressively to 95%... (4 Replies)
Discussion started by: drusa79
4 Replies

8. Hardware

Fan Tray for Sunfire T2000

Recently the rear fan assembly of one of our T2000 servers went faulty. I could replace it immediately with the one from a currently powered off standby machine. But now this one has to be replaced. So I got a quote from our supplier who charges EUR 776 for a new spare part or EUR 405 (all... (0 Replies)
Discussion started by: hergp
0 Replies

9. Solaris

Sun T2000 error codes

I got a Power supply failure. I replaced the power supply and still got the error. Any ideas on what I should try next? (1 Reply)
Discussion started by: 642fiddi
1 Replies

10. Hardware

POST error on SunFire V245

I've recently bought an SunFire V245. 2x 2.5ghz x64 4gb ram 4x 73gb sas hdd and... an blinking 'Identifior led' (white) with 'Service led' (amber) simultaneously. It boots for +- 5 secs and then the error occurd. Things done: Removed all hdd. Switched cpu Switched/removed ram... (2 Replies)
Discussion started by: niswier2222
2 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)
All times are GMT -4. The time now is 03:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy