Sponsored Content
Operating Systems Solaris Modifying properties to use scsi-3 reservation for disks with two paths in sun cluster Post 302954403 by hicksd8 on Monday 7th of September 2015 12:57:48 PM
Old 09-07-2015
What make/model of iSCSI SAN box is it?

https://docs.oracle.com/cd/E19787-01...jts/index.html

I guess it depends whether Oracle support your iSCSI SAN.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

The difference between SCSI & IDE Hard disks.

Hello agian ! What is the difference between SCSI and IDE hard disks ? I have Intel PC and when i check i have Generic IDE TYPE DISK0 is IDE hard disk is ok for Solrais ? or should i buy the SCSI hard disk ? Thanks Abid Malik (3 Replies)
Discussion started by: abidmalik
3 Replies

2. AIX

SCSI Disks

Hi Is it possible to install in p5 and pSeries SCSI Disks from SUN on DELL? Will they work? Regards, Pit (0 Replies)
Discussion started by: piooooter
0 Replies

3. Solaris

Reclaiming EMC disks after losing paths

First time writer....take it easy on me. I had a situation where I lost all paths to EMC disk. There was a failure on the EMC frame. After that was repaired, my server had a difficult time reclaiming all disks and veritas had marked the disks as failed. Veritas was confused. What are some of... (3 Replies)
Discussion started by: Sowser
3 Replies

4. Linux

Modifying Linux in WesternDigital net disks

Hi, I am installing perl and rsnapshot on the OS of a Western Digital MyBook disk. To install perl the ./Configure command tells me that both 'tr' and 'split' are missing. I don't find them on the net. Where can I download them? Thanks. Charles. (2 Replies)
Discussion started by: mosndup
2 Replies

5. Solaris

Sun cluster and Veritas cluster question.

Yesterday my customer told me to expect a vcs upgrade to happen in the future. He also plans to stop using HDS and move to EMC. Am thinking how to migrate to sun cluster setup instead. My plan as follows leave the existing vcs intact as a fallback plan. Then install and build suncluster on... (5 Replies)
Discussion started by: sparcguy
5 Replies

6. Solaris

Sun cluster 4.0 - zone cluster failover doubt

Hello experts - I am planning to install a Sun cluster 4.0 zone cluster fail-over. few basic doubts. (1) Where should i install the cluster s/w binaries ?. ( global zone or the container zone where i am planning to install the zone fail-over) (2) Or should i perform the installation on... (0 Replies)
Discussion started by: NVA
0 Replies

7. Solaris

Unknown Disks "offline or reservation conflict"

Hi All, I am a RH Linux admin that recently started working at a company with a number of SUN Servers so it's been an interesting transition. Considering the last person left with very little documentation left behind so I have been picking up most issues half complete, or troubleshot. ... (7 Replies)
Discussion started by: MobileGSP
7 Replies

8. HP-UX

HP-UX check SCSI reservation

Hi guys, I need some help to better understand how to determine if a disk have persistent SCSI reservation. I know that we should use the "Persisten Reservation Utility" but we are not allowed to run that tool. Since we have the output from some grab utility and specifically we have the... (0 Replies)
Discussion started by: cecco16
0 Replies
fence_scsi(8)						      System Manager's Manual						     fence_scsi(8)

NAME
fence_scsi - I/O fencing agent for SCSI persistent reservations SYNOPSIS
fence_scsi [OPTION]... DESCRIPTION
fence_scsi is an I/O fencing agent that uses SCSI-3 persistent reservations to control access to shared storage devices. These devices must support SCSI-3 persistent reservations (SPC-3 or greater) as well as the "preempt-and-abort" subcommand. The fence_scsi agent works by having each node in the cluster register a unique key with the SCSI devive(s). Once registered, a single node will become the reservation holder by creating a "write exclusive, registrants only" reservation on the device(s). The result is that only registered nodes may write to the device(s). When a node failure occurs, the fence_scsi agent will remove the key belonging to the failed node from the device(s). The failed node will no longer be able to write to the device(s). A manual reboot is required. Keys are either be specified manually (see -k option) or generated automatically (see -n option). Automatic key generation requires that cman be running. Keys will then be generated using the cluster ID and node ID such that each node has a unique key that can be determined by any other node in the cluster. Devices can either be specified manually (see -d option) or discovered automatically. Multiple devices can be specified manually by using a comma-separated list. If no devices are specified, the fence_scsi agent will attempt to discover devices by looking for cluster volumes and extracting the underlying devices. Devices may be device-mapper multipath devices or raw devices. If using a device-mapper multipath device, the fence_scsi agent will find the underlying devices (paths) and created registrations for each path. OPTIONS
-o action Fencing action. This value can be "on", "off", or "status". All actions require either a key (see -k option) or node name (see -n option). For "on", the agent will attempt to register with the device(s) and create a reservation if none exists. The "off" action will attempt to remove a node's key from the device(s). The "status" action will report whether or not a node's key is currently register with one or more of the devices. The default action if "off". -d devices List of devices to use for current operation. Devices can be comma-separated list of raw device (eg. /dev/sdc) or device-mapper mul- tipath devices (eg. /dev/dm-3). Each device must support SCSI-3 persistent reservations. -f logfile Log output to file. -n nodename Name of the node to be fenced. The node name is used to generate the key value used for the current operation. This option will be ignored when used with the -k option. -k key Key to use for the current operation. This key should be unique to a node. For the "on" action, the key specifies the key use to register the local node. For the "off" action, this key specifies the key to be removed from the device(s). -a Use the APTPL flag for registrations. This option is only used for the "on" action. -h Print out a help message describing available options, then exit. -v Verbose output. -V Print out a version message, then exit. STDIN PARAMETERS
agent = "param" This option is used by fence_node(8) and is ignored by fence_scsi. nodename = "param" Same as -n option. action = "param" Same as -o option. devices = "param" Same as -d option. logfile = "param" Same as -f option key = "param" Same as -k option. aptpl = "1" Enable the APTPL flag. Default is 0 (disable). SEE ALSO
fence(8), fence_node(8), sg_persist(8), vgs(8), cman_tool(8), cman(5) fence_scsi(8)
All times are GMT -4. The time now is 02:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy