Attention: Only supported web browsers should be used for management. Non-supported web browser versions might cause some MI panes to malfunction.

Note: Modem is not supported any longer in the new TS3000 System Console model.

Note: All inbound connections are subject to the security policies and standards defined by the client. When a Storage Authentication Service, Direct Lightweight Directory Access Protocol (LDAP), or RACF policy is enabled for a cluster, service personnel (local or remote) are required to use the LDAP-defined service login. Important: Be sure that local and remote authentication has been allowed, or that an account has been created to be used by service personnel, before enabling storage authentication, LDAP, or RACF policies.

Note: The AOTM and ECC interfaces should be in different TCP/IP subnets. This avoids both communications from using the same network connection.

Note: Remember that all authentications are subject to the Authentication policy in effect. See the information under 8.2.9, “The Access icon” on page 413.

Tip: Starting with R3.0, a new graphical user interface (GUI) has been implemented. This gives the TS7700 MI an appearance and operation that is similar to other IBM Storage products management interfaces.

Tip: The following web browsers are currently supported: •Firefox 13.0, Firefox 17.0, Firefox 17.x ESR, Firefox 19.x, Firefox 24.0, and Firefox 24.x ESR •Internet Explorer 9 and 10

Function	Port	Direction (from library)	Protocol
TS3500 Tape Library Specialist	80	Inbound	TCP/IP
Simple Network Management Protocol (SNMP) traps	161/162	Bidirectional	User Datagram Protocol (UDP)/IP
Encryption Key Manager	1443	Outbound	Secure Sockets Layer (SSL)
Encryption Key Manager	3801	Outbound	TCP/IP

Tip: To support Japanese input, a Japanese front-end processor needs to be installed on the computer where a web browser is running the MI.

Restriction: You cannot use the Back or Forward buttons or the Go Back or Go Forward options in your browser to navigate between MI pages.

Remember: The LI REQ option only shows in the bottom of the Management Interface pages for users with the Administrator role.

Important: LI REQ commands issued from this window are not presented in the host console logs.

Tip: The Systems icon is only visible when the accessed TS7700 Cluster is part of a grid.

Note: If the accessing cluster is a stand-alone cluster, the Cluster Summary window is shown upon login.

Note: The number shown in parentheses in breadcrumb navigation and cluster labels is always the cluster ID.

Restriction: An existing cluster family cannot be moved within the Cluster Families window.

Remember: Each cluster family must contain at least one cluster. If you attempt to save changes and a cluster family does not contain any clusters, an error message displays and the Cluster Families window remains in edit mode.

If the current state is	You can select	Restrictions and notes
Online	Service Prep	All following conditions must first be met: •The cluster is online. •No other clusters in the grid are in service prep mode. •At least one other cluster must remain online. Caution: If only one other cluster remains online, a single point of failure exists when this cluster state becomes service prep mode.   Select Service Prep to confirm this change.
	Force Shutdown	Select Force Shutdown to confirm this change. Important: After a shutdown operation is initiated, it cannot be canceled.
Service Pending	Force Service	You can select this option if you think that an operation has stalled and is preventing the cluster from entering Service Prep.   Select Force Service to confirm this change. Note: You can place all but one cluster in a grid into service mode but it is advised that only one cluster be in service mode at a time. If more than one cluster is in service mode, and you cancel service mode on one of them, that cluster does not return to normal operation until service mode is canceled on all clusters in the grid.
	Return to Normal	You can select this option to cancel a previous service prep change and return the cluster to the normal online state.   Select Return to Normal to confirm this change.
	Force Shutdown	Select Force Shutdown to confirm this change. Important: After a shutdown operation is initiated, it cannot be canceled.
Shutdown (offline)	User interface not available	After an offline cluster is powered on, it attempts to return to normal. If no other clusters in the grid are available, you can skip hot token reconciliation.
Online-Pending or Shutdown Pending	Menu disabled	No options to change state are available when a cluster is in a pending state.

Note: After a shutdown or force shutdown action, the targeted cluster (and associated cache) are powered off. A manual intervention is required on site where the cluster is physically located to power it up again.

Remember: Service mode is only possible for clusters that are members of a grid.

Important: Forcing Service Mode causes jobs currently mounted or using resources provided by targeted cluster to fail.

Consideration: Although you can place all clusters except one in service mode, the best approach is having only one cluster in service mode at a time. If more than one cluster is in service mode, and you cancel service mode on one of them, that cluster does not return to online state until service mode is canceled on all the clusters.

Note: After a shutdown or force shutdown action, the targeted cluster (and associated cache) are powered off. A manual intervention is required on site where cluster is physically located to power it up again.

Attention: A forced shutdown can result in lost access to data and job failure.

Important: After a shutdown operation is initiated, it cannot be canceled.

Tip: The expansion frame icon is only displayed if the accessed cluster has an expansion frame.

Restriction: If the cluster is not a TS7740 or a TS7720T, the Tape Library icon does not display on the TS7700 Virtualization Engine MI.

Detail	Definition
Physical library type - virtual library name	The type of physical library (type is always TS3500) accompanied by the name of the virtual library established on the physical library.
Tape Library Health   Fibre Switch Health   Tape Drive Health	The health states of the library and its main components. The following values are possible: •Normal •Degraded •Failed •Unknown
State	Whether the library is online or offline to the TS7700 Virtualization Engine.
Operational Mode	The library operational mode. The following values are possible: •Auto •Paused
Frame Door	Whether a frame door is open or closed.
Virtual I/O Slots	Status of the I/O station used to move cartridges into and out of the library. The following values are possible: •Occupied •Full •Empty
Physical Cartridges	The number of physical cartridges assigned to the identified virtual library.
Tape Drives	The number of physical tape drives available, as a fraction of the total. Click this detail to open the Physical Tape Drives window.

Tip: Notice in Figure 8-34 that the Systems icon only shows up in a grid configuration, and the Cluster Summary item only shows up under Monitor in a stand-alone configuration.

Note: The Date & Time column refers the time of the events to the local time in the computer where the Management Interface was initiated. If the DATA/TIME has been modified in the TS7700 from Coordinated Universal Time during installation, the event times are offset by the same difference in the Events display on the Management Interface. We suggest using Coordinated Universal Time in all TS7700 clusters when possible.

