Sponsored Content
Full Discussion: EMC Failover
Operating Systems Solaris EMC Failover Post 302366759 by System Shock on Friday 30th of October 2009 09:34:44 AM
Old 10-30-2009
According to this output, you don't have a license. Do you have a license for Powerpath? Have you installed the license with emcpreg ?
 

10 More Discussions You Might Find Interesting

1. Solaris

Interfaces do not failover

Would anyone know why a V440 Solaris 9 machine's interfaces (ce0 and ce1) will not failover? Both interfaces are on the same subnet, but different IPs. I can pull the plug on once interface (ce0) and ce1 will be accessible. I can reverse it and pull ce1, and ce0 will NOT be accessible. ... (5 Replies)
Discussion started by: StorageGuy
5 Replies

2. HP-UX

is anybody using EMC symmetrix?

Hello, I'm looking for reference sites using HP-UX and EMC symmetrix disk. Then, May I ask you questions? (6 Replies)
Discussion started by: cooldugong
6 Replies

3. Solaris

Emc

Dear gentelmen kindly please update me me how can i know disks on EMC and get size for all disks on EMC? (1 Reply)
Discussion started by: magasem
1 Replies

4. HP-UX

Emc

Dear gentelmen kindly please update me how can i know disks on EMC and get size for all disks on EMC? (0 Replies)
Discussion started by: magasem
0 Replies

5. UNIX for Advanced & Expert Users

AIX MPIO and EMC

We are looking at running MPIO for it's redundancy and load balancing benefits. Does anyone know what pieces of software or modules are needed on the VIO server to get load balancing to work. Remember we are using EMC's DMX3500 storage system. We no longer want to use Powerpath. :rolleyes: ... (2 Replies)
Discussion started by: vxg0wa3
2 Replies

6. UNIX for Advanced & Expert Users

directories failover

Hi, I have 3 directories (/1 /2 and /3) with same contents and want to achieve fail over among them. The Solution i thought of: 1. link /data to /1 (and provide users with /data to access) 2. CRON a script (to run every minute) to verify if /1 exist or not, if it does not exist (or its... (3 Replies)
Discussion started by: prvnrk
3 Replies

7. AIX

failover on 4.5 hacmp

Hi All, How do I trigger the failover on the second hacmp server? Please give me idea and I will do the rest. Thanks, itik (2 Replies)
Discussion started by: itik
2 Replies

8. IP Networking

IP failover needed

All, I am looking to setup a simple IP failover setup, but it seems every place i look has some difficult setup like pacemaker or LVS. I only want to handle the IP piece to failover a VIP. Any suggestions? I checked out keepalived and that my work for me. (4 Replies)
Discussion started by: markdjones82
4 Replies

9. Gentoo

How to failover the cluster ?

How to failover the cluster ? GNU/Linux By which command, My Linux version 2008 x86_64 x86_64 x86_64 GNU/Linux What are the prerequisites we need to take while failover ? if any Regards (3 Replies)
Discussion started by: sidharthmellam
3 Replies

10. AIX

Help with EMC BCV device

I'm trying to auto-mount EMC Symmetrix BCV device at boot. but having problem making BCV available. I put script called mkbcv to the inittab and engineer suggested to add 120 sec sleep between cfgmgr so I did that also. My mkbcv script seems to be working fine, it says "hdisk4 Available" ... (1 Reply)
Discussion started by: shuhei365
1 Replies
device_remap(1M)					  System Administration Commands					  device_remap(1M)

NAME
device_remap - administer the Solaris I/O remapping feature SYNOPSIS
/usr/platform/sun4v/sbin/device_remap [-v | -R dir] DESCRIPTION
Certain multi-node sun4v platforms, such as T5440 and T5240 servers, have an integrated PCI topology that cause the I/O device paths to change in a CPU node failover condition. The device remapping script, device_remap, remaps the device paths in /etc/path_to_inst file and the symlinks under /dev to match the hardware. OPTIONS
The following options are supported: -v Displays the /etc/path_to_inst and /dev symlink changes. -R dir Perform remapping on the /etc/path_to_inst and /etc/path_to_inst files in the root image at dir. USAGE
The primary function of device_remap is to remap the device paths in the /etc/path_to_inst file and the symlinks under /dev in a CPU node failover condition to match the hardware. After adding CPU node(s) or removing CPU node(s), boot the system to the OBP prompt and use the following procedure: 1. Boot either the failsafe miniroot using: boot -F failsafe , or an install miniroot using boot net -s or similar command. 2. Mount the root disk as /mnt. 3. Change directory to the mounted root disk: # cd /mnt 4. Run device_remap script: # /mnt/usr/platform/sun4v/sbin/device_remap 5. Boot the system from disk. All the error messages are self-explanatory, except for the error message "missing ioaliases node" which means the firmware on the system does not support device remapping. EXAMPLES
Example 1 Displaying Changes Following Failover The following command displays the path_to_inst and /dev changes following a CPU node failover. # device_remap -v Example 2 Changing Directory Prior to Any Changes The following command changes the directory on which the boot image is mounted prior to making any changes. # device_remap -R /newroot ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWkvm.v | +-----------------------------+-----------------------------+ |Interface Stability |Unstable | +-----------------------------+-----------------------------+ SEE ALSO
boot(1M), attributes(5) SunOS 5.11 24 Dec 2008 device_remap(1M)
All times are GMT -4. The time now is 05:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy