7700 flash storage platform installation guide for

Document Number: 530-0267-00 Rev 02

7700 Flash Storage PlatformInstallation Guide

for Concerto Release 7.6.3.x

ii 7700 Flash Storage Platform Installation Guide 7.6.3.x 530-0267-00 Rev 02

LEGAL NOTICE

© 2014-2019 Violin Systems LLC. All rights reserved.

Violin and the Violin logo are registered trademarks of Violin Systems LLC. A complete list of Violin’s trademarks and registered trademarks is available at www.violinsystems.com/company/trademarks/

All other brands, product names, company names, trademarks, and service marks are the properties of their respective owners.

Violin Systems LLC2560 N. 1st Street, Suite 300San Jose, CA 95131USA

http://www.violin-memory.com/company/trademarks/

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

CHAPTER 1. Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77700 Flash Storage Platform Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77700 Flash Storage Platform Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

7700 FSP Component Reference Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117700 Flash Storage Platform Setup and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Setup and Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12Hardware Pre-Installation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Installation Checklists and Site Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13Installation and Configuration Task Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

CHAPTER 2. Connecting the 7700 Flash Storage Platform Hardware . . . . . . . . . . . . . . . . . . . . . . . . . 23Connectivity Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Connecting Cables to the 7700 FSP Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

7700 FSP Controller - Fibre Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267700 FSP Controller - iSCSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Connecting Cables to the Fibre Channel Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Connecting Cables to a Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

About the Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29Understanding Port Numbering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29Connecting Management Cables to 7700 FSP Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Connecting Cables to the Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Support for Controller-to-Controller Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

Connecting 7700 FSP Cluster Storage Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Connecting 7700 FSP Cluster Southbound Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Connecting Northbound Fibre Channel Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Connecting Northbound iSCSI Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Powering on the 7700 FSP Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Powering on a 7000 Series FSP/6000 Series Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42Powering on the FC Switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43Powering on 7700 FSP Controllers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

7700 FSP Power Down and Power Up Sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Required 7700 FSP Power Down Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Required 7700 FSP Power On Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

CHAPTER 3. 7700 Flash Storage Platform Device Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Device Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Configuring 7700 FSP Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Configuring 7700 FSP Storage Shelves. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Upgrading 7700 FSP Controllers and Shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51Configuring a 6000 Series Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51Configuring a 7000 Series FSP Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Using Symphony to Configure and Manage 7700 FSP Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

530-0267-00 Rev 02 7700 Flash Storage Platform Installation Guide 7.6.3.x iii

Contents

Adding Local Network Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Activating a Simple SetUp Configured Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Adding Stretched Cluster Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Creating and Managing Storage Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Creating and Managing LUNs on a Shelf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Creating and Managing SAN Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Configuring the 7700 FSP Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Default IP Addresses for the 7700 FSP Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Setting Up Management Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Configuring 7700 FSP Controllers at Initial Power On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Configuring 7700 FSP Controller Management Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Testing iDRAC Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Using the CLI to Set Hostname, DNS, NTP, and Domain Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Using Symphony to Set Up the 7700 FSP Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Configuring Brocade 6510 Fibre Channel Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Setting Up Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Next Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

CHAPTER 4. Southbound Fibre Channel Switch Zone Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 69Understanding a Fibre Channel Switch Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Managing the Zoning Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Confirming Southbound HBA Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Transferring the Zone Configuration to FC Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Copying a Zone Configuration into a Replacement FC Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Next Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

CHAPTER 5. Configuring Northbound Switches for Fibre Channel and iSCSI Operations . . . . . . . . 79Configuring Northbound Switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Configuring iSCSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Configuring 7700 FSP Controllers for iSCSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Configuring iSCSI Clients, Targets, and LUNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Configuring FC Ports in the FC Switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Configuring the 7700 FSP Controller Target and Initiator Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

APPENDIX A. System Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Configuring the 7000 Series FSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Configuring the Memory Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Enabling Callhome and E-mail Alert Setting for Memory Gateways and 7700 FSP Controllers . . . . . . . . . . 95Completing the ACM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Configuring Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Allocating the Storage Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Creating the Storage Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Enabling the Configuration Repositories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Verifying Storage Pools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Rescanning all Memory Gateway Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Setting up High Availability (HA) and Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Configuring High Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Completing the HA Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Enabling High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Enabling Dedup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Troubleshooting Memory Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Determining IP Addresses of Internal Memory Gateways (One Known, One Unknown). . . . . . . . . . . . . . . 113Determining IP Addresses of Internal Memory Gateways (Both Unknown). . . . . . . . . . . . . . . . . . . . . . . . . 114Error Messages When Logging in to Memory Gateways. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

APPENDIX B. Overview: 7700 FSP Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Understanding 7700 FSP Controller Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

iv 7700 Flash Storage Platform Installation Guide 7.6.3.x 530-0267-00 Rev 02

Contents

Monitoring 7700 FSP Controllers Using iDRAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Inspecting 7700 FSP Controller Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121Setting Up DNS and Domain Names in iDRAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123Setting Up Time Zones and NTP in iDRAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123Setting Up SNMP E-mail Alerts in iDRAC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123

APPENDIX C. Configuring Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Configuring Network Interfaces for Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Replication Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1257700 FSP Controller Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126Replication Network Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127Configuring Interfaces Using CLI Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129Using Symphony to Configure Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133Replication in an HA Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135

APPENDIX D. Configuring Brocade 6510 Fibre Channel Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Configuring Brocade 6510 for a 7700 FSP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Configuring the Brocade 6510 FC Switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140

APPENDIX E. Installing and Accessing Violin Symphony. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Installing Violin Symphony . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Accessing Symphony . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143

APPENDIX F. Configuring Stretched Cluster and Tiebreaker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Overview: Stretched Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Stretched Cluster Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146

Configuring a Stretched Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Identifying Northbound and Southbound Ports on 7700 FSP Controllers. . . . . . . . . . . . . . . . . . . . . . . . . . .149Disabling Target Mode on the Southbound Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149Inspecting the Discovered Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149Renaming LUNs and Minimum Stretched Cluster LUN Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149Creating Local and Remote Storage Pools on Site-A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150Creating a Configuration Repository/Mirror on Site-A. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151Creating Local and Remote Storage Pools on Site-B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151Creating a Configuration Repository and Mirror on Site-B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151Enabling HA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151Checking Failover Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152Enabling a Stretched Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152

Installing and Configuring Tiebreaker. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Tiebreaker Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152Downloading Tiebreaker Installation File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153Installing Tiebreaker on a Virtual Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153Installing Tiebreaker on an Independent Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154Configure Tiebreaker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155Manage Tiebreaker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157Tiebreaker Status Field Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158Tiebreaker Configuration Field Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159Modifying a Tiebreaker Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160Resume Tiebreaker Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161Sample Traps Sent by Tiebreaker. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161Setting Up Tiebreaker Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162Upgrading Tiebreaker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163

APPENDIX G. Managing HA Using CLI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Enabling and Disabling HA Using CLI Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167Verifying the Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167

530-0267-00 Rev 02 7700 Flash Storage Platform Installation Guide 7.6.3.x v

Contents

Troubleshooting HA Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

APPENDIX H. Compliance Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

FCC Class A Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Regulatory Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177Regulatory Model Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178Installation Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Network Connected Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Electrostatic Discharge (ESD) Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Lithium Battery Caution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182Cabinet Safety Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Disposal of Waste Equipment by Users in Private Households in the European Union . . . . . . . . . . 184Perchlorate Material - Special Handling May Apply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185European Union RFI Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186USA Radio Frequency Interference FCC Notice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187Japan Radio Frequency Interference VCCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188Korea RFI Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189Canada RFI Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190CISPR 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Australia C-Tick Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Taiwan BSMI Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193Four-in-One Recycling Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194Product Information for People’s Republic of China . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

vi 7700 Flash Storage Platform Installation Guide 7.6.3.x 530-0267-00 Rev 02

Preface

This preface outlines the organization of this book, describes document conventions, and provides information about additional resources.

• Intended Audience on page 1

• About This Guide on page 1

• Document Organization on page 2

• Reference Documents on page 3

• Replacement Procedures on page 4

• Document Conventions on page 4

• Contacting Violin Systems on page 5

Intended Audience

This guide is intended for experienced systems administrators. Violin Systems assumes that you are experienced in installing and servicing high-performance storage systems.

Contact Violin Systems Customer Support for any assistance with installing and servicing this system. See Contacting Violin Systems on page 5 for contact information.

About This Guide

This guide describes the hardware installation and first-time system configuration of a 7700 Flash Storage Platform system running on Concerto version 7.6.3.1 or later.

The CLI samples used in this document are from Concerto version 7.6.3.1. They are also relevant to more recent versions of Concerto that were released after the 7.6.3.1 release.

530-0267-00 Rev 02 7700 Flash Storage Platform Installation Guide 7.6.3.x 1

Preface

For other Violin Systems installation guides, see the Violin Systems Support site at http://www.violinsystems.com/support/

Document Organization

This guide is organized into the following sections:

• Chapter 1, Overview—Describes the 7700 Flash Storage Platform system components and configuration process.

• Chapter 2, Connecting the 7700 Flash Storage Platform Hardware—Describes how to install a 7700 Flash Storage Platform system, including Violin Symphony, 7000 Series Flash Storage Platforms (FSPs) and 6000 Series storage shelves, 7700 FSP Controllers, and Fibre Channel (FC) switches.

• Chapter 3, 7700 Flash Storage Platform Device Configuration—Describes the process for performing an initial configuration of the 7700 Flash Storage Platform.

• Chapter 4, Southbound Fibre Channel Switch Zone Configuration—Describes and provides an example of the fabric switch zone configuration that represents the southbound path from the 7700 FSP Controllers to the shelf choices in your system.

• Chapter 5, Configuring Northbound Switches for Fibre Channel and iSCSI Operations—Describes and provides instructions for configuring northbound client network switches for both Fibre Channel and iSCSI operations, and describes and provides instructions for configuring iSCSI, and describes and provides instructions for configuring FC pots in the FC switches.

• Appendix A, System Reference—Provides reference information and procedures for performing a manual configuration of the Memory Gateways on the FSPs, other key settings for the 7700 Flash Storage Platform system, and also provides a description of the key components of the 7700 FSP Controller, and provides procedures for using iDRAC to inspect, monitor, and modify management settings and e-mail alerts.

• Appendix B, Overview: 7700 FSP Controller—Provides a brief overview of the 7700 FSP Controller and contains tables and figures that describe the 7700 FSP Controller chassis front and rear panel components, and the status LEDs for the power supply units in the chassis.

• Appendix C, Configuring Replication—Describes replication, provides reference information, and provides a procedure for configuring the network interfaces to support replication in a 7700 FSP storage cluster.

• Appendix D, Configuring Brocade 6510 Fibre Channel Switches—Provides reference information, and provides procedures for setting up and configuring Brocade 6510 Fibre Channel switches.

• Appendix E, Installing and Accessing Violin Symphony—Provides reference information about installing Violin Symphony and contains a procedure for accessing Violin Symphony using a supported web browser.

• Appendix F, Configuring Stretched Cluster and Tiebreaker—Provides an overview that describes stretched cluster basics, provides prerequisites for installing a stretched cluster and instructions for configuring a stretched cluster, and provides instructions on installing, configuring, and managing the Tiebreaker utility to prevent any issues if failover servers ever lose communication with each other in a stretched cluster environment.

• Appendix G, Managing HA Using CLI Commands—Describes how to manage, enable, and disable High Availability (HA) in the 7700 FSP using CLI commands, and also provides a table that lists and describes how to troubleshoot and resolve potential HA issues.

• Appendix H, Compliance Information—Provides compliance information that supports the Violin 7700 Flash Storage Platform.

2 7700 Flash Storage Platform Installation Guide 7.6.3.x 530-0267-00 Rev 02

http://www.violin-systems.com/support/


Preface

Reference Documents

In addition to this guide, the following Violin Systems documents comprise the documentation suite that will assist you with setting up, using, and servicing an array and 7700 FSP Controllers. These guides are available for download from the Violin Systems Support site at:

http://www.violinsystems.com/support/

This document... Provides this information...

7000 Series Flash Storage Platform Release Notes This document describes the new features, resolved issues, known limitations, and software upgrade instructions for the current release of the 7700 and 7000 Series Flash Storage Platforms.

Violin 7000 Series Flash Storage Platform User’s Guide

This guide provides instructions for managing, monitoring, and maintaining both 7700 and 7000 Series FSPs in a 7700 FSP environment.

Violin 7000 Series Flash Storage Platform Installation Guide

This guide provides instructions for performing a hardware installation and first-time setup of the 7000 Series FSP in various configurations.

Violin 6000 Series All Flash Array User’s Guide This guide provides instructions for managing, monitoring, and maintaining an FSP or array using the Violin Web interface and Command Line Interface (CLI).

Violin 6000 Series All Flash Array Service Guide This guide describes how to safely replace the system components in a Flash Array.

Violin 7000 Series Flash Storage Platform Service Guide

This guide describes how to safely replace the system components in the Violin 7000 Series Flash Storage Platform.

Concerto Command Line Interface Reference This guide is a reference for the Concerto OS software commands used to configure, manage, and monitor the Memory Gateways.

Aria Command Line Interface Reference This guide provides all of the command modes, lists syntax conventions, and abbreviations for the commands available in the Aria command line interface (CLI). These CLI commands allow you to monitor, configure, and manage the Array Controller Modules (ACMs).

Violin Symphony Installation Guide This guide provides instructions for installing, configuring, and launching Violin Symphony.

Reference Documents



Preface

Also, see the following for additional information about the hardware devices that accompany the shelf in a 7700 Flash Storage Platform system:

• For additional information about the 7700 FSP Controller hardware, see the documentation for the Dell R720 appliance at http://www.Dell.com

• For additional information about the Brocade Fibre Channel switches, see the following Brocade product documentation:

— Brocade 6510 Hardware Reference Manual, at http://www.brocade.com

— Fabric OS Administrators Guide, at http://www.brocade.com

Replacement Procedures

• For instructions on replacing modules in these devices, see the latest version Violin 6000 Series All Flash Array Service Guide or the Violin 7000 Series Flash Storage Platform Service Guide.

• Contact Violin Systems Customer Support if a component within a 7700 FSP Controller or a Fibre Channel switch requires replacement.

Document Conventions

This section explains the meanings of the safety icons used in this guide, as well as the typological conventions.

Safety Icons

The table below summarizes warning, caution, and note icons used in this document and includes sample text.

Safety Icons

Icon Sample Text

WARNING! WARNING! Only authorized, qualified, and trained personnel should attempt to work on this equipment.

Caution: Caution: Follow the listed safety precautions when working on the 7000 Series Flash Storage Platforms.

Note: Note: Read through this entire chapter and plan your installation according to your location before installing the equipment. The following procedures and the order in which they appear are general installation guidelines only.


http://www.dell.com

http://www.dell.com

http://www.brocade.com/index.page

http://www.brocade.com/downloads/documents/html_product_manuals/B6510_HRM_08/GUID-072F86BC-6B54-410E-A08F-FD3140DDF5B3.html

Preface

Typographical Conventions

The following typographic conventions are used in this guide:

Security

Violin Systems LLC, cannot be responsible for unauthorized use of equipment and will not make allowance or credit for unauthorized use or access.

Contacting Violin Systems

To obtain additional information or technical support for Violin Systems products, contact us at:

• Phone: 1-855-VIOLIN-5 (1-855-846-5465)

• International: +1 650-396-1500 Extension 3

• Website: http://www.violinsystems.com/support/

• Support E-mail: [email protected]

When contacting Violin Systems Customer Support, please have the following information available:

• Model and serial number of the system for which you are requesting support.

• Software version.

• A brief description of the problem.

• Command Line Interface or web interface access to the affected system.

• The output of the show alarms and vdiag diagnostic commands.

Format Meaning

Bold User Interface text.

Italic Provides emphasis and identifies variables and document titles.

Courier Command names, examples, and output.

Courier bold Input you must type exactly as shown.

<Courier italic> Information for which you must supply a value.

[ ] Optional command parameters are enclosed within square brackets.

| Separates a set of command choices from which only one may be chosen.

{ } Required command parameters that must be specified are enclosed within curly brackets.

Typographical Conventions


http://www.violin-systems.com/

[email protected]

Preface


CHAPTER 1 Overview

This chapter provides an overview of the supported 7700 Flash Storage Platform configurations and the processes for installing and configuring 7700 Flash Storage Platform (also referred to as 7700 FSP) appliances on your network. The following topics are covered:

• 7700 Flash Storage Platform Terminology on page 7

• 7700 Flash Storage Platform Components on page 9

• 7700 Flash Storage Platform Setup and Configuration on page 12

7700 Flash Storage Platform Terminology

The table below introduces and describes the terminology used in the 7700 Flash Storage Platform.

Term Description

7700 Flash Storage Platform (FSP)

The 7700 FSP modular storage cluster consists of two 7700 FSP Controllers, one (or more) 7000 Series FSPs or 6000 Series storage shelves, and two Brocade® 6510 Fibre Channel (FC) switches (or four Brocade® 6510 FC switches in a stretched cluster).

7700 FSP Controller

Hardware appliance pre-installed with the Concerto 7.x Operating System (OS) software, which manages the data stored in a 7700 FSP modular storage cluster. The 7700 FSP Controller manages and communicates with the FC switches and each storage shelf in the 7700 FSP.

Table 1.1 7700 Flash Storage Platform Terminology


Chapter 1 - Overview

7000 Series FSP The 7000 Series of Flash Storage Platforms (FSPs) can be of any of the following model types: • 7300 FSP, equipped with 1TB x 64 VIMMs

• 7300E FSP, equipped with 1TB x 32 VIMM7600-2G, equipped with 2TB x 64 VIMMs

• 7600-1G, equipped with 1TB x 64 VIMMs

• 7250-1D, equipped with 1TB x 24 VIMMs

• 7450, 500MHz, equipped with 1TB x 24 VIMMs, 1TB x 64 VIMMs, 2TB x 64

• VIMMs

• 7650, 500 MHz, equipped with 1TB x 24 VIMMs, 1TB x 64 VIMMs, 2TB x 64

• VIMMs

All 7000 Series FSPs can be configured as storage shelves in the modular 7700 FSP storage cluster, and you can add or remove capacity at the storage shelf level. Each 7000 Series FSP shelf is a single, integrated storage device that runs Concerto OS 7.x and Aria 7.x. When a 7000 Series FSP is single, standalone and not connected to a 7700 FSP Controller, it is known as an array.

Note: Throughout the rest of this guide, generic FSP or 7000 Series FSP references are used interchangeably to indicate any 7000 Series FSP model. Only where a specific difference exists or a distinction needs to be made, will the specific FSP model number be noted.

6000 Series FSP The 6000 Series storage devices can be of any of the following model types:• 6600, equipped with 1 x 64 VIMMs

• 6200, equipped with 1 x 64 VIMMs

• 6100, equipped with 1 X 32 VIMMs

These 6000 Series units can be configured as storage shelves in the modular 7700 FSP, you can add or remove capacity at the storage shelf level. Each 6000 Series unit is a single, integrated storage device that runs vMOS 5.x or vMOS 6.x. When 6000 Series are single, standalone units, and not connected to a 7700 FSP Controller, they are known as storage arrays.

Simple SetUpTM Configuration Tool

Simple SetUpTM Editor is a web-based configuration tool that creates array configuration (.cfg) files for any 7000 Series FSP used as standalone array or as a storage shelf in a 7700 FSP modular storage cluster. You create .cfg files based on the configuration values you specify, and using the .cfg file, you can rapidly configure multiple storage arrays in any Enterprise data center using the same .cfg file as a template or a modified version you create using this utility.

Dedup Violin Systems’s in-line storage deduplication and compression feature. Compression is data encoding so that it requires less space for storage and less time to transmit. Deduplication is a specialized form of compression that eliminates the storage of redundant data, improves storage utilization, and in SAN data transfers, reduces the number of bytes needing to be transferred. Deduplication identifies unique chunks of data or byte patterns when analyzed and stored. When further data analysis is done, new data is compared with the stored dedup data, and if a match is made, this makes the data redundant and eliminates the need to store or transfer it.

Term Description

Table 1.1 7700 Flash Storage Platform Terminology(Continued)


7700 Flash Storage Platform Components


The 7700 Flash Storage Platform (FSP) is an independent, switched fabric Fibre Channel storage cluster managed and monitored by Symphony.

7700 Flash Storage Platform—Two 7700 FSP Controllers connect to one to 10 Violin Systems FSPs (7000 Series) or 6000 Series storage shelves through two Brocade® 6510 Fibre Channel (FC) switches (or four Brocade® 6510 FC switches in a stretched cluster). The modular nature of the 7700 FSP allows you to add storage capacity as needed, and it can consist of a mix of the following:

• 7000 Series FSPs

— 7300

— 7300E

— 7450

— 7600

— 7650• 6000 Series arrays

Northbound Connections

Northbound connections refer to cable connections made between the 7700 FSP Controllers in the 7700 FSP cluster and the network switches in the client network (also known as upstream connections). For inter-cluster cable connections, see Southbound Connections.

Southbound Connections

Southbound connections refer to cable connections made between the 7700 FSP Controllers, the Brocade 6510 Fibre Channel switches, and the 7000/6000 Series storage shelves in the 7700 FSP cluster (also known as downstream connections). For client network-facing cable connections, see Northbound Connections.

Stretched Cluster 7700 FSP modular storage clusters that are configured in multiple locations, which allow one 7700 FSP Controller to fail over to a partner 7700 FSP Controller located at a remote site that can be located on a different floor in the same building or in a remote building located across town. For details, see Appendix F, "Configuring Stretched Cluster and Tiebreaker", on page 145.

Switch Brocade 6510 Fibre Channel switch used in the 7700 FSP cluster to perform internal storage area networking.

Symphony Violin Systems’s GUI-based management platform for configuring, managing, and monitoring any of the installed 7700 FSP components (shelves and controllers) over a standard Web browser console. The browser and computer from which you run Symphony needs connectivity to the network segment where the storage shelves and controllers are running, because it communicates directly with the server and clients.

VIMM Violin Intelligent Memory Modules are bundled NAND flash memory that function as storage memory in the FSPs. VIMMs are an effective solution for delivering the advantages in flash memory to the data center. VIMMs function as a hardware-based Flash Translation Layer within the Flash Fabric Architecture (FFA), which provide the Flash Storage Platform (FSP) with both data storage and a means to manage error and fault. Data is written to and read from VIMMs, and for maximum performance, VIMMs are where data is written to and from in each array, and VIMMs are hot-swappable components in each array.

Term Description

Table 1.1 7700 Flash Storage Platform Terminology(Continued)

530-0267-00 Rev 02 7700 Flash Storage Platform Installation Guide 7.6.3.x 7.6.3 9


— 6600

— 6200

— 6100

The 7700 Flash Storage Platform storage cluster also supports a stretched cluster configuration. Stretched clusters are 7700 Flash Storage Platform clusters that have the 7700 FSP Controllers configured and located in two different locations.

A stretched cluster enables a 7700 FSP Controller to fail over to its partner or standby 7700 FSP Controller located at another remote site. For basics, see Overview: Stretched Clusters on page 145. For details, see the latest version Concerto 7700 FSP stretched cluster Implementation and Best Practices Guide.

The 7700 Flash Storage Platform supports either Fibre Channel or iSCSI network connections to provide block storage services and perform data transfers in SAN environments. Fibre Channel or iSCSI connections are used for northbound connections from the 7700 FSP. Only Fibre Channel is used for 7700 FSP southbound cluster connections.

Note: The term southbound refers to cable connections made between the 7700 FSP Controllers, the Brocade 6510 FC switches, and any shelf configured in the 7700 FSP system. The term northbound refers to cable connections made between the 7700 FSP Controllers and the network switches in the client network.

Figure 1.1 on page 11, is an illustration that shows a generic configuration that consists of two 7700 FSP Controllers, two Brocade 6510 Fibre Channel switches, and four 7000 Series FSP storage shelves connected and aligned in an example southbound configuration.

To view an example that illustrates specific southbound connections between the 7700 FSP storage cluster components (7700 FSP Controller/FC switches/7000 Series FSP-6000 Series storage shelves), see Figure 2.9.

To view an example that illustrates specific northbound connections between 7700 FSP storage cluster components (7700 FSP Controller and client network switch), see Figure 2.11 (for Fibre Channel northbound) and Figure 2.12 (for iSCSI northbound).



Figure 1.1 Violin 7700 Flash Storage Platform Storage Cluster (Southbound Connections Only)

7700 FSP Component Reference Conventions

This guide uses the following reference conventions in figures, tables, and text for 7700 FSP cluster components:

• 7700 FSP Controllers: 7700 FSP Controller A and 7700 FSP Controller B

• Brocade 6510 Fibre Channel (FC) switches: FC Switch A and FC Switch B

• 6000 Series or 7000 Series FSP shelves: Shelf 1 and Shelf 2

• Memory Gateways (MG): MG-A and MG-B

• Array Controller Modules (ACM): ACM-A and ACM-B

This guide uses the following abbreviation conventions in cable labels to refer to the following 7700 FSP cluster components:

• Shelves are "SH" (1-10)

• Memory Gateways in a shelf are "MG" (A or B)

• Brocade 6510 Fibre Channel switches are "SW" (A or B)

• 7700 FSP Controllers are "CT" (A or B)

7700 FSP Controllers

Shelves

Switches



Note: See Table 2.5 for a complete list of the 7700 FSP cluster system cable connections using this label abbreviation format.

Create host and device names in the 7700 FSP cluster based on your own network naming conventions, and assign them to the 7700 FSP components. Violin provides device and cable references in this guide that are meant to serve only as guidelines in identifying components.

7700 Flash Storage Platform Setup and Configuration

This section provides an overview of the process for installing, setting up, configuring, and connecting a new 7700 Flash Storage Platform system.

Setup and Configuration Tasks

The 7700 Flash Storage Platform setup and configuration process includes the following sections and related tasks, which should be performed in the order listed below:

Hardware Pre-Installation Information

Before you attempt to install any of the 7700 Flash Storage Platform storage cluster hardware, you must collect all of the necessary management and site-related information listed in the Customer Requirements Documents from Violin Systems.

Violin Systems recommends using the Customer Requirements Documents to capture the customer network deployment site environment as the first step in the installation process leading to a successful installation. You must complete this effort prior to the start of the actual installation.

Customer Requirement Documents serve as a series of information gathering checklists that you need to complete and provide to the customer during the initial installation planning stage of the deployment process. The checklists in the Customer Requirement Documents are used to define and plan the execution of the on-site installation as well as define the completion criteria.

Customer Requirement Document checklists cover the following installation and site-specific information that help ensure a successful installation and remove unnecessary delays:

• Environment requirements

• Firewall ports

• Network equipment information (including IP addresses for all Violin products to be installed)

Task 1: Hardware Pre-Installation Information on page 12

Task 2: Connectivity Overview on page 24

Task 3: Connecting Cables to the Fibre Channel Switches on page 28

Task 4: Connecting 7700 FSP Cluster Storage Devices on page 33

Task 5: Powering on the 7700 FSP Devices on page 42



• Management information

• SAN information

• Host server information

• Operating system information

• Application information

• Storage feature requirements

• General deployment site or required technical service information to expedite installation

Installation Checklists and Site Information

This section provides references to the hardware pre-installation checklists found in the Customer Requirements Documents for each of the 7700 FSP components, and also provides important site information for the 7700 FSP storage cluster, and CAT5/CAT6 physical cable information that you should consult prior to installation. Before starting to install any hardware, review the following sections:

• 6000 Series Checklist Information on page 13

• 7000 Series FSP Checklist Information on page 14

• 7700 FSP Controller Checklist Information on page 15

• Brocade 6510 Fibre Channel Switch Configuration Checklist on page 15

• Symphony Installation Requirements Checklist on page 16

• Physical Cabling Information on page 19

6000 Series Checklist Information

Ensure that you have read and completed all of the checklists listed in the Customer Requirements Document for Violin 6000 Series storage arrays, and then address the following tasks:

• Ensure that each network-manageable shelf and subcomponents have unique suffixes that conform with the customer network-naming conventions.

• Ensure that you address the following when installing 6000 Series arrays:

— The callhome.vmem.com may not be reachable via TCP port 25 due to corporate firewall security restrictions (TCP port 25 is a default, and you may need to use another customer-approved TCP port).

— When setting up callhome and e-mail alerts, use these parameters: -ss (customer mail relay host name or IP address) and -mf (customer e-mail address). For details, see Enabling Callhome and E-mail Alert Settings on page 95.

— Because time synchronization inside the 7700 FSP and its related components is so important, ensure that you specify multiple Network Time Protocol (NTP) servers.

— Ensure that you include an e-mail address for the local receipt of logs, in addition to the standard Violin Systems Support address.



7000 Series FSP Checklist Information

Ensure that you have read and completed all of the checklists listed in the Customer Requirements Document for Violin 7000 Series storage arrays, and then address the following tasks:

Note: For the remainder of this guide, 7000 Series and FSP has been used interchangeably to identify any of the 7000 Series FSP models (for specific details on supported 7000 Series FSP model types, see 7700 Flash Storage Platform Terminology on page 7, or 7700 Flash Storage Platform Components on page 9).

• Ensure that each network-manageable shelf and subcomponents have unique suffixes that conform with the customer network-naming conventions.

• Ensure that you address the following when installing 7000 Series FSPs:

— The callhome.vmem.com may not be reachable via TCP port 25 due to corporate firewall security restrictions (TCP port 25 is a default, and you may need to use another customer-approved TCP port).

— When setting up callhome and e-mail alerts, use these parameters: -ss (customer mail relay host name or IP address) and -mf (customer e-mail address). For details, see Enabling Callhome and E-mail Alert Settings on page 95.

— Because time synchronization inside the 7700 FSP and its related components is so important, ensure that you specify multiple Network Time Protocol (NTP) servers.

— Ensure that you include an e-mail address for the local receipt of logs, in addition to the standard Violin Systems Support address.

— Use the web-based Simple SetUp Editor configuration utility to create array configuration (.cfg) files for use on any 7000 Series FSP to be deployed as a standalone array or as a shelf in a 7700 FSP storage cluster. For more details, see Simple SetUp Editor in the latest version 7000 Series Flash Storage Platform Installation Guide.



7700 FSP Controller Checklist Information

Ensure that you have read and completed the checklists listed in the Customer Requirements Document for Violin 7700 FSP Controllers, and then address the following prerequisites:

Note: You can also enable callhome and e-mail alert settings for 7700 FSP Controllers. For details, see Enabling Callhome and E-mail Alert Setting for Memory Gateways and 7700 FSP Controllers on page 95.

• Ensure that each 7700 FSP Controller has an IP address that can be accessed, from both the local and remote sites, for management of the 7700 FSP Controllers. This IP address is a networking requirement that provides access to each 7700 FSP Controller via SSH and Symphony.

• Ensure that each 7700 FSP Controller has a unique suffix that conforms with the customer network-naming conventions.

• Ensure that you address the following prerequisites when installing 7700 FSP Controllers:

— If you are using the replication feature, replication is performed between rep0 port on one 7700 FSP Controller to rep0 port on another 7700 FSP Controller in a physically separate stretched cluster via either a local direct SFP+ 10GbE cable connection or via a 10Gb Ethernet client network switch (and each side of this connection must know the IP address for the rep0 port on the corresponding 7700 FSP Controller).

— To properly set up management access, ensure to log in to a 7700 FSP Controller and provide the required login credentials (user name and password). For details, see Setting Up Management Access on page 57.

— To properly use licenses to manage 7700 FSP Controllers and other 7700 FSP storage cluster components using Symphony, ensure that you read and complete the licensing process. For details, see licenses in the latest version 7700 Flash Storage Platforms User’s Guide, and the topic on licenses in the latest version Symphony Help.

Note: You can also enable callhome and e-mail alert settings for 7700 FSP Controllers. For details, see Enabling Callhome and E-mail Alert Setting for Memory Gateways and 7700 FSP Controllers on page 95.

Brocade 6510 Fibre Channel Switch Configuration Checklist

All managed components need unique hostname and network IP addresses for use on the client network. Collect these from the appropriate storage, system, or network administrator before beginning the configuration for each Brocade 6510 Fibre Channel (FC) switch being deployed. Gather the following management IP addresses for the two FC switches in your storage network. This checklist information must be available to complete the switch configuration.



Note: For details about preconfiguration and procedures for configuring and setting up the Brocade 6510 Fibre Channel switches for use within the 7700 FSP system, see Configuring Brocade 6510 for a 7700 FSP System on page 139.

Symphony Installation Requirements Checklist

Symphony can be installed and deployed by meeting either the Violin Symphony VM or Violin Symphony Red Hat Package Manager (RPM) requirements. The basic requirements for each of these installation types are listed in Table 1.3. Under Symphony VM, Symphony runs as a virtual appliance, while under Symphony RPM it runs as bundle running under its native OS (Linux):

• For more details on Violin Symphony VN, see VMware vSphere compatibility requirements at http://www.vmware.com/, and see the latest version Violin Symphony Installation Guide, and Connecting Cables to the Fibre Channel Switches on page 28.

• For more details on Violin Symphony RPM, see the latest version Violin Symphony Installation Guide, and Connecting Cables to the Fibre Channel Switches on page 28.

Note: The Symphony server needs IP network access to all of the Violin Systems devices (7700 FSP Controllers, 7000 Series FSP and 6000 Series shelves, and the FC switches) that are under its management. Symphony itself is either assigned an IP address (static or DHCP) or a host name during installation by the on-site network or storage administrator.

Note: The Health gadget in Symphony provides an at-a-glance view of system health for devices and device groups managed by Symphony. However, Symphony does not directly monitor the 7700 FSP Controllers in the 7700 FSP storage cluster.

To monitor the system status for its disks, power supplies, fans, and temperature of the 7700 FSP Controllers, use iDRAC. iDRAC supports SNMP, IPMI, remote logging, and SMTP mail alerts. For more details on setting up and using iDRAC, see Monitoring 7700 FSP Controllers Using iDRAC on page 120.

When installing the 7700 FSP storage cluster and Symphony, set up and use the iDRAC alerts to avoid unreported issues with the 7700 FSP Controllers.

Checklist Information Description

Host Names

6510 FC Switches Two host names are required (one for each Brocade 6510 FC switch in a 7700 FSP storage cluster), and these switches would be known as:• FC Switch A

• FC Switch B

Two Management IP Addresses

• FC Switch A

• FC Switch B

• Identifies Switch A to 7700 FSP Controllers

• Identifies Switch B to 7700 FSP Controllers

Table 1.2 Brocade 6510 Fibre Channel Switch Checklist


http://www.vmware.com/


7700 Flash Storage Platform Site Information

This section provides site guideline information that describes rack space, power, and cooling needed to support the 7700 Flash Storage Platform.

Minimum Rack Space

Note: The minimum 3 RU per device value for FSP shelves in a 7700 FSP storage cluster is also dependent upon the total number of shelves that are being deployed. Violin Systems recommends leaving 1 RU above each FSP for service access and other benefits derived from having this additional rack space available.

Requirements Checklist Description of Requirements

Violin Symphony VM Requirements

Environment • Deploy Symphony VM using VMware vCenter Server 5.0 or later, which is the recommended version (vCenter Server 4.0 or later is also supported).

• Symphony VM must be deployed on an ESX/ESXi host using vCenter Server, and meet the following requirements:— ESX/ESXi version 4.1 or later— 3 GB of RAM— Minimum available disk space (60 GB for thick LUN

configuration or 4 GB for a thin LUN configuration)

Violin Symphony RPM Requirements

Environment • Deploy Symphony RPM as an application bundle running on your native OS: Red Hat 6.x (64-bit), or CentOS 6.x (64-bit).

• Symphony RPM must meet the following requirements:— 3 GB of RAM— Minimum available disk space (60 GB for thick LUN

configuration or 4 GB for a thin LUN configuration)

Table 1.3 Violin Systems Symphony Installation Requirements Checklist

Device RU Per Device RU Per Cluster

7700 FSP Controller 2 4

Switch 1 2

Shelf 3 --

Table 1.4 Required Rack Unit (RU) Space 7700 Flash Storage Platform



The benefits for using a 1 RU racking space above the shelf, include:

• Reduced exhaust airflow restrictions

• Improved overall airflow

• Improved access for hot-swap of components

• Improved room for cable management

Note: If implemented, this would be a 4 RU value per FSP shelf. An additional 1 RU space should be considered when allocating RU space above the 7700 FSP Controller for the same reasons. For more details on equipment racks, see the latest version 7000 Series Flash Storage Platform Installation Guide.

Note: When installing 7000 Series FSP shelves in a 7700 FSP storage cluster, observe the following rack mounting best practices.

— Weight: populate the equipment rack with the FSPs at the lowest possible level that helps maintain the lowest center of gravity in rack.

— Cooling: mount FSPs at lower rack levels to improve access to cold air intake coming from the floor.

— Serviceability: use an additional 1RU (rack unit) separation that improves ease-of-access to FSPs during service and allows better access to system components from the top.

— Accessibility: maintain a minimum of three feet of clearance between the highest mounted FSP and the data center ceiling to promote a safer environment for accessing, servicing, or replacing FSPs.

Power

The typical load shown for the devices in a 7700 FSP configuration reflect 70%read/30% write operations being performed at 25 degrees Celsius.

