Planning for new system arrival (customer tasks)

Use this section to locate and collect information required to install a TS7700.

As you plan for the installation of your new system, consult the following tables and consider the values that you would provide to match the information listed in the Field column. This information will be used to install your TS7700 and as reference during any future service actions. If you are working from an electronic copy of this information center, consider printing this topic to use it as a working document.

Before the service support representative (SSR) arrives, you should complete the Systems Assurance Worksheets. You can get the Systems Assurance Worksheets from your marketing representative or from your Field Technical Support Specialist.

The Systems Assurance Worksheets are similar to Table 1 through Table 24.

Important: The information that is requested in the tables should be completed before the arrival of the SSR. This information is used by the SSR to perform installation tasks. The pre-installation information should be recorded in tables in the following sections:

Cluster Description Table and Notes (Table 1)
TS3500 or TS4500 Tape Library Configuration Information Table and Notes (Table 2)
TS3500 or TS4500 Tape Library Drive Information Table and Notes (Table 3)
TS3500 Limited Drive Support Table (Table 5)
Media Volume Serial (VOLSER) Range Table and Notes (Table 7)
Encryption Key Information Table (Table 8)
TS4500 Limited Drive Support Table (Table 9)
Review media types in 3592 Tape Cartridges
TS7700 Code Activation/VPD Information Table and Notes (Table 11)
TS7700 Customer Network Configuration Table and Notes (Table 12)
TSSC Configuration Information Table and Notes (Table 13)
Grid Local Address Table and Notes (Table 22)
Summary Table (Table 23)
TSSC Grid Configuration Information Table and Notes (Table 24)

After you complete the Systems Assurance Worksheets, ensure that you store the Worksheets with the TS7700 so the worksheets are available for future service calls.

Cluster Descriptions

Complete the Description of Location column with geographical information that is unique to each cluster. Complete as much information as possible. Some suggestions for descriptions are the x, y coordinates within a data center, room number, floor number, building number, city, and so on.

If you are installing a stand-alone (non-GRID) TS7700, then choose a cluster number designation 0 - 7 and complete the cluster j information, but leave the other cluster fields blank.
If you are joining to an existing stand-alone cluster to create a two cluster GRID TS7700, then complete the cluster j (new joining cluster) and cluster x (existing cluster) information, but leave the remaining cluster fields blank.
If you are installing a three-cluster GRID TS7700, then complete the Cluster 0, Cluster 1, and Cluster 2 information but leave the Cluster 3, Cluster 4, Cluster 5, Cluster 6, and Cluster 7 fields blank.
If you are installing a four-cluster GRID TS7700, then complete the Cluster 0, Cluster 1, Cluster 2, and Cluster 3 information but leave the Cluster 4, Cluster 5, Cluster 6, and Cluster 7 fields blank.
If you are installing a five-cluster GRID TS7700, then complete the Cluster 0, Cluster 1, Cluster 2, Cluster 3, and Cluster 4 information but leave the Cluster 5, Cluster 6, and Cluster 7 fields blank. An RPQ is required for a grid of five or more clusters.
If you are installing a six-cluster GRID TS7700, then complete the Cluster 0, Cluster 1, Cluster 2, Cluster 3, Cluster 4, and Cluster 5 information. Leave the Cluster 6 and Cluster 7 fields blank. An RPQ is required for a grid of five or more clusters.
If you are installing a seven-cluster GRID TS7700, complete the Cluster 0, Cluster 1, Cluster 2, Cluster 3, Cluster 4, Cluster 5, and Cluster 6 information. Leave the Cluster 7 field blank. An RPQ is required for a grid of five or more clusters.
If you are installing an eight-cluster GRID TS7700, complete the Cluster 0, Cluster 1, Cluster 2, Cluster 3, Cluster 4, Cluster 5, Cluster 6, and Cluster 7 information. An RPQ is required for a grid of five or more clusters.

Note: The terms CLUSTER 0, CLUSTER 1, CLUSTER 2, CLUSTER 3, CLUSTER 4, CLUSTER 5, CLUSTER 6, and CLUSTER 7 refer to eight separate TS7760s, or TS7760TAs participating in a GRID (peer to peer) configuration, but you can have a mix (hybrid) configuration of TS7770, TS7760, TS7770T and TS7760 Tape Attach. The cluster number identifiers in a grid must be unique but they do not need to be in a specific order. For example, you might have a 3-way grid that is composed of CLUSTER 2, CLUSTER 3, and CLUSTER 6. In choosing a cluster number identifier, it is important for the customer to plan for future configurations. For example, the customer might set up two 2-way grids and assign cluster identifiers of CLUSTER 0 and CLUSTER 1 for grid-A and CLUSTER 2 and CLUSTER 3 for grid-B. Eventually, the customer might plan on merging the two grids to create a four-way grid that is composed of CLUSTER 0-3. Advanced planning removes extra steps in a grid merge process.

For 3-way or higher configurations, the customer can make use of cluster families. The customer will have the ability to group two or more clusters together into a family. Clusters within a family will then cooperate with each other in order to most efficiently bring copies into their cluster family. At any one time, only one cluster within a family will copy a volume into a family group from an external family. If a copy already exists on at least one cluster within the family, replication among clusters in the family is deferred for that volume. Once all volumes external to the family exist within at least one of the clusters in the family, the clusters will then replicate among each other in order to be brought up to consistency. (The copies between family members will actually start if there are available copy tasks that are not tied up with remote copies, that is, there are less than 20 remote copies remaining). This provides improved copy performance based on using additional copy task within the family to pull copies into the family. This might be configured by the customer from the management interface after some performance runs.

Provide the serial number and location of the machines that make up each cluster. The information in Table 1 helps the installer know which TS7700 is designated as Cluster 0, which is Cluster 1, which is Cluster 2, which is Cluster 3, which is Cluster 4, which is Cluster 5, which is Cluster 6, and which is Cluster 7.

Table 1. Cluster Description Table and Notes
Cluster	Component Serial Numbers	Description of Location
Cluster 0	3948-Vxx or 3957-Vxx:
	3948 F0x or 3952 F0x:
	3948-F0x or 3952-F0x : Optional attachment to a TS7700 Storage Expansion Frame:
	3948-F0x or 3952-F0x : Optional attachment to a TS7700 Storage Expansion Frame:
	3584 Lxx: (if installing a TS7700 with tape attached)
