SafeGuard Solutions Deploying Brocade AP-7600B and PB-48K ...

Unisys SafeGuard Solutions 

Deploying Brocade 

AP-7600B and PB-48K-AP4-18 Devices Technical 

Notes 

Unisys SafeGuard Solutions Release 6.1 

September 2008 3826 5294–001 

unisys 

imagine it. done.

NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product or related information 

described herein is only furnished pursuant and subject to the terms and conditions of a duly executed agreement to 

purchase or lease equipment or to license software. The only warranties made by Unisys, if any, with respect to the 

products described in this document are set forth in such agreement. Unisys cannot accept any financial or other 

responsibility that may be the result of your use of the information in this document or software material, including 

direct, special, or consequential damages. 

You should be very careful to ensure that the use of this information and/or software material complies with the laws, 

rules, and regulations of the jurisdictions with respect to which it is used. 

The information contained herein is subject to change without notice. Revisions may be issued to advise of such 

changes and/or additions. 

Notice to U.S. Government End Users: This is commercial computer software or hardware documentation developed at 

private expense. Use, reproduction, or disclosure by the Government is subject to the terms of Unisys standard 

commercial license for the products, and where applicable, the restricted/limited rights provisions of the contract data 

rights clauses. 

Unisys is a registered trademark of Unisys Corporation in the United States and other countries. 

All other brands and products referenced in this document are acknowledged to be the trademarks or registered 

trademarks of their respective holders.

EMC ® Unisys SafeGuard Solutions 

Deploying Unisys SafeGuard Solutions with 

the Brocade ® AP-7600B and PB-48K-AP4-18 

Technical Notes 

P/N 300-005-595 

REV A03 

June 20, 2008 

This document describes how to deploy Unisys SafeGuard Solutions 

with the Brocade AP-7600B and PB-48K-AP4-18 devices to deliver a 

complete data replication solution without host-based agents. Topics 

include: 

◆ Introduction........................................................................................... 2 

◆ Overview of the deployment concepts ............................................. 4 

◆ Unisys SafeGuard Solutions deployment procedure.................... 18 

◆ Running and upgrading Unisys SafeGuard Solutions SAS agent 25 

◆ Useful Brocade CP commands ......................................................... 26 

◆ Upgrading the SAS............................................................................. 27 

◆ Migrating from multi-VI to frame redirect ..................................... 29 

◆ Migrating from AP-7420B to AP-7600B .......................................... 30 

◆ Troubleshooting.................................................................................. 34 

1

Introduction 

Unisys SafeGuard Solutions supports deployment with the new 

Brocade application platforms: 

◆ Brocade AP-7600B stand-alone switch 

◆ Brocade PB-48K-AP4-18 blade (which slots into a Brocade 

ED-48000B director for full functionality) 

Unisys SafeGuard Solutions deployment involves the installation of a 

Unisys SafeGuard Solutions SAS agent on each Brocade device. In 

Unisys SafeGuard Solutions terms, this Unisys SafeGuard Solutions 

SAS agent serves as a “splitter”, which is responsible for ensuring 

that all data routed to the switch by host applications (and that is to 

be replicated) is forwarded in parallel both to the SAN-attached 

storage and to a replication appliance (RA), from where it is 

replicated to target-side storage. The Unisys SafeGuard Solutions 

Replication Appliance Administrator’s Guide provides additional 

information on Unisys SafeGuard Solutions system architecture. 

This document is intended primarily for IT professionals who are 

responsible for deploying Unisys SafeGuard Solutions in a 

SAS-equipped Brocade environment, and who are experienced in the 

areas of SAN management and topology. 

Prerequisites Unisys SafeGuard Solutions deployment with the new Brocade 

application platforms requires the following items: 

◆ Brocade AP-7600B or PB-48K-AP4-18, with the Fabric Operating 

System (FOS) and Storage Application Services (SAS) that is 

supported for your installed version of Unisys SafeGuard 

Solutions. 

2 Unisys SafeGuard Solutions Deploying Brocade AP-7600B and PB-48K-AP4-18 Devices Technical Notes

Table 1 Supported FOS and SAS per Unisys SafeGuard Solutions release 

Unisys 

SafeGuard 

Solutions 

release FOS SAS a 

5.0 5.3.0c 

5.3.0a 

Use the firmwareshow switch CLI command to display the 

version of the currently installed FOS and SAS. “Upgrading the 

SAS” on page 27 presents instructions for upgrading the SAS. 

Additional information about installation of the Brocade 

AP-7600B and PB-48K-AP4-18 devices, and the FOS and SAS, is 

available in the Brocade documentation on: 

http:\\support.unisys.com 

◆ For PB-48K-AP4-18, a Brocade EC-48000B director, in which the 

blade is installed. 

◆ replication appliances (RAs), running the version of Unisys 

SafeGuard Solutions software that is compatible with the 

installed Brocade devices. The Unisys SafeGuard Solutions 

Replication Appliance Installation Guide provides RA installation 

instructions. 

◆ Latest Unisys SafeGuard Solutions SAS agent installation 

package. Unisys personnel can download the executable file from 

Unisys Support Center. 

Related documents Use the release of any of the following documents, available in the 

Documentation Library on http:\\support.unisys.com, that matches 

your installed Unisys SafeGuard Solutions version: 

◆ Brocade Fabric OS Command Reference Manual 

◆ Unisys SafeGuard Solutions Replication Appliance Release Notes 

Unisys SafeGuard Solutions Deploying Brocade AP-7600B and PB-48K-AP4-18 Devices Technical Notes 

3.0.0b 

6.0 5.3.0d 3.0.0e 

6.1 6.0.1a 3.1.0a 

a. The AP-7600B and PB-48K-AP4-18 are shipped 

with the SAS pre-installed. 

3

◆ Unisys SafeGuard Solutions Replication Appliance Administrator’s 

Guide 

◆ Unisys SafeGuard Solutions Replication Appliance Command Line 

Interface (CLI) Reference Guide 

◆ Unisys SafeGuard Solutions Replication Appliance Installation Guide 

Overview of the deployment concepts 

Common terms for 

the deployment 

The new generation of EMC Brocade storage virtualization solutions 

is delivered both as the AP-7600B stand-alone switch, and as the 

PB-48K-AP4-18 blade, which slots into a Brocade EC-48000B director. 

Both offer 16 Fibre Channel ports. 

The management of these two platforms is divided between the 

following components: 

◆ Control processor (CP) — Runs the Fabric OS and handles layer 2 

communications. 

◆ Blade processor (BP) — Runs the storage application services 

(SAS) and manages the virtualization layer. The Unisys 

SafeGuard Solutions SAS agent is installed on the BP. 

The CP and BP have unique IP addresses. You can use the 

ipaddrshow switch CLI command to display the IP address for each. 

It may be helpful to refer to Figure 2 on page 8 while reading the 

following paragraphs: 

◆ Data path controller — Both the AP-7600B and PB-48K-AP4-18 

have two data path controllers (DPCs). The DPC handles most 

I/O operations without further CPU involvement. You can 

associate a set of virtual initiators and virtual targets with each 

DPC. 

