Asset ID: |
1-71-1009306.1 |
Update Date: | 2011-02-24 |
Keywords: | |
Solution Type
Technical Instruction Sure
Solution
1009306.1
:
Persistant Binding (with Leadville) for Shared FC Tape Drives Under NetBackup 5.1 Control
Related Items |
- Sun Storage SAN Foundation Software
- Sun StorageTek 9840B Tape Drive
- Sun StorageTek L700 Tape Library
- Sun StorageTek L180 Tape Library
|
Related Categories |
- GCS>Sun Microsystems>Storage - Tape>Drives - 9840
|
PreviouslyPublishedAs
212884
Applies to:
Sun StorageTek 9840B Tape Drive
Sun StorageTek L180 Tape Library
Sun StorageTek L700 Tape Library
Sun Storage SAN Foundation Software - Version: 4.0 and later [Release: 4.0 and later]
All Platforms
Checked for relevance on 25-Feb-2011.
Goal
The StorEdge[TM] Network Foundation HBA requires
special configuration steps to bind device World Wide Port Names (WWPN)
for use by the Veritas NetBackup sg driver.
In a shared storage
environment (where the same tape drive X can be used by both Windows and
Unix servers for backups and restores) it is critical that tape drives
do not change device paths. The mapping from say "/dev/rmt/0" to a
physical tape drive 2 can change after reconfiguration boots, after SAN
reconfigurations and after NetBackup configuration changes. However, if
the Solaris[TM] rmt device is bound to the World-wide Port Number (WWPN)
of the Tape drive, then it is no longer possible for such
reconfiguration events to impact the mapping of tape drive to physical
Solaris devices.
This document is intended as a guide for Customers who wish to
configure FC Tape drives under Netbackup control with the following
conditions:
1. The tape drives are Fibre Channel and SAN-based (that is connected via a switch).
2. The host bus adaptors on the server are using the Sun StorEdge HBAs
(Leadville stack) - that is the drivers are either qlc, jfca or emlxs.
This document assumes that the correct steps have been taken with
regard to SAN zoning, patching and general installation and
configuration of NetBackup.
Solution
Steps to FollowConfiguration Steps:
1. Create a backup copy of the current st.conf file:
# cp /kernel/drv/st.conf /kernel/drv/st.conf.orig
2. Move the existing sg.conf to a backup (this must be a move, otherwise a later step will fail):
# mv /kernel/drv/sg.conf /kernel/drv/sg.conf.orig
3. Create a backup copy of the current devlink.tab file:
# cp /etc/devlink.tab /etc/devlink.tab.orig
4. Delete SCSI targets/LUNs from the /kernel/drv/st.conf file:
name="st" class="scsi"
target=0 lun=0;
All of these entries should be removed, otherwise duplicates will be added later.
5. Delete SCSI targets/LUNs from /etc/devlink.tab. This is typically the section near the end of the file and the entries are typically of the form:
# begin SCSA Generic devlinks file - creates nodes in /dev/sg
type=ddi_pseudo;name=sg;addr=0,0; sg/c\N0t0l0
type=ddi_pseudo;name=sg;addr=1,0; sg/c\N0t1l0
type=ddi_pseudo;name=sg;addr=2,0; sg/c\N0t2l0
type=ddi_pseudo;name=sg;addr=3,0; sg/c\N0t3l0
type=ddi_pseudo;name=sg;addr=4,0; sg/c\N0t4l0
type=ddi_pseudo;name=sg;addr=5,0; sg/c\N0t5l0
type=ddi_pseudo;name=sg;addr=6,0; sg/c\N0t6l0
type=ddi_pseudo;name=sg;addr=0,1; sg/c\N0t0l1
type=ddi_pseudo;name=sg;addr=1,1; sg/c\N0t1l1
type=ddi_pseudo;name=sg;addr=2,1; sg/c\N0t2l1
type=ddi_pseudo;name=sg;addr=3,1; sg/c\N0t3l1
type=ddi_pseudo;name=sg;addr=4,1; sg/c\N0t4l1
type=ddi_pseudo;name=sg;addr=5,1; sg/c\N0t5l1
type=ddi_pseudo;name=sg;addr=6,1; sg/c\N0t6l1
# end SCSA devlinks
Everything in this section should be removed, inclusive of the beginning and ending lines.
6. Now add the WWPN of each tape drive to the sg.links as shown in the example following:
# cat /usr/openv/volmgr/bin/driver/sg.links
# SCSA Generic devlinks file - creates nodes in /dev/sg
#
# sg.links scsi and FC configuration
# Sun Microsystems
# February 2, 2005
#
type=ddi_pseudo;name=sg;addr=0,0; sg/c\N0t0l0
type=ddi_pseudo;name=sg;addr=w500104f000599150,0; sg/c\N6t\A1l0
type=ddi_pseudo;name=sg;addr=w500104f00059914d,0; sg/c\N7t\A1l0
type=ddi_pseudo;name=sg;addr=w500104f000599156,0; sg/c\N8t\A1l0
type=ddi_pseudo;name=sg;addr=w500104f000599153,0; sg/c\N9t\A1l0
# end SCSA devlinks
7. Edit the sg.conf file adding the same WWPN's as follows:
# cat /usr/openv/volmgr/bin/driver/sg.conf
# Configuration file for SCSA Generic.
#
# sg.conf scsi and FC configuration
# Sun Microsystems
# February 2, 2005
#
name="sg" class="scsi" target=0 lun=0;
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="500104f000599150";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="500104f00059914d";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="500104f000599156";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="500104f000599153";
8. Edit the st.conf file adding the same WWPN's, this time specifying which qlc instance the drive WWPN should bind to. In the example below two drives are bound to qlc instance 2 and two drives are bound to qlc instance 3:
# cat /kernel/drv/st.conf
# Copyright (c) 1995-2000 by Sun Microsystems, Inc.
# All rights reserved.
#
#pragma ident "@(#)st.conf 1.27 00/08/29 SMI"
#
#
# st.conf scsi and FC configuration
# February 2, 2005
#
# This line adds support for Fibre Channel Tapes
# name="st" parent="fp" target=0;
# Do not use the above fp parent line... we want persistant binding through
# specific HBA ports e.g qlc2 and qlc3
# name="st" class="scsi" target=0 lun=0;
name="st" class="scsi" hba="qlc2" wwn="500104f00059914d" target=0 lun=0;
name="st" class="scsi" hba="qlc2" wwn="500104f000599150" target=0 lun=0;
name="st" class="scsi" hba="qlc3" wwn="500104f000599153" target=0 lun=0;
name="st" class="scsi" hba="qlc3" wwn="500104f000599156" target=0 lun=0;
9. Don't forget to add the forceload statements to the /etc/system file:
# cat /etc/system
forceload: drv/st
forceload: drv/sg
forceload: drv/qlc
10. Edit the devlink.tab file CAREFULLY. Matching the Netbackup sg devices from the sg.conf to the appropriate WWPN. (Use only tabs between entries and not spaces).
# cat /etc/devlink.tab
# /etc/devlink.tab for SCSI and FC sg devices
# February 2, 2005
# type=ddi_pseudo;name=sg;addr=0,0;sg/c\N0t0l0
type=ddi_pseudo;name=sg;addr=w500104f000599150,0; sg/c\N6t0l0
type=ddi_pseudo;name=sg;addr=w500104f00059914d,0; sg/c\N7t0l0
type=ddi_pseudo;name=sg;addr=w500104f000599156,0; sg/c\N8t0l0
type=ddi_pseudo;name=sg;addr=w500104f000599153,0; sg/c\N9t0l0
11. Unload the sg driver:
# rem_drv sg
12. Generate the configuration files (st.conf, sg.conf and sg.links):
# /usr/openv/volmgr/bin/sg.build all
sg.build adds the proper entries to the sg.links and sg.conf files. Before running the script, make sure that all devices are powered on and connected to the HBA.
13. Use the provided script to re-create the /kernel/drv/sg.conf file with the appended SCSA entries in /etc/devlink.tab and reload the sg driver:
# /usr/openv/volmgr/bin/driver/sg.install
14. Now sgscan should see the appropriate devices:
# /usr/openv/volmgr/bin/sgscan all conf -v
Please Note: each time a new device is added or an old device removed, re-create and re-install the new sg configuration
15. Run sgscan. The script /usr/openv/volmgr/bin/sgscan checks for devices that are not configured, and produces output similar to the following example:
# /usr/openv/volmgr/bin/sgscan
#WARNING: detected StorEdge Network Foundation connected devices not in sg configuration file:
#
# Device World Wide Port Name 21000090a50001c8
#
# See /usr/openv/volmgr/MediaMgr_DeviceConfig_Guide.txt topic
# "Configuring the Sun StorEdge Network Foundation HBA/Driver"
# for information on how to use sg.build and sg.install
# to configure these devices
16. Run the following Solaris command and note any output:
# devfsadm -Cv
Check in the /etc/path_to_inst that Solaris has configured devices for both the st and sg drivers:
# cat /etc/path_to_inst
"/pci@8,700000/SUNW,qlc@3/fp@0,0/st@w500104f000599156,0" 32 "st" "/pci@8,700000/SUNW,qlc@3/fp@0,0/sg@w500104f000599156,0" 59 "sg" "/pci@8,700000/SUNW,qlc@3/fp@0,0/st@w500104f000599153,0" 33 "st" "/pci@8,700000/SUNW,qlc@3/fp@0,0/sg@w500104f000599153,0" 58 "sg" "/pci@8,700000/SUNW,qlc@2/fp@0,0/st@w500104f000599150,0" 34 "st" "/pci@8,700000/SUNW,qlc@2/fp@0,0/sg@w500104f000599150,0" 57 "sg" "/pci@8,700000/SUNW,qlc@2/fp@0,0/st@w500104f00059914d,0" 35 "st" "/pci@8,700000/SUNW,qlc@2/fp@0,0/sg@w500104f00059914d,0" 56 "sg"
Common Issues:
- Problems with the entries in the /etc/devlink.tab file (created from sg.links). Check the following:
* The first entry uses hexadecimal notation for the target and LUN.
* The second entry uses decimal notation for the target and LUN.
* Use a single tab character between the entries, NOT a space or a space and a tab.
- Did not configure the operating system to forceload the sg/st/qlc/jfca/emlxs drivers.
- Another commonly overlooked task is to increase the messages queues and shared memory in /etc/system
Reference: "Veritas NetBackup 5.1, Media Manager Device Configuration Guide", page 13 Chapter 2.
persistant, binding, NetBackup, leadville, qlc, st.conf, 5.1
Previously Published As 82276
Change History
Date: 2006-11-27
User Name: 95826
Action: Approved
Comment: - verified metadata
- changed review date to 2007-11-27
- checked for TM - none added
- checked audience : internal
Publishing
Version: 6
Date: 2006-11-27
User Name: 95826
Action: Accept
Comment:
Version: 0
Date: 2006-11-27
User Name: 39181
Action: Approved
Comment: All updates look correct. Technical data has been verified.
Version: 0
Product_uuid
cb37c818-a23f-11d9-9adf-080020a9ed93|Sun StorageTek SAN Foundation Software S10 Update 1
331852aa-146b-11d7-88af-9cb4cd4acaa0|Sun StorageTek 9840B Tape Drive
0ea7f2bc-de4b-11d7-9de1-080020a9ed93|Sun StorageTek LTO FC for L700/L180
2ad1aed8-0a18-11d6-90e0-ed11c048e8c6|Sun StorageTek L700 Tape Library
2ac5ccc6-0a18-11d6-8a03-a74e2320ffcd|Sun StorageTek L180 Tape Library
Attachments
This solution has no attachment