hi friends,
i know that when there is a crash then that memory image is
put into /var/adm/crash
but if the system hangs up and if i have access to console of
that machine then how can i take the crash dump manully.
thanks (2 Replies)
Hi Guys,
I have two nodes clustered. Each node is AIX 5.2 & they are clustered with HACMP 5.2. The mode of the cluster is Active/Passive which mean one node is the Active node & have all resource groups on it & the 2nd node is standby.
Last Monday I noted that all resource groupes have been... (2 Replies)
Hi.
I have started heartbeat on two redhat servers. Using eth0.
Before I start heartbeat I can ping the two server to each other.
Once I start heartbeat both the server become active as they both have warnings that the other node is dead.
Also I am not able to ping each other. After stopping... (1 Reply)
Hi Guys,
I have to design a multinode hacmp cluster and am not sure if the design I am thinking of makes any sense.
I have to make an environment that currently resides on 5 nodes more resilient but I have the constrain of only having 4 frames. In addition the business doesnt want to pay for... (7 Replies)
Hi
I had an active passive cluster. Node A went down and all resource groups moved to Node B.
Now we brought up Node A. What is the procedure to bring everything back to Node A.
Node A #lssrc -a | grep cl
clcomdES clcomdES 323782 active
clstrmgrES cluster... (9 Replies)
Hi Experts,
I have configured HP-UX Service Guard cluster and it dumps crash every time i reboot a cluster node. Can anyone please help me to prevent these unnecessary crash dumps at the time of rebooting SG cluster node?
Thanks in advance.
Vaishey (2 Replies)
MacPro (2013) 12-Core, 64GB RAM (today's crash):
panic(cpu 2 caller 0xffffff7f8b333ad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since load (318824 seconds ago): 31883, last successful... (3 Replies)
Discussion started by: Neo
3 Replies
LEARN ABOUT NETBSD
ixgb
IXGB(4) BSD Kernel Interfaces Manual IXGB(4)NAME
ixgb -- Intel(R) PRO/10GbE Ethernet driver for the FreeBSD operating system
SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file:
device ixgb
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
if_ixgb_load="YES"
DESCRIPTION
The ixgb driver provides support for PCI Gigabit Ethernet adapters based on the Intel 82597EX Ethernet controller chips. The driver supports
Transmit/Receive checksum offload and Jumbo Frames.
For questions related to hardware requirements, refer to the documentation supplied with your Intel PRO/10GbE adapter. All hardware require-
ments listed apply to use with FreeBSD.
Support for Jumbo Frames is provided via the interface MTU setting. Selecting an MTU larger than 1500 bytes with the ifconfig(8) utility
configures the adapter to receive and transmit Jumbo Frames. The maximum MTU size for Jumbo Frames is 16114.
This driver version supports VLANs. For information on enabling VLANs, see ifconfig(8).
HARDWARE
The ixgb driver supports the following cards:
o Intel PRO/10GbE LR Server Adapter
o Intel PRO/10GbE SR Server Adapter
DIAGNOSTICS
ixgb%d: Unable to allocate bus resource: memory A fatal initialization error has occurred.
ixgb%d: Unable to allocate bus resource: interrupt A fatal initialization error has occurred.
ixgb%d: watchdog timeout -- resetting The device has stopped responding to the network, or there is a problem with the network connection
(cable).
SUPPORT
For general information and support, go to the Intel support website at: http://support.intel.com.
If an issue is identified with the released source code on the supported kernel with a supported adapter, email the specific information
related to the issue to <freebsdnic@mailbox.intel.com>.
SEE ALSO arp(4), em(4), netintro(4), ng_ether(4), polling(4), vlan(4), ifconfig(8)HISTORY
The ixgb device driver first appeared in FreeBSD 4.11 and FreeBSD 5.3.
AUTHORS
The ixgb driver was written by Intel Corporation <freebsdnic@mailbox.intel.com>.
BSD August 18, 2006 BSD