03-09-2013
With a /etc/hosts containing the same hostname twice, only the first entry will ever be used when the system searches to resolve a hostname.
That's why you have an ip address in the second hostname file.
This is very unusual.
You are definitely saying that both network interfaces were working a short while ago? Has the network switch been changed recently?
Or, has there been another change on the network that might have created a loop that the switch can see? This could be just a cable being moved or something elsewhere on your network.
I reckon that network conditions (loops???) are causing your switch to drop one of the Solaris interfaces.
Hopefully, I can get a second opinion on this forum from another Solaris networking expert. I can't think of much else it can be.
---------- Post updated at 08:55 PM ---------- Previous update was at 08:15 PM ----------
Here's an idea..........
If you've got a spare switch put each interface cable into different switches. Connect just a PC or something to the spare switch too.
See if you can ping the respective ip address from each "separate" network and also see if both interfaces stay up.
If the interfaces stay up then that pretty much eliminates the Solaris box as being the problem.
Last edited by hicksd8; 03-09-2013 at 05:32 PM..
This User Gave Thanks to hicksd8 For This Post:
10 More Discussions You Might Find Interesting
1. Solaris
Hi
I'm having a big trouble running a configuration tool (ftamtool) which uses xview on sunos 5.8, it refuses to start and says: XView error: could not load font 'FONT_FAMILY_SANS_SERIF...
How to force the program to use installed fonts and where are fonts installed available to use ?
... (0 Replies)
Discussion started by: andryk
0 Replies
2. IP Networking
I'm trying to plumb a new interface bge1 on my machine:
root@obms2-com-indianapolis-in:/root# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
bge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet... (3 Replies)
Discussion started by: R37ribution
3 Replies
3. Shell Programming and Scripting
I am looking to get a report on autosys jobs in RUNNING state b/w certain time frame (timeA and timeB).
What I am after is the list of all the jobs that ran between AND during timeA and timeB.
Jobs within the timeframe could either:
A: STARTING --> RUNNING --> SUCCESS/FAILURE etc..
B: ... (0 Replies)
Discussion started by: rgilan01
0 Replies
4. Programming
I am looking to get a report on autosys jobs in RUNNING state b/w certain time frame (timeA and timeB).
What I am after is the list of all the jobs that ran between AND during timeA and timeB.
Jobs within the timeframe could either:
A: STARTING --> RUNNING --> SUCCESS/FAILURE etc..
B: ... (0 Replies)
Discussion started by: rgilan01
0 Replies
5. Solaris
I am looking to get a report on autosys jobs in RUNNING state b/w certain time frame (timeA and timeB).
What I am after is the list of all the jobs that ran between AND during timeA and timeB.
Jobs within the timeframe could either:
A: STARTING --> RUNNING --> SUCCESS/FAILURE etc..
B: ... (2 Replies)
Discussion started by: rgilan01
2 Replies
6. Solaris
Hi all,
I encounter some problem with my e1000g interface running on sol 10. I can't permanently change the auto-nego to disable, if i use ndd commands, it will only stay until the next reboot.
But i can't change the link speed either is set to /etc/init.d/nddconfig or using ndd commands.
... (1 Reply)
Discussion started by: mailbox80
1 Replies
7. Solaris
hi frineds
in sunfire 6800 server for one domain when ever i am giving ifconfig -a interface names like hme0,hme1.......are not showing.Actually in the server hme0,hme1,qfe are showing .when i was tried with the cat /etc/path_to_intstshowing tphysical interfcace names .
after giving the... (2 Replies)
Discussion started by: tv.praveenkumar
2 Replies
8. AIX
Hi Admins,
I am having a whole system lpar in open firmware state on HMC.
How can I bring it to running state ?
Let me know. Thanks. (2 Replies)
Discussion started by: snchaudhari2
2 Replies
9. Solaris
on both of my T2000 I am seeing same values of 100Mbps for e1000g0 ethernet port.
i know all four ethernet ports on T2000 are gigabit ports so why is my first link showing as 100Mbps and how can i correct it?
# dladm show-dev
e1000g0 link: up speed: 100 Mbps ... (1 Reply)
Discussion started by: aliyesami
1 Replies
10. Solaris
Hi All,
Please let me know the step by step process to set the e1000g0 interface speed to 1000mbps with full duplex from 100fdx and how to disable the auto negotiation with switch?.
Thanks and Regards,
Ganesh. (7 Replies)
Discussion started by: gsrungav
7 Replies
LEARN ABOUT SUNOS
tsalarm
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.10 16 Mar 2004 tsalarm(7D)