Column name	Description
Date & Time	Date and time the event occurred.
Source	Cluster where the event occurred.
Location	Specific location on the cluster where the event occurred.
Description	Description of the event.
ID	The unique number that identifies the instance of the event. This number consists of the following values: •A locally generated ID, for example: 923 •The type of event: E (event) or T (task) An event ID based on these examples appears as 923E.
Status	The status of an alert or task. If the event is an alert, this value is a fix procedure to be performed or the status of a call home operation. If the event is a task, this value is its progress or one of these final status categories: •Canceled •Canceling •Completed •Completed, with information •Completed, with warning •Failed
System Clearable	Whether the event can be cleared automatically by the system. The following values are possible: Yes. The event is cleared automatically by the system when the condition causing the event has been resolved. No. The event requires user intervention to clear. You must clear or deactivate the event manually after resolving the condition causing the event.

To run this task	Action
Deactivate or clear one or more alerts	1. Select at least one but no more than 10 events. 2. Click Mark Inactive. If a selected event is normally cleared by the system, you must confirm your selection. Other selected events are cleared immediately. Note: You can clear a running task but if the task later fails, it is displayed again as an active event.
Enable or disable host notification for alerts	Select Actions → [Enable/Disable] Host Notification. This change affects only the accessing cluster. Note: Tasks are not sent to the host.
View a fix procedure for an alert	Select Actions → View Fix Procedure. Note: A fix procedure can be shown for only one alert at a time. No fix procedures are shown for tasks.
Download a comma-separated value (CSV) file of the events list	Select Actions → Download all Events.
View more details for a selected event	1. Select an event. 2. Select Actions → Properties.
Hide or show columns on the table	1. Right-click the table header. 2. Click the check box next to a column heading to hide or show that column in the table. Column headings that are checked display on the table.
Filter the table data	Follow these steps to filter by using a string of text: 1. Click in the Filter field. 2. Enter a search string. 3. Press Enter. To filter by column heading: 1. Click the down arrow next to the Filter field. 2. Select the column heading to filter by. 3. Refine the selection.
Reset the table to its default view	1. Right-click the table header. 2. Click Reset Table Preferences.

Note: Up to ten different statistic data sets can be selected for the same graph view.

Tip: Consider limiting the Management Interface user roles who are allowed to change the partition configurations through this page.

Note: The Start Time column refers to the time of starting a task to the local time on the computer where the Management Interface was started. If the DATA/TIME has been modified in the TS7700 from Coordinated Universal Time during installation, the task start times are offset by the same difference in the Tasks display on the MI. Use Coordinated Universal Time in all TS7700 clusters unless you have a good reason not to.

Restrictions: No new partition can be created if Resident-Only (CP0) has 2 TB or less of free space. Creation of new partitions is blocked by a Flash Copy for DR in progress, or by one of the existing partitions being in overcommitted state.

Tip: Consider limiting the Management Interface user roles that are allowed to change the partition configurations through this page.

Column type	Description
Copy Type	The type of copy that is in the queue. The following values are possible: •Immediate: Volumes can be in this queue if they are assigned to a Management Class that uses the Rewind Unload (RUN) copy mode. •Synchronous-deferred: Volumes can be in this queue if they are assigned to a Management Class that uses the Synchronous mode copy and some event (such as the secondary cluster going offline) prevented the secondary copy from occurring. •Immediate-deferred: Volumes can be in this queue if they are assigned to a Management Class that uses the RUN copy mode and some event (such as the secondary cluster going offline) prevented the immediate copy from occurring. •Deferred: Volumes can be in this queue if they are assigned to a Management Class that uses the Deferred copy mode. •Time Delayed: Volumes can be in this queue if they are eligible to be copied based on either their creation time or last access time. •Copy-refresh: Volumes can be in this queue if the Management Class assigned to the volumes has changed and a LI REQ command was sent from the host to initiate a copy. •Family-deferred: Volumes can be in this queue if they are assigned to a Management Class that uses RUN or Deferred copy mode and cluster families are being used.
Last TVC Cluster	The name of the cluster where the copy last was in the TVC. Although this might not be the cluster from which the copy is received, most copies are typically obtained from the TVC cluster. Note: This column is only shown when View by Last TVC is selected.
Size	Total size of the queue, displayed in GiB. Note: See 1.5, “Data storage values” on page 12 for additional information about the use of binary prefixes. When Copy Type is selected, this value is per copy type. When View by Last TVC is selected, this value is per cluster.
Quantity	The total number of copies in queue for each type.

Tip: This item is not visible on the TS7700 Virtualization Engine MI if there is no TS7740 or TS7720T cluster in grid.

Column name	Description
Position	The position of the virtual volume in the recall queue. The following values are possible: •In Progress: A recall is in progress for the volume. •Scheduled: The volume is scheduled to be recalled. If optimization is enabled, the TS7700 Virtualization Engine schedules recalls to be processed from the same physical cartridge. •Position: A number that represents the volume’s current position in the list of volumes that have not yet been scheduled. These unscheduled volumes can be promoted using the Actions menu.
Virtual Volume	The virtual volume to be recalled.
Physical Cartridges	The serial number of the physical cartridge on which the virtual volume resides. This column can be hidden.
Time in Queue	Length of time the virtual volume has been in the queue, which is displayed in hours, minutes, and seconds as HH:MM:SS. This column can be hidden.