Cluster 1	3948-Vxx or 3957-Vxx:
	3948-F0x or 3952-F0x:
	3948-F0x or 3952-F0x : Optional attachment to a TS7700 Storage Expansion Frame:
	3948-F0x or 3952-F0x : Optional attachment to a TS7700 Storage Expansion Frame:
	3584 Lxx: (if installing a TS7700 with tape attached)
Cluster 2	3948-Vxx or 3957-Vxx:
	3948 F0x or 3952 F0x:
	3948-F0x or 3952-F0x : Optional attachment to a TS7700 Storage Expansion Frame:
	3948-F0x or 3952-F0x : Optional attachment to a TS7700 Storage Expansion Frame:
	3584 Lxx: (if installing a TS7700 with tape attached)
Cluster 3	3948-Vxx or 3957-Vxx:
	3948 F0x or 3952 F0x:
	3948-F0x or 3952-F0x : Optional attachment to a TS7700 Storage Expansion Frame:
	3948-F0x or 3952-F0x : Optional attachment to a TS7700 Storage Expansion Frame:
	3584 Lxx: (if installing a TS7700 with tape attached)
Cluster 4	3948-Vxx or 3957-Vxx:
	3948 F0x or 3952 F0x:
	3948-F0x or 3952-F0x : Optional attachment to a TS7700 Storage Expansion Frame:
	3948-F0x or 3952-F0x : Optional attachment to a TS7700 Storage Expansion Frame:
	3584 Lxx: (if installing a TS7700 with tape attached)
Cluster 5	3948-Vxx or 3957-Vxx:
	3948 F0x or 3952 F0x:
	3948-F0x or 3952-F0x : Optional attachment to a TS7700 Storage Expansion Frame:
	3948-F0x or 3952-F0x: Optional attachment to a TS7700 Storage Expansion Frame:
	3584 Lxx: (if installing a TS7700 with tape attached)
Cluster 6	3948-Vxx or 3957-Vxx:
	3948 F0x or 3952 F0x:
	3948-F0x or 3952-F0x : Optional attachment to a TS7700 Storage Expansion Frame:
	3948-F0x or 3952-F0x : Optional attachment to a TS7700 Storage Expansion Frame:
	3584 Lxx: (if installing a TS7700 with tape attached)
Cluster 7	3948-Vxx or 3957-Vxx:
	3948 F0x or 3952 F0x:
	3948-F0x or 3952-F0x : Optional attachment to a TS7700 Storage Expansion Frame:
	3948-F0x or 3952-F0x : Optional attachment to a TS7700 Storage Expansion Frame:
	3584 Lxx: (if installing a TS7700 with tape attached)

Tape Library Attachment Configuration.

Provide values for each of the TS3500 or TS4500 configuration fields defined in Table 2 and Table 3. Required information includes:

Network Ethernet configuration method
Network Ethernet IP address for TS3500 or TS4500 management GUI access
TS3500 or TS4500 Ethernet hostname
Network Ethernet gateway
Network Ethernet subnet mask
Maximum number of physical cartridges
Logical library name for the TS3500 or TS4500
Physical position and World Wide Node Name (WWNN) of each drive in the TS3500 or TS4500, according to cluster

Table 2. TS3500 or TS4500 Tape Library Configuration Information Table and Notes
Field	Value	Notes
TS3500 or TS4500 Tape Library Serial Number	CLUSTER 0 - 7	The serial number of the TS3500 or TS4500 Tape Library model Lxx (frame 1) is a 7 character serial number consisting of the 2-digit Plant of Mfg code and the 5 character sequence number. It can be found on the back door of the TS3500 or TS4500 Tape Library Lxx frame, or by viewing library Vital Product Data (VPD) on the library operator panel or web user interface.
TS3500 or TS4500 Tape Library Ethernet Network Configuration Method (customer network) Library Type:	CLUSTER 0: DHCP [ ] Fixed IP [ ]	The network configuration method is specified by the customer's LAN administrator. It is either Fixed IP or Dynamic Host Configuration Protocol (DHCP). Note: Fixed IP is recommended.
	CLUSTER 1: DHCP [ ] Fixed IP [ ]
	CLUSTER 2: DHCP [ ] Fixed IP [ ]
	CLUSTER 3: DHCP [ ] Fixed IP [ ]
	CLUSTER 4: DHCP [ ] Fixed IP [ ]
	CLUSTER 5: DHCP [ ] Fixed IP [ ]
	CLUSTER 6: DHCP [ ] Fixed IP [ ]
	CLUSTER 7: DHCP [ ] Fixed IP [ ]
TS3500 or TS4500 Tape Library Ethernet IP address (customer network) (Used for Web interface access)	CLUSTER 0: _ _ _._ _ _._ _ _._ _ _	If Network Configuration Method is DHCP, then this field is not used. Note: The Ethernet ports are 10/100 Mb only.
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _
TS3500 or TS4500 Tape Library Ethernet Hostname	CLUSTER 0: _ _ _._ _ _._ _ _._ _ _	The entry in this field is used to identify the machine in remote support logs. Note: Even if hostnames are not typically used by the customer, this hostname is still required. A typical hostname is ATL1.
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _
TS3500 or TS4500 Tape Library Ethernet Subnet Mask (customer network)	CLUSTER 0: _ _ _._ _ _._ _ _._ _ _	If Network Configuration Method is DHCP, then this field is not used.
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _
TS3500 or TS4500 Tape Library Ethernet Gateway (customer network)	CLUSTER 0: _ _ _._ _ _._ _ _._ _ _	If Network Configuration Method is DHCP, then this field is not used.
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _
TS3500 or TS4500 Tape Library Logical Library Name (for TS7700 attachment)		Each TS7700 must be connected to a single TS3500 or TS4500 tape library logical library. This logical library must have a name, which should have been assigned when the logical library was created. Record the logical library name (assign it if necessary). The logical library name is needed to perform 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 WWNNs of those tape drives Setting the Cartridge Assignment Policy Configuring Control paths Setting Exports to Show (default) Setting Encryption method if necessary Configuring ALMS
Max Cartridges		This value defaults to the number of physical cartridge slots that are currently installed in the TS3500 or TS4500 tape library. Valid values range 1 - 6260. You might want to set a different value in the following cases: The customer wants to restrict the number of cartridges in the logical library to manage the cost of application licensing. The TS3500 or TS4500 tape library will be expanded later and you want to avoid reconfiguring the host then.

Notes:

A TS7700 cluster must have a minimum of 4 and maximum of 16 tape drives that can be connected.
It is recommended that the drives for a single TS7700 are listed in order by using the frame and row. As an example, if a TS7700 has eight drives that are in F4,R01 - F4,R08, then drive 1 should be F4,R01, drive 2 should be F4,R02, and so on. If a second TS7700 has four drives in F2,R11, F2,R12, F3R1, and F3R2, then drive 1 should be F2,R11, drive 2 should be F2,R12, drive 3 should be F3,R01, and drive 4 should be F3,R02. This is not a requirement, but it might help avoid confusion when identifying drives during future troubleshooting.
Distributing the tape drives across 2 TS3500 or TS4500 frames is recommended to improve availability. Placing up to eight drives (two control path drives) in one frame and up to eight drives (two control path drives) in a second frame is recommended.

TS3500 or TS4500 Tape Library Drive Information Table and Notes

Table 3. TS3500 or TS4500 Tape Library Drive Information Table and Notes
Field	Values
Tape Drive Physical Positions (Fn,Rnn) in the TS3500 or TS4500 tape library for the drives that are assigned to each 3948-Vxx or 3957-Vxx . Record the physical position and the last two digits of the World Wide Node Name (WWNN) for each tape drive. Circle the drives that will be control paths. Read the notes below this table for guidance in completing the values.	CLUSTER 0: F=Frame, C=Column, R=Row WWNN=World Wide Node Name Note: For the TS3500 tape library, complete F (Frame) and R (Row) only. F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___	CLUSTER 1: F=Frame, C=Column, R=Row WWNN=World Wide Node Name Note: For the TS3500 tape library, complete F (Frame) and R (Row) only. F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___
	CLUSTER 2: F=Frame, C=Column, R=Row WWNN=World Wide Node Name	CLUSTER 3: F=Frame, C=Column, R=Row WWNN=World Wide Node Name
	Note: For the TS3500 tape library, complete F (Frame) and R (Row) only. F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___	Note: For the TS3500 tape library, complete F (Frame) and R (Row) only. F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___
	CLUSTER 5: F=Frame, C=Column, R=Row WWNN=World Wide Node Name Note: For the TS3500 tape library, complete F (Frame) and R (Row) only. F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___	CLUSTER 6: F=Frame, C=Column, R=Row WWNN=World Wide Node Name Note: For the TS3500 tape library, complete F (Frame) and R (Row) only. F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___ F___C___R___WWNN___

Notes:

A TS7700 cluster must have a minimum of 4 and maximum of 16 tape drives that can be connected.
It is recommended that the drives for a single TS7700 attached to a TS3500 are listed in order by using the frame and row. As an example, if a TS7700 has eight drives that are in F4,R01 - F4,R08, then drive 1 should be F4,R01, drive 2 should be F4,R02, and so on. If a second TS7700 has four drives in F2,R11, F2,R12, F3R1, and F3R2, then drive 1 should be F2,R11, drive 2 should be F2,R12, drive 3 should be F3,R01, and drive 4 should be F3,R02. This is not a requirement, but it might help avoid confusion when identifying drives during future troubleshooting.
Distributing the tape drives across two TS3500 or TS4500 frames is recommended to improve availability. Placing up to eight drives (two control path drives) in one frame and up to eight drives (two control path drives) in a second frame is recommended.

To obtain the WWNN, press Menu > Vital Product Data > World Wide Node Names.

Media Volume Serial (VOLSER) Range Table and Notes

Complete Table 7 with the requested information. There might be one or many Media Volume Serial Ranges so complete as many rows as apply to your system.

From, To

This is a range containing the bar code label VOLSERs of all the cartridges assigned to a single TS7700. As an example, if cartridges assigned to a TS7700 have bar code labels in the range from A00000JA - A00500JA, then record the following:

From: __A00000_
To:__A00500

Media Type

The type is indicated by the last two characters of the 8character bar code label VOLSER on the cartridges. As an example, if the cartridges are labeled 123456JA then the media type is JA. Label rules are defined in the following notes.

Notes:

JA and JJ tape cartridges are supported and can be mixed in a TS7700. JA and JJ media is supported in "read-only" mode when E07 tape drives are connected to the TS7700. JA and JJ tape cartridges are not supported by E08, 60F, and 60G tape drives.
JB tape cartridges are also supported (and can be mixed with JA and JJ tape cartridges, except when E07 tape drives are installed) if all of the tape drives associated with the TS7700 are 3592 model E05, E06/EU6, or E07 tape drives and none of them are in J1A emulation mode. JB tape cartridges are not supported by E08, 60F, and 60G tape drives.
JC and JK tape cartridges are supported by E07, E08, 60F, and 60G tape drives.
JD and JL tape cartridges are only supported by E08, 60F, and 60G tape drives.
JE and JM tape cartridges are only supported by 60F and 60G tape drives.
No other tape types are currently supported for use with the TS7760 → TS7700.
If there is at least one 3592 model J1A tape drive associated with the TS7700, then ALL 3592 model E05 tape drives associated with the TS7700 must be in J1A emulation mode.
If at least one tape cartridge associated with a TS7700 has been written by a 3592 model E05 tape drive that is NOT in J1A emulation mode, then the TS7700 no longer supports any 3592 model J1A tape drives or any 3592 model E05 tape drive that is in J1A emulation mode. Once you go to 'E05 Native' mode, you cannot go back to J1A mode. This is because the J1A tape drive cannot read or write a tape cartridge that is written in E05 mode and the TS7700 does not currently support mixed J1A and E05 tape drives (unless all E05 tape drives are in J1A emulation mode).
The capacity of a JJ tape cartridge is 60 GB if written by a J1A tape drive (or an E05 tape drive that is in J1A emulation mode), or 100 GB if written by an E05 tape drive that is NOT in J1A emulation mode, or 128 GB if written by an E06 tape drive.
The capacity of a JA tape cartridge is 300 GB if written by a J1A tape drive (or an E05 tape drive that is in J1A emulation mode) or 500 GB if written by an E05 tape drive that is NOT in J1A emulation mode, or 640 GB if written by an E06/EU6 tape drive.
The capacity of a JB cartridge is 700 GB if written by an E05 tape drive that is not in J1A emulation mode, or 1 TB if written by an E06/EU6 tape drive, or 1.6 TB if written by an E07 tape drive.
The capacity of a JC cartridge is 4 TB if written by an E07 tape drive or 7 TB if written by an E08, 60F, or 60G tape drive.
The capacity of a JK cartridge is 500 GB if written by an E07 tape drive or 900 GB if written by an E08, 60F, or 60G tape drive.
The capacity of a JD cartridge is 10 TB if written by an E08 tape drive or 15 TB if written by a 60F or 69G tape drive.
The capacity of a JL cartridge is 2 TB if written by an E08 tape drive or 3 TB if written by a 60F or 69G tape drive.
The capacity of a JE cartridge is 20 TB if written by a 60F or 60G tape drive.
The capacity of a JM cartridge is 5 TB if written by a 60F or 60G tape drive.
3592 model E06/EU6 tape drives CANNOT be intermixed with 3592 model J1A, 3592 model E05, or 3592 model E07 tape drives.
3592 model E08/EH8/60F/60G tape drives can be intermixed with 3592 model J1A, E05, E06, and E07 tape drives. See Table 5 for valid combinations.
If you are installing a 3592 model 60F/60G (TS1160) tape drive in a TS7700, the microcode level must be at 8.52.101.x or later.
TS7700 Feature Code 9900 (Encryption) requires that all E05 tape drives are in E05 'Native' mode. The Encryption feature is NOT compatible with J1A emulation mode. The E06 drives support encryption and do not require to be set into any mode.

