System Z End-To-End Extended Distance Guide

System Z End-To-End Extended Distance Guide

Front cover System z End-to-End Extended Distance Guide Why you should have an end-to-end connectivity strategy for System z What you should understand about the technology How you should plan your connectivity infrastructure Frank Kyne Jack Consoli Richard Davey Gary Fisher Iain Neville Mauricio Nogueira Fabio Pereira Giancarlo Rodolfi Ulrich Schlegel ibm.com/redbooks International Technical Support Organization System z End-to-End Extended Distance Guide March 2014 SG24-8047-00 Note: Before using this information and the product it supports, read the information in “Notices” on page ix. First Edition (March 2014) © Copyright International Business Machines Corporation 2014. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . ix Trademarks . .x Preface . xi Authors. xi Now you can become a published author, too! . xiii Comments welcome. xiii Stay connected to IBM Redbooks . xiii Chapter 1. Introduction. 1 1.1 Why we wrote this book . 2 1.1.1 The scope of this book . 2 1.2 Why you would have multiple data centers. 3 1.3 Common data center models . 4 1.3.1 Distances . 5 1.3.2 Connectivity solutions . 7 1.4 The importance of an end-to-end architecture . 7 1.4.1 End-to-end support structure . 9 1.4.2 Support models. 11 1.5 Role of the connectivity architecture group . 12 1.5.1 Scope of responsibility . 12 1.5.2 Configuration planning . 13 1.5.3 Problem determination . 14 1.5.4 Performance and capacity planning . 14 1.5.5 Documentation . 14 1.6 What needs to be connected . 15 1.7 Connectivity options . 16 1.7.1 Connecting devices over an extended distance . 18 1.8 System z qualification and testing programs. 23 1.8.1 IBM System z connectivity testing. 23 1.8.2 System Storage Interoperation Center . 28 1.8.3 Non-IBM storage vendors qualification . 28 1.8.4 Other platforms . 29 1.8.5 Standards for cables and connectors . 29 1.9 Planning for the future. 29 1.9.1 The evolution of data center networking . 30 1.9.2 Traditional data center network architecture. 31 1.9.3 The future of data center networking . 32 1.9.4 System z and ODIN . 34 1.10 Where to go for help . 36 1.11 Layout of this book . 37 1.11.1 Relationship to other documentation . 38 Chapter 2. Storage area network . 39 2.1 SAN overview . 40 2.2 Channel extension . 42 2.2.1 FCIP extension switches. 42 2.2.2 Switch port types. 44 © Copyright IBM Corp. 2014. All rights reserved. iii 2.3 SAN support for System z channel protocols . 45 2.3.1 Uses of SAN switches in a System z environment . 45 2.3.2 FC addresses and SAN ports . 48 2.3.3 FICON link addresses and FC addresses. 49 2.4 Extending the SAN . 52 2.4.1 Direct fiber ISLs . 55 2.4.2 ISLs through DWDMs . 56 2.4.3 Fibre Channel over IP (FCIP) . 57 2.5 Considerations for inter-switch link (ISL)-extended SANs. 58 2.5.1 When ISLs are appropriate . 58 2.5.2 Buffer credits. 59 2.5.3 Identifying the correct number of ISLs . 60 2.5.4 Configuring for availability. 60 2.5.5 Optics . 61 2.5.6 Managing and prioritizing traffic on ISLs. 64 2.5.7 Using DWDMs with ISL links. 64 2.5.8 Using DWDMs with ISL Trunks. 65 2.6 Considerations for FCIP-extended SANs . 69 2.6.1 QoS and propagation delay . 69 2.6.2 FCIP circuits, tunnels, and trunks . 70 2.6.3 IP planning and design . 72 2.6.4 Adaptive rate limiting. 73 2.6.5 FICON Acceleration . 75 2.6.6 FC Fast Write . 80 2.6.7 Monitoring and managing FCIP ports . 81 2.7 Switch features . ..

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    268 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us