Each 7700 FSP Controller has two power supply units (PSUs), with one PSU acting as a spare. The two PSUs operate in a current share mode, with each one rated to approximately 750 watts. All 7700 FSP Controller values in this table reflect maximum power values with an added 4.5% margin.

Device Watts Per Device

Watts Per Cluster

Typical Load

7700 FSP Controller 550 1100 1100

Switch 110 220 220

Shelf (each) 1056(32 x 1TB, 7300E FSP)

1600(64 x 1TB, 7300 FSP)

Depends on the number of deployed FSPs

1056 (7300E FSP)1600 (7300 FSP)

Table 1.5 Required AC Power (in Watts) for a 7700 Flash Storage Platform



Note: With two identical PSUs installed, the current share mode power supply configuration is considered to be redundant (1 + 1). In this redundant mode, power is supplied to the system equally from both PSUs to maximize efficiency.

Note: The required power value (in Watts) for shelves in a 7700 FSP storage cluster depends upon the number of shelves that are deployed (up to 10), and the value shown in this table is per shelf (7300E/7300 FSP).

Cooling

Note: The required cooling value (in BTUs/Hour) for shelves in a 7700 FSP storage cluster depends upon the number of shelves that are deployed (up to 10), and this table is per shelf.

Physical Cabling Information

Minimum CAT5/CAT6 Cables with RJ-45 Connectors

Note: The required minimum number of CAT5/CAT6 cables with RJ-45 connectors for shelves in a 7700 FSP storage cluster depends upon the number of shelves that are deployed (up to 10) and this table reflects a per shelf value (there is no cable required for eth1).

Device Per Device in BTUs/hr Per Cluster BTUs/hr

7700 FSP Controller 5872 11744

Switch 195 390

Shelf 5549 5549

Table 1.6 Required Cooling (In BTUs/Hour) for a 7700 Flash Storage Platform

Device Each Per Cluster

7700 FSP Controller 2• Eth0

• iDRAC (IPMI)

4

Switch 1 2

Shelf 2• ACM-A

• ACM-B

--

Table 1.7 Minimum CAT5/CAT6 Cabling with RJ-45 Connectors (7700 Flash Storage Platform)



Multimode Duplex OM3 Optical Cables LC-LC Connectors

In the 7700 FSP, all of the fiber optic connections require 50-micron OM3 multimode duplex cables with LC connectors. In the 7700 FSP, all Fibre Channel ports are 16 Gbps.

The iSCSI, Server Cluster Interconnect (SCI), and the Replication ports are 10 Gbps Ethernet (10GbE). Table 1.8 lists the number of optical connections per 7700 FSP Controller, and a total for a 7700 FSP storage cluster (the listed optical cable values do not reflect a stretched cluster environment).

Note: The WAN replication cables (rep0/rep1) are optional and are only required if the replication feature is used.

Device Per 7700 FSP Controller Per Cluster

7700 FSP Controller 2 — WAN replication (rep0/rep1)

Note: Only applies to total if the replication feature is used.

4

4 — Fibre Channel or iSCSI (northbound) 8

4 — Fibre Channel (southbound) 8

2 — SCI (sci0/sci1) 4

TOTAL 24

Table 1.8 Multimode Duplex OM3 Optical Cables


Installation and Configuration Task Overview

Installation and Configuration Task Overview

This section provides an overview of the 7700 FSP hardware installation, cabling, and configuration tasks in the recommended order. The related reference documentation is listed in the Table 1.9

Task Description

Task 1: Unpack, inspect contents of all 7700 FSP device shipping boxes, and rack mount all 7700 FSP components including the Fibre Channel switches. For details, see Connectivity Overview on page 24 for related reference documents.

Note: Ensure that you properly ground all shelves installed in the rack. For details, see the latest version 7000 Series Flash Storage Platform Installation Guide or 6000 Series All Flash Array Installation Guide.

Note: For details on the best practice for rack-mounting storage shelves, see Minimum Rack Space on page 17. For more details, see equipment racks in the latest version 7000 Series Flash Storage Platform Installation Guide.

Task 2: Install Symphony, connect all storage network, management network, and power connections to the 7700 FSP components. For details, see:

• Connecting Cables to the Fibre Channel Switches on page 28

• Connecting Cables to the Fibre Channel Switches on page 28

• Connecting 7700 FSP Cluster Storage Devices on page 33

• Connecting Northbound Fibre Channel Ports on page 40

• Connecting Northbound iSCSI Cables on page 40

• Powering on the 7700 FSP Devices on page 42

Task 3: Configure shelves for the 7700 FSP system, the 7700 FSP Controllers, the fibre channel switches, and manage the FC switch zone configuration. For details, see:

• Configuring 7700 FSP Storage Shelves on page 51

• Configuring the 7700 FSP Controller on page 56

• Configuring Brocade 6510 Fibre Channel Switches on page 67

• Setting Up Replication on page 68

• Setting Up Replication on page 68

• Understanding a Fibre Channel Switch Zone on page 70

• Managing the Zoning Configuration on page 71

Table 1.9 7700 FSP Hardware Installation, Cabling, and Configuration Tasks



Task 4: Configure northbound client network switches for both Fibre Channel and iSCSI operations. For details, see:

• Configuring Northbound Switches on page 79

• Configuring iSCSI on page 80

Task 5: Review stretched cluster prerequisites prior to attempting to install, configure, and manage Tiebreaker for stretched cluster operations. For details, see:

• Overview: Stretched Clusters on page 145

• Configuring a Stretched Cluster on page 148

• Installing and Configuring Tiebreaker on page 152

• Modifying a Tiebreaker Configuration on page 160

• Setting Up Tiebreaker Using the CLI on page 162

Note: For more details, see the latest version of Concerto 7700 FSP Stretch Cluster Implementation and Best Practices Guide.

Task 6: Configure the enabling and disabling of HA using CLI commands, and manage and troubleshoot HA issues. For details, see:

• Enabling and Disabling HA Using CLI Commands on page 167

• Troubleshooting HA Issues on page 172

Task Description

Table 1.9 7700 FSP Hardware Installation, Cabling, and Configuration Tasks


CHAPTER 2 Connecting the 7700 Flash Storage Platform Hardware

This chapter provides procedures for connecting all of the 7700 Flash Storage Platform hardware devices that comprise the storage cluster:

• Storage shelves

• 7700 FSP Controllers

• Fibre Channel switches

While making sure to properly rack-mount, install, and cable all of the 7700 FSP storage cluster hardware, it is equally important that you install Symphony as soon as possible. Symphony provides a GUI-based management platform you can use for configuring, managing, and monitoring all of the installed 7700 FSP storage cluster components.

Hardware installation and configuration involves completing the following tasks:

• Rack-mounting the Fibre Channel switches, all of the storage shelves being deployed, and the two 7700 FSP Controllers.

• Connecting all network, storage, and power cables, ensuring that all southbound cable connections have been completed between the storage shelves, the 7700 FSP Controllers, and the Fibre Channel switches.

Note: The remaining topics and instructions in this chapter assume that all of the 7700 Flash Storage Platform devices have been unpacked, inspected, and installed at the customer site using the following procedures that are listed in the related documentation in Connectivity Overview on page 24.


Chapter 2 - Connecting the 7700 Flash Storage Platform Hardware

Connectivity Overview

For detailed information about installing Symphony and the physical devices of the 7700 Flash Storage Platform system, refer to Table 2.1, which provides a list of all the corresponding reference documentation needed to install and complete the initial installation tasks.

Note: See the latest version release notes for the latest supported configurations, as well as all updated software installation, software version, and upgrade instructions.

This guide is structured for the experienced system administrator familiar with installing storage system hardware devices in equipment racks.

Note: Before you attempt to install a 7700 Flash Storage Platform system and its devices, see Hardware Pre-Installation Information on page 12 for the management and site information that you will need for each of the devices. For details about rack spacing required for the hardware, see Minimum Rack Space on page 17.

Device Type Document Provides this information...

Violin Symphony

Symphony Violin Symphony Installation Guide

Installing and getting started with using Symphony

Note: For an overview, see APPENDIX E on page 143, in this guide.

Fibre Channel Switch

Brocade 6510 Fixed Rack Mount Kit Installation Procedure

Installing the Brocade switch

Shelf

7000 Series FSP shelf

Violin 7000 Series Flash Storage Platform Installation Guide

Installing the 7000 Series FSP hardware (Chapter 1)

6000 Series shelf

Violin 6000 Series All Flash Array Installation Guide (v6.3.1)

Installing the 6000 Series hardware (Chapter 1)

Slide Rail Installation Guide Installing the slide rails, cage nuts, and mounting the shelf

Cable Management Installation Guide

Connecting a cable management arm to a shelf

External Controller

7700 FSP Controllers

Rack Installation Instructions Installing the 7700 FSP Controllers

Table 2.1 Installation Overview for the 7700 Flash Storage Platform System Devices


Connecting Cables to the 7700 FSP Controllers

Read this chapter and use the reference information during rack-mounting and installing the 7700 Flash Storage Platform devices to complete the following tasks:

• Installing Violin Symphony on page 143: Appendix E, Installing and Accessing Violin Symphony, provides a brief overview of a Symphony installation, provides reference documentation that supports installing Symphony on a separate server that can access the 7700 FSP components, identifies it as the single point for configuring and managing your 7700 FSP storage cluster, and provides the procedure for accessing Symphony to get started.

Note: For best results, Symphony requires that all 7000 Series FSP and 6000 Series storage shelves, 7700 FSP Controllers, and Brocade 6510 switches be rack mounted, powered on, and all network management cabling connected. Each shelf should have the configuration jump-start process completed. For more details, see Chapter 4 Using the Configuration Wizard-Script File for Setup in the latest version 7000 Series Flash Storage Platform Installation Guide.

• Connecting Cables to the Fibre Channel Switches on page 28: describes where you should connect the fibre cabling on the two Brocade 6510 Fibre Channel switches, which act as the connection point between the 7700 FSP storage shelves and the 7700 FSP Controllers. Together, these connected components form the 7700 FSP storage cluster.

• Connecting Cables to a Shelf on page 29: describes where you connect the storage network interface cables from a supported shelf to a storage area network (SAN) using Fibre Channel cabling.

• Connecting 7700 FSP Cluster Storage Devices on page 33: describes where you connect the northbound, southbound, and power cables between the 7700 Flash Storage Platform devices (Fibre Channel switches, 7000 Series FSPs/6000 Series storage shelves, and 7700 FSP Controllers) and the client network.

• Powering on the 7700 FSP Devices on page 42: describes where you power on the racked and cabled 7700 Flash Storage Platform devices.

Caution: To prevent potential power surge damage to your equipment when installing multiple shelves in the 7700 Flash Storage Platform cluster, complete all rack mounting, and route all network and power cables for every shelf before applying power to the first shelf. After you complete the power on for the first shelf, wait several minutes before you power on the next shelf. Continue until each deployed shelf in the 7700 FSP has been powered on to prevent potential circuit damage.


This section provides an overview of the 7700 FSP Controllers that includes figures and tables that describe the slots, ports, and connectors needed for connecting either the Fibre Channel or iSCSI version 7700 FSP Controllers.

• Figure 2.1 shows the Fibre Channel slot, port, and connector locations on the 7700 Controller rear panel and Table 2.2 provides descriptions for each location (for details, see 7700 FSP Controller - Fibre Channel on page 26).

• Figure 2.2 shows the iSCSI slot, port, and connector locations on the 7700 Controller rear panel and Table 2.3 provides descriptions for each location (for details, see 7700 FSP Controller - iSCSI on page 27).



7700 FSP Controller - Fibre Channel

Figure 2.1 Fibre Channel Slot-Port-Connector Locations on the 7700 Controller Rear Panel

Item Description

1 Slot 1, 10Gb Ethernet, Replication port (Rep0), slot-port 1-0


3 Slot 2, 16Gb FC, northbound Fibre Channel, Target port ID 107, slot-port 2-1


5 Slot 3 (empty)

6 iDRAC/IPMI port

7 Slot 4, 16Gb FC, southbound Fibre Channel, Initiator port ID 104, slot-port 4-0




11 Storage Cluster Interlink (SCI) port, 10 Gb Ethernet, sci0

12 SCI, 10 Gb Ethernet port, sci1

13 Ethernet Management port, 10Gb Ethernet, eth0


15 Slot 6 (empty)



Table 2.2 Descriptions of Fibre Channel Slots-Ports-Connectors on 7700 FSP Controller Rear Panel

1 2 3 4

ST

21

iDRAC

2

1

3750W750W

5

4

7

6

PCIe x816G FC/10GbE

PORT 2

PORT 1

TX RXTX RX

PCIe x816G FC/10GbE

PORT 2

PORT 1

TX RXTX RX

PCIe x816G FC/10GbE

PORT 2

PORT 1

TX RXTX RX

PCIe x816G FC/10GbE

PORT 2

PORT 1

TX RXTX RX

6

5

1 2

3 4

7 8

9 10

1112

13

16

17 15

14



7700 FSP Controller - iSCSI

Figure 2.2 iSCSI Slot-Port-Connector Locations on the 7700 Controller Rear Panel

Item Description



3 Slot 2, 10Gb, northbound iSCSI, Target port ID, slot-port 2-0, isc2


5 Slot 3 (empty)

6 iDRAC/IPMI port





11 Storage Cluster Interlink (SCI) port, 10 Gb Ethernet, sci0

12 SCI, 10 Gb Ethernet port, sci1



15 Slot 6 (empty)



Table 2.3 Descriptions of iSCI Slots-Ports-Connectors on 7700 FSP Controller Rear Panel

1 2 3 4

ST

21

iDRAC

2

1

3750W750W

5

4

7

6

PCIe x816G FC/10GbE

PORT 2

PORT 1

TX RXTX RX

PCIe x816G FC/10GbE

PORT 2

PORT 1

TX RXTX RX

PCIe x816G FC/10GbE

PORT 2

PORT 1

TX RXTX RX

PCIe x816G FC/10GbE

PORT 2

PORT 1

TX RXTX RX

6

5

1 2

3 4

7 8

9 10

1112

13

16

17 15

14



Connecting Cables to the Fibre Channel Switches

A key cabling connection target in the 7700 FSP storage cluster are the two Brocade 6510 Fibre Channel switches. These two FC switches form a central part of the cluster where you patch together the 7700 FSP storage shelves and the 7700 FSP Controllers to create the 7700 FSP storage cluster using 16 Gbps (16Gb FC) cabling:

• Figure 2.9 provides an example of a 7700 FSP storage cluster configured and cabled with two 7700 FSP Controllers, two storage shelves, and two Brocade 6510 switches.

• Figure 2.10 provides an example of southbound port locations on the 7700 FSP Controllers (Fibre Channel and iSCSI) for the Brocade 6510 switches, and southbound port locations on the Brocade 6510 switches for the 7700 FSP Controllers and the 7000 Series/6000 Series shelves.

Note: See Configuring Brocade 6510 for a 7700 FSP System on page 139, for details and procedures for configuring and setting up the Brocade 6510 Fibre Channel switches for use within the 7700 FSP system. Figure 2.3 provides a FC switch and 7000 Series FSP cabling example.

Figure 2.3 Cabling Example: 7000 Series FSP and Fibre Channel Switches

.

.


Connecting Cables to a Shelf


This section describes the steps required to connect the storage network interface cables from a supported shelf to a storage area network (SAN) using Fibre Channel cabling. To better understand the ports to use on the shelf to support high-availability installation, see Understanding Port Numbering on this page. For sections specific to connecting the shelf, see Connecting Cables to the Fibre Channel Switches on page 28.

About the Shelf

Both the 7000 Series FSP and 6000 Series shelves include two internal Memory Gateways. Each Memory Gateway supports two network interface modules, each of which support the four 16 Gbps Fibre Channel ports that auto-negotiate down to 4 Gbps. The dual 16 Gbps ports on the Fibre Channel HBA are SFP+ with LC-style connectors. Memory Gateways can use up to four ports of 16 Gbps FC to connect to other devices.

Understanding Port Numbering

When connecting interface cables in a SAN-attached configuration, reference the ports from which LUNs are exported from the array. Figure 2.4 shows the slot and port numbers for Fibre Channel cards in a 6000 Series array and a 7000 Series FSP (the figure also lists the representative CLI values for each port):

• Aria is the OS for the ACMs, and its CLI values are shown in blue.

• Concerto is the OS for the MGs, and its CLI values are shown in green.

Figure 2.4 6000 Series and 7000 Series FSP Memory Gateway HBA Slots: Fibre Channel Port Numbers



To view the actual port numbering shown in the Concerto CLI, issue the isscli getadapterinfo CLI command from each Memory Gateway, as shown:

Connecting Management Cables to 7700 FSP Controllers

This section describes the steps required to connect the required network management cables to the rear panel ports on the 7700 FSP Controller (see Figure 2.5).

To connect network management cables to the 7700 FSP Controller, complete the following tasks:

1. Connect one network management cable (Ethernet RJ-45) to the IPMI/iDRAC port.

2. Connect one network management cable (Ethernet RJ-45) to the Eth0 port (this is port 3 in center of rear panel).

3. Connect management cables (10GbE LC) between the SCI ports (port 1 and 2) on the two 7700 FSP Controllers in the 7700 FSP storage cluster as follows:

• Connect port1 (sci0) from 7700 FSP Controller A to port1 (sci0) on 7700 FSP Controller B.

• Connect port2 (sci1) from 7700 FSP Controller A to port2 (sci1) on 7700 FSP Controller B.

Figure 2.5 IPMI/iDRAC, SCI, and Eth0 Port Connections on 7700 FSP Controller Rear Panel

IPMI/iDRAC Port SCI Ports Eth0 Port



Connecting Cables to the Shelf

This section describes the steps required to connect the network interface cables from the 7000 Series FSP/6000 Series shelves to the SAN using Fibre Channel.

Note: When connecting the interface cables in a SAN-attached configuration, it is important to know the ports from which LUNs are exported from the 7000 Series FSP. See Understanding Port Numbering on page 29 for more information about the port numbering of the supported cards.

The 50-micron OM3 optical cables that connect to the dual 16 Gbps ports on the Fibre Channel HBA are SFP+ with LC-style connectors (see Figure 2.4 for FC port numbers and locations). The 7000 Series FSP and 6000 Series array both use the same OM3 optical cable type.

1. Connect four cables from the upper row of ports on the interface cards (MG-A and MG-B) to one Brocade switch.

2. Connect the four cables from the lower row of ports on the interface cards (MG-A and MG-B) to the second Brocade switch (as shown in Figure 2.9).

For more information, see the Fibre Channel adapter card specifications in the latest version 7000 Series Flash Storage Platform Installation Guide or Violin 6000 Series All Flash Array Installation Guide.

Note: After completing the initial configuration of the 7000 Series FSP, see the latest version Violin Systems Interoperability Best Practices Guide for the best practice for each of the supported operating systems.

Figure 2.6 Interface Cable Ports

ID

n

11

n

D

D

1

n

C

C

1

n

B

B A

AB

AB

A

AB

Fibre Channel Ports



32

Support for Controller-to-Controller Replication

To support the replication feature between two 7700 FSP Controllers, you must make one of the following cable connection types:

• A direct connection (intra-rack) between rep0 port on one 7700 FSP Controller to the corresponding port rep0 port on the second 7700 FSP Controller using 10GbE SFP+ cables.

• A LAN-based connection between rep0 port on one 7700 FSP Controller to the corresponding rep0 port on the second 7700 FSP Controller via the LAN using 10GbE SFP+ cables.

• A WAN-based connection where 7700 FSP Controllers are physically remote from one another via a 10Gb Ethernet client network switch. Using 10GbE SFP+ cables, connect rep0 port on one 7700 FSP Controller to the 10Gb Ethernet client network switch and from this switch to the corresponding rep0 port on the second 7700 FSP Controller using 10GbE SFP+ cables.

Note: You must know the IP address for the respective replication port on both 7700 FSP Controllers to properly connect and configure replication operations. Replication policies are configured and performed using Symphony.

Note: If you are enabling HA across the controller-to-controller replication, you must establish connections to both 7700 FSP Controllers in each HA pair. Each connected port will need to know the monitor and virtual IP addresses for each of the peer replication ports on the 7700 FSP Controllers.

1. Connect one end of the SFP+ 10GbE cable to rep0 on one 7700 FSP Controller for a direct, LAN, or WAN connection.

2. Connect the other end of the 10GbE cable in one of the following methods:

a. (Direct) Connect the 10GbE cable to rep0 on the second 7700 FSP Controller.

b. (LAN) Connect the 10GbE cable via the LAN to rep0 on the second 7700 FSP Controller.

c. (WAN) Connect the 10GbE cable to an available port on the 10Gb Ethernet client network switch, and from this client network switch, and then connect the 10GbE cable to rep0 on the second 7700 FSP Controller.

Figure 2.7 7700 FSP Controller Replication Ports - Cable Connection Location

Replication Ports

7700 Flash Storage Platform Installation Guide 7.6.3.x 530-0267-00 Rev 02

Connecting 7700 FSP Cluster Storage Devices

3. Configure the replication interfaces. This includes collecting the IP address for each configured rep0 interface, collecting routing information between the controllers, and making sure that each route is specified at each controller instance to assure the proper use of the replication ports and replication paths.

For specific details, see Configuring Network Interfaces for Replication on page 125.

4. Configure replication by creating a replication policy using Symphony Help. Using Symphony, start the process for creating a replication policy by selecting Manage > Devices > Replications.

In addition to creating replication policies, Symphony Help describes a variety of replication-related procedures that include how to edit or delete a replication policy, manually start or stop a replication process, and export replication data. For more details on managing replication operations, see the topic on replication in the latest version Symphony Help.


This section describes how to make southbound connections that connect the cabling from the storage shelves to the FC switches, and from the FC switches to the 7700 FSP Controllers. Southbound connections use Fibre Channel cabling to connect each of the 7700 FSP Controllers to both FC switches, and from both FC switches to the storage shelves/arrays.

Note: The ports in 7700 FSP Controller rear panel HBA slots 4 and 5 are southbound ports to the storage cluster and are configured as initiator ports.

Figure 2.8 Cabling Example: Fibre Channel Switches and 7700 FSP Controllers



Connecting 7700 FSP Cluster Southbound Cables

Note: For details on device reference and cable abbreviation conventions, see 7700 FSP Component Reference Conventions on page 11.

Apply the supplied cable labels to the fibre optic cables that ship with the 7700 FSP system, and these labels indicate the respective component ports for making device connections.

The southbound inter-cluster cables connect the Memory Gateways on each shelf with the FC switches, and also connect the FC switches to the 7700 FSP Controllers. The supplied labels for the fibre optic cables use the following label format, WW:X-Y-ZZZ at each end, and this is shown in examples in Table 2.4.

Figure 2.9 shows an example of cable connections for a southbound data path for a 7700 Flash Storage Platform system that is comprised of two 7700 FSP Controllers, two FC switches, and two shelves.

1. Apply the supplied cable labels to the fibre optic cables.

2. Connect each storage shelf to both FC switches using the labeled cables.

Refer to Table 2.5 and connect the ports on Shelf 1 to FC switch A and FC switch B. Table 2.5 and Figure 2.4 provide all the FC port references for MG-A and MG-B for each shelf.

Label Format Format Group Description/Example

WW:X-Y-ZZZ

WW Component Type CT = 7700 FSP Controller

SW = Fibre Channel Switch

SH = 7000 Series FSP/6000 Series Shelf

X Component Sequence

CT:A or CT:B are 7700 FSP Controllers A or B

SW:A or SW:B are Fibre Channel switches A or B

SH:1 through SH:10 are Shelves 1 through 10

Y Subcomponent ID (Memory Gateway or HBA Slot)

SH:1-A is Shelf 1, Memory Gateway A (MG-A)

SH:1-B is Shelf 1, MG-B

CT:A-4 is 7700 FSP Controller A, HBA slot 4

ZZZ Port Number SH:1-A-101 is Shelf 1, MG-A, port 101

SH:1-B-101 is Shelf 1, MG-B, port 100

CT:A-4-0 is 7700 FSP Controller A, HBA slot 4, port 0

CT:B-5-1 is 7700 FSP Controller B, HBA slot 5, port 1

Table 2.4 Fibre Optic Cable Label Descriptions



3. Repeat the port connections using available ports on the two FC switches if you are installing more than one shelf.

4. Connect the FC switches to the 7700 FSP Controllers using the slot number-port number cabling shown in Figure 2.5 and Figure 2.9.

Note: For instructions on setting up the zoning configuration for the southbound Fibre Channel switches, see Chapter 4, Southbound Fibre Channel Switch Zone Configuration.

Table 2.5 lists the ports connecting the 7700 FSP Controllers, FC switches, and all supported shelves. The labels for the cables use the Table 2.4 label naming convention (with each label listing the end-to-end port connections).

Note: The "==" shown in the end-to-end cable labels represents the cable connecting each of the respective cable ends with a port (for example, in SW:A-0==CT:A-5-0, the cable connects port 0 on Fibre Channel switch A and port 5-0 on 7700 FSP Controller A).

FC Switch (A/B) and Ports

7700 FSP Controller/Shelf Ports

Fibre Optic Cable Labels

FC Switch A and B Ports 7700 FSP Controller A End-to-End Label

SW:A-0 CT:A-5-0 SW:A-0==CT:A-5-0

SW:A-1 CT:A-4-0 SW:A-1==CT:A-4-0

SW:B-0 CT:A-5-1 SW:B-0==CT:A-5-1

SW:B-1 CT:A-4-1 SW:B-1==CT:A-4-1

FC Switch A and B 7700 FSP Controller B End-to-End Label

SW:A-2 CT:B-5-0 SW:A-2==CT:B-5-0

SW:A-3 CT:B-4-0 SW:A-3==CT:B-4-0

SW:B-2 CT:B-5-1 SW:B-2==CT:B-5-1

SW:B-3 CT:B-4-1 SW:B-3==CT:B-4-1

FC Switch A Shelf 1 (MG-A and MG-B) End-to-End Label

SW:A-4 SH:1-A-100 SW:A-4==SH:1-A-100

SW:A-5 SH:1-A-102 SW:A-5==SH:1-A-102

SW:A-6 SH:1-B-100 SW:B-6==SH:1-B-100

SW:A-7 SH:1-B-102 SW:B-7==SH:1-B-102

FC Switch B Shelf 1 (MG-A and MG-B) End-to-End Label

SW:B-4 SH:1-A-101 SW:B-4==SH:1-A-101

SW:B-5 SH:1-A-103 SW:B-5==SH:1-A-103

SW:B-6 SH:1-B-101 SW:B-6==SH:1-B-101

SW:B-7 SH:1-B-103 SW:B-7==SH:1-B-103

Table 2.5 Cable Bundle End-to-End Port Connections




SW:A-8 SH:2-A-100 SW:A-8==SH:2-A-100

SW:A-9 SH:2-A-102 SW:A-9==SH:2-A-102

SW:A-10 SH:2-B-100 SW:B-10==SH:2-B-100

SW:A-11 SH:2-B-102 SW:B-11==SH:2-B-102


SW:B-8 SH:2-A-101 SW:B-8==SH:2-A-101

SW:B-9 SH:2-A-103 SW:B-9==SH:2-A-103

SW:B-10 SH:2-B-101 SW:B-10==SH:2-B-101

SW:B-11 SH:2-B-103 SW:B-11==SH:2-B-103


SW:A-12 SH:3-A-100 SW:A-12==SH:3-A-100

SW:A-13 SH:3-A-102 SW:A-13==SH:3-A-102

SW:A-14 SH:3-B-100 SW:B-14==SH:3-B-100

SW:A-15 SH:3-B-102 SW:B-15==SH:3-B-102


SW:B-12 SH:3-A-101 SW:B-12==SH:3-A-101

SW:B-13 SH:3-A-103 SW:B-13==SH:3-A-103

SW:B-14 SH:3-B-101 SW:B-14==SH:3-B-101

SW:B-15 SH:3-B-103 SW:B-15==SH:3-B-103


SW:A-16 SH:4-A-100 SW:A-16==SH:4-A-100

SW:A-17 SH:4-A-102 SW:A-17==SH:4-A-102

SW:A-18 SH:4-B-100 SW:B-18==SH:4-B-100

SW:A-19 SH:4-B-102 SW:B-19==SH:4-B-102

