Invista with Brocade Configuration v.1 - Dell...

Invista Installation and Configuration Procedures with Brocade 7420 Multi-Protocol Routers

EMC Proven™ Professional Knowledge Sharing September, 2007

Adam Jones Senior Technology Consultant

EMC Corporation [email protected]

2

Table of Contents

1 OVERVIEW ............................................................................................................................4

2 COMPONENT LAYOUT AND CABLING ...............................................................................5

2.1 IP SWITCH COMPONENT LAYOUT .........................................................................................5 2.2 MULTI-PROTOCOL ROUTER COMPONENT LAYOUT.................................................................5 2.3 CPC COMPONENT LAYOUT ..................................................................................................5 2.4 IP SWITCH PORT MAPPINGS ................................................................................................6

3 CPC INITIAL CONFIGURATION............................................................................................7

3.1 PPP/RAS CONNECTION CONFIGURATION ..............................................................................7 3.2 SP CONFIGURATION............................................................................................................7

4 CPC FINAL CONFIGURATION............................................................................................10

4.1 INITIAL INSTANCE LOGIN ...................................................................................................10 4.2 INVISTA CPC CODE UPGRADE............................................................................................11 4.3 INVISTA CPC CODE COMMIT ..............................................................................................17

5 IP SWITCH INITIAL CONFIGURATION...............................................................................20

5.1 CONSOLE CONNECTION CONFIGURATION...........................................................................20 5.2 IP SWITCH MAIN CONFIGURATION ......................................................................................21

6 IP SWITCH FINAL CONFIGURATION.................................................................................23

6.1 EMCREMOTE CONFIGURATION ..........................................................................................23 6.2 IP SWITCH CONFIGURATION SCRIPT ..................................................................................24

7 FC ROUTER CONFIGURATION .........................................................................................27

7.1 CONSOLE CONNECTION CONFIGURATION...........................................................................27 7.2 FC ROUTER MAIN CONFIGURATION ....................................................................................28 7.3 FC ROUTER LICENSE ADDITION..........................................................................................30 7.4 FC ROUTER SNMP CONFIGURATION ...................................................................................31

8 FC ROUTER OPERATING SYSTEM UPGRADE................................................................33

8.1 FTP CONFIGURATION........................................................................................................33 8.2 XPATH OS AND SAS UPGRADE ...........................................................................................35

9 SAL AGENT INSTALLATION FROM CPC TO DPC ............................................................37

9.1 EMCREMOTE CONFIGURATION ..........................................................................................37 9.2 SAL AGENT CONFIGURATION SCRIPT .................................................................................38

10 SAL AGENT PROCESS MONITORING ..............................................................................39

11 CONFIRMING WWN BLOCK...............................................................................................40

3

12 NETWORK TIME PROTOCOL (NTP) CONFIGURATION...................................................40

12.1 IP SWITCH NTP CONFIGURATION........................................................................................40 12.2 FC ROUTER NTP CONFIGURATION......................................................................................42 12.3 CPC NTP CONFIGURATION.................................................................................................43

13 IMPORTING DPC (BROCADE 7420 MPR) INTO THE CPC ...............................................45

14 PERFORMING INVISTA TO BACK-END STORAGE ZONING ...........................................53

14.1 ZONE ALIASES..................................................................................................................53 14.2 ZONING............................................................................................................................56 14.3 ZONE CONFIGURATION .....................................................................................................58

15 CLARIION BACK-END CONFIGURATION..........................................................................61

15.1 INITIATOR CONFIGURATION ...............................................................................................61 15.2 RAID GROUP CONFIGURATION...........................................................................................67 15.3 BIND LUN CONFIGURATION................................................................................................71 15.4 STORAGE GROUP CONFIGURATION....................................................................................72 15.5 LUN/HOST ASSIGNMENT....................................................................................................74

16 SYMMETRIX BACK-END CONFIGURATION .....................................................................78

16.1 SYMMETRIX META DEVICE CREATION.................................................................................78 16.2 SYMMETRIX META DEVICE FA MAPPING..............................................................................78 16.3 SYMMETRIX META DEVICE AND FA MAPPING CONFIGURATION .............................................79 16.4 SYMMETRIX META DEVICE AND FA MAPPING CONFIRMATION ...............................................80 16.5 SYMMETRIX FA MAPPING ADDRESS CONFIRMATION ............................................................83 16.6 SYMMETRIX META DEVICE MASKING ..................................................................................83

17 INVISTA STORAGE IMPORTING........................................................................................86

18 INVISTA VIRTUAL VOLUME CREATION............................................................................90

19 INVISTA VIRTUAL FRAME CREATION ..............................................................................93

20 INVISTA HOST CONNECTIVITY.........................................................................................95

21 VIRTUAL FRAME RESOURCE ALLOCATION....................................................................98

22 INVISTA CLONE OPERATIONS........................................................................................103

22.1 CLONE GROUP CONFIGURATION......................................................................................103 22.2 ADDING CLONES.............................................................................................................105 22.3 CLONE FRACTURING.......................................................................................................107 22.4 CLONE SYNCHRONIZATION..............................................................................................108

23 CPC .MIF FILE CONFIGURATION REBUILD ...................................................................111

23.1 CONSOLE CONNECTION CONFIGURATION.........................................................................111 23.2 INITIAL CPC PREPARATION ..............................................................................................112 23.3 LAN SERVICE PORT CONFIGURATION ...............................................................................116 23.4 CPC .MIF FILE FTP TRANSFER..........................................................................................116 23.5 CPC .MIF FILE TRANSFER FROM RAM DISK TO THE IMAGE REPOSITORY..............................117 23.6 IMAGE INSTALLATION......................................................................................................118 23.7 INVALIDATE DATA DIRECTORY .........................................................................................120

24 CPC INITIAL CONFIGURATION........................................................................................122

4

24.1 PPP/RAS CONNECTION CONFIGURATION ..........................................................................122 24.2 SP CONFIGURATION........................................................................................................122

25 USING THE RECOVERY KERNEL TO INSTALL THE XPATH BASE FIRMWARE..........125

25.1 CONSOLE CONNECTION CONFIGURATION.........................................................................125 25.2 RECOVERY KERNEL FILE SYSTEM PREPARATION ..............................................................126 25.3 FTP CONFIGURATION......................................................................................................127 25.4 XPATH DOWNLOAD AND INSTALLATION ............................................................................127 25.5 FC ROUTER MAIN CONFIGURATION ..................................................................................128 25.6 FC ROUTER LICENSE ADDITION........................................................................................130 25.7 FC ROUTER SNMP CONFIGURATION .................................................................................131

APPENDIX A SETTING UP A SERVICE LAPTOP CONNECTION TO AN INVISTA SP ...............................133

Disclaimer: The views, processes or methodologies published in this compilation are those of the author. They do not necessarily reflect EMC Corporation’s views, processes or methodologies.

5

1 – Overview This article will outline the procedures for setting up an Invista environment utilizing Brocade 7420 Multi-Protocol Routers. The procedure will review all of the steps necessary to cable and configure the CPCs, IP Switches and Brocade 7420 Multi-Protocol Routers (DPCs) to integrate into a Symmetrix® and CLARiiON® storage environment. I have included procedures to build out the CPCs from scratch with the Invista .mif file and also how to recover the Brocade 7420 Multi-Protocol Routers from the Recovery Kernel. We used the following equipment for this procedure:

• 2 Invista CPC’s running Code Level 1.0 – SP2 • 2 Allied Telesyn AT-8948 IP Switches running Code Level 2.7.3-00 • 2 Brocade 7420 Multi-Protocol Routers running Code Level 7.4.1 and SAS Code

Level 2.1.3h • 1 Symmetrix DMX800 running Microcode Release 5671.54.59 • 1 CLARiiON CX600 running FLARE Code Level 2.19.600.5.007 • 1 Windows 2003 Server (SP1) with 2 QLogic QLA2342 HBA’s running Code

Level 9.1.4.15 (Driver), 1.52 (BIOS) and 3.03.21 (Firmware) The illustration on the following page illustrates the Fibre Channel and Ethernet relationships between the Invista components and the Storage/Host elements.

6

2 – Component Layout and Cabling

1. Please refer to the component drawings below in section 2.1 – 2.3 to become familiar with the equipment and port layout.

7

2.1 - IP Switch Component Layout

2.2 - Multi-Protocol Router Component Layout

2.3 - CPC Component Layout

2.4 – IP Switch Port Mappings

8

2. The picture below shows the IP Switch ports used for the Invista configuration. Please refer to the red dots on the IP Switch picture and the mapping table below to gain a thorough understanding of the device/port mappings.

AT-8948 Switch 1 Ports Destination Hardware Port 01 External Network Port 03 AT-8948 Switch 2 - Port 03 Port 05 CPC - SP A Port 09 AP-7420 - DPC 1 MGMT 1 Port 19 AT-8948 Switch 2 - Port 19 Port 25 AP-7420 - DPC 1 MGMT 2 AT-8948 Switch 2 Ports Destination Hardware Port 01 External Network Port 03 AT-8948 Switch 1 - Port 03 Port 07 CPC - SP B Port 11 AP-7420 - DPC 2 MGMT 1 Port 19 AT-8948 Switch 1 - Port 19 Port 27 AP-7420 - DPC 2 MGMT 2

3 - CPC Initial Configuration

3.1 – PPP/RAS Connection Configuration

9

1. Create a PPP/RAS Connection as outlined in Appendix A on pages 133-134 if unfamiliar with the connection creation process. Once created, double click on the Shortcut to launch the connection.

2. Provide the proper login credentials (Username = clarion – Password = clarion!) and select the “Connect” icon.

3.2 – SP Configuration

3. Open a Web Browser page and enter https://192.168.1.1/setup to launch the Storage Processor (SP) Configuration Utility.

https://192.168.1.1/setup

10

4. Select “Yes” on the Security Alert to continue.

5. Enter the IP Address, Hostname, Subnet Mask, Gateway, Peer IP Address (SPB) and select “Apply Settings” to commit the configuration.

11

6. You should now be at the Configuration Summary screen. Allow the SP several minutes to reboot until proceeding forward. Next, complete steps 1-6 again to configure SP B.

12

4 - CPC Final Configuration

4.1 – Initial Instance Login

1. Open a Web Browser page and enter the CPC – SP A IP Address to launch the Invista Element Manager. You do not need to check mark “Enable NAT Support” since we are utilizing the Non-Firewall configuration.

2. Enter the login credentials (Username = admin – Password = password) and select the OK icon to continue.

13

3. You should now be in the main Invista Element Manager interface.

4.2 - Invista CPC Code Upgrade

4. Run the key combination “Ctrl + Shift + F12” within Invista Element Manager to enter Engineering Mode. The Engineering Mode password is “invEngineer”.

14

5. While in Engineering Mode, select the Software tab to review the software code currently installed and confirm the Active/Not Active status.

6. Right click on the Invista Instance Serial Number, go to Software Operations and select Software Installation Wizard to start the process of installing software code on the Invista Instance.

15

7. Select Next while in the Control Path Cluster (CPC) Software Installation dialog to continue.

16

8. At this point, a rules check will be conducted to verify the health of the Invista Instance. If the Instance passes the health check, select Next to continue.

9. Select the Browse icon under the Software to Install text to locate new Invista packages on the Service Laptop. This upgrade will include Invista-Storage-Virtualization-Services and Invista License Enablers. The License Enablers installation will be performed after this upgrade.

17

10. Select the appropriate Invista packages to install, then select Next to continue.

11. Verify the following summary and select Next to continue.

18

12. The dialog will summarize the Invista packages you have selected to install. Once the review is complete, select Next to continue.

19

13. All installation checks have been performed at this point. Select Next to continue the installation.

14. The Software Operation Progress History dialog will now appear and update the progress of the installation as it progresses.

20

15. A green check mark will be displayed by each task as it successfully completes. The upgrade process is now complete. Select the OK icon to close the dialog screen.

4.3 - Invista CPC Code Commit

16. Right click on the Invista Instance and select Edit Properties to open the Invista Instance Properties window.

21

17. Highlight the Software Packages you previously installed and select the Commit icon to commit the software.

18. You will be brought to the Control Path Cluster Properties window that will have you confirm the Software Package you are about to commit.

22

19. The Invista-Storage-Virtualization-Services Package has now been successfully

installed. Next, go through steps 6 – 19 again to install the Invista License Enablers separately.

23

20. Review the Invista-Storage-Virtualization-Services Package under the Software Tab of the Invista Instance Properties window. The package should now have an Active status.

5 - IP Switch Initial Configuration

5.1 – Console Connection Configuration

1. Open a HyperTerminal session to configure, enter the session name and select the OK icon to continue.

24

2. Select the proper COM Port. In this example, it happens to be the COM1 Serial Port.

3. Select the COM1 Properties for this device (Bits per second = 9600, Data bits = 8, Parity = None, Stop bits = 1 and Flow control = Hardware).

25

5.2 – IP Switch Main Configuration

4. Once in the console window, run “show file” as listed below to ensure that the ipsw1ini.cfg configuration file is present from the factory.

Manager EMC-FW1> show file Filename Device Size Created Locks ------------------------------------------------------------------------- 89-273.rez flash 4260300 22-Nov-2005 23:51:56 0 89-273a.hlp flash 184849 22-Nov-2005 23:52:53 0 boot.cfg flash 2218 22-Nov-2005 23:56:39 0 config.ins flash 32 10-Jun-2006 05:15:11 0 emc-fw1.cfg flash 8789 16-Jun-2006 12:41:08 0 emc-nfw1.cfg flash 3448 10-Jun-2006 05:14:59 0 emcboot.cfg flash 164 22-Nov-2005 23:52:59 0 emc_tmp1.cfg flash 7965 09-Jun-2006 07:33:04 0 emc_tmp2.cfg flash 3449 09-Jun-2006 07:33:04 0 emc_tmp2.scp flash 68 09-Jun-2006 07:33:04 0 emc_tmp3.scp flash 14 09-Jun-2006 07:33:04 0 emc_tmp4.scp flash 68 09-Jun-2006 07:33:04 0 emc_tmp5.scp flash 14 09-Jun-2006 07:33:03 0 feature.lic flash 39 22-Nov-2005 23:53:29 0 gwd.scp flash 14 10-Jun-2006 05:14:59 0 gwu.scp flash 68 10-Jun-2006 05:14:59 0 ipsw1ini.cfg flash 553 22-Nov-2005 23:52:55 0 ipsw2ini.cfg flash 553 22-Nov-2005 23:52:57 0

