TS3500 and TS7700 checklists
These checklists can help you to collect the information that must be available to configure a TS7740 and TS3500 subsystem. Data, such as IP addresses, cluster numbers, library serial number, tape drive configuration, control paths, physical volume ranges, and logical library names (which must be collected or defined) are listed and correlated to each other in those tables. Work with your IBM support team to sort it out before the actual installation of the TS7740 and TS3500.
A complete set of checklists is available in the Planning section of the TS7700 Virtualization Engine Information Center:
The following checklists are based on the installation instructions for the IBM service support representative (SSR) and provide a practical list of the items to be defined.
This appendix includes the following topics:
TS7700 Virtualization Engine installation worksheets
In Table C-1, the terms Cluster 0, Cluster 1, Cluster 2, Cluster 3, Cluster 4, and Cluster 5 show separated TS7700 Virtualization Engines participating in a multicluster grid configuration. Generally, plan your grid starting from Cluster 0, adding new clusters in ascending order.
For instance, if you are installing a stand-alone TS7700 Virtualization Engine, make it Cluster 0 (and you will only need the information regarding Cluster 0 in the checklist). If new clusters are added, they will be Cluster 1, Cluster 2, and so on.
The checklists show the maximum configuration supported at this time. You only need to fill in the information corresponding to your configuration.
|
Important: There might be additional tape control units, virtual tape subsystems, or open tape drives sharing the same TS3500. Be careful to not disrupt a working environment when checking or configuring the TS3500.
|
Multiple TS7740s can be connected to the same TS3500, as long as each one is assigned to its own logical library in the TS3500.
Grid cluster descriptions
Table C-1 shows the grid cluster descriptions worksheet. Fill out the serial number and a description of each TS7700 Virtualization Engine cluster in your configuration, and the TS3500 attached to each cluster. Complete the “Description of location” column by entering geographical information that is unique to each cluster and library. Enter as much information as necessary to completely identify one machine, such as X-Y coordinates within a data center, room number, floor number, building numbers, city, and so on.
Table C-1 Grid cluster descriptions worksheet
|
Cluster
|
Machine type-model
|
Serial number
|
Description of location
|
|
Cluster 0
|
3957-Vxx
|
|
|
|
Cluster 0
|
3952-F05 (FC7322 Not Encryption Capable) or (FC7331 Encryption Capable)
|
|
|
|
Cluster 0
Optional attachment to a TS7720 Storage Expansion Frame
|
3952-F05 (FC7323 Not Encryption Capable) or (FC7332 Encryption Capable)
|
|
|
|
Cluster 1
|
3957-Vxx
|
|
|
|
Cluster 1
|
3952-F05 (FC7322 Not Encryption Capable) or (FC7331 Encryption Capable)
|
|
|
|
Cluster 1
Optional attachment to a TS7720 Storage Expansion Frame
|
3952-F05 (FC7323 Not Encryption Capable) or (FC7332 Encryption Capable)
|
|
|
|
Cluster 2
|
3957-Vxx
|
|
|
|
Cluster 2
|
3952-F05 (FC7322 Not Encryption Capable) or (FC7331 Encryption Capable)
|
|
|
|
Cluster 2
Optional attachment to a TS7720 Storage Expansion Frame
|
3952-F05 (FC7323 Not Encryption Capable) or (FC7332 Encryption Capable)
|
|
|
|
Cluster 3
|
3957-Vxx
|
|
|
|
Cluster 3
|
3952-F05 (FC7322 Not Encryption Capable) or (FC7331 Encryption Capable)
|
|
|
|
Cluster 3
Optional attachment to a TS7720 Storage Expansion Frame
|
3952-F05 (FC7323 Not Encryption Capable) or (FC7332 Encryption Capable)
|
|
|
|
Cluster 4
|
3957-Vxx
|
|
|
|
Cluster 4
|
3952-F05 (FC7322 Not Encryption Capable) or (FC7331 Encryption Capable)
|
|
|
|
Cluster 4
Optional attachment to a TS7720 Storage Expansion Frame
|
3952-F05 (FC7323 Not Encryption Capable) or (FC7332 Encryption Capable)
|
|
|
|
Cluster 5
|
3957-Vxx
|
|
|
|
Cluster 5
|
3952-F05 (FC7322 Not Encryption Capable) or (FC7331 Encryption Capable)
|
|
|
|
Cluster 5
Optional attachment to a TS7720 Storage Expansion Frame
|
3952-F05 (FC7323 Not Encryption Capable) or (FC7332 Encryption Capable)
|
|
|
TS3500 Tape Library configuration information
Table C-2 shows the TS3500 Tape Library configuration information worksheet. This is a cluster-centric view of all TS3500s within a grid, sorted by the cluster to which each TS3500 is attached. When filling out this table, ensure that you correlate each cluster to its correct physical library, as shown in Table C-1 on page 868.
Table C-2 TS3500 Tape Library configuration information worksheet
|
Field
|
Value
|
Notes
|
|
TS3500 Tape Library Ethernet Network Configuration Method
and
TS3500 Tape Library Ethernet IP Address
Used for TS3500 Tape Library web specialist access
|
Cluster 0 Lib SN:_________
DHCP [ ]
or
Fixed IP [___.___.___.___]
Subnet [___.___.___.___]
Gateway [___.___.___.___]
|
The network configuration method is specified by the your LAN administrator. It is either Fixed IP or Dynamic Host Configuration Protocol (DHCP).
Fixed IP is suggested. The Ethernet ports are 10/100 Mb only.
If the Network Configuration Method is DHCP, this field is not used.
|
|
Cluster 1 Lib SN:__________
DHCP [ ]
or
Fixed IP [___.___.___.___ ]
Subnet [___.___.___.___]
Gateway [___.___.___.___]
|
||
|
Cluster 2 Lib SN:_________ DHCP [ ]
or
Fixed IP [___.___.___.___]
Subnet [___.___.___.___]
Gateway [___.___.___.___]
|
||
|
Cluster 3 Lib SN:_________
DHCP [ ]
or
Fixed IP [___.___.___.___]
Subnet [___.___.___.___]
Gateway [___.___.___.___]
|
||
|
Cluster 4 Lib SN:_________
DHCP [ ]
or
Fixed IP [___.___.___.___]
Subnet [___.___.___.___]
Gateway [___.___.___.___]
|
||
|
Cluster 5 Lib SN:_________
DHCP [ ]
or
Fixed IP [___.___.___.___]
Subnet [___.___.___.___]
Gateway [___.___.___.___]
|
|
|
|
TS3500 Tape Library Ethernet Hostname
|
Cluster 0 LIB:
|
The entry in this field is used to identify the machine in remote support logs.
Even if host names are not typically used, this host name is still required. A typical host name is ATL1. |
|
Cluster 1 LIB:
|
||
|
Cluster 2 LIB:
|
||
|
Cluster 3 LIB:
|
||
|
Cluster 4 LIB:
|
||
|
Cluster 5 LIB:
|
||
|
TS3500 Tape Library Logical Library Name for each TS7740 cluster attachment).
Note that those logical libraries probably belong to separate physical libraries.
|
Cluster 0:
|
Each IBM Virtualization Engine TS7740 must be connected to a single TS3500 Tape Library logical library. This logical library must have a name, which needed to be assigned when the logical library was created. Record the logical library name (assign it if necessary). The logical library name will be needed when performing the following tasks:
•Configuring the logical library
•Obtaining the Starting Element Address for the logical library
•Obtaining the physical position of tape drives within the logical library
•Obtaining the worldwide node names (WWNNs) of those tape drives
•Setting the Cartridge Assignment Policy (CAP)
•Configuring TS3500 IBM Tape Library - Advanced Library Management System (ALMS)
|
|
Cluster 1:
|
||
|
Cluster 2:
|
||
|
Cluster 3:
|
||
|
Cluster 4:
|
||
|
Cluster 5:
|
||
|
Max Cartridges
|
Cluster 0:
|
This value defaults to the number of physical cartridge slots currently installed in the TS3500 Tape Library. You might want to set a different value in the following cases:
•You want to restrict the number of cartridges in the logical library to manage the cost of application licensing.
•The TS3500 Tape Library will be expanded at a later date and you want to avoid reconfiguring the host.
|
|
Cluster 1:
|
||
|
Cluster 2:
|
||
|
Cluster 3:
|
||
|
Cluster 4:
|
||
|
Cluster 5:
|
TS3500 Tape Library drive information worksheet
Table C-3 on page 872 shows the TS3500 Tape Library drive information worksheet. Fill out the assigned tape drives for each cluster.
|
Restriction: A TS7740 cluster must have a minimum of four and maximum of 16 drives that can be connected.
|
List the drives in the worksheet in ascending order by frame and row. This will clarify the drive locations and help you avoid possible mistakes during the installation or troubleshooting.
To obtain the WWNN by using the Operator window in the TS3500, press Menu → Vital Product Data → World Wide Node Names.
Or, to obtain the WWNN by using the TS3500 web interface, click DRIVES → Drive Assignment → World Wide Names.
|
Tip: If possible, distribute tape drives and control paths belonging to a cluster across separate frames in the TS3500. Tape drives can reside in the same frame or within three frames of the 3584-based switches.
|
Table C-3 TS3500 Tape Library drive information worksheet
|
Field
|
Value
|
Notes
|
|
Tape Drive Physical Positions (Fn, Rnn) in the TS3500 Tape Library for the drives assigned to this TS7700 Virtualization Engine.
Mark the drives that will be control paths.
Read the notes in the right column of this table for guidance in filling in the values.
Mark the final two digits of WWNN for each selected drive. Watch out for duplicates.
|
Cluster 0: [3584-Lxx S/N_____]
F=Frame, R=Row, CP=Control Path
1. F____,R____CP: [_]WWNN_____
2. F____,R____CP: [_]WWNN_____
3. F____,R____CP: [_]WWNN_____
4. F____,R____CP: [_]WWNN_____
5. F____,R____CP: [_]WWNN_____
6. F____,R____CP: [_]WWNN_____
7. F____,R____CP: [_]WWNN_____
8. F____,R____CP: [_]WWNN_____
9. F____,R____CP: [_]WWNN_____
10. F____,R____CP: [_]WWNN____
11. F____,R____CP: [_]WWNN____
12. F____,R____CP: [_]WWNN____
13. F____,R____CP: [_]WWNN____
14. F____,R____CP: [_]WWNN____
15. F____,R____CP: [_]WWNN____
16. F____,R____CP: [_]WWNN____
|
List the drives for a stand-alone cluster in order, using the frame and row. The lowest numbered drive needs to be in the lowest numbered frame and row for its assigned drive slots. This is not a requirement, but it might help you to avoid confusion when identifying drives during future troubleshooting.
Distribute the tape drives across the TS3500 Tape Library frames to improve availability. Drives can reside in the same frame as the FC switches or within three frames of the frame containing the switches. Distribute the control paths among those frames.
To obtain the WWNN from the Operator window, press Menu → Vital Product Data → World Wide Node Names.
|
|
Cluster 1: [3584-Lxx S/N_____]
F=Frame, R=Row, CP=Control Path
1. F____,R____CP: [_]WWNN_____
2. F____,R____CP: [_]WWNN_____
3. F____,R____CP: [_]WWNN_____
4. F____,R____CP: [_]WWNN_____
5. F____,R____CP: [_]WWNN_____
6. F____,R____CP: [_]WWNN_____
7. F____,R____CP: [_]WWNN_____
8. F____,R____CP: [_]WWNN_____
9. F____,R____CP: [_]WWNN_____
10. F____,R____CP: [_]WWNN____
11. F____,R____CP: [_]WWNN____
12. F____,R____CP: [_]WWNN____
13. F____,R____CP: [_]WWNN____
14. F____,R____CP: [_]WWNN____
15. F____,R____CP: [_]WWNN____
16. F____,R____CP: [_]WWNN____
|
||
|
|
Cluster 2: [3584-Lxx S/N_____]
F=Frame, R=Row, CP=Control Path
1. F____,R____CP: [_]WWNN_____
2. F____,R____CP: [_]WWNN_____
3. F____,R____CP: [_]WWNN_____
4. F____,R____CP: [_]WWNN_____
5. F____,R____CP: [_]WWNN_____
6. F____,R____CP: [_]WWNN_____
7. F____,R____CP: [_]WWNN_____
8. F____,R____CP: [_]WWNN_____
9. F____,R____CP: [_]WWNN_____
10. F____,R____CP: [_]WWNN____
11. F____,R____CP: [_]WWNN____
12. F____,R____CP: [_]WWNN____
13. F____,R____CP: [_]WWNN____
14. F____,R____CP: [_]WWNN____
15. F____,R____CP: [_]WWNN____
16. F____,R____CP: [_]WWNN____
|
|
|
|
Cluster 3: [3584-Lxx S/N_____]
F=Frame, R=Row, CP=Control Path
1. F____,R____CP: [_]WWNN_____
2. F____,R____CP: [_]WWNN_____
3. F____,R____CP: [_]WWNN_____
4. F____,R____CP: [_]WWNN_____
5. F____,R____CP: [_]WWNN_____
6. F____,R____CP: [_]WWNN_____
7. F____,R____CP: [_]WWNN_____
8. F____,R____CP: [_]WWNN_____
9. F____,R____CP: [_]WWNN_____
10. F____,R____CP: [_]WWNN____
11. F____,R____CP: [_]WWNN____
12. F____,R____CP: [_]WWNN____
13. F____,R____CP: [_]WWNN____
14. F____,R____CP: [_]WWNN____
15. F____,R____CP: [_]WWNN____
16. F____,R____CP: [_]WWNN____
|
|
|
|
Cluster 4: [3584-Lxx S/N_____]
F=Frame, R=Row, CP=Control Path
1. F____,R____CP: [_]WWNN_____
2. F____,R____CP: [_]WWNN_____
3. F____,R____CP: [_]WWNN_____
4. F____,R____CP: [_]WWNN_____
5. F____,R____CP: [_]WWNN_____
6. F____,R____CP: [_]WWNN_____
7. F____,R____CP: [_]WWNN_____
8. F____,R____CP: [_]WWNN_____
9. F____,R____CP: [_]WWNN_____
10. F____,R____CP: [_]WWNN____
11. F____,R____CP: [_]WWNN____
12. F____,R____CP: [_]WWNN____
13. F____,R____CP: [_]WWNN____
14. F____,R____CP: [_]WWNN____
15. F____,R____CP: [_]WWNN____
16. F____,R____CP: [_]WWNN____
|
|
|
|
Cluster 5: [3584-Lxx SN_____]
F=Frame, R=Row, CP=Control Path
1. F____,R____CP: [_]WWNN_____
2. F____,R____CP: [_]WWNN_____
3. F____,R____CP: [_]WWNN_____
4. F____,R____CP: [_]WWNN_____
5. F____,R____CP: [_]WWNN_____
6. F____,R____CP: [_]WWNN_____
7. F____,R____CP: [_]WWNN_____
8. F____,R____CP: [_]WWNN_____
9. F____,R____CP: [_]WWNN_____
10. F____,R____CP: [_]WWNN____
11. F____,R____CP: [_]WWNN____
12. F____,R____CP: [_]WWNN____
13. F____,R____CP: [_]WWNN____
14. F____,R____CP: [_]WWNN____
15. F____,R____CP: [_]WWNN____
16. F____,R____CP: [_]WWNN____
|
|
Media volume serial range
Complete Table C-4 on page 875 using information gathered from the team responsible for the installation of the library or gathered from the management interface (MI). There might be one or many media volume serial ranges, so complete as many rows as apply to your system.
Fill out the cluster numbers, associated volume serial ranges, and media type for each range. Also, fill out the distributed library sequence numbers that are associated to each cluster in the correct field, and the planned home pool for each range (if you want separated pools: If no requirement exists, the default Scratch Pool is 00). You can mark whether encryption will be adopted for an specific pool (not valid for pool 00).
Table C-4 Media volume serial range
|
Cluster
(0 - 6)
|
From
|
To
|
Media type
|
Distributed library
sequence number
|
Home pool
|
Encrypted pool (Y/N)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The fields in Table C-4 contain the following information:
•From, To: This range contains the bar code label VOLSERS of all the cartridges assigned to a single TS7740 Virtualization Engine. For example, if cartridges assigned to a TS7740 Virtualization Engine have bar code labels in the range from A00000JA - A00500JA, record the following information:
– From: A00000
– To: A00500
– Media type: The type is indicated by the last two characters of the 8-character bar code label VOLSER on the cartridges. For example, if the cartridges are labeled 123456JA, the media type is JA. Use these rules:
• JA and JJ tape cartridges are supported and can be mixed in a TS7700 Virtualization Engine. JA and JJ media are supported in “read-only” mode when E07 tape drives are connected to the TS7740.
• JB tape cartridges are also supported (and can be mixed with JA and JJ tape cartridges, except when E07 drives are installed) if all of the tape drives associated with the TS7700 Virtualization Engine are 3952 E05, E06/EU6, or E07 tape drives, and none of them are in J1A emulation mode.
• JC and JK tape cartridges are only supported by E07 drives.
• No other tape types are currently supported for use with the TS7740 Virtualization Engine.
• If there is at least one 3592 model J1A tape drive associated with the TS7740, all 3592 Model E05 tape drives associated with the TS7740 must be in J1A emulation mode.
• If at least one tape cartridge that is associated with a TS7700 Virtualization Engine has been written by a 3592 E05/EU5 tape drive that is not in 3592 J1A emulation mode, the TS7700 Virtualization Engine will no longer support any 3592 J1A Tape Drives or any 3592 E05/EU5 Tape Drive that is in J1A emulation mode. After the 3592 “E05 Native” mode has been used, you cannot return to J1A mode, because the 3592 J1A Tape Drives cannot read or write a tape cartridge written in E05 mode and the TS7700 Virtualization Engine does not currently support mixed 3592 J1A and E05 tape drives unless all E05 Tape Drives are in J1A emulation mode. To use E05 Tape Drives in native mode, the drives must be set to E05 native mode.
• The capacity of a JJ tape cartridge is 60 GB if written by a J1A drive (or an E05 drive working in J1A emulation mode) or 100 GB if written by an E05 drive in native mode. The capacity of a JA tape cartridge is 300 GB if written by a J1A drive (or an E05 drive working in J1A emulation mode) or 500 GB if written by an E05 drive in native mode. The capacity of a JB cartridge is 700 GB if written by an E05 drive that is not in J1A emulation mode, or 1 TB if written by an E06/EU6 drive, or 1.6 TB if written by an E07 drive. The capacity of a JC cartridge is 4 TB if written by an E07 drive. The capacity of a JK cartridge is 500 GB if written by an E07 drive.
• 3592 model E06/EU6 drives cannot be intermixed with 3592 Model J1A, 3592 Model E05, or 3592 Model E07 drives.
• TS7700 Virtualization Engine Feature Code 9900 (Encryption) requires that all tape drives are in E05 native mode. The Encryption feature is not compatible with J1A emulation mode.
Using these rules, determine whether you want the tape drives that are attached to the TS7700 Virtualization Engine to be in J1A emulation mode or in E05 native mode. Record this in the Tape Drive Format entry in Table C-5 on page 877.
•Distributed Library Sequence Number (DLSN): The (Distributed) Library Sequence Number is assigned by your administrator. This five-character name is used as an identifier for a specific cluster and the associated library and grid configuration. This identifier is specified in the TS7700 Virtualization Engine configuration. It is required even if the TS7700 Virtualization Engine is not in a grid configuration.
|
Important: Each TS7700 Virtualization Engine cluster must have a single, unique value for the DLSN. For the TS7700 Virtualization Engine, a typical value is the last five digits of the 3952-F05 Frame serial number.
|
•Home pool (also called scratch pool): You might have assigned a home pool value. If one has not been set, the default value is 00.
|
Clarification: A pool is a group of physical tape cartridges. A scratch pool is a group of cartridges that are considered to be scratch, which means that they are ready for use by any write job.
|
•Encrypted pool: Encryption can be controlled by pools. If you want, mark the pool enabled for encryption.
|
Restriction: Certain requirements must be met before enabling encryption. See the TS7700 Virtualization Engine Information Center, Chapter 5, “Hardware implementation” on page 189, and Chapter 6, “Software implementation” on page 285 for more details about encryption.
|
TS7700 Virtualization Engine configuration information
Table C-5 shows the TS7700 Virtualization Engine configuration information worksheet. Fill in the required information in the correct fields:
•Library Sequence Numbers (composite and distributed)
•IP addresses (virtual, primary, alternate, and Network Time Protocol (NTP))
•Subnet mask
•Gateway
•Tape drive format
•Network speed settings
Table C-5 TS7700 Virtualization Engine configuration information worksheet
|
Field
|
Value
|
Notes
|
|
Composite Library Sequence Number
|
|
This five-character name must be the same on all clusters (peers) within the same grid. This identifier is specified in the TS7700 Virtualization Engine configuration. It is required even if the machine is not in a grid configuration.
The Composite Library Sequence Number must differ from the distributed library sequence number specified.
|
|
Distributed Library Sequence Number
|
Cluster 0: ____________
|
The Distributed Library Sequence Number is assigned by the your administrator. This is a five-hex character name that is used as an identifier for a specific cluster. Each TS7740 Virtualization Engine must have a single, unique value for the Distributed Library Sequence Number. For the TS7740 Virtualization Engine, a typical value is the last five digits of the 3952-F05 Frame serial number.
The Distributed Library Sequence Number must differ from the composite library sequence number specified.
|
|
Cluster 1: ____________
|
||
|
Cluster 2: ______________
|
||
|
Cluster 3: ______________
|
||
|
Cluster 4: ______________
|
||
|
Cluster 5: ______________
|
||
|
Customer IP 1 (Virtual)
|
Cluster 0: ____.____.____.____
|
Used for TS7700 Virtualization Engine web MI.
This number is a virtual IP that is not associated with a physical cable. It communicates through the Primary IP, and automatically fails over to the Alternate IP when required.
|
|
Cluster 1: ____.____.____.____
|
||
|
Cluster 2: ____.____.____.____
|
||
|
Cluster 3: ____.____.____.____
|
||
|
Cluster 4:
____.____.____.____
|
||
|
Cluster 5:
____.____.____.____
|
||
|
Customer IP 2
(Primary)
|
Cluster 0: ____.____.____.____
|
This is the IP address used to connect to the TS7700 Virtualization Engine through the internal primary network. This IP address must not be used unless the Virtual IP is inaccessible.
Note: On a V06 and VEA, the customer IP (for web MI) must be 10/100 Mb/s connection speed. On a V07 or VEB, the customer IPs are capable of 1000 Mb/s.
|
|
Cluster 1: ____.____.____.____
|
||
|
Cluster 2: ____.____.____.____
|
||
|
Cluster 3: ____.____.____.____
|
||
|
Cluster 4:
____.____.____.____
|
||
|
Cluster 5:
____.____.____.____
|
||
|
Customer IP 3
(Alternate)
|
Cluster 0: ____.____.____.____
|
This IP address is used to connect to the TS7700 Virtualization Engine through the internal alternate network. This IP address must not be used unless the Virtual IP is inaccessible.
Note: On a V06 and VEA, the customer IP (for web MI) must be 10/100 Mb/s connection speed. On a V07 or VEB, the customer IPs are capable of 1000 Mb/s.
|
|
Cluster 1: ____.____.____.____
|
||
|
Cluster 2: ____.____.____.____
|
||
|
Cluster 3:
____.____.____.____
|
||
|
Cluster 4:
____.____.____.____
|
||
|
Cluster 5:
____.____.____.____
|
||
|
Customer Gateway
|
Cluster 0: ____.____.____.____
|
This is used with the virtual, primary, and alternate IP addresses.
|
|
Cluster 1: ____.____.____.____
|
||
|
Cluster 2: ____.____.____.____
|
||
|
Cluster 3: ____.____.____.____
|
||
|
Cluster 4: ____.____.____.____
|
||
|
Cluster 5: ____.____.____.____
|
||
|
Customer Subnet Mask
|
Cluster 0: ____.____.____.____
|
This is used with the virtual, primary, and alternate IP addresses.
|
|
Cluster 1: ____.____.____.____
|
||
|
Cluster 2: ____.____.____.____
|
||
|
Cluster 3: ____.____.____.____
|
||
|
Cluster 4: ____.____.____.____
|
||
|
Cluster 5: ____.____.____.____
|
||
|
NTP server IP address (if used)
Using the NTP server ensures that all components have consistent time settings.
|
____.____.____.____
|
The TCP/IP address you obtain from the customer is either the NTP server at the customer site (if the customer maintains one locally), or an Internet server. Use of an Internet server assumes that the customer allows access to the Internet on the NTP services port (TCP/IP port 123).
|
|
Tape Drive Format
|
Cluster 0:
J1A Emulation Mode [_]
E05 Native Mode [_]
E06/EU6 Mode [_]
E07 Mode [_]
|
To determine whether to use J1A emulation mode, E05 native, E06/Eu6, or E07 modes, see the rules listed in the media type field notes under Table C-4 on page 875.
|
|
Cluster 1:
J1A Emulation Mode [_]
E05 Native Mode [_]
E06/EU6 Mode [_]
E07 Mode [_]
|
||
|
Cluster 2:
J1A Emulation Mode [_]
E05 Native Mode [_]
E06/EU6 Mode [_]
E07 Mode [_]
|
||
|
Cluster 3:
J1A Emulation Mode [_]
E05 Native Mode [_]
E06/EU6 Mode [_]
E07 Mode [_]
|
||
|
Cluster 4:
J1A Emulation Mode [_]
E05 Native Mode [_] E06/EU6 Mode [_]
E07 Mode [_]
|
||
|
Cluster 5:
J1A Emulation Mode []
E05 Native Mode [_]
E06/EU6 Mode [_]
E07 Mode [_]
|
Grid local address
The following notes apply to Table C-6 on page 881 and Table C-7 on page 882:
•If the TS7700 Virtualization Engine that you are installing is a stand-alone machine (not part of a grid configuration), leave Table C-6 on page 881 and Table C-7 on page 882 blank.
•The grid interfaces are the Gb Internet connections between clusters, allowing them to automatically remain in sync.
•IBM strongly recommends that the primary and alternate Grid interfaces be on separate subnets. If the Grid interfaces are directly connected (without using Ethernet switches), using separate subnets is required.
The grid interfaces require connections using the following TCP/IP ports:
•Internet Control Message Protocol (ICMP)
•7 (Ping)
•9 (Discard Service - for bandwidth measuring tools)
•123 (Network Time Protocol)
•350 (Distributed library to distributed library file transfer)
•1415/1416 (WebSphere message queues grid to grid)
•80: Remote management interface (Remote MI)
•433: Management interface (MI)
The following TCP/IP ports are also useful in service scenarios if allowed:
•20 (FTP)
•21 (FTP)
•23 (Telnet)
Table C-6 Grid local address
|
Field
|
Value
|
Notes
|
|
Primary Grid Interface IP address
|
Cluster 0
I/P: ___.___.___.___
Subnet: ___.___.___.___
Gateway: ___.___.___.___
|
The Primary Grid Interface is the 1 Gb Ethernet Adapter located in slot C4 of the 3957-V06
or
Drawer 0, Slot 1, Port 0 for the 3957-V07 machine.
The Primary Grid Interface at each cluster will connect to the Primary Grid Interface at each of the other clusters in the same grid.
If a gateway is not used, leave this field blank.
If using a direct connection, you must not specify a gateway.
|
|
Cluster 1
I/P: ___.___.___.___
Subnet: ___.___.___.___
Gateway: ___.___.___.___
|
||
|
Cluster 2
I/P: ___.___.___.___
Subnet: ___.___.___.___
Gateway: ___.___.___.___
|
||
|
Cluster 3
I/P: ___.___.___.___
Subnet: ___.___.___.___
Gateway: ___.___.___.___
|
||
|
Cluster 4
I/P: ___.___.___.___
Subnet: ___.___.___.___
Gateway: ___.___.___.___
|
||
|
Cluster 5
I/P: ___.___.___.___
Subnet: ___.___.___.___
Gateway: ___.___.___.___
|
||
|
Alternate Grid Interface IP address
|
Cluster 0
I/P: ___.___.___.___
Subnet: ___.___.___.___
Gateway: ___.___.___.___
|
The Alternate Grid Interface is the 1 Gb Ethernet Adapter located in slot C4 of the 3957-V06
or
Drawer 1, Slot 1, Port 0 for the 3957-V07 machine.
The Alternate Grid Interface at each cluster will connect to the Alternate Grid Interface at each of the other clusters in the same grid.
If a gateway is not used, leave this field blank.
If using a direct connection, you must not specify a gateway.
|
|
Cluster 1
I/P: ___.___.___.___
Subnet: ___.___.___.___
Gateway: ___.___.___.___
|
||
|
Cluster 2
I/P: ___.___.___.___
Subnet: ___.___.___.___
Gateway: ___.___.___.___
|
||
|
Cluster 3
I/P: ___.___.___.___
Subnet: ___.___.___.___
Gateway: ___.___.___.___
|
||
|
Cluster 4
I/P: ___.___.___.___
Subnet: ___.___.___.___
Gateway: ___.___.___.___
|
||
|
Cluster 5
I/P: ___.___.___.___
Subnet: ___.___.___.___
Gateway: ___.___.___.___
|
For a 3957-V07 with dual-ported GRID adapters and FC1034 (which enables the second port for the 1 GB copper or fiber grid adapters), fill out the tables corresponding to the third and fourth grid links (Table C-7).
Table C-7 Third and Fourth Grid links
|
Third Grid Interface IP address
|
Cluster 0
I/P: ___.___.___.___
Subnet: ___.___.___.___
Gateway: ___.___.___.___
|
The Third Grid Interface is the 1 Gb Ethernet Adapter located in Drawer 0, Slot 1, Port 1, only in 3957-V07 machine.
The Third Grid Interface at each cluster will connect to the Third Grid Interface at each of the other clusters in the same grid.
If a Gateway is not used, leave this field blank.
If using a direct connection, you must not specify a Gateway.
|
|
|
Cluster 1
I/P: ___.___.___.___
Subnet: ___.___.___.___
Gateway: ___.___.___.___
|
|
|
Cluster 2
I/P: ___.___.___.___
Subnet: ___.___.___.___
Gateway: ___.___.___.___
|
||
|
|
Cluster 3
I/P: ___.___.___.___
Subnet: ___.___.___.___
Gateway: ___.___.___.___
|
|
|
Cluster 4
I/P: ___.___.___.___
Subnet: ___.___.___.___
Gateway: ___.___.___.___
|
||
|
Cluster 5
I/P: ___.___.___.___
Subnet: ___.___.___.___
Gateway: ___.___.___.___
|
|
Fourth Grid Interface IP address
|
Cluster 0
I/P: ___.___.___.___
Subnet: ___.___.___.___
Gateway: ___.___.___.___
|
The Fourth Grid Interface is the 1 Gb Ethernet Adapter located in Drawer 1, Slot 1, Port 1, only in 3957-V07 machine.
The Fourth Grid Interface at each cluster will connect to the Fourth Grid Interface at each of the other clusters in the same grid.
If a Gateway is not used, leave this field blank.
If using a direct connection, you must not specify a Gateway.
|
|
Cluster 1
I/P: ___.___.___.___
Subnet: ___.___.___.___
Gateway: ___.___.___.___
|
|
|
|
Cluster 2
I/P: ___.___.___.___
Subnet: ___.___.___.___
Gateway: ___.___.___.___
|
||
|
Cluster 3
I/P: ___.___.___.___
Subnet: ___.___.___.___
Gateway: ___.___.___.___
|
||
|
Cluster 4
I/P: ___.___.___.___
Subnet: ___.___.___.___
Gateway: ___.___.___.___
|
||
|
Cluster 5
I/P: ___.___.___.___
Subnet: ___.___.___.___
Gateway: ___.___.___.___
|
||
|
|
|
|
TSSC grid configuration information
The following notes apply to Table C-8:
•If the TS7700 Virtualization Engine that you are installing is a stand-alone machine (not part of a grid configuration), leave the table blank.
•If you will be using the grid in a Cascade Deferred style, you do not need the Autonomic Ownership Takeover Manager (AOTM) and you can leave the table blank.
|
Clarification: Cascade Deferred means one or more clusters do not have host FICON connections enabled in normal operation. There is no need to use AOTM on a cluster that does not have host FICON connections enabled in normal operation.
|
•If you plan to use AOTM, contact your IBM SSR for the preparation and configuration.
•If you do not want to use AOTM, leave the table blank.
•The TSSC Grid Interface is only used for the AOTM.
•Each cluster can be configured to use AOTM to provide ownership takeover for one cluster.
The AOTM requires the following TCP/IP ports:
•7 (Ping)
•80 (HTTP)
Table C-8 TSSC grid configuration information
|
Field
|
Value
|
Notes
|
|
TSSC Grid Interface IP Address
|
Cluster 0: ____.____.____.____
|
The TSSC Grid Interface is used to allow the TSSC at one cluster to communicate with the TSSC at one other cluster. This is required if AOTM will be used.
|
|
|
Cluster 1: ____.____.____.____
|
|
|
|
Cluster 2: ____.____.____.____
|
|
|
|
Cluster 3: ____.____.____.____
|
|
|
|
Cluster 4: ____.____.____.____
|
|
|
|
Cluster 5: ____.____.____.____
|
|
|
TSSC Grid Interface Subnet Mask
|
Cluster 0: ____.____.____.____
|
Specify the subnet mask to use with the grid interface IP address.
|
|
|
Cluster 1: ____.____.____.____
|
|
|
|
Cluster 2: ____.____.____.____
|
|
|
|
Cluster 3: ____.____.____.____
|
|
|
|
Cluster 4: ____.____.____.____
|
|
|
|
Cluster 5: ____.____.____.____
|
|
|
TSSC Grid Interface Gateway
|
Cluster 0: ____.____.____.____
|
Specify the gateway IP address to use with the grid interface IP addresses.
|
|
|
Cluster 1: ____.____.____.____
|
|
|
|
Cluster 2: ____.____.____.____
|
|
|
|
Cluster 3: ____.____.____.____
|
|
|
|
Cluster 4: ____.____.____.____
|
|
|
|
Cluster 5: ____.____.____.____
|
|
|
Takeover Mode
|
Cluster 0:
DISABLED [_]
ROT [_]
WOT [_]
|
The Takeover Modes are DISABLED, Read Ownership Takeover (ROT), or Write Ownership Takeover (WOT). When DISABLED, no auto takeover is allowed. ROT only allows the local cluster to read but not write to volumes to the remote cluster. WOT allows the local cluster to read or write to any volumes it takes over from the remote cluster. ROT is suggested, because it automatically gives you read access to any consistent copies of data without any requirement for manual intervention during reconnection after the failed cluster is repaired. WOT is appropriate if your application must be able to update existing logical volumes, but it can cause different copies of a logical volume to be inconsistent, requiring manual intervention during reconciliation after the failed cluster is repaired.
|
|
|
Cluster 1:
DISABLED [_]
ROT [_]
WOT [_]
|
|
|
|
Cluster 2:
DISABLED [_]
ROT [_]
WOT [_]
|
|
|
|
Cluster 3:
DISABLED [_]
ROT [_]
WOT [_}
|
|
|
|
Cluster 4:
DISABLED [_]
ROT [_]
WOT [_]
|
|
|
|
Cluster 5:
DISABLED [_]
ROT [_]
WOT [_]
|
|
|
Grace Period (Minutes)
|
Cluster 0:
|
When a cluster detects that another cluster in the same grid has failed, it will wait for the number of minutes specified as the Grace Period before it attempts to take over the volumes of the failed cluster. A typical Grace Period is 25 minutes.
|
|
|
Cluster 1:
|
|
|
|
Cluster 2:
|
|
|
|
Cluster 3:
|
|
|
|
Cluster 4:
|
|
|
|
Cluster 5:
|
|
|
Retry Period (Minutes)
|
Cluster 0:
|
The retry period is the number of minutes between attempts to take over ownership of the volumes associated with a failed cluster. A typical Retry Period is five minutes. In most cases, this will be the same for both clusters.
|
|
|
Cluster 1:
|
|
|
|
Cluster 2:
|
|
|
|
Cluster 3:
|
|
|
|
Cluster 4:
|
|
|
|
Cluster 5:
|
|
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.