FC Switch B Shelf 4 (MG-A and MG-B End-to-End Label

SW:B-16 SH:4-A-101 SW:B-16==SH:4-A-101

SW:B-17 SH:4-A-103 SW:B-17==SH:4-A-103

SW:B-18 SH:4-B-101 SW:B-18==SH:4-B-101

SW:B-19 SH:4-B-103 SW:B-19==SH:4-B-103




Table 2.5 Cable Bundle End-to-End Port Connections(Continued)




SW:A-20 SH:5-A-100 SW:A-20==SH:5-A-100

SW:A-21 SH:5-A-102 SW:A-21==SH:5-A-102

SW:A-22 SH:5-B-100 SW:B-22==SH:5-B-100

SW:A-23 SH:5-B-102 SW:B-23==SH:5-B-102


SW:B-20 SH:5-A-101 SW:B-20==SH:5-A-101

SW:B-21 SH:5-A-103 SW:B-21==SH:5-A-103

SW:B-22 SH:5-B-101 SW:B-22==SH:5-B-101

SW:B-23 SH:5-B-103 SW:B-23==SH:5-B-103


SW:A-24 SH:6-A-100 SW:A-24==SH:6-A-100

SW:A-25 SH:6-A-102 SW:A-25==SH:6-A-102

SW:A-26 SH:6-B-100 SW:B-26==SH:6-B-100

SW:A-27 SH:6-B-102 SW:B-27==SH:6-B-102


SW:B-24 SH:6-A-101 SW:B-24==SH:6-A-101

SW:B-25 SH:6-A-103 SW:B-25==SH:6-A-103

SW:B-26 SH:6-B-101 SW:B-26==SH:6-B-101

SW:B-27 SH:6-B-103 SW:B-27==SH:6-B-103


SW:A-28 SH:7-A-100 SW:A-28==SH:7-A-100

SW:A-29 SH:7-A-102 SW:A-29==SH:7-A-102

SW:A-30 SH:7-B-100 SW:B-30==SH:7-B-100

SW:A-31 SH:7-B-102 SW:B-31==SH:7-B-102


SW:B-28 SH:7-A-101 SW:B-28==SH:7-A-101

SW:B-29 SH:7-A-103 SW:B-29==SH:7-A-103

SW:B-30 SH:7-B-101 SW:B-30==SH:7-B-101

SW:B-31 SH:7-B-103 SW:B-31==SH:7-B-103








SW:A-32 SH:8-A-100 SW:A-32==SH:8-A-100

SW:A-33 SH:8-A-102 SW:A-33==SH:8-A-102

SW:A-34 SH:8-B-100 SW:B-34==SH:8-B-100

SW:A-35 SH:8-B-102 SW:B-35==SH:8-B-102


SW:B-32 SH:8-A-101 SW:B-32==SH:8-A-101

SW:B-33 SH:8-A-103 SW:B-33==SH:8-A-103

SW:B-34 SH:8-B-101 SW:B-34==SH:8-B-101

SW:B-35 SH:8-B-103 SW:B-35==SH:8-B-103


SW:A-36 SH:9-A-100 SW:A-36==SH:9-A-100

SW:A-37 SH:9-A-102 SW:A-37==SH:9-A-102

SW:A-38 SH:9-B-100 SW:B-38==SH:9-B-100

SW:A-39 SH:9-B-102 SW:B-39==SH:9-B-102


SW:B-36 SH:9-A-101 SW:B-36==SH:9-A-101

SW:B-37 SH:9-A-103 SW:B-37==SH:9-A-103

SW:B-38 SH:9-B-101 SW:B-38==SH:9-B-101

SW:B-39 SH:9-B-103 SW:B-39==SH:9-B-103


SW:A-40 SH:10-A-100 SW:A-40==SH:10-A-100

SW:A-41 SH:10-A-102 SW:A-41==SH:10-A-102

SW:A-42 SH:10-B-100 SW:B-42==SH:10-B-100

SW:A-43 SH:10-B-102 SW:B-43==SH:10-B-102


SW:B-40 SH:10-A-101 SW:B-40==SH:10-A-101

SW:B-41 SH:10-A-103 SW:B-41==SH:10-A-103

SW:B-42 SH:10-B-101 SW:B-42==SH:10-B-101

SW:B-43 SH:10-B-103 SW:B-43==SH:10-B-103







Figure 2.9 Southbound Fibre Channel Configuration: 7700 FSP Controllers-FC Switches-Shelves

Figure 2.10 Southbound Port Locations: 7700 FSP Controllers, Shelves, and Brocade 6510 Switch

�

��

��

��

��

�� !

��

� �! ��

�� !

��

��! � � � �

�"# "��

��$�� $�� $��

��$��"# "��

��$�� $��

��$� ��$��

��$�� $�!

��

��

�

��

�

��

��

��

��

��

��

��

%&�%

��

��

��

��

��

��

��

��

��

�

��

�

��

��

��

��

��

��

%&�%

��

��

��

��

��

��

��

��



Connecting Northbound Fibre Channel Ports

This section describes how to make northbound Fibre Channel connections by cabling the 7700 FSP Controllers to the client storage network switches. Figure 2.11 shows the required Fibre Channel cable connections for configuring a northbound Fibre Channel data path.

Note: The northbound switches must support N_Port ID Virtualization (NPIV) to accommodate multiple Fibre Channel initiators occupying a single physical port.

1. Connect Fibre Channel cables from the 7700 FSP Controllers to client network switches. 7700 FSP Controller ports are listed using a slot number-port number format (shown in Figure 2.11).

For example, a slot number-port number of 2-1 reference means slot 2-port 1. After making the connections, verify that the link state is UP (as indicated by green LEDs being solidly lit).

Note: Any northbound port that has a status as Offline may cause HA setup to fail. After HA is enabled, an HA takeover event can occur when all northbound target ports fail.

Figure 2.11 Northbound Fibre Channel Configuration: 7700 FSP Controllers-Client Network Switches

Connecting Northbound iSCSI Cables

This section describes how to make northbound iSCSI connections by cabling the 7700 FSP Controllers to the client storage network switches. Figure 2.12 shows the required iSCSI cable connections for configuring a northbound iSCSI data path.


Connecting Northbound iSCSI Cables

Note: Ensure that all network paths and client ports used for iSCSI support jumbo frames (MTU 9000). Confirm that all 7700 FSP Controller iSCSI ports have link status UP (as indicated by green LEDs being lit) before configuring interface network settings and enabling HA.

1. Connect iSCSI cables from the 7700 FSP Controllers to client network switches. 7700 FSP Controller ports are listed using a slot number-port number format (shown in Figure 2.12).

For example, a slot number-port number of 2-0 reference means slot 2-port 0. After making the connections, verify that the link state is UP (indicated by green LEDs being lit).

Note: Any northbound port that has a status as Offline may cause HA setup to fail. After HA is enabled, an HA takeover event can occur when all northbound target ports fail.

Figure 2.12 Northbound iSCSI Cable Connections: 7700 FSP Controllers to Client Network Switch



Powering on the 7700 FSP Devices

This section provides an overview of the required AC power connections. After you have rack-mounted and cabled all devices, verify that all shelves are grounded and connections are secure, and then power up the devices as described in the following subsections.

Note: For the required sequential order to follow when powering down or powering up the entire set of 7700 Flash Storage Platform storage cluster system components, see 7700 FSP Power Down and Power Up Sequences on page 44.

Powering on a 7000 Series FSP/6000 Series Shelf

Table 2.6 displays the power requirements for both the 6000 Series/7000 Series FSP shelves, and both storage shelf types boot up when connected to AC power. The listed power requirements are for the entire chassis.

The 7700 FSP shelf power cords include International Electrotechnical Commission (IEC) 60320 C19 plugs for the shelves, and IEC 60320 C14 plugs to the data center power strip. The 7700 FSP shelves use power requirements that reflect North American electrical ratings. For complete system specifications, see the system specifications in the latest version 7000 Series Flash Storage Platform Installation Guide or Violin 6000 Series All Flash Array User’s Guide.

The 7700 FSP storage shelves have a pair of redundant AC power supplies installed prior to shipping. Connect each of the AC power supplies to a separate Power Distribution Unit (PDU) when possible. For specific details about making AC power cable connections, see the latest version Violin 7000 Series Flash Storage Platform Installation Guide or Violin 6000 Series All Flash Array User’s Guide.

WARNING! To avoid circuit overload, after you have racked and cabled each shelf, it is recommended that you only power on one shelf at a time. Once you have successfully powered up one shelf, wait several minutes before powering up the next shelf to avoid any potential circuit overload.

1. Plug each AC power cord from the chassis into an AC outlet.

Note: Observe the listed warning above, and power on one shelf at a time (shelves have the longest boot time of all 7700 FSP devices). A shelf is fully booted when the Status LED remains continuously lit.

Item Requirement

Voltage Input Range 200-264 Volt AC 50/60 Hz, single-phase, 15 Amp (maximum)

Supported Operating Range 180-264 V AC

Supported Frequency Range 47-63 Hz

Table 2.6 Power Requirements for 7000 Series FSP and 6000 Series Shelves


Powering on the 7700 FSP Devices

Note: Confirm that the PSU Power LED is not flashing. If the PSU Power LED (top LED on the power supply) flashes green after boot up, this indicates that the power controller for the power supply is improperly seated or it must be replaced. Contact Violin Systems Customer Support for assistance and resolve this issue.

Powering on the FC Switches

Power on the FC switches by connecting the power cord for each of FC switch to a power source (there is no On/Off switch). Typically, a FC switch completes its boot up within 3 minutes. When the System Power and System Status LEDs are lit solid green, this indicates its proper running state.

Powering on 7700 FSP Controllers

7700 FSP Controllers are configured to power on when connected to a power source. To monitor the system POST and boot, you must first connect a VGA monitor and a USB keyboard and mouse before you apply power to the 7700 FSP Controllers.

After the 7700 FSP Controllers boot up, use this local console access to complete the Violin Quick Start and configure management and iDRAC/IPMI network interfaces.

Two power cables are shipped with each 7700 FSP Controller, one for each of the power supplies in the chassis. Two additional standard data center power cables are provided, if preferred. Connect the appropriately terminated power supply cords from each of the 7700 FSP Controllers to the equipment rack power sources. Cords for regional outlet and rack PDU are provided.

Each of the power supplies in a 7700 FSP Controller has a Power LED that is built into the top portion of the plastic handle (one of the power supplies acts as a hot spare for reduced stand-by power for the 7700 FSP Controller). The Power LED should remain illuminated when the 7700 FSP Controller is UP.

Note: For details on configuring the 7700 FSP Controllers, see Configuring the 7700 FSP Controller on page 56.

System Power LED

System Status LED



7700 FSP Power Down and Power Up Sequences

This section provides two required procedures that describe the sequential order you must follow when powering down or powering up the entire set of 7700 Flash Storage Platform storage cluster system components.

Powering down or powering up all of the 7700 Flash Storage Platform system components is not something done on any regular or routine basis. You would only perform the required procedural sequence to power down or power up the 7700 FSP system components when the following types of events occur:

• There is site-wide maintenance being done on the data center power system.

• All of the data center equipment is being physically moved to another location.

• There is a serious loss of data center power due to a natural or civil disaster.

Note: A best practice to remember when powering down and powering up 7700 FSP system components is that the Brocade 6510 Fibre Channel switches should be the last of the devices powered down and the first to be powered on, and that the 7700 FSP Controllers should be the first devices powered off and the last to be powered on.

Required 7700 FSP Power Down Sequence

This section provides the required procedural sequence to perform when you need to power down the entire 7700 FSP system and its components. To properly power down all 7700 FSP system components, complete the following:

1. Disable HA on each 7700 FSP Controller by using the following command:

For details, see “Enabling and Disabling HA Using CLI Commands” on page 167

2. Log in as root and stop the Concerto software services on each 7700 FSP Controller by issuing the following command:

3. Log in as root and shut down the Concerto OS on each 7700 FSP Controller by issuing one of the following commands:

• # shutdown –h now

• # halt

Note: These alternate commands shut down the Concerto OS on each of the 7700 FSP Controller.

4. Disconnect the power source to power down each 7700 FSP Controller.

isscli disableha -s

# concerto stop all



5. Log in as admin in the Master ACM (ACM-A or ACM-B) and shut down each installed 7000 Series FSP shelf in the 7700 FSP system by issuing the following command:

Note: Respond yes in the confirmation dialog for shutting down the array.

6. Wait until the 7000 Series FSP has shut down, and then remove power from both Power Supply Units (PSUs) on the shelf.

Note: When shut down, all HBA and Ethernet port LEDs will be unlit on the 7000 Series FSP shelf.

7. Log in as admin in the Master ACM (ACM-A or ACM-B) and shut down each installed 6000 Series array in the 7700 FSP system by issuing the following command:

Note: Respond yes in the confirmation dialog for shutting down the array.

8. Wait until the 6000 Series array has shut down, and then remove power from both Power Supply Units (PSUs) on the array.

Note: When shut down, all HBA and Ethernet port LEDs will be unlit on the 6000 Series array.

9. Repeat this procedure for each installed 7000 Series FSP and 6000 Series array in the 7700 FSP storage cluster system.

Note: You can perform a shutdown of all the installed 6000 Series arrays and 7000 Series FSPs in parallel.

10.Remove power from both Power Supply Units (PSUs) on each of the Brocade 6510 Fibre Channel switches.

Required 7700 FSP Power On Sequence

This section provides the required procedural sequence to perform when you need to power on the entire 7700 FSP system and its components. To properly power on all 7700 FSP system components, complete the following:

1. Apply power to both Power Supply Units (PSUs) on each of the Brocade 6510 Fibre Channel switches.

2. Apply power to both PSUs on all 7700 FSP system shelves (7000 Series FSPs and 6000 Series arrays).

> enable# configure terminal(config) # array shutdown

> enable# configure terminal(config) # array shutdown



Note: You can start up all of the installed 6000 Series arrays and 7000 Series FSPs in parallel.

3. After a few minutes have elapsed, log in to the Master ACM (ACM-A or ACM-B) as admin, issue the following commands, and monitor the boot process from the Master ACM:

Note: You can expect to wait up to 5 minutes for ethernet access to be established, and up to 15 minutes for the system to completely boot.

Log in to each of the Memory Gateways and inspect their current status.

Note: There is no LED status to indicate that the boot up of the Memory Gateways has completed.

Once both Memory Gateways have completed boot up, the Concerto software starts up automatically.

4. Inspect the failover status, and confirm that both Memory Gateways return a normal HA status, FailOverStatus=1 (UP), after issuing the following command:

Note: If a Memory Gateway or 7700 FSP Controller does not return to FailOverStatus=1 (UP) after reboot, issue the following command: # sms setFOState 1.

5. Once all the installed 7000 Series FSPs and 6000 Series arrays have booted up, log in to Symphony, and confirm the status of each 7700 FSP shelf.

For details on logging in to Symphony, see Accessing Symphony on page 143.

6. Verify that all the LUNs presented to the 7700 FSP Controllers show 7700 FSP Controllers displayed in the Clients column on the LUNs tab.

> enable# configure terminal(config) # monitor boot(config) # show alarms

[root@mg-a ~]# isscli getfailoverstatusFailover Servers=mg-a / mg-bConfiguration Type=Mutual FailoverFailover State=NormalFailover Suspended=NoStretched Cluster Enabled=NoFailOverStatus=1(UP)[root@mg-a ~]# isscli getfailoverstatus -s mg-bFailover Servers=mg-b / mg-aConfiguration Type=Mutual FailoverFailover State=NormalFailover Suspended=NoStretched Cluster Enabled=NoFailOverStatus=1(UP)



7. Apply power to both of the 7700 FSP Controllers.

8. After several minutes, log in as root and start the Concerto software services on each 7700 FSP Controller by issuing the following command:

Wait approximately 10 minutes for the Concerto software services startup to complete.

9. Inspect failover status, and confirm that both 7700 FSP Controllers return the normal HA status (FailOverStatus: 1 UP) after issuing the following command:

10.After the failover state on both 7700 FSP Controllers shows as FailOverStatus: 1(UP), the 7700 FSP storage cluster system is ready for use.

11.Verify that the 7700 FSP Controllers can access each other by using the ping and sms -v commands and the respective IP addresses for each controller.

Note: Ensure that you enable HA on each 7700 FSP Controller after you have applied power to each 7700 FSP Controller by using the isscli enableha -s command. For more details on configuring HA, see the Failover section in the Symphony Online Help document.

# concerto start all

# sms# isscli getfailoverstatusFailOverStatus: 1(UP)


CHAPTER 3 7700 Flash Storage Platform Device Configuration

This chapter describes the process and the tasks for configuring the devices in a 7700 Flash Storage Platform storage cluster. Before beginning component and cluster configuration, verify that you have completed the following:

• Pre-installation checklist and site information has been collected (for details, see Installation Checklists and Site Information on page 13).

• 7700 FSP devices are properly rack-installed, secured, and grounded.

• Cable connections have been made between all 7700 FSP devices.

• 7700 FSP devices have been powered on.

• Port link state LEDs indicate that links are UP (solid green) on all devices.

Note: If any LED is amber, resolve the problem immediately before continuing with the configuration.

Any configuration information that is not presented in this guide is referenced in the following Violin Systems product documentation:

• 7000 Series Flash Storage Platform Installation Guide

• 6000 Series All Flash Array Installation Guide

• Violin Symphony Installation Guide


Chapter 3 - 7700 Flash Storage Platform Device Configuration

Device Configuration Tasks

This section is an overview of the tasks you must complete to configure all of the devices in the 7700 Flash Storage Platform system. To configure each 7700 FSP system device for your network, perform the following tasks in the order listed in the table.

Configuring 7700 FSP Devices

This section introduces the tasks for configuring the installed 7700 Flash Storage Platform devices:

Task 1: Configuring 7700 FSP Devices on page 50

Task 2: Configuring 7700 FSP Storage Shelves on page 51

Task 3: Using Symphony to Configure and Manage 7700 FSP Devices on page 52

Task 4: Configuring the 7700 FSP Controller on page 56

Task 5: Configuring Brocade 6510 Fibre Channel Switches on page 67

Task 6: Enabling Dedup on page 110

Device Task Description

6000 Series shelf Configuring using a Configuration Wizard and CLI commands:

• Array Controller Modules (ACMs)

• Memory Gateways (MGs)

7000 Series FSP shelf Configuring using one of two methods:

• Simple SetUp configuration process

• Manual configuration (manually running configuration jump-start, initial_config.exp script file, and CLI commands)

Both methods configure the following:

• ACMs

• MGs

• All physical devices assigned to Storage Pool A

• Media is initialized

• HA has been configured

• Configuration Repositories (CRs) created and enabled

Note: For specific details about the two configuration methods, see the latest version 7000 Series Flash Storage Platform Installation Guide.

7700 FSP Controllers Configuring using a Quick-Start utility:

• 7700 FSP Controller software

Table 3.1 Tasks for Configuring 7700 Flash Storage Platform Devices


Configuring 7700 FSP Storage Shelves

Note: There is also one additional task that verifies that the iDRAC interfaces provide connectivity to the 7700 FSP Controllers, which also confirms that the 7700 FSP Controllers have been successfully installed. For details, see Testing iDRAC Interfaces on page 61.

Configuring 7700 FSP Storage Shelves

This section provides the location for information about configuring the ACMs and Memory Gateways for the 6000 Series and 7000 Series FSP storage shelves. When a new shelf is powered on for the first time, all configuration settings remain at their default values. You must change the default settings to communicate with the shelf over your network.

Upgrading 7700 FSP Controllers and Shelves

Violin recommends that you upgrade the 7700 FSP Controllers and the 7000 Series FSP storage shelves to the current released Concerto OS software version after the 7700 FSP components have been assigned IP addresses using the Simple SetUp configuration tool or using the Configuration Wizard (configuration jump-start, CLI commands, and initial_config.exp script file), and before completing any additional component or cluster configuration.

Concerto OS supports an RPM upgrade process for both the 7700 FSP Controllers and the 7000 Series FSP storage shelves. After configuration completes, perform ongoing updates without any I/O disruption. For specific details and upgrade instructions, see the latest version 7700 Flash Storage Platform Release Notes for Violin Concerto OS 7.6.3.x.

Configuring a 6000 Series Shelf

For details and procedures for configuring a 6000 Series unit as a storage shelf in the 7700 FSP storage cluster, see the chapter on setting up and configuring an array in the latest version Violin 6000 Series All Flash Array Installation Guide.

Brocade 6510 Fibre Channel Switches

Configuring using a serial connection and CLI commands:

• Northbound target ports on the 7700 FSP Controllers

• 1:many (1:N) zoning for host initiator and target ports

7700 Flash Storage Platform system

Configuring using Symphony:

• Generate zoning configuration (once switch, shelf, and controllers are configured)

• Add 7700 FSP Controllers

• Add a shelf

• Create LUNs

• Manage SAN clients

• Transfer zoning configuration to client network switches

Device Task Description

Table 3.1 Tasks for Configuring 7700 Flash Storage Platform Devices(Continued)



Configuring a 7000 Series FSP Shelf

For specific details about configuring a 7000 Series FSP as a storage shelf in the 7700 FSP storage cluster, see the chapter on using the Simple SetUp Editor to create one or more configuration files or the chapter on using the Configuration Wizard and script file to configure and setup an array in the latest version Violin 7000 Series Flash Storage Platform Installation Guide.

As part of the 7000 Series FSP shelf configuration process, you can choose between the following two methods:

• An automated process using Simple SetUp Editor

• A manual process using a Configuration Wizard and script file

The Simple SetUp Editor tool allows you to create an array configuration (.cfg) file to use to automatically configure one or more 7000 Series FSPs. The Configuration Wizard process involves using configuration jump-start, CLI commands, and the initial_config.exp script file to configure a single array.

Both methods perform a series of important initial network and HA configuration tasks, including creating the initial storage pools. For specific details about each of these two methods, see the latest version Violin 7000 Series Flash Storage Platform Installation Guide.

Note: Before you set up or allocate space for any storage pool, and specifically before setting up a dedup storage pool, the recommendation is to plan for the most efficient use of your storage pools. For details and best practices, see the latest version Violin 7700 Flash Storage Platform Best Practices Guide. If you plan this for a stretched cluster environment, see the latest version Concerto 7700 FSP Stretch Cluster Implementation and Best Practices Guide for more information.

Using Symphony to Configure and Manage 7700 FSP Devices

This section references the topics in Symphony Help that provide information and procedures for configuring and managing the 7700 FSP cluster devices using Symphony-based procedures, and these include:

• Adding Local Network Devices on page 53

• Activating a Simple SetUp Configured Device on page 53

• Adding Stretched Cluster Devices on page 53

• Creating and Managing Storage Pools on page 54

• Creating and Managing LUNs on a Shelf on page 55

• Creating and Managing SAN Clients on page 56

Note: For information about using Symphony to manage the Fibre Channel zone configuration, see Setting Up Replication on page 68.



Adding Local Network Devices

Symphony Help provides information about adding standalone or cluster storage devices to Symphony. For details, see the topic on adding devices to a local network in the latest version of Symphony Help.

Adding a Device

Using Symphony, add storage devices such as an external 7700 FSP Controller, any of the supported storage shelves, or a standalone array.

Note: After one shelf is configured and added to Symphony, you can continue on with configuring the 7700 FSP Controller.

Specifying the Device Type

Using Symphony, specify the following type of devices you are adding:

• Adding a 7700 FSP Controller

• Adding a 7000 Series FSP as a shelf

• Adding 6000 Series array as a shelf

Activating a Simple SetUp Configured Device

The Simple SetUp configuration tool allows administrators to rapidly configure and deploy multiple 7000 Series FSPs in an Enterprise data center. Symphony automatically lists any newly configured array with a Pending Activation Connection Status in the Devices window. For details on checking for a newly configured array in Symphony, and to activate this new array, see the topic on enabling devices with a Pending Activation status in the latest version Symphony Help.

Adding Stretched Cluster Devices

Symphony Help provides information and procedures for adding stretched cluster devices to Symphony. For details, see the topic on adding devices to a stretched cluster in the latest version Symphony Help.

About Stretched Cluster Configurations

Symphony Help provides a brief overview about a stretched cluster configuration that resides in two distinct data center locations. In this type of stretched cluster configuration, there are both primary and secondary 7700 FSP Controllers.

The primary controller is active in one data center and the secondary controller (on standby for failover) is in the second data center. For basics, see Overview: Stretched Clusters on page 145 in this guide, and for details, see the latest version Concerto 7700 FSP Stretch Cluster Implementation and Best Practices Guide.



Adding 7700 FSP Controllers to a Stretched Cluster Configu-ration

Symphony Help provides information about how you add 7700 FSP Controllers to local and remote sites to create a new FSP. Before you begin any of these processes, make sure you have the IP addresses or device names for the controllers, both local and remote.

Adding a Shelf to a Stretched Cluster

Symphony Help provides information about how you add a shelf to a stretched cluster; the important difference between adding a shelf to a local site and adding one to a remote site is the specific FSP to which you designate as the destination.

Creating and Managing Storage Pools

For more detailed information and procedures on how to create and manage storage pools, see the topic on creating storage pools in the latest version of Symphony Help. Before creating any storage pool, make sure you review and observe the storage pool best practices guidelines in this section.

Storage Pools Best Practices

The 7000 Series FSP storage shelf is an integral component within the 7700 FSP storage cluster. Memory Gateways (MG-A and MG-B) run the Concerto OS and reside on a 7000 Series FSP. Memory Gateways provide the SAN/LAN block storage function. They manage network connectivity and provide storage virtualization services. The best practices to observe when managing storage pools on the Memory Gateways are as follows:

Note: When deduplication (dedup) is enabled and configured on the 7000 Series FSP, ensure that you observe and apply the important storage pool recommendations in this list.

• A storage pool must be created prior to creating LUNs.

• For a standard 7000 Series FSP deployment, it is recommended that you create a single storage pool on MG-A, with MG-B acting as the failover controller in the pair. It is recommended that you assign all physical storage to this one pool.

• If performance and latency is of primary concern, one storage pool may be created per MG. However, this will cause islands of storage as physical storage from one pool cannot be assigned to another pool in the future.

• In 7300 FSPs, a maximum of 32TB of unique data is supported for deduplication. The remaining storage space can be used for thick, thin, and snapshot.

In other FSP types such as 7450 FSPs that support deduplication, you can use the complete storage space for deduplication.

• When dedup is enabled on an array, it must only be configured on MG-A. Deduplication may not be configured on MG-B.

• After physical devices are assigned to a storage pool and a LUN is created, it can be extremely difficult to remove the physical device and will almost always incur data loss. As such, it is recommended to assign only needed physical devices to the storage pool and leave unused physical devices unassigned. This makes allocation easier when it is necessary to expand the storage pool. By following the best practices, you avoid such issues.

• Unassigned physical devices may always be added to expand a storage pool, however once physical devices are assigned to a storage pool they should not be removed.



• Dedup storage pools cannot exceed 32TB in size.

• When creating storage pools, it is important that you do not use the two physical devices that are to act as the Configuration Repositories.

For specific details about the 7000 Series FSP, including installation and initial configuration, configuring HA, storage management, deduplication, client management, and VMware, see the latest version Violin Systems 7000 Series Flash Storage Platform Best Practices Guide.

Creating and Managing LUNs on a Shelf

For information and procedures on how to create and manage a LUN on a shelf in a local network, see the topic on creating LUNs in the latest version Symphony Help, which provides:

• A list of recommended guidelines that are useful for planning and creating southbound data LUNs.

• A procedure for creating a LUN and adding it to a storage pool.

Overview: LUN Types

When creating and exporting LUNs from a supported shelf to a 7700 FSP Controller, there are three possible types of LUNs:

• Dedup: A deduplication LUN could be grouped together into a separate storage pool to create a dedup storage pool at the 7700 FSP Controller level. Dedup LUNs are not supported at the 7700 FSP Controller level, and must be provisioned at the shelf level.

• Thick: A thick LUN could be grouped together into a separate storage pool to create a thick storage pool at the 7700 FSP Controller level.

• Thin: A thin LUN could be grouped together into a separate storage pool to create a thin storage pool at the 7700 FSP Controller level.

• Primary LUN purposes:

— Configuration Repository (CR)

— Data

Note: LUNs must be 512-byte blocks. LUNs that are 4096 block size are not supported.

For the CR, which you enable using Symphony, create two non-ALUA LUNs with a minimum size of 11GB. Use Symphony to share/assign the new 11GB LUNs to both 7700 FSP Controllers with read/write (shared) access rights. For details, see the topic on assigning and unassigning SAN clients in the latest version Symphony Help.

Note: Before you can create LUNs, you must first create storage pools. When you create a LUN, you need to select the storage pool in which it will reside.

In a modular 7700 FSP storage cluster (non-stretch cluster), each 7700 FSP Controller requires only one CR. If there are multiple storage shelves in the configuration, you need to select one of them to act as the CR.



In the case of a 7700 FSP stretched cluster environment, each 7700 FSP Controller ends up with one primary CR and one remote (mirror) CR. For more details, see Configuring a Stretched Cluster on page 148.

For the data LUNs, create two groups of four non-ALUA LUNs, one for each 7700 FSP Controller in the HA pair. For details on creating LUNs, see the topic on adding LUNs in the latest version Symphony Help.

Note: Keep the maximum number of paths for each LUN from the 7700 FSP Controller perspective to no more than eight. This guideline is based on maintaining the required cabling and zoning, and to support the way that the LUNs are exported.

Creating and Managing SAN Clients

Symphony Help provides information and procedures on how to create and manage SAN clients that you physically attach to one of the 7700 FSP shelves in a local network. For details, see the topic on SAN clients in the latest version Symphony Help. SAN clients are devices that you attach to a 7700 FSP shelves, and you must create logical resources to be used by these clients.

Symphony lets you add, edit, delete, assign, and unassign SAN clients. For details, see the following procedures in the latest version Symphony Help that describe how to:

• Create a SAN client

• Edit and delete a SAN client

• Assign and unassign a SAN client

Configuring the 7700 FSP Controller

To configure the 7700 FSP Controller, you review and complete the following tasks:

• Default IP Addresses for the 7700 FSP Controller on page 56

• Setting Up Management Access on page 57

• Configuring 7700 FSP Controllers at Initial Power On on page 59

• Configuring 7700 FSP Controller Management Access on page 60

Default IP Addresses for the 7700 FSP Controller

The 7700 FSP Controller ships with the following factory default addresses supporting the IPMI/iDRAC system interface:

• IPMI IP address: 192.168.0.120/24 (iDRAC on 7700 FSP Controller)

• Management IP address: 192.168.0.121/24 (port 3 on 7700 FSP Controller rear panel)



Setting Up Management Access

Set up management access and log in to a 7700 FSP Controller by using a USB keyboard and VGA monitor as a local console for the first system POST.

Note: Use the front/rear panel USB and VGA ports for keyboard and monitor access to the 7700 FSP Controller as a local console.

There are two methods of using a local VGA console to perform an initial configuration of the 7700 FSP Controllers:

• Configuring management access using the Quick Start configuration utility.

• Configuring from local console only the iDRAC/IPMI access to allow remote Virtual Console access (and complete the Quick Start configuration through the virtual console).

Note: If you planning to configure the 7700 FSP Controllers for iSCSI, see Configuring 7700 FSP Controllers for iSCSI on page 81, for details about iSCSI-specific set up commands.

Using a VGA Setup to Complete the Quick Start Utility

To configure the management IP and IPMI IP addresses, perform the following:

1. Connect a VGA monitor and USB keyboard to the front or rear panel VGA and USB ports.

2. Power on to boot the 7700 FSP Controller.

3. Allow the POST and the Concerto OS system boot to complete.

4. Using the Appliance Set Up Complete screen in the Quick Start configuration utility, set all the necessary values for the 7700 FSP Controller (time zone, IPMI admin user password, network eth0 settings, and the Management and IPMI IP addresses).

For details, see Configuring 7700 FSP Controller Management Access on page 60.

5. After the Quick Start utility completes and the 7700 FSP Controller reboots, access the 7700 FSP Controller using SSH connections and Symphony. Virtual Console access is available via the IPMI address.

Using a VGA Setup for IPMI/iDRAC Remote Console Access to the Quick Start Utility

IPMI/iDRAC provides a Web-browser/HTTPS-based Virtual Console that allows you to remotely access the 7700 FSP Controller POST and Concerto OS. The remote console emulates access using a VGA monitor, USB keyboard, and mouse connected directly to the 7700 FSP Controller.

Note: IPMI/iDRAC provides a Java-based Virtual Console that allows for secure remote access using a standard Web browser.



To preconfigure IPMI/iDRAC to access the Concerto OS Quick Start configuration utility via a Virtual Console, perform the following:

1. Connect a VGA monitor and USB keyboard to the front or rear panel VGA and USB ports.

2. Power on to boot the 7700 FSP Controller.

3. Carefully monitor the POST and after the initial setup and firmware initialization, press F2 to access System BIOS and Settings on the 7700 FSP Controller.

4. Navigate to the IMPMI/iDRAC Settings and iPMI/iDRAC Network Settings.

5. Modify the current default IPv4 settings for the IPMI/iDRAC (192.168.0.120), and reset this IP address to your desired IP address (either as a static or as a DHCP client and record this new IP address).

Factory default values for IPMI/iDRAC: IP Address (192.168.0.120), Subnet Mask (255.255.255.0), and Gateway (192.168.0.2).

6. Press Esc to exit the navigation.

7. Accept the new settings and allow the 7700 FSP Controller to reboot.

The 7700 FSP Controller is now accessible via the Virtual Console at https://<IPMI/iDRAC IP address>.

8. Browse to the assigned IP address to access the iDRAC Management interface using the IPMI/iDRAC Virtual Console (using https://<IPMI/iDRAC IP address>).

9. Accept all security warnings to use the iDRAC unregistered SSL certificate at first connection.

10.At the iDRAC Web logging screen, type in the username and password (Violin default values are "admin" and "violin101"), and click Submit.



11.Navigate to Overview > Server in the navigation panel (left-side of main window).

12.Click Properties in the main window, click the Summary tab, and click Launch in the Virtual Console Preview pane.

13.Download the viewer.jnlp file, and click Open to download and start the session.

Note: The viewer.jnlp file uses a Java Network Launching Protocol file format to launch the Virtual Console on the local desktop because the web browser perceives this link to the Virtual Console downloaded file as a remote application.

14.Accept all Java-based warnings and approval requests.

15.When the Using the Appliance Set Up Complete screen in the Quick Start configuration utility displays, set all of the necessary values to complete Quick Start.

For details, see Configuring 7700 FSP Controller Management Access on page 60.

16.After the Quick Start utility completes and the 7700 FSP Controller reboots, access the 7700 FSP Controller using SSH connections and Symphony.

Note: Ensure that you repeat this process on the other 7700 FSP Controller in your system.

Configuring 7700 FSP Controllers at Initial Power On

To properly configure the 7700 FSP Controllers at initial power on through SCI configuration, you need to complete the following tasks:

• Perform initial setup up on 7700 FSP Controllers.

• Use CLI commands to set new hostname, DNS, NTP, and domain values.

• Configure 7700 FSP Controllers using CLI commands to set SCI values.



Performing Initial Set Up on 7700 FSP Controllers

You must perform setup during the initial configuration of the 7700 FSP Controllers using one of the following methods and the Quick Start utility to configure management settings:

• If you choose the Using a VGA Setup for IPMI/iDRAC Remote Console Access to the Quick Start Utility on page 57, you can interrupt the POST to configure iDRAC for Virtual Console, or allow it to boot until the Quick Start utility.

• If you choose the Using a VGA Setup to Complete the Quick Start Utility on page 57, you can allow it to boot until the Quick Start utility.

For more details, see Setting Up Management Access on page 57, and Configuring 7700 FSP Controller Management Access on this page.

Configuring 7700 FSP Controller Management Access

After the 7700 FSP Controller completes boot up, you are prompted to run the Quick Start configuration utility to configure values for the time zone, the password for the IPMI admin user, the management network (eth0) Eth0 settings for IP, Netmask, Gateway addresses, and the IPMI IP address to suit your own network requirements. After setup, use SSH access to the management IP.

To configure the 7700 FSP Controller (7700 FSP Controller A), do the following:

1. Connect RJ-45 cables from Eth0 (see Figure 2.5) and iPMI to the management network.

2. On the Appliance Set Up Complete screen at the VGA or Virtual Console, type yes and press Enter to begin the configuration process.

If you type no and press Enter, the 7700 FSP Controller will shut down. Modify the default initial configuration after the next system reboot.

3. To set the time zone setting, do one of the following:

— Type s and press Enter to set a new time zone setting, and choose the appropriate time zone for your locale or type q and press Enter to keep the current time zone (America/Los_Angeles).

4. To set the password for the IPMI admin user, do one of the following:

— To enter a new password for the IPMI admin user, type in a password and click OK, or to retain the default password for the IPMI admin user, click Cancel.

Note: The password length must be between 8 and 16 characters, use the following character sets (A-Z, a-z, 0-9, and special characters such as !, @, #, $, %, ^, &, and _), and the password must include at least one uppercase character, one lowercase character, and one special character.

5. Verify the network Eth0 settings for 7700 FSP Controller, and do one of the following:

— Type yes and press Enter to change the default network Eth0 settings, or type no and press Enter to retain the default network Eth0 settings.

Note: At setup, the default network Eth0 setting is the Virtual Interface IP address (embedded port 3), which is a factory default setting.



6. To change the network Eth0 parameter settings for the IP, Netmask, and Gateway addresses, do the following:

— To enter a new IP address, type 1 and press Enter, and type a new IP address in the dotted decimal format (xxx.xxx.xxx.xxx), and press Enter.

— To enter a new Netmask address, type 2 and press Enter, and type a new Netmask address in the dotted decimal format, and press Enter.

— To enter a new Gateway address, type 3 and press Enter, and type a new Gateway address in the dotted decimal format, and press Enter.

— To save your settings, type 4 and press Enter.

7. To change the IPMI IP address, do one of the following:

— To enter a new IPMI IP address, type in new IP address in the dotted decimal format, and press Enter, or to retain the existing IPMI/iDRAC IP address, type q and press Enter.

The Appliance Setup Complete screen displays.

8. Press Enter to continue, and an MG script file stops and restarts all of the Concerto software services and reboots.

9. Log in as "root", and the default password is "ViolinMEM1".

10.Go to 7700 FSP Controller B and repeat the previous series of steps to configure it to match the 7700 FSP Controller A settings.

This completes the initial configuration of the 7700 FSP system. Once you have configured both 7700 FSP Controller A and 7700 FSP Controller B, perform the following:

• Test and verify that you have connectivity using the iDRAC interfaces to both the 7700 FSP Controllers.

• If you can successfully connect to both 7700 FSP Controllers, then your network connectivity is good. If it is not, the test may fail at some point, and you should then troubleshoot the problem. For details, see Testing iDRAC Interfaces on page 61.

11.If this is not already installed on an accessible server in your network, install Symphony. For details, see Connecting Cables to the Fibre Channel Switches on page 28.

Once both 7700 FSP Controllers are configured, perform any additional configuration on the 7700 FSP Controller using Symphony and command line access using SSH. For more details on installing Symphony, see the latest version Violin Symphony Installation Guide.

Testing iDRAC Interfaces

It is important to verify the iDRAC interfaces on the 7700 FSP Controllers to ensure connectivity. This section demonstrates how to perform this procedure.

Prerequisites:

The 7700 FSP Controllers have been successfully installed.

To test iDRAC interfaces, do the following:

1. Open an HTTPS session using the IP address assigned to the iDRAC interface.



An iDRAC Login screen displays.

2. Enter the Username and Password.

The default Username is "admin" and the default Password is "violin101".

Note: Changing the password requires the 7700 FSP Controller to be rebooted.

3. Select This iDRAC for the Domain and click Submit.

The iDRAC System Summary screen confirms you have a valid connection.

Using the CLI to Set Hostname, DNS, NTP, and Domain Values

Set up a terminal session (using a SSH program) to connect to each of the 7700 FSP Controllers in your 7700 FSP storage data cluster, and set the following values on each 7700 FSP Controller:

• Hostname

• Domain Name Server (DNS)

• Network Time Protocol (NTP)

• Domain name



To use CLI commands to set these values on a 7700 FSP Controller, complete the following:

1. Log in to 7700 FSP Controller A using its IP address, and issue the ipstorhostname.sh

CLI command to set a new hostname:

2. Issue the initialize CLI command to initialize the 7700 FSP Controller:

3. Issue the setdns CLI command to set new DNS1 and DNS2 values:

4. Issue the setntp CLI command to set NTP1 and NTP2 options:

5. Issue the setdomainname CLI command to set the domain name option:

6. Issue the setappenddomain CLI command to append a domain to the list:

7. Issue the finalize CLI command:

8. Issue the restart CLI command to restart the 7700 FSP Controller:

9. Issue the start update CLI command to update the Concerto OS:

10.Configure 7700 FSP Controller B using the identical steps, CLI commands, and values.

11.Ensure that you add both 7700 FSP Controllers to Symphony.

Testing SCI Setup on 7700 FSP Controllers Using CLI Com-mands

Set up a terminal session (using PuTTY or a similar SSH program) to connect to each of the 7700 FSP Controllers and set the Storage Cluster Interlink (sci0 and sci1) Network Interface Card (NIC) values when prompted:

Note: Ensure that you have physically connected 10GbE LC management cables between the SCI ports (sci0 and sci1) on the rear panel of the two 7700 FSO Controllers in the 7700 FSP storage cluster. For details, see Connecting Management Cables to 7700 FSP Controllers on page 30.

1. Log in to 7700 FSP Controller A using its IP address, and issue the following CLI command to initialize the 7700 FSP Controller:

[controller ~]# ipstorhostname.sh <newhostname> NOW

[controller ~]# networkconfig.sh initialize

[controller ~]# networkconfig.sh setdns <dns1> <dns2>

[controller ~]# networkconfig.sh setntp <ntp1> <ntp2>

[controller ~]# networkconfig.sh setdomainname <domainname>

[controller ~]# networkconfig.sh setappenddomain <domainname>

[controller ~]# networkconfig.sh finalize

[controller ~]# networkconfig.sh restart 1 1 1

[controller ~]# concerto start update




2. Issue the setnic sci0 CLI command to set the sci0 NIC values:

This command sets the following values for the sci0 NIC:

• <nic-name> sci0

• <yes|no for DHCP> no

• <MTU> 9000

• <interface-count> 1

• <1st-interface-number> -1

• <1st-interface-IP> 169.254.0.2

• <1st-interface-netmask> 255.255.0.0


4. Issue the following finalize CLI command:

5. Issue the following restart CLI command:

6. Issue the following start update CLI command to update Concerto:

7. Log in to 7700 FSP Controller B using its IP address, and issue the following CLI command to initialize the 7700 FSP Controller:



10.Issue the following finalize CLI command:

11.Issue the following restart CLI command:

12.Issue the following start update CLI command to update Concerto:

Set up for both 7700 FSP Controllers has now been completed.

[controller ~]# networkconfig.sh setnic sci0 no 9000 1 -1 1.1.1.1 255.255.255.0













13.Connect the sci0 ports between 7700 FSP Controller A and B using 10 Gbps Ethernet (10GbE) cabling.

14.Confirm link state and IP using the following commands:

15.Issue the ping command from 7700 FSP Controller A to 7700 FSP Controller B (and from the reverse direction) to test access:

The 7700 FSP Controller initial setup has been completed. You must still create LUNs, enable the Configuration Repository (CR), and enable HA using a combination of Symphony Help and CLI commands.

Note: If you will use iSCSI, see Configuring 7700 FSP Controllers for iSCSI on page 81 and complete configuring the 7700 FSP Controllers for iSCSI. After completing iSCSI configuration on the 7700 FSP Controllers, return here to complete the setup for the 7700 FSP Controllers.

Using Symphony to Set Up the 7700 FSP Controller

This section describes the remaining tasks you need to complete set up for the 7700 FSP Controllers:

• Create a SAN client and a LUN to act as a Configuration Repository (CR)

• Create and Enable a CR for each 7700 FSP Controller

• Configure and Enable HA on each 7700 FSP Controller

Creating SAN Clients and CRs

Before creating SAN clients and Configuration Repositories, verify you have completed the following prerequisites:

• All storage shelves have been zoned and recognized by the 7700 FSP Controllers.

• All storage shelves have been installed, configured, and managed by Symphony.

Use Symphony to create a SAN client for each 7700 FSP Controller on all storage shelves that will contain a Configuration Repository (CR) LUN, by completing the following:

1. Create SAN clients using the procedure described in the "Creating and Deleting SAN Clients" topic in Symphony Help on each storage shelf you selected.

2. In Symphony, create a 11GB LUN using the procedure described in the "Adding LUNs" topic in Symphony Help on each storage shelf specified in step 1.

For more details, see Configuring Storage on page 98. To support a stretched cluster, see Stretched Cluster Prerequisites on page 146 for basics. For more detailed information, see the latest version Concerto 7700 FSP Stretch Cluster Implementation and Best Practices Guide.

[controller ~]# ifconfig -a | grep sci -A3

[controller ~]# ping -I sci0 -c 5 -s 9000 169.254.0.3[controller ~]# ping -I sci0 -c 5 -s 9000 169.254.0.1



3. In Symphony, share each newly created 11GB LUN to all 7700 FSP Controllers with read/write (shared) access as described in the topic on assigning and unassigning SAN clients in the latest version Symphony Help.

Note: Each 7700 FSP Controller requires only one Configuration Repository (CR). Even if there are multiple shelves, you only need to designate one CR per 7700 FSP Controller. In the event of the primary 7700 Controller failing, HA will failover to the standby 7700 FSP Controller with the CR in the 7700 FSP storage cluster.

In a 7700 FSP stretched cluster, the CR on one 7700 FSP Controller is mirrored in the secondary 7700 FSP Controller. For details, see the section on preparing the CR in the latest version Concerto 7700 FSP Stretch Cluster Implementation and Best Practices Guide.

4. In Symphony, initiate a physical device rescan on each 7700 FSP Controller using the procedure described in the "Rescanning Physical Devices" topic in Symphony Help.

5. In Symphony, prepare one of the 11GB LUNs for each 7700 FSP Controller by editing the physical device to be Virtualized and update it in the Edit Physical Device window as described in the "Editing a Device" topic in Symphony Help.

Note: Record the SCSI Address in A:C:S:L format listed in the Edit Physical Device window for each 7700 FSP Controller’s 11GB LUN that will act as a CR. You will need this information to verify the CR and enable HA on each of the 7700 FSP Controllers.

Creating and Enabling a CR on a 7700 FSP Controller

Use Symphony to create and enable a CR on each 7700 FSP Controller by completing the following:

1. Create a CR and enable it on 7700 FSP Controller A using the procedure described in the "Create a Configuration Repository" topic in Symphony Help, which describes how to:

• Navigate to Administration > Devices > Failover, and select 7700 FSP Controller A from the navigation pane.

• Select Failover > Configuration Repository, and toggle the Configuration Repository Enabled setting to ON.

• Select the Physical Device from the drop-down list, and click Save.

2. Repeat the same steps to create and enable a CR on 7700 FSP Controller B.


Configuring Brocade 6510 Fibre Channel Switches

Configuring and Enabling HA on a 7700 FSP Controller

7700 FSP Controllers in a 7700 FSP storage cluster are installed in failover pairs to ensure high availability (HA). Use Symphony to enable HA on each 7700 FSP Controller by using the FSP Settings and Failover tabs under Administration > Devices to configure and enable HA on each 7700 FSP Controller and complete the following.

1. Configure and enable HA failover for 7700 FSP Controller A in a 7700 FSP storage cluster using the procedure in the "Configuring Failover for a 7700 FSP or stretched cluster" topic in Symphony Help, which documents how to:

• Navigate to Administration > Devices > Failover, and select 7700 FSP Controller A from the navigation pane.

• Select Failover > Failover Configuration, and toggle the Failover setting to ON.

• Select a Secondary Controller from the drop-down list, and toggle the Stretched Cluster setting to OFF for a 7700 FSP storage cluster.

Note: The secondary 7700 FSP Controller is the partner node in a failover configuration that takes over if a failure occurs. By default, mutual failover is configured between the primary and secondary 7700 FSP Controllers.

• Enter the Primary Monitor IP Address and Secondary Monitor IP Address (also known as heartbeat) in the appropriate fields for the respective 7700 FSP Controllers (A and B), and click Save when you are satisfied with the monitor IP addresses.

Note: You are not allowed to edit the monitor IP addresses once the settings have been saved. Once set, the only way to change monitor IP addresses is to disable failover, make the changes, and re-enable failover again.

• Enter the Primary Controller and Secondary Controller login credentials (Username and Password) for both 7700 FSP Controllers, and click Save.

• Click the Allow Restart check box so that the system restarts, and saves all changes that you configured.

Configuring Brocade 6510 Fibre Channel Switches

For details about preconfiguration and procedures for configuring and setting up the Brocade 6510 Fibre Channel switches for use within the 7700 FSP system, see Configuring Brocade 6510 for a 7700 FSP System on page 139.



Setting Up Replication

One of the last remaining post-installation configuration tasks you may need to set up depends upon if you are using the replication feature. Replication is the process by which you ensure that an array in the 7700 FSP maintains a copy of any LUN, either locally or somewhere else in the storage cluster.

This capability helps prevent damage from failures or disasters in one array, in which you provide the ability to recover without a loss of data. For more details about replication, see the latest version 7000 Series Flash Storage Platform User’s Guide, and see Support for Controller-to-Controller Replication on page 32, and Configuring Network Interfaces for Replication on page 125.

Next Steps

Continue to Chapter 4, Southbound Fibre Channel Switch Zone Configuration for a brief introduction on performing southbound Fibre Channel switch zone Configuration.


CHAPTER 4 Southbound Fibre Channel Switch Zone Configuration

This chapter provides information to better understand and view the Fibre Channel fabric switch zone configuration for the southbound path from the 7700 FSP Controllers to each shelf.

The 7700 Flash Storage Platform system supports 1:N (1:many) zoning, and the southbound zones are set up within the fabric when the following prerequisites have been completed:

• Two 7700 FSP Controllers, two Brocade Fibre Channel switches, and the 7000 Series FSPs or 6000 Series arrays have been properly installed in your storage network.

• All 7700 FSP devices are powered up, and all cable connections have been properly made to the corresponding ports using the supplied cabling and cable labels.

When you have met these prerequisites, the shelf and the 7700 FSP Controllers are able to communicate through the Brocade Fibre Channel switches.

Symphony lets you manage the Fibre Channel zone configuration process, display details about the HBAs in use on each shelf or 7700 FSP Controller in your system, and transfer the zone configuration to your Brocade Fibre Channel switches. For details, see Managing the Zoning Configuration on page 71.


Chapter 4 - Southbound Fibre Channel Switch Zone Configuration

Understanding a Fibre Channel Switch Zone

Note: The CLI commands for the Fibre Channel switches in this chapter apply to Brocade switches only. If your configuration uses Fibre Channel switches from another vendor, use the comparable CLI commands from that vendor.

Figure 4.1 shows an example 7700 Flash Storage Platform configuration that contains:

• Two 7700 FSP Controllers connected to two southbound Fibre Channel switches

• Two Fibre Channel switches connected to a single shelf

Note: In Figure 4.1, rear panel slots 2 and 7 are used for northbound data connections. The ports associated with these slots (2-0, 2-1, 7-0, and 7-1) are either 16Gb Fibre Channel or 10Gb Ethernet ports.

WWPN zones on the Fibre Channel switches will allow all 7700 FSP Controller Initiator ports to access all target ports on the storage shelves.

Note: To prevent HA failover issues, verify that the four southbound Fibre Channel ports are set to Initiator mode and the four northbound Fibre Channel ports are set to Dual mode.

Figure 4.1 7700 Flash Storage Platform Configuration with Southbound Fibre Channel Switches


Managing the Zoning Configuration


Symphony creates a southbound zone configuration file for each 7700 FSP storage cluster to add to the Fibre Channel switch configuration of both southbound storage cluster switches that support the 7700 FSP storage cluster. The Fibre Channel switch zone configuration includes aliases for all WWPNs for all device ports and allows all 7700 FSP Controller dual mode initiator WWPNs to access all of the storage shelf target WWPNs.

Symphony can manage and monitor all of the 7700 FSP devices once you have added them to Symphony. For an overview and details, see the topic on adding devices to be managed by Symphony in the latest version Symphony Help.

Note: When naming a switch zone configuration or creating an alias with Brocade 6510 switches, observe the naming conventions (see Zoning and Alias Naming Conventions on this page).

Zoning and Alias Naming Conventions

Observe the following Brocade switch zoning and alias naming conventions when creating a switch zone configuration or alias in a 7700 FSP storage cluster:

Note: The following is a restriction for zone, alias, and configuration names: they cannot begin with “bfa_”,“red_”, “lsan_red_”, or “d__efault__”. In addition, zone configuration names cannot begin with “r_e_d_i_r_c__fg” because these are reserved prefixes.

Zoning Naming Conventions

A zone is a way to assign a name that identifies a partitioning of a Fibre Channel fabric into smaller subsets to add security and simplify management. Zoning most commonly applies to the switched fabric topology (FC-SW).

• Zone names must begin with an alphabetic character, and they may contain alpha-numeric characters and the underscore (_) character.

• Zone names are not case-sensitive.

• Names cannot begin with a numeric character or a special character.

• The recommended character limit is 64 characters.

• Duplicate names are not allowed between zones, zone aliases, and zone configurations within a zone database.

• If you enter an invalid zone or zone configuration name, an error or warning message displays depending on the type of fabric you are trying to zone.

Alias Naming Conventions

Use alias names to assign a unique or identifiable name to a device, or to group together multiple devices under a single alias name to simplify entries and allow an intuitive naming structure (for example, using LINUX_Hosts to define all Linux hosts in the fabric).

• An alias must be a unique alpha-numeric string that begins with an alphabetic character, and underscore characters (_) are allowed.



• Alias names are case sensitive (for example, linux_hosts is not the same name as LINUX_Hosts).

• Alias names can simplify the administrative process, but they are not required to define zones.

Note: The following subsections provide procedures for using Symphony to perform two important 7700 FSP-related tasks.

Confirming Southbound HBA Information

Symphony lets you confirm that the southbound HBA ports are properly configured on your 7700 FSP Controllers (for more details, see the topic on setting downstream HBAs in the latest version Symphony Help).

To confirm southbound HBA and port information for a 7700 FSP Controller, do the following:

1. Select Manage > Devices.

2. In the left navigation panel under Manage Devices, click the 7700 FSP Controller you want to view, click the HBAs tab in the main window, and click Downstream HBAs (down-arrow icon).

The Select Downstream HBAs window displays.

3. Confirm that the selected check boxes correspond to the correct southbound HBA ports you want.

• For Fibre Channel controllers, these should be ports 100, 101, 104, and 105.

• For iSCSI controllers, these should be ports 100, 101, 102, and 103.



Transferring the Zone Configuration to FC Switches

Use the Fibre Channel zone configuration gathered by Symphony, and transfer this into the Brocade 6510 Fibre Channel switches that are part of your 7700 Flash Storage Platform system.

To download the current Fibre Channel zone configuration to your FC switches, do the following:


2. In the left panel under Manage Devices, select a 7700 FSP system, and in the main window, click the Zone Config tab.

Fibre Channel zone configuration is automatically generated from the FC initiator HBAs on the 7700 FSP Controllers to the FC target HBAs on storage shelves in the 7700 FSP.

In this example 7700 FSP configuration, there are two 7700 FSP Controllers and a single 7000 Series FSP, with the Fibre Channel zone configuration including the following command entries:

— "alicreate": command creates aliases for each WWPN target or initiator for the cluster (for 7700 FSP Controller A and B, and for every 7000 Series FSP or 6000 Series MG-A and MG-B).

— "zonecreate": command creates a one-to-many zone for each initiator for every target.

— "cfgcreate": command creates the zone configuration.

— "cfgadd": command adds the Fibre Channel zones to the configuration.

3. (Optional) Type a unique name for the Fibre Channel zone configuration in the Zone Configuration Name field and click Generate to generate it.

Note: When naming a switch zone configuration with Brocade 6510 switches, do not start zone names with numeric characters (prepend zone names with alphabetic characters only).

4. To transfer the Fibre Channel zone configuration, select and highlight the lines in the ZONE CONFIG window, and right-click to Copy.

One option is to save the Fibre Channel zone configuration to a text editor as a file that allows you to review, modify attributes, or save this file before transferring it to the FC switches. Both FC switches use the exact same zone configuration for consistency and reliability.

5. Start an SSH session (using PuTTY or a similar program) using the IP address of the first

6510 Brocade Fibre Channel switches.

FC7700-switch-a:root>



6. At the FC switch-A prompt, right-click to Paste the Fibre Channel zone configuration.

If you are not pasting the entire zone configuration, repeat this process until you have copied the entire Fibre Channel zone configuration into the first FC switch.

Note: If you do not save the Fibre Channel zone configuration to a separate file, it is recommended that you only copy over 10 lines at a time to prevent any potential session time outs when connecting to your FC switches.

7. Confirm the transfer of the final script line entry (for example, cfgadd "sample_zoning_cfg", "...zone"), by adding a line break (by pressing Enter) after the last line.

8. Issue the following commands after applying the zoning configuration to the switch:

9. Verify that the zone configuration is in effect by issuing the following commands:

FC7700-switch-a:root> cfgenable "sample_zoning_cfg"You are about to enable a new zoning configuration. This action will replace the old zoning configuration with the current configuration selected. If the update includes changes to one or more traffic isolation zones, the update may result in localized disruption to traffic on ports associated with the traffic isolation zone changes.Do you want to enable 'sample_zoning_config' configuration (yes, y, no, n): [no] yeszone config "Portzone_7700A" is in effectUpdating flash...

FC7700-switch-a:root> cfgshowEffective configuration: cfg: sample_zoning_cfg zone: array_3159_100_zone 21:00:00:0e:1e:18:a9:30 21:00:00:1b:97:22:e8:e0 21:00:00:1b:97:22:e8:e1 21:00:00:1b:97:22:e7:d0 21:00:00:1b:97:22:e7:d1 21:00:00:1b:97:22:ea:90 21:00:00:1b:97:22:ea:91 21:00:00:1b:97:22:b2:40 21:00:00:1b:97:22:b2:41 zone: array_3159_101_zone 21:00:00:0e:1e:18:a9:31 21:00:00:1b:97:22:e8:e0 21:00:00:1b:97:22:e8:e1 21:00:00:1b:97:22:e7:d0 21:00:00:1b:97:22:e7:d1 21:00:00:1b:97:22:ea:90 21:00:00:1b:97:22:ea:91 21:00:00:1b:97:22:b2:40 21:00:00:1b:97:22:b2:41



Note: This is only a limited display of the entire zone configuration. The cfgshow command displays the entirety of the zone configuration.

10.Confirm that the zone configuration is saved by issuing the following command:

11.Repeat the process in steps 3 through 9 to transfer the Fibre Channel zone configuration into the second FC switch (for example, FC7700-switch-b) in your 7700 FSP system.

For Fibre Channel switch-related configuration information, see the documentation for the Brocade 6510 switch listed in Reference Documents on page 3.

Copying a Zone Configuration into a Replacement FC Switch

If the need exists during an installation for performing a field replacement of a failed or modified FC switch (or if you are setting up a stretched cluster configuration), you can copy the existing zone configuration into the replacement FC switch to support your 7700 FSP system. This copy process will not move or copy port or Inter-Link Switch (ISL) licensing from one switch to another.

Prerequisites

This section is intended as reference information and is not intended to serve or replace a service guide. Anyone attempting to perform an FRU procedure on a FC switch and copy an existing zone configuration into the replacement switch should have the following level of experience:

• Network/storage administrator

• Familiar with using network file systems and CLI commands

• Familiar with using FC switches, including performing upload and download file operations

• Familiar with Violin Systems storage arrays and SANs

To copy a zone configuration from a running FC switch into another FC switch, perform the following:

1. Preconfigure the new switch IP (for complete details, see Configuring Brocade 6510 Fibre Channel Switches on page 67).

2. Start an SSH session (using PuTTY or a similar program) using the IP address of the current 6510 Brocade Fibre Channel switch that will act as your source for the zone configuration:

FC7700-switch-a:root> cfgsave

FC7700-switch-a:root>



3. Upload the current zone configuration from the source FC switch to an SCP, FTP, or SFTP file server or USB memory device by issuing the following command as shown (with some example values):

Note: The configupload command lets you choose to upload all, chassis, or switch only, and provides a number of parameters and options.

4. Edit the new FC switch configuration file as needed to only copy the necessary zone configuration (or stretched cluster information) from the source FC switch to a new configuration file.

5. Prepare the new FC switch by issuing the following commands:

To disable the switch prior to making configuration changes, issue this command:

To disable the current zone configuration, issue this command:

To clear all zone configuration, issue this command:

To save this cleared state for the FC switch, issue this command:

FC7700-switch-a:root> configuploadProtocol (scp, ftp, sftp, local) [ftp]: sftpServer Name or IP Address [host]: 10.18.18.24User Name [user]: jdoeFile Name [<home dir>/config.txt]:Section (all|chassis|switch [all]):Password: ******configUpload complete: All config parameters are uploaded

FC7700-switch-a:root> switchdisable

FC7700-switch-a:root> cfgdisableYou are about to disable zoning configuration. This action will disable any previous zoning configuration.Do you want to disable zoning configuration? (yes, y, no, n): [no] y

FC7700-switch-a:root> cfgclearThe Clear All action will clear all Aliases, Zones, FA Zones and configurations in the Defined configuration. Run cfgSave to commit the transaction or cfgTransAbort to cancel the transaction.Do you really want to clear all configurations? (yes, y, no, n): [no] y

FC7700-switch-a:root> cfgsaveYou are about to save the Defined zoning configuration. This action will only save the changes on Defined configuration. Any changes made on the Effective configuration will not take effect until it is re-enabled. Until the Effective configuration is re-enabled, merging new switches into the fabric is not recommended and may cause unpredictable results with the potential of mismatched Effective Zoning configurations.Do you want to save Defined zoning configuration only? (yes, y, no, n): [no] y



6. Download the source zone configuration from SCP, FTP, or SFTP file server or USB memory device by issuing the following command:

The zone configuration is saved automatically. If you intend to re-run the configdownload command prior to reboot, you may wish to use the following commands:

Note: The configdownload command displays a number of different commands, parameters, and options for use in performing download operations for your network environment. You may want to select just the switch section of the configuration file.

7. Reboot the new FC switch by issuing the following command:

8. Following the reboot, issue the following command to enable the zoning configuration downloaded to the new switch:

9. Inspect that the zone configuration is in effect by issuing the following command (which displays the effective zone configuration information):

FC7700-switch-b:root> configdownload

cfgtranshow and cfgtransabort

FC7700-switch-b:root> rebootWarning: This command would cause the switch to rebootand result in traffic disruption.Are you sure you want to reboot the switch [y/n]? yThe system is going down for a reboot NOW ! !

FC7700-switch-b:root> cfgenable "sample_zoning_cfg"You are about to enable a new zoning configuration. This action will replace the old zoning configuration with the current configuration selected. If the update includes changes to one or more traffic isolation zones, the update may result in localized disruption to traffic on ports associated with the traffic isolation zone changes.Do you want to enable 'sample_zoning_config' configuration (yes, y, no, n): [no] yeszone config "Portzone_7700A" is in effectUpdating flash...

FC7700-switch-b:root> cfgshowEffective configuration: cfg: sample_zoning_cfg zone: array_3159_100_zone 21:00:00:0e:1e:18:a9:30 21:00:00:1b:97:22:e8:e0 21:00:00:1b:97:22:e8:e1 21:00:00:1b:97:22:e7:d0 21:00:00:1b:97:22:e7:d1 21:00:00:1b:97:22:ea:90 21:00:00:1b:97:22:ea:91 21:00:00:1b:97:22:b2:40 21:00:00:1b:97:22:b2:41



10.Confirm that the zone configuration is saved by issuing the following command:

Next Steps

Before you attempt to allocate the remaining free physical devices for use, ensure that you have completed the following prerequisites:

• Read, understand, and observe the storage pool best practices (see storage pools best practices in the latest version 7000 Series Flash Storage Platform Installation Guide).

• Allocate the remaining free storage space on each shelf and make it available to the 7700 FSP Controllers. This may involve moving all physical devices from southbound shelves to storage pools on the 7700 FSP Controllers, and preparing them for discovery and use by the northbound hosts.

Note: In general, a single storage pool is created on MG-A with all of the physical device on each of the storage shelves in the 7700 FSP storage cluster. From this amount, 32TB can be used for dedup and the remainder can be allocated for use as thick/thin/snapshot. If you plan to allocate the remaining storage from the southbound storage shelves, configure the out-of-space alerts on the storage shelves (assuming this is thick LUNs) as appropriate for your specific needs.

FC7700-switch-b:root> cfgsave


CHAPTER 5 Configuring Northbound Switches for Fibre Channel and iSCSI Operations

This chapter provides instructions for configuring northbound client network switches for both Fibre Channel and iSCSI operations in the following topics:

• Configuring Northbound Switches on page 79

• Configuring iSCSI on page 80

Before You Begin

1. Ensure that all connections to and from the 7700 Flash Storage Platform devices are secure.

2. Ensure that all devices are properly installed in the equipment rack and secured.

3. Ensure that all of the devices have been powered on.

4. Check connection indicators: LEDs and port links should be solid green. If otherwise, or if any LED is amber, solve the problem before continuing.

Configuring Northbound Switches

This section covers the process for configuring the Fibre Channel switches on the client network. Violin recommends that you use best practices to eliminate vulnerability to single points of failure and to distribute Fibre Channel and iSCSI connections among the two northbound FC or iSCSI HBAs.

The procedures in this section assume that HA has been enabled between the 7700 FSP Controllers before attempting to configure the client storage network northbound from the 7700 FSP Controllers.

Note: By default, the four southbound Fibre Channel ports are set to Initiator mode (the four northbound Fibre Channel ports are set to Dual mode). To confirm southbound ports, see Confirming Southbound HBA Information on page 72.


Chapter 5 - Configuring Northbound Switches for Fibre Channel and iSCSI Operations

To configure the northbound path from the 7700 FSP Controllers to the client network, do the fol-lowing:

1. Confirm which FC or iSCSI ports on the 7700 FSP Controller are to be used as a target port for northbound connectivity (see Figure 2.1, which shows all Fibre Channel HBA ports and slot numbers, and Figure 2.2, which shows all iSCSI HBA ports and slot numbers).

Use the following FC ports and HBA slot and port numbers on the 7700 FSP Controller rear panel:

— HBA slots 2-1 (port 107) and 2-0 (port 106)

— HBA slots 7-1 (port 103) and 7-0 (port 102)

Use the following iSCSI ports and HBA slot and port numbers on the 7700 FSP Controller rear panel:

— HBA slots 2-0 (port isc2) and 2-1 (port isc3)

— HBA slots 7-0 (port isc0) and 7-1 (port isc1)

2. In Symphony, identify the designated FC or iSCSI ports you want as target (northbound) ports by selecting and enabling these ports.

FC target ports are automatically configured when you create storage containers on the 7700 FSP Controllers. You can verify ports using Symphony (see Confirming Southbound HBA Information on page 72).

iSCSI target ports must be configured manually. For details, see Configuring iSCSI on page 80, and the latest version Symphony Help. You can verify ports using Symphony (see Confirming Southbound HBA Information on page 72).

3. Confirm that all northbound cable connections have been properly patched, and that the link state is UP.

4. Create zones in client FC switches or VLANs in client iSCSI network to allow every client port to communicate with every 7700 FSP Controller northbound target ports.

5. Use Symphony to create SAN clients by specifying the management IP address and the Fibre Channel WWPN or iSCSI initiator identity for each client server platform. For details, see the topic on creating and deleting SAN clients in the latest version Symphony Help.

Configuring iSCSI

This section and its subsections address enabling iSCSI and configuring northbound iSCSI ports and iSCSI clients, targets, and LUNs. CLI commands allow scanning and inspecting physical devices, and Symphony allows managing iSCSI SAN clients. See the latest version Symphony Help for iSCSI-specific topics and procedures.

Prerequisites

Install on the client hosts all of the necessary iSCSI multipath software packages before you attempt adding the iSCSI client to the 7700 FSP Controllers or trying to assign iSCSI targets to the new client. For more details on using iSCSI-related commands, see the latest version Concerto Command Line Interface Reference.


Configuring iSCSI

Configuring 7700 FSP Controllers for iSCSI

After the 7700 FSP Controllers are configured with management and Storage Cluster Interlink (SCI) network access (see Configuring 7700 FSP Controllers at Initial Power On on page 59), complete the following tasks to enable iSCSI support:

• Enable iSCSI support on both the 7700 FSP Controllers

• Configure the iSCSI network interfaces

Enabling iSCSI on 7700 FSP Controllers

Set up a terminal session (using PuTTY or a similar SSH program) to connect to both of the 7700 FSP Controllers in your 7700 FSP storage data cluster, and enable iSCSI support on the specified host servers using the CLI command as shown:

Log in and issue the isscli enableiscsi CLI command to enable iSCSI support on both 7700 FSP Controllers:

Configuring the iSCSI Network Interfaces

Set up a terminal session (using PuTTY or a similar SSH program) to connect to each of the 7700 FSP Controllers in your 7700 FSP storage data cluster.

1. Log in to 7700 FSP Controller A using its IP address, and issue the following CLI command to initialize 7700 FSP Controller A:

2. Issue the setnic isc0 CLI command to set the iSCSI VLAN A (isc0) interface values on 7700 FSP Controller A:

This command sets the following values for the isc0 VLAN A interface (with the other VLAN IP addresses for VLAN B, VLAN C, and VLAN D incrementing accordingly):

• <iscsi-interface-name> isc0

• <yes|no for DHCP> no

• <MTU> 9000

• <interface-count> 1

• <1st-interface-number> -1

• <ip-address> controller-a-isc0

• <subnetmask> vlanA-subnetmask

3. Issue the setnic isc1 CLI command to set the iSCSI VLAN B (isc1) interface values on 7700 FSP Controller A:

[controller ~]# isscli enableiscsi

Command: enableiscsi executed successfully.


[controller ~]# networkconfig.sh setnic isc0 no 9000 1 -1 <controller-a-isc0> <vlanA-subnetmask>

[controller ~]# networkconfig.sh setnic isc1 no 9000 1 -1 <controller-a-isc1> <vlanB-subnetmask>



4. Issue the setnic isc2 CLI command to set the iSCSI VLAN C (isc2) interface values on

7700 FSP Controller A:

5. Issue the setnic isc3 CLI command to set the iSCSI VLAN D (isc3) interface values on

7700 FSP Controller A:

6. Issue the following finalize CLI command:

7. Issue the following restart CLI command:

8. Issue the following start update CLI command to update Concerto:

9. Log in to 7700 FSP Controller B using its IP address, and issue the following CLI command to

initialize 7700 FSP Controller B:

10.Issue the setnic isc0 CLI command to set the iSCSI VLAN A (isc0) interface values on 7700 FSP Controller B:

This command sets the following values for the isc0 VLAN B interface on 7700 FSP Controller B (with the other VLAN IP addresses for VLAN B, VLAN C, and VLAN D incrementing accordingly).

11.Issue the setnic isc1 CLI command to set the iSCSI VLAN B (isc1) interface values on 7700 FSP Controller B:

12.Issue the setnic isc2 CLI command to set the iSCSI VLAN C (isc2) interface values on

7700 FSP Controller B:

13.Issue the setnic isc3 CLI command to set the iSCSI VLAN D (isc3) interface values on

7700 FSP Controller B:

[controller ~]# networkconfig.sh setnic isc2 no 9000 1 -1 <controller-a-isc2> <vlanC-subnetmask>

[controller ~]# networkconfig.sh setnic isc3 no 9000 1 -1 <controller-a-isc3> <vlanD-subnetmask>





[controller ~]# networkconfig.sh setnic isc0 no 9000 1 -1 <controller-b-isc0> <vlanA-subnetmask>

[controller ~]# networkconfig.sh setnic isc1 no 9000 1 -1 <controller-b-isc1> <vlanB-subnetmask>

[controller ~]# networkconfig.sh setnic isc2 no 9000 1 -1 <controller-c-isc2> <vlanC-subnetmask>

[controller ~]# networkconfig.sh setnic isc3 no 9000 1 -1 <controller-d-isc3> <vlanD-subnetmask>


Configuring iSCSI

14.Issue the following finalize CLI command:

15.Issue the following restart CLI command:

16.Issue the following start update CLI command to update Concerto:

iSCSI network interfaces have been set up for both 7700 FSP Controllers.

17.Confirm link state and IP using the following commands:

18.Issue the ping command from both 7700 FSP Controller A and 7700 FSP Controller B to test access:

The iSCSI network interface configuration for the 7700 FSP Controllers has been completed. Return to Configuring 7700 FSP Controller Management Access on page 60, and resume with the remaining processes to complete the 7700 FSP Controller configuration.

Configuring iSCSI Clients, Targets, and LUNs

This section provides examples and references to Violin Systems documentation for CLI commands and Symphony procedures that are needed to enable iSCSI support, configure iSCSI clients, create an iSCSI target, and assign LUNs to an iSCSI target. iSCSI services are enabled in Confirming iSCSI Support on page 83.

Confirming iSCSI Support

Confirm that iSCSI support is enabled on both 7700 FSP Controllers by issuing the isscli enableiscsi CLI command on the specified host server as shown:




[controller ~]# ifconfig -a | grep isc -A3

[controller ~]# ping -I isc0 -c 5 -s 9000 <client-iscsi-vlanA>[controller ~]# ping -I isc1 -c 5 -s 9000 <client-iscsi-vlanB>[controller ~]# ping -I isc2 -c 5 -s 9000 <client-iscsi-vlanC>[controller ~]# ping -I isc3 -c 5 -s 9000 <client-iscsi-vlanD>

[controller ~]# isscli enableiscsi

Command: enableiscsi executed successfully.



Locating an Initiator Name to Use for an iSCSI Client

To discover an iSCSI initiator to add as an iSCSI client, issue the isscli getiscsiinitiators CLI command as shown:

Note: It is recommended that you collect initiator IQNs (iSCSI Qualified Names) from your client servers directly, because in new environments, the unconfigured, undiscovered, or unconnected initiators may not yet be discoverable.

Adding an iSCSI Client with a Valid Initiator Name

To add an iSCSI client, issue the isscli addclient CLI command as shown:

About iSCSI Client Names and Commands

Because iSCSI client names cannot be changed once created, each name must be unique and used only once on a Memory Gateway. However, the same iSCSI client name is allowed on both Memory Gateways. Host or cluster names are often used as client names.

Client ID numbers are assigned automatically and sequentially by each Memory Gateway, and client IDs for deleted clients are not re-used. The iSCSI client command options include the following parameters (showing the respective settings from the previous CLI example):

• -s = Memory Gateway name or ID (san-array3003-mgb)

• -c = Unique iSCSI client name; 7700 FSP Controller (cont-ib1-cn6)

• -t = iSCSI target (ISCSI)

• -d = Client management IP address; not an iSCSI data IP address (12.16.10.6)

• -o = Client OS type that is installed; Windows, Linux, HP-UX, AIX, Solaris, VMware, Macintosh, with the default OS being Windows (Linux)

• -i = iSCSI Qualified Name (IQN) representing the iSCSI client initiator (iqn.198812.com.oracle:dd6af6e2795)

The iSCSI client authentication options include the following parameters:

• -du = iSCSI default CHAP authentication user

Note: Some network environments may expect the Challenge-Handshake Authentication

isscli getiscsiinitiatorsTotal iSCSI Initiators: 3iSCSI Initiator / IP address------------------------------------------------iqn.1988-12.com.oracle:dd6af6e2795 (12.16.10.6)iqn.1988-11.com.oracle:dd6ad6a2696 (12.15.10.5)iqn.1988-13.com.oracle:dd6cf6d2213 (12.14.10.4)

[controller ~]# isscli addclient -c <clientname> -t ISCSI -d 12.16.10.6 -o Linux -i iqn.1988-12.com.oracle:dd6af6e2795

Command: addclient executed successfully.


Configuring iSCSI

Protocol (CHAP) user name to match the initiator or the target IQN. If a user name is not specified, the initiator IQN will be used.

• -cs = iSCSI CHAP user secret/password

• -mc = Optional Mutual CHAP (on/off) to enable reciprocal CHAP authentication

• -mu = Mutual CHAP user name (used when creating a new user)

Note: If this user name is taken, use the getmutualchapusers, deletemutualchapusers, or resetmutualchapuserpwd commands to view or delete current Mutual CHAP user, or to reset the password for a Mutual CHAP user.

• -ms = Mutual CHAP user secret/password

A recommended practice to follow when using CLI commands to add clients is to begin by first inspecting the current list of users. If you are using authentication, you should also inspect iSCSI and Mutual CHAP users.

The following are some useful commands for inspecting and collecting client, iSCSI user, and Mutual CHAP user information:

• getclientlist (collects a list of client names)

• getclientproper -c <clientname> (shows the properties and attributes for a specific user)

• getclientvdevlist -c <clientname> -t iscsi -T -l -a(collects a list of targets and LUNs assigned to a specific user)

• getisciusers(collects a list of iSCSI users)

• getmutualchapusers(collects a list of Mutual CHAP users)

Use Symphony to add, edit, or delete SAN iSCSI clients. For more details, see the topic on creating and deleting SAN clients in the latest version Symphony Help (or use CLI commands to add, edit, or delete SAN iSCSI clients). For more details, see the latest version Concerto Command Line Interface Reference.

Adding an iSCSI Client User with CHAP Authentication

If you want to require authentication to access an iSCSI client, issue the isscli adduser CLI command, which creates an iSCSI user with CHAP authentication enabled as shown:

[root@san-array3003-mgb ~]# isscli adduser -s 12.0.0.1 -t I -N myuser -W chapauth123456

Command: adduser executed successfully.



To verify that the new iSCSI user (myuser) with CHAP authentication was added, issue the following isscli getiscsiusers CLI command as shown:

Options for Adding an iSCSI User with CHAP Authentication

You have two options for adding an iSCSI user with CHAP authentication:

• Adding a client with CHAP authentication enabled

• Modifying an existing client and enabling CHAP authentication using the setiscsiclientprop CLI command

Adding a Client with CHAP Authentication Enabled

To add an iSCSI client with mutual CHAP authentication enabled, issue the isscli addclient CLI command as shown:

Note: Choose to exclude the use of the -mc, -mu, and -ms options if you prefer one-way CHAP authentication instead of two-way (mutual) authentication. For more details, see the iSCSI client authentication options in About iSCSI Client Names and Commands on page 84.

Enabling CHAP Authentication on an Existing Client

To enable CHAP authentication on an existing iSCSI client that was added without authentication, issue the isscli addclient CLI command as shown:

If CHAP authentication is enabled on the 7700 FSP Controller when you add the iSCSI client, you need to make sure that the CHAP Settings in the iscsid.conf file (in /etc/iscsi/) are modified on the client side to successfully establish an iSCSI connection between the iSCSI client and the 7700 FSP Controller. The lines in the iscsid.conf file that need to be modified are shown in red:

[root@san-array3003-mgb ~]# isscli getiscsiusersTotal iSCSI Users: 3iSCSI User------------------------------------------------------------iscsiuseriqn.1988-12.com.oracle:dd6af6e2795myuser

Command: getiscsiusers executed successfully.

[root@san-array3003-mgb ~]# isscli addclient -s san-array3003-mgb -c lab-ib1-cn6 -t ISCSI -d 10.5.10.1 -o Linux -i iqn.1988-12.com.oracle:dd6af6e2795 -du iqn.1988-12.com.oracle:dd6af6e2795 -cs ViolinMEM123456 -mc on -mu iqn.1988-12.com.oracle:dd6af6e2795 -ms ViolinMEM123456

[root@san-array3003-mgb ~]# isscli setiscsiclientprop –c lab-ib1-cn6 -du iqn.1988-12.com.oracle:dd6af6e2795 -cs ViolinMEM123456


Configuring iSCSI

Note: You must modify the iscsid.conf file before the target is discovered by iscsiadm. If the target is already discovered before you make the required modifications to the file, you will need to delete the discovered target and re-discover it.

The following example shows a successful login by the iSCSI client after the modifications in the iscsid.conf file have been made prior to discovery by the iscsiadmin:

# *************# CHAP Settings# *************

# To enable CHAP authentication set node.session.auth.authmethod# to CHAP. The default is None.# node.session.auth.authmethod = CHAP

# To set a CHAP username and password for initiator# authentication by the target(s), uncomment the following lines:# node.session.auth.username = iqn.1988-12.com.oracle:dd6af6e2795# node.session.auth.password = ViolinMEM123456

# To set a CHAP username and password for target(s)# authentication by the initiator, uncomment the following lines:#node.session.auth.username_in = username#node.session.auth.password_in = password

# To enable CHAP authentication for a discovery session to the target# set discovery.sendtargets.auth.authmethod to CHAP. The default is None.# discovery.sendtargets.auth.authmethod = CHAP

# To set a discovery session CHAP username and password for the initiator# authentication by the target(s), uncomment the following lines:# discovery.sendtargets.auth.uZsername = iqn.1988-12.com.oracle:dd6af6e2795# discovery.sendtargets.auth.password = ViolinMEM123456

[root@lab-ib1-cn6 ~]# iscsiadm -m node -lLogging in to [iface: default, target: iqn.2004-02.com.vmem-concerto.san-array3003-mgb.lab-ib1-cn6-25, portal: 192.168.20.106,3260] (multiple)

Logging in to [iface: default, target: iqn.2004-02.com.vmem-concerto.san-array3003-mgb.lab-ib1-cn6-25, portal: 192.168.10.106,3260] (multiple)Login to [iface: default, target: iqn.2004-02.com.vmem-concerto.san-array3003-mgb.lab-ib1-cn6-25, portal: 192.168.20.106,3260] successful.Login to [iface: default, target: iqn.2004-02.com.vmem-concerto.san-array3003-mgb.lab-ib1-cn6-25, portal: 192.168.10.106,3260] successful.



Adding an iSCSI Target under an Existing iSCSI Client

If you want to add an iSCSI target in which its initiator resides in an existing iSCSI client and the IP addresses for the target (typically, these are 10 GbE ports on the Memory Gateways) are known, and the access settings are Read/Write Non-Exclusive, issue the command as shown:

To verify the name of the target you just created and its related information, issue the following command:

To successfully ensure you connect to the initiator, use the iscsiadm command to check on the client side that the name of the target node discovered by the initiator is the same as the one you just created.

To perform this check, issue the following command:

Note: If for any reason the name of the target displayed on the client side is not the same, you need to issue the iscsiadm command to delete the old target node and re-discover the latest target node created on the 7700 FSP Controller.

[root@san-array3003-mgb san-array3003-mgb]# isscli createiscsitarget -c lab-ib1-cn6 -I 192.168.10.106,192.168.20.106 -a NNew ISCSI Target ID: 15Command: createiscsitarget executed successfully.

[root@san-array3003-mgb san-array3003-mgb]# isscli getiscsitargetinfo -r 15

ISCSI Targets: 1

Target Name Target ID IP Address Lun Access Mode Target Type Always Redirect Redirect IP Address----------------------------------------------------------------------iqn.2004-02.com.vmem-concerto.lab-fil3003-mgb.lab-ib1-cn6-15 15 192.168.10.106 192.168.20.106 0 Read/Write Non-Exclusive iSCSI false (null)

Command: getiscsitargetinfo executed successfully.

[root@lab-ib1-cn6 ~]# iscsiadm -m node192.168.20.106:3260,0 iqn.2004-02.com.vmem-concerto.san-array3003-mgb.lab-ib1-cn6-15192.168.10.106:3260,0 iqn.2004-02.com.vmem-concerto.san-array3003-mgb.lab-ib1-cn6-15


Configuring iSCSI

If this has occurred, after you delete the old node from the iSCSI client and re-discover the target node, the login process will complete without issue. The following example shows the old node as deleted and the new target node is discovered, and login succeeds without issue:

Assigning LUNs to an Existing iSCSI Target

If you want to assign a virtual device with (for example, VID=3) to an iSCSI target (with for example, Target_ID=15), issue the following commands to assign two LUNs (for example, ID=3 and 4) to a designated target (ID=15).

To assign these LUNs to an existing target, issue the isscli assigntoiscsitarget command as shown:

[root@lab-ib1-cn6 ~]# iscsiadm -m node -o delete -T iqn.2004-02.com.vmem-concerto.san-array3003-mgb.lab-ib1-cn6-0 -p 192.168.10.106[root@lab-ib1-cn6 ~]# iscsiadm -m node -o delete -T iqn.2004-02.com.vmem-concerto.san-array3003-mgb.lab-ib1-cn6-0 -p 192.168.20.106

[root@lab-ib1-cn6 ~]# iscsiadm -m nodeiscsiadm: No records found

[root@lab-ib1-cn6 ~]# iscsiadm -m discovery -t st -p 192.168.10.106192.168.10.106:3260,0 iqn.2004-02.com.vmem-concerto.san-array3003-mgb.lab-ib1-cn6-15192.168.20.106:3260,0 iqn.2004-02.com.vmem-concerto.san-array3003-mgb.lab-ib1-cn6-15[root@lab-ib1-cn6 ~]# iscsiadm -m node -lLogging in to [iface: default, target: iqn.2004-02.com.vmem-concerto.san-array3003-mgb.lab-ib1-cn6-15, portal: 192.168.20.106,3260] (multiple)

Logging in to [iface: default, target: iqn.2004-02.com.vmem-concerto.san-array3003-mgb.lab-ib1-cn6-15, portal: 192.168.10.106,3260] (multiple)

Login to [iface: default, target: iqn.2004-02.com.vmem-concerto.san-array3003-mgb.lab-ib1-cn6-15, portal: 192.168.20.106,3260] successful.

Login to [iface: default, target: iqn.2004-02.com.vmem-concerto.san-array3003-mgb.lab-ib1-cn6-15, portal: 192.168.10.106,3260] successful.

[root@san-array3003-mgb san-array3003-mgb]# isscli assigntoiscsitarget -v 3 -r 15Command: assigntoiscsitarget executed successfully.[root@san-array3003-mgb lab-fil3003-mgb]# isscli assigntoiscsitarget -v 4 -r 15Command: assigntoiscsitarget executed successfully



Configuring FC Ports in the FC Switches

This section addresses the use of Fibre Channel ports in a northbound configuration, in which you need to create a 1-to-1 zone between every FC host initiator and 7700 FSP Controller target to which you plan to connect. NPIV (N_Port ID Virtualization) must be enabled and functional on all Fibre Channel switch ports that are directly attached to the 7000 Series FSP. Use the “portcfgshow” and “switchshow” commands to verify.

Note: NPIV (N_Port ID Virtualization) must be enabled and functional on all Fibre Channel switch ports that are directly attached to a 7000 Series FSP. To verify, use the portcfgshow and switchshow commands CLI commands.

Note: To prevent HA failover issues, you must configure the 7700 Flash Storage Platform so that the four southbound Fibre Channel ports are set to Initiator mode and the four northbound Fibre Channel ports are set to Dual mode.

Note: Each interface in an HA pair must be assigned a unique IP address for failover to work correctly (and these IP addresses are not in use for connectivity).

Configuring the 7700 FSP Controller Target and Initiator Ports

For Fibre Channel failover, select the initiator on the secondary 7700 FSP Controller that will function as a standby for every target port on the primary 7700 FSP Controller (as shown in the examples in the following table).

Controller A/B HBA Slot and Ports

Client Target WWPN (Primary)

Client Initiator WWPN (Secondary)

7700 FSP Controller AHBA Slot 2: Ports 107-106

Port 107 connects to Port 5 on client FC-A switch

Port 106 connects to Port 5 on client FC-B switch

7700 FSP Controller AHBA Slot7: Ports 102-103



7700 FSP Controller BHBA Slot 2: Ports 107-106



7700 FSP Controller BHBA Slot 7: Ports 102-103


Port 103 connects to Port 6 client FC-B switch

Table 5.1 Fibre Channel Failover Between 7700 FSP Controllers


Configuring iSCSI

For iSCSI failover, select the initiator on the secondary 7700 FSP Controller that will function as a standby for every target port on the primary 7700 FSP Controller (as shown in Table 5.2).

Controller A/B HBA Slot and Ports

Client Target WWPN (Primary)

Client Initiator WWPN (Secondary)

7700 FSP Controller AHBA Slot 2: Ports isc2-isc3

Port isc2 connects to Port 4 on client FC-A switch

Port isc3 connects to Port 4 on client FC-B switch

7700 FSP Controller AHBA Slot 7: Ports isc1-isc0



7700 FSP Controller BHBA Slot 2: Ports isc2-isc3



7700 FSP Controller BHBA Slot 7: Ports isc1-isc0



Table 5.2 iSCSI Failover Between 7700 FSP Controllers


APPENDIX A System Reference

This appendix contains reference information for the 7700 FSP storage cluster and devices that include the following topics:

• CLI-based procedures for manually:

— Configuring the 7000 Series FSP Memory Gateways (MG)

— Configuring and verifying storage pools

— Enabling Configuration Repositories (CR)

— Rescanning MG devices

— Setting up HA and failover on a new 7000 Series FSP shelf

Note: Manual configuration is not required if you configured the Memory Gateways using either the Simple SetUp configuration tool or the Configuration Wizard method, which includes using the initial_config.exp script file.

• Troubleshooting procedures and tips for resolving issues with:

— Configuring or accessing Memory Gateways (for example, determining the IP addresses of internal Memory Gateways)

— Understanding the status and error messages that are returned if you encounter an error when logging in to the Memory Gateways

The following topics are included for your reference:

• Configuring the 7000 Series FSP on page 94

• Troubleshooting Memory Gateways on page 112

530-0267-00 Rev 02 7700 Series Flash Storage Platform Installation Guide 7.6.3.x 93

Appendix A - System Reference

Configuring the 7000 Series FSP

Use the following topics to manually configure Memory Gateways and other important settings on a new 7000 Series Flash Storage Platform:

• Configuring the Memory Gateways on page 94

• Configuring Storage on page 98

• Enabling the Configuration Repositories on page 104

• Verifying Storage Pools on page 105

• Rescanning all Memory Gateway Devices on page 106

• Setting up High Availability (HA) and Failover on page 108

Configuring the Memory Gateways

Complete the steps in this section to configure the Memory Gateways.

Powering on the Memory Gateways

Both Memory Gateways need to be manually powered on to continue with the configuration process.

1. Log in to the Master ACM.

2. Issue the following commands from the Master ACM to reboot both Memory Gateways:

Configuring the Network on the Memory Gateways

IMPORTANT: After the Memory Gateways are powered on, issue the following commands to eliminate IP conflicts between the Memory Gateways on eth1. The eth1 IP address on Memory Gateway A and on Memory Gateway B are set to the same IP value by default.

1. Start a terminal session (using PuTTY or a similar SSH program) to connect to Memory Gateway A using its hostname or IP address, which was set while completing the configuration wizard.

2. Log in to Memory Gateway A:

• User name: root

• Password: <password>

(config) # array modules id mg-a enable(config) # array modules id mg-b enable

[root@violin-MG-A]# networkconfig.sh initialize [root@violin-MG-A]# networkconfig.sh setnic eth1 no 1500 1 -1 1.0.0.4 255.255.255.0 [root@violin-MG-A ~]# networkconfig.sh finalize [root@violin-MG-A ~]# networkconfig.sh restart 1 1 1

94 7700 Series Flash Storage Platform Installation Guide 7.6.3.x 530-0267-00 Rev 02


Configuring the Replication Ports

Issue the following commands to configure the ports used for replication. For example:

This command only needs to be run on Memory Gateway A.

Configuring the Mail Server for Log Upload

Issue the following command on both Memory Gateways (or 7700 FSP Controllers) to set the e-mail size limit and to configure the SMTP (mail server). This is required so that log upload will send callhome e-mail alerts of the appropriate size:

Enabling Callhome and E-mail Alert Setting for Memory Gateways and 7700 FSP Controllers

Enabling Callhome and E-mail Alert Settings

The configuration jump-start process completed previously included setting up callhome and e-mail alert functions for the ACMs. Complete the steps in this section to set up the callhome and e-mail alert functions for either the Memory Gateways or for the 7700 FSP Controllers.

The only difference between command usage is that you log in to a 7700 FSP Controller and specify its host name or IP address (controller_hostname_or_IP_address) instead of logging in to a Memory Gateway and specifying a host name or IP address (mg_hostname_or_IP_address).

Issue the "isscli enablecallhome" command on both Memory Gateways (or 7700 FSP Controllers) to enable callhome and e-mail alerts, and the following example illustrates this command for a Memory Gateway. For example:

Where:

-ss SMTP server hostname or IP address

-mf E-mail From address

-mt E-mail To address

-ms E-mail subject (such as, "Callhome Event")

-ai Alert interval, specified as DD:HH:MM (alerts will only be sent at specified interval)

-al Alert level options: Information, Warning, Error, Critical, or None (the default)

[root@hostname-mga~]# networkconfig.sh initialize [root@hostname-mga~]# networkconfig.sh setnic rep0 no 1500 1 -1 <replication IP> <replication netmask> [root@hostname-mga~]# networkconfig.sh finalize [root@hostname-mga~]# networkconfig.sh restart 1 1 1

[root@hostname-MG-A ~]# postconf -e message_size_limit=31457280

[root@hostname-MG-A ~]# isscli enablecallhome -ss customer_mail_relay_hostname_or_IP -mf customer_email_address -mt [email protected] -ms subject -ai 00:00:15 -al Information

Command: enablecallhome executed successfully.



-spt SMTP relay server port number (if not specified, port 25 is the default)

-su SMTP user name

-spd SMTP password (if the SMTP relay server needs authentication)

Note: In the example above, the -al setting indicates that all events with level Information and above will be included in the callhome alert e-mail.

The following two subsection provides the complete example syntax.

Note: You can use spaces between the option values if you enclose them within quotation marks (for example, "smtp mail server").

Enable callhome option:

Enable E-mail Alerts option:

To set up e-mail alerts, specify the configuration of the SMTP server, as well as alert e-mail configurations.

isscli enablecallhome --smtp-server=<smtp-server> [--smtp-port=<smtp-port>] [-smtp-username=<smtp-username>][--smtp-password=<smtp-password>] --email-from=<email-from> --email-to=<email-to> --email-

subject=<email-subject> --alert-interval=<alert interval>[ --alert-level=<alert-level>] [--rpc-timeout=<rpc-timeout>]isscli enablecallhome -ss <smtp-server> [-spt <smtp-port>][-su <smtp-username>][-spd <smtp-password>] -mf <email-from> -mt <email-to> -ms <email-subject> -ai <alert-interval> [-al <alert-level>] [-X <rpc-timeout>]

-ss (--smtp-server) specifies the name of SMTP server.-spt (--smtp-port) is an option to specify SMTP port. It defaults to '25' if not specified.-su (--smtp-username) and -spd (--smtp-password) are options to specify a SMTP username and its password.



To describe the alert e-mail configuration, specify:

Run the following to verify that callhome is set up properly:

For specific details about manually configuring the Memory Gateways (MG-A and MG-B) in a 7000 Series FSP shelf, see Configuring the Memory Gateways on page 94, or see the setup and configuration methods in the latest version Violin 7000 Series Flash Storage Platform Installation Guide. If you encounter any issues with configuring or accessing a Memory Gateway, see Troubleshooting Memory Gateways on page 112 for details.

Completing the ACM Configuration

Log in to the Master ACM and then issue the following commands:

Where:

“array serial-logging all-mgs” enables serial logging on the Memory Gateways. This feature is disabled by default.

-mf (--email-from), -mt (--email-to) and -ms (--email-subject), which represent 'from', 'to' and 'subject' fields of the alert email respectively.-ai (--alert-interval) is an required parameter which specifies the interval for alert email to be received. It has following format: DD:HH:MM, meaning the interval unit of Day:Hour:Minute.-al (--alert-level) is an option to filter server events. Through this option, you can select events to be received based on event severity level. The legal values to the options are:None: no alert email will be received;Critical: only Critical events will be received;Error: only events with severity Error and above will be received;Warning: only events with severity Warning and above will be received;Information: events with level Information and above will be received.

# /usr/local/concerto/bin/test_mail <customer-mail-relay_hostname_or_IP> <customer_email_address> [email protected]

(config) # array serial-logging all-mgs(config) # write memory



Configuring Storage

Follow these steps to configure the storage on the 7000 Series Flash Storage Platform.

Note: Before you set up or allocate space for a storage pool, it is recommended that you consider a strategy for planning the most efficient use of your storage pools. For details and best practices, see the latest version Violin 7700 Flash Storage Platform Best Practices Guide.

1. Start a terminal session (using PuTTY or a similar SSH program) to connect to Memory Gateway A using its hostname or IP address.


• User name: root


Note: Another option is to connect directly to the Memory Gateway using its IP address rather than connecting from the ACM.

3. Issue the following command to show the current total allocated and total available space on the 7000 Series FSP. The total space shown will be different after creating the storage pools (done later in this process).

4. Issue the “media_init.sh” command to begin initialization and to set up the partitions on the 7000 Series FSP:

5. Before initializing the partitions, you are prompted to respond with “y” (yes) to continue, which will shut down (stop) the Concerto modules. Enter “y” to continue.

Note: You only need to run the “media_init” command from one of the Memory Gateways.

[root@hostname-MG-A ~]# isscli getpdevinfo

IPStor Server: hostname-MG-A

Total Allocated Space: 0MB

Total Available Space: 0MB

Command: getpdevinfo executed successfully.

[root@hostname-MG-A ~]# media_init.sh -fStopping Concerto services to initiate partitioning .......All virtual devices are going to be detached.We recommend stopping all Concerto client services prior to shutdown.Otherwise, data loss may occur.Are you sure you want to continue? (y/n) [n]: y


Configuring Storage

This begins the process of dividing the storage into multiple data partitions, each of them approximately 1TB in size.

For example:

This partitioning process continues until all of the physical storage has been allocated into separate physical partitions. Once the partitioning process completes, all partitions are shown.

For example:

6. Regardless of the storage size of the 7000 Series FSP, the last two devices are the configuration devices (numbers 42 and 43 in the example above).

Force partitioning /dev/vtmsa .....

Total = 44375GB, Config Repository Size = 10260MB (per mg), Data Size = 22177GB (per mg)

ndisks = 40 pds = 2147483648 dataSize = 86629070848 left = 729724928Data partition : 0GB -> 1099GB/sbin/parted -s /dev/vtmsa mkpart DATA_0 2048s 2147485695s -a optData partition DATA_0 successfully created

Data partition : 1099GB -> 2199GB/sbin/parted -s /dev/vtmsa mkpart DATA_0 2048s 2147485695s -a optData partition DATA_1 successfully created

Data partition : 2199GB -> 3298GB/sbin/parted -s /dev/vtmsa mkpart DATA_0 2048s 2147485695s -a optData partition DATA_2 successfully created...

media init completed successfully

Model: Unknown (unknown)Disk /dev/vtmsa: 44.4TBSector size (logical/physical): 512B/512BPartition Table: gpt

Number Start End Size File system Name Flags

1 1049KB 1100GB 1100GB DATA_0

2 1100GB 2199GB 1100GB DATA_1

3 2199GB 3299GB 1100GB DATA_2

4 3299GB 4398GB 1100GB DATA_3

...

42 44.4TB 44.4TB 10.8GB CFG_A

43 44.4TB 44.4TB 10.8GB CFG_B

clnttcp_create: RPC: Success



Note: A 7000 Series FSP with 32 VIMM will have a different number of partitions.

7. Issue the following commands to read the new partitions created by the “media_init” command into the configuration file:

8. Log in to Memory Gateway B and then issue the same commands:

9. Start a terminal session to the Master ACM, and then type the following commands to enter configuration mode:

10.Enter the following commands to power down both Memory Gateways:

11.Once both Memory Gateways are powered down, restart them one at a time, as follows:

[root@hostname-MG-A ~]# concerto stop all[root@hostname-MG-A ~]# concerto setupConcerto Block Device Module [ OK ]Violin Systems Concerto Server v7.6.3.1 - (Build 9271) SetupWARNING: Configuration file already exists: /usr/local/concerto/etc/[hostname-mg-x]/ipstor.confOverwrite? (y/n) Y

[root@hostname-MG-B ~]# concerto stop allViolin Concerto Server version 7.6.3.1 (Build 9271)Copyright (c) 2017-2018 Violin Systems LLC. All Rights Reserved.

All virtual devices are going to be detached.We recommend stopping all Concerto client services prior to shutdown.Otherwise, data loss may occur.Are you sure you want to continue? (y/n) [n]: yContinue with detaching all virtual devices[root@hostname-MG-B ~]# concerto setupConcerto Block Device Module [ OK ]Violin Systems Concerto Server v7.6.3.1 (Build 9271) SetupWARNING: Configuration file already exists: /usr/local/concerto/etc/[hostname-mg-x]/ipstor.confOverwrite? (y/n) Y

violin-acma [violin: master] > enableviolin-acma [violin: master] # configure terminal

(config) # no array module type mg enableWARNING: Powering down array module(s) may cause data disruption. Are you sure? [no] yes

(config) # array module id mg-a enable.Power-on completed successfully..(config) # array module id mg-b enable.Power-on completed successfully.


Configuring Storage

12.Type the following command to verify that both Memory Gateways are up and running and that the IP addresses are assigned:

Allocating the Storage Space

Follow the steps in this section to allocate the storage to both Memory Gateways. You will be creating two storage pools: one for Memory Gateway A and one for Memory Gateway B.

Note: Only one storage pool is allowed to be created on a Memory Gateway.

1. Using its IP address, connect directly to Memory Gateway A.


• User name: root


3. Once logged in, type the “concerto status” command to verify that the Memory Gateway is up and running and that all modules show a status of “[RUNNING]”:

4. Type the following command to display all of the storage devices created on the 7000 Series FSP:

(config) # show array module type mg detail

[root@hostname-MG-A ~]# concerto status

Violin Concerto Server version 7.6.3.1 (Build 9271)Copyright (c) 2017-2018 Violin Systems LLC. All Rights Reserved.

Status of Concerto FC Initiator Module [RUNNING]...

[root@hostname-MG-A ~]# isscli getpdevinfo -F



Where:

Device Name is the name of the device

ACSL is the SCSI address of the physical device

Total Sectors is the size of the device

Category is the current category of the device (unassigned, virtual or service-enabled). All of the devices are "Unassigned" at this point because they are not prepared or assigned to any storage pool, which you will do later.

Note: Not all devices are shown in the example above.

Notice the two shaded devices in the example above are smaller in size than the other devices. These smaller devices will not be configured like the other devices. These are the configuration devices, which you will allocate differently from the other storage devices.

Using the ACSL value, one device will be assigned to Memory Gateway A (98:0:4:2) and one to Memory Gateway B (98:0:5:2). They will be configured later to store gateway configuration.

Note that the storage assigned to Memory Gateway A will be available for use as dedup LUNs. If you need more dedup capability, then assign more storage to Memory Gateway A. If you are not using dedup, you may want to assign a balance of storage between the two Memory Gateways.

You do not need to assign all the storage at this time. As your requirements for storage evolve, assign the space that is not currently prepared to either Memory Gateway depending on where it is needed.

Device Name ACSL Total Sectors Category

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

BKSC:OTHDISK-MFCN01.000 98:0:0:0 2147483648 Unassigned Device





...

BKSC:OTHDISK-MFCN2A.002 98:0:4:2 21012480 Unassigned Device

BKSC:OTHDISK-MFCN0E.000 98:0:5:0 2147483648 Unassigned Device

BKSC:OTHDISK-MFCN2B.002 98:0:5:2 21012480 Unassigned Device

...


Configuring Storage

5. Looking at the ACSL values, identify which values you want to assign to Memory Gateway A and which to assign to Memory Gateway B (excluding the smaller configuration devices for this step).

6. Issue the “preparedisk” command to allocate the ACSL values to Memory Gateway A. For example:

Where:

-I is the ACSL, followed by the ACSL value that you chose to allocate

-C precedes the category, which should be changed to virtual so that it is used as virtual storage

7. Continue issuing the preparedisk command until all ACSL values for Memory Gateway A are implemented (excluding the configuration devices, which are set up as virtual devices later).

Make sure to use the correct ACSL value as you progress with allocating the devices.

Note: Once you have completed allocating the devices on Memory Gateway A, complete the same process on Memory Gateway B.

8. Log in to Memory Gateway B:

• User name: root


9. Repeat steps 3-6 to allocate the devices on Memory Gateway B. Make sure that you use the available ACSL values for Memory Gateway B (those not already assigned to Memory Gateway A and not the two smaller devices that will be used for gateway configuration).

10.Issue the “getpdevinfo” command once again to review the status of the physical devices you just allocated:

The Category value for each ACSL allocated should now show “Reserved by Virtual Device.”

Creating the Storage Pools

Complete the following step on both Memory Gateways to create a storage pool on each gateway. Memory Gateway A (MG-A) is shown in this example. Assignment will be based on the ACSL values provided in the storage creation statement.

1. Log in to Memory Gateway A.

2. Issue the “createstoragepool” command to create a storage pool. Remember to leave one device for the configuration repository:

[root@hostname-MG-A ~]# isscli preparedisk -I 98:0:0:0,98:0:0:1,98:0:0:2,98:0:1:0,98:0:1:1,98:0:1:2,98:0:2:0,98:0:2:1,98:0:2:2,98:0:3:0 -C virtual

Command: preparedisk executed successfully.




Where:

-SP precedes the storage pool name

-D precedes the list of devices using their ACSL values. Separate each ACSL value with a comma.

-sa precedes the type of storage. In this case, primary.

In the example above, the storage pool contains seven devices. You are able to create whatever size fits your specific needs.

3. Repeat the above command for Memory Gateway B, applying different storage devices and a different storage pool name to Memory Gateway B.

Enabling the Configuration Repositories

Complete the following steps on both Memory Gateways to enable the configuration repositories as virtual devices. Memory Gateway A (MG-A) is shown in this example.

1. Use the following command to find the two smallest unassigned physical devices:

2. Use the following command to prepare one of these devices for Memory Gateway A:

Where: 98:0:4:2 is the ACSL value for one of the two smaller configuration devices.

3. Repeat step 2, using the second device for Memory Gateway B and “mgb-server-name” for the server name. Use the other device reserved for the configuration repositories.

4. Log in to Memory Gateway A and identify the ACSL that is used for Memory Gateway A’s configuration repository. Issue the following command to display the virtual devices that are configured:

[root@hostname-MG-A ~]# isscli createstoragepool -SP StoragePool-1 -D <98:0:7:2,98:0:8:0,98:0:8:1,98:0:8:2,98:0:9:0,98:0:9:1,98:0:9:2> -sa primary

Command: create storagepool executed successfully.


[root@hostname-MG-A ~]# isscli preparedisk -I 98:0:4:2 -C virtual

Command: preparedisk executed successfully.

[root@hostname-MG-A ~]# isscli getpdevinfo -F --category=virtual


Verifying Storage Pools

5. Enable the Configuration Repository for Memory Gateway A as follows:

Where:

--scsiaddress= precedes the ACSL value for the configuration device.

6. Log in to Memory Gateway B.

7. Repeat steps 1 and 2 above, using the other small device (98:0:5:2).

Verifying Storage Pools

It is important to verify that each Memory Gateway has a unique name, the correct set of devices identified by their ACSLs and the correct owner before enabling high availability.

1. Issue the following command on both Memory Gateways to inspect the storage pools (as shown):

[root@hostname-MG-A ~]# isscli enableconfigurationrepository --scsiaddress=98:0:4:2New Virtual Device ID: 2Device Name ACSL First Sector Last Sector Size(MB) Header

----------------------------------------------------------------------BKSC:OTHDISK-MFCN2A. 98:0:4:2 14336 20479 3 YesBKSC:OTHDISK-MFCN2A. 98:0:4:2 20480 20991999 10240 No

Command: enableconfigurationrepository executed successfully.

[root@hostname-MG-A ~]# isscli getstoragepools -o detail

Storage Pools: 1

Name: StoragePool-2ID: 1Category: Virtual DeviceApplication Tag:Resource Types: AllStorageAttribute: Primary StorageRemote Pool ID: 0

ACL User=

ACL Groups: 0

Devices: 11Total Size: 10653577MB (21818525696 Sectors)Total Allocated Space: 10651593MB (21814462464 Sectors)Total Available Space: 1984MB (4063232 Sectors)



2. Verify that each storage pool has a unique name, a correct ACSL, and an owner for each device (shown in red text in the example above).

Note: Due to brevity, only two devices are shown in the previous example.

Rescanning all Memory Gateway Devices

Complete the steps in this section to ensure that both Memory Gateways are able to see the state of all devices assigned to the other Memory Gateway, and it is important that no devices should be unassigned.

IMPORTANT: Complete the following steps on both Memory Gateways.

1. Issue the following command to inspect the devices and view each device’s Category:

Device Name: BKSC:OTHDISK-MFCN06.001ACSL: 98:0:3:1 redTotal Sectors: 2147469312Sector Size: 512Size: 1048568MBCategory: Virtual DeviceOwner: hostname-mg-aGuid: 5c90e836-7b24-7ee7-2afe-000054c9597bState: Online

Device Name: BKSC:OTHDISK-MFCN0D.000ACSL: 98:0:4:0Total Sectors: 2147469312Sector Size: 512Size: 1048568MBCategory: Virtual DeviceOwner: hostname-mg-aGuid: 67706a81-1d59-3eea-31e6-000054c95985State: Online...Command: getstoragepools executed successfully.[root@hostname-MG-A ~]#


Rescanning all Memory Gateway Devices

Notice that there are two devices that show a Category of “Unassigned Device” in the example above. All devices must be in one of the following categories: Reserved by Virtual Device, Used by Virtual Device, or Reserved by Device.

2. Issue the following to rescan the SCSI bus (update each device’s category):

The “rescandevices” command may take up to 30 seconds to complete.

3. Issue the “getpdevinfo” command once again.

4. Reinspect the device categories. Ensure that the devices that were “Unassigned Device” are now either “Reserved by Virtual Device” or “Used by Virtual Device.”

[root@hostname-MG-A ~]# isscli getpdevinfo –F...Device Name ACSL Total Sectors Category

-------------------------------------------------------------------------------BKSC:OTHDISK-MFCN01.000 98:0:0:0 2147469312 Reserved by Virtual DeviceBKSC:OTHDISK-MFCN18.001 98:0:0:1 2147469312 Reserved by Virtual DeviceBKSC:OTHDISK-MFCN27.002 98:0:0:2 2147469312 Reserved by Virtual DeviceBKSC:OTHDISK-MFCN0A.000 98:0:1:0 2147469312 Reserved by Virtual DeviceBKSC:OTHDISK-MFCN19.001 98:0:1:1 2147469312 Reserved by Virtual DeviceBKSC:OTHDISK-MFCN04.002 98:0:1:2 2147469312 Reserved by Virtual DeviceBKSC:OTHDISK-MFCN0B.000 98:0:2:0 2147469312 Reserved by Virtual DeviceBKSC:OTHDISK-MFCN1A.001 98:0:2:1 2147469312 Reserved by Virtual DeviceBKSC:OTHDISK-MFCN28.002 98:0:2:2 2147469312 Reserved by Virtual DeviceBKSC:OTHDISK-MFCN0C.000 98:0:3:0 2147469312 Reserved by Virtual DeviceBKSC:OTHDISK-MFCN1B.001 98:0:3:1 2147469312 Reserved by Virtual DeviceBKSC:OTHDISK-MFCN29.002 98:0:3:2 729708544 Reserved by Virtual DeviceBKSC:OTHDISK-MFCN0D.000 98:0:4:0 2147469312 Reserved by Virtual DeviceBKSC:OTHDISK-MFCN1C.001 98:0:4:1 2147469312 Reserved by Virtual DeviceBKSC:OTHDISK-MFCN2A.002 98:0:4:2 21012480 Used by Virtual DeviceBKSC:OTHDISK-MFCN0E.000 98:0:5:0 2147469312 Reserved by Virtual DeviceBKSC:OTHDISK-MFCN1D.001 98:0:5:1 2147469312 Reserved by Virtual DeviceBKSC:OTHDISK-MFCN2B.002 98:0:5:2 21012480 Unassigned DeviceBKSC:OTHDISK-MFCN0F.000 98:0:6:0 2147469312 Reserved by Virtual DeviceBKSC:OTHDISK-MFCN03.001 98:0:6:1 2147469312 Reserved by Virtual DeviceBKSC:OTHDISK-MFCN05.002 98:0:6:2 2147469312 Reserved by Virtual DeviceBKSC:OTHDISK-MFCN10.000 98:0:7:0 2147469312 Reserved by Virtual DeviceBKSC:OTHDISK-MFCN1E.001 98:0:7:1 2147469312 Reserved by Virtual DeviceBKSC:OTHDISK-MFCN06.002 98:0:7:2 2147483648 Unassigned DeviceBKSC:OTHDISK-MFCN11.000 98:0:8:0 2147483648 Unassigned Device...Command: getpdevinfo executed successfully.[root@hostname-MG-A ~]#

[root@hostname-MG-A ~]# isscli rescandevices Command: rescandevices executed successfully.[root@hostname-MG-A ~]#



Setting up High Availability (HA) and Failover

In the 7000 Series Flash Storage Platform, Memory Gateway A (MG-A) is the primary server for its devices, while Memory Gateway B (MG-B) serves as the secondary server. When both MGs are available, devices created on A accept I/O through Memory Gateway A only, and vice versa.

If Memory Gateway A fails, Memory Gateway B takes over MG-A’s devices and accepts I/O for those devices. Once MG-A comes back up, failback must be manually for MG-A to start accepting I/O. Complete the steps in the following sections to set up HA.

Configuring High Availability


2. Type the following command to open the HA Preconfiguration Editor:

Completing the HA Configuration File

Edit the file as shown in the following output steps. You will be configuring HA between both Memory Gateways, starting with Memory Gateway A.

• Bold text indicates that a response must be submitted.

• The Courier italic format identifies information for which you must supply a value.

• Press Enter to choose a default value (when one is available).

[root@hostname-MG-A ~]# cfghaprecfg.sh

A preconfiguration file already exists, with the following settings:[HA] = truemutual = truepowercontrol = ipmiisStretchCluster = false[primary]hostname = array-1234sci_ip = 192.168.0.0interface = eth0heartbeat_ip =virtual_ip = 10.5.5.206impi_ip = 10.5.5.206quorum_drive = 98:0:4:2quorum_mirror_drive =[secondary]hostname = array-2345sci_ip = 192.168.0.1interface = eth0heartbeat_ip =virtual_ip = 10.5.5.199impi_ip = 10.5.5.198quorum_drive = 98:0:5:2quorum_mirror_drive =Here are settings you have entered:



1. Do you want to modify these settings? (y/n:) y

2. Enable configuring HA using this preconfiguration file (true/false) [true]:

3. Configure for Mutual Failover (true/false) [true]:

4. Enter the primary server hostname [violin3550]: hostname-mg-a

This is the hostname for Memory Gateway A.

5. Set the primary server's Storage Cluster Interlink IP address (nnn.nnn.nnn.nnn) [192.168.200.50]: 192.168.0.0

6. Set the primary server's power control IP address (nnn.nnn.nnn.nnn) [10.5.5.206]: 169.254.1.101

7. Enter the interface (eth0/eth1/rep0/sci0/eth0.10) [eth0]:

8. Enter the primary server's Virtual IP address (nnn.nnn.nnn.nnn) [10.5.5.207]: <mg-a assigned virtual IP>

Enter the physical address of Memory Gateway A. This IP address is assigned to eth0:0, and this is the value required by Symphony.

9. Enter the primary server's Heartbeat IP address (nnn.nnn.nnn.nnn) []: mg-a assigned monitor IP>

This is a secondary IP address on the same subnet as the primary server’s virtual IP address. This IP address is assigned to eth0, and to verify this, use the ipconfig command.

10.Enter another Virtual and Heartbeat IP address pair? (y/n): n

11.Enter the primary server's quorum drive selection (any / A:C:S:L) [any]: <mg-a configuration device> (for example, 98:0:4:2).

This is the ACSL value used for the configuration device for Memory Gateway A.

12.Enter the primary server's quorum mirror drive selection (any / A:C:S:L / none) []: none

13.Enter the secondary server hostname [violin3554]: hostname-mg-b

This is the hostname for Memory Gateway B.

14.Set the secondary server's Storage Cluster Interlink IP address (nnn.nnn.nnn.nnn) [192.168.200.54]: 192.168.0.1

15.Set the secondary server's power control IP address (nnn.nnn.nnn.nnn) [10.5.5.198]: 169.254.1.102

16.Enter the interface (eth0/eth1/rep0/sci0/eth0.10) [eth0]:

17.Enter the secondary server's Virtual IP address (nnn.nnn.nnn.nnn) [10.5.5.199]: <mg-b assigned IP>

18.Enter the secondary server's Heartbeat IP address (nnn.nnn.nnn.nnn) []: mg-b assigned monitor IP>

19.Enter another Virtual and Heartbeat IP address pair? (y/n): n

20.Enter the secondary server's quorum drive selection (any / A:C:S:L) [any]: <mg-a configuration device> (for example, 98:0:5:2).

21.Enter the secondary server's quorum mirror drive selection (any / A:C:S:L / none) []: none

22.Ensure that all values entered are correct and then enter “y” to commit these settings.



Once the new settings are committed, any previous settings are saved in /usr/local/concerto/etc/ha_precfg.ini.prev. The new ha_precfg.ini file you created is ready for use in setting up HA using CLI commands.

Enabling High Availability

Complete these steps on Memory Gateway A to enable high availability between Memory Gateway A and Memory Gateway B.


2. Enter the “enableha” command to enable the HA function:

Where:

-s (lowercase) precedes the primary server name (Memory Gateway A)

-S (uppercase) precedes the secondary server name (Memory Gateway B)

-U (uppercase) precedes the secondary server’s (Memory Gateway B) user name

-P (uppercase) precedes the secondary server’s (Memory Gateway B) password

-pcu precedes the power control user name

-pcp precedes the power control password

-ar allows the secondary server to restart for any resolution of configuration conflicts

-X precedes the remote procedure call timeout value (in seconds)

3. Ignore any messages stating, “Can’t open lock file...” and wait for the command to be executed successfully.

Enabling Dedup

At least one 7000 Series FSP shelf is required in your 7700 FSP cluster to support the deduplication and compression (dedup) feature. The 7000 Series FSP must have one storage pool with dedup enabled where dedup LUNs may be created (6000 Series arrays do not support dedup).

During the enabling of dedup, the process only creates dedup vdevs (virtual devices) in storage pools, where dedup is enabled and no LUNs are yet created. The process of allocating space must be planned so that the entire capacity is judiciously used as needs arise.

Once created, both LUN types are visible in the CLI and Symphony (all of the dedup LUNs are compressed by default). You must be logged in to Memory Gateway A to enable dedup, and only enable dedup on one storage pool on MG-A on the 7000 Series FSP shelf.

[root@hostname-MG-A ~]# isscli enableha -s hostname-MG-A -u root -p <password> -S hostname-MG-B -U root - P <password> -pcu admin -pcp admin -ar -X 60

Command: enableha executed successfully.



Note: Before you set up or allocate space for a dedup storage pool, it is recommended that you consider a strategy for planning the most efficient use of your storage pools. For details and best practices, see the latest version Violin 7700 Flash Storage Platform Best Practices Guide. If this is planned in a stretched cluster environment, see the latest version Concerto 7700 FSP Stretch Cluster Implementation and Best Practices Guide.

Note: Dedup LUNs are limited to being created only in Storage Pool A. Use Storage Pool B (or other storage pools you create) for creating thick and thin LUNs.

To set up the storage pool to be allocated for dedup use:

1. While logged in to Memory Gateway A, issue the “getstoragepools” command to list the storage pools that you created:

2. From this list, choose the storage pool to be used for dedup. In the above example, “StoragePool-A” is the only storage pool that exists.

3. Issue the isscli enablededuplication command to enable dedup:

[root@hostname-MG-A ~]# isscli getstoragepools -o detail

Storage Pools: 1

Name: StoragePool-mgaID: 1Category: Virtual DeviceApplication Tag:Resource Types: AllStorageAttribute: NoneRemote Pool ID: 0...



Where:-sp precedes the storage pool ID number shown in the output of the “getstoragepools” command.

Troubleshooting Memory Gateways

This section provides troubleshooting tips, should you have problems configuring or accessing a Memory Gateway. The following topics are covered:

• Determining IP Addresses of Internal Memory Gateways (One Known, One Unknown) on page 113

• Determining IP Addresses of Internal Memory Gateways (Both Unknown) on page 114

• Error Messages When Logging in to Memory Gateways on page 115

[root@hostname-MG-A ~]# isscli enablededuplication -sp 1

Max memory provisioned for RDE: 163840MBTotal storage pool size: 4194276MBAvailable storage pool size: 4194276MB

Using Default Arguments :

Number of Data Disks : 2Data Disk Size : 16384GBIndex Disk Size: 560GBFolder Disk Size : 1GBDedupe Index Disk Type: thickDedupe Folder Disk Type : thickAllocation Mode : 0 (classic)Classic Rows : 1Classic Cols : 2

Initial allocation size for Data Disks: 155390MB

Starting enable deduplication on hostname-MG-A, could take several minutes...

Command: enablededuplication executed successfully.



Determining IP Addresses of Internal Memory Gateways (One Known, One Unknown)

If the IP address for one internal Memory Gateway is known (and verified via a direct ping) and the other Gateway’s address is unknown, use the following procedure to determine the unknown IP address.

1. Verify each Memory Gateway is powered and drawing current by examining the output of the show array modules type mg detail command.

2. Perform a broadcast ping to 169.254.255.255 from the ACM CLI, similar to this example:

3. Examine the output of the above command and determine the IP address that is not 169.254.1.10 (acm-a), 169.254.1.11 (acm-b) or the known IP address of the other Memory Gateway. The remaining IP address is the Memory Gateway’s unknown IP address.

4. Set up the host definition for the appropriate Memory Gateway (“mg-a” or “mg-b”) and the newly discovered IP address using the following commands:

Note: Pressing the Tab key after the first command auto completes the command with any existing IP address assigned to that host. If none is present, the first command is unnecessary.

5. Verify the host definition by pinging the Memory Gateway directly using its hostname:

6. If the Memory Gateway responds properly, save the host settings using the write mem command.

violin-acma [violin: master] # ping -b -w1 169.254.255.255WARNING: pinging broadcast addressPING 169.254.255.255 (169.254.255.255) 56(84) bytes of data.64 bytes from 169.254.1.10: icmp_seq=1 ttl=64 time=0.061 ms64 bytes from 169.254.1.11: icmp_seq=1 ttl=64 time=0.102 ms (DUP!)64 bytes from 169.254.42.198: icmp_seq=1 ttl=64 time=0.115 ms (DUP!)64 bytes from 169.254.87.114: icmp_seq=1 ttl=64 time=0.115 ms (DUP!)64 bytes from 169.254.1.10: icmp_seq=2 ttl=64 time=0.036 ms

64 bytes from 169.254.1.11: icmp_seq=2 ttl=64 time=0.058 ms (DUP!)64 bytes from 169.254.42.198: icmp_seq=2 ttl=64 time=0.099 ms (DUP!)64 bytes from 169.254.87.114: icmp_seq=1 ttl=64 time=0.115 ms (DUP!)

no ip host <mg-a|mg-b> <tab>ip host <mg-a|mg-b> <ip address>

ping mg-a or ping mg-b



Determining IP Addresses of Internal Memory Gateways (Both Unknown)

If both Memory Gateway IP addresses are unknown, it is necessary to power down one Memory Gateway to properly identify which Memory Gateway is which. The following procedure powers down mg-b.

1. Make sure mg-a is powered on and mg-b is powered off by running the following commands on the ACM master node:

2. Issue the following command and then verify that mg-a is drawing current (>0) and mg-b is not:

3. Perform a broadcast ping to 169.254.255.255 from the ACM CLI, for example:

4. Examine the output of the above command and determine the IP address that is neither 169.254.1.10 (acm-a) nor 169.254.1.11. The remaining IP address is the address for mg-a.

5. Set up the host definition for mg-a using the following commands:

Note: Pressing the Tab key after the first command will auto-complete the command with any existing IP address assigned to that host. If none is present, the first command is unnecessary.

6. Verify the host definition by pinging mg-a directly using its hostname:

7. Power on mg-b as follows:

8. Wait 5 minutes for mg-b to boot up completely. Once booted, repeat steps 2-5 above to determine the IP address of mg-b. In this case, when looking at the output of the ping command, mg-b’s address will be the address that is not 169.254.1.10, 169.254.1.11 or the previously-discovered mg-a address.

9. Save the host definitions by running the write mem command.

array module id mg-a enableno array module id mg-b enable

show array module type mg detail

violin-acma [violin: master] # ping -b -w1 169.254.255.255

WARNING: pinging broadcast address

PING 169.254.255.255 (169.254.255.255) 56(84) bytes of data.

64 bytes from 169.254.1.10: icmp_seq=1 ttl=64 time=0.061 ms

64 bytes from 169.254.1.11: icmp_seq=1 ttl=64 time=0.102 ms (DUP!)


64 bytes from 169.254.1.10: icmp_seq=2 ttl=64 time=0.036 ms



no ip host mg-a <tab>ip host mg-a <ip address>

ping mg-a

array module id mg-b enable



Error Messages When Logging in to Memory Gateways

Complete the steps described in this section if any of the following warning messages display:

• “WARNING: POSSIBLE DNS SPOOFING DETECTED!”

or

• “WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!”

The following steps allow you to log in to the Memory Gateways from either ACM:

1. Log in to the ACM Master.

2. Type the following at the command prompt to access the CLI’s configuration mode:

3. Type the following commands:

violin-acma [violin: master] > enableviolin-acma [violin: master] # configure terminal

(config) # ssh client user admin known-host mg-a remove(config) # ssh client user admin known-host mg-b remove(config) # ssh client user admin known-host 169.254.1.101 remove(config) # ssh client user admin known-host 169.254.1.102 remove


APPENDIX B Overview: 7700 FSP Controller

This appendix provides the following types of 7700 FSP Controller reference information:

• Tables and figures that describe the 7700 FSP Controller chassis front panel and rear panel components, and the status LEDs for the power supply units (PSUs) in the 7700 FSP Controller chassis. For details, see:

— Understanding 7700 FSP Controller Components on page 118

— Table B.1 on page 118, which describes the 7700 FSP Controller front panel components

— Table B.2 on page 119, which describes the 7700 rear panel components

— Table B.3 on page 120, which describes the 7700 FSP Controller status LEDs

• CLI-based procedures that describe how to use iDRAC with the 7700 FSP Controller. For details, see:

— Monitoring 7700 FSP Controllers Using iDRAC on page 120

— Inspecting 7700 FSP Controller Status on page 121

— Setting Up DNS and Domain Names in iDRAC on page 123

— Setting Up Time Zones and NTP in iDRAC on page 123

— Setting Up SNMP E-mail Alerts in iDRAC on page 123


Appendix B - Overview: 7700 FSP Controller

Understanding 7700 FSP Controller Components

This section consists of tables and figures that describe the location of key components of the 7700 FSP Controller chassis.

Note: For additional details, see the OEM documentation for the Dell R720 appliance at http://www.Dell.com.

Item Component Description

1 Power Button Switches the system power on or off.

2 System ID Button

Press this button to cause the LCD panel on the front panel to flash, which helps identify it in a heavily populated equipment rack (the LCD panel keeps flashing until the System ID button is pressed again).

3 VGA Video Connector

Front panel VGA port lets you connect a VGA monitor to the 7700 FSP Controller for use as a local console.

4 LCD Menu Buttons

Controls the cursor on the LCD panel:

— The < button moves the cursor left.

— The √ button selects the highlighted menu item.

— The > button or console client moves the cursor right.

5 LCD Panel Displays system information and error messages.

6 Information Tag Slides out of chassis and provides a place for recording important information (for example, the MAC addresses of the Ethernet ports).

7 USB Ports Front USB 2.0 ports support flash media, mouse, or keyboard.

Table B.1 7700 FSP Controller Front Panel Components

1 2 4 5

7

6

3


http://www.dell.com

Understanding 7700 FSP Controller Components

Note: 7700 FSP Controller rear panel illustration shows HBA slot and port numbers for an FC configuration. Table B.2 describes both FC and iSCSI HBA slot and port numbers.

Item Component Description

1 IPMI/iDRAC Port Intelligent Platform Management Interface (IPMI) and Integrated Dell Remote Access Controller (iDRAC) 10GbE port, which is used for out-of-band management of the device and access as a virtual console.

2 Serial Port Lets you connect a serial device or console monitor to the system.

3 VGA Video Connector

Rear panel VGA port lets you connect a VGA monitor to the 7700 FSP Controller for use as a local console.

4 USB Ports Rear panel USB 2.0 ports support flash media, mouse, or keyboard.

5 Storage Cluster Interlink Ports

Two 10GbE ports, SCI0 and SCI1. These ports are connected to another 7700 FSP Controller to allow for mirroring of snapshot metadata between failover pairs.

6 10/100/1000Ethernet Ports

Two 10/100/1000 Mb Ethernet ports, ETH0 and ETH1. The ETH0 port is used for device management.

7 Power Supplies Two redundant, hot-swappable power supplies (750 W).

8 Replication Ports Two 10GbE ports (rep0 and rep1) for 7700 FSP replication.

9 Storage Interface Ports

(Southboundand Northbound Fibre Channel HBAs and Ports)

7700-Fibre Channel Ports:

— Four 16Gbps southbound; HBA slot 4, ports 4-0 and 4-1 (104 and 105), and HBA slot 5, ports 5-0 and 5-1 (100 and 101)

— Four 16Gbps northbound; HBA slot 2, ports 2-1 and 2-0 (107 and 106), and HBA slot 7, ports 7-0 and 7-1 (102 and 103)

10 Storage Interface Ports

(Southbound and Northbound iSCSI HBAs and Ports)

7700-iSCSI Ports:

— Four 16Gb FC southbound; HBA slot 4, ports 4-0 and 4-1 (102 and 103), and HBA slot 5, ports 5-0 and 5-1 (100 and 101)

— Four 10Gbps iSCSI northbound; HBA slot 2, ports2-0 and 2-1 (isc2 and isc3), and HBA slot 7, ports 7-1 and 7-0 (isc1 and isc0)

Table B.2 7700 FSP Controller Rear Panel Components

1 2 3 4 5 6 7

8 9

10

10



Note: To reference the specific physical locations for both the Fibre Channel and iSCSI HBA slots and port numbers, see Figure 2.1 (Fibre Channel) and Figure 2.2 (iSCSI).

Table B.3 describes the status LEDs for the 7700 FSP Controller power supplies.

Monitoring 7700 FSP Controllers Using iDRAC

The IPMI/iDRAC support in the 7700 FSP Controllers provides system power control that supports a standard Web browser and a Virtual Console with a standard Web browser with Java support. iDRAC supports SNMP, IPMI, remote logging, and SMTP e-mail alerts (for more details, see the latest Dell iDRAC documentation at http://www.Dell.com).

Symphony and the Concerto OS use IPMI monitoring and control for access and power control, and use iDRAC to monitor other important system components such as system disks, fans, and temperature. If your data center already supports Dell iDRAC, add each 7700 FSP Controller’s iDRAC to your management infrastructure.

Note: Do not upgrade iDRAC, the System BIOS, or system firmware used on the 7700 FSP Controllers without first consulting Violin Support.

Log in to the iDRAC Virtual Console on each 7700 FSP Controller to inspect current status and/or modify management or monitoring settings by using the default login credentials set by Violin Systems: admin and violin101 (for a log in example, see Testing iDRAC Interfaces on page 61).

Note: Because Symphony does not directly monitor the 7700 FSP Controllers in the 7700 FSP storage cluster, use iDRAC to monitor the system status for 7700 FSP Controller components. iDRAC supports SNMP, IPMI, remote logging, and SMTP mail alerts. For more details on setting up and using iDRAC, see the following subsections in this appendix.

LED Display Description

unlit Indicates that no AC power going to the power supply.

green Indicates that the power supplies are operating normally.

blinking green Indicates that the power supplies are not the same type.

blinking amber Indicates that a problem has been detected on the power supply.

Table B.3 7700 FSP Controller Power Supply Status LEDs



Inspecting 7700 FSP Controller Status

Use iDRAC to view the current system status for a 7700 FSP Controller by completing the following:


2. Log in to iDRAC using its login credentials (default login credentials are admin and violin101).

3. By default, the System Summary page displays, and it contains six panes of information, with the most important panes that display current status are Server Health, Server Information, and Recent Logged Events. The left navigation pane provides an Overview menu with Server, iDRAC Settings, Hardware, and Storage options.

The Server Health pane displays the current status of key system categories. A normal running state is indicated by green check boxes. Click the link associated with each health category for more details (for example, click Power Supplies to display a page that indicates the health and other information about the individual power supply elements).

The Server Information pane displays important categories such as Power State, System Host Name, Operating System and Version, Service Tag, Firmware and BIOS versions, and IP Address.



The Recent Logged Events pane displays the Severity, Date/Time, and a Description of recently logged events.

4. In the navigation pane, click Overview > Hardware to display individual pages that provide current status on Batteries, Fans, CPU, Memory, Front Panel, Network Devices, Power Supplies, Removable Flash Media, and Fibre Channel Devices.

5. In the navigation pane, click Overview > Storage to display Storage Summary that lists the internal boot media, and under Summary of Disks lists links to Physical Disks, Virtual Disks, Controllers, and Enclosures. Concerto OS boots from the primary RAID-1 Virtual Disk that is comprised of two SATA physical disks.



Setting Up DNS and Domain Names in iDRAC

Most alert functions require proper DNS and domain name settings to correctly resolve names to network IP addresses, and to allow alerts to be correctly formatted for Enterprise hosts. Set up DNS and domain names in iDRAC by completing the following steps:



3. In the navigation pane, click Overview > iDRAC Settings > Network and scroll down to the Common Settings pane.

4. In Static DNS Domain Name, enter a valid DNS domain name.

5. Navigate to the IPv4 Settings pane, and in Static Preferred DNS Server and Static Alternate DNS Server, enter valid IP addresses.

6. At the bottom of the Network page, click Apply to apply all these DNS and domain name settings.

Setting Up Time Zones and NTP in iDRAC

You should inspect and verify that the time zone and NTP information used by IPMI matches that information used by other 7700 FSP storage cluster devices.

Set up time zone and NTP information in iDRAC by completing the following:



3. In the navigation pane, click Overview > iDRAC Settings and in the iDRAC Information page, click Settings.

4. In the Time Zone and NTP page, verify the Time Zone Value and the NTP Server 1-2-3 and Enable Network Time Protocol (NTP) check box values in the Time Zone pane.

5. Click Apply if you make any changes.

Setting Up SNMP E-mail Alerts in iDRAC

iDRAC provides a means to receive SMTP e-mail platform-based alerts about the 7700 FSP Controllers in the 7700 FSP storage cluster. Use iDRAC to set these e-mail alerts up in addition to other existing monitoring methods or if you have no other monitoring methods available. To configure SNMP e-mail alerts in iDRAC, complete the following:



3. In the navigation pane, click Overview > Server > Alerts, and in the Alerts page navigate to the Alerts pane, click Enabled, and click Apply.



4. In the Alerts page, click SNMP and Email Settings, and navigate to the SMTP (E-mail) Server Address Settings pane.

5. In SMTP (Email) Server IP Address or FQDN/DNS Name, enter a valid Fully Qualified Domain Name hostname or IP address of the SMTP (E-mail) Server, and click Apply.

6. Navigate to the Destination Email Addresses pane, and perform the following:

• Enter a recipient e-mail address in Destination Email Address.

• Select the State check box to activate this e-mail address and click Apply.

• Click Send and confirm that the designated recipient received an e-mail alert message.

7. In the Alerts page, click Alert Recurrence, and in the Customize Alert Recurrence pane, set interval values (in days) for repeating alerts in Recurrence for Severity Warning and Critical events, and click Apply.

Note: It is recommended that you enter a 1 (in the Days field) under the Recurrence column for Severity Critical events.

8. In the Alerts page, click Alerts tab, and in the Alerts Filter pane, make sure that all of the Category and Severity check boxes are selected, and click Apply.

9. In the Alerts and Remote System Log Configuration pane, click the Email check box in the column head to select e-mail notifications for all categories of System Health alerts (or select the individual Email check box for those alerts for which you want e-mail notifications).

10.Click the right-arrow page control (adjacent to Apply button) to complete the selection of Email check boxes, and click Apply.


APPENDIX C Configuring Replication

This appendix describes replication, provides reference information, and a procedure for configuring the network interfaces to support replication in a 7700 FSP storage cluster.

Configuring Network Interfaces for Replication

In a 7700 FSP storage cluster, if you are using the replication feature, it is performed over TCP using the two 10Gpbs ports in HBA slot 1 of the rear chassis in the 7700 FSP Controllers.

The replication interface port is named rep0 at HBA slot 1-0 and port rep1 at HBA slot 1-1. Currently, replication configurations only support using rep0.

Replication Overview

Replication is configured on a per-LUN basis and this is unidirectional from the primary LUN to the replica 7700 FSP Controller to an existing storage pool and a new or existing LUN. A 7700 FSP Controller that is primary for one replication LUN may also be a replica for another 7700 FSP Controller’s LUN.


Appendix C - Configuring Replication

Replication is typically between 7700 FSP Controllers. If you have configured all storage that is assigned to 7700 FSP Controller A, and this is configured for replication, 7700 FSP Controller B may be configured as an HA failover partner for 7700 FSP Controller A. In this case, the 7700 FSP Controller B rep0 port must be configured and included in the 7700 FSP storage cluster HA configuration.

An HA configuration will require that the virtual IP and monitor IP addresses for all Concerto-based device rep0 ports be assigned. If two Concerto-based 7700 FSP Controllers are used for primary storage, and are also not configured as part of an HA pair, then replication may be configured between these two Concerto-based 7700 FSP Controllers.

Using Symphony and CLI commands, you can configure primary and replica LUNs from the primary 7700 FSP Controller. Symphony must have access to both 7700 FSP Controller primary management interfaces.

Symphony will use its secure access to each 7700 FSP Controller to collect LUN and storage pool information automatically. Replica enabling commands are directed to the primary 7700 FSP Controller. The primary replication device must have access to the replica device management interface to complete the replication set up.

7700 FSP Controller Preparation

The replication interface rep0 is not configured by the current configuration jump-start or initial_config.exp scripts. Replication interfaces and inter-controller routing must be configured using Concerto-based CLI commands at each 7700 FSP Controller.

Prerequisites, Tools, and Skills

This section lists the recommended experience, prerequisites, tools, and skills that are needed for configuring the replication interfaces in a 7700 FSP storage cluster, which include:

• Familiarity using the Concerto command line interface commands (isscli).

• Experience with basic text editing using vi or nano via CLI commands (for example, being able to perform edit, insert, write, and quit operations).

• Experience using basic shell tool commands to perform operations (for example, using grep, cat, and ifconfig).

• Understanding IP subnets. You can use the IP Subnet Mask Calculator at this Web site for reference purposes:http://www.subnet-calculator.com/

• Experience performing network speed conversions based on measurements from the customer network, such as GBps (gigabytes per second) and Gbps (gigabits per second) found in replication operations (for example, 16Gbps = 1000 Mbps = 125000 KBps = 0.125 GBps = 125 MBps). You can use this Web site for reference purposes: http://www.checkyourmath.com/convert/data_rates/

• Understanding storage conversions (for example, converting storage capacities like MiB/mebibyte and GiB/gibibyte to MB/megabyte and GB/gigabyte).


http://www.checkyourmath.com/convert/data_rates/

http://www.subnet-calculator.com/


Installation Preview

Before configuring for replication, you must first complete the normal 7700 FSP installation using the following best practices:

1. Ensure that you upgrade the 7700 FSP Controllers in the 7700 FSP storage cluster to the latest Concerto OS versions available (the RPM update unless starting at 7.5.0 requires either a USB or network install).

2. Power on the 7700 FSP Controllers after the upgrade and configure the hostname and network.

3. You can install or upgrade Symphony at any time in the process.

4. Add all 7700 FSP Controllers and storage shelves to one Symphony instance.

Replication Network Information

In this section, you need to determine the active and desired LAN and WAN link speeds, usage, and the bandwidth limits, as appropriate for the installed environment.

Performance

Table C.1 lists and describes the TCP ports that are used for replication operations. The replication process uses the TCP ports listed in this table to handle one-way incoming requests. The reply to each of these requests is sent back using a dynamic port number. Network firewalls must be configured to allow access through these TCP ports for successful communications.

Note: Other ICMP, UDP, and other TCP ports will also be used for inspection and diagnostics purposes (for example, ping and traceroute; and iperf uses TCP 5001).

Port Source Used By Description

11576 Concerto device • CLI from SAN client

• Concerto Management Console

• IMA

• MemRecover

• Snapshot Director

• VMware

• Tiebreaker server

(RPC) Secure RPC communication port used for sending requests to the configuration management module on the server.

11577 • Replication source server

• Replica server

• Replica server

• Replication source server

(Replication location/IOCore) Communication port used to send replication data. This port is only open while replication is being performed. Otherwise, this port remains closed.

Table C.1 TCP Ports and Replication



IP Addresses

Collect all virtual IP addresses for each configured rep0 interface, and collect route information between the 7700 FSP Controllers. A route must be specified at each 7700 FSP Controller instance to assure the proper use of the rep0 ports and replication path.

Table C.2 lists the information required for site-to-site replication operations, which includes the host name, IP address, subnet mask, bitmask, network ID, and gateway to replication partner.

11579 • Concerto device (primary)

• Concerto device (secondary)


• Concerto device (primary)

(Auth) Authentication for replication.

11580 • Concerto device (primary)



• Concerto device (primary)

(Failover) Communication port used between a pair of failover servers (this is not required for a standalone Concerto OS-based controller).

11582 Concerto device • CLI from SDAN client

• MemRecover

• HyperTrac

• Snapshot Director

• VMware

(CLI Proxy)Communication port used to send CLI commands to the 7700 FSP Controller.

11583 Concerto device Concerto Management Console

(RPT_STAT)Communication port used to send report requests to the configuration management module on the server: such as report schedules, global replication report, and statistics log configuration updates.

Port Source Used By Description

Table C.1 TCP Ports and Replication(Continued)

HostName

IP Address

Subnet Mask Bitmask Network

IDGateway to Replication

Partner

sample site1 192.168.1.11 255.255.255.248 29 192.168.1.8 192.168.1.9

sample site2 192.168.2.11 255.255.255.248 29 192.168.2.8 192.168.2.9

Site1 7700 FSP Controller A

<site1-rep0-ipaddress>

<site1-rep-netmask>

<site1-rep-bitmask>

<site1-rep-network>

<site1-rep-gateway>

Site2 7700 FSP Controller A

<site2-rep0-ipaddress>

<site2-rep-netmask>

<site2-rep-bitmask>

<site2-rep-network>

<site2-rep-gateway>

Table C.2 Site-to-Site Replication



Adding HA at each Site

If you are enabling HA that will include replication ports, you must collect virtual IPs for the HA partners and monitor IPs for all rep0 interfaces (for details, see Replication in an HA Environment on page 135).

Configuring Interfaces Using CLI Commands

You can only configure network interfaces when HA is not enabled. The status of Concerto-based devices such as the 7700 FSP Controllers as either primary or replica is determined on a per LUN-basis. The following example shows default authentication and MTU 1500 values.

Configuring Site 1, 7700 FSP Controller A

1. Log into the site1 7700 FSP Controller A CLI by using its login credentials.

2. Disable HA by issuing the following command:

3. Configure rep0 by issuing the following commands:

For example:

4. Add a replication route from rep0 to Site2 by setting a static replication route for each replication interface, as shown:

For example:

ip route add 192.168.2.8 via 192.168.1.9 dev rep0

5. Inspect the static replication route, as shown:

[controller-a ~]# isscli disableha -s <site1-cont-a-virtual-ipaddress> -u root -p <password> -S <site1-cont-b-virtual-ipaddress> -U root -P <password>

[controller-a ~]# networkconfig.sh initialize[controller-a ~]# networkconfig.sh setnic rep0 no 1500 1 -1 <site1-rep0-ipaddress> <site1-netmask>

networkconfig.sh setnic rep0 no 1500 1 -1 192.168.1.11 255.255.255.248[mg-a ~]# networkconfig.sh finalize[mg-a ~]# networkconfig.sh restart 1 1 1[mg-a ~]# concerto start update[mg-a ~]# ifconfig rep0 up

[controller-a ~]# ip route add <site2-rep-network> via <site1-rep-gateway> dev rep0

[controller-a ~]# ip route[controller-a ~]# ping -I rep0 <site2-rep-gateway> -c 5 -s 1500[controller-a ~]# traceroute <site2-rep-gateway>



6. Make the replication route persistent by creating or editing an existing route file to reload the route after a 7700 FSP Controller reboot.

Use vi (or any text editor) to add a line, insert, write, quit, and then confirm the file access rights as shown:

Verify the file content:

For example:

7. Perform a network inspection, and confirm the IP address, subnet, and the Concerto setup, as shown:

8. Use iperf -h to display command parameters related to basic network performance as shown:

For example, this is some sample output from 10.5.1.25:

9. Verify that there is bidirectional bandwidth, going from the local host to the remote host, which defaults to the destination TCP port 5001 and 1640 (use -p to specify alternate ports):

10.Inspect or edit the HA configuration before attempting to re-enable HA and type 'n' or <ctrl>+C to make no changes to the current ha_precfg.ini file, as shown:

Note: You may wish to add the rep0 port to the HA configuration (for details, see Replication in an HA Environment on page 135). 7700 FSP Controller A requires both the heartbeat and monitor IP addresses to be in the same subnet as rep0 (7700 FSP Controller B also requires two IP addresses in the same subnet). Complete all rep0 port configuration prior to issuing the enableha command.

[controller-a ~]# vi /etc/sysconfig/network-scripts/route-rep0[controller-a ~]# chmod a+rx route-rep0

<site2-rep-network>/<site2-rep-netmask> via <site1-rep-gateway> dev rep0

#static route added for rep0192.168.2.8/29 via 192.168.1.9 dev rep0

[controller-a ~]# ifconfig -a | grep rep0 -A8[controller-a ~]# cat $IS_CONF | grep rep0

[controller-a ~]# iperf -c <site2-rep-gateway>[controller-a ~]# iperf -h

iperf -c 10.5.75.100 ------------------------------------------------------------Client connecting to 10.5.75.100, TCP port 5001TCP window size: 64.0 KByte (default)------------------------------------------------------------[ 3] local 10.5.1.25 port 60838 connected with 10.5.75.100 port 5001[ ID] Interval Transfer Bandwidth[ 3] 0.0-10.0 sec 1.11 GBytes 952 Mbits/sec

[controller-a ~]# iperf -c <site2-rep-gateway> –r

[controller-a ~]# cfghaprecfg.sh



11.Re-enable HA, by issuing the following commands:

12.Inspect HA, by issuing the following commands:

Configuring Site 2, 7700 FSP Controller A

1. Log into the site2 7700 FSP Controller A CLI by using its login credentials.

2. Disable HA by issuing the following command:

3. Configure rep0 by issuing the following commands:

For example:

4. Add a replication route from rep0 to Site2 by setting a static replication route for each replication interface, as shown:

For example:

5. Inspect the static replication route, as shown:

6. Make the replication route persistent by creating or editing an existing route file to reload the route after a 7700 FSP Controller reboot.

Use vi (or any text editor) to add a line, insert, write, quit, and then confirm the file access rights as shown:

[controller-a ~]# isscli enableha -s <site1-cont-a-ipaddress> -u root -p <password> -S <site1-cont-b-ipaddress> -U root -P <password> -pcu admin -pcp admin -ar -X 60

[controller-a ~]# sms[controller-a ~]# isscli getfailoverstatus

[controller-a ~]# isscli disableha -s <site2-cont-a-ipaddress> -u root -p <password> -S <site2-cont-b-ipaddress> -U root -P <password>

[controller-a ~]# networkconfig.sh initialize[controller-a ~]# networkconfig.sh setnic rep0 no 1500 1 -1 <site2-rep-ipaddress> <site2-netmask>

networkconfig.sh setnic rep0 no 1500 1 -1 192.168.2.11 255.255.255.248[mg-a ~]# networkconfig.sh finalize[mg-a ~]# networkconfig.sh restart 1 1 1[mg-a ~]# concerto start update[mg-a ~]# ifconfig rep0 up

[controller-a ~]# ip route add <site1-rep-network> via <site2-rep-gateway> dev rep0

ip route add 192.168.1.8 via 192.168.2.9 dev rep0

[controller-a ~]# ip route[controller-a ~]# ping -I rep0 <site1-rep0-ipaddress> -c 5 -s 1500[controller-a ~]# traceroute <site1-rep0-ipaddress>

[controller-a ~]# vi /etc/sysconfig/network-scripts/route-rep0[controller-a ~]# chmod a+rx route-rep0



Verify the file content:

For example:

7. Perform a network inspection, and confirm the IP address, subnet, and the Concerto setup, as shown:

8. Use iperf -h to display command parameters related to basic network performance as shown:

9. Verify that there is bidirectional bandwidth, going from the local host to the remote host, which defaults to the destination TCP port 5001 and 1640 (use -p to specify alternate ports):

10.Inspect or edit the HA configuration before attempting to re-enable HA and type 'n' or <ctrl>+C to make no changes to the current ha_precfg.ini file, as shown:

Note: You may wish to add the rep0 port to the HA configuration (for details, see Replication in an HA Environment on page 135). 7700 FSP Controller A requires both the heartbeat and monitor IP addresses to be in the same subnet as rep0 (7700 FSP Controller B also requires two IP addresses in the same subnet). Complete all rep0 port configuration prior to issuing the enableha command.

11.Re-enable HA, by issuing the following commands:

12.Inspect HA, by issuing the following commands:

<site2-rep-network>/<site1-rep-netmask> via <site2-rep-gateway> dev rep0

#static route added for rep0192.168.1.8/29 via 192.168.2.9 dev rep0

[controller-a ~]# ifconfig -a | grep rep0 -A8[controller-a ~]# cat $IS_CONF | grep rep0

[controller-a ~]# iperf -c <site1-rep0-ipaddress>[controller-a ~]# iperf -h

[mg-a ~]# iperf -c <site1-rep0-ipaddress> –r

[controller-a ~]# cfghaprecfg.sh

[controller-a ~]# isscli enableha -s <site2-cont-a-ipaddress> -u root -p <password> -S <site2-cont-b-ipaddress> -U root -P <password> -pcu admin -pcp admin -ar -X 60

[controller-a ~]# sms[controller-a ~]# isscli getfailoverstatus



Using Symphony to Configure Replication

The status of Concerto-based devices such as the 7700 FSP Controllers at each site as either primary or replica is determined on a per LUN-basis. You need to enable LUN replication using the procedures in Symphony Help.

Note: This section only provides an overview of the tasks that are involved in configuring replication. For specific details and procedural steps, see the latest version Symphony Help.

Task 1: Adding LUNs

1. Complete any necessary prerequisites.


3. Select a 7700 FSP Controller in the Manage Devices panel in the left navigation pane (you are choosing the device that will be a primary replica server).

4. With the LUNs tab selected, click Add (+) and specify the options to create a LUN.

5. Complete the procedural steps in the "Adding LUNs" topic in Symphony Help to add the LUN needed for replication.

Task 2: Creating a Snapshot Resource

Before you can add a replication policy, you must first create a snapshot resource for the LUN. You can create a snapshot resource using the procedures in Symphony Help. This section only provides an overview of the tasks that are involved in adding a snapshot resource (for specific details and steps, see the latest version Symphony Help).

1. Select Manage > Devices > Snapshot Resources.

2. Select a 7700 FSP Controller in the Manage Devices panel in the left navigation pane.

A list of available LUNs on the device appears in a table in the main window.

3. Click to select a LUN from the list, which highlights the selected LUN.

4. Click Add (+).

The Create Snapshot Resource dialog displays.

5. Complete the procedural steps in the "Creating a Snapshot Resource" topic in Symphony Help to configure and create a Snapshot Resource needed for replication.

Task 3: Creating a Replication Policy for a LUN

Replication is the process by which a SAN resource maintains a copy of itself, and the data is copied, distributed, and then synchronized to ensure consistency between the redundant resources. The LUN that is being replicated is known as the primary LUN, and the changed data is transmitted from the primary to the replica LUN so that they are in synch with one another.

You can create a replication policy for the designated LUN using the procedures contained in Symphony Help. This section only provides an overview of the tasks that are involved in creating a replication policy (for specific details and steps, see the topic on creating a replication policy for a LUN in the latest version Symphony Help). This is a three-step process:

• Define the primary and replica LUNs



• Define a replication policy

• Define the transfer mode and transmission

1. To define primary and replica LUNs, select Manage > Devices.

2. Select a 7700 FSP Controller in the Manage Devices panel in the left navigation pane.

A list of available LUNs on the device appears in a table in the main window.

3. Click to select a LUN from the list as the primary LUN, which highlights the selected LUN row.

4. Click Replication in the menu bar and select Add Replication.

The Add Replication dialog displays.

5. Select the Primary LUN from the drop down list.

The Primary Controller names appears in the dialog about the Primary LUN name.

6. Complete the procedural steps in the "Creating a Replication Policy for a LUN" topic in Symphony Help to configure and create a replication policy for the selected LUN.

Make sure to designate the Replica Controller rep0 IP address. The Primary Controller will communicate with the Replica Controller to apply these settings.

Task 4: View Replication Data

1. To view replication data, select Manage > Devices.

2. Select the 7700 FSP Controller in the Manage Devices panel that you configured as the primary replica server.

3. Select the Replications tab to display the Replications window showing the entire table of replication-related status including the following:

• Primary Controller

• Primary LUN

• Replica Controller

• Replica IP Address

• Replica LUN

• Snapshot Group

• Replication Status

• Last Sync

• Next Sync



Replication in an HA Environment

It is required that the IP addresses for data/virtual and monitor/heartbeat must be in the same IP subnet on each interface. Each interface must be able to access the IP address of its HA partner.

Note: Replication is not supported between HA partners.

Use the exact same commands to configure the rep0 interface for the HA partner as you issued for the HA primary in the partner pair. The following example uses 7700 FSP Controller references.

7700 FSP Controller B Login

Log in to HA partner (7700 FSP Controller B) CLI while HA is disabled on the HA primary (7700 FSP Controller A), and use the following commands as shown:

1. Configure 7700 FSP Controller B rep0 port using these commands:

2. Test basic access between the two 7700 FSP Controllers (7700 FSP Controller B to 7700 FSP Controller A) by using the following commands:

Confirm that rep0 for 7700 FSP Controller A indicates its MAC address.

3. Add a replication route from 7700 FSP Controller B rep0 to Site2.

For details, see step 4 and step 6 in Configuring Site 1, 7700 FSP Controller A on page 129.

4. Return to 7700 FSP Controller A to complete HA configuration and enable HA.

Table C.3 provides host, virtual IP address, and monitor IP address examples for rep0 when setting up HA.

<site1-controller-b-rep0-ipaddress><site2-controller-b-rep0-ipaddress>

[controller-b ~]# ping -I rep0 <site1-rep0-ipaddress> -c 5 -s 1500[controller-b ~]# arp -a

Host Virtual IP Address Monitor IP Address

Sample site1, 7700 FSP Controller A

192.168.1.11 192.168.1.12

Sample site1, 7700 FSP Controller B

192.168.2.13 192.168.1.14

Sample site2, 7700 FSP Controller A

192.168.2.11 192.168.2.12

Sample site2, 7700 FSP Controller B

192.168.2.13 192.168.2.14

Site 1, 7700 FSP Controller A

<site1-rep0-ipaddress> <site1-rep0-monitoripaddress>

Site 1, 7700 FSP Controller B

<site1-controllerb-rep0-ipaddress> <site1-controllerb-rep0-monitoripaddress>

Table C.3 Information for rep0 HA



Example cfghaprecfg Files with Sample Values for Site 1 and Site 2

The following cfghaprecfg.sh output example displays sample values for 7700 FSP Controller A and 7700 FSP Controller B in site 1 and site 2, and follows the same format as the ha_precfg.ini file. Observe that the sequence of "interface =" comma-separated interface names correspond to the "heartbeat ip =" and "virtual ip =" IP address values.

Site 1: 7700 FSP Controller A and 7700 FSP Controller B

Site 2, 7700 FSP Controller A

<site2-rep0-ipaddress> <site2-rep0-monitoripaddress>

Site 2, 7700 FSPController B

<site2-controllerb-rep0-ipaddress> <site2-controllerb-rep0-monitoripaddress>

[HA] enabled = true mutual = true powercontrol = ipmi isStretchCluster = false[primary] hostname = site1-controller-a sci_ip = 169.254.2.101 interface = eth0,rep0 heartbeat_ip = 10.0.XXX.XX2,192.168.1.12 virtual_ip = 10.0.XXX.XX1,192.168.1.11 ipmi_ip = 169.254.1.101 quorum_drive = any quorum_mirror_drive =[secondary] hostname = site1-controller-b sci_ip = 169.254.2.102 interface = eth0,rep0 heartbeat_ip = 10.0.XXX.XX4,192.168.1.14 virtual_ip = 10.0.XXX.XX3,192.168.1.13 ipmi_ip = 192.168.1.102 quorum_drive = any quorum_mirror_drive =

Host Virtual IP Address Monitor IP Address

Table C.3 Information for rep0 HA(Continued)



Site 2: 7700 FSP Controller A and 7700 FSP Controller B

[HA] enabled = true mutual = true powercontrol = ipmi isStretchCluster = false[primary] hostname = site2-controller-a sci_ip = 169.254.2.101 interface = eth0,rep0 heartbeat_ip = 10.0.XXX.XX2,192.168.2.12 virtual_ip = 10.0.XXX.XX1,192.168.2.11 ipmi_ip = 169.254.1.101 quorum_drive = any quorum_mirror_drive =[secondary] hostname = site2-controller-b sci_ip = 169.254.2.102 interface = eth0,rep0 heartbeat_ip = 10.0.XXX.XX4,192.168.2.14 virtual_ip = 10.0.XXX.XX3,192.168.2.13 ipmi_ip = 192.168.1.102 quorum_drive = any quorum_mirror_drive =


APPENDIX D Configuring Brocade 6510 Fibre Channel Switches

This appendix provides reference information and contains procedures for setting up and configuring the Brocade 6510 Fibre Channel switches that are used within the 7700 FSP storage cluster.

Configuring Brocade 6510 for a 7700 FSP System

Before starting to configure the Brocade 6510, make sure you have completed all of the preconfiguration steps prior to configuring the switches.

Performing Brocade 6510 FC Switch Preconfiguration

To perform preconfiguration, complete the following:

1. Connect a laptop, PC, or Mac to the RJ-45 serial port on the Brocade 6510 FC switch.

2. Start a terminal emulation program, and use the following settings:

— Bits per second: 9600

— Data bits: 8

— Parity: None

— Stop bits: 1

— Flow control: None

3. Log into the FC switch using the factory default username and password: "root" and "fibranne".

Note: The default IP address of the FC switch is 10.77.77.77, and is for optional configuration without a using a serial console connection.


Appendix D - Configuring Brocade 6510 Fibre Channel Switches

4. Start the Console session, which prompts you to change the default settings and set new FC switch passwords for "root", "admin", "factory", and "user".

Any new passwords that you set must observe existing customer-based corporate or network password naming conventions, and make sure that all new passwords are recorded. In addition, to inspect and change account passwords, you can use the following:

• To change the current login: log in using "admin" and "passwd".

• To inspect the current login accounts: log in and issue userconfig -show <username> or userconfig -show -a.

• To change another login password: log in using "admin" and "passwd <username>".

5. Type "ipaddrset" to set new IP addresses for the FC switch Management, subnet mask, and default gateway to uniquely identify them on the network.

6. Connect the FC switch Management network RJ-45 port to the management network.

7. Confirm that this connection is valid and functional by using the "ping" command with the gateway IP address.

8. Type "exit" and logout.

9. Continue FC switch management using SSH and the Management IP address you just assigned.

10.Repeat these steps on the second Brocade 6510 FC switch in your 7700 FSP storage cluster system.

Configuring the Brocade 6510 FC Switch

To set the FC switch hostname and network services for each Brocade 6510, perform the following:

Note: To get instructions for any Brocade CLI command, prepend the command with "help".

1. Start a terminal session (using PuTTY or a similar SSH program) to connect to the Management IP address.

2. Change the default FC switch name by issuing the switchname "<new-switchname>" CLI

command, as shown:

switchname:user> switchname "FC7700-switch-a"Committing configuration...Done.Switch name has been changed. Please re-login into the switch for the change to be applied.switchname:root> logoutFC7700-switch-a:root>


Configuring Brocade 6510 for a 7700 FSP System

3. Inspect the FC switch IP and hostname by issuing the "fabricshow" CLI command, as

shown:

4. Change the default FC switch DNS configuration by issuing the "dnsconfig" CLI command, as shown below:

Note: The DNS server IP addresses listed in this step (10.5.0.12 and 10.5.0.13) are example DNS server IP addresses.

5. Inspect the FC switch time zone (default is UTC) by issuing the "tstimezone" CLI commands, as shown:

To set the time zone offset or zone:

To navigate to set your time zone:

6. Set the NTP time server by issuing the "tsclockserver" CLI command, as shown in the following single and multiple NTP time server examples:

To set for a single NTP time server:

FC7700-switch-a:root> fabricshowSwitch ID Worldwide Name Enet IP Addr FC IP Addr Name1: fffc01 10:00:50:eb:1a:6d:1b:f0 10.5.76.81 0.0.0.0 "FC7700-switch-a"

FC7700-switch-a:root> dnsconfig1 Display Domain Name Service (DNS) configuration2 Set DNS configuration3 Remove DNS configuration4 QuitSelect an item: (1..4) [4] 2Enter Domain Name: [] eng.vmem.intEnter Name Server IP address in dot notation: [] \ 10.5.0.12Enter Name Server IP address in dot notation: [] \ 10.5.0.13DNS parameters saved successfullyEnter option1 Display Domain Name Service (DNS) configuration2 Set DNS configuration3 Remove DNS configuration4 QuitSelect an item: (1..4) [4] 4

FC7700-switch-a:root> tstimezone <+ or - ><hours-offset>, <+ or - ><minutes-offset)

FC7700-switch-a:root> tstimezone --interactive

FC7700-switch-a:root> tsClockServer 192.168.0.1Updating Clock Server configuration...done.Updated with the NTP servers.


Appendix D - Configuring Brocade 6510 Fibre Channel Switches

To set for multiple NTP time servers:

7. Inspect the FC switch date and time (if not setting an NTP time server) by issuing the "date" CLI command, as shown:

8. Inspect the FC switch version by issuing the "version show" command, as shown in the following command:

9. Inspect the FC switch license by issuing the "showlicense" command, as shown:

Note: The Brocade 6510 FC switches are licensed to use up to 24 ports. If you need more than 24 ports, you must obtain additional licenses. Contact Violin Systems Customer Support for more information. For details, see Contacting Violin Systems on page 5.

Inspect FC switch access accounts:

10.Inspect the FC switch ports and confirm that NPIV is enabled on all ports by issuing the "portcfgshow" command, as shown:

Note: It is recommended that you record the output of this current deployed configuration, and save this as a configuration backup for reference.

11.Repeat this process on the second Brocade 6510 FC switch in your 7700 FSP storage cluster system.

FC7700-switch-a:root> tsClockServer 192.168.0.1; 192.168.0.3Updating Clock Server configuration...done.Updated with the NTP servers.

FC7700-switch-a:root> date "mmddhhmmyy"

FC7700-switch-a:root> version showKernel: 2.6.14.2Fabric OS: v7.0.2cMade on: Fri Feb 22 21:29:23 2013Flash: Wed Jan 7 17:53:32 2015BootProm: 1.0.9

FC7700-switch-a:root> licenseshowNo licenses installed.

FC7700-switch-a:root> userconfig --show -a

FC7700-switch-a:root> > portcfgshow


APPENDIX E Installing and Accessing Violin Symphony

This appendix provides reference information about installing Symphony and contains a procedure for accessing Symphony using a supported Web browser.

Installing Violin Symphony

At the same time that you start to install, rack-mount, and connect all of the 7700 Flash Storage Platform devices to your storage network, it is a good practice to install either the Violin Symphony VM (VMware) or Violin Symphony RPM (Red Hat Package Manager) on a separate server capable of accessing all of your 7700 Flash Storage Platform components.

For the latest Symphony installation instructions, system requirements, supported platforms, supported Web browsers, and post-installation procedures for installing and getting started with Symphony, see the latest version Violin Symphony Installation Guide. The following section assumes you have successfully installed Symphony and any necessary licenses.

Accessing Symphony

Access Symphony by completing the following:

1. Open one of the supported Web browsers that are listed in the "System Requirements" section in the latest Violin Symphony Installation Guide.

2. Enter the Symphony IP address in the browser address field and press Enter.

The Violin Symphony login dialog appears.

3. Enter your user name and password, and click Login.


Appendix E - Installing and Accessing Violin Symphony

Note: The default login credentials to use for login name and password are admin, admin.

See the Violin Symphony Help for instructions on using Violin Symphony:


APPENDIX F Configuring Stretched Cluster and Tiebreaker

This chapter provides an overview that describes stretched cluster basics, provides prerequisites needed to install and use a stretched cluster, describes how to configure a stretched clusterstretched cluster, and provides procedures for installing, configuring, and managing tiebreaker for stretched clusters in the following topics:

• Overview: Stretched Clusters on page 145

• Configuring a Stretched Cluster on page 148

• Installing and Configuring Tiebreaker on page 152

Overview: Stretched Clusters

A stretched cluster is a 7700 Flash Storage Platform where each of the 7700 FSP Controllers is located in a different network location. A stretched cluster provides synchronous mirroring and storage redundancy. A stretched cluster 7700 FSP Controller can fail over to the remote site 7700 FSP Controller, which then takes over responsibility for the storage and workload of the remote site during a failure.

In a stretched cluster configuration, the two 7700 FSP Controllers could be located on different floors in the same building or in different buildings in the same city. A stretched cluster provides synchronous mirroring with array-based high availability that allows application workloads to run at both sites.

If a failure occurs at either site, the 7700 FSP Controller at the surviving site will take over storage services for the failed 7700 FSP Controller and your applications and operations will continue running.

Each stretched cluster site will have a 7700 Controller, one or more Fibre Channel cluster switches, and one or more 7000 Series or 6000 Series storage shelves to provide primary local storage services. An external server, where the Tiebreaker utility resides, manages the interpretation of site status and failover between sites.


Appendix F - Configuring Stretched Cluster and Tiebreaker

Stretched cluster configurations need an external server or the Cloud to serve as the location for the Tiebreaker utility, which manages the interpretation of site status and failover between the stretched cluster sites. If a 7700 FSP Controller fails at either site, the 7700 FSP Controller at the surviving site will take over storage services for the offline 7700 FSP Controller.

In this way, a properly configured stretched cluster environment contains redundant 7700 FSP Controllers, southbound Fibre Channel switches, and storage shelves that provide you with complete end-to-end storage services across both sites in which the storage cluster spans.

Note: For specific details about stretched cluster connectivity, deployment, and best practices, see the latest version Concerto 7700 FSP Stretch Cluster Implementation and Best Practices Guide.

Stretched Cluster Prerequisites

This section describes the basic requirements that need to be in place to deploy the 7700 FSP as a stretched cluster:

• Storage and zoning requirements

• Networking and Tiebreaker requirements

Storage and Zoning Requirements

A stretched cluster requires the following storage and zoning configuration:

1. Each site where a 7700 FSP Controller is deployed requires access to a northbound storage fabric, a southbound storage fabric, and at least one storage shelf.

Each 7700 FSP Controller mirrors application data on each LUN from the shelf at its local site to the corresponding shelf at the remote site. In general, local applications will run at both sites while either site is prepared to take over all traffic in the event of a failure at the other site.

2. The Fibre Channel switches must have long-distance Inter-Switch Link (ISL) connections. The 7700 FSP Controller at each site must have southbound access to the storage shelves at the remote site. This requires that the southbound initiator ports on each 7700 FSP Controller (ports 100, 101, 104, and 105) must be included in Fibre Channel switch zones at the remote site.

3. Each site must have two 11GB storage pools created on the local shelf to be configured as 7700 FSP Controller Configuration Repositories (CRs). One of the 11GB storage pools is the CR for the local 7700 FSP Controller, and the other 11GB storage pool is the CR for the remote 7700 FSP Controller.

Each 7700 FSP Controller maintains a mirror of its own CR at the remote site. During failover, the surviving 7700 FSP Controller takes control of the CR mirror at the remote site. See Figure F.1 for an example of a best practice CR for a 7700 FSP stretched cluster, and for more details, see the latest version Concerto 7700 FSP Stretch Cluster Implementation and Best Practices Guide.


Overview: Stretched Clusters

4. Use Symphony to mirror the CRs that are created during the initial configuration of the 7700 FSP storage cluster. On each 7700 FSP Controller, a separate storage pool is created for its local CR, and its mirror CR resides on a shelf at the remote site.

For specific details and procedures for configuring a CR and configuring failover in which the CR is mirrored in a stretched cluster, see the topics for creating a CR and for configuring failover for a 7700 FSP or stretched cluster in the latest version Symphony Help.

5. To enable synchronous mirroring for application data, matching storage cluster LUNs need to be created on the shelf at both, local and remote sites.

Networking and Tiebreaker Requirements

A stretched cluster requires meeting the following networking and Tiebreaker requirements:

1. The 10Gbps SCI (Storage Cluster Interlink) optical ports (SCI-0) on the 7700 FSP Controllers in the stretched cluster need IP network access to communicate with each another.

Connectivity can be via a direct LAN link, a long-distance fibre connection, or via a Fiber Optic WAN transport connection with 1Gbps guaranteed minimum bandwidth between the two remote sites. The SCI-1 ports do not need to be connected for stretched cluster operations.

If there is existing network connectivity between the two sites in a stretched cluster, link the SCI-0 ports over that connection (provided that this connection meets the 1Gbps guaranteed minimum bandwidth).

2. Each 7700 FSP Controller and storage cluster shelf needs management and HA monitor IP addresses that are accessible from both the local and remote sites, and from the Symphony server which uses these IP addresses for storage management and monitoring.

3. A Linux server is needed as the location for the Tiebreaker utility. Ideally, the Tiebreaker utility should reside at a 3rd site or in the Cloud, and it needs IP network access to both 7700 FSP Controller management and monitoring IP addresses.

The Tiebreaker utility is deployed to prevent a split-brain scenario condition, in which both 7700 FSP Controllers assume that the other one has failed. It is recommended that the Tiebreaker utility be installed on a dedicated physical Linux-based server or on a virtual machine that has Linux OS installed.

Note: The IP addresses associated with the IPMI ports on both 7700 FSP Controllers must be accessible via Tiebreaker using valid IPMI credentials.



Configuring a Stretched Cluster

Prior to configuring a stretched cluster, you must complete the following tasks:

• Identifying Northbound and Southbound Ports on 7700 FSP Controllers on page 149

• Disabling Target Mode on the Southbound Ports on page 149

• Inspecting the Discovered Devices on page 149

• Renaming LUNs and Minimum Stretched Cluster LUN Requirements on page 149

• Creating Local and Remote Storage Pools on Site-A on page 150

• Creating a Configuration Repository/Mirror on Site-A on page 151

• Creating Local and Remote Storage Pools on Site-B on page 151

• Creating a Configuration Repository and Mirror on Site-B on page 151

• Enabling HA on page 151

• Checking Failover Status on page 152

Note: If you intend to create a stretch cluster, it is recommended that you first read Overview: Stretched Clusters on page 145 and Enabling a Stretched Cluster on page 152, prior to using the HA CLI commands. For specific details about CLI commands, refer to the Concerto Command Line Interface Reference.

Figure F.1 Example of a 7700 FSP stretched cluster Configuration Repository (CR) Best Practice

Tip: When creating a 7700 FSP stretched cluster configuration, each 7700 FSP Controller needs to know the management IP addresses for the two Fibre Channel switches, and each 7700 FSP Controller needs a second IP address in the same subnet of the management IP address, which is used for cluster heartbeat monitoring (and this must be accessible from the 7700 FSP Controller at the remote site).



Identifying Northbound and Southbound Ports on 7700 FSP Controllers

Identify and display a list of Fibre Channel adapters by using the getadapterinfo CLI command as shown:

Note: To confirm the correct southbound HBA ports using Symphony, see Confirming Southbound HBA Information on page 72.

For Fibre Channel, the southbound ports on a 7700 FSP Controller should be ports 100, 101, 104, and 105.

For iSCSI, the southbound ports on a 7700 FSP Controller should be ports 100, 101, 102, and 103.

Disabling Target Mode on the Southbound Ports

Disable the target mode on a specified Fibre Channel adapter (for example, 100-105) by using the disablefcadaptertarget CLI command as shown:

Assign LUNs at the storage shelves in the stretched cluster environment to both of the 7700 FSP Controllers. At each of the 7700 FSP Controllers, rescan for new physical devices by using the rescandevices CLI command as shown:

Inspecting the Discovered Devices

Gather new and current physical device information in your system by using the following getpdevinfo CLI commands as shown:

Renaming LUNs and Minimum Stretched Cluster LUN Requirements

The minimum requirement for a stretched cluster is to have two LUNs for the quorum and two LUNs for data per each supported shelf. The best practice for improving ease of use and for diagnostic purposes is to name each LUN with a symbolic name that easily and uniquely identifies it.

isscli getadapterinfo -s <node name/ip address>

isscli disablefcadaptertarget -s <node name/ip address> -a 100isscli disablefcadaptertarget -s <node name/ip address> -a 101isscli disablefcadaptertarget -s <node name/ip address> -a 104isscli disablefcadaptertarget -s <node name/ip address> -a 105

isscli rescandevices -s <node name/ip address>

isscli getpdevinfo -s <node name/ip address> -Fisscli getpdevinfo -s <node name/ip address> -F -o detail | egrep '^Size:|Owner:|guid:|Hardware ID:|ACSL:'



Use the renamephysicaldevice CLI command to rename the LUNs as a best practice, as shown for both Site-A and Site-B:

Tip: When one device is renamed on a server in a failover pair, the corresponding device is also renamed on the partner server.

Creating Local and Remote Storage Pools on Site-A

Create local and remote storage pools on a designated site (for example: Site-A, head-A) by using the createstoragepool CLI command, which creates the following (and provides an example):

• A storage pool named local-A, and lets you add Quorum-A and Data-A (with the following values, Quorum-A: 105:0:0:1 and Data-A: 104:0:3:3)

• A storage pool named remote-A, and lets you add Quorum-A-Remote and Data-A-Remote (with the following values, Quorum-A-Remote: 106:0:2:4 and Data-A-Remote: 104:0:1:3)

isscli renamephysicaldevice -I 104:0:0:1 -n Quorum-Aisscli renamephysicaldevice -I 104:0:2:4 -n Quorum-A-Remoteisscli renamephysicaldevice -I 106:0:4:3 -n Data-A-Remoteisscli renamephysicaldevice -I 107:0:0:3 -n Data-Aisscli renamephysicaldevice -I 106:0:3:1 -n Quorum-B-Remoteisscli renamephysicaldevice -I 105:0:1:4 -n Data-Bisscli renamephysicaldevice -I 105:0:1:2 -n Quorum-Bisscli renamephysicaldevice -I 104:0:2:2 -n Data-B-Remote

Site-A Site-B

7700 FSP Controller head-A and Storage-A on Site-A

7700 FSP Controller head-B and Storage-B on Site-B

Head-A uses:The quorum disk (Quorum-A) and the data disk (Data-A) from Storage-AThe remote quorum disk (Quorum-A-Remote) and the remote data disk (Data-A-Remote) from Storage-B

Head-B uses:The quorum disk (Quorum-B) and the data disk (Data-B) from Storage-BThe remote quorum disk (Quorum-B-Remote) and the remote data disk (Data-B-Remote) from Storage-A

Storage-A LUNs Storage-B LUNs

• Quorum-A

• Data-A

• Quorum-B

• Data-B

• Quorum-B-Remote

• Data-B-Remote

• Quorum-A-Remote

• Data-A-Remote

Table F.1 Example Site-A and Site-B LUNs Configuration

isscli createstoragepool -SP local-A -D 104:0:3:3, 105:0:0:1 -sa primaryisscli createstoragepool -SP remote-A -D 106:0:2:4, 104:0:1:3 -sa remote



Creating a Configuration Repository/Mirror on Site-A

Create a configuration repository and mirror on Site-A by using the following CLI commands (enableconfigurationrepository and createconfigurationrepositorymirror), as shown:

Creating Local and Remote Storage Pools on Site-B

Create local and remote storage pools on a designated site (for example: Site-B, head-B) by using the createstoragepool CLI command as shown:

• A storage pool named local-B, and lets you add Quorum-B and Data-B (with the following values, Quorum-B: 104:0:2:2 and Data-B: 104:0:0:1)

• A storage pool named remote-B, and lets you add Quorum-B-Remote and Data-B-Remote (with the following values, Quorum-B-Remote: 107:0:1:2 and Data-B-Remote: 104:0:4:4)

Creating a Configuration Repository and Mirror on Site-B

Create a configuration repository and mirror on Site-B by using the following CLI commands (enableconfigurationrepository and createconfigurationrepositorymirror) as shown:

Enabling HA

If you have successfully created a preconfiguration file, use the enableha CLI command to enable HA for two Memory Gateways using the information in this file.

Note: For details about using cfgprecfg.sh or the ha_precfg.ini file, see Configuring High Availability on page 108 and Completing the HA Configuration File on page 108.

Start the process to enable HA from the secondary node by issuing rebindqla (which rebinds the QLogic Adapter) to a specific server host as shown:

isisscli enableconfigurationrepository -I 105:0:0:1isscli createconfigurationrepositorymirror -I 106:0:2:4

isscli createstoragepool -SP local-B -D 104:0:2:2,104:0:0:1 -sa primaryisscli createstoragepool -SP remote-B -D 104:0:4:4,107:0:1:2 -sa remote

isscli enableconfigurationrepository -I 104:0:2:2isscli createconfigurationrepositorymirror -I 107:0:1:2

rebindqla /usr/local/concerto/etc/<hostname-ipaddress>/ipstor.conf



Note: If you are prompted to fix any binding conflict, enter yes.

From the primary node, use the enableha CLI command as shown:

Checking Failover Status

Use the getfailoverstatus CLI command to check the current status of failover. This command also displays all failover settings, including which IP addresses are being monitored for failover. Use the following command on both nodes:

Enabling a Stretched Cluster

Once an HA cluster has been successfully created, use the enabledstretchedcluster CLI command from the primary node, as shown:

Installing and Configuring Tiebreaker

Tiebreaker is a utility that must be installed on an independent physical or virtual server running Linux, which is external to the 7700 FSP system, specifically for stretched cluster configurations.

Tiebreaker acts to prevent "split-brain" scenarios that can happen if failover servers ever lose communication with each other, and if this happens, each one assumes that the other has failed. In a split-brain scenario, both 7700 Controllers may attempt to write to the same storage, which results in data inconsistency.

Note: Tiebreaker is only recommended for use in stretched cluster configurations.

The Tiebreaker server monitors 7700 Controllers for failover, and attempts to reset an unresponsive server so that the partner can safely take over. Tiebreaker monitors up to 10 failover pairs or stretched clusters, although you cannot use more than one Tiebreaker server to monitor the same failover pair. Tiebreaker uses SNMP for reporting alerts.

Tiebreaker Requirements

Tiebreaker requires an independent server with the following requirements:

• Physical or virtual Linux server for installation of an RPM or OVA file.

isscli enableha -s 192.168.24.7 -u root -p <password> -S 192.168.24.130 -U root -P <password> -pcuroot -pcp <password> -ar

isscli getfailoverstatus -s <node name/ip address>

isscli enablestretchedcluster



• Ability to connect to the 7700 Controllers via the heartbeat IP address.

• Ability to connect to server’s power control device via IPMI or Dell iDRAC.

Downloading Tiebreaker Installation File

1. Go to http://www.violinsystems.com/support/

2. Log in to Customer Support using your Violin Systems Customer Portal login and password information. (Contact Customer Support if you do not have an account.)

3. Click the Software Downloads tab.

4. Navigate to the following folder: Concerto OS7 Flash Storage Platform > Concerto OS <release_version> > Stretch Cluster Software > Stretch Cluster Software Image Files.

5. Depending on the server used for tiebreaker (physical or virtual), download one of the following files:

a. For a virtual server, download the tiebreaker-<release-version>.ova file to a USB drive.

b. For a physical server, download the tiebreaker-<release-version>.rpm file to a USB drive.

Installing Tiebreaker on a Virtual Machine

This section demonstrates the basic steps for installing the tiebreaker-<release-version>.ova file on vCenter server. See the vCenter documentation for more information.

1. Launch a vSphere Client connected to a vCenter Server, then select the ESX server (datacenter) from the navigation pane on the left on which to deploy tiebreaker.

2. Choose File > Deploy OVF Template. Then in the dialog that appears, click Browse, navigate to the download location of the .ova file, select the file, and then click Open.

3. Click Next. The template details appear. Click Next again.

4. Read through the End User License Agreement (EULA), click Accept, click Accept a second time, then click Next.

5. Select the datacenter from the Inventory Location list, enter a unique Name for the VM if necessary, then click Next.

6. Select the resource pool (ESX server) within which to install tiebreaker and then click Next.

7. Select the destination datastore for tiebreaker VM, click Next, then select one of the following provision options:

— Thick Provision Lazy Zeroed: requires a minimum of 60 GB of free space.

— Thick Provision Eager Zeroed: requires a minimum of 60 GB of free space.

— Thin Provision: requires a minimum of 4 GB of free space.

8. Click Next and do one of the following:

— To specify a static IP address, set the appropriate network properties.

— For DHCP, leave the Network Property options blank.

9. Review the configuration summary, click the Power on after deployment check box, then click Finish.


http://www.violin-memory.com/support/


Note: Make note of the Host/Cluster IP address on the Ready to Complete screen, as shown in the following example. You enter this IP address in the browser address bar to launch the tiebreaker VM.

When activated, the Power on after deployment option automatically starts the tiebreaker VM after the installation is complete.

Installing Tiebreaker on an Independent Server

This section demonstrates the basic steps for installing the tiebreaker-<release-version>.rpm file on an independent server. See your server documentation for more information.

1. Attach a keyboard (PS/2) and video (VGA) cable to the independent server.

A mouse and network cables are not required.

2. Insert the USB drive containing the tiebreaker image into the USB port on the server.

3. Boot the tiebreaker image from the USB drive by pressing F11.

Note: For HP appliances, press F9. For IBM appliances, press F12.

A splash screen appears, followed by a list of available boot devices in the BIOS Boot Manager. Wait while the server boots from the USB drive and loads the installation utility.

4. On the Image Installation Summary screen, verify that the installation type, operating system, product, and package to be installed are correct.

5. On the RAID controller screen, click OK.

6. On the Change Host Name screen, enter the host name for the server and then click OK.

7. On the Configure Eth0 IP screen, enter the Ethernet port Eth0 and then click OK.

8. On the Configure Management Port IP Address screen, configure the IP address of IPMI as necessary, and then click OK.

9. Wait while the boot image installation proceeds.

This process takes a few minutes to complete. When the image is installed, a screen appears verifying the process completed successfully.

10.Remove the USB device once the server has powered off.

11.Power the server back on, and wait for the boot image to load.

Note: If the boot device is not found, change the boot order so boot LUN disk is first.

12.On the Change IP Address screen, enter a new IP address or click OK to accept the default.

13.On the Change IPMI screen, enter a new IPMI or click OK to accept the default.



Configure Tiebreaker

This section demonstrates how to configure Tiebreaker on the 7700 Controller on which the Tiebreaker image was installed, and this example sets up Tiebreaker to manage a stretched cluster failover pair.

To configure Tiebreaker, do the following:

1. Execute tiebreakersetup and follow the prompts to configure the Tiebreaker utility.

You are prompted to select an action.

2. Choose a [A]dd to add a new failover pair.

3. You are prompted for the following information:

(This is the SNMP server IP address.)

(This is the amount of time in milliseconds that SCI latency is allowed. Once the SCI latency reaches this value, an SNMP trap is sent.)

(Set this option to monitor the Tiebreaker SNMP daemon status.)

[root@tiebreaker ~]# tiebreakersetup

Select an action:a) - [A]dd a failover pairm) - [M]odify a failover pairr) - [R]emove a failover pairq) - [Q]uit