Tape cartridge capacities are as follows:

Table 4. Tape cartridge capacities
Media type	Format	Capacity
JJ	J1A format, including E05 drives in J1A emulation mode	60 GB (55.88 GiB)
	E05 format (NOT in J1A emulation mode)	100 GB (93.13 GiB)
	E06 format	128 GB (119.2 GiB)
JA	J1A format, including E05 drives in J1A emulation mode	300 GB (279.39 GiB)
	E05 format (NOT in J1A emulation mode)	500 GB (465.6 GiB)
	E06 format	640 GB (596 GiB)
JB	E05 format (NOT in J1A emulation mode)	700 GB (651.93 GiB)
	E06 format	1 TB (0.9 TiB)
	E07 format	1.6 TB (1.45 TiB)
JK	E07 format	500 GB (465.66 GiB)
JK	E08 format	900 GB (838.19 GiB)
JC	E07 format	4 TB (3.63 TiB)
JC	E08 format	7 TB (6.36 TiB)
JD	E08 format	10 TB (9.09 TiB)
JL	E08 format	2 TB (1.81 TiB)

If you are installing 3592 E05 tape drives, use the rules that are defined in the previous step to determine whether you want the 3592 E05 tape drives attached to the TS7700 to be in J1A emulation mode or in E05 native mode. Record this value in the E05 in J1A Emulation entry in Table 11.

(Distributed) Library Sequence Number

The Library Sequence Number is assigned by your administrator. This is a 5 hex character name that is used as an identifier for a specific cluster and the associated Library in a grid configuration. This identifier is specified in the TS7700 configuration.

It is required even if the TS7700 is not in a Grid configuration.

Note: Each VTS partition must have a single, unique value for the Distributed Library Sequence Number. For the TS7700, a typical value is the last five digits of the 3952 Tape Frame serial number.

Home Pool

Also called Scratch Pool. A pool is a group of physical tape cartridges. A scratch pool is a group of cartridges that are considered to be scratch, meaning that they are ready for use by any write job.

You may have assigned a Home Pool value. If one has not been set, the default value is 00.

If you are installing a 3592 model E08 (TS1150) drive in a TS7760, the microcode level must be at 8.33.x.x or later and has a limited heterogeneous drive support shown in Table 5:

Note: When using E08 tape drives, go to the MI Pool Properties page to ensure that media settings are set to either Any 3592 or an E08 compatible media type.

Table 5. TS3500 Limited Drive Support Table
	Pre-E08 Drive Type 2	Min and Max Number of E08 (Heterogeneous) Drives Allowed	Min and Max Number of E08 (Homogeneous) Drives Allowed	Combined Maximum Number of Tape Drives Allowed
3592 J1A	3592 E05 in J1A emulation mode	2 – 12 (any combo up to 12)	4 – 14	16
3592 E05 in Native Mode	Not supported	2 – 12	4 – 14	16
3592 E06	Not supported	2 – 12	4 – 14	16
3592 E07	Not supported	2 – 12	4 – 14	16

If you are installing a 3592 model E08 (TS1150) drive into a TS3500 Tape Library and it is connected to a TS7700 with tape drives attached, the microcode level must be at 8.33.x.x or later and supports the following homogeneous tape drive configurations:
- Up to 16 drives in a single logical library for a new TS7760 installation
- Up to 16 drives in a single logical library for a TS7700 MES conversion to a TS7760
- Up to 16 drives in a single logical library for existing TS7700 with active data on JK and/or JC cartridges only
Note: The following cartridges can be used as scratch media: JK, JC, JL, and JD.

If you are installing a 3592 model 60G (TS1160) drive into a TS3500 Tape Library, the microcode level must be at 8.52.101.x or later and must have a limited heterogeneous drive support as shown the following table:

Table 6. TS3500 heterogenous limited drive support
	Minimum and maximum E0x	Minimum and maximum number of 3592 60G drives allowed	Combined maximum number of tape drives allowed
3592 E06	2-12	4-14	16
3592 E07	2-12	4-14	16
3592 E08	2-12	4-14	16

If you are installing a 3592 model 60G (TS1160) drive into a TS3500 Tape Library and it is connected to a TS7700 with tape drives attached, the microcode level must be at 8.52.101.x or later and must support the following homogeneous tape drive configurations:
- Up to 16 drives in a single logical library for a new TS7700 installation
- Up to 16 drives in a single logical library for existing TS7700 with active data on JC, JD, JE, JK, JL, and/or JM cartridges only

Table 7. Media Volume Serial (VOLSER) Range Table and Notes
Cluster (0 to 7)	From	To	Media Type	(Distributed) Library Sequence Number	Home Pool	Scratch Category

Table 8. Encryption Key Information Table
Key Server Address	Address	Port
Primary
Secondary

If you are installing a 3592 model EH8 (TS1150) tape drive into a TS4500 Tape Library and it is connected to a TS7700 with tape drives attached, the microcode level must be at 8.40.x.x or later and supports the following tape drive configurations shown in Table 9.

Table 9. TS4500 Limited Drive Support Table
	EH8 Drive Type 2	Min and Max Number of EH8 (Heterogeneous) Drives Allowed	Min and Max Number of EH8 (Homogeneous) Drives Allowed	Combined Maximum Number of Tape Drives Allowed
3592 EH7	Supported	2 – 12	4 – 14	16

If you are installing a 3592 model 60F (TS1160) drive into a TS4500 Tape Library, the microcode level must be at 8.52.101.x or later and must have a limited heterogeneous drive support as shown in the following table:

Table 10. TS4500 heterogenous limited drive support
	Minimum and maximum EHx	Minimum and maximum number of 3592 60F drives allowed	Combined maximum number of tape drives allowed