Column name	Description
Address	The virtual drive address takes the format vtdXXXX, where X is a hexadecimal number.
Host Device Number	The device identifier as defined in the attached host. The value in this field does not affect drive operations, but if the host device number is set, it is easier to compare the virtual tape drives to their associated host devices. Follow these steps to add host device numbers: 1. Select one or more virtual tape drives. 2. Select Assign Host Device Numbers from the Actions menu. 3. Enter the host device address that you want assigned to the first virtual tape drive. Host device numbers are added to subsequent virtual tape drives incrementally.
Mounted Volume	The volume serial number (VOLSER) of the mounted virtual volume.
Previously Mounted Volume	The VOLSER of the virtual volume mounted on the drive before this one.
State	The role that the drive is performing. The following values are possible: Idle: The drive is not in use. Read: The drive is reading a virtual volume. Write: The drive is writing a virtual volume. This column is blank if no volume is mounted. With R3.1, this column shows Offline status for the virtual tape drive when appropriate. The column Online in previous versions of this page was removed; drive status is assumed Online unless specifically stated Offline in this column.
Time on Drive	The elapsed time that the virtual volume has been mounted on the virtual tape drive. This column is blank if no volume is mounted.
Cache Mount Cluster	The TVC cluster running the mount operation. If a synchronous mount exists, this field displays two clusters. This column is blank if no volume is mounted.
Bytes Read	Amount of data read from the mounted virtual volume. This value is shown as Raw KiB (Compressed KiB).
Bytes Written	Amount of data that was written to the mounted virtual volume. This value is shown as Raw KiB (Compressed KiB).
Virtual Block Position	The position of the drive on the tape surface in a block number, as calculated from the beginning of the tape. This value is displayed in hexadecimal form. When a volume is not mounted, this value is 0x0.
Mount Type	The type of mount on the drive. This field is blank if no volume is mounted. Possible values are: •Live Copy: The mount is a live copy of the volume. This is the type used during normal production. •Flash Copy: The mount is a Flash Copy used for disaster recovery testing. •Stand-alone: The mount request was initiated by the cluster and not the host. To mount a virtual volume: 1. Select a volume. 2. Select Stand-alone Mount from the Actions menu. Note: You can only mount virtual volumes that are not already mounted, on a drive that is online. Follow these steps to unmount a virtual volume: 1. Select a mounted volume. 2. Select Unmount from the Actions menu. Note: You can unmount only those virtual volumes that are mounted and have a status of Idle. •Stand-alone Flash Copy: A user initiated a stand-alone mount for a Flash Copy.

Note: The physical resources are shown in the virtual volume summary, virtual volume details table, or the cluster-specific virtual volume properties table for the TS7720T and TS7740 cluster models.

Removal Residency state		Removal Time indicator
Removed		The date and time the virtual volume was removed from the cluster.
Held		The date and time the virtual volume becomes a candidate for removal.
Pinned		The virtual volume is never removed from the cluster.
No Removal Attempted, “-”, Retained, or Deferred		“-” The Removal Time field is not applicable.

Note: If the cluster contains a physical library, Removal Residency does not apply and this field displays a dash.

Note: The Modify Virtual Volume function is helpful to manage virtual volumes that belong to a non-MVS host that is not aware of constructs. MVS hosts automatically assign constructs for virtual volumes. Management Interface acts indistinctly over any logical volume belonging to the cluster or grid regardless of the host that owns the volume, under user command. Notice that new constructs will only take effect over the modified volume or range after a mount-demount sequence, or by using the LI REQ COPYRFSH command.

Note: Only the unused logical volumes can be deleted through this window, meaning volumes in insert category FF00 that have never been mounted or have had its category, constructs, or attributes modified by a host. Otherwise, those logical volumes must be deleted from host.

Tip: Only one search can be run at a time. If a search is in progress, an information message occurs at the top of the Virtual Volumes Search window. You can cancel a search in progress by clicking Cancel Search.

Tip: Plan when assigning volumes to this group to avoid cache overruns.

Remember: You can print or download the results of a search query using Print Report or Download Spreadsheet on the Volumes found table at the end of the Search Results window, as shown in Figure 8-73 on page 372.

Column name	Description
Categories	The type of category that defines the virtual volume. The following values are valid: •Scratch: Categories within the user-defined private range 0x0001 through 0xEFFF that are defined as scratch (Fast Ready). Click the plus sign (+) icon to expand this heading and reveal the list of categories defined by this type. Expire time and hold values are shown in parentheses next to the category number. See Table 8-10 for descriptions of these values. •Private: Custom categories established by a user, within the range of 0x0001 - 0xEFFF. Click the plus sign (+) icon to expand this heading and reveal the list of categories defined by this type. •Damaged: A system category identified by the number 0xFF20. Virtual volumes in this category are considered damaged. •Insert: A system category identified by the number 0xFF00. Inserted virtual volumes are held in this category until moved by the host into a scratch category.   If no defined categories exist for a certain type, that type is not displayed on the Categories table.
Owning Cluster	Names of all clusters in the grid. Expand a category type or number to display. This column is visible only when the accessing cluster is part of a grid.
Counts	The total number of virtual volumes according to category type, category, or owning cluster.
Scratch Expired	The total number of scratch volumes per owning cluster that are expired. The total of all scratch expired volumes is the number of ready scratch volumes.

Tip: The total number of volumes within a grid is not always equal to the sum of all category counts. Volumes can change category multiple times per second, which makes the snapshot count obsolete.

Action	Steps to perform action
Add a scratch category	1. Select Add Scratch Category. 2. Define the following category properties:  – Category: A four-digit hexadecimal number that identifies the category. The valid characters for this field are A - F and 0 - 9. Do not use category name 0000 or “FFxx”, where xx equals 0 - 9 or A - F. 0000 represents a null value, and “FFxx” is reserved for hardware.    – Expire: The amount of time after a virtual volume is returned to the scratch (Fast Ready) category before its data content is automatically delete-expired. Select an expiration time from the menu. If you select No Expiration, volume data never automatically delete-expires. If you select Custom, enter values for the following fields:  • Time: Enter a number in the field according to these restrictions:  1 - 32,767 if unit is hours   1 - 1365 if unit is days   1 - 195 if unit is weeks  • Time Unit: Select a corresponding unit from the menu.  – Set Expire Hold: Check this box to prevent the virtual volume from being mounted or having its category and attributes changed before the expire time has elapsed. Checking this field activates the hold state for any volumes currently in the scratch (Fast Ready) category and for which the expire time has not yet elapsed. Clearing this field removes the access restrictions on all volumes currently in the hold state within this scratch (Fast Ready) category.
Modify a scratch category	You can modify a scratch category in two ways: •Select a category on the table, and then, select Actions → Modify Scratch Category. •Right-click a category on the table and either hold, or select Modify Scratch Category from the menu. You can modify the following category values: •Expire •Set Expire Hold You can modify one category at a time.
Delete a scratch category	You can delete a scratch category in two ways: 1. Select a category on the table, and then, select Actions → Delete Scratch Category. 2. Right-click a category on the table and select Delete Scratch Category from the menu. You can delete only one category at a time.
Hide or show columns on the table	1. Right-click the table header. 2. Click the check box next to a column heading to hide or show that column in the table. Column headings that are checked display on the table.
Filter the table data	Follow these steps to filter using a string of text: 1. Click in the Filter field. 2. Enter a search string. 3. Press Enter.   Follow these steps to filter by column heading: 1. Click the down arrow next to the Filter field. 2. Select the column heading to filter by. 3. Refine the selection:  – Categories: Enter a whole or partial category number and press Enter.  – Owning Cluster: Enter a cluster name or number and press Enter. Expand the category type or category to view highlighted results.  – Counts: Enter a number and press Enter to search on that number string.  – Scratch Expired: Enter a number and press Enter to search on that number string.
Reset the table to its default view	1. Right-click the table header. 2. Click Reset Table Preferences.