Failover Type (0/1)(0:Mutual Failover, 1:Non-Mutual Failover, default 1) : 0 Heartbeat IP address of the first active server (ex: 10.0.0.1): 10.6.3.112 Hostname of the first active server: IPS-26857-111 Administration account of the first active server: rootAdministration account password of the first active server:Heartbeat IP address of the secondary server (ex: 10.0.0.2): 10.6.3.110Host name of the secondary server : IPS-26858-109Administration account of the secondary server: rootAdministration account password of the secondary server: IP address of the SNMP managers to receive traps (Max. 5,comma separated. ex: 10.0.0.101,10.0.0.102,10.0.0.103,10.0.0.104,10.0.0.105) : 10.6.3.199)

SCI Latency Threshold (ms), default 200): 200

Mirror Latency Threshold (ms), default 200): 200 (This is the amount of time in milliseconds, that mirror latency is allowed. When mirror latency reaches this value, an SNMP trap is sent.)Send an SNMP heartbeat trap to monitor the Tiebreaker SNMP daemon? (y/n), default n: y

Interval for SNMP heartbeat trap (in seconds, default 300): 300



(Set this option if you have chosen to monitor the Tiebreaker SNMP daemon status. This setting means an SNMP trap will be sent every n seconds.)

(Answer yes to have Tiebreaker monitor this failover pair.)