3592 EH7	2-12	4-14	16
3592 EH8	2-12	4-14	16

TS7700 configuration

Provide values for each of the defined TS7700 configuration fields defined in Table 11 and Table 12. Required information includes:

Library sequence numbers (composite and distributed)
Disk cache type
IP addresses (logical, primary, alternate, NTP)
Subnet mask
Gateway
Tape drive format
Network speed settings

Table 11. Code Activation/VPD Information Table and Notes
Field	Value	Notes®
Machine model
Cluster Index	CLUSTER 0:
	CLUSTER 1:
	CLUSTER 2:
	CLUSTER 3:
	CLUSTER 4:
	CLUSTER 5:
	CLUSTER 6:
	CLUSTER 7:
TS7700 3948-F0x or 3952-F0x Base Frame serial number	CLUSTER 0:	Refer to the frame serial number, on a label in the bottom of the 3952 Tape Frame inside the rear door. Use the last 5 characters of the serial number that is shown on the label.
	CLUSTER 1:
	CLUSTER 2:
	CLUSTER 3:
	CLUSTER 4:
	CLUSTER 5:
	CLUSTER 6:
	CLUSTER 7:
TS7700 3948-F0x or 3952-F0x Storage Expansion Frame serial number	CLUSTER 0:
	CLUSTER 1:
	CLUSTER 2:
	CLUSTER 3:
	CLUSTER 4:
	CLUSTER 5:
	CLUSTER 6:
	CLUSTER 7:
TS7700 3948-F0x or 3952-F0x Storage Expansion Frame serial number (Optional)	CLUSTER 0:
	CLUSTER 1:
	CLUSTER 2:
	CLUSTER 3:
	CLUSTER \4:
	CLUSTER 5:
	CLUSTER 6:
	CLUSTER 7:
Composite Library Sequence Number		This 5-character hexadecimal name must be the same on all clusters (peers) within the same grid. This identifier is specified in the TS7700 configuration. It is required even if the machine is not in a grid configuration. Note: This is the Composite Library Sequence Number. It must be different than the Distributed Library Sequence number specified below.
Distributed Library Sequence Number		This 5-character hexadecimal number is assigned by the customer's administrator and is used as an identifier for a specific cluster. Each TS7700 must have a single, unique value for the Distributed Library Sequence Number. A typical value is the last five digits of the 3952 Tape Frame serial number. Note: This number must be different than the Composite Library Sequence number.
TS3500 or TS4500 attached	Y or N	Reply yes or no if there will be a TS3500 or TS4500 tape library attached at the time of the TS7700 installation.
E05 in J1A Emulation	Y or N or NA
TS7700 cache type		The TS7700 Cache distributed from manufacturing with microcode 8.40.0.xx uses a DS3000(r) cache type. For a new TS7700, the cache type is 3956-CSA.
TS7700 cache controller serial number (Base Frame)	CLUSTER 0:	Refer to the serial number label on the front of the bottom cache drawer. The serial number is on a label on the detachable cover on the right side of the cache drawer. Note: This serial number is only used for reporting installation or repair of the cache. The TS7700 microcode activation process allows you to change the serial number, but you should always use the serial number that was set during the manufacturing process.
	CLUSTER 1:
	CLUSTER 2:
	CLUSTER 3:
	CLUSTER 4:
	CLUSTER 5:
	CLUSTER 6:
	CLUSTER 7:
Additional controllers		Enter the number of additional cache controllers that are installed. Note: There is only 1 controller per frame.
TS7700 cache controller serial number (Cache Frame 1)	CLUSTER 0:	Refer to the serial number label on the front of the bottom cache drawer. The serial number is on a label on the detachable cover on the right side of the cache drawer. Note: This serial number is only used for reporting installation or repair of the cache. The TS7700 microcode activation process allows you to change the serial number, but you should always use the serial number that was set during the manufacturing process.
	CLUSTER 1:
	CLUSTER 2:
	CLUSTER 3:
	CLUSTER 4:
	CLUSTER 5:
	CLUSTER 6:
	CLUSTER 7:
TS7700 cache controller serial number (Cache Frame 2)	CLUSTER 0:	Refer to the serial number label on the front of the bottom cache drawer. The serial number is on a label on the detachable cover on the right side of the cache drawer. Note: This serial number is only used for reporting installation or repair of the cache. The TS7700 microcode activation process allows you to change the serial number, but you should always use the serial number that was set during the manufacturing process.
	CLUSTER 1:
	CLUSTER 2:
	CLUSTER 3:
	CLUSTER 4:
	CLUSTER 5:
	CLUSTER 6:
	CLUSTER 7:
Cluster Index	CLUSTER 0 - 7	This value is the same as the cluster number used throughout these tables.
Cluster IP address for the TSSC	CLUSTER 0:
	CLUSTER 1:
	CLUSTER 2:
	CLUSTER 3:
	CLUSTER 4:
	CLUSTER 5:
	CLUSTER 6:
	CLUSTER 7:
Internal network type		For a new TS7700, the Internal network type is Switch.

Table 12. TS7700 Customer Network Configuration Information Table and Notes
Field	Value	Notes
Dead Gateway Detection	CLUSTER 0: _ _ _._ _ _._ _ _._ _ _	Select either Enable or Disable.
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _
Customer IP 1 (Virtual)	CLUSTER 0: _ _ _._ _ _._ _ _._ _ _	Used For: TS7700 web Management Interface Note: 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. 1 Gbps can use CAT 5e or CAT 6. 10 Gbps need CAT 6.
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _
Customer IP 2 (Primary)	CLUSTER 0: _ _ _._ _ _._ _ _._ _ _	This is the IP address that is used to connect to the TS7700 through the internal primary network. This IP address should not be used by the customer unless the Virtual IP is inaccessible. Note: On a V07/VEB Customer IPs are capable of 1000 MB/s. 1 Gbps can use CAT 5e or CAT 6. 10 Gbps need CAT 6.
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _
Customer IP 3 (Alternate)	CLUSTER 0: _ _ _._ _ _._ _ _._ _ _	This is the IP address that is used to connect to the TS7700 through the internal alternate network. This IP address should not be used by the customer unless the Virtual IP is inaccessible. Note: On a V07/VEB Customer IPs are capable of 1000 MB/s. 1 Gbps can use CAT 5e or CAT 6. 10 Gbps need CAT 6.
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _
Customer Gateway	CLUSTER 0: _ _ _._ _ _._ _ _._ _ _	This is used with the virtual, primary, and alternate customer IP addresses.
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _
Customer Subnet Mask	CLUSTER 0: _ _ _._ _ _._ _ _._ _ _	This is used with the virtual, primary, and alternate customer IP addresses.
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _
Customer Network Speed/Duplex Setting		This is the network setting the customer wants to use for their customer interface. The default value is Auto-Negotiate. The customer can specify one of the following values: Auto-Negotiate 1000 Full Duplex 100 Full Duplex 100 Half Duplex 10 Full Duplex 10 Half Duplex
Customer Library IP	CLUSTER 0: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _
3948-Vxx or 3957-Vxx IP address on the TSSC Network	172.31.1.xx	This is the recommended IP address for the first TS7700 attached to a TSSC. The last octet of this IP address must be in an increment of 10 between 10 and 240 (that is, 10, 20 ... 230, 240). The TS7700 switch configuration uses this and the following 9 IP addresses (example: .150 - .159) so no other device should be set to an IP address in this range.
NTP server IP address (if used). Using an NTP server is strongly recommended to ensure that all components have consistent time settings.	_ _ _._ _ _._ _ _._ _ _	Notes: The TCP/IP address you obtain from the customer is either the NTP server at their site (if they maintain 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). Only 1 NTP server can be used for the entire Grid and ALL clusters in the Grid need to be able to access that specific NTP server.