26

--More-- � (<space> = next page, <CR> = one line, C = continuous, Q = quit) [2K longname.lfn flash 17 22-Nov-2005 23:53:27 0 pmdn.scp flash 14 10-Jun-2006 05:14:58 0 pmup.scp flash 68 10-Jun-2006 05:14:58 0 prefer.ins flash 64 22-Nov-2005 23:53:07 0 release.lic flash 32 22-Nov-2005 23:53:06 0 snmpengn.sec flash 40 30-Nov-2006 16:50:07 0 config.ins nvs 32 10-Jun-2006 05:15:04 0 random.rnd nvs 3904 30-Nov-2006 17:09:07 0

5. Run “set config=ipsw1ini.cfg” to set this configuration file as the Boot Configuration File.

Manager EMC-FW1> set config=ipsw1ini.cfg Info (1049003): Operation successful.

6. Run “show config” to confirm that ipsw1ini.cfg is the Boot Configuration File. You will notice that emc-fw1.cfg is still the Current Configuration File. The IP Switch must be restarted to change the Current Configuration status.

Manager EMC-FW1> show config Boot configuration file: flash:ipsw1ini.cfg (exists) Current configuration: flash:emc-fw1.cfg

7. Run “restart switch” to restart the IP Switch. Manager EMC-FW1> restart switch INFO: Initialising Flash File System. INFO: IGMP packet trapping is active for IGMP snooping, L3FILT is activated INFO: Executing configuration script <flash:ipsw1ini.cfg> INFO: Switch startup complete

8. Once at the login screen, type the login credentials (Username = manager – Password = EMC2wil).

login: manager Password: EMC2wil

9. Run “show config” to confirm that ipsw1ini.cfg is the Boot Configuration File along with the Current Configuration File.

Manager > show config Boot configuration file: flash:ipsw1ini.cfg (exists) Current configuration: flash:ipsw1ini.cfg

10. Perform steps 4-9 for the second IP Switch in the Invista Instance.

27

6 - IP Switch Final Configuration

6.1 - EMCRemote Configuration

1. Launch the EMCRemote Dialer to connect to CPC – SP A. Enter the CPC – SP A IP Address and login credentials (Username = clariion – Password = clariion!).

2. Once at the SP Login screen, type the login credentials (Username = clariion – Password = clariion!).

28

6.2 - IP Switch Configuration Script

3. Once in Windows XP Embedded, go to a DOS prompt and change directories to C:\EMC\base\<install_dir>\msgbin.

4. We are first going to configure IP Switch 2. Run “configipsw.pl –prompt –write

IP_Switch2 -configure 2” to start the script to configure the IP Switch and write the configuration to a file. Note: All script input is highlighted in red text below.

C:\EMC\Base\10042000.002\msgbin> configipsw.pl –prompt –write IP_Switch2 -configure 2 Configure which switch? (2, 1, both) [default is 2]: 2 Current IP Address of IP Switch 2 (IP address): 192.168.10.3 Configure for how many FibreChannel Switches? (2, 4, 1) [default is 2]: 2 Do you want to change any of the following internal subnet addresses or masks? These are used in Cisco MDS environments for both firewall and non-firewall based configurations. FibreChannel Switch 1 control path subnet: 192.168.11.0 FibreChannel Switch 1 control path network mask in 255.255.255.0

29

FibreChannel Switch 2 control path subnet: 192.168.12.0 FibreChannel Switch 2 control path network mask in 255.255.255.0 (Yes, No) [default is No]: n External Network subnet address (IP address): 10.5.80.0 External Network subnet mask (IP address): 255.255.255.0 External Network gateway (IP address): 10.5.80.1 External Network NTP server address (optional IP address): IP Switch 1 address on the external network (IP address): 10.5.80.132 IP Switch 2 address on the external network (IP address): 10.5.80.133 SP-A address on the external network (IP address): 10.5.80.130 SP-B address on the external network (IP address): 10.5.80.131 FibreChannel Switch 1 address on the external network (IP address): 10.5.80.136 FibreChannel Switch 2 address on the external network (IP address): 10.5.80.139 Generating configuration files... Configuration files generated. Enter password for IP Switch Admin Account: EMC2wil Connecting to 192.168.10.3... Removing prior temporary files... done Saving original configuration... done Transferred files: Transferred emc-nfw2.cfg Transferred dnnet1.scp Transferred emc-fw2.cfg Transferred upnet1.scp Transfer: done Setting new configuration... done Restarting switch... done Configuration of 192.168.10.3 complete. IP Switch Write Configuration Example

30

5. We are now going to configure IP Switch 1. Run “configipsw.pl –read IP_Switch2 -configure 1” to start the script to configure the IP Switch. The read option will read from the configuration file created while configuring IP Switch 2. Note: All script input is highlighted in red text below.

C:\EMC\Base\10042000.002\msgbin> configipsw.pl –read IP_Switch2 -configure 1 Generating configuration files... Configuration files generated. Enter password for IP Switch Admin Account: ******* Connecting to 192.168.10.2 Removing prior temporary files... done Saving original configuration... done Transferring files: Transferred pmdn.scp Transferred pmup.scp Transferred gwu.scp Transferred gwd.scp Transferred emc-nfw1.cfg Transferred emc-fw1.cfg Transfer: done Setting new configuration... done Restarting switch... done Configuration of 192.168.10.2 complete.

31

IP Switch Read Configuration Example

32

7 - FC Router Configuration


1. Open a HyperTerminal session to configure, enter the session name and select the OK icon to continue.


33

3. Select the COM1 Properties for this device (Bits per second = 9600, Data bits = 8, Parity = None, Stop bits = 1 and Flow control = None).

7.2 – FC Router Main Configuration

34

4. Once in the console window, you will be brought into the factory default router

initialization dialog. Type the initial factory login credentials (Username = admin – Password = password). You will then be prompted to change the root, admin and user passwords to a new one. Please change all of them to the Invista standard password of Serv4EMC. Note: All script input is highlighted in red text below.

login: admin Password: password Please change the system passwords now. Use Control-C to exit or press 'Enter' key to proceed. Change password for user: root New password: Serv4EMC Retype new password: Serv4EMC Changed password for user: root. Change password for user: admin New password: Serv4EMC Retype new password: Serv4EMC Changed password for user: admin. Change password for user: user New password: Serv4EMC Retype new password: Serv4EMC Changed password for user: user. Please remember to config time zone for the switch

5. Run “ipaddrset 1 -i 10.5.80.134 -n 255.255.255.0 -g 10.5.80.1 -a cfgnow” to configure the IP Address, Subnet Mask and Default Gateway for Management Interface 1.

MP Router:admin> ipaddrset 1 -i 10.5.80.134 -n 255.255.255.0 -g 10.5.80.1 -a cfgnow Management Ethernet interface configuration for port 1 is set The switch virtual ip is set


MP Router:admin> ipaddrset 2 -i 10.5.80.135 -n 255.255.255.0 -g 10.5.80.1 -a cfgnow Set the switch virtual ip as well (yes, y, no, n): y Management ethernet interface configuration for port 2 is set The switch virtual ip is set

35

7. Run “svipaddrset -i 10.5.80.136 -n 255.255.255.0 -a cfgnow” to configure the IP

Address, Subnet Mask and Default Gateway for Virtual Interface 1. All IP access to this router will be accessed through this address.

MP Router:admin> svipaddrset -i 10.5.80.136 -n 255.255.255.0 -a cfgnow The virtual IP configuration of the switch is set

8. Run “ipaddrshow” to confirm the configuration results from steps 5-6. MP Router:admin> ipaddrshow MGMT 1 Configuration Current IP Address 10.5.80.134 10.5.80.134 Net Mask 255.255.255.0 255.255.255.0 Gateway 10.5.80.1 10.5.80.1 MGMT 2 Configuration Current IP Address 10.5.80.135 10.5.80.135 Net Mask 255.255.255.0 255.255.255.0 Gateway 10.5.80.1 10.5.80.1

9. Run “svipaddrshow” to confirm the configuration results from step 7. MP Router:admin> svipaddrshow The switch virtual IP configuration current IP address 10.5.80.136 10.5.80.136 Netmask 255.255.255.0 255.255.255.0 Gateway - 10.5.80.1

10. Run “switchname FX2_FC_SW1” to change the name of this Multi-Protocol Router to FX2_FC_SW1.

MP Router:admin> switchname FX2_FC_SW1

11. Run “switchname” to confirm the configuration results from step 10. FX2_FC_SW1:admin> switchname FX2_FC_SW1

12. Run “timezoneset” to start the timezoneset configuration script. Note: All script input is highlighted in red text below.

FX2_FC_SW1:admin> timezoneset

36

Please select a continent or ocean 1). Africa 2). America 3). Antarctica 4). Arctic Ocean 5). Asia 6). Atlantic Ocean 7). Australia 8). Europe 9). Indian Ocean 10). Pacific Ocean 11). US 12). Canada Enter the option #: 2 Please select a country or city 1). Adak 2). Anchorage 3). Anguilla 4). Antigua 5). Araguaina 6). Aruba 7). Asuncion 8). Atka 9). Barbados 10). Belem 11). Belize 12). Boa_Vista 13). Bogota 14). Boise 15). Buenos_Aires 16). Cambridge_Bay 17). Cancun 18). Caracas 19). Catamarca 20). Cayenne 21). Cayman 22). Chicago 23). Chihuahua 24). Cordoba 25). Costa_Rica 26). Cuiaba 27). Curacao 28). Danmarkshavn 29). Dawson 30). Dawson_Creek 31). Denver 32). Detroit 33). Dominica 34). Edmonton 35). Eirunepe 36). El_Salvador 37). Ensenada 38). Fort_Wayne 39). Fortaleza 40). Glace_Bay 41). Godthab 42). Goose_Bay 43). Grand_Turk 44). Grenada 45). Guadeloupe 46). Guatemala 47). Guayaquil 48). Guyana 49). Halifax 50). Havana 51). Hermosillo 52). Indiana 53). Indianapolis 54). Inuvik 55). Iqaluit 56). Jamaica 57). Jujuy 58). Juneau 59). Kentucky 60). Knox_IN 61). La_Paz 62). Lima 63). Los_Angeles 64). Louisville 65). Maceio 66). Managua 67). Manaus 68). Martinique 69). Mazatlan 70). Mendoza 71). Menominee 72). Merida 73). Mexico_City 74). Miquelon 75). Monterrey 76). Montevideo 77). Montreal 78). Montserrat 79). Nassau 80). New_York 81). Nipigon 82). Nome 83). Noronha 84). North_Dakota 85). Panama 86). Pangnirtung 87). Paramaribo 88). Phoenix 89). Port-au-Prince 90). Port_of_Spain 91). Porto_Acre 92). Porto_Velho 93). Puerto_Rico 94). Rainy_River 95). Rankin_Inlet 96). Recife 97). Regina 98). Rio_Branco 99). Rio_Branco 100). Rosario 101). Santiago 102). Santo_Domingo 103). Sao_Paulo 104). Scoresbysund 105). Shiprock 106). St_Johns 107). St_Kitts 108). St_Lucia 109). St_Thomas 110). St_Vincent 111). Swift_Current 112). Tegucigalpa 113). Thule 114). Thunder_Bay 115). Tijuana 116). Tortola 117). Vancouver 118). Virgin 119). Whitehorse 120). Winnipeg 121). Yakutat 122). Yellowknife Enter the option #: 22 time zone is set

7.3 – FC Router License Addition

13. Run “licenseadd (License Key)” to install the appropriate license keys. Licenses are created from EMC based on the Multi-Protocol Router World Wide Name. In this example, we are adding the Storage Application Service (SAS) License which is required for Invista functionality. Note: iSCSI services have been disabled since we added and enabled the SAS License.

37

FX2_FC_SW1:admin> licenseadd bbRebzee9Sccafcp license bbRebzee9Sccafcp added iSCSI service is disabled on addition of SAS license You have to reboot the system to make the change take effect. Note: Fibre Channel Routing Services and FCIP must be deleted prior to adding the SAS License.

14. Run “licenseshow” to confirm that the SAS License was added from step 13. FX2_FC_SW1:admin> licenseshow License Key: ScSz9RyzReTdT0Aq Web License Key: bde99c9SSzcefAA3 Zoning License Key: R9cRceRSdSAdSdj Base switch license License Key: bbRebzee9SkcSfcp Trunking License Key: bbRebzee9Sccafcp Storage Application Service License Key: bbRebzee9ScsSfcx Ports on Demand - enable all 16 ports

7.4 - FC Router SNMP Configuration

15. Run “agtcfgset” to start the SNMP Configuration Script. The recipient IP Addresses used will be CPC – SP A & SP B. Note: All script input is highlighted in red text below.

FX2_FC_SW1:admin> agtcfgset Customize MIB-II system variables...... At each prompt, do one of following: <return> to accept current value enter the appropriate new value <ctrl-D> to skip the rest of configuration and finish <ctrl-C> to cancel any changes sysDescr: [Connectrix B Application Platform ] sysLocation: [End User Premise. ]

38