Note: When working with Unisys SafeGuard Solutions Release 6.1, in 

frame redirect mode, both DPCs are utilized. Otherwise, only one DPC is 

utilized. 

◆ Host initiator — Each HBA on a host machine can be a host 

initiator (HI). Each host initiator is represented by a single virtual 

initiator on each DPC that it uses. 


◆ Virtual initiator — When working in multi-VI mode, a single 

virtual initiator (VI) is created to correspond with each host 

(HBA) initiator. In frame redirect mode, if the host is bound to 

targets on both DPCs, a separate VI is created for that host for each 

DPC. The WWN that is set for the virtual initiator is different 

from the WWN of the host initiator to which it corresponds. 

When working in multi-VI mode, LUN masking exposes the 

storage ports to the virtual initiator, rather than to the host 

initiator. In frame redirect, LUN masking does not change from 

that which is already in place for the host HBA. 

◆ System virtual initiator — Unisys SafeGuard Solutions SAS 

agent creates a special System VI, to support communication 

between the splitter and the RAs. 

◆ Virtual target — The virtual target (VT) is a representation on the 

switch of the actual storage target to which the host initiator 

directs it I/O. Its WWN is different, however, from the WWN of 

the storage target (as presented in “Virtual target WWNs” on 

page 11). 

Note: The point at which the Unisys SafeGuard Solutions SAS agent 

creates a virtual target depends on whether you are working in 

“multi-VI” or “frame redirect” mode. These modes are described in 

“Multi-VI and frame redirect modes” on page 6. 

The Unisys SafeGuard Solutions SAS agent creates the virtual 

target as follows: 

In multi-VI mode, upon first binding a host initiator to the 

virtual initiator to which the storage target is exposed. The 

host initiator then sends its I/O to the virtual target, rather 

than to the storage target. 

In frame redirect mode, upon first binding a host initiator to 

the storage target. 

◆ Appliance virtual target — The appliance virtual target (AVT) is 

a special virtual target that ensures that the RA has access to the 

storage targets for groups that use reservations, as described in 

“Reservations” on page 15. 

◆ Storage target — The storage target (ST) is a physical port on the 

storage array, to which the data written by the host initiator is 

ultimately directed. 


5

Multi-VI and frame 

redirect modes 

The Unisys SafeGuard Solutions SAS agent on AP7600B or 

PB-48K-AP4-18 platforms can be deployed in either frame redirect or 

multi-VI mode. 

Multi-VI mode will impact the existing fabric in the following ways: 

◆ LUN mapping must now direct the LUNs to the virtual initiators 

instead of the host initiators. 

◆ Zoning must be completely reorganized. 

Unisys SafeGuard Solutions can use the frame redirect capabilities of 

the AP-7600B and PB-48K-AP4-18 to alleviate the need for much of 

the reconfiguration. 

When frame redirect is enabled, the name server deliberately gives 

“misleading” answers to FCID queries that are generated by the host 

and target. As a result, host initiators send writes that are directed to 

the storage targets to the virtual targets, and storage targets see writes 

that come from the virtual initiators as if they are coming from the 

host initiators themselves. 

Figure 1 on page 7 shows an environment in which the storage target 

with WWN W1 and FCID F1 is exposing LUNs to the host initiator 

with WWN W2 and FCID F2. 


Host Initiator 

FCID F2 

Target 

FCID 

For W1? 

FR VT 

FCID F3 

Figure 1 Frame redirect communications 

SCSI Wr10, SID=F2, DID=F1 

Wr10, SID=F2,DID=F3 

Wr10, SID=F4,DID=F1 

F3 

Host 

FCID 

For W2? 

F4 

NameServer 

FR VI 

FCID F4 

FR Zone {Host Initiator,Target,FR VT,FR VI} 

When deploying Unisys SafeGuard Solutions in multi-VI mode, the 

host initiator must be zoned with the virtual target (with WWN W3 

and FCID F3) that represents the physical target, and the target must 

be zoned with and reconfigured to expose LUNs to the virtual 

initiator (with WWN W4 and FCID F4) that represents the host 

initiator. 

When working in frame redirect mode, however, the zone between 

the initiator and the target remains, but the Unisys SafeGuard 

Solutions SAS agent automatically creates an additional “frame 

redirect” zone between the host initiator, virtual initiator, virtual 

target, and storage target. Then, whenever the initiator sends a query 

to the name server requesting the corresponding FCID of target W1, it 

receives the FCID F3, therefore directing its writes to the virtual target 

instead of to the actual target. Further, whenever the target requests 

the corresponding FCID of initiator W2, it receives the FCID F4, 

therefore treating writes from the virtual initiator as if they are 

received from the host initiator. 


Target 

FCID F1 

7

Note: When establishing frame redirect connectivity between an initiator and 

target, the initiator and target must be connected directly to a switch running 

FOS version 5.3.0 or later. Also, frame redirect mode is not supported in 

mixed Brocade-McData fabrics. 

Basic configurations Figure 2 shows a virtual initiator that has access to three storage 

target devices. As a result, three virtual targets are created. 

Bound 

Host Initiator 

Virtual Targets (VT) 

Virtual Initiator (VI) 

DMX CX Invista 

Storage Targets 

Figure 2 Single DPC with VI access to multiple storage targets in multi-VI mode 

8 Unisys SafeGuard Solutions Deploying Brocade AP-7600B and PB-48K-AP4-18 Devices Technical Notes 

DPC 0 

Masked 

GEN-000633

Figure 3 shows an example, when using multi-VI binding, of multiple 

(in this case, two) virtual initiators with access to the same storage 

target devices. 

HBA Initiator HBA Initiator 

Virtual Targets (VT) 

Bound DPC 0 

Bound 

Masked 

Host server Host server 



DMX CX Invista GEN-000634 

Figure 3 Host initiators accessing the same storage targets (multi-VI binding) 

Multiple virtual initiators can access the same storage target. While 

only one virtual target is created for that storage target, a different set 

of LUNs, from among the LUNs that belong to the storage target, can 

be exposed to each initiator. For example, the DMX storage port can 

expose LUNs (0,1,2) to one of the virtual initiators and LUNs (3,4,5) 

to the other virtual initiator (in multi-VI mode). As a result, the 

corresponding virtual target will expose LUNs (0,1,2) to one of the 

host initiators and LUNs (3,4,5) to the other host initiator, according 

to the HI-VI matching. 

In this configuration, if the same set of storage devices is exposed to a 

single virtual initiator through multiple storage targets (that is, 

multipathing), a virtual target is created for each path. 


Masked 

9

Using dual DPCs in 

frame redirect 

mode 

When working in frame redirect mode with the Unisys SafeGuard 

Solutions SAS agent for Unisys SafeGuard Solutions 6.1, the agent 

utilizes both DPCs by alternating the DPC on which it creates each 

new virtual target. Since virtual initiators and virtual targets that 

reside on different DPCs cannot interact, then if a single initiator is 

bound to targets on both DPCs, it will be necessary to represent that 

initiator with a separate VI on each DPC. A target, however, is always 

represented by a single VT. 

For example, if initiator I1 is bound to target T1 and initiator I2 is 

