Troubleshooting and diagnostics
IBM Spectrum Virtualize is a robust and reliable virtualization engine that demonstrated excellent availability in the field. However, today’s storage area networks (SANs), storage subsystems, and host systems are external components that might cause some events.
This chapter provides an overview of common events that can occur in your environment. It describes situations that are related to IBM Spectrum Virtualize, Storwize, the SAN environment, storage subsystems, hosts, and multipathing drivers. It also explains how to collect the necessary problem determination data.
This chapter includes the following sections:
•Health status during upgrade
10.1 Common issues
SANs, storage subsystems, and host systems can be complicated. They often consist of hundreds or thousands of disks, multiple redundant subsystem controllers, virtualization engines, and different types of SAN switches. All of these components must be configured, monitored, and managed properly. If issues occur, administrators must know what to look for and where to look.
With functions that are native in IBM Spectrum Virtualize, administrators can easily locate any issue areas and take the necessary steps to fix any events. In many cases, IBM Spectrum Virtualize and its service and maintenance features guide administrators directly, provide help, and suggest remedial action. Furthermore, IBM Spectrum Virtualize detemines whether the problem still persists or not.
When you experience events in the IBM Spectrum Virtualize environment, ensure that all components that comprise the storage infrastructure are interoperable. In an IBM Spectrum Virtualize environment, the IBM Spectrum Virtualize support matrix is the main source for this information. For the latest IBM Spectrum Virtualize V7.8 support matrix, see V7.8 Supported Hardware List, Device Driver, Firmware and Recommended Software Levels, available at these websites:
•IBM Spectrum Virtualize
•Storwize V7000
Although the latest IBM Spectrum Virtualize code level is supported to run on older host bus adapters (HBAs), storage subsystem drivers, and code levels, use the latest tested levels for best results.
10.1.1 Host problems
From the host perspective, you can experience various situations that range from performance degradation to inaccessible disks. To diagnose these issues, you can check items from the host before you drill down to the SAN, IBM Spectrum Virtualize, and storage subsystems.
Check the following areas on the host:
•Any special software that you are using
•Any recent change in the OS, such as patching the OS, an upgrade, and so on
•Operating system version and maintenance or service pack level
•Multipathing type and driver level
•Host bus adapter model, firmware, and driver level
•Host bus adapter connectivity issues
Based on this list, the host administrator must check and correct any problems.
For more information about managing hosts on IBM Spectrum Virtualize, see Chapter 6, “Hosts” on page 229.
10.1.2 IBM Spectrum Virtualize events
IBM Spectrum Virtualize has some useful error logging mechanisms. It keeps track of its internal events and informs the user about issues in the SAN or storage subsystem. It also helps to isolate problems with the attached host systems. Every IBM Spectrum Virtualize node maintains a database of other devices that are visible in the SAN fabrics. This database is updated as devices appear and disappear.
Fast node reset
The IBM Spectrum Virtualize Cluster software incorporates a fast node reset function. The intention of a fast node reset is to avoid I/O errors and path changes from the perspective of the host if a software problem occurs in one of the IBM Spectrum Virtualize nodes.
The fast node reset function means that IBM Spectrum Virtualize software issues can be recovered without the host experiencing an I/O error and without requiring the multipathing driver to fail over to an alternative path. The fast node reset is performed automatically by the IBM Spectrum Virtualize node. This node informs the other members of the cluster that it is resetting.
Other than IBM Spectrum Virtualize node hardware and software events, failures in the SAN zoning configuration are a problem. A misconfiguration in the SAN zoning might lead to the IBM Spectrum Virtualize cluster not working properly, This problem occurs because the IBM Spectrum Virtualize cluster nodes communicate with each other by using the Fibre Channel SAN fabrics.
Check the following areas from an IBM Spectrum Virtualize perspective:
•The attached hosts. For more information, see 10.1.1, “Host problems” on page 342.
•The SAN. For more information, see 10.1.3, “SAN events” on page 345.
•The attached storage subsystem. For more information, see 10.1.4, “Storage subsystem issues” on page 345.
•The local FC port masking. See 6.1.5, “Port masking” on page 232 for more details.
IBM Spectrum Virtualize has several CLI commands that you can use to check the status of IBM Spectrum Virtualize and the attached storage subsystems. Before you start a complete data collection or problem isolation on the SAN or subsystem level, use the following commands first and check the status from the IBM Spectrum Virtualize perspective:
•svcinfo lscontroller controllerid
Check that multiple worldwide port names (WWPNs) that match the back-end storage subsystem controller ports are available.
Check that the path_counts are evenly distributed across each storage subsystem controller, or that they are distributed correctly based on the preferred controller. Use the path_count calculation that is described in 10.3.4, “Solving back-end storage issues” on page 353. The total of all path_counts must add up to the number of managed disks (MDisks) multiplied by the number of IBM Spectrum Virtualize nodes.
•svcinfo lsmdisk
Check that all MDisks are online (not degraded or offline).
•svcinfo lsmdisk mdiskid
Check several of the MDisks from each storage subsystem controller. Are they online? Do they all have path_count = number of backend ports in the zone to IBM Spectrum Virtualize x number of nodes? See Example 10-1 for an example of the output from this command.
Example 10-1 Issuing an lsmdisk command
IBM_2145:itsosvccl1:superuser>lsmdisk 0
id 0
name flash9h01_itsosvccl1_0
status online
mode managed
mdisk_grp_id 0
mdisk_grp_name Pool0
capacity 1.6TB
quorum_index
block_size 512
controller_name itsoflash9h01
ctrl_type 4
ctrl_WWNN 500507605E852080
controller_id 1
path_count 32
max_path_count 32
ctrl_LUN_# 0000000000000000
UID 6005076441b53004400000000000000100000000000000000000000000000000
preferred_WWPN
active_WWPN many
fast_write_state empty
raid_status
raid_level
redundancy
strip_size
spare_goal
spare_protection_min
balanced
tier ssd
slow_write_priority
fabric_type fc
site_id
site_name
easy_tier_load very_high
encrypt yes
distributed no
drive_class_id
drive_count 0
stripe_width 0
rebuild_areas_total
rebuild_areas_available
rebuild_areas_goal
IBM_2145:itsosvccl1:superuser>
Example 10-1 shows that the Flash900 has eight ports zoned to IBM Spectrum Virtualize, and IBM Spectrum Virtualize has four nodes, so 8 x 4 = 32.
•svcinfo lsvdisk
Check that all volumes are online (not degraded or offline). If the volumes are degraded, are there stopped FlashCopy jobs? Restart any stopped FlashCopy jobs or seek IBM Spectrum Virtualize support guidance.
•svcinfo lshostvdiskmap
Check that all volumes are mapped to the correct hosts. If a volume is not mapped correctly, create the necessary host mapping.
•svcinfo lsfabric
Use this command with the various options, such as -controller controllerid. Also, check different parts of the IBM Spectrum Virtualize configuration to ensure that multiple paths are available from each IBM Spectrum Virtualize node port to an attached host or controller. Confirm that all IBM Spectrum Virtualize node port WWPNs are connected to the back-end storage consistently.
10.1.3 SAN events
Introducing IBM Spectrum Virtualize into your SAN environment and the use of its virtualization functions are not difficult tasks. However, before you can use IBM Spectrum Virtualize in your environment, you must follow some basic rules. These rules are not complicated, but you can make mistakes that lead to accessibility issues or a reduction in the performance experienced.
Two types of SAN zones are needed to run IBM Spectrum Virtualize in your environment: A host zone and a storage zone. In addition, you must have an IBM Spectrum Virtualize zone that contains all of the IBM Spectrum Virtualize node ports of the IBM Spectrum Virtualize cluster. This IBM Spectrum Virtualize zone enables intracluster communication. For more information and important points about setting up IBM Spectrum Virtualize in a SAN fabric environment, see Chapter 1, “Storage area network topology” on page 1.
Because IBM Spectrum Virtualize is in the middle of the SAN and connects the host to the storage subsystem, check and monitor the SAN fabrics.
10.1.4 Storage subsystem issues
Today, various heterogeneous storage subsystems are available. All of these subsystems have different management tools, different setup strategies, and possible problem areas depending on the manufacturer. To support a stable environment, all subsystems must be correctly configured, following the respective preferred practices and with no existing issues.
Check the following areas if you experience a storage-subsystem-related issue:
•Storage subsystem configuration. Ensure that a valid configuration and preferred practices are applied to the subsystem.
•Storage controller. Check the health and configurable settings on the controllers.
•Array. Check the state of the hardware, such as a disk drive module (DDM) failure or enclosure alerts.
•Storage volumes. Ensure that the logical unit number (LUN) masking is correct.
•Host attachment ports. Check the status and configuration.
•Connectivity. Check the available paths (SAN environment).
•Layout and size of RAID arrays and LUNs. Performance and redundancy are contributing factors.
For more information about managing subsystems, see Chapter 2, “Back-end storage” on page 37.
Determining the correct number of paths to a storage subsystem
By using IBM Spectrum Virtualize CLI commands, it is possible to determine the total number of paths to a storage subsystem. To determine the proper value of the available paths, use the following formula:
Number of MDisks x Number of SVC nodes per Cluster = Number of paths
mdisk_link_count x Number of SVC nodes per Cluster = Sum of path_count
Example 10-2 shows how to obtain this information by using the svcinfo lscontroller controllerid and svcinfo lsnode commands.
Example 10-2 Output of the svcinfo lscontroller command
IBM_2145:itsosvccl1:superuser>lscontroller 1
id 1
controller_name itsof9h01
WWNN 500507605E852080
mdisk_link_count 16
max_mdisk_link_count 16
degraded no
vendor_id IBM
product_id_low FlashSys
product_id_high tem-9840
product_revision 1430
ctrl_s/n 01106d4c0110-0000-0
allow_quorum yes
fabric_type fc
site_id
site_name
WWPN 500507605E8520B1
path_count 64
max_path_count 64
WWPN 500507605E8520A1
path_count 64
max_path_count 64
WWPN 500507605E852081
path_count 64
max_path_count 64
WWPN 500507605E852091
path_count 64
max_path_count 64
WWPN 500507605E8520B2
path_count 64
max_path_count 64
WWPN 500507605E8520A2
path_count 64
max_path_count 64
WWPN 500507605E852082
path_count 64
max_path_count 64
WWPN 500507605E852092
path_count 64
max_path_count 64
IBM_2145:itsosvccl1:superuser>
IBM_2145:itsosvccl1:superuser>svcinfo lsnode
id name UPS_serial_number WWNN status IO_group_id IO_group_name config_node UPS_unique_id hardware iscsi_name iscsi_alias panel_name enclosure_id canister_id enclosure_serial_number site_id site_name
1 node1 500507680C003AE1 online 0 io_grp0 yes DH8 iqn.1986-03.com.ibm:2145.itsosvccl1.node1 78CBFEA0
2 node2 500507680C003ACA online 0 io_grp0 no DH8 iqn.1986-03.com.ibm:2145.itsosvccl1.node2 78CBRB0
3 node3 500507680C003A9F online 1 io_grp1 no DH8 iqn.1986-03.com.ibm:2145.itsosvccl1.node3 78CBLP0
4 node4 500507680C003DB6 online 1 io_grp1 no DH8 iqn.1986-03.com.ibm:2145.itsosvccl1.node4 78CCAQ0
IBM_2145:itsosvccl1:superuser>
Example 10-2 shows that sixteen MDisks are present for the storage subsystem controller with ID 1, and four IBM Spectrum Virtualize nodes are in the IBM Spectrum Virtualize cluster. In this example, the path_count is 16 x 4 = 64.
10.1.5 Port masking issues
Some situations of performance degradation and buffer-to-buffer credit exhaustion can be caused by incorrect local FC port masking and remote FC port masking. To have a healthy operation in your IBM Spectrum Virtualize, configure both your local FC port masking and your remote FC port masking accordingly. The ports intended to have only intracluster/node to node communication traffic must not have replication data or host/back-end data running on it. The ports intended to have only replication traffic must not have intracluster/node to node communication data or host/back-end data running on it.
10.2 Collecting data and isolating the problem
Data collection and problem isolation in an IT environment are sometimes difficult tasks. In the following section, the essential steps that are needed to collect debug data to find and isolate problems in an IBM Spectrum Virtualize environment are described.
10.2.1 Data collection
Data collection methods vary by operating system. You can collect the data for various major host operating systems.
First, collect the following basic information from the host:
•Operating system: Version and level
•HBA: Driver and firmware level
•Multipathing driver level
Regarding host, storage and SAN data collection, due to the dynamic changes that occur over time, follow this IBM w3 Connections community (only available to IBMers):
|
Note: This community is IBM internal only. You must use your intranet ID and password. If you are not an IBM employee, contact your IBM representative or the vendor of your hardware and follow the specific procedures for data collection.
|
The w3 Connections community has up-to-date procedures for several kinds of devices, including hosts, storage, and SAN, as shown in Figure 10-1.
Figure 10-1 CoC - Cookbook on Connections internal wiki
10.3 Recovering from problems
You can recover from several of the more common events that you might encounter. In all cases, you must read and understand the current product limitations to verify the configuration and to determine whether you need to upgrade any components or install the latest fixes or patches.
To obtain support for IBM products, see the following IBM Support website:
For more information about the latest flashes, concurrent code upgrades, code levels, and matrixes, see the following IBM Spectrum Virtualize website:
10.3.1 Solving host problems
Apart from hardware-related situations, problems can exist in such areas as the operating system or the software that is used on the host. These problems normally are handled by the host administrator or the service provider of the host system. However, the multipathing driver that is installed on the host and its features can help to determine possible issues.
Example 10-3 shows two faulty paths that are reported by the SDD output on the host by using the datapath query device -l command. The faulty paths are the paths in the close state. Faulty paths can be caused by hardware and software problems.
Example 10-3 SDD output on a host with faulty paths 
C:Program FilesIBMSubsystem Device Driver>datapath query device -l
Total Devices : 1
DEV#: 3 DEVICE NAME: Disk4 Part0 TYPE: 2145 POLICY: OPTIMIZED
SERIAL: 60050768018381BF2800000000000027
LUN IDENTIFIER: 60050768018381BF2800000000000027
============================================================================
Path# Adapter/Hard Disk State Mode Select Errors
0 Scsi Port2 Bus0/Disk4 Part0 CLOSE OFFLINE 218297 0
1 * Scsi Port2 Bus0/Disk4 Part0 CLOSE OFFLINE 0 0
2 Scsi Port3 Bus0/Disk4 Part0 OPEN NORMAL 222394 0
3 * Scsi Port3 Bus0/Disk4 Part0 OPEN NORMAL 0 0
Faulty paths can result from hardware issues, such as the following examples:
•Faulty Small Form-factor Pluggable transceiver (SFP) on the host or SAN switch
•Faulty fiber optic cables
•Faulty HBAs
Faulty paths can result from software problems, such as the following examples:
•A back-level multipathing driver
•Obsolete HBA firmware or driver
•Wrong zoning
•Incorrect host-to-VDisk mapping
Based on field experience, complete the following hardware checks first:
•Check whether any connection error indicators are lit on the host or SAN switch.
•Check whether all of the parts are seated correctly. For example, cables are securely plugged in to the SFPs and the SFPs are plugged all the way into the switch port sockets.
•Ensure that no fiber-optic cables are broken. If possible, swap the cables with cables that are known to work.
After the hardware check, continue to check the following aspects of software setup:
•Check that the HBA driver level and firmware level are at the preferred and supported levels.
•Check the multipathing driver level, and make sure that it is at the preferred and supported level.
•Check for link layer errors that are reported by the host or the SAN switch, which can indicate a cabling or SFP failure.
•Verify your SAN zoning configuration.
•Check the general SAN switch status and health for all switches in the fabric.
Example 10-4 shows that one of the HBAs was experiencing a link failure because of a fiber-optic cable that had bent over too far. After we changed the cable, the missing paths reappeared.
Example 10-4 Output from datapath query device command after fiber optic cable change
C:Program FilesIBMSubsystem Device Driver>datapath query device -l
Total Devices : 1
DEV#: 3 DEVICE NAME: Disk4 Part0 TYPE: 2145 POLICY: OPTIMIZED
SERIAL: 60050768018381BF2800000000000027
LUN IDENTIFIER: 60050768018381BF2800000000000027
============================================================================
Path# Adapter/Hard Disk State Mode Select Errors
0 Scsi Port3 Bus0/Disk4 Part0 OPEN NORMAL 218457 1
1 * Scsi Port3 Bus0/Disk4 Part0 OPEN NORMAL 0 0
2 Scsi Port2 Bus0/Disk4 Part0 OPEN NORMAL 222394 0
3 * Scsi Port2 Bus0/Disk4 Part0 OPEN NORMAL 0
10.3.2 Solving IBM Spectrum Virtualize events
For any events in an environment that is implementing IBM Spectrum Virtualize, use the Recommended Actions window before you try to fix the problem anywhere else. Find the Recommended Actions pane by clicking Monitoring → Events → Recommended Actions in the IBM Spectrum Virtualize Console GUI, as shown in Figure 10-2.
:Figure 10-2 Recommended Action window
The Recommended Actions window shows event conditions that require actions and the procedures to diagnose and fix them. The highest-priority event is indicated with information about how long ago the event occurred. If an event is reported, you must select the event and run a fix procedure.
Complete the following steps to retrieve properties and sense about a specific event:
1. Select an event in the table.
|
Tip: You can also obtain access to the Properties by right-clicking an event.
|
Figure 10-3 Opening Properties in the GUI
3. In the Properties and Sense Data for Event sequence_number window (see Figure 10-4, where sequence_number is the sequence number of the event that you selected in the previous step), review the information. Then, click Close.
Figure 10-4 Properties and sense data for event window
|
Tip: From the Properties and Sense Data for Event Window, you can use the Previous and Next buttons to move between events.
|
You now return to the Recommended Actions window.
Another common practice is to use the IBM Spectrum Virtualize CLI to find issues. The following list of commands provides information about the status of your environment:
•svctask detectmdisk
Discovers changes in the back-end storage configuration.
•svcinfo lscluster clustername
Checks the IBM Spectrum Virtualize cluster status.
•svcinfo lsnode nodeid
Checks the IBM Spectrum Virtualize nodes and port status.
•svcinfo lscontroller controllerid
Checks the back-end storage status.
•svcinfo lsmdisk
Provides a status for all of the MDisks.
•svcinfo lsmdisk mdiskid
Checks the status of a single MDisk.
•svcinfo lsmdiskgrp
Provides a status for all of the storage pools.
•svcinfo lsmdiskgrp mdiskgrpid
Checks the status of a single storage pool.
•svcinfo lsvdisk
Checks whether volumes are online and working correctly,
|
Locating issues: Although IBM Spectrum Virtualize raises error messages, most events are not caused by IBM Spectrum Virtualize. Most issues are introduced by the storage subsystems or the SAN.
|
If the problem is caused by IBM Spectrum Virtualize and you are unable to fix it by using the Recommended Action window or the event log, collect the IBM Spectrum Virtualize debug data as described in 10.2.1, “Data collection” on page 347.
To identify and fix other issues outside of IBM Spectrum Virtualize, consider the guidance in the other sections in this chapter that are not related to IBM Spectrum Virtualize.
10.3.3 Solving SAN issues
Some situations can cause issues in the SAN and on the SAN switches. Problems can be related to a hardware fault or to a software problem on the switch. The following hardware defects are normally the easiest problems to find:
•Switch power, fan, or cooling units
•Installed SFP modules
•Fiber-optic cables
Software failures are more difficult to analyze. In most cases, you must collect data and involve IBM Support. But before you take any other steps, check the installed code level for any known issues. Also, check whether a new code level is available that resolves the problem that you are experiencing.
The most common SAN issues often are related to zoning. For example, perhaps you chose the wrong WWPN for a host zone, such as when two IBM Spectrum Virtualize node ports must be zoned to one HBA with one port from each IBM Spectrum Virtualize node. However, as shown in Example 10-5, two ports are zoned that belong to the same node. Therefore, the result is that the host and its multipathing driver do not see all of the necessary paths.
Example 10-5 Incorrect WWPN zoning
zone: Senegal_Win2k3_itsosvccl1_iogrp0_Zone
50:05:07:68:01:20:37:dc
50:05:07:68:01:40:37:dc
20:00:00:e0:8b:89:cc:c2
The correct zoning must look like the zoning that is shown in Example 10-6.
Example 10-6 Correct WWPN zoning
zone: Senegal_Win2k3_itsosvccl1_iogrp0_Zone
50:05:07:68:01:40:37:e5
50:05:07:68:01:40:37:dc
20:00:00:e0:8b:89:cc:c2
The following IBM Spectrum Virtualize error codes are related to the SAN environment:
•Error 1060 Fibre Channel ports are not operational.
•Error 1220 A remote port is excluded.
If you cannot fix the issue with these actions, use the method that is described in 10.2.1, “Data collection” on page 347, collect the SAN switch debugging data, and then contact IBM Support for assistance.
10.3.4 Solving back-end storage issues
IBM Spectrum Virtualize has useful tools for finding and analyzing back-end storage subsystem issues because it has a monitoring and logging mechanism.
Typical events for storage subsystem controllers include incorrect configuration, which results in a 1625 error code. Other issues related to the storage subsystem include failures pointing to the managed disk I/O (error code 1310), disk media (error code 1320), and error recovery procedure (error code 1370).
However, all messages do not have only one explicit reason for being issued. Therefore, you must check multiple areas for issues, not just the storage subsystem. To determine the root cause of a problem, complete the following tasks:
1. Check the Recommended Actions window under IBM Spectrum Virtualize.
2. Check the attached storage subsystem for misconfigurations or failures.
3. Check the SAN for switch problems or zoning failures.
4. Collect all support data and involve IBM Support.
Complete the following steps:
1. Check the Recommended Actions panel by clicking Monitoring → Events → Recommended Actions, as shown in Figure 10-2 on page 350.
For more information about how to use the Recommended Actions panel, see the IBM System Storage IBM Spectrum Virtualize Information Center at:
2. Check the attached storage subsystem for misconfigurations or failures:
a. Independent of the type of storage subsystem, first check whether the system has any unfixed errors. Use the service or maintenance features that are provided with the storage subsystem to fix these issues.
b. Check whether the LUN masking is correct. When attached to IBM Spectrum Virtualize, ensure that the LUN masking maps to the active zone set on the switch. Create a similar LUN mask for each storage subsystem controller port that is zoned to IBM Spectrum Virtualize. Also, observe the IBM Spectrum Virtualize restrictions for back-end storage subsystems, which can be found at these websites:
• IBM Spectrum Virtualize
• Storwize V7000
If you need to identify which of the attached MDisks has which corresponding LUN ID, run the IBM Spectrum Virtualize svcinfo lsmdisk CLI command as shown in Example 10-7. This command also shows to which storage subsystem a specific MDisk belongs (the controller ID).
Example 10-7 Determining the ID for the MDisk
IBM_2145:itsosvccl1:admin>svcinfo lsmdisk
id name status mode mdisk_grp_id mdisk_grp_name capacity ctrl_LUN_# controller_name UID
0 mdisk0 online managed 0 MDG-1 600.0GB 0000000000000000 controller0 600a0b800017423300000059469cf84500000000000000000000000000000000
2 mdisk2 online managed 0 MDG-1 70.9GB 0000000000000002 controller0 600a0b800017443100000096469cf0e800000000000000000000000000000000
3. Collect all support data and contact IBM Support.
Collect the support data for the involved SAN, IBM Spectrum Virtualize, or storage systems as described in 10.2.1, “Data collection” on page 347.
Common error recovery steps by using the IBM Spectrum Virtualize CLI
For SAN issues or back-end storage issues, you can use the IBM Spectrum Virtualize CLI to perform common error recovery steps.
Although the maintenance procedures perform these steps, it is sometimes faster to run these commands directly through the CLI. Run these commands any time that you have the following issues:
•You experience a back-end storage issue (for example, error code 1370 or error code 1630).
•You performed maintenance on the back-end storage subsystems.
|
Important: Run these commands when back-end storage is configured or a zoning change occurs to ensure that IBM Spectrum Virtualize has recognized the changes.
|
Common error recovery involves the following IBM Spectrum Virtualize CLI commands:
•svctask detectmdisk
Discovers the changes in the back end.
•svcinfo lscontroller and svcinfo lsmdisk
Provides overall status of all controllers and MDisks.
•svcinfo lscontroller controllerid
Checks the controller that was causing the issue and verifies that all the WWPNs are listed as you expect.
•svcinfo lsmdisk
Determines whether all MDisks are now online.
•svcinfo lscontroller controllerid
Checks that the path_counts are distributed evenly across the WWPNs.
Finally, run the maintenance procedures on IBM Spectrum Virtualize to fix every error.
10.3.5 Replacing a failed disk
Always run directed maintenance procedures (dmp) to replace a failed disk. IBM Spectrum Virtualize has a policy that it never writes to a disk unless the disk is defined. When a disk is replaced, the system identifies it as a new disk. To use the new disk, it marks the old disk as unused and the new disk as spare.
10.4 Health status during upgrade and known errors
When the software upgrade completes and the node canister firmware upgrade starts during the software and firmware upgrade process, the Health Status goes from Red to Orange to Green in the GUI until the upgrade is complete. This is normal behavior and is not an alarm.
While trying to upgrade an IBM Spectrum Virtualize, you might get a message such as “The system is unable to install the update package. Error in verifying the signature of the update package.” as shown in Figure 10-5.
Figure 10-5 Error message during upgrade attempt
This message does not mean that you have an issue on the code package or in your system. In this case, open a PMR and follow the support instructions.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.