sysContact: [Field Support. ] swEventTrapLevel: (0..5) [3 ] SNMP community and trap recipient configuration: You can add maximum 6 trap recipients type <.> at IP address to delete the recipient recipient1--Community [Secret C0de] private recipient1--IP address in dot notion [0.0.0.0] 10.5.80.130 - Note: CPC SP A recipient2--Community [OrigEquipMfr] private recipient2--IP address in dot notion [0.0.0.0] 10.5.80.131 - Note: CPC SP B recipient3--Community [private] public recipient3--IP address in dot notion [0.0.0.0] 10.5.80.130 - Note: CPC SP A recipient4--Community [public] public recipient4--IP address in dot notion [0.0.0.0] 10.5.80.131 - Note: CPC SP B recipient5--Community [common]

16. Run “agtcfgshow” to confirm that the SNMP Configuration was added from step 15.

FX2_FC_SW1:admin> agtcfgshow Current SNMP Agent Configuration Customizable MIB-II system variables: sysDescr = Connectrix B Application Platform sysLocation = End User Premise. sysContact = Field Support. swEventTrapLevel = 3 SNMPv1 Trap Recipient Configuration recipient1--Community=private recipient1--IP address=10.5.80.130 recipient2--Community=private recipient2--IP address=10.5.80.131 recipient3--Community=private No trap recipient configured yet recipient4--Community=public No trap recipient configured yet

39

recipient5--Community=common No trap recipient configured yet recipient6--Community=FibreChannel No trap recipient configured yet

17. Perform steps 4-16 for each additional DPC that is present in the Invista Instance.

8 - FC Router Operating System Upgrade

8.1 - FTP Configuration

1. Open a Web Browser page and enter the Multi-Protocol Router Virtual IP Address to launch the Brocade Switch Explorer. You must upgrade the XPath OS and XPath SAS Code to match the Invista-Storage-Virtualization-Services Package on the CPC’s. Select the Admin Icon under the router picture to launch the Admin GUI.

2. Place the XPath OS and XPath SAS Code to be installed into the FTP directory

on a active FTP Server.

40

3. From within the Switch Manager Administration window, select the Config Upload/Download tab and then Edit to edit the FTP configuration.

41

4. From within the Server for config files window, enter the FTP Server IP Address, Protocol (FTP or TFTP), FTP Server Username, FTP Server Password, File Name (Can be anything), check mark Verify settings and then select the OK icon to continue.

42

5. While still in the Config UploadDownload tab, select Upload Configuration to upload the test file you configured in step 4 to the FTP Server Directory. These steps confirm FTP connectivity.

8.2 - XPath OS Upgrade

6. Telnet to the router and run “switchdisable” to disable the router. The router (DPC) must be disabled prior to starting the code upgrade.

FX2_FC_SW1:admin> switchdisable Switch is being disabled................

7. Run “firmwaredownload (FTP Server IP Address) (FTP User Name) (XPath OS Code Name) (FTP Server Password)” to copy the XPath Code from the FTP Server to the Router.

FX2_FC_SW1:admin> firmwaredownload 10.5.80.100 ftp xpath_os_v7.4.1 password Downloading xpath_os_v7.4.1... Protocol not implemented, use (1,1) Downloading xpath-base-skel-7.4.1-ga_bld18.ppc.rpm... Protocol not implemented, use (1,1) Installing xpath-base-skel-7.4.1-ga_bld18.ppc.rpm to bank 1... xpath-base-skel ################################################## Downloading netbsd-2.0.ga.1-proto1_bld374.ppc.rpm... Protocol not implemented, use (1,1)

43

Installing netbsd-2.0.ga.1-proto1_bld374.ppc.rpm to bank 1... netbsd ################################################## Downloading xpath-base-os-7.4.1-ga_bld18.ppc.rpm... Protocol not implemented, use (1,1) Installing xpath-base-os-7.4.1-ga_bld18.ppc.rpm to bank 1... xpath-base-os ################################################## Downloading xpath-kernel-7.4.1-ga_bld18.ppc.rpm... Protocol not implemented, use (1,1) Installing xpath-kernel-7.4.1-ga_bld18.ppc.rpm to bank 1... xpath-kernel ################################################## Downloading xpath-bootloader-7.4.1-ga_bld18.ppc.rpm... Protocol not implemented, use (1,1) Installing xpath-bootloader-7.4.1-ga_bld18.ppc.rpm to bank 1... xpath-bootloader ################################################## writing silk.loader into bank1. Erasing ................done! .........finished. wrote: 525312 bytes into flash Patch success. Please reboot the switch. Firmware download and install complete: Please reboot to activate

8. Run “reboot” to activate the upgraded code. FX2_FC_SW1:admin> reboot Do you really want to reboot the switch? (y, n) y reboot[25516]: switch is being rebooted by the user....

9. Complete steps 6-8 again to upgrade the SAS Code. Downloading xpath_sas_v2.1.3h... Downloading sas_rpm-2.1.3h-ga0_bld0.ppc.rpm... sas_rpm ################################################## Firmware download and install complete: Please reboot to activate

10. Run “showrecovery” to confirm the Recovery Kernel, XPath OS and XPath SAS code versions.

FX2_FC_SW1:admin> showrecovery Recovery Kernel version : 1.5.2.9 FX2_FC_SW1:admin> version =================== Installed Packages: =================== Package Name: xpath_os_v7.4.1 Install Date: Mar 10, 2007 10:37 Package Name: xpath_sas_v2.1.3h Install Date: Mar 10, 2007 10:53

44


9 - SAL Agent Installation from CPC to DPC

9.1 - EMCRemote Configuration



45

3. Once in Windows XP Embedded, go to a DOS prompt and change directories to C:\EMC\base\<install_dir>\msgbin and run “Switchcli -swip (DPC Virtual IP Address) -install FabxBrocade Install.pl -swusr root -cpcusr clarion”. Note: All script input is highlighted in red text below.

C:\EMC\Base\102102000.006\msgbin > Switchcli -swip 10.5.80.136 -install FabxBrocade Install.pl -swusr root -cpcusr clarion. Enter the switch password: Serv4EMC Enter the CPC FTP password: clariion! Log file location: C:\DUMPS\brocade_install.log Checking for virtualizer and DPC states... Copying FABX_Brocade.tar from C:\EMC\Brocade\10212000.006\FABX_Brocade.tar to c:\SwitchTemp\ ... 1 files(s) copied. Checking for firmware compatibility...

46

Checking if the version is already installed ... Checking for disk space availability ... Initiating file transfer ... FTP file transfer successful Installation completed Rebooting the switch ... SAL Agent Configuration Example

4. Perform step 3 for each additional DPC that is present in the Invista Instance. 10 - SAL Agent Process Monitoring

1. Telnet to the Virtual IP Address of the Multi-Protocol Router and provide the login credentials (Username = root – Password = Serv4EMC). You must login as root to very that the SAL Agent is running.

login: root Password: Serv4EMC Terminal type is ansi.

47

Disclaimer for Root and Factory Accounts Usage! This Fibre Channel switch is equipped with Root and Factory accounts that are intended for diagnostics and debugging purposes solely by the Equipment vendor's trained engineers. Improper use of the functionality made available through the Root or Factory account could cause significant harm and disruption to the operation of the SAN fabric. Your use of the functionality made available through the Root or Factory account is at your sole risk and you assume all liability resulting from such use. The Equipment vendor shall have no liability for any losses or damages arising from or relating to the use of the Root or Factory account (and the functionality enabled thereby) by anyone other than the Equipment vendor's authorized engineers. Proceeding with the usage of this switch as the Root or Factory user explicitly indicates your agreement to the terms of this disclaimer.

2. Run “ps -waux | grep sal” to verify that the processes are running. The salagent and salmonitor should be running as indicated in blue text below. These processes must be running for the Invista Instance to function properly.

# ps -waux | grep sal root 28711 0.0 0.2 4292 2280 ?? S 11:13AM 0:00.04 /brocade/current/salagent root 27917 0.0 0.1 176 592 p0 S+ 11:13AM 0:00.01 grep sal root 25714 0.0 0.1 2440 1468 00- S 11:13AM 0:00.03 /brocade/current/salmonitor


11 - Confirming WWN Block

48

1. From the Service Laptop with Invista CLI running, change directories to

C:\Program Files\EMC\INVCLI and run “java -jar invcli.jar -address 10.5.80.130 -user admin -password password portwwn –listwwnblocks” to confirm the Invista WWN Block.

C:\Program Files\EMC\INVCLI>java -jar invcli.jar -address 10.5.80.130 -user admi n -password password portwwn -listwwnblocks First WWN: 50:00:14:41:00:19:8F:A9 Count: 1024

12 - Network Time Protocol (NTP) Configuration

12.1 IP Switch NTP Configuration

1. Telnet to the IP Address of the IP Switch and provide the login credentials (Username = manager – Password = EMC2wil).

login: manager Password: password

2. Run “show time” to view the current time and date that the switch is set to. EMC-NFW1> show time System time is 12:20:39 on Monday 09-Apr-2007.

3. Run “set time=hr:mn:sc” to set the current Non-NTP Time. Manager EMC-NFW1> set time=01:15:10 System time is 01:15:10 on Monday 09-Apr-2007.

4. Run “enable ntp” to enable NTP for this IP Switch. Manager EMC-NFW1> enable ntp

5. Run “add ntp peer=(IP Address)” to add a NTP Peer. The example below is using IP Switch 2 as the NTP Peer.

Manager EMC-NFW1> add ntp peer=10.5.80.133 Info (1040003): Operation successful.

6. Run “set ntp utcoffset=(Time Zone). The example below is using the Central Time Zone.

49

Manager EMC-NFW1> set ntp utcoffset=6:00:00 Info (1040003): Operation successful.

7. Run “reset ntp” to reset NTP for this IP Switch. Manager EMC-NFW1> reset ntp Info (1040003): Operation successful.

8. Type “show ntp” to confirm that the changes are present from steps 1-7. Manager EMC-NFW1> show ntp ------------------------- NTP Module Configurations ------------------------- Status : ENABLED Host Address : 10.5.80.132 UTC offset : +06:00:00 (UTC/GMT) Last Updated : 01:30:18 on 04-09-2007 Last Delta : +0.00 Configured Peer ---------------- 10.5.80.133 Counters --------- Packets Sent : 0000000018 Packets Received : 0000000845 Packets w/ head error : 0000000000 Packets w/ data error : 0000000000

9. Run “show config” to confirm the Boot and Current Configuration Files. Note: Notice that the Boot and Current Configuration Files are the same.

Manager EMC-FW1> show config Boot configuration file: flash:ipsw1ini.cfg (exists) Current configuration: flash:ipsw1ini.cfg

10. Run “set config=(New Configuration Name.cfg)” to save the NTP configuration changes. Without this new configuration, the NTP configuration changes will be lost upon reboot.

Manager EMC-FW1> set config=ipsw1ini_w_ntp.cfg Info (1049003): Operation successful.

50

11. Run “show config” to confirm that ipsw1ini_w_ntp.cfg is the Boot Configuration File. You will notice that ipsw1ini.cfg is still the Current Configuration File. The IP Switch must be restarted to change the Current Configuration status.

Manager EMC-FW1> show config Boot configuration file: flash:ipsw1ini_w_ntp.cfg (exists) Current configuration: flash:ipsw1ini.cfg

12. Run “restart switch” to restart the IP Switch. Manager EMC-FW1> restart switch INFO: Initialising Flash File System. INFO: IGMP packet trapping is active for IGMP snooping, L3FILT is activated INFO: Executing configuration script <flash:ipsw1ini_w_ntp.cfg> INFO: Switch startup complete

13. Once at the login screen, type the login credentials (Username = manager – Password = EMC2wil).

login: manager Password: EMC2will

14. Run “show config” to confirm that ipsw1ini_w_ntp.cfg is the Boot Configuration File along with the Current Configuration File.

Manager > show config Boot configuration file: flash:ipsw1ini_w_ntp.cfg (exists) Current configuration: flash:ipsw1ini_w_ntp.cfg

15. Perform steps 1-14 for the other IP Switch that is present in the Invista Instance.

12.2 - FC Router NTP Configuration

16. Telnet to the Virtual IP Address of the Multi-Protocol Router and provide the login credentials (Username = root – Password = Serv4EMC). You must login as root to configure NTP.

login: root Password: Serv4EMC

51

Terminal type is ansi. Disclaimer for Root and Factory Accounts Usage! This Fibre Channel switch is equipped with Root and Factory accounts that are intended for diagnostics and debugging purposes solely by the Equipment vendor's trained engineers. Improper use of the functionality made available through the Root or Factory account could cause significant harm and disruption to the operation of the SAN fabric. Your use of the functionality made available through the Root or Factory account is at your sole risk and you assume all liability resulting from such use. The Equipment vendor shall have no liability for any losses or damages arising from or relating to the use of the Root or Factory account (and the functionality enabled thereby) by anyone other than the Equipment vendor's authorized engineers. Proceeding with the usage of this switch as the Root or Factory user explicitly indicates your agreement to the terms of this disclaimer. XPath (switchboard) (ttyp0)

17. Change directories to /brocade/current and run “./fabxntp (NTP Server IP Address)” to add the NTP Server entry. Note: This example is using IP Switch 1 as the NTP Server.

# cd /brocade/current # ./fabxntp 10.5.80.132 tsclockserver succeeded

18. Run “crontab –l” to confirm that the ntpdate variable is set. # crontab -l 1 **** /usr/sbin/ntpdate -s 10.5.80.132 If corrections are needed, enter the command crontab -e to make the necessary changes

12.3 - CPC NTP Configuration

52



21. Once in Windows XP Embedded, go to a DOS prompt, change directories to C:\WINNT\system32\drivers\etc and edit the hosts file by adding the NTP Server Name and IP Address of the VRRP Address of the Allied Telesyn Switch which is 10.5.80.132

