Konfiguracja switchy FC.pdf

(4929 KB) Pobierz
Application Notes
hp StorageWorks
Fabric Interoperability:
Merging Fabrics Based on M-Series and B-Series
Fibre Channel Switches
Sixth Edition (September 2006)
Part Number: AA-RUQQF-TE
This document summarizes information for planning a merge of separate SAN fabrics, where one fabric
consists of M-Series Product Line switches, and the other SAN fabric consists of B-Series Product Line switches.
This guide provides the techniques and best practices for such an implementation.
For the latest version of these Application Notes and other SAN documentation, access the HP storage website
.
917677595.012.png 917677595.013.png 917677595.014.png 917677595.015.png 917677595.001.png 917677595.002.png 917677595.003.png
© Copyright 2003, 2006 Hewlett-Packard Development Company, L.P.
Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied
warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for
incidental or consequential damages in connection with the furnishing, performance, or use of this material.
This document contains proprietary information, which is protected by copyright. No part of this document may be photocopied,
reproduced, or translated into another language without the prior written consent of Hewlett-Packard. The information contained in this
document is subject to change without notice.
Intel® and Itanium® are trademarks or registered trademarks of Intel Corporation in the U.S. and other countries and are used under
license.
Intel® Itanium™ Processor Family is a trademark in the U.S. and other countries and is used under license.
Microsoft®, MS-DOS®, MS Windows®, Windows®, and Windows NT® are U.S. registered trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.
Hewlett-Packard Company shall not be liable for technical or editorial errors or omissions contained herein. The information is provided
“as is” without warranty of any kind and is subject to change without notice. The warranties for Hewlett-Packard Company products are
set forth in the express limited warranty statements for such products. Nothing herein should be construed as constituting an additional
warranty.
Fabric Interoperability Application Notes
Sixth Edition (September 2006)
Part Number: AA-RUQQF-TE
2
Fabric Interoperability Application Notes
917677595.004.png
About this document
About this document
This section describes the content reflected in this document, including:
Intended audience , page 3
Related documentation , page 3
Topics
This document contains the following major topics:
Checklist for merging fabrics , page 4
Segmentation errors , page 34
Supported configuration rules , page 36
Troubleshooting , page 41
Glossary , page 42
Intended audience
This document is intended for customers who have separate SAN fabrics composed of
M-Series or B-Series Fibre Channel switches, and who wish to merge these fabrics.
Related documentation
Related documents with relevant information include:
Online Help/User Guide (accessible via the Web browser interface)
Installation Guide
Additional documentation, including white papers and best practices documents, are available
via the HP website at: http://www.hp.com ..
Changes from last version
Updated Figure 9 on page 12 to include the McDATA 4Gb SAN Switch for the HP p-class
BladeSystem.
Inserted a new Step 11 on page 27 for the McDATA 4Gb SAN Switch.
Updated Ta ble 2 on page 37 for revised B-Series supported firmware versions.
Updated Ta ble 3 by adding a row for the McData 4Gb SAN Switch for HP p-Class
BladeSystem.
Updated Ta ble 5 on page 39 for McDATA 4 Gb SAN Switch support.
Fabric Interoperability Application Notes
3
917677595.005.png
Checklist for merging fabrics
Checklist for merging fabrics
Complete the steps below before actually merging the fabrics:
Verify the correct version of firmware is installed on the HP M-Series and HP B-Series
products and also the correct version of High Availability Fabric Manager (HAFM) is
installed.
Ensure there are no duplicate domain ID’s.
Select an M-Series Director as the Principal Switch.
Ensure there are no duplicate zone/zone set names.
Ensure that B-Series and M-Series products have fabric zoning configured with WWN.
Ensure that M-Series and B-Series products comply with proper zone naming.
Ensure the fabrics are in the proper operating mode.
Ensure HP default settings are in effect on both B-Series and M-Series switches
Ensure M-Series ports are 1 Gbps for B-Series SAN Switch 8 and 16 models
Ensure M-Series ports are 2 Gbps for the B-Series SAN Switch 2/8 and 2/16 models
Ensure McData 4Gb SAN switch for HP p Class BladeSystem default settings are in effect
Disable Management Server if it is present
Ensure Fabric Binding and Enterprise Fabric Mode are disabled
Add the switches to the fabric one at a time.
Use HAFM for Zoning Activities.
Step 1: Verify application and firmware versions
Before merging the two fabrics (M-Series and B-Series), make sure:
The correct versions of HAFM is installed.
The correct versions of firmware are installed.
Refer to Tables 2 , 3 , 4 , and 6 to determine what versions are needed and if necessary, obtain
the latest versions of applications and firmware.
Step 2: Ensure there are no duplicate domain ID’s
When merging fabrics, you must ensure that no duplicate domain ID’s exist among the
switches between the two fabrics. For example, Figure 1 on page 5 shows two fabrics and the
domain ID’s assigned to the switches in each fabric. In the example, the M-Series domain IDs
of 1 and 2 are equivalent to the B-Series domain IDs of 97 and 98. If you tried to merge these
two fabrics, the merger would fail as the ISL’s would segment due to the duplicate domain
ID’s.
A requirement for merging fabrics is that all domain ID’s must be unique. In the example, you
would change the M-Series domain ID’s. See Figure 2 on page 5 for acceptable domain IDs.
Please note that M-Series and B-Series use different numbering schemes for their domain ID
numbers. For example, the M-Series domain 1 is equivalent to B-Series domain 97. See
Table 1 on page 6 for a chart showing the correlation between M-Series’s and B-Series’s
domain ID’s.
4
Fabric Interoperability Application Notes
917677595.006.png
Checklist for merging fabrics
Figure 1: Example of Duplicate Domain IDs (M-Series Conflicts with B-Series)
Figure 2: Example of Unique Domain IDs (M-Series Changed to Domains 4 & 5)
Fabric Interoperability Application Notes
5
917677595.007.png 917677595.008.png 917677595.009.png 917677595.010.png 917677595.011.png
Zgłoś jeśli naruszono regulamin