Note: There is no cross-check between defined categories in the z/OS systems and the definitions in the TS7700.

Tip: Pools 1 - 32 are preinstalled and initially set to default attributes. Pool 1 functions as the default pool and is used if no other pool is selected.

Important: The reclaim pool that is designated for the Copy Export pool needs to be set to the same value as the Copy Export pool. If the reclaim pool is modified, Copy Export disaster recovery capabilities can be compromised.

Note: You can use identical values in Key Label 1 and Key Label 2, but you must define each label for each key.

Tip: This page is not visible on the TS7700 Virtualization Engine MI if the grid does not possess a physical library.

Note: JC (EATC) and JK (EAETC) media types are only available if the highest common format (HCF) is set to E07 or higher.

Note: Before a stacked volume with active virtual volumes can be ejected, all active logical volumes in it are copied to a different stacked volume.

Tip: When inserting a VOLSER that belongs to a defined TS7720T or TS7740 range, it is presented and inventoried according to the setup in place. If the newly inserted VOLSER does not belong to any defined range in the TS7720T or TS7740, an intervention-required message is generated, requiring the user to correct the assignment for this VOLSER.

Important: If a physical volume range contains virtual volumes with active data, those virtual volumes must be moved or deleted before the physical volume range can be moved or deleted.

Note: JA and JJ media are only supported for read-only operations with 3592 E07 Tape Drives.

Note: JA and JJ media are only supported for read-only operations with 3592 E07 Tape Drives.

Note: Only one search can be run at a time. If a search is in progress, an information message displays at the top of the Physical Volume Search page. You can cancel a search in progress by clicking Cancel Search within this message.

Note: Only one search can be run at a time. If a search is in progress, an information message displays at the top of the Physical Volume Search page. You can cancel a search in progress by clicking Cancel Search within this message.

Note: The search-in-progress message is displayed on the Physical Volume Search page until the in-progress search completes or is canceled.

Tip: This percentage is a hyperlink; click it to open the Modify Pool Properties page, where you can modify the percentage that is used for this threshold.

Tip: This page is not visible on the TS7700 Virtualization Engine MI if the grid does not possess a physical library.

Note: If you are monitoring this field while changing the encryption status of a drive, the new status will not display until you bring the TS7700 Cluster offline and then return it to an online state.

Tip: This page is not visible on the TS7700 Virtualization Engine MI if the grid does not possess a physical library.

Tip: A value in the Full field is displayed as a hyperlink; click it to open the Active Data Distribution subpage. The Active Data Distribution subpage displays a graphical representation of the number of physical volumes per utilization increment in a pool. If no full volumes exist, the hyperlink is disabled.

Restriction: If the cluster does not possess a physical library, the Primary Pool field is not available in the Add or Modify options.

Remember: If the cluster does not possess a physical library, the Secondary Pool field is not available in the Add option.

Restriction: You cannot delete the default Management Class.

Important: Scratch (Fast Ready) categories and Data Classes work at the system level and are unique for all clusters in a grid. Therefore, if you modify them on one cluster, they are applied to all clusters in the grid.

Tip: You can create up to 256 Data Classes per TS7700 Virtualization Engine Grid.

Note: Before Release 3.0 (from R1.6 to R2.1), RBAC policies applied only to the MI.

Note: Define a user account for service, or select the boxes to enable IBM service personnel to log in to the machine (local and remote) before enabling external policies.

Important: Before enabling External policies, create an account that can be used by service personnel (local and remote), or select the boxes in MI to exclude IBM Service Representative (local and remote) from RBAC policies.

Tip: The Local Policy name is Local and cannot be modified.

Tip: Passwords for the users are changed from this window also.

Restriction: You cannot modify the user name or Group Name. Only the role and the clusters to which it is applied can be modified.

Important: When a Storage Authentication Service policy is enabled for a cluster, service personnel are required to log in with the setup user or group. Before enabling storage authentication, create an account that can be used by service personnel.

Remember: If the Primary or alternative Server URL uses the HTTPS protocol, a certificate for that address must be defined on the SSL Certificates page.

Tip: The policy needs to be configured to an LDAP server before being added in the TS7700 MI. External users and groups to be mapped by the new policy are checked in LDAP before being added.

Note: If the user name entered belongs to a user not included on the policy, test results show success, but the result comments show a null value for the role and access fields. Additionally, the user name entered cannot be used to log in to the MI.

Important: When a Direct LDAP policy is enabled for a cluster, service personnel are required to log in with the setup user or group. Before enabling LDAP authentication, create an account that can be used by service personnel. From R3.1 on, you can enable an IBM Service Representative to connect to your TS7700 through physical access or remotely by selecting those options in the DIRECT LDAP POLICY page.

Note: LDAP external authentication policies are not available for backup or recovery through the backup or restore settings operations. Record it, keep it safe, and have it available for a manual recovery as dictated by your security standards.

Remember: You can apply the permissions of a predefined role to a custom role by selecting a role from the Role Template menu and clicking Apply. You can then customize the permissions by selecting or clearing tasks.

Note: Any modifications to IP addresses on the accessing cluster interrupt access to that cluster for all current users. If the accessing cluster IP addresses are modified, the current users are redirected to the new virtual address.