Example of Host File Changes 10.5.80.132 NTP_Server1

53

22. From the Service Laptop with Invista CLI running, change directories to C:\Program Files\EMC\INVCLI and run “java -jar invcli.jar -user (Invista Username) -password (Invista Password) -address CPC – SP A IP Address setntpserver NTP_Server1” This NTP Server Alias was defined in the previous step during the Host File update.

java -jar invcli.jar -user admin -password password -address 10.5.80.130 setntpserver NTP_Server1

54

13 - Importing DPC (Brocade 7420 MPR) into the CPC

1. Go back to the Invista Element Manager and navigate to Storage, Physical, Intelligent Switches and select Import Switch.

2. Within the Import Switch window, provide the SNMP Management Address (Brocade Multi-Protocol Router Virtual IP Address) and the SNMP Community String (Private).

55

3. Select the Yes Icon to confirm the import of this switch.

4. You should see a Success message in the Import Switch window.

56

5. Navigate to Storage, Physical, Intelligent Switches, Switch Name, Chassis 1, DPC1 and select Import.

57

6. Select the port numbers you wish to configure as Front-End ports. In this

example, we are configuring Ports 0-7 as Front-End Ports. These 8 Ports will be the Virtual Targets. We have the ability to use all 16 Ports on the Multi-Protocol Router as Virtual Targets, but I have only selected 8 for this example. Note: The 16 ports on the Multi-Protocol Router function both as Virtual Targets and Virtual Initiators at the same time.

7. Select the Yes Icon to confirm the configuration of 8 Front-End Ports on this switch.

58

8. You should see a Success message in the Import DPC 1 window.

59

9. Navigate to Storage, Physical, Intelligent Switches, Switch Name, Chassis 1, DPC1 and select Set Online.

10. Select the Yes Icon to confirm setting this DPC online.

60

11. A Success message will appear in the window.

12. Navigate to Storage, Physical, Intelligent Switches, Switch Name and select Set Online.

61

13. Select the Yes Icon to confirm setting this Switch online.


62

15. Now that you have imported the Switch/DPC and set all components online, all 8 Virtual Targets and 16 Virtual Initiators are fully configured. The Invista virtualization services are up and running.


63

14 - Performing Invista to Back-End Storage Zoning

14.1 - Zone Aliases

1. Open a Web Browser page and enter the Multi-Protocol Router Virtual IP Address to launch the Brocade Switch Explorer. Select the first icon to the right in the lower left portion of the screen to launch the Switch Manager.

64

2. Once in Switch Manager, select the Name Server tab to view the currently populated Name Server. Note: Take note in the Physical Column of Physical and Virtual entries.

3. Within Switch Manager, select the Zoning then Zone Aliases tabs to start

creating Aliases. Next, select the New entry under the Zone Alias tab. We recommend these Aliases to ease the level of effort needed to create zones, and to identify them later.

65

4. When selecting New Zone Aliases, you will be prompted to login as the Switch Administrator.

5. Enter the Switch login credentials (Username = admin – Password = Serv4EMC) and select the OK icon to continue.

66

6. Within the New Zone Alias window, create a Zone Alias Name in the upper left corner of the window. Next, highlight the WWN under the FC Devices in Fabric column that you wish to create an Alias for and select the Add PWWN icon to add the entry to the Zone Alias Members to be Added column.

7. Confirm the proper PWWN in the Zone Alias Members to be Added column and select the OK icon to save the alias.

67

8. Confirm that the Alias created in steps 3-7 is present and correct. Create these entries for all Invista Virtual Targets, Invista Virtual Initiators, Physical Storage Ports and Physical Host HBA Ports.

14.2 - Zoning

9. Within Switch Manager, select the Zoning and Zones tabs. Select New to create a new Zone.

68

10. Create the 2 different zone types. These will be Physical Storage Ports to Invista

Virtual Initiators and Host HBA Ports to Invista Virtual Targets. Select the entries from the Aliases in the Fabric column, select the Add icon to add these aliases into this zone. Select the OK icon to continue.

Physical Storage Port to Invista Virtual Initiators Zoning Requirements: Each Storage Port WWN must be in a Zone with all 16 Invista Virtual Initiators (17 Member Zone). Host HBA to Invista Virtual Target Zoning Requirements: Each Host HBA Port WWN must be in a Zone with 1 Invista Virtual Target (2 Member Zone).

69

11. Confirm that the zone created in steps 9-10 is present and correct. Create these zones for all Physical Storage Ports and Physical Host HBA Ports.

14.3 – Zone Configuration

12. Within Switch Manager, select the Zoning and Zone Configuration tabs. Select New to create a new Zone Configuration.

70

13. Within the New Zone Configuration window, create a Zone Configuration Name in the upper left corner of the window. Next, highlight the Available Zones under the Available Zones column that you wish to add to the configuration and select the Add icon. This will add the Zones to the new Zone Configuration. Do this for all Storage and Host Zones and select the OK icon to continue.

14. Confirm that the Zones added in steps 12-13 are present and correct. Select the

Enable text to enable this configuration.

71

15. Select the Yes icon at the Confirm Enable window to proceed with enabling the configuration.

72

16. Confirm that the Zone Configuration is active. The active Zone Configuration will have a check mark in the Effective column.


73

15 - CLARiiON Back-End Configuration

15.1 – Initiator Configuration

1. Open a Web Browser page and enter the CLARiiON SP IP Address to launch Navisphere. Next, provide the proper credentials and press the OK icon to continue.

2. Once in Navisphere®, right click on the CLARiiON and select Update Now to update the array. Next, select Connectivity Status from the same menu to view CLARiiON Connectivity Status.

74

3. From the Connectivity Status screen, confirm that the Invista Initiator entry is present. Of the 16 Invista Virtual Initiators within a Zone, only 1 entry will login and you will have to register the others manually. Highlight the logged-in entry and select the Register icon.

75

4. From the Register Initiator Record window, select Initiator Type (CLARiiON Open), Unit Serial Number (Array), Failover Mode (1), ArrayCommPath (Enabled), New Host Radio icon, provide Host Name/IP Address. Select the OK icon to continue.

5. Select the Yes icon to confirm the Registering Initiator Record task.

76


77

7. You will receive a warning message indicating that the host entry will not be

managed because it was manually registered. This is normal for any device not utilizing a Navisphere Agent. Just ignore the message by selecting the OK icon.

8. The entry is now fully registered. Next, select the New icon in the lower left corner to manually register the other 15 Invista Virtual Initiators.

78

9. From the Create Initiator Record window, select Initiator Name (WWN), Initiator Type (CLARiiON Open), Unit Serial Number (Array), Failover Mode (1), ArrayCommPath (Enabled), New Host Radio icon, provide Host Name/IP Address and select the OK icon to continue. You will have to perform this step to register 16 Invista Virtual Initiators for each SP Port used.

10. Select the Yes icon to confirm the Registering Initiator Record task.

79


12. You will receive a warning message indicating that the host entry will not be managed because it was manually registered. This is normal for any device not utilizing a Navisphere Agent. Just ignore the message by selecting the OK icon.

80

15.2 – RAID Group Configuration

13. Navigate down to RAID Group, right click and select Create RAID Group.

81

14. From within the Create RAID Group screen, select the Manual radio icon under Disk Selection. The next numerical value will be populated automatically for the RAID Group ID.

15. Highlight the disks that you want to use for this RAID Group. We will be creating a RAID 1/0 configuration. A best practice is to select available disks that are on

82

separate Buses for added protection. Once you have highlighted the correct disks from the Available Disks section on the left side of the screen, select the top arrow icon in the center of the screen.

16. The disk should now be located under the Selected Disks section located on the

right side of the screen. Next, select the OK icon to go back to the Create RAID Group main screen.

17. Confirm that the selected entries are correct and select the Apply icon to commit this configuration.

83

18. Select Yes at the Create RAID Group confirmation screen.


84

20. Expand the RAID Groups tree and confirm that the newly created RAID Group is present. The RAID Group will have a status of Unbound since no LUNs have been Bound against it.

85

86

15.3 – Bind LUN Configuration

21. Highlight the RAID Group you created in the previous step, right click and select Bind LUN. Next, select the RAID Type (RAID 1/0), LUN ID, Default SP Owner, LUN Size (MB, GB or Block Count), Number of LUNs to Bind and select the Apply icon to continue.

22. Select Yes at the Bind LUN confirmation screen.

87

23. The RAID Group will go into a state of Transitioning while the Binding process is occurring.

15.4 – Storage Group Configuration

88

24. Highlight the CLARiiON, right click and select Create Storage Group.

25. Name the Storage Group and select the OK icon.

26. Select Yes at the Create Storage Group confirmation screen.

89


90

15.5 – LUN/Host Assignment

28. Navigate down to the newly created Storage Group Invista_Brocade, right click and select LUNs to assign LUNs/Host to this Storage Group.

29. Select the correct LUN from the Available LUNs section on the left side of the

screen. Then, select the top arrow icon located in the center of the screen.

91

30. Select the correct host from the Available Host section on the left side of the screen. Then, select the top arrow icon located in the center of the screen. The host should now be located under the Hosts to be Connected section located on the right side of the screen. Next, select the OK icon to commit these configuration changes.

92

31. Select Yes at the Storage Group Properties confirmation screen for LUNs addition.

32. Select Yes at the Storage Group Properties confirmation screen for Hosts addition.

93

33. You will receive a status message of Success if the configuration committed with no issues.

94

34. Navigate down to the newly created Storage Group Invista_Brocade and expand

the Hosts and LUNs section to confirm that the assigned Host and LUN are visible to this particular Storage Group.

16 – Symmetrix Back-End Configuration

16.1 – Symmetrix Meta Device Creation

1. From Solutions Enabler, run "symcfg discover" to update the symapi_db.bin file locally.

This operation may take a few minutes; please be patient.

2. From Solutions Enabler, run "symdev list -noport | more" to identify devices to form a Meta.

Symmetrix ID: 000187910440 Device Name Directors Device --------------------------- ------------ -------------------------------------- Cap Sym Physical SA :P DA :IT Config Attribute Sts (MB) --------------------------- ------------- ------------------------------------- 01B1 Not Visible ???:? 01A:D5 RAID-5 N/Grp'd RW 17263

95

01B2 Not Visible ???:? 02A:D2 RAID-5 N/Grp'd RW 17263 01B3 Not Visible ???:? 01A:C2 RAID-5 N/Grp'd RW 17263 01B4 Not Visible ???:? 02A:C3 RAID-5 N/Grp'd RW 17263 01B5 Not Visible ???:? 01A:D1 RAID-5 N/Grp'd RW 17263 01B6 Not Visible ???:? 02A:D4 RAID-5 N/Grp'd RW 17263

3. Create a map file with the following context. The map file is just a simple text file that will later be committed to the Symmetrix. This example will create a 6 member Striped Meta Device with a Stripe Size of 1920 which is the default. Device 01B1 is the Meta Head which forms the Meta Device.

Form meta from dev 01B1, config=striped stripe_size=1920; add dev 01B2 to meta 01B1; add dev 01B3 to meta 01B1; add dev 01B4 to meta 01B1; add dev 01B5 to meta 01B1; add dev 01B6 to meta 01B1;

16.2 – Symmetrix Meta Device FA Mapping

4. From Solutions Enabler, run "symcfg list -available -addresses -sa 2c -p 0" and "symcfg list -available -addresses -sa 15c -p 0" to determine the next available VBUS, TID and LUN. Note: Port A on the Symmetrix is 0 and Port B is 1 when running any commands.

From the output below, the next available address is 0 00 004. Try to get the same address on the other FA used.

Symmetrix ID: 000187910440 (Local) Director Device Name Attr Address ---------------------- ----------------------------- ---- -------------- Ident Symbolic Port Sym Physical VBUS TID LUN ------ -------- ---- ---- ----------------------- ---- --- --- FA-2C 02C 0 0000 Not Visible VCM 0 00 000 0001 Not Visible 0 00 001 0002 Not Visible 0 00 002 0003 Not Visible 0 00 003 - AVAILABLE 0 00 004 * Legend for Available address: (*): The VBUS, TID, LUN address values represent a gap in the address assignments or are the next available address

5. Append the following context to the map file created in step 3.

map dev 01B1 to dir 02c:0, target=0, lun=004; map dev 01B1 to dir 15c:0, target=0, lun=004;

96

16.3 – Symmetrix Meta Device and FA Mapping Configuration

6. From Solutions Enabler, run "symconfigure -sid 0440 -v -f meta_map_file commit" to commit the text within the map file. This will acquire the Symmetrix Lock, prepare the needed steps and commit all needed changes. You can also run "symconfigure -sid 0440 -v -f meta_map_file preview" to check the syntax of the map file you created. This is automatically performed as one of the first steps when specifying the commit option. The complete contents of the map file are listed below.

Form meta from dev 01B1, config=striped stripe_size=1920; add dev 01B2 to meta 01B1; add dev 01B3 to meta 01B1; add dev 01B4 to meta 01B1; add dev 01B5 to meta 01B1; add dev 01B6 to meta 01B1; map dev 01B1 to dir 02c:0, target=0, lun=004; map dev 01B1 to dir 15c:0, target=0, lun=004; Execute a symconfigure operation for symmetrix '000187910440' (y/[n]) ? y A Configuration Change operation is in progress. Please wait. Establishing a configuration change session...............Established. Processing symmetrix 000187910440 { form meta from dev 01B1 config=Striped, stripe_size=1920; add dev 01B2 to meta 01B1, protect_data=FALSE; add dev 01B3 to meta 01B1, protect_data=FALSE; add dev 01B4 to meta 01B1, protect_data=FALSE; add dev 01B5 to meta 01B1, protect_data=FALSE; add dev 01B6 to meta 01B1, protect_data=FALSE; map dev 01B1 to dir 2C:0 target=00, lun=04; map dev 01B1 to dir 15C:0 target=00, lun=04; } Performing Access checks..................................Allowed. Locking devices...........................................Locked. Submitting configuration changes..........................Submitted. Validating configuration changes..........................Validated. Initiating PREPARE of configuration changes...............Queued. PREPARE requesting required resources.....................Obtained. Step 003 of 073 steps.....................................Executing.

