11-30-2009
There should be a /etc/modprobe.conf.pp and a reference to it in modprobe.conf. If they are there, perhaps your SAN drivers do not get loaded at boot time and the mkinitrd did not go right? What do the logs say?
Last edited by Scrutinizer; 11-30-2009 at 02:19 AM..
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
We currently have a Solaris box connected to a Clariion storage system that is utilising DMP for path failover. I would prefer to use EMC's Powerpath and was wondering if the two can coexist?
Basically, I am struggling to find any documentation on the subject and was wonder if anyone can give me... (2 Replies)
Discussion started by: aaron2k
2 Replies
2. Solaris
How to change the following values in power path from SP B to SP A ?
Owner: default=SP B, current=SP B
this is excerpt from powermt display dev=all (3 Replies)
Discussion started by: fugitive
3 Replies
3. AIX
Hi Guys,
I have a problem while trying to upgrade to more current EMC powerpath software on AIX 5.3 - respectively uninstalling the existing one.
I tried to deinstall the powerpath software with removed disks - was working perfectly fine on 12 servers - but number 13 is failing with errors:
... (4 Replies)
Discussion started by: zxmaus
4 Replies
4. Solaris
Hello,
I have an issue with veritas volume manager version 5.0 in combination with EMC powerpath version 5.2.0 running on Solaris10(Sparc). This server is fiber connected to a EMC Clariion CX3-40 SAN.
This is the situation :
Server is a SUN Enterprise M5000
OS = Solaris10 Sparc
Veritas... (1 Reply)
Discussion started by: chipke2005
1 Replies
5. Solaris
Here is the issue:
I am building a database server using Solaris 10x86 U8.
The system is jumpstarted with mpxio enabled and booting from the san.
We need to have powerpath 5.3 installed and would like to have powerpath take control of the the boot san as well or have mpxio control the san... (2 Replies)
Discussion started by: nabru72
2 Replies
6. AIX
Hi All,
I'm preparing to migrate some servers from vscsi to pass-thru NPIV. I am planning to have the SAN team move the exact LUNs from vio1/vio2 to those two VWWN through NPIV.
My question is on the partition itself.. right now, let's say I have hdisk0/1/2/3/4 that are part of datavg. They... (2 Replies)
Discussion started by: lapfrank
2 Replies
7. Linux
Hello guys, I'm going crazy over here with a problem with a LUN created on a EMC CX3.
I did sucessfully managed to create the LUN on the Storage (the LUN is named DBLNX25EC_TST), after doing the following process:
echo "1" > /sys/class/fc_host/host<n>/issue_lip
and
echo "- - -" >... (10 Replies)
Discussion started by: Zarnick
10 Replies
8. Solaris
Hi all
I am running the following hardware:
2 SUN Solaris 10 machines
They are connected to EMC clarion LUNs
We are running a Sun Cluster 3.2 managing both nodes
We are using Solaris Volume Manager to handle the shared storage for the cluster. It is using a number of named disk sets that is... (0 Replies)
Discussion started by: abohmeed
0 Replies
9. Solaris
It seems like I lost one path on my Solaris-11 box. But I want to make sure before going to Storage team, if issue is from OS side or Storage side. Storage team is able to see that only one wwwn is looged in their switch. I am not at server's physical location. What does below output says ? I... (0 Replies)
Discussion started by: solaris_1977
0 Replies
10. Solaris
Hi,
We're trying out a SAN migration from HP EVA to EMC VMAX, and run into a bit of an issue with powerpath and zfs.
The method we're currently using to migrate is to export the HP EVA luns from our sun server, replicate using SAN based method, and then present the new luns to our Sun server... (7 Replies)
Discussion started by: badoshi
7 Replies
LEARN ABOUT REDHAT
netdump-server
NETDUMP-SERVER(8) System Programs NETDUMP-SERVER(8)
NAME
netdump-server - handle crash dumps over the network
SYNOPSIS
netdump-server [--port portnumber]
[--concurrent number]
[--pidfile path]
[--daemon]
[--help] [--usage]
DESCRIPTION
Listens to the network for clients that crashes and uses the netdump protocol to recieve a memory dump and a stack trace. The memory dump
and oops message are stored in a timestamped directory in /var/crash. The server can also run scripts when some events happen.
OPTIONS
--port portnumber
Specifies the IP port number for the netdump server to listen to. The default is 6666.
--concurrent number
You can limit the amount of concurrent dumps being done at any one time. If more clients than the specified maximum connects at one
time the last ones will just be logged and then rebooted.
--pidfile path
Store a pidfile. The default service uses /var/run/ttywatch.pid. The default is not to write a pidfile.
--daemon
ttywatch should background itself and run as a daemon.
EXAMPLES
netdump-server --daemon
This launches the netdump-server and puts it in the background, listening for crashed clients.
EXIT STATUS
Exit status is 0 for a clean exit and non-0 for a non-clean exit.
FILES
/etc/netdump.conf
A configuration file read by netdump-server on startup. It is a "key=value" style file. Currently it supports the options: port,
max_concurrent_dumps, daemon and pidfile.
/etc/init.d/netdump-server
An init script to start a default system installation of netdump-server. This is normally turned off by default; use the command
/sbin/chkconfig netdump-server on
to enable the netdump-server service.
/var/crash
The main directory where the crash dump files are stored. Each dump is put in a subdirectory named with the ip of the crashed
machine and the date and time of the crash.
/var/crash/scripts
This directory can contain scripts that are run at various times. They all get passed the ip of the crashing machine as the first
argument, and each one except netdump-start gets the directory that the dump is written into as the second argument.
netdump-start - This is called when a client connects to the server to tell it that it has just started the netdump client. This
normally means that the machine just booted up.
netdump-crash - This is run when a client reports that it has crashed. If it returns a non-zero value the dump request will be
ignored and the client will be told to reboot immediately
netdump-nospace - This is run when there is not enough diskspace for the dump of the crashed machine. If this script exits with a
non-zero return value netdump-server will try once again (but only once) before giving up the dump. If this script exits with a zero
return value, netdump-server will reboot the client without performing a dump.
netdump-reboot - This is run when netdump-server is finished with a client and is about to tell the client to reboot itself.
SEE ALSO
netdump(8)
BUGS
Report any bugs you find to http://bugzilla.redhat.com/bugzilla
AUTHOR
Alexander Larsson <alexl@redhat.com>
Linux 14 Feb 2002 NETDUMP-SERVER(8)