bound to Target T2, the Unisys SafeGuard Solutions SAS agent 

creates VI1 and VT1 on DPC 0 and VI2 and VT2 on DPC 1. If I1 is 

bound also to T2, the agent must create another VI for I1 on DPC 

1—since VI1, that resides on DPC #0 cannot interact with VT2 on 

DPC 1. When enabling reservation support for a group, the agent will 

create an AVT for each VI that represents a host that has access to a 

volume that supports reservations, up to one AVT per initiator per 

DPC. 

Although the total number of virtual entities may be higher when 

utilizing two DPCs, the number of virtual entities per DPC is always 

lower. Hence, the possible scalability in this mode is always higher 

(since the limit is per DPC). The number of used ITLs is not affected 

by the utilization of both DPCs, but the maximum possible number of 

ITLs doubles, as does the number of virtual initiators. 

To determine the number of virtual entities on each DPC, use the 4-bit 

DPC number in the WWN to determine the DPC number of each VT 

(as described under “Virtual target WWNs”). Then, use the binding 

scheme to determine the number of VIs for each DPC. Note that an 

additional VI (the “System VI”) will be created on DPC 0. 

Note: Dual DPC utilization is not supported for multi-VI mode. 


Virtual target WWNs Figure 4 shows the format for the virtual target PWWN. 

70 01 24 82 

Figure 4 VT WWN format 

For example, a virtual target created on DPC 0, where the WWN of 

the corresponding storage target is 0x1234567890123456, and the hash 

of that WWN is 0xabcd, would be: 

0x70012482abcd0456 

These WWNs are displayed by the get_virtual_targets CLI 

command, and are used to define front-end zoning on the switch, 

when working in multi-VI mode. 

Even though the WWNs for virtual targets are different from the 

WWNs of the corresponding storage targets, the virtual targets 

borrow their SCSI personality from the storage targets (except, in 

some cases, for the LUN size, which Unisys SafeGuard Solutions may 

“fake”). Therefore, the host initiator sees the virtual targets as the 

same type of storage as the actual storage target, including vendor, 

product, and UID. As a result, any multipathing software installed on 

the host works with the virtual targets as if they are the actual 

physical storage targets. 

Splitter identification The Unisys SafeGuard Solutions SAS agent behaves as a standard 

splitter in the Unisys SafeGuard Solutions Management Application 

or CLI. The OS type for the splitter is designated as Brocade AP. The 

splitter name will be set during agent installation, which is presented 

in Step 6 on page 19. 

The format of the splitter name is as follows: 

SW_name-SW_IPaddress 

where: 

16-bit hash of 

storage WWN 

4-bit DPC # 

Last 12 bits of 

storage WWN 

SW_name is the name of the BP that you specified during agent 

installation; it can be obtained by running hostname on the BP. 

SW_IPaddress is the IP address of the BP (at time of agent 

installation); it can be obtained by running ifconfig on the BP. 


11

LUN configuration 

Note: This section is relevant only when working in multi-VI mode; LUN 

configuration changes are not needed in frame redirect mode. 

LUNs are provisioned (or exposed) to initiators according to the LUN 

configuration. When deploying Unisys SafeGuard Solutions on the 

Brocade AP-7600B or PB-48K-AP4-18, and working in multi-VI mode, 

the LUN configuration must be directed at the virtual initiators, 

rather than the host initiators. 

In most cases, an initiator must log in to a storage array before the 

storage allows LUN configuration related to that initiator. As part of 

the boot process, the Unisys SafeGuard Solutions SAS agent performs 

SAN discovery, during which it logs in to all the storage targets from 

all virtual initiators. Therefore, once the Unisys SafeGuard Solutions 

SAS agent is running, and you have created virtual initiators 

(through the process of binding the host and virtual initiators) and 

the Brocade zone, it should be possible to set the LUN configuration 

for the virtual initiators. 

The best practice for changing the LUN configuration is: 

1. Set HI-VI binding, through which the WWNs are set for the 

virtual initiators. 

2. Create the Brocade zone (and add all virtual initiators and 

physical storage targets to the zone). 

3. For each host initiator that is referenced in the LUN 

configuration, substitute the WWN for the virtual initiator to 

which that host initiator is now bound. 

Zoning The following types of Fibre Channel entities should be zoned when 

deploying Unisys SafeGuard Solutions on the Brocade AP-7600B or 

PB-48K-AP4-18: 

◆ Host initiators 

◆ Physical storage targets 

◆ Virtual initiators 

◆ System virtual initiator 

◆ Virtual targets 

◆ RA initiator ports 

◆ RA target ports 


Table 2 lists the minimal zoning that you will need to define during 

deployment of Unisys SafeGuard Solutions, as instructed in “Unisys 

SafeGuard Solutions deployment procedure” on page 18. Note that 

working in frame redirect mode requires somewhat different zoning 

than working in multi-VI mode. The zones required when working in 

multi-VI and frame redirect modes are pictured in Figure 5 on 

page 14 and Figure 6 on page 15, respectively. 

You will create and populate each of these zones according to the 

instructions in the “Unisys SafeGuard Solutions deployment 

procedure”, which begin on page 18. 

Table 2 Required zoning 

Zone Members Multi-VI 

Front-end zone host initiator, virtual targets 

Brocade zone virtual initiator, physical storage targets 

Initiator-target 

zone a 


Frame 

redirect 

host initiator, physical storage targets 

RA front-end zone b RA initiator ports, appliance virtual targets 

RA target zone virtual initiator, system virtual initiator, RA target 

ports c 

RA initiator zone RA initiator ports, physical storage targets c 

 

 

a. In “Unisys SafeGuard Solutions deployment procedure” on page 18, it is 

assumed that this zone already exists prior to deployment. 

b. This zone is needed only when working with reservations. “Reservations” on 

page 15 provides details. It is not shown in Figure 5. 

c. When using RAs with two dual-ported 4 Gb HBAs (QLE24xx), each RA port can 

serve both as an initiator and as a target. 

13

Figure 5 Required zoning for multi-VI, without reservation support 


Figure 6 Required zoning for frame redirect, without reservation support 

It is possible to split these zones further, as needed. For example, 

when working in multi-VI mode, the front-end zone can be divided 

into several zones, where each contains a single host initiator and the 

relevant virtual targets. When working in frame redirect mode, the 

same can be done to the initiator-target zone. 

Reservations Since reservation commands (both SCSI-2 and SCSI-3) are forwarded 

to the target storage devices, the storage devices are reserved, but by 

a virtual initiator, rather than by a host. 


15

When replicating with Unisys SafeGuard Solutions, the RAs must be 

able to send I/O to these storage devices, even if they are reserved by 

some other initiator. The only way for the RA to reach the target 

storage is through a virtual target, and from there (to the target 

storage) by way of a virtual initiator. The RA cannot, however, use an 

existing virtual target to access the storage target, since each virtual 

target can use more than one virtual initiator to access the backend 

device, and each RA port accessing the virtual target must be bound 

to a single virtual initiator. 

Therefore, the RA uses a special virtual target, called an appliance 

virtual target (AVT) to enable it to access the storage target. 