(Answer yes to allow Tiebreaker to decide what happens when a split-brain event is encountered.)

Your saved configuration appears below:

4. Press Enter to continue.

Start monitoring the Tiebreaker pair (y/n), default y : y

In a split-brain scenario, activate the policy to force a node to take over its partner when all communications from tiebreaker to that partner node have failed (y/n), default y : y

Do you want to Save (y/n) ? Choose y to save.

Failover Type: Non-Mutual FailoverHeartbeat IP address of the first active server: 172.22.12.123Host name of the first active server: H12-122Administration account of the first active server: rootIP address of the second server: 172.22.12.132Host name of the second server: H12-132Administration account of the second server: rootIP address of the SNMP managers to receive traps: 172.22.12.199SCI Latency Threshold (ms): 200Mirror Latency Threshold (ms): 200Send an SNMP heartbeat trap to monitor the Tiebreaker SNMP daemon: noStart monitoring the failover pair: yesIn a split-brain scenario, activate the policy to force a node to take over its partner when all communications from Tiebreaker to that partner node have failed: yesSaving Tiebreaker configuration...The configuration was saved.

Press any key to continue.Select an action :a) - [A]dd a failover pairm) - [M]odify a failover pairr) - [R]emove a failover pairq) - [Q]uit



Manage Tiebreaker

