11-30-2009
Configure EMC Powerpath?
Hi ,
I have a redhat 5.3 server which has 2 vg.. one is rootvg in local harddisk and another one is applicationvg in SAN.. When I reboot the server , EMC powerpath driver is not starting up automatically. Hence applicationvg is not mounting properly. Therefore I need to unmount it manually and then I can get into system.
1.How do I start up emc powerpath driver automatically... ?
I did lsmod and restart the service.. still it gives the same problem...
I thought of uninstall and reinstalling the emc powerpath and reconfigure the whole thing... is that good idea???
If so, How do i configure the EMC Powerpath?
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
reboot(1M) reboot(1M)
NAME
reboot - reboot the system
SYNOPSIS
time] message]
time] message]
DESCRIPTION
The command terminates all currently executing processes except those essential to the system, then reboots the system, or halts, or makes
the partition ready for reconfiguration. When invoked without arguments, syncs all disks before rebooting the system.
Options
The command recognizes the following options:
Shut down the system and halt.
Shut down the system and reboot automatically (default).
Shut down the system to a ready-to-reconfigure state and reboot if possible.
If the partition is unable to reboot, it will stop at a ready-to-reconfigure state. However, if the option is also
specified, the system will always stop at ready-to-reconfigure state. This option is available only on systems that
support hardware partitions.
Shut down the system to a ready-to-reconfigure state and do not reboot.
This option can be used only in combination with the option. This option is available only on systems that support
hardware partitions.
Do not sync the file systems before shutdown.
The and options are ignored with this option.
Sync the file systems before shutdown;
for file systems that were cleanly mounted, modify the flag from to (default).
Quick and quiet.
Suppress broadcast of warning messages, terminate processes by brute force (with and immediately call with arguments
as indicated by the other options (see reboot(2)). No logging is performed. The and options are ignored with this
option.
Specify what time
will bring the system down. time can be the word (indicating immediate shutdown) or a future time in one of two for-
mats: and The first form brings the system down in number minutes; the second brings the system down at the time of
day indicated (based on a 24-hour clock).
Display message at the terminals of all users on the system at decreasing intervals as reboot time approaches. The message
must not contain any embedded double quotes.
At shutdown time a message is written in the file
(if it exists), containing the time of shutdown, who ran and the reason.
Only users with appropriate privileges can execute the command.
WARNINGS
does not invoke the shutdown scripts associated with subsystems to bring them down in a cautious manner. See shutdown(1M).
If the option is used in a virtual partition environment on a partitionable system, then the requested reconfiguration will not take place
until all the virtual partitions on that hard partition are shut down and the virtual partition monitor is rebooted.
AUTHOR
was developed by HP and the University of California, Berkeley.
FILES
Shutdown log
SEE ALSO
vpartition(1), reboot(2), partition(5).
reboot(1M)