Whenever you specify (in the Unisys SafeGuard Solutions 

Management Application or CLI) that a group side supports 

reservations, the Unisys SafeGuard Solutions SAS agent creates one 

AVT for each virtual initiator that represents a host initiator that has 

access to volumes within this group. For every LUN that the initiator 

may reserve, a corresponding LUN that points to the same physical 

storage LUN is created on the AVT. 

Because a single initiator may access LUNs on more than one storage 

target, the LUNs on the AVT may represent as many different storage 

targets as the number of storage targets on which the corresponding 

initiator can reserve LUNs. Also, all LUNs on the AVT are created in 

pass-through mode, so that I/Os sent to the AVT LUNs are not split 

(which would cause the I/Os to be sent back to the RA), but rather, 

are written directly to the storage target. Access to the AVT is limited 

so that only RA ports can access the LUNs on the AVT. 

When replicating a group that supports reservations, if the regular 

path to the target storage device returns a “Reservation conflict” 

error, the RA then checks other potential paths, including the AVTs. 

Since the RA cannot determine which host initiator is reserving the 

device, all existing AVTs are tried until one is found that allows access 

to the target storage. 

A list of 200 PWWNs is produced during installation of the Unisys 

SafeGuard Solutions SAS agent, and is placed in the file 

/thirdparty/recoverpoint/init_host/scimitar_wwns_list.txt on the 

BP module. The WWNs are unique for the switch. They are available 

for subsequent use by AVTs. 

The RA port must have access to the virtual target, so zoning must be 

set correctly according to the specification listed in “Zoning” on 

page 12. All of the WWNs from the scimitar_wwns_list.txt file should 

be zoned as AVTs. 


Scalability 

limitations 

The limitations of Brocade AP-7600B or PB-48K-AP4-18 resources 

when deployed with Unisys SafeGuard Solutions are published in 

the release notes for your release of Unisys SafeGuard Solutions. 

Limits are presented for the following parameters: 

◆ Host initiator-target nexuses 

◆ Total virtual entities, including virtual initiators, virtual targets, 

AVTs, and the system VI 

◆ Replicated LUNs 

◆ Total LUNs 

◆ ITLs 

It is important to review these limitations when planning the 

deployment of Unisys SafeGuard Solutions with your Brocade 

AP-7600B or PB-48K-AP4-18. 

Computing ITLs The total number of ITLs is the sum of host ITLs and AVT ITLs, 

where: 

◆ Host ITLs = number of LUNs to which a host initiator has access 

◆ AVT ITLs = RA initiator ports x Host ITLs (for which LUNs 

support reservations) 

For example, if the configuration includes the following: 

◆ 4 RA initiator ports 

◆ 2 host initiators 

◆ With access to 1000 LUNs 

◆ 700 of the LUNs support reservations 

◆ Use of 1 DPC 

Then the total number of ITLs is as follows: 

ITLs = [(2 host initiators) x (1000 LUNs)] + [(1400 host ITLs for which 

LUNs support reservations) x (4 RA initiator ports)] 

= 2000 + 5600 

= 7600 


17

If, however, using frame redirect, you are able to use both DPCs, then 

ITLs are calculated separately for each DPC. Hence, if the 

configuration in the first example is changed, as follows: 

◆ 500 (of the 1000 LUNs in the first example) are exposed to the 

hosts through DPC 0, and the remaining 500 are exposed through 

DPC 1 

◆ All 500 of the hosts in DPC 0 support reservations; 200 of the 

hosts in DPC 1 support reservations 

Then the total number of ITLs is as follows: 

ITLs = {ITLs for DPC 0} + {ITLs for DPC 1} 

= {[(2 host initiators) x (500 LUNs)] + [(1000 host ITLs for which 

LUNs support reservations) x (4 RA initiator ports)]} + {[(2 

host initiators) x (500 LUNs)] + [(400 host ITLs for which 

LUNs support reservations) x (4 RA initiator ports)]} 

= {1000 + 4000} + {1000 + 1600} 

= 7600 

Note: Beginning with Unisys SafeGuard Solutions 6.1, the system displays 

warnings whenever your system approaches or exceeds scalability limits for 

ITLs, virtual entities, and total LUNs. 

Unisys SafeGuard Solutions deployment procedure 

This section outlines the procedure for deploying Unisys SafeGuard 

Solutions on the Brocade AP-7600B or PB-48K-AP4-18, as well as tests 

that can be used to verify that the installation has been completed 

successfully. It is assumed that the Brocade devices, running the 

specified version of Fabric OS, have been installed prior to beginning 

this procedure. 

With multiple SAS-enabled Brocade switches, and with hosts running 

multipathing software, this process can be done nondisruptively by 

migrating one switch at a time. 

The procedure for deploying Unisys SafeGuard Solutions in a 

Brocade AP-7600B or PB-48K-AP4-18 environment is presented in 

this section as a single, consecutively numbered procedure, with the 

following primary tasks: 


Prepare Unisys SafeGuard 

Solutions for deployment 

Prepare the Brocade 

devices for deployment 

Primary task in procedure Steps 

Prepare Unisys SafeGuard Solutions for deployment 1–4 

Prepare the Brocade devices for deployment 5–10 

Deploy Unisys SafeGuard Solutions for this switch 11–20 

Configure Unisys SafeGuard Solutions for replication over the Brocade 

device 

To prepare for deploying Unisys SafeGuard Solutions in a Brocade 

AP-7600B or PB-48K-AP4-18 environment: 

1. Prior to Unisys SafeGuard Solutions deployment, verify that all 

hosts can access the storage and perform I/Os. Where multiple 

paths are available, verify I/O capability down all paths. 

2. Connect the RAs to the Brocade devices. 

3. Install Unisys SafeGuard Solutions on the RAs. The Unisys 

SafeGuard Solutions Replication Appliance Installation Guide 

provides RA installation instructions. 

4. If you are using multiple switches, and hosts are running 

multipathing software, and you want to deploy Unisys 

SafeGuard Solutions nondisruptively: 

a. Disable all paths for one of switches. 

b. Verify that I/O is running through the other paths. 

Run Steps 5 through 20, as presented in this section, for each Brocade 

device. If you are performing a nondisruptive installation, run these 

steps for the currently disabled switch: 

5. If working in frame redirect mode, ensure that the initiator-target 

zone (or zones) exist, and that LUN masking from the targets to 

the initiators is defined. 

6. Install the Unisys SafeGuard Solutions SAS agent on the Brocade 

AP-7600B or PB-48K-AP4-18: 

a. Ensure that the BP IP address is set. 

21–24 


19

Detailed information regarding the use of the ipaddrset 

switch CLI command is presented in the Brocade Fabric OS 

Command Reference Manual. 

b. Download the Unisys SafeGuard Solutions SAS agent 

installation file from Unisys Support Center 

(http:support.unisys.com), and copy the installation file onto 

the BP for the platform/blade. To do so: 

1. Log in to BP as root. 

2. Download the Unisys SafeGuard Solutions SAS agent 

binary file to the /tmp directory. 

3. Run: chmod +x agent_binary_file 

c. Run the installation package. When prompted, enter the 

hostname for the platform/blade. 