97

Step 041 of 145 steps.....................................Executing. Step 134 of 145 steps.....................................Executing. Local: COMMIT............................................Done. Terminating the configuration change session..............Done. The configuration change session has successfully completed.

16.4 – Symmetrix Meta Device and FA Mapping Confirmation

7. From Solutions Enabler, run "symdev show 01B1 | more" to confirm that the

appropriate changes have been made to the device.

Symmetrix ID: 000187910440 Device Physical Name : Not Visible Device Symmetrix Name : 01B1 Device Serial ID : N/A Symmetrix ID : 000187910440 Attached BCV Device : N/A Attached VDEV TGT Device : N/A Vendor ID : EMC Product ID : SYMMETRIX Product Revision : 5671 Device WWN : 85578490475343457235408756783244 Device Emulation Type : FBA Device Defined Label Type: N/A Device Defined Label : N/A Device Sub System Id : 0x0142 Device Block Size : 512 Device Capacity { Cylinders : 220968 Tracks : 3314520 512-byte Blocks : 212129280 MegaBytes : 103579 (Confirm the Device Size is Correct) KiloBytes : 106064640 } Device Configuration : RAID-5 (Meta Head, (Confirm the Device Config is Correct) Non-Exclusive Access) Device is WORM Enabled : No Device is WORM Protected : No

98

SCSI-3 Persistent Reserve: Disabled Dynamic Spare Invoked : No Dynamic RDF Capability : None Device Service State : Normal Device Status : Ready (RW) (Confirm the Device is in a Ready State) Device SA Status : Ready (RW)

Front Director Paths (2): { ---------------------------------------------------------------------- POWERPATH DIRECTOR PORT LUN --------- ---------- ---- -------- --------- PdevName Type Type Num Sts VBUS TID SYMM Host ---------------------------------------------------------------------- Not Visible N/A FA 02c:0 RW 000 00 004 N/A Not Visible N/A FA 15c:0 RW 000 00 004 N/A } (Confirm that the Device FA Settings are Correct) Meta Configuration : Striped Meta Stripe Size : 960k (2 Cylinders) Meta Device Members (6) : { ---------------------------------------------------------------------- BCV DATA RDF DATA ---------------------------- -------------------------- Sym Cap Std Inv BCV Inv Pair R1 Inv R2 Inv Pair Dev (MB) Tracks Tracks State Tracks Tracks State ---------------------------------------------------------------------- -->01B1 17263 - - N/A - - N/A 01B2 17263 - - N/A - - N/A 01B3 17263 - - N/A - - N/A 01B4 17263 - - N/A - - N/A 01B5 17263 - - N/A - - N/A 01B6 17263 - - N/A - - N/A ---------------------------------------------------------------------- 103579 - - - - } (Shows How the Meta Device is Comprised) Mirror Set Type : [RAID-5,RAID-5,N/A,N/A] Mirror Set DA Status : [RW,RW,N/A,N/A] Mirror Set Inv. Tracks : [0,0,0,0] Back End Disk Director Information {

99

Hyper Type : RAID-5 Hyper Status : Ready (RW) Disk [Director, Interface, TID] : [N/A,N/A,N/A] Disk Director Volume Number : N/A Hyper Number : N/A Hyper Type : RAID-5 Hyper Status : Ready (RW) Disk [Director, Interface, TID] : [N/A,N/A,N/A] Disk Director Volume Number : N/A Hyper Number : N/A } RAID-5 Device Information { Number of Tracks in a Stripe : 4 Overall Ready State of RAID-5 Device : ReadyNoSpare Overall WriteProtect State of RAID-5 Device : EnabledNoSpare Member Number of the Failing Device : None Mirror Number of the Failing Device : None Mirror Number of the Data Device : 0 Member Number that Invoked the Spare : None Mirror Number of the Spare Member : None Disk Director (DA) that Owns the Spare : None Copy Direction : N/A RAID-5 Hyper Devices (7+1): { Device : 01B1 (M) { -------------------------------------------------------------- Disk DA Hyper Member Spare Disk DA :IT Vol# Num Cap(MB) Num Status Status Grp# Cap(MB) -------------------------------------------------------------- 01A:D5 864 46 2472 3 RW N/A 2 285902 15A:D5 864 46 2472 7 RW N/A 2 285902 01B:C5 354 46 2472 4 RW N/A 2 285902 15B:C5 354 46 2472 8 RW N/A 2 285902 02C:C5 354 46 2472 6 RW N/A 2 285902 16C:C5 354 46 2472 2 RW N/A 2 285902 02D:D5 864 46 2472 5 RW N/A 2 285902 16D:D5 864 46 2472 1 RW N/A 2 285902 } Device : 01B2 (m) { -------------------------------------------------------------- Disk DA Hyper Member Spare Disk DA :IT Vol# Num Cap(MB) Num Status Status Grp# Cap(MB) -------------------------------------------------------------- 02A:D2 585 47 2472 6 RW N/A 2 285902 16A:D2 586 47 2472 2 RW N/A 2 285902

100

02B:C2 76 47 2472 5 RW N/A 2 285902 16B:C2 76 47 2472 1 RW N/A 2 285902 01C:C2 76 47 2472 3 RW N/A 2 285902 15C:C2 76 47 2472 7 RW N/A 2 285902 01D:D2 586 47 2472 4 RW N/A 2 285902 15D:D2 586 47 2472 8 RW N/A 2 285902 } Device : 01B3 (m) { -------------------------------------------------------------- Disk DA Hyper Member Spare Disk DA :IT Vol# Num Cap(MB) Num Status Status Grp# Cap(MB) -------------------------------------------------------------- 01A:C2 76 47 2472 3 RW N/A 2 285902 15A:C2 76 47 2472 7 RW N/A 2 285902 01B:D2 712 47 2472 4 RW N/A 2 285902 15B:D2 712 47 2472 8 RW N/A 2 285902 02C:D2 712 47 2472 6 RW N/A 2 285902 16C:D2 712 47 2472 2 RW N/A 2 285902 02D:C2 76 47 2472 5 RW N/A 2 285902 16D:C2 76 47 2472 1 RW N/A 2 285902 } Device : 01B4 (m) { -------------------------------------------------------------- Disk DA Hyper Member Spare Disk DA :IT Vol# Num Cap(MB) Num Status Status Grp# Cap(MB) -------------------------------------------------------------- 02A:C3 75 47 2472 5 RW N/A 2 285902 16A:C3 76 47 2472 1 RW N/A 2 285902 02B:D3 586 47 2472 4 RW N/A 2 285902 16B:D3 585 47 2472 8 RW N/A 2 285902 01C:D3 586 47 2472 2 RW N/A 2 285902 15C:D3 586 47 2472 6 RW N/A 2 285902 01D:C3 76 47 2472 3 RW N/A 2 285902 15D:C3 76 47 2472 7 RW N/A 2 285902 } Device : 01B5 (m) { -------------------------------------------------------------- Disk DA Hyper Member Spare Disk DA :IT Vol# Num Cap(MB) Num Status Status Grp# Cap(MB) -------------------------------------------------------------- 01A:D1 557 47 2472 2 RW N/A 2 285902 15A:D1 557 47 2472 6 RW N/A 2 285902 01B:C1 47 47 2472 3 RW N/A 2 285902 15B:C1 47 47 2472 7 RW N/A 2 285902 02C:C1 47 47 2472 5 RW N/A 2 285902 16C:C1 47 47 2472 1 RW N/A 2 285902 02D:D1 557 47 2472 4 RW N/A 2 285902

101

16D:D1 557 47 2472 8 RW N/A 2 285902 } Device : 01B6 (m) { -------------------------------------------------------------- Disk DA Hyper Member Spare Disk DA :IT Vol# Num Cap(MB) Num Status Status Grp# Cap(MB) -------------------------------------------------------------- 02A:D4 739 47 2472 6 RW N/A 2 285902 16A:D4 740 47 2472 2 RW N/A 2 285902 02B:C4 230 47 2472 5 RW N/A 2 285902 16B:C4 230 47 2472 1 RW N/A 2 285902 01C:C4 230 47 2472 3 RW N/A 2 285902 15C:C4 230 47 2472 7 RW N/A 2 285902 01D:D4 740 47 2472 4 RW N/A 2 285902 15D:D4 740 47 2472 8 RW N/A 2 285902 }

16.5 – Symmetrix FA Mapping Address Confirmation

8. From Solutions Enabler, run "symcfg list -available -addresses -sa 2c -p 0" and "symcfg list -available -addresses -sa 15c -p 0" again to confirm that the addresses are now being used.

Output: Symmetrix ID: 000187910440 (Local) Director Device Name Attr Address ---------------------- ----------------------------- ---- -------------- Ident Symbolic Port Sym Physical VBUS TID LUN ------ -------- ---- ---- ----------------------- ---- --- --- FA-2C 02C 0 0000 Not Visible VCM 0 00 000 0001 Not Visible 0 00 001 0002 Not Visible 0 00 002 0003 Not Visible 0 00 003 01B1 Not Visible (M) 0 00 004

16.6 – Symmetrix Meta Device Masking

9. From Solutions Enabler, run "symmaskdb list database | more" to look at each

FA to determine if all devices being masked. Page down until you get to the needed FA Ports. From the output below, you can see that 2 devices are currently available to this FA Port. Be sure to look at the other corresponding FA (FA-15C :0) as well.

102

Output: Director Identification : FA-2C Director Port : 0 User-generated Identifier Type Node Name Port Name Devices ---------------- ----- --------------------------------- -------------------------- ------- 5006048accd24a01 Fibre 5006048accd24a01 5006048accd24a01 01A1 01A2

10. Create a script with the following context. This will mask the device to all 16 Invista Virtual Initiators on each Multi-Protocol Router (DPCs).

The example below will map 1 Symmetrix LUN to all 32 Invista Virtual Initiators over 2 FAs.

symmask -sid 0440 -wwn 5000144100000081 -dir 02c -p 0 add dev 01B1 –nop symmask -sid 0440 -wwn 5000144100000082 -dir 02c -p 0 add dev 01B1 –nop symmask -sid 0440 -wwn 5000144100000083 -dir 02c -p 0 add dev 01B1 –nop symmask -sid 0440 -wwn 5000144100000085 -dir 02c -p 0 add dev 01B1 –nop symmask -sid 0440 -wwn 5000144100000084 -dir 02c -p 0 add dev 01B1 –nop symmask -sid 0440 -wwn 5000144100000086 -dir 02c -p 0 add dev 01B1 –nop symmask -sid 0440 -wwn 5000144100000087 -dir 02c -p 0 add dev 01B1 –nop symmask -sid 0440 -wwn 5000144100000088 -dir 02c -p 0 add dev 01B1 -nop symmask -sid 0440 -wwn 5000144100000089 -dir 02c -p 0 add dev 01B1 –nop symmask -sid 0440 -wwn 5000144100000090 -dir 02c -p 0 add dev 01B1 –nop symmask -sid 0440 -wwn 500014410000008A -dir 02c -p 0 add dev 01B1 –nop symmask -sid 0440 -wwn 500014410000008B -dir 02c -p 0 add dev 01B1 -nop symmask -sid 0440 -wwn 500014410000008C -dir 02c -p 0 add dev 01B1 –nop symmask -sid 0440 -wwn 500014410000008D -dir 02c -p 0 add dev 01B1 –nop symmask -sid 0440 -wwn 500014410000008E -dir 02c -p 0 add dev 01B1 –nop symmask -sid 0440 -wwn 500014410000008F -dir 02c -p 0 add dev 01B1 -nop symmask -sid 0440 -wwn 5000144100000081 -dir 015c -p 0 add dev 01B1 –nop symmask -sid 0440 -wwn 5000144100000082 -dir 015c -p 0 add dev 01B1 –nop symmask -sid 0440 -wwn 5000144100000083 -dir 015c -p 0 add dev 01B1 –nop symmask -sid 0440 -wwn 5000144100000085 -dir 015c -p 0 add dev 01B1 –nop symmask -sid 0440 -wwn 5000144100000084 -dir 015c -p 0 add dev 01B1 –nop symmask -sid 0440 -wwn 5000144100000086 -dir 015c -p 0 add dev 01B1 –nop symmask -sid 0440 -wwn 5000144100000087 -dir 015c -p 0 add dev 01B1 –nop symmask -sid 0440 -wwn 5000144100000088 -dir 015c -p 0 add dev 01B1 –nop symmask -sid 0440 -wwn 5000144100000089 -dir 015c -p 0 add dev 01B1 –nop symmask -sid 0440 -wwn 5000144100000090 -dir 015c -p 0 add dev 01B1 –nop symmask -sid 0440 -wwn 500014410000008A -dir 015c -p 0 add dev 01B1 –nop symmask -sid 0440 -wwn 500014410000008B -dir 015c -p 0 add dev 01B1 –nop symmask -sid 0440 -wwn 500014410000008C -dir 015c -p 0 add dev 01B1 –nop symmask -sid 0440 -wwn 500014410000008D -dir 015c -p 0 add dev 01B1 –nop symmask -sid 0440 -wwn 500014410000008E -dir 015c -p 0 add dev 01B1 –nop symmask -sid 0440 -wwn 500014410000008F -dir 015c -p 0 add dev 01B1 –nop

103

symmask refresh -sid 0440

11. From Solutions Enabler, run "symcfg discover" to update the symapi_db.bin file locally.

This operation may take up to a few minutes; Please be patient.

12. From Solutions Enabler, run "symmaskdb list database | more" to look at each FA and confirm that all devices are visible to the new WWN entries. Be sure to look at FA-15C :0 (Corresponding FA) as well.

Output: Director Identification : FA-2C Director Port : 0 User-generated Identifier Type Node Name Port Name Devices ---------------- ----- --------------------------------- -------------------------- ------- 5006048accd24a01 Fibre 5006048accd24a01 5006048accd24a01 01A1 01A2 01B1

104

17 - Invista Storage Importing

1. Go back to the Invista Element Manager, right click on the Invista Serial Number and select Rediscover Backend SEs and Paths.

105

2. A status message will display indicating that the discovery process may take a

while for the GUI to get refreshed with the results. Select the OK icon to continue.

3. Navigate to Storage, Physical, Arrays and confirm that the CLARiiON and Symmetrix Storage Arrays are now present.

106

4. Expand each SE Entry on the CLARiiON and Symmetrix. Right click on each SE Entry and select Import to import the Physical Storage Elements into the Invista environment.

107


6. For a Volume Backend Path summary, select each SE Entry and a summary of the Storage Type will be displayed. In this example, this volume is from a CLARiiON on SP A – Port 2.

108

7. For a complete volume summary, navigate to Storage and Storage Elements to view a summary of the CLARiiON and Symmetrix storage.

109

18 - Invista Virtual Volume Creation

1. Navigate to Storage, Physical, Storage Elements, Imported and right click on the appropriate CLARiiON or Symmetrix SE Entry to start the process of creating a Virtual Volume.

2. From the SE Entry – Create Virtual Volume Window, provide the Virtual Volume ID, Virtual Volume Name, Number of Virtual Volumes to Create, Virtual Volume Size (MB or GB) and select the OK icon to continue.

110

3. Select Yes at the Create Virtual Volume confirmation screen.


111

5. Highlight the newly created Virtual Volume under the SE Entry – Backend Paths to view the volume attributes in the right hand window.

112

113

19 - Invista Virtual Frame Creation

1. Navigate to Storage, Physical and right click on Virtual Frames to Create Virtual Frames.

.

2. Name the Virtual Frame and select the OK icon.

114

3. Select Yes at the Create Storage Group confirmation screen.


115

20 - Invista Host Connectivity

1. Right click on the Invista Serial Number and select Connectivity Status to view the Invista Connectivity Status.

2. From the Connectivity Status screen, confirm that the Host HBA Initiator entry is present. You should see 1 entry for each HBA Port that is present in the Host.

3. Highlight the Host Initiator WWN and select the Register icon to continue.

116

4. From the Register Initiator Record window, select HBA Port Type (Type 1 - Default. e.g. MS-CS), Unit Serial Number (Array), ArrayCommPath (Enabled), New Host Radio Icon, provide Host Name/IP Address. Select the OK icon to continue.


117

6. You will receive a warning message indicating that the host entry will not be managed because it was manually registered. This is normal for any device not utilizing an Agent. Just ignore the message by selecting the OK icon.

118

119

21 - Virtual Frame Resource Allocation

1. Navigate down to the newly created Virtual Frame chipdc, right click and select Edit Properties to assign Virtual Volumes, HBA Ports and Front-End Ports to this Virtual Frame.

2. From the Virtual Volumes tab, select the correct Virtual Volume from the Available Virtual Volumes section on the left side of the screen and then select the top arrow icon located in the center of the screen.

120

3. From the HBA Ports tab, select the correct HBA Port from the Available HBA Ports section on the left side of the screen and then select the top arrow icon located in the center of the screen.

4. From the Front-End Paths tab, check mark the correct HBA Port WWN/Virtual Target WWN pairs and then select the OK icon to continue.

121

5. Select Yes at the Virtual Frame Properties confirmation screen for Front-End Paths configuration.

6. Select Yes at the Virtual Frame Properties confirmation screen for Virtual Volume addition.

122

7. You will receive a status message of Success if the Virtual Volume configuration is committed with no issues.

123

8. You will receive a status message of Success if the Virtual Frame configuration is committed with no issues.

124

9. Navigate down to the newly created Virtual Frame chipdc and expand the Hosts

and Volumes section to confirm that the assigned Host and LUN(s) are visible to this particular Virtual Frame.

125

22 - Invista Clone Operations

22.1 - Clone Group Configuration

1. Navigate to Storage, Physical and right click on Create Clone Group to create a Clone Group.

2. From within the Create Clone Group Window, name the Clone Group, select the Virtual Volume to be cloned (Source). Select the OK icon to continue.

126

3. Select Yes at the Create Clone Group confirmation screen.


127

22.2 - Adding Clones

5. Under the Clones section, right click on the Clone Group that was just created and select Add Clone.

128

6. From within the Add Clone window, select the Clone (Destination), Initial Sync Required, Recovery Policy, Synchronization Rate. Select the OK icon to continue.

7. Select Yes at the Add Clone confirmation screen.

129


130

22.3 - Clone Fracturing

9. Under the Clones section, navigate to the clone, right click and select Fracture to fracture this clone. This clone will start the synchronization process after the previous step has been completed. The following steps demonstrate how to Administratively Fracture a clone.

10. Select Yes at the Fracture Clone confirmation screen.

131


22.4 - Clone Synchronization

12. Under the Clones section, navigate to the clone, right click and select Synchronize to synchronize it.

132

13. Select Yes at the Synchronize Clone confirmation screen.


133

15. At this point, the clone is synchronized and steps 9-11 can be performed to Administratively Fracture this clone. Example: After this step has been performed, the clone can be mounted to a Backup Server to be backed up.

134

135

23 - CPC .mif File Configuration Rebuild


1. This section reviews how to build an Invista V1.0 CPC cluster. This is a “bare-

metal” code install, also referred to as an ICA. If the SPs were previously running Invista, the procedure will erase all existing code and metadata.

2. Open a HyperTerminal session to configure, enter the session name and select

the OK icon to continue.


136

4. Select the COM1 Properties for this device (Bits per second = 115200, Data bits = 8, Parity = None, Stop bits = 1 and Flow control = Hardware).

23.2 - Initial CPC Preparation

137

5. Change the IP Address on the Service Laptop to the same Subnet as the CPC.

6. Unplug both SPs and insert SP A to start the boot process. verBIOS 3 Release 6.0. Copyright 1985-2001 Phoenix Technologies Ltd.All Rights Reserved Copyright 1999-2004 by EMC Corporation, All Rights Reserved. Copyright (c) EMC Corporation , 2005 Disk Array Subsystem Controller Model: CX700: SAN GBFCC4 DiagName: Extended POST DiagRev: Rev. 02.36 Build Date: Mon Aug 29 11:47:26 2005 StartTime: 03/08/2007 20:44:02 SaSerialNo: LKE00060701623 AabcdefgBC

7. Press "Esc" at this point to break the boot sequence. EndTime: 03/08/2007 20:44:03 .... Storage System Failure - Contact your Service Representative ...

8. Type "SHIP_it" and press Enter to enter the Diagnostic Menu.

SHIP_it ****** Aborting!!!! ******

9. Press “Esc” to begin running the diagnostic menu.

10. Enter Option 33 to go to the Image Sub-Menu. Diagnostic Menu 1) Reset Controller 21) BE1 FCC Sub-Menu 2) Enter Debugger 22) CMI0 FCC Sub-Menu 3) Display Warnings/Errors 23) CMI1 FCC Sub-Menu 4) Boot OS 24) AUX0 FCC Sub-Menu 5) POST Sub-Menu 25) AUX1 FCC Sub-Menu 6) Display/Change Privilege 26) FE0 FCC Sub-Menu 7) Boot UProc Sub-Menu 27) FE1 FCC Sub-Menu 8) Ap UProc Sub-Menu 28) FE2 FCC Sub-Menu 9) Real Time Clock Sub-Menu 29) FE3 FCC Sub-Menu 10) Pers. Module Sub-Menu 30) POST ROM Sub-Menu 11) RAM Sub-Menu 31) BIOS ROM Sub-Menu 12) NOVRAM Sub-Menu 32) System Test Sub-Menu 13) Console UART Sub-Menu 33) Image Sub-Menu