Important: Enabling grid encryption significantly affects the performance of the TS7700 Virtualization Engine. System performance can be reduced by 70% or more when grid encryption is enabled.

Note: You can back up these settings as part of the ts7700_cluster<cluster ID>.xmi file and restore them for later use. When the backup settings are restored, new settings are added but no settings are deleted. You cannot restore feature license settings to a cluster different from the cluster that created the ts7700_cluster<cluster ID>.xmi backup file. After you restore feature license settings on a cluster, it is suggested that you log out and then log in to refresh the system.

Note: A user with read-only permissions cannot modify the contents of the Destination Settings table.

Tip: A valid IPv4 address is 32 bits long, consists of four decimal numbers, each ranging from 0 - 255, separated by periods, such as 98.104.120.12 A valid IPv6 address is a 128-bit long hexadecimal value separated into 16-bit fields by colons, such as 3afa:1910:2535:3:110:e8ef:ef41:91cf. Leading zeros can be omitted in each field, so that :0003: can be written as :3:. A double colon (::) can be used once per address to replace multiple fields of zeros. For example, 3afa:0:0:0:200:2535:e8ef:91cf” is also 3afa::200:2535:e8ef:91cf”.

Note: Any change to SNMP settings is logged on the Tasks page.

Tip: This page is only visible if at least one instance of FC5271 (Selective device access control (SDAC)) is installed on all clusters in the grid.

Important: VOLSERs not found in the Selective Device Access Control (SDAC) VOLSER range table use this default group to determine access. You can modify this group to remove any or all default Library Port IDs. However, if all default Library Port ID values are removed, no access is granted to any volumes not in a defined range.

Note: Access groups and access group ranges are backed up and restored together. For additional information, see “Backup settings” on page 460 and “Restore Settings page” on page 463.

Note: This override can be enabled independently of the status of the copies in the cluster.

Note: These settings override the default TS7700 Virtualization Engine behavior and can be different for every cluster in a grid.

Tip: This page is not visible on the TS7700 Virtualization Engine MI if the grid does not possess a physical library.

Note: Inhibit Reclaim schedules cannot overlap.

Note: Plan the Inhibit Reclaim schedules carefully. Running the reclaims during peak times can affect your production, and not having enough reclaim schedules influences your media consumption.

Tip: This page is not visible on the TS7700 Virtualization Engine MI if the grid does not possess a physical library.

Note: Your Encryption Key Server software must support default keys to use this option.

Tip: You can back up these settings as part of the ts7700_cluster<cluster ID>.xmi file and restore them for later use or use with another cluster. If a key server address is empty at the time that the backup is run, when it is restored, the port settings are the same as the default values.

Tip: A valid IPv4 address is 32 bits long, consists of four decimal numbers, each 0 - 255, separated by periods, such as 98.104.120.12. A valid IPv6 address is a 128-bit long hexadecimal value separated into 16-bit fields by colons, such as 3afa:1910:2535:3:110:e8ef:ef41:91cf. Leading zeros can be omitted in each field, so that :0003: can be written as :3:. A double colon (::) can be used once per address to replace multiple fields of zeros. For example, 3afa:0:0:0:200:2535:e8ef:91cf can be written as: 3afa::200:2535:e8ef:91cf.

Note: Flash Copy is enabled from LI REQ (Library Request Host Console) command.

Important: Backup and restore functions are not supported between clusters operating at different code levels. Only clusters operating at the same code level as the accessing cluster (the one addressed by the web browser) can be selected for Backup or Restore. Clusters operating different code levels are visible, but options are disabled.

Note: If the cluster does not possess a physical library, physical volume pools are not available.

Note: If the cluster does not possess a physical library, the Inhibit Reclaim Schedules option is not available.

Note: This setting is only available if all clusters in the grid are operating with microcode levels of 8.20.0.xx or higher and the SDAC feature is installed.

Important: A restore operation after a backup of cluster settings does not restore or otherwise modify any user, role, or password settings defined by a security policy.

Note: You can back up these settings as part of the ts7700_cluster<cluster ID>.xmi file and restore them for later use on the same cluster. However, you cannot restore feature license settings to a cluster different from the cluster that created the ts7700_cluster<cluster ID>.xmi backup file.

Important: A restore operation after a backup of cluster settings does not restore or otherwise modify any user, role, or password settings defined by a security policy.

Important: If you navigate away from this page while the backup is in progress, the backup operation is stopped and the operation must be restarted.

Restriction: Backup and restore functions are not supported between clusters operating at different code levels. Only clusters operating at the same code level as the current cluster can be selected from the Current Cluster Selected graphic. Clusters operating at different code levels are visible, but not available, in the graphic.

Important: If the backup file was created by a cluster that did not possess a physical library, physical volume pool settings are reset to default.

Note: If the backup file was created by a cluster that did not possess a physical library, the Inhibit Reclaim schedules settings are reset to default.

Important: Changes to network settings affect access to the TS7700 MI. When these settings are restored, routers that access the TS7700 MI are reset. No TS7700 grid communications or jobs are affected, but any current users are required to log back on to the TS7700 MI using the new IP address.

Note: You cannot restore feature license settings to a cluster different from the cluster that created the ts7700_cluster<cluster ID>.xmi backup file.

Note: The restore operation overwrites existing settings on the cluster.

Important: If you navigate away from this page while the restore is in progress, the restore operation is stopped and the operation must be restarted.

Note: You can modify this field even if a Copy Export operation is running, but the changed value will not take effect until the next Copy Export operation starts.

Note: Copy Export Recover or Copy Export Recover Status are only available in a single cluster configuration for TS7740 or TS7720T.

Note: Have the Management Interface IP addresses for all clusters in the configuration available for use so that if one cluster fails you can still access the MI.

Important: An IBM SSR must configure the TSSC IP addresses for each cluster in the grid before AOTM can be enabled and configured for any cluster in the grid.