TSSC Configuration Information Table and Notes

Table 13. TSSC Configuration Information Table and Notes
Field	Value	Notes
IP address for the External connection that is used for ECC, AOS, and SNMP	CLUSTER 0: _ _ _._ _ _._ _ _._ _ _	Note: Ethernet Call Home is required for FC 2725 (M93p Tiny PC TSSC), but optional for older models of TSSC. This is an optional (but strongly recommended) IP address on the customer network that allows the TSSC to Call Home by using a high-speed connection through the customer network to the internet. Ports 443 (https) and 80 (http) on this IP address must be free for outbound traffic through the customer network to the internet. Call Home through an Ethernet connection greatly improves the speed of the data transfer, making the data available to support personnel more quickly. IBM recommends enabling Call Home to improve data collection when a problem occurs. Call Home through an Ethernet connection provides better throughput and lower cost than Call Home through a modem connection. Refer to Table 14 for a list that provides the IP addresses that AOS 4.0 needs to get through the firewall. Refer to Table 16 for a list that provides the IP addresses that Legacy ECC Broadband Call Home needs to get through the firewall. Refer to Table 15 for a list that provides the IP addresses that Edge ECC Broadband Call Home needs to get through the firewall. Refer to Table 17 for a list that provides the IP addresses that the Fix Download needs to get through the firewall.
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _
Subnet Mask (for Ethernet Call Home)	CLUSTER 0: _ _ _._ _ _._ _ _._ _ _	This is the subnet mask that is associated with the IP address (for Ethernet Call Home).
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _
Gateway (for Ethernet Call Home)	CLUSTER 0: _ _ _._ _ _._ _ _._ _ _	This is the gateway that is associated with the IP address (for Ethernet Call Home).
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _
DNS (Domain Name Server) IPs	_ _ _._ _ _._ _ _._ _ _ _ _ _._ _ _._ _ _._ _ _ _ _ _._ _ _._ _ _._ _ _ _ _ _._ _ _._ _ _._ _ _ _ _ _._ _ _._ _ _._ _ _	Nearly all networks use Domain Name Servers to convert names (such as www.ibm.com) to numeric IP addresses. Domain Name Servers significantly improve the reliability of AOS connections to the TSSC. Provide numeric IP addresses for Domain Name Servers (at least one is required for DNS functionality, two or more are recommended).
DNS Domain Names	1. ______________________________ 2. ______________________________ 3. ______________________________	Enter the Domain Names. An example is myServer.CompanyXYZ.com.

TSSC IP Address Table and Notes

TSSC Remote Support Information

Table 14. TSSC AOS version 4.0
Hostname	IP address	Port	Description
aoshats.us.ihost.com	72.15.223.62	443	US AOS Broker¹
aosback.us.ihost.com	72.15.223.61	443	US AOS Broker¹
aosrelay1.us.ihost.com	72.15.223.60	443	US AOS Broker¹

¹ IBM recommends the use of all AOS broker for redundancy. A client may restrict the use to a specific broker as needed, requiring a manual change of the AOS configuration.

Table 15. URL table for Edge ECC
Hostname	IP address	Port	Description
esupport.ibm.com	129.42.56.189 129.42.18.70³	443,80¹	ECC Edge transaction gateway
esupport.ibm.com	129.42.60.189 129.42.19.70³	443,80¹	ECC Edge transaction gateway
esupport.ibm.com	129.42.54.189 129.42.21.70²	443,80¹	ECC Edge transaction gateway
¹ Fix Acquisition through port 80 or 443 as configured per client preference ² IP address change planned April 14th, 2023, replacing the prior IP address ³ IP address change planned in 2024 with no final date set yet
Notes: ECC Edge should be used for all future deployments. It is recommended customers open 129.42.0.0/18 for convenience. The IPs are not pingable. Use the following link to verify a connection: https://esupport.ibm.com/eccedge/gateway/services/projects/ecc/iepd/services/ProblemReport.

Table 16. URL table for Legacy ECC
Hostname	IP address	Port	Description
eccgw01.boulder.ibm.com	207.25.252.197	443	ECC transaction gateway
eccgw02.rochester.ibm.com	129.42.160.51	443	ECC transaction gateway
www.ecurep.ibm.com	192.109.81.20	443	File upload for status reporting and problem reporting.
www6.software.ibm.com	170.225.15.41 170.225.126.56²	443	File upload proxy for status reporting and problem reporting.
www-945.ibm.com	129.42.26.224 129.42.18.71⁴	443	Problem reporting server v4
www-945.ibm.com	129.42.42.224 129.42.19.71⁴	443	Problem reporting server v4
www-945.ibm.com	129.42.50.224 129.42.21.71³	443	Problem reporting server v4
www.ibm.com	129.42.56.216¹	443	Service provider file (CCF) download
www.ibm.com	129.42.54.216¹	443	Service provider file (CCF) download
www.ibm.com	129.42.60.216¹	443	Service provider file (CCF) download
www-03.ibm.com	204.146.30.17	443	Service provider file (CCF) download

¹ Use of IP addresses for www.ibm.com is discouraged, DNS lookup highly recommended

² IP address change pending after June 4th, 2022, replacing the prior IP address

³ IP address change planned April 14th, 2023, replacing the prior IP address