138

14) SPS UART Sub-Menu 34) Disk Sub-Menu 15) LCC 0 UART Sub-Menu 35) Resume PROM Sub-Menu 16) LCC 1 UART Sub-Menu 36) Voltage Margin Sub-Menu 17) LCC 2 UART Sub-Menu 37) Information Display 18) LCC 3 UART Sub-Menu 38) ICA Sub-Menu 19) LAN Service Port Sub-Menu 39) DDBS Service Sub-Menu 20) BE0 FCC Sub-Menu 40) FCC Boot Sub-Menu Enter Option : 33

11. Enter Option 9 to go to the Utility Partition Boot Menu. Note: This portion will display many messages and take around 5 minutes to get to the next step. You will be ready for the next step when you see the “int13 - GET DRIVE PARAMETERS (Extended) (1436) - CLARiiON Utility Toolkit” message.

Image Sub-Menu 1) Init Loop 6) Exit Loop 2) Serial Download 7) Relocate/Run Image 3) Load from disk 8) Display Sector Protection 4) Save to disk 9) Utility Partition Boot 5) Update Firmware 0) Exit Enter Option : 9 Initializing back end FIBRE... PCI Config Reg: 2.4.1 0x0157 FCDMTL 0 [2.4.1] Dual Mode Fibre init - OSW DB PTR 0x397D43A0 AG: init DMD to FC_SPEED_2_GBPS FCDMTL 0 [2.4.1] Cached memory - 0xF77B9 bytes @ 0x396DCB80 FCDMTL 0 [2.4.1] Noncached memory - 0xC037F bytes @ 0x3961C7A0 (0x3961C7A0 phys) FCDMTL 0 [2.4.1] DVM Initialized FCDMTL 0 [2.4.1] IMQ base ptr = 39690000; IMQ length = 8000 Dualmode fibre init completed FCDMTL 0 [2.4.1] TPM Notify: st=0xA000000, flg=0x4, cmd=0x1 FCDMTL 0 [2.4.1] TPM Hndle API Event: cntx=0x397D4864, evnt=0x4002, info=0x0 FCDMTL 0 [2.4.1] TPM Lnk Up: state=0xA000000, flg=0x84 Link Event: 0x00030005 Device Event (0xEF): 0x00030012, tach_ptr: 0x3C04894C Device Event (0xE4): 0x00030012, tach_ptr: 0x3C04894C Device Event (0xE8): 0x00030012, tach_ptr: 0x3C04894C Device Event (0xE2): 0x00030012, tach_ptr: 0x3C04894C Device Event (0xE1): 0x00030012, tach_ptr: 0x3C04894C DL waited 1s for discovery Target 0 is online Target 1 is online Target 2 is online Target 3 is online

139

Target 4 is online Relocating Data Directory Boot Service (DDBS: Rev. 02.04)... DDBS: MDDE (Rev 2) on disk 1 DDBS: MDDE (Rev 2) on disk 3DDBS: MDB read from both disks. DDBS: Chassis and disk WWN seeds match. DDBS: First disk is valid for boot. DDBS: Second disk is valid for boot. Utility Partition image (0x0040000F) located at sector LBA 0x00BE804C Disk Set: 1 3 Total Sectors: 0x00095067 Relative Sectors: 0x0000003F Calculated mirror drive geometry: Sectors: 63 Heads: 255 Cylinders: 38 Capacity: 610470 sectors Total Sectors: 0x00095067 Relative Sectors: 0x0000003F Calculated mirror drive geometry: Sectors: 63 Heads: 255 Cylinders: 38 Capacity: 610470 sectors int13 - RESET (1) int13 - READ PARAMETERS (3) int13 - RESET (5) int13 - READ PARAMETERS (7) int13 - READ PARAMETERS (24) int13 - READ PARAMETERS (611) int13 - CHECK EXTENSIONS PRESENT (612) int13 - GET DRIVE PARAMETERS (Extended) (613) int13 - READ PARAMETERS (616) int13 - CHECK EXTENSIONS PRESENT (617) int13 - GET DRIVE PARAMETERS (Extended) (618) int13 - READ PARAMETERS (620) int13 - CHECK EXTENSIONS PRESENT (621) int13 - GET DRIVE PARAMETERS (Extended) (622) int13 - READ PARAMETERS (631) int13 - CHECK EXTENSIONS PRESENT (632) int13 - GET DRIVE PARAMETERS (Extended) (633) int13 - DRIVE TYPE (648) int13 - READ PARAMETERS (649) int13 - DRIVE TYPE (650) int13 - CHECK EXTENSIONS PRESENT (652) int13 - GET DRIVE PARAMETERS (Extended) (653) int13 - READ PARAMETERS (654) int13 - CHECK EXTENSIONS PRESENT (655) int13 - GET DRIVE PARAMETERS (Extended) (656) int13 - READ PARAMETERS (666) int13 - CHECK EXTENSIONS PRESENT (667) int13 - GET DRIVE PARAMETERS (Extended) (668)

140