Read/write ownership takeover mode		Read-only ownership takeover mode
Operational clusters in the grid can run these tasks: •Perform read and write operations on the virtual volumes owned by the failed cluster. •Change virtual volumes owned by the failed cluster to private or SCRATCH status.		Operational clusters in the grid can run these tasks: •Perform read operations on the virtual volumes owned by the failed cluster. Operational clusters in the grid cannot run these tasks: •Change the status of a volume to private or scratch. •Perform read and write operations on the virtual volumes owned by the failed cluster.
A consistent copy of the virtual volume must be available on the grid or the virtual volume must exist in a scratch category. If no cluster failure occurred (grid links down) and the ownership takeover was started by mistake, the possibility exists for two sites to write data to the same virtual volume.		If no cluster failure occurred, it is possible that a virtual volume accessed by another cluster in read-only takeover mode contains older data than the one on the owning cluster. This situation can occur if the virtual volume was modified on the owning cluster while the communication path between the clusters was down. When the links are reestablished, those volumes are marked in error.

Important: The Traceroute command is intended for network testing, measurement, and management. It imposes a heavy load on the network and should not be used during normal operations.

Note: Time periods covered by TS7700 Log Collection files cannot overlap. If you attempt to generate a log file that includes a time period covered by an existing log file, a message prompts you to select a different value for the hours field.

Note: Data collected during this operation is not automatically forwarded to IBM. You must contact IBM and open a problem management report (PMR) to manually move the collected data off the system.

Important: If you start data collection on a cluster in service mode, you might not be able to check the progress of data collection. Tasks page is not available for clusters in service mode, so there is no link to it in message.

Tip: This page is only visible in a single TS7740 or TS7720T configuration (both of which are connected to a physical tape library).

Important: In a grid configuration, each TS7700 Virtualization Engine is considered a separate source. Therefore, only the physical volume that is exported from a source TS7700 Virtualization Engine can be used for the recovery of that source. Physical volumes exported from more than one source TS7700 Virtualization Engine in a grid configuration cannot be combined to use in recovery. Recovery can occur only to a single cluster configuration; the TS7700 Virtualization Engine used for recovery must be configured as Cluster 0.

Note: The number of virtual volumes that can be recovered depends on the number of FC5270 licenses installed on the TS7700 Virtualization Engine used for recovery. Additionally, a recovery of more than 2 million virtual volumes must be run by a TS7740 Virtualization Engine operating with a 3957-V07 and a code level of 8.30.0.xx or higher.

Important: The Copy Export recovery status is only available in a single cluster configuration for a TS7700 grid.

Important: •Each TS7740 or TS7720T Virtualization Engine requires its own logical library in a TS3500 Tape Library. •The ALMS feature must be installed and enabled to define a logical library partition in the TS3500 Tape Library.

Tip: You can create or remove a logical library from the TS3500 Tape Library by using the Tape Library Specialist web interface.

Restriction: No intermix of tape drive models is supported by TS7740. The only exception is 3592-E05 Tape Drives working in J1A emulation mode and 3592-J1A Tape Drives (the first and second generation of the 3592 Tape Drives). TS1130 (3592 Model E06) and TS1140 (3592 Model E07) cannot be intermixed with any other model of 3592 Tape Drive within the same TS7740 or TS7720T.

Restriction: Do not share drives belonging to a TS7720T or TS7740. They must be exclusive.

Restriction: Do not change drive assignments if they belong to an operating TS7740, TS7720T, or tape controller. Work with your IBM SSR, if necessary.

Important: In a System z environment, use the Drive Assignment window only for these functions: •Initially assign the tape drives from TS3500 Tape Library Web Specialist to a logical partition. •Assign more tape drives after they have been attached to the TS7740 Virtualization Engine or a tape controller. •Remove physical tape drives from the configuration after they are physically detached from the TS7740 Virtualization Engine or tape controller. In addition, never disable ALMS at the TS3500 Tape Library after it has been enabled for System z host support and System z tape drive attachment.

Reminders: •When using encryption, tape drives must be set to Native mode. •To activate encryption, FC9900 must have been ordered for the TS7400 or the TS7720T, and the license key must be installed. In addition, the associated tape drives must be Encryption Capable 3592-E05, 3592-E06, or 3952-E07 (although it is supported, 3592-J1A is unable to encrypt data).

Important: Keep the Advanced Encryption Settings as NO ADVANCED SETTING, unless set otherwise by IBM Engineering.

Tip: The Cartridge Assignment Policy does not reassign an already assigned tape cartridge. If needed, you must first unassign it, then manually reassign it.

Important: Before inserting TS7740 or TS7720T Virtualization Engine physical volumes into the tape library, ensure that the VOLSER ranges are defined correctly at the TS7700 MI. For more information, see “Defining VOLSER ranges for physical volumes” on page 498.

Important: With ALMS enabled, cartridges that are not in a CAP are not added to any logical library.

Tip: Only place cartridges in a frame whose front door is open. Do not add or remove cartridges from an adjacent frame.

Restriction: Insert Notification is not supported on a high-density library. If a cartridge outside the CAP-defined ranges is inserted, it remains unassigned without any notification.

Important: Unassigned cartridges can exist in the TS3500 Tape Library, and in the TS7700 Virtualization Engine MI. However, unassigned has separate meanings and requires separate actions from the operator in each system.

Clarifications: •Insert Notification is not supported in a high-density library. The CAP must be correctly configured to provide automated assignment of all the inserted cartridges. •A cartridge that has been manually assigned to the TS7700 Logical Library does not display automatically in the TS7740 or TS7720T inventory. An Inventory Upload is needed to refresh the TS7700 cluster inventory. The Inventory Upload function is available on the Physical Volume Ranges menu as shown in Figure 8-160. •Cartridge assignment to a logical library is available only through the TS3500 Tape Library Specialist web interface. The operator window does not provide this function.

Remember: •TS7740 or TS7720T requires ALMS to be installed and enabled in the TS3500 Tape Library. ALMS sets cleaning mode to automatic. Therefore, library manages drive cleaning. •A cleaning cartridge is good for 50 cleaning actions.

Tip: Cleaning cartridge are not assigned to specific logical libraries.

Important: •When using a TS3500 Tape Library, you must assign the CAP at the library hardware level before using the library with System z hosts. •When using a TS3500 Tape Library and the TS7740 or TS7720T Virtualization Engine, physical volumes must fall within ranges that are assigned by the CAP to the Logical Library belonging to this cluster in the TS3500 Tape Library.