Determine the status of the Tiebreaker server by issuing the tiebreakerd status command. In addition, stop, start, or restart the server using the commands listed in Table F.2 in the command line. Refer to the following table for details.

Tiebreaker Command Description

tiebreakerd status Obtains the status of the Tiebreaker daemon. [root@tiebreaker ~]# tiebreakerd statusSample output:Status of Tiebreaker Monitor Module: [RUNNING]Status of Tiebreaker SNMP Module: [RUNNING]

tiebreakerd start Starts the Tiebreaker daemon.[root@tiebreaker ~]# tiebreakerd startSample output:Starting Tiebreaker Monitor Module: [OK]Starting Tiebreaker SNMP Module: [OK]

tiebreakerd stop Stops the Tiebreaker daemon. [root@tiebreaker ~]# tiebreakerd stopSample output:Stopping Tiebreaker SNMP Module: [OK]Stopping Tiebreaker MonitorModule: [OK]

tiebreakerd restart Stops and starts the Tiebreaker daemon.[root@tiebreaker ~]# tiebreakerd restartSample output:Stopping Tiebreaker SNMP Module: [OK]Stopping Tiebreaker Monitor Module: [OK]Starting Tiebreaker Monitor Module: [OK]Starting Tiebreaker SNMP Module: [OK]

