HP XP P9000 RAID Manager User Guide (T1610-96059, January 2014)

2. Testing SLPR: RAID Manager verifies whether or not the command device can access a target
within SLPR. So, if the command device belongs to SLPR#0, or RAID Manager has no SLPR
function, then the SLPR protection is ignored.
However, if the command device is shared with the port on SLPR#1 and SLPR#2, RAID Manager
allows you to operate the volume on SLPR#1 and SLPR#2.
3. Rejecting commands: If access is denied on the specified port (or target volume), RAID Manager
rejects the following commands and outputs an error code, EX_ESPERM:
• horctakeover, paircurchk, paircreate, pairsplit, pairresync,
pairvolchk, pairevtwait, pairsyncwait
• raidscan (except -find verify, -find inst), raidar, pairdisplay
• raidvchkset, raidvchkscan (except -v jnl), raidvchkdsp
[EX_ESPERM] Permission denied with the SLPR
[Cause ] : A specified command device does not have a permission to access other SLPR.
[Action] : Please make the SLPR so that the target port and the command device belongs to the same
SLPR.
SLPR configuration examples
Single host
SLPR configuration on a single host (page 196) provides an example of when control is denied to
the paircreate and raidscan commands in the following cases:
• The volume described on RMINST1 is different from the SLPR of the command device, so the
paircreate command cannot control the paired volume.
• The specified port is different from the SLPR of the command device, so the raidscan -p
CL3-A command cannot scan any ports that are defined as SLPR#N.
Figure 68 SLPR configuration on a single host
To operate SLPR#N, assign the command device. If RMINST1 has been assigned to a command
device for SLPR#N, the paircreate command is permitted. However, the raidscan -p CL3-A
command (via RMINST0) is unable to scan a port, because the specified port is different than the
SLPR of the command device. In this case, -p CL3-A must be operated via RMINST1, as shown in
the following example.
196 Examples of using RAID Manager commands