Important: Operator intervention is required to resolve unassigned volumes.

Important: Modifying a predefined VOLSER range will not affect physical volumes that are already inserted and assigned to the TS7740 or TS7720T Virtualization Engine. Only physical volumes that are inserted after the VOLSER range modification are changed.

Restriction: VOLSER ranges defined at the IBM TS3500 Tape Library user interface refer exclusively to physical cartridges. Logical Volumes are defined only through the TS7700 Virtualization Engine MI. See “Inserting virtual volumes” on page 514 for more information.

Tip: Pools 1 - 32 are preinstalled. Pool 1 functions as the default pool and is used if no other pool is selected.

Tip: A tutorial is available at the Physical Volume Pools page to show you how to modify encryption properties.

Restriction: Your encryption key manager software must support default keys to use this option.

Clarification: Each reclamation task uses two tape drives (source and target) in a tape-to-tape copy function. The TS7700 Tape Volume Cache is not used for reclamation.

Number of available drives	Maximum number of reclaims
3	1
4	1
5	1
6	2
7	2
8	3
9	3
10	4
11	4
12	5
13	5
14	6
15	6
16	7

Tip: The maximum number of inhibit reclaim schedules is 14.

Important: A physical volume pool running out of scratch cartridges might stop mounts in the TS7740 or TS7720T tape attach partitions, affecting your operations. Mistakes in pool configuration (media type, borrow and return, home pool, and so on) or operating with an empty common scratch pool might lead to this situation.

Priority	Condition	Reclaim schedule honored	Active data threshold% honored	Number of concurrent reclaims	Comments
1	Pool in Panic scratch state	No	No	At least one, regardless of idle drives. If more idle drives are available, more reclaims are started, up to the maximum limit.
2	Priority move	Yes or No	No	At least one, regardless of idle drives. If more idle drives are available, more reclaims are started, up to the maximum limit.	If a volume is within 10 days of a Secure Data Erasure and still has active data on it, it is reclaimed at this priority. An SDE priority move accepts the inhibit reclaim schedule.   For a TS7700 MI-initiated priority move, the option to accept the inhibit reclaim schedule is given to the operator.
3	Pool in Low scratch state	Yes	Yes	At least one, regardless of idle drives. If more idle drives are available, more reclaims are started, up to the maximum limit.	Volumes that are subject to reclaim because of Maximum Active Data, Days Without Access, Age of Last Data Written, and Days Without Data Inactivation use priority 3 or 4 reclamation.
4	Normal reclaim	Yes	Yes, pick from all eligible pools	(Number of idle drives divided by 2) minus 1   8 drv: 3 max 16 drv: 7 max	Volumes that are subject to reclaim because of Maximum Active Data, Days Without Access, Age of Last Data Written, and Days Without Data Inactivation use priority 3 or 4 reclamation.

Tips: •A physical drive is considered idle when no activity has occurred for the previous 10 minutes. •The Inhibit Reclaim schedule is not accepted by the Secure Data Erase function for a volume that has no active data.

Consideration: The two encryption key servers must be set up on separate systems to provide redundancy. Connection to a key manager is required to read encrypted data.

Important: When using z/OS, do not specify constructs when the volumes are added. Instead, they are assigned during job processing when a volume is mounted and written from the load point.

Restriction: You can insert up to 10,000 logical volumes at one time. This applies to both inserting a range of logical volumes and inserting a quantity of logical volumes.

Tip: Do not add a scratch category using MI that was previously designated as a private volume category at the host. Categories should correspond to the defined categories in the DEVSUPxx from the attached hosts.

Number of virtual volumes: You cannot arrive at the total number of virtual volumes by adding all volumes shown in the Counts column, because some rare, internal categories are not displayed on the Categories table. Additionally, movement of virtual volumes between scratch and private categories can occur multiple times per second and any snapshot of volumes on all clusters in a grid is obsolete by the time a total count completes.

Important: Do not use category name 0000 or FFxx, where xx equals 0 - 9 or A - F. 0000 represents a null value, and FFxx is reserved for hardware.

Note: If you select No Expiration, volume data never automatically delete-expires.

Restriction: Trying to mount a non-expired volume that belongs to a scratch (Fast Ready) category with Expire Hold on results in an error.

Tip: Add a comment to DEVSUPnn to ensure that the scratch (Fast Ready) categories are updated when the category values in DEVSUPnn are changed. They always need to be in sync.

Remember: •Scratch (Fast Ready) categories are global settings within a multicluster grid. Therefore, each defined scratch (Fast Ready) category and the associated Delete Expire settings are valid on each cluster of the grid. •The Delete Expired Volume Data setting applies also to TS7720 clusters. If it is not used, logical volumes that have been returned to scratch are still considered active data, allocating physical space in the TVC. Therefore, setting an expiration time on TS7720 is important to maintain an effective cache usage by deleting expired data.

Restriction: If the cluster is not attached to a physical library, the Primary Pool field is not available in the Add or Modify menu options.

Important: Do not delete any existing Storage Group if there are still logical volumes assigned to that Storage Group.

Tip: If cluster is not attached to a physical library, the Secondary Pool field is not available in the Add option.

Important: Care must be taken when assigning volumes to this group to avoid cache overruns.

Important: Do not delete any existing storage class if there are still logical volumes assigned to this storage class.

Rules: Support for 25,000 MiB logical volumes is allowed without any restriction if all TS7700 clusters in grid operate at R3.2 of LIC level. 25000 MiB is not supported in mixed code-level grids (members not exclusively at R3.2) with one or more TS7740 cluster present in grid. For disk-only grids (no tape-attached member) Feature Code 0001 is required in each TS7720 operating at levels earlier than R3.2 LIC.

Tip: You can create up to 256 Data Classes per TS7700 Virtualization Engine Grid.

Important: Do not delete any existing Data Class if there are still logical volumes assigned to this Data Class.

Clarification: Cache enablement license key (FC5267) applies only to a TS7740 cluster, where Maximum amount of queued premigration content (FC5274) only applies to TS7720T tape attach configuration.

Important: Do not remove any installed peak data throughput features, because removal can affect host jobs. Some feature codes are not removable after being installed.