tiebreakerstatus -s This command displays Tiebreaker monitor status. Refer to the Tiebreaker Status Field Definitions on page 158 for additional information.

tiebreakerstatus -c This command displays Tiebreaker configuration status. Refer to the Tiebreaker Configuration Field Definitions on page 159 for additional information.

Table F.2 Tiebreaker Usage



Tiebreaker Status Field Definitions

Table F.3 describes the Tiebreaker status fields.

Sample output:

Status Description

Tiebreaker Monitor Status Indicates whether this failover pair is being monitored. OK indicates the failover pair is being monitored; otherwise the status will display Stopped. To restart Tiebreaker monitoring, refer to the Modifying a Tiebreaker Configuration section.

Primary Health, Secondary health

Indicates whether a split-brain situation has been detected. If it has, Primary Health displays Error and Tiebreaker attempts to trigger power control to reset the primary 7700 Controller. If split-brain has not been detected, Primary Health displays Ok.Secondary Health indicates whether the secondary’s status is healthy or not. If it displays Error, the secondary 7700 Controller is not healthy enough to take over the primary 7700 Controller.

Power Control Type, State Displays the power type and status for each server in the failover configuration (with status values of On, Off, or Unknown).

Storage Cluster ng Latency Indicates if the SCI latency time between the primary and secondary server is OK. An error displays if the latency exceeds the threshold defined during setup.

Mirror Sync Status Indicates whether the mirror in a stretched cluster is synchronized or not. If the failover configuration is not a stretched cluster, this field will display NA.

Primary Failure Status Indicates the primary 7700 Controller failover configuration status (with status values of Up or Failed over).

Primary Management Connection

Indicates whether Tiebreaker is able to communicate with the primary and secondary 7700 Controllers in a failover configuration.

Secondary Management Connection

Table F.3 Tiebreaker Status Field Descriptions



Tiebreaker Configuration Field Definitions

Table F.4 describes Tiebreaker configuration fields.

Configuration Description

SCI Latency Threshold If Tiebreaker detects that SCI latency exceeds the threshold, it sends an SNMP trap to the SNMP receiver. (Default value is 200ms).

MirrorLatencyThreshold If Tiebreaker detects that the mirror latency of any mirrored disks exceeds the threshold, it sends a SNMP trap for each mirrored disk that exceeds the threshold. Check the mirror latency value by navigating to: /usr/local/tiebreaker/[HA_Pair_name]/Type #cat /usr/local/tiebreaker/[HA_Pair_name]/mrlatency

3,2,ac1f0cc6-0000-6e98-5008-e225d9c86ac2,624,46367c31-0888-709a-a224-000051edea17,7864,2,ac160cc7-0000-164d-54a7-e24e28309f9a,502,46367c31-0888-709a-a224-000051edea17,503The last number in the string is the latency value.View mirror latency by performing an SNMP query in your MIB browser.

SNMP Heartbeat Checking Tiebreaker sends an SNMP heartbeat trap to monitor if the Tiebreaker SNMP daemon is alive.

SNMP Heartbeat Checking Interval (sec.)

The interval for SNMP heartbeat traps to be sent.

Tiebreaker Monitoring Failover

Tiebreaker monitors the failover pair status (Health, Power Control, SCI Latency, Mirror status and latency for stretched clusters). N indicates Tiebreaker is not monitoring failover pair status. Y indicates Tiebreaker is monitoring failover pair status.

Tiebreaker Policy Policy to force the secondary server to take over when all communications from the Tiebreaker 7700 Controller to the primary 7700 Controller fails. Yes indicates the policy is active. No indicates the policy is not active and you must manually initiate failover when an unresponsive server cannot be reset.

Table F.4 Tiebreaker Configuration Field Definitions



Sample output:

Modifying a Tiebreaker Configuration

You must modify your Tiebreaker configuration if:

• The failover type (for example, Mutual Failover) changes in your failover configuration. The type must match the Tiebreaker configuration or Tiebreaker will stop monitoring.

• The power control type changes to a non-supported type for the failover pair. Currently only IPMI and Dell iDRAC are supported.

To modify an existing Tiebreaker configuration, do the following:

1. Run command tiebreakersetup.

2. Select [M] to modify a failover pair.

3. Select the appropriate option for the Tiebreaker configuration you wish to modify.

4. Enter the changed value.

[a]Failover Type: Mutual Failover[b]Heartbeat IP address of the first active server: 10.6.13.151[c]Host name of the first active server: IPS-26950-150[d]Administration account of the first active server: root[e]Administration account password of the first active server: *[f]Heartbeat IP address of the second server: 10.6.13.153[g]Host name of the second server: IPS-26949-152[h]Administration account of the second server: root[i]Administration account password of the second server: *[j]IP address of the SNMP managers to receive traps: 10.6.3.199[k]SCI Latency Threshold (ms): 200[l]Mirror Latency Threshold (ms): 200[m]Send an SNMP heartbeat trap to monitor the Tiebreaker SNMP daemon: yesInterval for SNMP heartbeat trap (in seconds): 300[n]Start monitoring the failover pair: yes[o]In a split-brain scenario, activate the policy to force a node to take over its partner when all communications from Tiebreaker to that partner node have failed: yes[q]Quit



5. Type S and click Enter to save the configuration.

Resume Tiebreaker Monitoring

In the event that Tiebreaker stops monitoring a failover pair, follow the steps below to resume monitoring:

1. Run command tiebreakersetup.

2. Select [M] to modify a failover pair.

3. Select the failover pair that you want to resume monitoring.

4. Select [n] to start monitoring the failover pair.