The name you enter here, appended with the IP address, 

forms the name of the splitter as it will be displayed by the 

Unisys SafeGuard Solutions Management Application. 

This creates the Unisys SafeGuard Solutions distribution 

under /thirdparty/recoverpoint, and also runs init_host to 

prepare the switch ID for the Unisys SafeGuard Solutions 

system. The installation creates a directory tree that contains 

everything needed for running the Unisys SafeGuard 

Solutions SAS agent on the switch. 

Note: The Unisys SafeGuard Solutions SAS agent is not yet activated. 

Also, the splitter is not yet recognized by Unisys SafeGuard Solutions; 

this will happen only after the virtual initiators are added to the RA 

target zone, as instructed in Step 13 on page 22. 

7. If not previously done during RA installation, create the RA 

initiator zone now, and add all RA initiators and physical storage 

targets to that zone. 

8. Reboot the switch. 

When the switch comes up, the Unisys SafeGuard Solutions SAS 

agent should be activated. You can verify that it is by using the 

kdrv status command, as presented in “Running the Unisys 

SafeGuard Solutions SAS agent” on page 25. 

If working in frame redirect mode, skip to Step 10 on page 21. 


9. If working in multi-VI mode, create the RA target zone and RA 

front-end zone as follows: 

a. On the BP, find the WWN for the system VI, which is labeled 

"system VI WWN" in the file: 

/thirdparty/recoverpoint/init_host/scimitar_wwns_li 

st.txt 

b. Create the RA target zone, and add the system VI and RA 

targets to it. This enables the RA to locate the Brocade-based 

splitter. 

c. Create the RA front-end zone, and add all RA initiators and 

appliance virtual targets (AVTs) to the zone. The AVT WWNs 

are listed in: 

/thirdparty/recoverpoint/init_host/scimitar_wwns_li 

st.txt 

Skip to “Deploy Unisys SafeGuard Solutions for this switch” on 

page 22. 

10. If working in frame redirect mode, create the RA target zone and 

RA front-end zone as follows: 

a. On the BP, run the script: 

/thirdparty/recoverpoint/install/zoning_script.sh 

The script creates the RA target zone 

(HOSTNAME_FR_RA_Target_Zone) and the RA front-end 

zone (HOSTNAME_RA_Front_End_Zone), and adds the 

system VI and all possible VI WWNs to the RA target zone, 

and the appliance virtual targets (AVTs) to the RA front-end 

zone. 

Alternatively, you can create those zones manually, using the 

WWNs list and zone creation examples located on: 

/thirdparty/recoverpoint/init_host/scimitar_wwns_ 

list.txt 

b. Add RA targets and RA initiators to the appropriate zone. 

Note: When using RAs with two dual-ported 4 Gb HBAs (QLE24xx), 

each RA port can serve both as an initiator and as a target, and 

should therefore be added to each zone. 


21

Deploy Unisys SafeGuard 

Solutions for this switch 

c. Add both zones to the effective configuration, and re-enable 

the configuration. 

Up to this point, no changes have been made to the data paths 

between hosts and targets. 

11. Use the Unisys SafeGuard Solutions Management Application or 

CLI to add the Brocade-based splitter to the Unisys SafeGuard 

Solutions configuration. 

If working in frame redirect mode, skip to Step 18 on page 23. 

12. This and the following steps (through Step 17 on page 23) apply 

only when working in multi-VI mode. 

Use the bind_host_initiators CLI command to configure host 

binding to virtual initiators, as in the following example: 

s1-bos> bind_host_initiators site=s1-bos 

splitter=myhostname_172.16.0.17 

host_initiators=10000000c92ab3bd 

Initiator binding(s) successfully added. 

The command returns the WWN of the virtual initiator that is 

bound to the host initiator. 

Note: The default value for the frame_redirect parameter is “no”; when 

working in multi-VI mode, it should not be changed. 

Alternatively, you can specify the virtual initiator that is to be 

bound to the host initiator; for example, so that the virtual 

initiator has the same WWN as the virtual initiator to which the 

host initiator was previously bound. To do so, add the following 

parameter to the bind_host_initiators command: 

virtual_initiator=60012482xxxxxxxx 

The WWN for the virtual initiator must always begin with the 

60012482 prefix, whether it is returned by the system or specified 

by the user. The remainder of this WWN, following the 60012482 

prefix, can be any value. 

Verify that virtual targets are created on the BP for each available 

target storage port. 

13. Add the virtual initiator WWNs that you obtained during the 

binding process to the RA target zone. 


14. Create the Brocade zone, and add all virtual initiators and 

physical storage targets to the zone. 

15. Define storage LUN masking for the virtual initiators according 

to the host binding scheme. 

For example, if host HI1 is bound to VI1, duplicate the LUN 

configuration defined for HI1 to VI1. 

16. Run rescan_san from the Unisys SafeGuard Solutions CLI, and 

then use the get_virtual_targets CLI command to obtain the list 

of virtual targets accessible to each host initiator. 

The following presents an example of the get_virtual_targets CLI 

command, run in interactive mode, together with the output 

generated: 

s1-bos> get_virtual_targets 

Enter the site name 

s1-bos 

Enter Brocade splitter name 

myhostname_172.16.0.12 

Host initiators: (default is all) 

1) 10000000c92ab3bd 

Select, or press 'ENTER': 

---------------------------------------------------- 

Host Initiator Virtual Target Original Port 

---------------------------------------------------- 

10000000c92ab3bd 70012482ff711a43 5006016210601a43 

70012482e7b41a43 5006016a10601a43 

Create the front-end zone, and add the host initiators and virtual 

targets to the zone. Alternatively, you can split the front-end 

zones further, as desired. For example, you can create zones 

where each contains a single host initiator and the relevant virtual 

targets. 

17. If, in multi-VI mode, you have been using a temporary 

host-physical targets zone—as mentioned in Step 5 on 

page 19—remove it now. 

Skip now to Step 19 on page 24. 

18. This step applies only when working in frame redirect mode. 

Use the bind_host_initiators CLI command to configure host 

binding to storage targets, as in the following example: 


23

Configure Unisys 

SafeGuard Solutions for 

replication over the 

Brocade device 

s1-bos> bind_host_initiators site=s1-bos 

splitter=sabre_172.16.0.17 

host_initiators=10000000c92ab3bd target=500611111111 

frame_redirect=yes 

Initiator binding(s) successfully added. 

Alternatively, you can add frame redirect bindings in the Unisys 

SafeGuard Solutions Management Application, by using Brocade 

bindings, under Splitter Properties. 

Whether you use the CLI or the Management Application, this 

command creates the virtual initiators and virtual targets that 

correspond to the host initiators and storage targets involved, and 

that enable the frame redirect mechanism to direct the data 

frames from the initiator to the target through the virtual entities. 

Each initiator should be bound to all targets that expose protected 

LUNs to it. You can bind multiple initiators to multiple targets. 

19. If you are deploying Unisys SafeGuard Solutions 

nondisruptively, enable the paths that you disabled in Step 4 on 

page 19. 

20. Verify that host initiators can see the virtual targets and the 

correct LUNs in them, and that I/Os continue properly. Verify 

