HP-UX check SCSI reservation


 
Thread Tools Search this Thread
Operating Systems HP-UX HP-UX check SCSI reservation
# 1  
Old 08-16-2013
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 "scsimgr get _attr" I want to know how can i determine if there is any reservation on the disks.


Thanks for your help!
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. Solaris

Modifying properties to use scsi-3 reservation for disks with two paths in sun cluster

Hi I am having two node cluster. I was trying to change the to use scsi3 reservation for all disks having two paths. Please let me know where I went wrong or there any issue to implement the same. On node1 bash-3.2# cldev status === Cluster DID Devices === Device Instance ... (8 Replies)
Discussion started by: sb200
8 Replies

2. 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

3. Filesystems, Disks and Memory

Installing SCSI

I need to hook a tape library to my compy (tru64 versifon 4F) by way of SCSI. I can get as far as plugging it in on my own. Please help Thanks (0 Replies)
Discussion started by: randUSR()
0 Replies

4. AIX

LUN Reservation and Clearence

Hello Everyone, I wud like to knw what we mean by LUN reservation and how to clear the LUN reservation in AIX. Regards, nivas (2 Replies)
Discussion started by: nivaspIND
2 Replies

5. Solaris

Help probe-scsi-all

I have run init 0 to bring it to OK prompt. I know that probe-scsi-all can hang the system. I want to know what is the difference between probe-scsi-all and probe-scsi. I was told that probe-scsi-all external and internal devices and probe-scsi shows only internal devices. what dose this ... (3 Replies)
Discussion started by: nitinkgoud
3 Replies

6. UNIX for Advanced & Expert Users

Scsi

I would like to install a AIT drive to the scsi connector on our solaris box. I am very new to the unix world and would be greatful if someone could help or lead me in the right direction. Thanks (4 Replies)
Discussion started by: vpyle
4 Replies

7. Filesystems, Disks and Memory

Compaq Scsi

Howto make Debian GNU/Linux install boot on a Compaq DeskPro XL 590 with Compaq SCSI diskdrive? The problem is that Compaq's Scsi controller sems to be odd. help please :) (0 Replies)
Discussion started by: Esaia
0 Replies

8. UNIX for Advanced & Expert Users

Scsi

How can you get a scsi card to initalize or decome available at boot up on AIX 4.3 (1 Reply)
Discussion started by: truma1
1 Replies
Login or Register to Ask a Question
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)