int13 - READ PARAMETERS (671) int13 - CHECK EXTENSIONS PRESENT (672) int13 - GET DRIVE PARAMETERS (Extended) (673) int13 - READ PARAMETERS (676) int13 - CHECK EXTENSIONS PRESENT (677) int13 - GET DRIVE PARAMETERS (Extended) (678) int13 - READ PARAMETERS (682) int13 - CHECK EXTENSIONS PRESENT (683) int13 - GET DRIVE PARAMETERS (Extended) (684) int13 - READ PARAMETERS (686) int13 - CHECK EXTENSIONS PRESENT (687) int13 - GET DRIVE PARAMETERS (Extended) (688) int13 - READ PARAMETERS (1291) int13 - CHECK EXTENSIONS PRESENT (1292) int13 - GET DRIVE PARAMETERS (Extended) (1293) int13 - READ PARAMETERS (1307) int13 - CHECK EXTENSIONS PRESENT (1308) int13 - GET DRIVE PARAMETERS (Extended) (1309) int13 - READ PARAMETERS (1323) int13 - CHECK EXTENSIONS PRESENT (1324) int13 - GET DRIVE PARAMETERS (Extended) (1325) int13 - READ PARAMETERS (1339) int13 - CHECK EXTENSIONS PRESENT (1340) int13 - GET DRIVE PARAMETERS (Extended) (1341) int13 - READ PARAMETERS (1364) int13 - CHECK EXTENSIONS PRESENT (1365) int13 - GET DRIVE PARAMETERS (Extended) (1366) int13 - READ PARAMETERS (1434) int13 - CHECK EXTENSIONS PRESENT (1435) int13 - GET DRIVE PARAMETERS (Extended) (1436) CLARiiON Utility Toolkit (c) EMC Corporation 2001-2003 All Rights Reserved DiagName: CLARiiON Utility Toolkit DiagRev: 02.06.700.5.003 StartTime: 03/08/07 19:46:24 OS Type............................WinXP SMBUS..............................Running SPID...............................Running ASIDC..............................Running ASIRAMDisk.........................Running ICA................................Running FileZilla Server...................Running Connecting to ICA..................Success SP Type............................CX700 SP ID..............................A SP Signature.......................0x08291953 Checking Image Repository.......... ICA::IRFS Checking Volume for consistency Sizing Image Repository............1024 MB

141

Sizing RAM Disk....................2039 MB Discovering Management LAN Port....ManagementPort0 Checking LAN Port State............Not Configured Checking LAN Port Config...........Found Configuration File Enabling LAN Port..................Done IP Address........................10.5.80.130 Subnet Mask.......................255.255.255.0 Default Gateway...................10.5.80.1 Loading Plugins....................Done Finding incompatible imagesDone =========================================================================WARNING ========================================================================= Installing a Release 13 (02.06.X.XX.X.XXX) or earlier Recovery Image or Conversion Image on an array running Release 14 (02.07.XXX.X.XXX) or higher Core Array Software will result in permanent, unrecoverable loss of configuration information and customer data.

12. Select “Yes” to continue to the next section. Have you read and understood the warning above? [y/N] : y EndTime: 03/08/07 19:46:47

13. Press the Enter key to continue.

23.3 - LAN Service Port Configuration

14. Select 6 to Enable the LAN Service Port and press Enter. ========================================================================= CLARiiON Utility Toolkit Main Menu ========================================================================= 1) About the Utility Toolkit 2) Reset Storage Processor 3) Image Repository Sub-Menu 4) Plugin Sub-Menu 5) NVRAM Sub-Menu 6) Enable LAN Service Port 7) Enable Engineering Mode 8) Install Images Enter Option: 6

15. Enter the IP Address, Subnet Mask and Default Gateway you would like to use and press Enter.

142

Please enter the settings you wish to use. IP Address_________________________ 10.5.80.130 Subnet Mask________________________ 255.255.255.0 Default Gateway____________________ 10.5.80.1 You entered the following settings: IP Address.........................10.5.80.130 Subnet Mask........................255.255.255.0 Default Gateway....................10.5.80.1

16. Select “Yes” to continue to the next section. Enable LAN Service Port with these settings [Y/n] y The LAN Service Port has been enabled

23.4 - CPC .mif File FTP Transfer

17. Place the .mif file (Example: EMC-INV-10.03.2.01.0.002.GA.HotFix2.Brocade.Cisco.mif) in a directory on the Service Laptop.

18. Open a DOS Command Prompt and change directories to the directory where

the .mif file is located. 19. Start an FTP session and perform the following tasks. Username: clarion –

Password: clarion! 20. Once connected, type bin and hash to set the FTP variables. 21. Type “put *.mif” to upload the .mif file from the Service Laptop to the CPC – SP

A. Note: This process could take 5-10 minutes to complete. After this step is complete, the .mif file will be located in RAM Disk on the CPC.

23.5 - CPC .mif File Transfer from RAM Disk to the Image Repository

22. Enter Option 3 to go to the Image Repository Sub-Menu.

CLARiiON Utility Toolkit Main Menu 1) About the Utility Toolkit 2) Reset Storage Processor 3) Image Repository Sub-Menu 4) Plugin Sub-Menu 5) NVRAM Sub-Menu 6) View LAN Service Port Settings 7) Enable Engineering Mode 8) Install Images Enter Option: 3

143

23. Enter Option 4 to copy files from the RAM Disk to the Image Repository.

CLARiiON Utility Toolkit Image Repository Menu 1) Back to the Main Menu 2) List Image Repository Contents 3) Delete Files from the Image Repository 4) Copy Files from the RAM Disk to the Image Repository 5) Copy Files from the Image Repository to the RAM Disk Enter Option: 4

24. Enter Option 1 to copy EMC-INV-10.03.2.01.0.002.GA.HotFix2.Brocade.Cisco.mif from the RAM Disk to the Image Repository.

Select files to copy to the Image Repository 1) EMC-INV-10.03.2.01.0.002.GA.HotFix2.Brocade.Cisco.mif Enter comma separated list of options: 1 Copying EMC-INV-10.03.2.01.0.002.GA.HotFix2.Brocade.Cisco.mif to the Image RepositorySuccess

25. Enter Option 1 to go back to the Main Menu. CLARiiON Utility Toolkit Image Repository Menu 1) Back to the Main Menu 2) List Image Repository Contents 3) Delete Files from the Image Repository 4) Copy Files from the RAM Disk to the Image Repository 5) Copy Files from the Image Repository to the RAM Disk Enter Option: 1

23.6 - Image Installation

26. Enter Option 8 to Install Images from the Image Respository. CLARiiON Utility Toolkit Main Menu 1) About the Utility Toolkit

144

2) Reset Storage Processor 3) Image Repository Sub-Menu 4) Plugin Sub-Menu 5) NVRAM Sub-Menu 6) View LAN Service Port Settings 7) Enable Engineering Mode 8) Install Images Enter Option: 8

27. Enter Option 2 to select the correct .mif file. Select Images to Install 1) 100-560-372.10.00.2.00.0.003.mif 2) EMC-INV-10.03.2.01.0.002.GA.HotFix2.Brocade.Cisco.mif Enter comma separated list of options: 2 EMC-INV-10.03.2.01.0.002.GA.HotFix2.Brocade.Cisco.mif

28. Type “Yes” and press enter to continue to install the images. Are you sure you want to install these images? [y/N] : y

29. Enter Option 3 to have the .mif file installed to both SPs. Select Storage Processors to install images for 1) This SP (SP A) 2) Peer SP (SP B) 3) Both SP's Enter Option: 3 You have chosen to install images for the peer SP. !!! WARNING !!!

30. Ensure that SP B is currently removed. Installing images for the peer SP while it is running may cause undesirable behavior, possibly resulting in data loss. Please ensure that SP B is removed before continuing.

31. Type “Yes” and select Enter to continue with the installation. Continue with image installation? [y/N] : y Copying EMC-INV-10.03.2.01.0.002.GA.HotFix2.Brocade.Cisco.mif to the RAM DiskSuccess Analyzing EMC-INV-10.03.2.01.0.002.GA.HotFix2.Brocade.Cisco.mifDone Sub-Images Found............................................4

145

Checking Disks for DDBS 02.04 Checking Disk 0_0_0................Present Checking Disk 0_0_1................Present Checking Disk 0_0_2................Present Installing DDBS 02.04 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% |----|----|----|----|----|----|----|----|----|----| *************************************************** The COPY operation has completed successfully. Checking Disks for BIOS 03.27 Checking Disk 0_0_0................Present Checking Disk 0_0_1................Present Checking Disk 0_0_2................Present Installing BIOS 03.27 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% |----|----|----|----|----|----|----|----|----|----| *************************************************** The COPY operation has completed successfully. Checking Disks for Extended POST 02.14 Checking Disk 0_0_0................Present Checking Disk 0_0_1................Present Checking Disk 0_0_2................Present Installing Extended POST 02.14 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% |----|----|----|----|----|----|----|----|----|----| *************************************************** The COPY operation has completed successfully. Checking Disks for FLARE Image FABX-HF1-US-FRI-20060127-125701 Checking Disk 0_0_0................Present Checking Disk 0_0_1................Present Checking Disk 0_0_2................Present Checking Disk 0_0_3................Present Installing FLARE Image FABX-HF1-US-FRI-20060127-125701 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% |----|----|----|----|----|----|----|----|----|----| *************************************************** The COPY operation has completed successfully.

146

Deleting EMC-INV-10.03.2.01.0.002.GA.HotFix2.Brocade.Cisco.mif from the RAM DiskSuccess

32. Press the Enter key to continue.

23.7 - Invalidate Data Directory

33. Enter Option 7 to Enable Engineering Mode. CLARiiON Utility Toolkit Main Menu 1) About the Utility Toolkit 2) Reset Storage Processor 3) Image Repository Sub-Menu 4) Plugin Sub-Menu 5) NVRAM Sub-Menu 6) View LAN Service Port Settings 7) Enable Engineering Mode 8) Install Images Enter Option: 7 This is an "Early Access" or General Availability build. The static Engineering Mode password is required.

34. Type “wobat” for the Engineering Mode password and press Enter to continue. Enter the Engineering Mode Password: wobat Engineering Mode has been enabled

35. Enter Option 9 to Invalidate the Data Directory. CLARiiON Utility Toolkit Main Menu 1) About the Utility Toolkit 2) Reset Storage Processor 3) Image Repository Sub-Menu 4) Plugin Sub-Menu

147

5) NVRAM Sub-Menu 6) View LAN Service Port Settings 7) Disable Engineering Mode 8) Install Images 9) Invalidate Data Directory Enter Option: 9 You have chosen to invalidate the Data Directory !!! WARNING !!! Invalidating the Data Directory will PERMANENTLY DESTROY ALL DATA on all bound LUs. The Data Directory should NEVER be invalidated without first escalating to the CLARiiON TS-2 technical support center. Invalidating the Data Directory will permanently destroy information that defines the configuration of this array. All configuration data, including defined storage groups, bound luns, and layered software configuration will be PERMANENTLY DESTROYED by this action. Invalidating the Data Directory without also re-imaging your array's FLARE [tm] Operating Environment partitions will leave your array in a non-functional state. The Peer SP must be removed while the Data Directory is invalidated. Please ensure that SP B is removed before continuing..

36. Type “Yes” and press Enter twice to continue. Are you sure that you want to invalidate the Data Directory? [y/N] : y Are you REALLY sure you want to invalidate the Data Directory? [y/N] : y Invalidating the Data Directory Checking disks for Primary MDDE.... Checking Disk 0_0_0................Present Checking Disk 0_0_1................Present Checking Disk 0_0_2................Present Checking Disk 0_0_3................Present Zeroing Primary MDDE...............Done Checking disks for Secondary MDDE.. Checking Disk 0_0_0................Present Checking Disk 0_0_1................Present Checking Disk 0_0_2................Present Checking Disk 0_0_3................Present Zeroing Secondary MDDE.............Done

37. Press the Enter key to continue

148

38. Reinsert SP B and enter Option 2 to Reset the Storage Processor. CLARiiON Utility Toolkit Main Menu 1) About the Utility Toolkit 2) Reset Storage Processor 3) Image Repository Sub-Menu 4) Plugin Sub-Menu 5) NVRAM Sub-Menu 6) View LAN Service Port Settings 7) Disable Engineering Mode 8) Install Images 9) Invalidate Data Directory Enter Option: 2

24 - CPC Initial Configuration

24.1 - PPP/RAS Connection Configuration

1. Create a PPP/RAS Connection as outlined in Appendix A on pages 133-134 if unfamiliar with the connection creation process. Once created, double click on the Shortcut to launch the connection.

149

2. Provide the proper login credentials (Username = clarion – Password = clarion!) and select the “Connect” icon.

24.2 – SP Configuration

3. Open a Web Browser page and enter https://192.168.1.1/setup to launch the Storage Processor (SP) Configuration Utility.

4. Select “Yes” on the Security Alert to continue.

https://192.168.1.1/setup

150

5. Enter the IP Address, Hostname, Subnet Mask, Gateway, Peer IP Address (SP B) and select “Apply Settings” to commit the configuration.

151

6. You should now be at the Configuration Summary screen. Allow the SP several minutes to reboot until proceeding forward. Next, complete steps 1-6 again to configure SP B.

152

25 - Using the Recovery Kernel to Install the XPath Base Firmware


1. Open a HyperTerminal session to configure, enter the session name and select

the OK icon to continue.


153

3. Select the COM1 Properties for this device (Bits per second = 9600, Data bits = 8, Parity = None, Stop bits = 1 and Flow control = None).

25.2 - Recovery Kernel File System Preparation

154

4. From the Recovery Kernel% prompt, type “mount /” to mount all File Systems.

Recovery Kernel% mount /

5. Type “format all” to format all File Systems. Recovery Kernel% format all format: umount all format: write disklabel format: newfs /root1 (/dev/cf0a) format: newfs /root2 (/dev/cf0e) format: newfs /root1/config (/dev/cf0f) format: newfs /root1/var (/dev/cf0g) format: newfs /thirdparty (/dev/cf0h) format: newfs /root2/config (/dev/cf0i) format: newfs /root2/var (/dev/cf0j) format: mount /root1 format: mount /root1/config format: mount /root1/var format: mount /root2 format: mount /root2/config format: mount /root2/var format: mount /thirdparty

25.3 - FTP Configuration

6. Place the XPath OS to be installed into the FTP directory on an active FTP Server.

25.4 - XPath Download and Installation

7. Type firmwaredownload to start the Firmware Download process.

Recovery Kernel% firmwaredownload

8. Type the FTP Server IP Address. Host name: 10.5.80.38