that all paths over all switches are working. 

Repeat Steps 4 through 20 for another switch (or Steps 5 through 20 if 

the deployment is not nondisruptive). When you have completed all 

switches, proceed to the next step. 

Use the Unisys SafeGuard Solutions Management Application or CLI 

to configure Unisys SafeGuard Solutions replication: 

21. Configure all Unisys SafeGuard Solutions volumes and 

consistency groups. Do not attach volumes to the Brocade-based 

splitter. 

22. If using reservations, indicate that Reservations are supported. 

You should have already created the RA front-end zone, as 

instructed in Step 9 on page 21 if working in multi-VI mode, or 

Step 10 on page 21 if working in frame redirect mode. 

23. Verify host is able to continue I/Os through the virtual targets 

and applications are functioning properly. 

24. Attach volumes to the Brocade-based splitter, and enable the 

groups. This will induce an initial full-sweep of the volumes. 


Running and upgrading Unisys SafeGuard Solutions SAS agent 

Running the Unisys 

SafeGuard Solutions 

SAS agent 

When the Unisys 

SafeGuard Solutions 

SAS agent is 

stopped or crashes 

Upgrading the 

Unisys SafeGuard 

Solutions SAS agent 

This section presents information specific to the Unisys SafeGuard 

Solutions SAS agent, which is installed on the BP module. 

The following commands are useful when running the Unisys 

SafeGuard Solutions SAS agent on the BP module on the Brocade 

AP-7600B or PB-48K-AP4-18: 

◆ To run the agent: 

/thirdparty/recoverpoint/install/kdrv start 

◆ To check agent status: 

/thirdparty/recoverpoint/install/kdrv status 

◆ To stop the agent: 

/thirdparty/recoverpoint/install/kdrv stop 

If for any reason the Unisys SafeGuard Solutions SAS agent crashes, 

it is not possible to simply reactivate it. Note that crashing and 

stopping the Unisys SafeGuard Solutions SAS agent are basically the 

same. In both cases, virtual targets and virtual initiators created by 

the Unisys SafeGuard Solutions SAS agent continue to exist after it 

stops or crashes. 

To clear all the virtual targets and virtual initiators, the switch reboots 

automatically following a crash, except in the following conditions: 

◆ The agent was stopped manually, using the kdrv stop command, 

to allow maintenance or upgrade of the switch. 

◆ The agent detected and aborted a "reboot cycle", in which the 

agent repeatedly crashed upon initialization after reboots. 

The cause of this problem should be corrected before the switch is 

manually rebooted. 

To upgrade the Unisys SafeGuard Solutions SAS agent, run the 

following procedure: 

1. Stop the Unisys SafeGuard Solutions SAS agent. 

2. Install the new version of the Unisys SafeGuard Solutions SAS 

agent, per the instructions in Step 6 on page 19. 


25

Uninstalling the 

Unisys SafeGuard 

Solutions SAS agent 

! 

To preserve the current splitter settings and avoid full-sweep 

resynchronization, however, you must add the upgrade parameter 

to the command line for the command used to run the 

installation. 

Do not use the upgrade parameter if upgrade of the Unisys 

SafeGuard Solutions SAS agent is part of an upgrade of the SAS 

software, as presented in “Upgrading the SAS” on page 27, or 

part of a Unisys SafeGuard Solutions major release upgrade, as 

presented in the Unisys SafeGuard Solutions Replication Appliance 

Installation Guide. 

CAUTION 

Failure to add the “upgrade” parameter results in the loss of all 

current splitter settings. 

3. Reboot the BP. 

To uninstall the Unisys SafeGuard Solutions SAS agent: 

1. Delete the /thirdparty/recoverpoint folder from the BP. 


Useful Brocade CP commands 

The following commands are available through the CP CLI: 

◆ nsshow 

Shows items currently in the switch name server. For each target, 

shows its PWWN, NWWN, and symbolic name. Also shows VIs 