5. Type Y to start monitoring failover pair

6. Type S to save the configuration.

Sample Traps Sent by Tiebreaker

The following are examples of traps sent by the Tiebreaker server.

You may receive two SNMP traps (listed below) during the failover configuration removal process, depending upon how long the removal process takes to complete (you can ignore the first trap).

• Tiebreaker stopped monitoring because its configuration did not match that of the failover pair. Update the configuration appropriately and run setup to restart Tiebreaker monitoring.

• Tiebreaker stopped monitoring because the failover configuration was removed. If you configure failover again, run setup to restart Tiebreaker monitoring.



Setting Up Tiebreaker Using the CLI

Set up Tiebreaker using the CLI as shown:

[root@Tiebreaker-vt2 ~]# tiebreakersetupSelect an option:a) - [A]dd a failover pairm) - [M]odify a failover pairr) - [R]emove a failover pairq) - [Q]uita) - Add a failover pair.===Enter the following parameters to configure Tiebreaker:Failover Type (0/1)(0:Mutual Failover, 1:Non-Mutual Failover, default 0):Heartbeat IP address of the first active server (ex: 10.0.0.1): 192.168.24.140Host name of the first active server: vt2500-3Administration account of the first active server: rootAdministration account password of the first active server:Heartbeat IP address of the second server (ex: 10.0.0.2): 192.168.24.141Host name of the second server: vt2500-33Administration account of the second server: rootAdministration account password of the second server:IP address of the SNMP managers to receive traps (max. 5, comma separated. ex:10.0.0.101,10.0.0.102,10.0.0.103,10.0.0.104,10.0.0.105): 192.168.48.169SCI Latency Threshold (ms), (default 200):Mirror Latency Threshold (ms), (default 200):Send an SNMP heartbeat trap to monitor the Tiebreaker SNMP daemon? (y/n), (default n):Start monitoring the failover pair (y/n, default y): yIn a split-brain scenario, activate the policy to force a node to take over its partner when allcommunications from Tiebreaker to that partner node have failed (y/n), (default y): yDo you want to save (y/n)? yYour saved configuration appears below:Failover Type: Mutual FailoverHeartbeat IP address of the first active server: 192.168.24.140Host name of the first active server: vt2500-3Administration account of the first active server: rootHeartbeat IP address of the second server: 192.168.24.141Host name of the second server: vt2500-33Administration account of the second server: rootIP address of the SNMP managers to receive traps: 192.168.48.169SCI Latency Threshold (ms): 200Mirror Latency Threshold (ms): 200



Upgrading Tiebreaker

This section describes how to upgrade an existing installed Tiebreaker configuration that supports the 7700 Controllers in a 7700 FSP storage cluster. Download the Violin Tiebreaker RPM (Red Hat Package Manager) from the Violin Systems Customer Support website, by completing the following:

1. Using a supported Web browser, navigate to the Customer Support portal at:

http://www.violinsystems.com/support

2. Log into Violin Support using your Username and Password.

3. On the Customer Support page, click Software Downloads.

4. In the left navigation pane, click Folders > Concerto OS7 Flash Storage Platform > Concerto OS <release_version>.

Send an SNMP heartbeat trap to monitor the Tiebreaker SNMP daemon: noStart monitoring the failover pair: yesIn a split-brain scenario, activate the policy to force a node to take over its partner when all communications from Tiebreaker to that partner node have failed: yesCan't open lock file /usr/local/tiebreaker/etc/vt2500-3/.ipstor.conf.lock - 2Can't open lock file /usr/local/tiebreaker/etc/vt2500-33/.ipstor.conf.lock - 2

Saving Tiebreaker configuration...The configuration was saved.[root@Tiebreaker-vt2 ~]# tiebreakerstatus -s vt2500-3_vt2500-33====== vt2500-3_vt2500-33 ======------ Status ------Tiebreaker Monitor Status OKPrimary Health,Secondary Health OK,OKPower Control Type,State IPMIStorage Cluster Interlink Latency OKMirror Sync Status Mirror in-syncPrimary Failover Status UpPrimary Management Connection OKSecondary Management Connection OK====== vt2500-33_vt2500-3 ======------ Status ------Tiebreaker Monitor Status OKPrimary Health,Secondary Health OK,OKPower Control Type,State IPMIStorage Cluster Interlink Latency OKMirror Sync Status Mirror in-syncPrimary Failover Status UpPrimary Management Connection OKSecondary Management Connection OK[root@Tiebreaker-vt2 ~]#


http://www.violin-memory.com/support


5. Under Concerto OS <release_version>, click Stretch Cluster Software > Stretch Cluster Software Image Files, and click the appropriate check boxes.

Note: There are two Tiebreaker options: the ".ova" and ".ova.md5" checksum file extension version is for a virtual server installation, and the ".rpm" and ".rpm.md5" checksum version is for a physical server.

6. Click the Item Actions drop-down, select Download, save the .rpm file, and copy it to the /root directory on the system where Tiebreaker is installed.

To upgrade an existing Tiebreaker configuration, do the following:

Note: This procedure applies to Concerto version 7.6.3.1 and later. When you run the stated commands, ensure that you replace the version number in the sample with the one your 7700 FSP is running.

1. Log in as root on the system where Tiebreaker is installed and enter the following command:

2. Enter the following command to stop the current version Tiebreaker:

3. Enter the rpm -qa | grep tie command.

4. Enter the rpm -e tiebreaker-7.6.3.1-XXXX.x86_64 command.

5. Enter the rpm -ivh tiebreaker-7.6.3.1-XXXX.x86_64 command.

6. Enter the following command to start Tiebreaker:

7. Enter the tiebreakerstatus -s 0 command.

8. Enter the tiebreaker status command.

[root@Tiebreaker1 ~]# tiebreaker status

[root@Tiebreaker1 ~]# tiebreaker stop

[root@Tiebreaker1 ~]# tiebreaker start



9. Enter the tiebreakerstatus -s 0 command to inspect Tiebreaker status.

[root@TieBreaker1 ~]# tiebreakerstatus -s 0====== card-srv3053_card-srv3056 ======------ Status ------Tiebreaker Monitor Status OKPrimary Health,Secondary Health OK,OKPower Control Type,State IPMI,OnStorage Cluster Interlink Latency OKMirror Sync Status Mirror in-syncPrimary Failover Status UpPrimary Management Connection OKSecondary Management Connection OK====== card-srv3056_card-srv3053 ======------ Status ------Tiebreaker Monitor Status OKPrimary Health,Secondary Health OK,OKPower Control Type,State IPMI,OnStorage Cluster Interlink Latency OKMirror Sync Status Mirror in-syncPrimary Failover Status UpPrimary Management Connection OKSecondary Management Connection OK



10.Enter the tiebreakerstatus -c 0 command to verify Tiebreaker status.

====== card-srv3053_card-srv3056 ======------ Config ------Failover Type A-APrimary Heartbeat IP 10.5.77.175Primary Host Name card-srv3053Primary User Name rootPrimary Password *Secondary Heartbeat IP 10.5.77.174Secondary Host Name card-srv3056Secondary Administrator rootSecondary Password *SNMP Manager IP 10.5.79.207SCI Latency Threshold 200MirrorLatencyThreshold 200SNMP Heartbeat Checking yesSNMP Heartbeat Checking Interval (sec.) 300Tiebreaker Monitoring Failover yesTiebreaker Policy yes====== card-srv3056_card-srv3053 ======------ Config ------Failover Type A-APrimary Heartbeat IP 10.5.77.174Primary Host Name card-srv3056Primary User Name rootPrimary Password *Secondary Heartbeat IP 10.5.77.175Secondary Host Name card-srv3053Secondary Administrator rootSecondary Password *SNMP Manager IP 10.5.79.207SCI Latency Threshold 200MirrorLatencyThreshold 200SNMP Heartbeat Checking yesSNMP Heartbeat Checking Interval (sec.) 300Tiebreaker Monitoring Failover yesTiebreaker Policy yesTiebreaker has successfully been upgraded.


APPENDIX G Managing HA Using CLI Commands

This chapter describes how to manage, enable, and disable High Availability (HA) in the 7700 FSP using CLI commands. In addition, this chapter provides a table that lists and describes some potential errors that you could encounter, and provides the available workarounds to resolve the HA issues in the following topics:

• Enabling and Disabling HA Using CLI Commands on page 167

• Troubleshooting HA Issues on page 172

Enabling and Disabling HA Using CLI Commands

Use CLI commands to enable and disable high availability (HA) in the 7700 Flash Storage Platform only after you have completed the prerequisites that ensure that all necessary files and components are properly configured and created.

You may need to disable HA if there is a change to the network configuration information (such as a host name or IP address having changed), or if there is a change related to the DNS server (such as replacing, renaming, or adding another DNS server).

Any changes made to the network configuration information requires that you disable HA, modify the ha_precfg.ini file to update it, and then re-enable HA.

Verifying the Prerequisites

• Collect the 7700 FSP Controller host names and IP addresses.

Note: Do not change the host name or IP address after enabling HA.


Appendix G - Managing HA Using CLI Commands

• Confirm that each 7700 FSP Controller SCI0 port has IP network access to its HA partner (the other 7700 FSP Controller). This access can be in the form of direct connect or WAN access (direct connect access is only for non-stretched cluster configurations).

Confirm that all ports being added to the HA configuration have link UP status, management with eth0, sci0, and rep0 (if replication is supported or being added), Fibre Channel northbound and southbound, and iSCSI ports.

Select one 7700 FSP Controller in each HA pair to act as the primary. Configure and enable HA from the primary 7700 FSP Controller. The enableha command applies settings that have been saved in a configuration file at /usr/local/concerto/etc/ha_precfg.ini.

Note: Changes that are made to network configuration require that HA be disabled, the ha_precfg.ini file needs to be updated, and HA re-enabled. To make changes, use cfghaprecfg.sh to edit the ha_precfg.ini file. For details, see Configuring High Availability on page 108 and Completing the HA Configuration File on page 108.

• Collect the configured and assigned IP addresses for both 7700 FSP Controllers. Inspect local physical interfaces and current IP address assignments using the ifconfig -a command. Use the ethtool command to inspect the current link and interface attributes. The ha_precfg.ini file format provides a single line for each attribute. Apply attributes in the same sequence as the interface is listed:

Note: Typically, 7700 FSP Controller A is the primary and 7700 FSP Controller B is the secondary.

a. sci_ip—This is the Storage Cluster Interface (SCI) IP address; there is an sci0 IP address on each 7700 FSP Controller.

b. ipmi_ip—This is the IPMI or iDRAC IP address that allows virtual control and power management access; this IP address must be accessible from heartbeat_ip and the virtual_ip.

c. interface—This is the Ethernet interface (eth0), and this setting can also list other configured interfaces.

d. heartbeat_ip—This is the heartbeat monitor IP address that is assigned to the server by network IT/network administrator, and is used for monitoring HA availability.

e. virtual_ip—This is the virtual or management IP address assigned to a 7700 FSP Controller (and associated with eth0 before HA is enabled). Once HA is enabled, this IP address is re-assigned to eth0:1 on each 7700 FSP Controller.

f. rep0—This is interface port number configured for or associated with replication (the 7700 FSP storage cluster supports two dedicated replication ports, rep0 and rep1).

g. iSCSI ports—These are the configured iSCSI interface ports (for example, isc0, isc1, isc2, and isc3).

• This following is a sample ha_precfg.ini file for a local storage cluster with SCI ports directly connected with the following attributes:

— a network IP address of 169.254.0.0/24

— a management network IP address of 10.5.4.0/24

— a replication network IP address of 172.16.1.0/24



— an iSCSI network IP address of 192.168.0.0/24

[HA]enabled = truemutual = truepowerControl = ipmiisStretchCluster= false[primary]hostname = controller-asci_ip = 169.254.0.1ipmi_ip = 10.5.4.18interface = eth0,rep0,isc0,isc1,isc2,isc3heartbeat_ip = 10.5.4.21,172.16.1.11,192.168.0.2,192.168.0.4,192.168.0.6,192.168.0.8virtual_ip = 10.5.4.20,172.16.1.10,192.168.0.1,192.168.0.3,192.168.0.5,192.168.0.7quorum = anyquorum_mirror_drive =[secondary]hostname = controller-bsci_ip = 169.254.0.2ipmi_ip = 10.5.4.19interface = eth0,rep0,isc0,isc1,isc2,isc3heartbeat_ip = 10.5.4.23,172.16.1.13,192.168.0.10,192.168.0.12,192.168.0.14,192.168.0.16virtual_ip = 10.5.4.22,172.16.1.12,192.168.0.9,192.168.0.11,192.168.0.13,192.168.0.15quorum = anyquorum_mirror_drive =



The following shows the ha_precfg.ini file; review, inspect, and edit it to prepare for enabling HA from the 7700 FSP Controller (listed as controller-a) by using the setting type examples shown (<in angle brackets>):

• Verify and confirm that a Configuration Repository LUN exists and is shared to each of the 7700 FSP Controllers (collect the A:C:S:L SCSI address for this LUN). A Configuration Repository must be present in the quorum disk on both servers.

If these are not present, use the enableconfigurationrepository CLI command to create the Configuration Repository on both servers. Use the getserverconfiginfo CLI command to verify if the Configuration Repository is enabled (this field is in red) as shown:

[HA]enabled = truemutual = truepowerControl = ipmiisStretchCluster= false[primary]hostname = <controller-a-hostname>sci_ip = <controller-a-sci_ip>ipmi_ip = <controller-a-ipmi_ip>interface = eth0heartbeat_ip = <controller-a-heartbeat_ip>virtual_ip = <controller-a-virtual_ip>quorum = <controller-a-A:C:S:L-configuration-repository>quorum_mirror_drive =[secondary]hostname = <controller-b-hostname>sci_ip = <controller-b-sci_ip>ipmi_ip = <controller-b-ipmi_ip>interface = eth0heartbeat_ip = <controller-b-heartbeat_ip>virtual_ip = <controller-b-virtual_ip>quorum = <controller-b-A:C:S:L-configuration-repository>quorum_mirror_drive =

[root@violin20151 ~]# isscli getserverconfiginfo -s violin20151

Server Name=violin20151

IP Address=10.5.5.237

ID Range=1 - 10000

System Information:

Server Version=Violin Systems Concerto Server v7.6.3.1 - (Build 9271)

Hardware Model=External-Gateway

Manufacturer=Others

O.S. Version=Red Hat Enterprise Linux Server release 6.4 (Santiago)

Kernel Version=Linux 2.6.32-358.23.2.el6.x86_64 #1 SMP Wed Oct 16 18:37:12 UTC 2013 x86_64

Processor=Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz 2599 MHz

...

Memory=387557MB



• Verify there is an installed cfghaprecfg.sh script file.

This shell script file is installed by RPM (and it should reside in /usr/local/concerto/bin/).

• Verify that DNS servers are set up.

Check whether the DNS servers have been set up by using networkconfig.sh getdns CLI command (in /usr/local/concerto/bin/networkconfig.sh), as shown:

If no DNS servers display when you use the networkconfig.sh getdns CLI command, set up the DNS servers by using the commands shown in the following example:

For more information about the networkconfig.sh file, see the latest version Concerto Command Line Reference Guide.

Note: You must ensure that the eth1 IP addresses for MG-A and MG-B are unique so as to avoid any possible IP address conflicts (IP address conflicts may cause the enableha CLI command to fail).

Swap=8197MB

Network Interface=eth0 - mtu 1500 inet 10.5.5.237 mac b8:ca:3a:68:c4:4c

Network Interface=eth1 - mtu 1500 inet 1.0.0.3 mac b8:ca:3a:68:c4:4d

Network Interface=eth2 - mtu 1500 inet 1.0.0.6 mac 0:1b:21:71:ae:e4

Network Interface=eth3 - mtu 1500 inet 1.0.0.7 mac 0:1b:21:71:ae:e5

Network Interface=sci0 - mtu 1500 inet 1.0.0.4 mac b8:ca:3a:68:c4:48

Network Interface=sci1 - mtu 1500 inet 1.0.0.5 mac b8:ca:3a:68:c4:4a

Configuration Repository=Enabled

ID=93

Size(MB)=10240

Mirror=off

guid=3a63157c-56cc-9b4c-ec48-0000540f3cbc

Meta Data Repository=Disabled

FC Target Mode=Enabled

iSCSI=Disabled

BootIP=Disabled

Command: getserverconfiginfo executed successfully.

[root@violin20151 ~]# networkconfig.sh getdns 10.5.0.12 10.5.0.13

[root@violin20151 ~]# networkconfig.sh setappenddomain eng.vmem.intnetworkconfig.sh setdns 10.5.0.12 10.5.0.13



To manually edit the resolv.conf configuration file (in /usr/local/concerto/bin/networkconfig.sh) to add DNS servers, issue the commands shown in the following example:

• Rescan the Memory Gateways if LUNs have been previously created.

If you have already created LUNs, it is recommended that you rescan both of the Memory Gateways before you use the enableha CLI command. Rescan the Memory Gateways by using the following command format (see the rescandevices CLI command example below):

Rescan the devices using the rescandevices CLI command:

Troubleshooting HA Issues

The following table in this section lists some potential errors that could be encountered under specific conditions, describes the error condition, and provides any workarounds to attempt to resolve the HA issues.

[root@viomemm315-mga ~]# cat /etc/resolv.conf

domain eng.vmem.int

search eng.vmem.int eng.vmem.int. vmem.int. violintech.net.

nameserver 10.5.0.12

nameserver 10.5.0.13

isscli rescandevices[-t] [-I][-a <adapter>] [-i <scsi-range>][-l <lun-range> | -r] [-L] [-A] [-k][-X <rpc-timeout>]

isscli rescandevices -X 60

Error Description Workaround/Resolution

Failed to resolve Concerto server to a valid IP address.(0x9022004)

Error condition after issuing enableha CLI command due to the DNS server not properly resolving the server name or was not properly set up.

Workaround: Replace the server name with its IP address.

Heartbeat monitor IP did not get properly set up or is not present.

Error condition after HA was set up when a heartbeat monitor error caused both servers to enter a split-brain condition.

Workaround: Ensure that the heartbeat monitor is present or is reset to its proper values.

No valid heartbeat_ip address was found. Please run cfghaprecfg.sh to modify ha_precfg.ini.(0x0902490d)

Error condition after issuing enableha CLI command that indicates the HA preconfiguration file is invalid, or that heartbeat_ip was not properly initialized by cfghaprecfg.sh.

Workaround: Ensure that you use cfghaprecfg.sh to modify the default ha_precfg.ini file installed by RPM.

Table G.1 Troubleshooting HA CLI Issues


Troubleshooting HA Issues

User authentication failed. Error condition after issuing enableha CLI command due to either an incorrect user login ID or password were used.

Workaround: Verify the user login ID and password and retry. If problem persists, contact the network storage administrator for proper user credentials.

IPMI authentication failed (RPC unspecified error/timeout error).(0x90021000)

Error condition after issuing enableha CLI command due to either an incorrect IPMI login ID or password were used.

Workaround: Verify the IPMI login ID and password and retry. If problem persists, contact the network storage administrator for proper IPMI credentials.

This option is already enabled.(0x80501421)

Error condition after issuing enableha CLI command when HA is currently in an enabled state.

Workaround: No problem occurs if you do issue the enableha CLI command when it is already enabled. To verify the latest system status, use the getserverconfiginfo CLI command, which displays the status of your failover servers, configuration type, failover state, failover suspended, and stretched cluster enabled settings.

QoS is enabled on mg-a, but disabled on mg-b. Must be consistent to set up failover.(0x0902490c)

Error condition after issuing enableha CLI command due to a QoS error that resulted from an operation inconsistently applied to one MG, but not the other in a failover pair.

Workaround: Ensure that the QoS settings in the ipstor.conf file match on both 7700 FSP Controllers.

Invalid configuration for stretched cluster.(0x80501451)

Error condition after issuing enablestretchedcluster CLI command when an invalid configuration was returned.

Workaround: 1) Disable HA and the configuration repository using the disableha and disableconfigurationrepository CLI commands.

2) Enable the configuration repository and mirror using the enableconfigurationrepository and createmirror CLI commands.

3) Enable HA using the enableha CLI command and retry the stretched cluster.

Error Description Workaround/Resolution

Table G.1 Troubleshooting HA CLI Issues(Continued)


APPENDIX H Compliance Information

This appendix contains the following compliance information that supports both the Violin 6000 Series and 7000 Series FSP shelves, as listed below:

• FCC Class A Compliance on page 176

• Regulatory Model Number on page 178

• Electrostatic Discharge (ESD) Precautions on page 181

• Lithium Battery Caution on page 182

• Cabinet Safety Precautions on page 183

• Disposal of Waste Equipment by Users in Private Households in the European Union on page 184

• Perchlorate Material - Special Handling May Apply on page 185

• European Union RFI Statement on page 186

• USA Radio Frequency Interference FCC Notice on page 187

• Japan Radio Frequency Interference VCCI on page 188

• Korea RFI Statement on page 189

• Canada RFI Statement on page 190

• CISPR 22 on page 191

• Australia C-Tick Label on page 192

• Taiwan BSMI Statement on page 193

• Four-in-One Recycling Symbol on page 194

• Product Information for People’s Republic of China on page 195


Appendix H - Compliance Information

FCC Class A Compliance

This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.

This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy, and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case, you are required to correct the interference at your own expense.


Regulatory Information

Regulatory Information

For your protection, this product has been tested for conformance to various national and international regulations and standards. The scope of this regulatory testing includes electrical and mechanical safety, electromagnetic emissions, immunity, acoustics and hazardous materials.



Regulatory Model Number

For the purpose of regulatory compliance certifications and identification, this product is assigned a Violin Systems regulatory model number. This number is found on the product label, along with the required approval markings and information. When requesting certification information for this product, always refer to this regulatory model number.

Note: Do not confuse the regulatory model number with the marketing or model number.


Installation Conditions

Installation Conditions

See installation instructions before connecting this equipment to the input supply.

WARNING! The equipment must be provided with a proper AC protective earth (PE) ground connection.



Network Connected Equipment

WARNING! The installation must provide a ground connection for the network equipment.


Electrostatic Discharge (ESD) Precautions

Electrostatic Discharge (ESD) Precautions

When handling any electronic component or assembly, you must observe the following antistatic precautions to prevent damage. An ESD kit (P/N A3024-80004) is available (or supplied with memory additions). This kit contains one wrist strap, one conductive sheet, and one antistatic foam pad.

• Always disconnect power from the server and wear a grounded wrist strap when working around the server.

• Always wear a grounded wrist strap when handling printed circuit boards.

• Treat all assemblies, components and interface connections as static-sensitive.

• Avoid working in carpeted areas, and keep body movement to a minimum while removing or installing boards, to minimize buildup of static charge.



Lithium Battery Caution

WARNING! Observe the correct polarity when changing the lithium battery. There is a danger of explosion if battery is installed incorrectly.

Replace only with the same or equivalent type recommended by the manufacturer. Dispose of used batteries according to the manufacturer’s instructions and local disposal requirements.

Note: Switzerland: Annex 4.10 of SR 814.013 applies to batteries.


Cabinet Safety Precautions

Cabinet Safety Precautions

WARNING! Cabinets are heavy even when empty. Exercise caution when moving cabinets whether equipment is installed in the cabinet or not. Avoid rolling cabinets on rough or uneven surfaces or inclines greater than 10 degrees. Unloading cabinets from the pallet and movement of cabinets should be performed by at least two people.

Slidable products are not to be extended from the cabinet while the equipment is on the shipping pallet. The cabinet must be unloaded from the pallet and all anti-tip devices properly installed prior to extending any slidable product.

Once installed, all anti-tip devices must remain in place to maintain stability. Only one slidable product must be extended at a time.

Failure to follow these precautions can result in damage to equipment or injury to personnel.



Disposal of Waste Equipment by Users in Private Households in the European Union

This symbol on the product or on its packaging indicates that this product must not be disposed of with your other household waste. Instead, it is your responsibility to dispose of your waste equipment by handing it over to a designated collection point for the recycling of waste electrical and electronic equipment. The separate collection and

recycling of your waste equipment at the time of disposal will help to conserve natural resources and ensure that it is recycled in a manner that protects human health and the environment. For more information about where you can drop off your waste equipment for recycling, please contact your local city office, your household waste disposal service or the shop where you purchased the product.


Perchlorate Material - Special Handling May Apply

Perchlorate Material - Special Handling May Apply

See http://www.dtsc.ca.gov/hazardouswaste/perchlorate.

This product may include a real-time clock battery or coin cell battery that may contain perchlorate and may require special handling when recycled or disposed of in California. Refer to the product user documentation to determine if this product contains batteries, and if so, the battery type(s) that are used.


http://www.dtsc.ca.gov/hazardouswaste/perchlorate


European Union RFI Statement

This is a Class A product. In a domestic environment, this product may cause radio interference in which case the user may be required to take adequate measures.


USA Radio Frequency Interference FCC Notice

USA Radio Frequency Interference FCC Notice

This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense.

The user is cautioned that changes or modifications not expressly approved by Violin Systems could result in the equipment being noncompliant with FCC Class A requirements and void the user’s authority to operate the equipment.



Japan Radio Frequency Interference VCCI


Korea RFI Statement

Korea RFI Statement



Canada RFI Statement

This Class A digital apparatus complies with Canadian ICES-003.

Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada.


CISPR 22

CISPR 22

WARNING! This is a class A product. In a domestic environment, this product may cause radio interference, in which case, the user may be required to take adequate remedial measures.



Australia C-Tick Label


Taiwan BSMI Statement

Taiwan BSMI Statement



Four-in-One Recycling Symbol


Product Information for People’s Republic of China

Product Information for People’s Republic of China


Index

Numerics6000 Series

shelf compliance information 175

7000 Series FSPs7300/7300E FSP compliance information 175

7700 Flash Storage Platformalso known as 7700 FSP 7component terms and description 7connectivity overview 24physical cabling requirements 19reference documents 3system components 9terminology 7

7700 FSP Controller 57configuring at initial power on 59configuring Fibre Channel target and initiator ports for

failover 90configuring iSCSI target and initiator ports for failover

91enabling callhome 95front and rear panel components and LEDs 118LEDs, connectors, and panel components 118panel components and descriptions 118power supply LED states 120two methods of management access 57verifying iDRAC interfaces to ensure connectivity 61VGA setup and SSH connections for IPMI/iDRAC ac-

cess to Quick Start utility 57VGA setup for IPMI/iDRAC access to Quick Start utility

57

7700 FSP Controllersperforming initial set up on 60using CLI to configure SCI setup 63using CLI to set hostname, DNS, NTP, and domain

name 62using Symphony to configure and enable HA 67using Symphony to create a SAN client and a LUN as

a configuration repository 65using Symphony to create and enable a configuration

repository 66using Symphony to set up SAN clients and LUNs 65

AACM configuration

commands to complete 97

ACSL valuesMemory Gateways 103

allocating storage spaceMemory Gateways 101

arrays6000 Series (6600/6200/6100) 8

Bbefore contacting Support

gather product and support issue information 5best practices

allocating space for a storage pool (standard and ded-up pools) 52

Brocade 6510configuring and setting up for use with a 7700 FSP 67,

139performing switch preconfiguration 139setting the hostname and network services on this FC

switch 140

Ccable connections

6000 Series and 7000 Series FSP cable ports and slots29

cable label format7700 FSP cluster devices 12

callhomeenabling for Memory Gateways (manual) 95

caution icons 4client network switches

all network paths and ports used for iSCSI must sup-port jumbo frames (MTU 9000) 41

configuring iSCSI ports in an northbound zone configu-ration 80

configuring the northbound path from 7700 FSP Con-trollers 79

northbound switch must support NPIV 40

complianceAustralia C-Tick label 192cabinet safety precautions 183Canada RFI statement 190


CISPR 22 warning 191ESD precautions 181European Union (EU) RFI statement 186FCC Class A 176FCC radio frequency interference (RFI) 187four-in-one recycling symbol 194installation conditions 179Japan RFI (VCCI) 188Korea RFI statement 189lithium battery caution 182network connected equipment 180perchlorate material (special handling) 185product information for People’s Republic of China

195regulatory information 177regulatory model number 178Taiwan BSMI statement 193waste equipment disposal EU 184

compliance information7700 FSP cluster shelves (7000 Series FSP and 6000

Series) 175

componentterminology 7

configuration checklist6000 Series array 137700 FSP Controller 15Brocade 6510 Fibre Channel switch 15Violin Systems Symphony 16

Configuration Repositoriesenabling both on Memory Gateways 104

configuring6000 Series array 517000 Series FSP storage shelves 527700 FSP Controller 567700 FSP storage shelves 51Memory Gateways 94

configuring 7700 FSP Controllersat initial power on 59

configuring management access7700 FSP Controllers 60

configuring storage7000 Series FSP (manual) 98

configuring the 7000 Series FSPmanual set up procedures 94

creatingstorage pools on Memory Gateways 103

Ddedup storage pool planning

best practice guides 52

deduplicationenabling 110

Ee-mail alert settings

enabling for Memory Gateways (manual) 95

enablingcallhome and e-mail alert setting for Memory Gateways

95Configuration Repositories on both Memory Gateways

104

enabling callhomefor 7700 FSP Controllers 95for Memory Gateways 95

Ffailover

setting up HA 108

FC target portsautomatically configured and associated with HBA

slots 4 and 5 (verify using Symphony) 80

Fibre Channelrear panel slot, port, and connector locations 26, 27

Fibre Channel switchesconfiguring FC ports 90

Flash Storage PlatformsFSPs 8

HHA

completing configuration file for Memory Gateways108

configuring and cfghaprecfg.sh 108enabling and disabling using CLI commands 167enabling high availability between Memory Gateways

110high availability 167troubleshooting HA issues 172verifying the prerequisites 167

HBA ports and slots6000 Series and 7000 Series FSP (Fibre Channel) 29

high availabilityconfiguring 108setting up 108–110

IiDRAC

inspecting 7700 FSP Controller status 121monitoring 7700 FSP Controller 120Recent Logged Events pane showing severity, date

and time, and descriptions of recent logged events122

Server Health pane showing current 7700 FSP Control-ler status categories 121

Server Information pane, 7700 FSP Controller informa-tion 121

setting up and verifying time zones and NTP for 7700


FSP Controllers 123setting up DNS and domain names used by 7700 FSP

Controllers 123setting up SNMP e-mail alerts for 7700 FSP Controllers

123System Summary page 121

initial set up7700 FSP Controllers 60

iSCSIabout client names and commands 84adding an iSCSI client user with CHAP authentication

85adding an iSCSI client with a valid initiator name 84adding an iSCSI client with CHAP authentication en-

abled 86adding an iSCSI target under an existing iSCSI target

88assigning LUNs to an existing iSCSI target 89client authentication parameter options 84client command parameter options 84configuring clients, targets, and LUNs 83confirming iSCSI support is enabled on 7700 FSP Con-

trollers 83enabled CHAP authentication on an existing client 86locating an initiator name for an iSCSI client 84options for add an iSCSI user with CHAP authentica-

tion 86

iSCSI target portsmanually configured and associated with HBA slots 4

and 5 (verify using Symphony) 80

LLUN types

overview 55

MMemory Gateways

configuring 94configuring network (manual) 94configuring replication ports (manual) 95configuring the mail server for log upload (manual) 95enabling callhome 95powering on (manual) 94rescanning devices assigned 106troubleshooting tips 112

Nnetwork interface cable ports

7000 Series FSP and 6000 Series arrays 31

northboundconfiguring northbound path from 7700 FSP Control-

lers to client network 80configuring northbound switches 79

confirm FC ports on 7700 FSP Controller as targets fornorthbound connectivity 80

confirm iSCSI ports on 7700 FSP Controller as targetsfor northbound connectivity 80

northbound connectionscable connections between 7700 FSP Controller-client

network switch 10connecting northbound Fibre Channel cables (7700

FSP Controller-client network switch) 40connecting northbound Fibre Channel ports 40connecting northbound iSCSI cables (7700 FSP Con-

troller-client network switch) 40Fibre Channel cable connections 40iSCSI cable connections 40

NPIVN_Port ID Virtualization support required on north-

bound switch for multiple FC initiators on a singleport 40

Ooptical cables

type and usage in 7700 FSP 20

Pplanning storage pools

best practices and details 52

ports-cable connectionsFC switch-to-controller and FC switch-to-shelf 12

power cordsIEC 320 C19 plugs for shelf and for data center power

strip 42

power requirements7000 Series FSP/6000 Series arrays 42

power up sequence7000 Series FSP/6000 Series arrays 42

powering on7000 Series FSP/6000 Series arrays 427700 FSP Controllers 43Brocade Fibre Channel switches 43

Rreference documents

7700 Flash Storage Platform 3replication

7700 FSP Controller preparation 126active and desired LAN-WAN speeds, usage, and

bandwidth limits 127adding LUNs 133configuring interfaces using CLI commands 129configuring network interfaces to support this feature

125connecting cables on 7000 Series FSP 32


creating a replication policy for a LUN 133creating a snapshot resource 133in an HA environment 135only supported in 7700 FSP system with a 7000 Series

FSP installed 32overview 125performance and TCP ports 127prerequisites, tools, and skills 126site-to-site information (host, IP address, subnet mask,

bitmask, network ID, and gateway to replicationpartner) 128

using Symphony to configure 133viewing replication data 134

replication operationsTCP ports used 127

rescanningverifying the state of Memory Gateway devices 106

Ssafety icons

describe warnings, cautions, and notes 4setting up

management access 57

setup and configurationtask list for setting up and configuring a 7700 FSP 12

shelf6000 Series and 7000 Series FSP shelf overview 29

Simple SetUpconfiguring 7000 Series FSPs (7300/7300E) 50creating a .cfg file for automatically configuring multiple

7000 Series FSPs 52

site informationdevice configuration, rack space, power, and cooling

information for the 7700 FSP 17

slot number-port numberdefines specific slot and port number reference 40

southboundSymphony can identify FC or iSCSI ports designated

as targets for southbound connectivity 80

southbound cableslabel formats define cable and device connections 34

southbound connectionsconnecting cables to southbound storage device ports

33

southbound ports7700 FSP Controller rear panel slots 4 and 5 33

status LEDs7700 FSP Controller power supplies 120

storageallocating space 101before configuring, refer to storage best practices 98configuring 98

storage clusterFibre Channel and iSCSI connections in SAN environ-

ment 10stretched cluster configuration 10

storage poolsbest practices 54creating on Memory Gateways 103guidelines for Memory Gateways on a 7000 Series

FSP shelf 54setting up for deduplication 111verifying 105–107verifying before enabling HA 105

storage space allocationcreating storage pools on Memory Gateways 101

stretched clusterchecking failover status 152configuration tasks 148creating a Configuration Repository and mirror on site-

A 151creating a Configuration Repository and mirror on site-

B 151creating local and remote storage pools on site-A 150creating local and remote storage pools on site-B 151disabling target mode on back-end ports 149enabling HA 151identifying front-end and back-end ports on 7700 FSP

Controllers 149inspecting discovered devices (collecting new and cur-

rent device information) 149networking and Tiebreaker requirements 147overview and description 145renaming LUNs and minimum stretched cluster LUN

requirements 149storage and zoning requirements 146

Symphonyadding 7700 FSP Controllers to a stretched cluster

configuration (Symphony Help) 54adding a shelf to a stretched cluster configuration

(Symphony Help) 54adding devices to a stretched cluster 53adding standalone or storage cluster devices to Sym-

phony 53creating and managing LUNs on a shelf (Symphony

Help) 55creating and managing SAN clients (Symphony Help)

56creating and managing storage pools (Symphony

Help) 54display HBA information for shelf or 7700 FSP Control-

ler 72installing and accessing Violin Symphony 143overview of stretched cluster configurations (Sympho-

ny Help) 53specifying the device types you add 53transferring zone configuration to FC switches 73types of devices to add 53using to configure and manage a 7700 FSP devices

52

TTCP

ports used for replication operations 127


technical supportViolin Systems Support contact information 5

terminology7700 Flash Storage Platform 7

Tiebreakerconfiguration field definitions 159downloading installation file 153installing and configuring Tiebreaker on a 7700 FSP

Controller 155installing and configuring to monitor 7700 FSP Control-

ler failovers 152installing the Tiebreaker image on a virtual machine

153installing the Tiebreaker image on an independent

server 154modifying a Tiebreaker configuration 160requirements 152resuming Tiebreaker monitoring of failover 161sample traps sent by Tiebreaker 161setting up Tiebreaker using the CLI 162status field definitions 158using Tiebreaker commands 157

troubleshootingdetermine IP addresses of internal Memory Gateways

(1 known, 1 unknown) 113determine IP addresses of internal Memory Gateways

(both unknown) 114Memory gateway error messages 115

Uupgrading

7700 FSP Controllers and 7000 Series FSP storageshelves 51

using CLIconfiguring SCI setup on 7700 FSP Controllers 63setting hostname, DNS, NTP, and domain name on

7700 FSP Controllers 62

VViolin Symphony

default login credentials 144installing GUI management tool 143launching and logging in 143

Violin Systems Supportmethods for contacting Support for assistance (tele-

phone, e-mail, and website) 5

Wwarning icons 4

Zzone configuration

copying into a replacement FC switch 75