9. Type the FTP Server username. User name: ftp

155

10. Type the XPath OS Plist file name. Note: A Plist file is a reference file that points to all of the XPath packages.

Plist file name and path: xpath_os_v7.4.0

11. Type the FTP Server password. The XPath download and installation will continue at this point.

Password: password Downloading xpath_os_v7.4.0... Protocol not implemented, use (1,1) Downloading xpath-base-skel-7.4.0-ga_bld05.ppc.rpm... Protocol not implemented, use (1,1) Installing xpath-base-skel-7.4.0-ga_bld05.ppc.rpm to bank 1... xpath-base-skel ################################################## Downloading netbsd-2.0.ga.1-proto1_bld197.ppc.rpm... Protocol not implemented, use (1,1) Installing netbsd-2.0.ga.1-proto1_bld197.ppc.rpm to bank 1... netbsd ################################################## Downloading xpath-base-os-7.4.0-ga_bld05.ppc.rpm... Protocol not implemented, use (1,1) Installing xpath-base-os-7.4.0-ga_bld05.ppc.rpm to bank 1... xpath-base-os ################################################## Downloading xpath-kernel-7.4.0-ga_bld05.ppc.rpm... Protocol not implemented, use (1,1) Installing xpath-kernel-7.4.0-ga_bld05.ppc.rpm to bank 1... xpath-kernel ################################################## Downloading xpath-bootloader-7.4.0-ga_bld05.ppc.rpm... Protocol not implemented, use (1,1) Installing xpath-bootloader-7.4.0-ga_bld05.ppc.rpm to bank 1... xpath-bootloader ################################################## writing silk.loader into bank1. Erasing ................done! .........finished. wrote: 525312 bytes into flash Patch success. Please reboot the switch. Firmware download and install complete: Please reboot to activate Recovery Kernel% reboot Mar 14 12:22:17 reboot: rebooted by root syncing disks... done rebooting..

25.5 - FC Router Main Configuration

12. You will be brought into the factory default router initialization dialog. Type the initial factory login credentials (Username = admin – Password = password). You will then be prompted to change the root, admin and user passwords to a

156

new one. Please change all of them to the Invista standard password of Serv4EMC. Note: All script input is highlighted in red text below.

XPath (switchboard) (tty00) login: admin Password: password login: admin Password: password Please change the system passwords now. Use Control-C to exit or press 'Enter' key to proceed. Change password for user: root New password: Serv4EMC Retype new password: Serv4EMC Changed password for user: root. Change password for user: admin New password: Serv4EMC Retype new password: Serv4EMC Changed password for user: admin. Change password for user: user New password: Serv4EMC Retype new password: Serv4EMC Changed password for user: user. Please remember to config time zone for the switch


MP Router:admin> ipaddrset 1 -i 10.5.80.134 -n 255.255.255.0 -g 10.5.80.1 -a cfgnow Management Ethernet interface configuration for port 1 is set The switch virtual ip is set


MP Router:admin> ipaddrset 2 -i 10.5.80.135 -n 255.255.255.0 -g 10.5.80.1 -a cfgnow Set the switch virtual ip as well (yes, y, no, n): y Management ethernet interface configuration for port 2 is set The switch virtual ip is set

157

15. Run “svipaddrset -i 10.5.80.136 -n 255.255.255.0 -a cfgnow” to configure the IP Address, Subnet Mask and Default Gateway for Virtual Interface 1. All IP access to this router will be accessed through this address.

MP Router:admin> svipaddrset -i 10.5.80.136 -n 255.255.255.0 -a cfgnow The virtual IP configuration of the switch is set

16. Run “ipaddrshow” to confirm the configuration results from steps 13-14. MP Router:admin> ipaddrshow MGMT 1 Configuration Current IP Address 10.5.80.134 10.5.80.134 Net Mask 255.255.255.0 255.255.255.0 Gateway 10.5.80.1 10.5.80.1 MGMT 2 Configuration Current IP Address 10.5.80.135 10.5.80.135 Net Mask 255.255.255.0 255.255.255.0 Gateway 10.5.80.1 10.5.80.1

17. Run “svipaddrshow” to confirm the configuration results from step 15. MP Router:admin> svipaddrshow The switch virtual IP configuration current IP address 10.5.80.136 10.5.80.136 Netmask 255.255.255.0 255.255.255.0 Gateway - 10.5.80.1

18. Run “switchname FX2_FC_SW1” to change the name of this Multi-Protocol Router to FX2_FC_SW1.

MP Router:admin> switchname FX2_FC_SW1

19. Run “switchname” to confirm the configuration results from step 18. FX2_FC_SW1:admin> switchname FX2_FC_SW1

20. Run “timezoneset” to start the timezoneset configuration script. Note: All script input is highlighted in red text below.

FX2_FC_SW1:admin> timezoneset Please select a continent or ocean 1). Africa 2). America 3). Antarctica 4). Arctic Ocean 5). Asia 6). Atlantic Ocean 7). Australia 8). Europe

158

9). Indian Ocean 10). Pacific Ocean 11). US 12). Canada Enter the option #: 2 Please select a country or city 1). Adak 2). Anchorage 3). Anguilla 4). Antigua 5). Araguaina 6). Aruba 7). Asuncion 8). Atka 9). Barbados 10). Belem 11). Belize 12). Boa_Vista 13). Bogota 14). Boise 15). Buenos_Aires 16). Cambridge_Bay 17). Cancun 18). Caracas 19). Catamarca 20). Cayenne 21). Cayman 22). Chicago 23). Chihuahua 24). Cordoba 25). Costa_Rica 26). Cuiaba 27). Curacao 28). Danmarkshavn 29). Dawson 30). Dawson_Creek 31). Denver 32). Detroit 33). Dominica 34). Edmonton 35). Eirunepe 36). El_Salvador 37). Ensenada 38). Fort_Wayne 39). Fortaleza 40). Glace_Bay 41). Godthab 42). Goose_Bay 43). Grand_Turk 44). Grenada 45). Guadeloupe 46). Guatemala 47). Guayaquil 48). Guyana 49). Halifax 50). Havana 51). Hermosillo 52). Indiana 53). Indianapolis 54). Inuvik 55). Iqaluit 56). Jamaica 57). Jujuy 58). Juneau 59). Kentucky 60). Knox_IN 61). La_Paz 62). Lima 63). Los_Angeles 64). Louisville 65). Maceio 66). Managua 67). Manaus 68). Martinique 69). Mazatlan 70). Mendoza 71). Menominee 72). Merida 73). Mexico_City 74). Miquelon 75). Monterrey 76). Montevideo 77). Montreal 78). Montserrat 79). Nassau 80). New_York 81). Nipigon 82). Nome 83). Noronha 84). North_Dakota 85). Panama 86). Pangnirtung 87). Paramaribo 88). Phoenix 89). Port-au-Prince 90). Port_of_Spain 91). Porto_Acre 92). Porto_Velho 93). Puerto_Rico 94). Rainy_River 95). Rankin_Inlet 96). Recife 97). Regina 98). Rio_Branco 99). Rio_Branco 100). Rosario 101). Santiago 102). Santo_Domingo 103). Sao_Paulo 104). Scoresbysund 105). Shiprock 106). St_Johns 107). St_Kitts 108). St_Lucia 109). St_Thomas 110). St_Vincent 111). Swift_Current 112). Tegucigalpa 113). Thule 114). Thunder_Bay 115). Tijuana 116). Tortola 117). Vancouver 118). Virgin 119). Whitehorse 120). Winnipeg 121). Yakutat 122). Yellowknife Enter the option #: 22 time zone is set

25.6 - FC Router License Addition

21. Run “licenseadd (License Key)” to install the appropriate license keys. Licenses are created from EMC based on the Multi-Protocol Router World Wide Name. In this example, we are adding the Storage Application Service (SAS) License which is required for Invista functionality. Note: iSCSI services have been disabled since we added and enabled the SAS License.

FX2_FC_SW1:admin> licenseadd bbRebzee9Sccafcp license bbRebzee9Sccafcp added

159

iSCSI service is disabled on addition of SAS license You have to reboot the system to make the change take effect. Note: Fibre Channel Routing Services and FCIP must be deleted prior to adding the SAS License.

22. Run “licenseshow” to confirm that the SAS License was added from step 21. FX2_FC_SW1:admin> licenseshow License Key: ScSz9RyzReTdT0Aq Web License Key: bde99c9SSzcefAA3 Zoning License Key: R9cRceRSdSAdSdj Base switch license License Key: bbRebzee9SkcSfcp Trunking License Key: bbRebzee9Sccafcp Storage Application Service License Key: bbRebzee9ScsSfcx Ports on Demand - enable all 16 ports

25.7 - FC Router SNMP Configuration

23. Run “agtcfgset” to start the SNMP Configuration Script. The recipient IP Addresses used will be CPC – SP A & SP B. Note: All script input is highlighted in red text below.

FX2_FC_SW1:admin> agtcfgset Customize MIB-II system variables...... At each prompt, do one of following: <return> to accept current value enter the appropriate new value <ctrl-D> to skip the rest of configuration and finish <ctrl-C> to cancel any changes sysDescr: [Connectrix B Application Platform ]

160

sysLocation: [End User Premise. ] sysContact: [Field Support. ] swEventTrapLevel: (0..5) [3 ] SNMP community and trap recipient configuration: You can add maximum 6 trap recipients type <.> at IP address to delete the recipient recipient1--Community [Secret C0de] private recipient1--IP address in dot notion [0.0.0.0] 10.5.80.130 - Note: CPC SP A recipient2--Community [OrigEquipMfr] private recipient2--IP address in dot notion [0.0.0.0] 10.5.80.131 - Note: CPC SP B recipient3--Community [private] public recipient3--IP address in dot notion [0.0.0.0] 10.5.80.130 - Note: CPC SP A recipient4--Community [public] public recipient4--IP address in dot notion [0.0.0.0] 10.5.80.131 - Note: CPC SP B recipient5--Community [common]

24. Run “agtcfgshow” to confirm that the SNMP Configuration was added from step 23.

FX2_FC_SW1:admin> agtcfgshow Current SNMP Agent Configuration Customizable MIB-II system variables: sysDescr = Connectrix B Application Platform sysLocation = End User Premise. sysContact = Field Support. swEventTrapLevel = 3 SNMPv1 Trap Recipient Configuration recipient1--Community=private recipient1--IP address=10.5.80.130 recipient2--Community=private recipient2--IP address=10.5.80.131 recipient3--Community=private No trap recipient configured yet

161

recipient4--Community=public No trap recipient configured yet recipient5--Community=common No trap recipient configured yet recipient6--Community=FibreChannel No trap recipient configured yet

25. Perform the steps from Section 8 “FC Router Operating System Upgrade” to upgrade the XPath OS and XPath SAS Code to the proper Invista code level.

162

Appendix A - Setting Up a Service Laptop Connection to an Invista SP

1. Modem Configuration Settings

If the laptop uses a physical modem, configure the modem for the line characteristics of the SP, as follows:

Line characteristic Setting Data bits 8 Parity None Stop bits 1 Baud rate 115200 baud

2. Setting Up the Dial-Up PPP Support

If a communication cable between two computers is not installed and set up, install it and set it up as follows:

a. Select Start → Settings → Control Panel → Phone and Modem Options.

b. If your laptop has a modem, then under the Modems tab, note below which

port your current modem is using and click Add.

c. Select Don't Detect my Modem; I will select it from a list and click Next.

d. In the Add/Remove Hardware Wizard dialog box that appears, select (Standard Modem Types) under the Manufacturers column.

e. Under the Models column, select Communication cable between two computers and click Next.

f. Under the list On which ports do you want to install it?, click Selected Ports and highlight a port which is not used by the installed modem (port you noted above). Note: The default is COM 1.

g. Click Next.

163

h. On the next screen, click Finish. Click OK.

3. Set Up Dial-Up Networking

a. Select Start → Settings → Control Panel → Network and Dial Up

Connections → Make New Connection.

b. When the Network Connection Wizard starts, click Next to begin.

c. Click Connect directly to another computer and click Next.

d. Select Guest and click Next.

e. In the Select a Device pull-down menu, select Communications between two computers (COM 1) or select COM 2 if the cable is connected to COM 2. Click Next.

f. In the Connection Availability dialog box, select Create this connection: For all users and click Next.

g. In the Completing Network Connection Wizard dialog box, assign the

connection a name (for example, Invista_init) and click Finish.

h. In the Connect dialog box that appears (with the name you assigned to it), click Properties.

i. Under the General tab in the Properties dialog box, click Configure.

j. In the Modem Configuration dialog box, select 115200 bps from the Maximum Speed pull-down list. Verify that the Enable hardware flow control is checked.

k. Click OK to close the dialog box.

l. Click the Networking tab.

PPP: Windows 95/98/NT 4/2000, Internet should appear in the Type of dial-up server I am calling list.

m. Click Settings.

n. Verify that Enable LCP extensions and Enable software compression are

checked, then click OK.

o. Highlight Internet Protocol (TCP/IP) and click Properties. p. Select Obtain an IP Address Automatically and Obtain DNS Server Address

Automatically.

164

q. Click Advanced. Verify that Use IP Header Compression is checked. Deselect Use Default Gateway on Remote Network.

r. Click OK three times to return to the Connect dialog box.

s. Click Cancel to close the Connect dialog box.

Note: These instructions assume that you are starting with SP A. However, you can start the initialization process with either SP.

4. Cable Connection

Connect the NULL Modem cable between the Service Laptop Serial Port (COM 1) and the SP A Service Port (|O|O| on the Invista as identified on Page 5 - 2.3 - CPC Component Layout where SP A/SP B Console Ports have been identified.

Date post:	23-Mar-2020
Category:	Documents
Upload:	others
View:	8 times
Download:	0 times

Invista with Brocade Configuration v.1 - Dell...

Documents