(“Brocade virtual Initiator-slot#,DPC#”) and VTs (“Brocade 

virtual target-slot#,DPC#”). 

◆ switchshow 

Shows switch information, including port information (WWN 

connected to the port, port status). 

◆ cfgshow 

Shows zoning configuration, including active and passive 

configuration and the zones included in each. 


Upgrading the SAS 

◆ firmwareshow 

Shows the version number for the fabric operating system (FOS) 

installed on the CP and the storage application services (SAS) 

installed on the BP. 

◆ ipaddrshow 

Shows the IP address of the CP module and BP module. 

◆ ipaddrset 

Sets the IP address of the CP module and BP module. 

◆ firmwaredownload 

Used to install the fabric operating system (FOS) on the CP and 

the storage application services (SAS) on the BP. 

◆ supportshow 

Outputs a range of diagnostic information about the switch 

configuration and status. It is generally recommended to direct 

this output to a file. 

The Brocade Fabric OS Command Reference Manual provides detailed 

information about these, and all other, switch CLI commands. 

It is recommended that you always upgrade to the latest SAS version. 

The procedure for upgrading the Unisys SafeGuard Solutions SAS 

agent only—that is, when not also upgrading the SAS—is presented 

in “Upgrading the Unisys SafeGuard Solutions SAS agent” on 

page 25. 

To upgrade the SAS: 

1. Back up the important files (same files as those you would keep 

when upgrading the switch) to an off-switch location, as follows: 

Note: When the SAS upgrade is part of a Unisys SafeGuard Solutions 

minor version upgrade (for example, Unisys SafeGuard Solutions 6.0 to 

6.1), a full sweep resynchronization will be required if you do not 

perform this backup. If, however, the SAS upgrade is part of a Unisys 

SafeGuard Solutions major version upgrade, you can skip this step, and 

go directly to Step 2. 


27

a. Run: 

thirdparty/recoverpoint/install/save_settings.sh 

This saves all the splitter settings to the 

/thirdparty/HOSTNAME_config.tar.gz backup file. 

b. Copy this backup file to a remote location. 

2. Upgrade SAS. 

3. Re-install the Unisys SafeGuard Solutions SAS agent, as 

presented in “Upgrading the Unisys SafeGuard Solutions SAS 

agent” on page 25. 

Do not use the upgrade parameter when re-installing the Unisys 

SafeGuard Solutions SAS agent. 

Note: Even if the agent files were still on the disk, the agent is not 

registered with new SAS until it is installed. 

4. Restore the files you backed up to the switch, as follows: 

Note: Skip this step if the SAS upgrade is part of a Unisys SafeGuard 

Solutions major version upgrade. 

a. Copy the HOSTNAME_config.tar.gz file to the /thirdparty/ 

folder on the BP. 

b. On the BP, run: 

/thirdparty/recoverpoint/install/load_settings.sh 

The previous configuration of the splitter should now be restored. 


6. If you have upgraded to Unisys SafeGuard Solutions 6.1, and are 

working in frame redirect mode, recreate the RA target zone and 

RA front-end zone, according to the instructions in Step 10 on 

page 21. 

Note: With dual-DPC support, the number of possible VIs and AVTs 

increases. Consequently, the zoning script (zoning_script.sh) adds a 

larger number of entities to each zone. 


Migrating from multi-VI to frame redirect 

If you are running Unisys SafeGuard Solutions in multi-VI mode 

(Unisys SafeGuard Solutions release 5.0 or 6.0), and you want to 

migrate to frame redirect mode (which is supported in Unisys 

SafeGuard Solutions release 6.0 and later), you should run the 

following procedure: 

1. Convert to the initiator-target binding scheme to allow host 

initiators direct access to the storage targets: 

a. If you are performing a nondisruptive installation, disable all 

paths for one of the intelligent Brocade devices. 

b. Use the unbind_host_initiators CLI command to remove all 

multi-VI bindings, as in the following example: 

s1-bos> unbind_host_initiators site=s1-bos 

splitter=sabre_172.16.0.17 

host_initiators=10000000c92ab3bd 

c. Delete the front-end and Brocade zones, and remove VI 

WWNs from the RA target zone. 

d. Create the initiator-target zone, according to the planned 

initiator-target binding scheme. 

e. Define storage LUN masking to the initiators, according to the 

host binding scheme (undo Step 15 on page 23). 

At this point you should be able to access the target directly from 

the initiator. 

Repeat Steps a–e for each intelligent Brocade device. 

2. Verify I/O capability on all paths. 

3. Before beginning deployment of Unisys SafeGuard Solutions in 

the new environment, do the following: 

a. If you need to upgrade the SAS, follow the instructions in 

“Upgrading the SAS” on page 27. 

b. If you need to upgrade your Unisys SafeGuard Solutions SAS 

agent to one that supports frame redirect, follow the 

instructions in “Upgrading the Unisys SafeGuard Solutions 

SAS agent” on page 25. 


29

Migrating from AP-7420B to AP-7600B 

Note: Do not use the upgrade parameter when installing the new 

Unisys SafeGuard Solutions SAS agent. 

When prompted for the hostname, enter the same name as in 

the previous installation of the Unisys SafeGuard Solutions 

SAS agent on this SAS. 

c. If you need to upgrade the RAs, follow the upgrade 

instructions presented in the Unisys SafeGuard Solutions 

Replication Appliance Installation Guide. 

4. Deploy Unisys SafeGuard Solutions, according to the instructions 

in “Unisys SafeGuard Solutions deployment procedure”, 

beginning with Step 10 on page 21. 

This section outlines the procedure for migrating Unisys SafeGuard 

Solutions volumes from an AP-7420B to an AP-7600B working in 

multi-VI mode, without incurring application downtime and without 

requiring full sweep resynchronization. 

Unisys SafeGuard Solutions release 6.0 does not support the Brocade 

AP-7420B. Customers using Unisys SafeGuard Solutions 6.0 must 

upgrade to AP-7600B (or, in the case of a blade, to PB-48K-AP4-18). 

Note: The procedure for migrating to a PB-48K-AP4-18 is very similar, but are 

not specifically covered here. 

The procedure assumes that hosts, storage ports, and RAs are 

connected directly to the AP-7420B and AP-7600B. If these 

components are not directly connected, but are in the same fabric as 

the AP-7420B, steps must be added to introduce the AP-7600B into 

the fabric and remove AP-7420B from the fabric. 

The procedure for migrating from an AP-7420B to an AP-7600B is 

presented in this section as a single, consecutively numbered 

procedure, with the following primary tasks: 


Preliminaries 1. Ensure that the correct Fabric OS, SAS, and Unisys SafeGuard 

Solutions SAS agent software has been installed on the AP-7600B. 

Connecting to the 

AP-7600B over one path 

Primary task in procedure Steps 

Preliminaries 1–3 

Connecting to the AP-7600B over one path 4–14 

Connecting to the AP-7600B over a second path 15–23 

The Unisys SafeGuard Solutions SAS agent should be up and 

running. You can check this with 

/thirdparty/recoverpoint/install/kdrv status command on the BP 

module. 

2. Ensure that AP-7420B has the necessary prerequisites to reduce 

the Unisys SafeGuard Solutions environment by one path (which 

will be introduced into the new AP-7600B environment), 

including: 

a. Two host HBAs, connected to the AP-7420B 

b. Two HBAs from each RA, connected to the AP-7420B 

c. Two storage ports, connected to the AP-7420B, zoned to the 

host HBAs, and with correctly masked volumes 

d. Unisys SafeGuard Solutions replication volumes, journal 

volumes, and repository volumes, all masked to all of the RAs 

3. Reconfigure multipathing software on the host, as necessary, to 

allow the use of only one path (since we will be removing one of 

the paths). This may include failing over all I/O to one path (that 

will be retained), or ensuring that both paths are active. 

4. Disconnect the following from the AP-7420B, and reconnect them 

to the AP-7600B: 

one host HBA 

one storage port (for which zoning and masking to the HBA 

are disconnected) 

one HBA from each RA 

5. Configure zoning on the AP-7600B as per the requirements. 


31

Note: At this point there are no VIs or VTs. 

6. Connect to the RA cluster IP and rescan the SAN, by running 

rescan_san from the Unisys SafeGuard Solutions Management 

Application (GUI) or CLI. 

This recognizes the AP-7600B as the splitter, since the system VI is 

zoned to the RA targets. 

7. Using the Unisys SafeGuard Solutions Management Application 

(GUI) or CLI, add the newly recognized splitter to the Unisys 

SafeGuard Solutions configuration. 

8. Bind host initiators to virtual initiators, using the 

bind_host_initiators command on the Unisys SafeGuard 

Solutions Management Application (GUI) or CLI. 

The command returns the WWN of the virtual initiator that has 

been created and bound to the initiator. 

9. After binding the virtual initiators to the host initiators, you must 

add the VIs to the zones and mask the VIs to the Unisys 

SafeGuard Solutions replication volumes on the storage port. 

This exposes the virtual targets to the host initiators. 


(GUI) or CLI, rescan the SAN, and use the get_virtual_targets 

CLI command to obtain the virtual target mapping. Then, add 

these virtual targets to the zone. 

11. Rescan the SAN volumes. 

You should now be able to see the new volumes that are to be 

attached to the AP-7600B splitter. 

12. Attach the volumes to the new splitter. Use the attach as clean 

option, so that no full sweep will be required. 

13. Reconfigure multipathing software on the host, as necessary, so 

that host uses the new path. This may include bringing the new 

path into multipathing software control, and ensuring support for 

I/O to the volumes seen through the new virtual targets. 

14. Ensure that the replication volumes, journal volumes, and 

repository volumes have at least one path each to/from both the 

AP-7420B and AP-7600B. The RAs also should see the repository 

and journal volumes from both platforms. 


Connecting to the 

AP-7600B over a second 

path 

15. Set up the requisite zoning on the AP-7600B for the second path 

that is to be added. 

Assuming you have predefined the names for the VIs, it should 

be possible to set up all the zoning except for virtual targets. 


ensure that even though the path though the AP-7420B will be 

removed, I/O will still supported through the VTs on the 

AP-7600B. This may include failing over all I/O to one path (that 

will be retained), or ensuring that both paths are active. 

17. Disconnect the following from the AP-7420B, and reconnect them 

to AP-7600B: 

second host HBA 

second storage port (for which masking to the HBA is 

disconnected) 

remaining HBA from each RA 

18. Bind the new host HBA to virtual initiators on the AP-7600B, 

using the bind_host_initiators Unisys SafeGuard Solutions CLI 

command. 


(GUI) or CLI, rescan the SAN, and use the get_virtual_targets 

CLI command to obtain the virtual target mapping. 

20. Mask the Unisys SafeGuard Solutions volumes to VIs assigned to 

the second HBA. 

21. Rescan the SAN. 

You should now be able to see the entire environment migrated to 

the new AP-7600B splitter. 

22. Unbind the host initiators from the AP-7420B splitter, and then 

remove the splitter. 


activate the new path. 

Migration is now complete. 


33

Troubleshooting 

Root file system is 

full 

Host initiators 

cannot write to 

virtual target 

You can use the following to diagnose and correct problems that may 

arise while operating the system. 

When the root (/) file system on the BP module is full, various 

problems may occur, such as an inability to run the Unisys SafeGuard 

Solutions SAS agent. 

Use the df command to check disk usage, and remove files from the 

file system. The core files under /thirdparty/recoverpoint/log are 

usually the cause for this problem. Unless they are needed for bug 

analysis, remove the core files, and reboot the switch. 

If host initiators are able to see the virtual target and the LUNs, but 

fail in writing to the storage, it is most likely a LUN-masking problem 

in the target storage device. 

Check the LUN configuration. 

Analysis pack The analysis pack is a set of scripts that is installed as part of the 

Unisys SafeGuard Solutions SAS agent installation package. These 

scripts enable on-site analysis of splitter logs, and extraction of 

important diagnostic information about current SAN view and SAN 

view changes. 

To execute the analysis scripts, run the following command on the 

BP: 

/thirdparty/recoverpoint/install/analysis_pack/log_analysis.sh 

The following parameters are valid: 

v Runs the view analysis, to display the latest san view. 

c Runs the changes analysis, to display the latest changes in SAN 

view (added and removed paths). 

i Runs the host ITL analysis, and displays and count ITLs per host. 

You must also choose at least one of the following: 

r Parse recovered logs (as created after a splitter crash). 

l Parse latest logs (host.log.00) 


To display on-screen syntax help, run the command without 

parameters: 

/thirdparty/recoverpoint/install/analysis_pack/log_analysis.sh 

For example, if you want to see the SAN view as the splitter sees it, 

run the command with the following parameters: 

/thirdparty/recoverpoint/install/analysis_pack/log_analysis.sh –vl 

The output of this command will contain the following: 

◆ Virtual Initiator information — For each VI: 

Port ID 

Corresponding initiator WWN 

VI WWN 

Whether it is in frame redirect mode 

In this example, there is one frame redirect VI and one system 

VI. There is always a system VI, and its port ID is always 0. 

VI information extracted from file: /thirdparty/recoverpoint/log/ram_log/host.log.00 

ID Bound Initiator VI WWN FR 

================================================== 

0 N/A (System VI) 0x60012482c6de1000 - 

1 0x5001248206ce4bc8 0x60012482c6de1001 + 

◆ SAN view — It is grouped by device GUID, and for each GUID it 

shows the relevant paths. The port number displayed is the port 

ID from the VI list. It also shows the size of the volume. Note that 

for the last device, there are 2 paths using the same GUID; both 

use LUN 1, since VI 1 can access the same volume through two 

different storage ports. 

If all zones are configured correctly, the Host SAN view should 

match the view of its corresponding Virtual Initiator. 

This portion of the output is shown on the following page. 


35

######################################################################### 

#### Parsing results from file /thirdparty/recoverpoint/log/ram_log/host.log.00 

######################################################################### 

######################################################################### 

#### View analysis 

######################################################################### 

Device information 

# WWN LUN Port Size (BLK) Size (MB) GUID 

========================================================================================== 

1 0x5001248205ae4bc8 0 1 2097152 1024 SHARK 

(73,66,77,32,32,32,32,32,50,49,48,53,32,32,32,32,32,32,32,32,32 

,32,32,32,50,53,48,50,54,32,32,32) 

2 0x5001248205ae4bc8 1 1 4194304 2048 SHARK 

(73,66,77,32,32,32,32,32,50,49,48,53,32,32,32,32,32,32,32,32,32 

,32,32,32,50,53,48,50,55,32,32,32) 

3 0x5001248205ae4bc8 2 1 6291456 3072 SHARK 

(73,66,77,32,32,32,32,32,50,49,48,53,32,32,32,32,32,32,32,32,32 

,32,32,32,50,53,48,50,56,32,32,32) 

4 0x5001248205ae4bc8 3 1 8388608 4096 SHARK 

(73,66,77,32,32,32,32,32,50,49,48,53,32,32,32,32,32,32,32,32,32 

,32,32,32,50,53,48,50,57,32,32,32) 

5 0x5001248205ae4bc8 4 1 10485760 5120 SHARK 

(73,66,77,32,32,32,32,32,50,49,48,53,32,32,32,32,32,32,32,32,32 

,32,32,32,50,53,48,51,48,32,32,32) 

6 0x5001248205ae4bc8 5 1 12582912 6144 SHARK 

(73,66,77,32,32,32,32,32,50,49,48,53,32,32,32,32,32,32,32,32,32 

,32,32,32,50,53,48,51,49,32,32,32) 

7 0x5001248205ae4bc8 6 1 14680064 7168 SHARK 

(73,66,77,32,32,32,32,32,50,49,48,53,32,32,32,32,32,32,32,32,32 

,32,32,32,50,53,48,51,50,32,32,32) 

8 0x5001248205ae4bc8 7 1 16777216 8192 SHARK 

(73,66,77,32,32,32,32,32,50,49,48,53,32,32,32,32,32,32,32,32,32 

,32,32,32,50,53,48,51,51,32,32,32) 

9 0x5001248205ae4bc8 8 1 18874368 9216 SHARK 

(73,66,77,32,32,32,32,32,50,49,48,53,32,32,32,32,32,32,32,32,32 

,32,32,32,50,53,48,51,52,32,32,32) 

10 0x5001248205ae4bc8 9 1 20971520 10240 SHARK 

(73,66,77,32,32,32,32,32,50,49,48,53,32,32,32,32,32,32,32,32,32 

,32,32,32,50,53,48,51,53,32,32,32) 

11 0x5001248205ae4bc8 10 1 23068672 11264 SHARK 

(73,66,77,32,32,32,32,32,50,49,48,53,32,32,32,32,32,32,32,32,32 

,32,32,32,50,53,48,51,54,32,32,32) 

12 0x50060e8014427506 1 1 6291840 3072 LIGHTNING 

(72,73,84,65,67,72,73,32,82,53,48,49,52,50,55,53,48,48,50,66) 

0x50060e8014427526 1 1 


© 2008 Unisys Corporation. 

All rights reserved. 

*38265294-001* 

3826 5294–001

SafeGuard Solutions Deploying Brocade AP-7600B and PB-48K ...

Create successful ePaper yourself

Delete template?

Save as template?