Tip: Performance Increments become active immediately. Others, such as Cache Increments or FICON dual port enablement, take 10 - 30 minutes to become active.

Restriction: A user with read-only permissions cannot modify the contents of the Destination Settings table.

Tip: The client network must use whether IPv4 or IPv6 for all functions, such as MI, key manager server, SNMP, Lightweight Directory Access Protocol (LDAP), and Network Time Protocol (NTP). Mixing IPv4 and IPv6 is not currently supported.

Caution: Enabling grid encryption significantly affects the performance of the TS7700 Virtualization Engine.

Important: When a Storage Authentication Service policy is enabled for a cluster, service personnel are required to log in with the setup user or group. Be sure that an account has been created for the service personnel before enabling storage authentication.

Important: When a Storage Authentication Service policy is enabled for a cluster, service personnel are required to log in with the setup user or group. Be sure that an account has been created for the service personnel before enabling storage authentication.

Tip: A stand-alone grid (stand-alone TS7700 Virtualization Engine) always uses Rewind Unload (RUN) as the Data Consistency Point.

Restriction: In a Geographically Dispersed Parallel Sysplex (GDPS), all three Copy Policy Override settings (cluster overrides for certain I/O and copy operations) must be selected on each cluster to ensure that wherever the GDPS primary site is, this TS7700 Virtualization Engine cluster is preferred for all I/O operations. If the TS7700 Virtualization Engine cluster of the GDPS primary site fails, you must complete the following recovery actions: 1. Vary virtual devices from a remote TS7700 Virtualization Engine cluster online from the primary site of the GDPS host. 2. Manually start, through the TS7700 Virtualization Engine MI, a read/write Ownership Takeover, unless Autonomic Ownership Takeover Manager (AOTM) has already transferred ownership.

Note: Scratch mount candidate list as defined in MI (Figure 8-190) is only accepted upon being enabled using the LI REQ setting.

Note: The Retain Copy mode option is effective only on private (non-Fast Ready) virtual volume mounts.

Restriction: A maximum of eight cluster families can be created.

Restriction: Each cluster family must contain at least one cluster. If you attempt to save changes and a cluster family does not contain any clusters, an error message is displayed and the Cluster families page remains in edit mode.

Important: Each cluster family needs to contain at least one cluster.

Clarification: Host writes to the TS7720 cluster and inbound copies continue during this state.

Clarification: New host allocations do not choose a TS7720 cluster in this state as a valid TVC candidate. New host allocations sent to a TS7720 cluster in this state choose a remote TVC instead. If all valid clusters are in this state or unable to accept mounts, the host allocations fail. Read mounts can choose the TS7720 cluster in this state, but modify and write operations fail. Copies inbound to this TS7720 cluster are queued as Deferred until the TS7720 cluster exits this state.

State	Enter state (free space available)	Exit state (free space available)	Host message displayed
Automatic removal	< 4 TB	> 3.5 TB	CBR3750I when automatic removal begins
Limited free cache space warning	< 3 TB	> 3.5 TB	CBR3792E upon entering state CBR3793I upon exiting state
Out of cache resources	< 1 TB	> 3.5 TB	CBR3794A upon entering state CBR3795I upon exiting state
Temporary removal1	< (X = 1 TB)2	> (X + 1.5 TB)b	Console message

---

Note: Logical volumes are only removed if there is another consistent copy within the grid.

Tip: This field is only visible if the selected cluster is a TS7720 Virtualization Engine in a grid configuration.

Note: This process does not initiate Service Prep mode.

Note: Unless you have a strong reason not to, use Coordinated Universal Time in all TS7700 clusters.

Tip: Before starting service preparation at the TS7700 Virtualization Engine, all virtual devices on this cluster must be in offline state to the accessing hosts. Pending offline devices (logical volumes mounted to local or remote TVC) with active tasks should be allowed to finish execution and volumes to unload, completing transition to offline state. Virtual devices in other clusters should be made online to provide mount point to new jobs, shifting workload to other clusters in the grid before start service preparation. After scheduled maintenance finishes and TS7700 can be taken out of service, then virtual devices can be varied back online for accessing hosts.

Note: Perform Inventory if there is no high-density frame installed on the tape library. Perform Inventory will inventory high-density frame cells only for the first cartridge unless the first cartridge differs from the stored library inventory. Perform Inventory with Audit will inventory all cells in a high-density frame.

Important: As stated on the confirmation window (Figure 8-200), if you continue, all jobs in the work queue might be delayed while the request is run. The inventory takes up to 1 minute per frame. The audit takes up to 1 hour per high-density frame.

Note: Perform the Inventory Upload from the TS3500 Tape Library to all TS7740 or TS7720T Virtualization Engines attached to that tape library whenever a library door is closed, manual inventory or Inventory with Audit is run, or TS7700 cluster is varied online from an offline state.

Note: Inserted volumes should belong also to a Physical Volume Range defined in the corresponding TS7740 or TS7720T cluster. Otherwise, they show as Unassigned in the TS7700 MI.

Tips: •The inventory is performed only on the frame where the door is opened and not on the frames to either side. If you insert cartridges into a frame next to the frame that you opened, you must perform a manual inventory of the adjacent frame using the operator window on the TS3500 Tape Library itself. •For a TS7740 or TS7720T Virtualization Engine, it is important to note that the external cartridge bar code label and the internal VOLID label match or, as is the case for a new cartridge, the internal VOLID label is blank. If the external label and the internal label do not meet this criteria, the cartridge is rejected.

Note: TS3500 disables Insert Notification for High Density frame configurations.

Consideration: Unassigned cartridges can exist in the TS3500 Tape Library, but unassigned cartridges can have different meanings and need different actions. For more information, see IBM System Storage TS3500 Tape Library with ALMS Operator Guide, GA32-0594.

Important: In a TS7720T cluster, only the tape attached partitions are affected.

Important: Repairing a 3592 tape must be done only for data recovery. After the data is moved to a new volume, replace the repaired cartridge.

Tip: Always see the appropriate documentation (TS7700 IBM Knowledge Center and MVS System Messages) for the meaning of the messages and the applicable recovery actions.

---