11-06-2014
Yes it is a HP hardware. DL380
9 More Discussions You Might Find Interesting
1. Solaris
I setup RSC on a 280R using the network connection. Unfortunately, I am unable to telnet to this card and I was wondering if there was a way to test the link from the rsc card. Here is my rsc configuration:
machine1:/tmp/rsc# /usr/platform/SUNW,Sun-Fire-280R/rsc/rscadm show
page_enabled="false"... (0 Replies)
Discussion started by: dangral
0 Replies
2. UNIX for Dummies Questions & Answers
My system info is show below:-
#uname -a
SunOS qfserver 5.8 Generic_117350-29 sun4u sparc SUNW,Sun-Blade-2500
and I have two network card as shown below:-
#ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
bge0:... (1 Reply)
Discussion started by: sarifudin
1 Replies
3. AIX
Hello,
I need "devices.common.IBM.ml 1.4.0.0 C F Multi Link Interface Runtime" to be installed on my machine.
I need it for two SAN cards to work correctly.
Where do I get it ?
thanks
Vilius (1 Reply)
Discussion started by: vilius
1 Replies
4. Red Hat
Hi
I have installed OEL 4 on my dell XPS laptop. But when i connect the LAN cable and try to acesss internet. it does not work. the led's in the port do not blink when i plug in the cable .do i need some drivers please suggest.
Thanks
Ankur (2 Replies)
Discussion started by: ankurk
2 Replies
5. IP Networking
Hello,
I've been using mode 4 with four slaves, however looking at ifconfig showed that the traffic was not balanced correctly between the interfaces, the outgoing traffic has been alot higher on the last slave.
Example:
eth0 RX 123.2 GiB TX 22.5 GiB
eth1 RX 84.8 GiB TX 8.3 GiB
eth2... (3 Replies)
Discussion started by: TehOne
3 Replies
6. Solaris
I have system which is using a lot of bandwidth and this is not a big problem,
but how do you troubleshoot this issue?
How can I find out which connections are made for one interface card,
there are about 5 on this system and I can see how much traffic is going through one interface, but I need... (5 Replies)
Discussion started by: misterx12345
5 Replies
7. Solaris
Hi All
I am facing an issue with our new solaris machine.
in /var/adm/messages
root@Prod-App1:/var/tmp#
root@Prod-App1:/var/tmp#
root@Prod-App1:/var/tmp# cat /var/adm//messages
Apr 20 03:10:01 Prod-App1 syslogd: line 25: WARNING: loghost could not be resolved
Apr 20 08:24:18 Prod-App1... (0 Replies)
Discussion started by: javeedkaleem
0 Replies
8. Red Hat
Dear All ,
While taking backups in one Linux Server , we find one alert came with regard to Network Interface Card.
Pl find the below alert.
Network Interface Card performance for NIC:eth1 has exceeded Major threshold.
Bytes sent and received per second (Average)= 105540.303101... (6 Replies)
Discussion started by: jegaraman
6 Replies
9. Solaris
I'm looking for driver for SunSAI/P 3.0 (Serial Asynchronous Interface) card X2156A for Solaris. It used to be on sun-solve, but I fail to find it on the Oracle site. Any help would be very appreciated! (1 Reply)
Discussion started by: Ira28
1 Replies
LEARN ABOUT PLAN9
ddi_intr_get_supported_types
ddi_intr_get_supported_types(9F) ddi_intr_get_supported_types(9F)
NAME
ddi_intr_get_supported_types - return information on supported hardware interrupt types
SYNOPSIS
#include <sys/types.h>
#include <sys/conf.h>
#include <sys/ddi.h>
#include <sys/sunddi.h>
int ddi_intr_get_supported_types(dev_info_t *dip, int *typesp);
INTERFACE LEVEL
Solaris DDI specific (Solaris DDI)
dip Pointer to dev_info structure
typesp Pointer to supported interrupt types
The ddi_intr_get_supported_types() function retrieves the interrupt types supported by a particular hardware device and by the system soft-
ware. Upon successful return, the supported types are returned as a bit mask in the integer pointed to by the typesp argument. See
<sys/ddi_intr.h> for a list of interrupts that can be returned by a hardware device.
For PCI devices that support MSI and/or MSI-X based hardware, this interface returns only the interrupt types that are supported by all the
hardware in the path to the hardware device.
An interrupt type is usable by the hardware device if it is returned by the ddi_intr_get_supported_types() function. The device driver can
be programmed to use one of the returned interrupt types to receive hardware interrupts.
The ddi_intr_get_supported_types() function returns:
DDI_SUCCESS On success.
DDI_EINVAL On encountering invalid input parameters.
DDI_INTR_NOTFOUND Returned when the hardware device is found not to support any hardware interrupts.
CONTEXT
The ddi_intr_get_supported_types() function can be called from user or kernel non-interrupt context.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
pci(4), attributes(5), pcmcia(7D), sysbus(4), ddi_intr_add_handler(9F), ddi_intr_alloc(9F), ddi_intr_enable(9F)
The ddi_intr_get_supported_types() function can be called by the device driver even at any time if the driver has added an interrupt han-
dler for a given interrupt type.
Soft interrupts are always usable and are not returned by this interface.
Any consumer of this interface should verify that the return value is not equal to DDI_SUCCESS. Incomplete checking for failure codes could
result in inconsistent behavior among platforms.
07 Apr 2005 ddi_intr_get_supported_types(9F)