⁴IP address change planned in 2024 with no final date set yet

Note: Legacy ECC should no longer be used.

Table 17. URL table for Fix Download
Hostname	IP address	Port	Description
download3.boulder.ibm.com	170.225.15.76 170.225.126.24¹	80	Fix Download
download3.mul.ie.ibm.com	129.35.224.114	80	Fix Download
download4.boulder.ibm.com	170.225.15.107 170.225.126.43¹	80	Fix Download
download4.mul.ie.ibm.com	129.35.224.107	80	Fix Download
delivery04-bld.dhe.ibm.com	170.225.15.104 129.35.224.104 170.225.126.45¹	80	Fix Download
delivery04-mul.dhe.ibm.com	129.35.224.115 170.225.15.115 170.225.126.46¹	80	Fix Download
delivery04.dhe.ibm.com	129.35.224.105 170.225.15.105 170.225.126.44¹	80	Fix Download

¹ IP address change pending June 4th, 2022, replacing the prior IP addresses

Note: Download servers should no longer be used.

Go to Managing remote support for important configuration information.

TS7700 Grid local addresses

The following notes apply to Table 22.

If the TS7700 being installed is a stand-alone machine (not part of a grid configuration), then do not complete Table 22.
The Grid interfaces are the network connections between clusters that allow them to automatically remain in sync.
IBM® strongly recommends that the primary and alternate Grid interfaces are on redundant networks.

The TS7700 Management Interface requires connections that use the following TCP/IP ports and settings:

Table 18. TS7700 Management Interface Port Information
Port	Function	Direction from TS7700	Protocol
	PING	Outbound	ICMP
53	DNS	Bi-directional	UDP
80²	HTTP	Inbound	TCP
123	NTP	Bi-directional	UDP
162	SNMP Trap	Outbound	UDP
389	LDAP	Outbound	TCP
415	RSYSLOG	Outbound	TCP
441	SKLM TLS (R5.0)	Outbound	TCP
443	HTTPS	Inbound	TCP
636	LDAP with TLS	Outbound	TCP
3801	TKLM/ISKLM Server	Outbound	TCP
5696	KMIP TLS (R5.0)	Outbound	TCP
16311¹	LDAP using SAS	Outbound	TCP
¹ SSPC support has been deprecated ²The use of port 80 has been deprecated and port 443 should be used instead

The Grid interfaces require connections using the following TCP/IP ports in both directions for all clusters:

Table 19. TS7700 Grid Port Information
Port	Function	Direction from TS7700	Protocol
	Ping	Bi-directional	ICMP
22¹	SSH	Bi-directional	TCP
80²	HTTP	Bi-directional	TCP
123	NTP (Network Time Protocol)	Bi-directional	UDP
350	Distributed Library file transfer	Bi-directional	TCP
443	HTTPS	Bi-directional	TCP
1415	Websphere Message Queues	Bi-directional	TCP
1416	Websphere Message Queue	Bi-directional	TCP
¹ used by PFE/Development during remote access (recommended) ² The use of port 80 has been deprecated and port 443 should be used instead

The TSSC "external" link is as follows:

Table 20. TSSC External Port Information²
Port	Function	Direction from TSSC	Protocol
	PING	Outbound	ICMP
22	SSH	Outbound	TCP
53	DNA	Bi-directional	UDP
123	NTP	Bi-directional	UDP
162	SNMP Trap	Outbound	UDP
389	LDA	Outbound	TCP
415	RSYSLOG	Outbound	TCP / UDP
443	HTTPS	Bi-directional¹	TCP
636	LDAP with TLS	Outbound	TCP
16311³	LDAP with SAS	Outbound	TCP
¹ Bi-directional in case of client web access, otherwise Outbound only ² For AOTM Port Information, refer to Autonomic Ownership Takeover Manager. ³ SSPC support has been deprecated

The TSSC Grid link is as follows:

Table 21. TSSC AOTM Port Information
Port	Function	Direction from TSSC	Protocol
¹	PING	Bi-directional	ICMP
22¹	SSH	Bi-directional	TCP
80²	HTTP	Bi-directional	TCP
443	HTTPS	Bi-directional	TCP
9666	COMM	Bi-directional	TCP
¹ used by PFE/Development during remote access, including authenticated user broadcast (recommended) ² The use of port 80 has been deprecated and port 443 should be used instead

Table 22. Grid Local Address Table and Notes
Field	Value	Notes
IP address Primary Grid Interface Port A	CLUSTER 0: _ _ _._ _ _._ _ _._ _ _	The Primary Grid Port A Interface is the Ethernet adapter in slot C1 (port 0, top port) of the 3948-Vxx or 3957-Vxx. The Primary Grid Port A Interface at each cluster connect to the Primary Grid Port A Interface at each of the other clusters in the same Grid. Note: IBM strongly recommends that the primary and alternate Grid interfaces exist on separate subnets. If the Grid interfaces are directly connected (without using Ethernet switches), then using separate subnets is required.
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _
IP address Primary Grid Interface Port B (if applicable)	CLUSTER 0: _ _ _._ _ _._ _ _._ _ _	The Primary Grid Port B Interface is the Ethernet adapter in slot C1 (port 1, bottom port) of the 3948-Vxx or 3957-Vxx. The Primary Grid Port B Interface at each cluster connect to the Primary Grid Port B Interface at each of the other clusters in the same grid.
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _
Primary Grid Port A Network Mask	CLUSTER 0: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _
Primary Grid Port B Network Mask (if applicable)	CLUSTER 0: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _
Primary Grid Port A Gateway	CLUSTER 0: _ _ _._ _ _._ _ _._ _ _	If a Gateway is not used, leave this field blank. If using a direct connection (without Ethernet switches), you must not specify a Gateway. Primary Grid Interface Port A: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _
Primary Grid Port B Gateway (if applicable)	CLUSTER 0: _ _ _._ _ _._ _ _._ _ _	If a Gateway is not used, leave this field blank. If using a direct connection (without Ethernet switches), you must not specify a Gateway. Primary Grid Interface Port B: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _
IP address Alternate Grid Interface Port A	CLUSTER 0: _ _ _._ _ _._ _ _._ _ _	The Alternate Grid Port A Interface is the Ethernet adapter in slot C1 (port 0, top port) of the 3948-Vxx or 3957-Vxx. The Alternate Grid Port A Interface at each cluster connect to the Alternate Grid port A Interface at each of the other clusters in the same grid. Note: IBM strongly recommends that the primary and alternate Grid interfaces exist on separate subnets. If the Grid interfaces are directly connected (without using Ethernet switches), then using separate subnets is required.
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _
IP address Alternate Grid Interface Port B (if applicable)	CLUSTER 0: _ _ _._ _ _._ _ _._ _ _	The Alternate Grid Interface Port B is the Ethernet adapter in slot C1 (port 1, bottom port) of the 3948-Vxx or 3957-Vxx. The Alternate Grid Port B Interface at each cluster connect to the Alternate Grid Port B Interface at each of the other clusters in the same grid.
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _
Alternate Grid Port A Network Mask	CLUSTER 0: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _
Alternate Grid Port B Network Mask (if applicable)	CLUSTER 0: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _
Alternate Grid Port A Gateway	CLUSTER 0: _ _ _._ _ _._ _ _._ _ _	If a Gateway is not used, leave this field blank. If using a direct connection (without Ethernet switches) you must not specify a Gateway. Alternate Grid Interface Port A: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _
Alternate Grid Port B Gateway (if applicable)	CLUSTER 0: _ _ _._ _ _._ _ _._ _ _	If a Gateway is not used, leave this field blank. If using a direct connection (without Ethernet switches) you must not specify a Gateway. Alternate Grid Interface Port B: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _

Customers can use Table 23 or one similar to it to summarize Grid Local Address information.

Note: Virtual Local Area Network (VLAN) and Classless Inter-Domain Routing (CIDR) listed in Table 23 are optional.

Table 23. Summary Table
Name: __________ CL__
Description	IP Address	Gateway	Subnet Mask	VLAN	CIDR
Customer IP 1 (Virtual)
Customer IP 2 (Primary)
Customer IP 3 (Alternate)
Ethernet Call Home
Primary Grid Port A Interface
Alternate Grid Port A Interface
Primary Grid Port B Interface (if applicable)
Alternate Grid Port B Interface (if applicable)

Name: __________ CL__
Description	IP Address	Gateway	Subnet Mask	VLAN	CIDR
Customer IP 1 (Virtual)
Customer IP 2 (Primary)
Customer IP 3 (Alternate)
Ethernet Call Home
Primary Grid Port A Interface
Alternate Grid Port A Interface
Primary Grid Port B Interface (if applicable)
Alternate Grid Port B Interface (if applicable)

Name: __________ CL__
Description	IP Address	Gateway	Subnet Mask	VLAN	CIDR
Customer IP 1 (Virtual)
Customer IP 2 (Primary)
Customer IP 3 (Alternate)
Ethernet Call Home
Primary Grid Port A Interface
Alternate Grid Port A Interface
Primary Grid Port B Interface (if applicable)
Alternate Grid Port B Interface (if applicable)

Name: __________ CL__
Description	IP Address	Gateway	Subnet Mask	VLAN	CIDR
Customer IP 1 (Virtual)
Customer IP 2 (Primary)
Customer IP 3 (Alternate)
Ethernet Call Home
Primary Grid Port A Interface
Alternate Grid Port A Interface
Primary Grid Port B Interface (if applicable)
Alternate Grid Port B Interface (if applicable)

Name: __________ CL__
Description	IP Address	Gateway	Subnet Mask	VLAN	CIDR
Customer IP 1 (Virtual)
Customer IP 2 (Primary)
Customer IP 3 (Alternate)
Ethernet Call Home
Primary Grid Port A Interface
Alternate Grid Port A Interface
Primary Grid Port B Interface (if applicable)
Alternate Grid Port B Interface (if applicable)

Name: __________ CL__
Description	IP Address	Gateway	Subnet Mask	VLAN	CIDR
Customer IP 1 (Virtual)
Customer IP 2 (Primary)
Customer IP 3 (Alternate)
Ethernet Call Home
Primary Grid Port A Interface
Alternate Grid Port A Interface
Primary Grid Port B Interface (if applicable)
Alternate Grid Port B Interface (if applicable)

Name: __________ CL__
Description	IP Address	Gateway	Subnet Mask	VLAN	CIDR
Customer IP 1 (Virtual)
Customer IP 2 (Primary)
Customer IP 3 (Alternate)
Ethernet Call Home
Primary Grid Port A Interface
Alternate Grid Port A Interface
Primary Grid Port B Interface (if applicable)
Alternate Grid Port B Interface (if applicable)

Name: __________ CL__
Description	IP Address	Gateway	Subnet Mask	VLAN	CIDR
Customer IP 1 (Virtual)
Customer IP 2 (Primary)
Customer IP 3 (Alternate)
Ethernet Call Home
Primary Grid Port A Interface
Alternate Grid Port A Interface
Primary Grid Port B Interface (if applicable)
Alternate Grid Port B Interface (if applicable)

TSSC Grid Configuration Information Table and Notes

The following notes apply to Table 24.

If the TS7700 you are installing is a stand-alone machine (not part of a grid configuration) then leave Table 24 blank.
If no host attachment is available on a cluster, Autonomic Ownership Takeover Manager (AOTM) does not need to be set up. However, it is recommended that AOTM remains set up so that it is available if host attachment is ever made. Leave Table 24 blank.
If the Autonomic Ownership Takeover Manager (AOTM) will not be used, then leave Table 24 blank.
Refer to Ownership takeover and The Autonomic Ownership Takeover Manager for more information on AOTM before you continue. Do NOT attempt to configure AOTM. Use these sections to make an informed decision whether to use AOTM.
The TSSC grid interface is only used for 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) open.

Table 24. TSSC Grid Configuration Information Table and Notes
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(s) at other cluster(s) in the same Grid network.
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _
TSSC Grid Interface Subnet Mask	CLUSTER 0: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _
TSSC Grid Interface Gateway	CLUSTER 0: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 1: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 2: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 3: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 4: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 5: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 6: _ _ _._ _ _._ _ _._ _ _
	CLUSTER 7: _ _ _._ _ _._ _ _._ _ _
Takeover Mode - Select One	DISABLED:	The Takeover Modes are DISABLED, Read Ownership Takeover (ROT), or Write Ownership Takeover (WOT). When DISABLED, no auto takeover is allowed. ROT allows only 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 recommended because it automatically gives you read access to any consistent copies of data without any requirement for manual intervention during reconciliation 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.
	ROT:
	WOT:
Grace Period (Minutes)		When a cluster detects that another cluster in the same grid has failed, it waits 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. In most cases, this is the same for both clusters.
Retry Period (Minutes)		The retry period is the number of minutes between attempts to take over ownership of the volumes that are associated with a failed cluster. A typical Retry Period is 5 minutes. In most cases, this is the same for both clusters.