SSQRB8 - Documentation Index

Table of Contents

• Welcome
  • Accessibility
  • Notices
    • Privacy policy considerations
    • Trademarks
• What's new
  • Change history
    • Changes in older releases
    • Refined alert definitions for IBM Storage Insights Pro
    • Product name changes
    • Streamlined performance metrics in Q3 2022
  • Release notes
  • Sponsor user program
• Overview dashboard (Carbon)
  • FlashSystem grid
    • Storage Systems
    • Storage partitions
• Storage systems tabular
  • Security parameters window
  • Storage type filter tags
  • System and FlashSystem grid labels
  • Quick filters panel
  • Table toolbar
    • Add storage systems
    • Column chooser
  • Context menu
  • Capacity overview
  • Status pane
  • Storage system resources
• Individual device dashboard
• Insights
  • Performance
  • Reclamation
  • Capacity
• Resource overview page
  • Switches overview page
  • Fabrics overview page
  • Chassis overview page
  • Hosts overview page
  • Virtual machines overview page
  • Data collectors
  • Storage as a service
• Resource details page
  • Block storage system details page
    • Insights
    • Alerts
    • Security posture
    • Hardware
    • Logical
    • Host resources
    • Connectivity
    • Data protection
• Product overview
  • Tour the key features
    • Begin data collection
    • Ready, steady, go
    • Dashboard overviews
    • Integrated support experience
    • Optimized DS8000 Support
    • Cost savings
    • Capacity planning overview
    • Performance, capacity, and configuration troubleshooting
    • Reporting overview
  • Supported devices
  • IBM Storage Insights
    • Deploying data collectors to get capacity and performance insights and to upload logs
  • IBM Storage Insights free vs IBM Storage Insights Pro
    • Want to try or buy IBM Storage Insights Pro?
    • Open a case for IBM Spectrum Control license entitlement validation request
  • Determining the capacity to be licensed
    • Licensing examples
  • Social media
    • Videos
    • Blogs
  • Dashboards
    • Operations dashboard
      • Capacity overview charts and information
        • Capacity by pool
        • Capacity by volume
    • NOC dashboard
    • Notifications dashboard
    • Storage as a Service dashboard
    • Security posture dashboard
      • Security posture tenant dashboard
      • Security posture device dashboard
      • Security dashboard policies
      • Creating security posture reports
  • Navigation
    • Keyboard navigation
    • Tracking tasks
  • Units of measurement for storage data
  • Service updates and maintenance
  • IBM Storage Insights for IBM Spectrum Control
• Getting started
  • Before you begin checklist
  • Adding and removing users
    • Roles and access rights
  • Preparing to add devices for monitoring
    • Ports for collecting metadata from devices
    • User roles for collecting metadata
    • Downloading and installing data collectors
      • Installing data collectors on Windows
      • Installing data collectors on AIX or Linux
      • Adding, changing, or removing connections to proxy servers
        • Adding or changing the connection to the proxy server
        • Removing the connection to the proxy server
      • Learn more about installing and administering data collectors
      • Metadata collection with multiple data collectors
      • Enabling the collection of metadata for devices that use TLS 1.0 or 1.1
      • Disabling the collection of metadata for devices that use TLS 1.0 or 1.1
  • Monitoring resources with Call Home
    • Enabling Call Home with email notifications
    • Enabling Call Home with cloud services
    • Monitoring resources with Call Home Storage Systems dashboard
    • Migrating data collection method
    • Acknowledging Call Home events
    • Benefits of Call Home with cloud services
  • Data collector vs Call Home with cloud services
  • Adding storage systems
    • DS8000
      • Adding DS8000 storage systems that use SSLv3 and MD5 signed certificates
    • IBM Storage Ceph [Pro]
      • Planning for IBM Storage Ceph Systems
      • Adding IBM Storage Ceph systems
      • Uploading the new log package to the existing IBM Storage Ceph support ticket
    • IBM Storage FlashSystem family
    • SAN Volume Controller or IBM Storage Virtualize
      • Setting the device statistics collection interval
      • Planning for IBM Storage Virtualize for Public Cloud
        • Monitoring IBM Storage Virtualize for Public Cloud with on-premises data collection (Site to Site VPN IPsec)
        • Monitoring IBM Storage Virtualize for Public Cloud with off-premises data collection (in AWS and installed on the bastion host)
      • Probing a SAN Volume Controller cluster fails when the cluster ID changes
      • User roles for collecting performance metadata from IBM Storage Virtualize
    • Storwize family
    • Storwize V7000 Unified
      • How to fix IBM Storwize V7000 Unified authentication errors
    • IBM Storage Scale System
    • IBM Spectrum Scale [Pro]
      • Monitoring IBM Storage Scale with non-root user privileges
      • Verifying that probe data can be collected for object storage
      • Configuring the collection of performance data for IBM Storage Scale
      • Configuring OpenStack access to monitor the object storage system
    • Cloud Object Storage System [Pro]
    • Dell EMC [Pro]
      • Planning for Dell EMC storage systems
      • Planning for Dell EMC Solutions Enabler and Dell EMC SMI-S Provider
      • Adding multiple instances of SMI-S Provider or Solutions Enabler
    • Hitachi VSP [Pro]
      • Planning for Hitachi storage systems
      • Installing the Hitachi Export Tool
    • NetApp [Pro]
      • Planning for NetApp device support
      • Adding multiple instances of SMI-S providers
    • Pure Storage [Pro]
      • Planning for Pure Storage systems
  • Adding switches and fabrics
    • Planning for Brocade switches and fabrics
      • Configuring Brocade switches for monitoring
    • Adding Brocade switches and fabrics
    • Planning for Cisco switches and fabrics
    • Adding Cisco switches and fabrics
  • Adding hosts
    • Planning for hosts
    • Adding vCenter Servers
    • Managing unmonitored hosts
  • Removing resources
    • Removing hosts
    • Removing storage systems
      • Removing IBM Storage Ceph systems
    • Removing enclosures and nodes
    • Removing chassis, switches, and fabrics
  • Creating applications [Pro]
    • Application models
    • Creating an application hierarchy
      • Creating an application
      • Creating subcomponents for an application
    • Filters for associating storage resources with applications and subcomponents
  • Creating departments [Pro]
    • Department models
    • Creating a department hierarchy
      • Creating departments and adding applications to departments
      • Adding departments as subdepartments to departments
  • Creating general groups [Pro]
    • Creating a general group hierarchy
      • Creating general groups and adding resources
      • Adding general groups as subgroups
  • Viewing information about resources
    • Creating customized dashboards
    • Viewing capacity information
    • Viewing performance information for storage systems
    • Viewing performance information for fabrics
    • Viewing performance of hosts
    • Viewing performance of datastores
  • Audit logs
• Configuring
  • Managing data collectors
    • Assigning data collectors
    • Stopping and starting the data collector service
    • Removing and uninstalling data collectors
    • Upgrading data collectors
      • Upgrading data collectors automatically
      • Upgrading data collectors manually
      • Upgrading data collectors individually
      • Resolving upgrading issues
    • Resolving connection issues
    • Restoring your dashboard after a service update or interruption
    • Monitoring the status of data collectors
    • Renaming data collectors
    • Uploading the data collector's log packages
      • Uploading the data collector's log packages to ECuRep
      • Uploading the data collector's log packages to Blue Diamond
    • Connecting a data collector through an HTTPS Squid proxy
  • Granting IBM Support permission to collect log packages
  • Specifying which users are emailed about service outages
  • Including alerts in storage systems health determination
  • Checking the collection of metadata for devices
    • Administering the collection of metadata for devices
    • Stopping and restarting the collection of metadata for devices
    • Starting and stopping the collection of performance metadata for IBM Spectrum Scale
    • Enabling and disabling the collection of performance metadata for Hitachi VSP storage systems
    • Modifying the schedules for collecting metadata
    • Aggregation and retention periods for the metadata that is collected
  • Assigning pools to tiers
    • Renaming tiers
  • Modifying applications and departments [Pro]
    • Adding applications as subcomponents to applications
    • Adding subcomponents to applications
    • Adding storage resources to applications
    • Adding storage resources to subcomponents
    • Adding applications to departments
    • Adding applications to subdepartments
    • Removing applications
    • Removing subcomponents
    • Removing departments
    • Removing subdepartments
  • Changing the owner of IBM Storage Insights
  • Exporting information to a file
  • Customizing lists
    • Filtering lists
    • Filtering storage systems using pattern matching
    • Sorting lists
    • Showing, hiding, and reordering columns in lists
  • Modifying the properties of resources [Pro]
    • Properties of resources that can be modified
  • User Access Management
  • Settings
  • Integrating IBM Storage Insights with ecosystem
    • ServiceNow
    • Slack
    • IBM Storage Defender
    • Grafana
      • Grafana setup
      • Grafana dashboard
    • IBM Cloud Pak® for Security
    • Dynatrace
      • IBM Storage Insights Tenant overview dashboard
      • IBM Storage Insights Block Systems Entities
      • IBM Storage Insights Tenant performance dashboard
    • Chatbot
    • vSphere plugin
    • Jira
    • Prometheus
    • OpenTelemetry
    • IBM Cloud Pak for AIOps
    • Model Context Protocol (MCP) server
    • Multitenant dashboard
      • Using the dashboard
    • Microsoft Teams
• Gaining insights [Pro]
  • Viewing insight charts
  • Capacity planning
    • Capacity planning details
    • Forecast used capacity
    • Forecast written capacity
    • Forecast capacity
  • Performance views
    • Viewing the performance of storage systems
  • Reclamation views
    • Reclamation
    • Reclamation views of storage systems
  • Monitoring recommended actions in the Advisor
    • Acknowledging recommended actions
• Monitoring resources
  • Capacity views
    • Viewing capacity charts
    • Viewing dashboard capacity charts
    • Storage systems
      • Storage system details
      • Administering storage systems
      • Viewing charts and information about storage systems
      • Block storage systems
        • Overview charts
        • Setting capacity limits
          • Tutorial: Investigating compliance with the capacity limit
          • Removing the capacity limit
          • Capacity limit metrics
        • Block internal resources
          • Nodes, modules, and directors
          • Drives and disks
          • Enclosures
          • External disks
          • zHyperLink ports
          • FC ports
          • Host connections
          • I/O groups
          • IP ports
          • Managed disks, external volumes, and array LUNs
          • Pools, aggregates, and common provisioning groups
          • Host adapters
          • RAID arrays
          • Device adapters
          • Volumes
          • Volume groups
        • Block storage copy data resources
      • File storage systems
        • Capacity and capacity usage charts
        • Viewing the capacity of external storage
          • Identifying shortfall before data is recalled from external storage
        • File internal resources
          • Clusters and nodes
          • Declustered arrays
          • Disk controllers
          • Enclosures
          • Filesets
          • File systems and file provisioning groups
          • Network Shared Disks
          • Nodes
          • Pools
          • Quotas for IBM Spectrum Scale clusters
          • Recovery groups
          • Shares
          • Snapshots of GPFS file systems or filesets
      • Object storage systems
        • Capacity and failure tolerance charts
        • Object internal resources
          • Access Pools
          • Accesser Nodes
          • Mirrors
          • Sites
          • Slicestor Nodes
          • Storage Pools
          • Vaults
            • Calculating the failure tolerance for vaults
        • Object resources
          • Accounts
          • Containers
      • Unified Storage Systems
      • Storage system related resources
    • Applications
      • Administering applications
      • Application details
      • Application Related Resources
    • Departments
      • Administering departments
      • Viewing information and charts about departments
      • Department details
    • General groups
      • General group hierarchies
      • Adding resources to general groups
      • Viewing and administering general groups
      • General Group details
    • Hosts
      • Administering hosts
      • Host details
      • Host Internal Resources
      • Host related resources
      • Virtual Machine details
      • Virtual Machine Internal Resources
      • Virtual Machine related resources
      • Virtual Machine Resources
    • Tiers
    • Investigating capacity trends
      • Investigating capacity trends for block storage systems
      • Investigating capacity trends for file storage systems
      • Investigating capacity trends for object storage systems
      • Investigating capacity trends for block storage pools
      • Investigating capacity trends for volumes
      • Investigating capacity trends for file systems
      • Investigating capacity trends for file system pools
      • Investigating capacity trends for filesets
      • Investigating capacity trends for containers
      • Investigating capacity trends for tiers
      • Controls for capacity views
    • Capacity and space metrics
      • Capacity metrics for block storage systems
        • Capacity metrics for IBM Storage FlashSystem
        • Capacity metrics for DS8000 storage systems
        • Capacity metrics for IBM SAN Volume Controller storage systems
        • Capacity metrics for all other block storage systems
      • Capacity metrics for file storage systems
      • Capacity metrics for object storage systems
      • Capacity metrics for tiers
      • Capacity metrics for hosts
      • Capacity metrics for virtual machines
  • Performance views
    • Investigating the performance of storage resources
      • Investigating the performance of storage systems
      • Tutorial: Comparing the performance of storage systems
      • Investigating the performance of a storage system
      • Investigating the performance of applications
      • Investigating the performance of application subcomponents
      • Investigating the performance of applications and subcomponents added to departments
      • Investigating the performance of applications and subcomponents added to subdepartments
      • Investigating the performance of hosts
      • Identifying performance issues for IBM Storage Virtualize storage systems
      • Tutorial: Identifying the source of slow drain problems caused by depletion of buffer credits
    • Controls for performance views
    • Performance metrics
      • Performance metrics for Dell EMC storage systems
      • Performance metrics for IBM FlashSystem 900
      • Performance metrics for Hitachi VSP storage systems
      • Performance metrics for NetApp storage systems
      • Performance metrics for Pure storage systems
      • Performance metrics for IBM Spectrum Scale
      • Performance metrics for DS8000
      • Performance metrics for resources that run IBM Storage Virtualize
      • Performance metrics for hosts
      • Performance metrics for virtual machines
    • Exporting and uploading performance data for storage systems
      • Tutorial: Exporting and uploading performance data for a SAN Volume Controller system
    • IBM Storage Virtualize guideline values for key performance indicators
    • Tutorial: Viewing the aggregated workload for an application
  • Monitoring switches and fabrics through chassis
    • Switches
      • Switch details
      • Switch Internal Resources
      • Switch Related Resources
      • Performance metrics for switches
      • Chassis
      • Chassis details
      • Chassis Internal Resources
      • Chassis Related Resources
      • Tutorial: Creating an inventory report for switches
      • Tutorial: Creating an inventory report for switch ports
      • Tutorial: Creating an inventory report for chassis
    • Fabrics
      • Fabric details
      • Fabric Internal Resources
      • Fabric Related Resources
      • Tutorial: Creating a report about fabrics
  • Monitoring Storage as a Service [Pro]
    • Viewing Storage as a Service
    • Editing the name of Storage as a Service
    • Viewing capacity usage charts and other information
    • Viewing and administering alerts
    • Adding storage
    • Creating reports
  • Monitoring the status and condition of resources
    • How the condition of a resource is determined
    • Viewing the condition of specific types of resources
    • Viewing the status of resources
    • Acknowledging the condition of top-level resources
    • Acknowledging the status of internal resources
  • Monitoring the status of data collection
  • Opening the management GUI for the storage system
    • Opening the management GUI for DS8000 storage systems
  • Opening, updating, and tracking IBM Support tickets
    • Call Home and IBM Support tickets
    • Information that you add to tickets
  • Identifying the locations of devices
  • Tracking maintenance contracts for storage systems
  • Creating a webhook in IBM Storage Insights
  • Receiving webhook deliveries
  • Integrating IBM Storage Insights with IBM Storage Defender
  • Integrating IBM Storage Insights with ServiceNow
    • Creating a REST API endpoint in ServiceNow
    • Creating a webhook for ServiceNow
  • Integrating IBM Storage Insights with Slack
    • Creating a Slack application and a private Slack channel
    • Creating a webhook for Slack
  • Monitoring integrations in IBM Storage Insights
  • Monitoring environment metrics in IBM Storage Insights
  • Evaluating workload placement advice
• Monitoring notifications
  • Acknowledging notifications
  • Creating notification reports
• Alerting [Pro]
  • How alerts work
  • Viewing and administering alerts
  • Viewing and administering alert definitions
  • Alert policies
    • Viewing alert policies
    • Creating alert policies
    • Configuring IBM Cloud Pak® for Security for real-time ransomware threat alerts
    • Modifying alert policies
      • Modifying which resources are managed by an alert policy
      • Adding a resource for management by an alert policy
      • Removing resources from alert policies
    • Deleting alert policies
  • Alerts for ransomware threat detection
    • Enabling and disabling alerts for ransomware threat detection
    • Monitoring alerts for ransomware threat detection
    • Acknowledging a false positive alert
    • Submitting feedback for ransomware false positives
  • Alerts for workload anomaly detection
    • Monitoring alerts for workload anomaly detection
    • Acknowledging a false positive alert
    • Submitting feedback for workload anomaly false positives
  • Defining alerts for attributes, capacity, and performance changes
    • Defining alert definitions for general attributes and capacity changes
    • Defining alert definitions for environmental metrics changes
    • Defining alert definitions for performance changes
  • Defining custom alerts for resources
    • Scenarios for custom alerts
  • Defining alerts for applications
    • Defining application alerts for attribute and capacity changes
    • Defining application alerts for performance metrics
    • Defining custom alerts for applications
  • Defining alerts for general groups
    • Defining general group alerts for attribute and capacity changes
    • Defining general group alerts for performance metrics
    • Defining custom alerts for general groups
  • Defining notification settings for alerts
    • Alert notifications
  • Triggering conditions for alerts
    • Triggering conditions for storage system alerts
      • Triggering conditions for storage system internal resource alerts
    • Triggering conditions for storage partition alerts
    • Triggering conditions for server alerts
    • Triggering conditions for host alerts
    • Triggering conditions for unmonitored host alerts
    • Triggering conditions for virtual machine alerts
    • Triggering conditions for switch alerts
    • Triggering conditions for fabric alerts
    • Triggering conditions for chassis alerts
• Reporting
  • Creating predefined capacity reports
    • Tutorial: Creating a predefined capacity report about storage systems
    • Tutorial: Creating a predefined capacity report about pools
    • Tutorial: Creating a predefined capacity report about tiered pools
    • Tutorial: Creating a predefined capacity report about the volumes assigned to hosts
    • Tutorial: Creating a predefined capacity report about managed disks by storage systems
    • Adding resources to applications to generate large reports
  • Creating predefined inventory reports
    • Tutorial: Creating an inventory report about block storage systems
  • Creating custom reports
    • Tutorials: Creating custom capacity and performance reports for applications
      • Creating the application for the capacity report
      • Creating the capacity report for the application
      • Creating the performance report for the application
    • Custom capacity and performance view reports
  • Creating chargeback and consumer reports
    • Creating chargeback reports
      • Chargeback reports
    • Creating consumer reports
      • Consumer reports
    • Creating summary reports of the storage capacity
    • Capacity metrics for chargeback and consumer reports
  • Creating capacity planning reports
  • Creating Storage as a Service capacity report
  • Creating Storage as a service capacity report legacy
  • Creating storage system maintenance information report
  • Creating storage systems report belonging to a FlashSystem grid
  • Creating storage partition report belonging to a FlashSystem grid
  • Running reports
  • Editing reports
  • Deleting reports
  • Types of predefined capacity and inventory reports
  • Reports FAQ
• Security
  • Security overview
  • What security measures are built in
  • Data Collection Methods
  • What is Call Home
  • What is the data collector
  • How is the metadata protected
  • What types of metadata are collected
  • How long is the metadata kept
  • Who can access the metadata
    • Metadata access controls and authorization
    • Metadata access for resolving issues
    • IBM Support access for troubleshooting your tickets
    • Metadata access for quality improvements
    • Data backup and restore
    • Requesting the deletion of personal information
  • Asset, capacity, and configuration metadata
    • Block storage system metadata
    • Block volumes metadata
    • Block pools metadata
    • I/O groups, nodes, and ports metadata
    • Disks and managed disks metadata
    • Enclosures metadata
    • File storage system metadata
    • File system metadata
    • Fileset metadata
    • File shares metadata
    • File system pools metadata
    • Network shared disks metadata
    • File nodes metadata
    • Object storage systems metadata
    • Switches metadata
    • Fabrics metadata
    • Groups metadata
    • Hosts metadata
  • Performance metadata
    • Performance metadata for storage systems that run IBM Storage Virtualize
    • Performance metadata for DS8000
    • Performance metadata for IBM Spectrum Scale
    • Performance metadata for Dell EMC Unity, VMAX, and VNX
    • Performance metadata for Hitachi VSP storage systems
    • Performance metadata for NetApp storage systems
    • Performance metadata for Pure Storage systems
    • Performance metadata for switches
• Frequently Asked Questions (FAQ)
• Troubleshooting
  • Troubleshooting data collectors
  • Troubleshooting switches and chassis
  • Getting support
    • Subscribing to IBM announcements
    • Collaborating with the team
  • Troubleshooting dynatrace extension
• Support
  • Creating a ticket
  • Updating a ticket
  • Viewing a ticket
  • Uploading logs
• Messages
  • Introduction to messages
  • Message types
    • Call Home Messages
      • The power supply failed
      • A fan is operating outside the expected range
      • The fan status in unknown due to a communication error
      • The power supply has a direct current (DC) failure
      • The serial-attached SCSI (SAS) drive has error counts that exceed the warning thresholds
      • A storage pool is offline
    • BPCCA - Data collector installation messages
      • BPCCA0001I The data collector started, connected to the service_name, and is ready to process requests from the service_name.
      • BPCCA0002E The data collector failed to connect or register to the service_name at server_url.
      • BPCCA0003E The data collector started but detected a problem with the directory directory_name and must stop.
      • BPCCA0004E The data collector cannot run because it is not configured correctly.
      • BPCCA0005E The data collector failed to connect to the storage management service at server_url because the host name could not be resolved.
      • BPCCA0006E The data collector failed to connect to the storage management service at server_url because of an unknown error.
      • BPCCA0007E The data collector failed to connect to a service from the storage management system.
      • BPCCA0008E The data collector failed to connect to the storage management service because of invalid credentials.
      • BPCCA0009I The data collector connected to the storage management service. The data collector had failed to connect since date_and_time.
      • BPCCA0010E The data collector in the directory_name directory of the host host_name was running and an attempt was made to start a second instance of the same data collector. The second instance of the data collector stopped.
      • BPCCA0011I The data collector stopped because a user requested it to shut down.
      • BPCCA0012I The data collector stopped to enable the installation of an upgraded version of the data collector.
      • BPCCA0013E The storage management service did not allow the data collector to connect because another data collector was already connected to the service.
      • BPCCA0100I The updateCollector utility started.
      • BPCCA0101E The collector directory was not specified in the collectorDirectory.properties file.
      • BPCCA0102E The collector directory directory_name that was specified in the collectorDirectory.properties file is invalid. The collector directory is the directory to which the updateCollector utility must copy the upgrade image files.
      • BPCCA0103E The collector directory directory_name that was specified in the collectorDirectory.properties file cannot be used as the collector directory.
      • BPCCA0104E The updateCollector utility started but there was a problem with the upgrade image directory current_directory.
      • BPCCA0105E The collector directory directory_name that was specified in the collectorDirectory.properties file is a subdirectory of the upgrade image directory upgrade_image_directory_name.
      • BPCCA0106E Cannot upgrade the data collector in the collector_directory directory because the directory contains the following locked files: locked_files_list
      • BPCCA0107I The content of the directory collector_directory will be deleted and replaced with subdirectories and files from the upgrade_image_directory directory. Some configuration files, the log directory, and the contents of the log directory will not be deleted.
      • BPCCA0108E The data collector service cannot be uninstalled from the operating system. The upgrade process cannot be completed.
      • BPCCA0109E The updateCollector utility could not upgrade the data collector. The data collector service is now in an inconsistent state.
      • BPCCA0110E The contents of the collector_directory directory could not be deleted. The upgrade process cannot be completed. The data collector might be in an inconsistent state.
      • BPCCA0111E The files and directories of the data collector from the directory upgrade_image_directory could not be copied into the directory collector_directory. The upgrade process cannot be continued. The data collector might be in an inconsistent state.
      • BPCCA0112I The data collector in the directory collector_directory was upgraded successfully to version downloaded_version.
      • BPCCA0113E The data collector in the directory collector_directory could not be upgraded.
      • BPCCA0114I The data collector was upgraded to the new version and will start automatically.
      • BPCCA0115I The attempt to upgrade the data collector failed. The existing data collector will start automatically.
      • BPCCA0116E The attempt to upgrade the data collector failed. You must download and install the latest version of the data collector.
      • BPCCA0117E The upgraded data collector could not be installed as a service on the operating system. You must install the new data collector service manually.
      • BPCCA0118I The data collector was upgraded to the new version and started successfully.
      • BPCCA0119I The data collector could not be upgraded, but was not modified. The existing data collector was restarted successfully.
      • BPCCA0120E The upgraded data collector did not start.
      • BPCCA0121E The existing data collector did not restart.
      • BPCCA0122E The data collector cannot authenticate to the HTTPS proxy server proxy_server_hostname. Therefore, the data collector cannot connect to the storage management service.
    • BPCDP - Data processor messages
      • BPCDP0000I Performance data for natural key resource at date and time timestamp was collected and processed successfully.
      • BPCDP0001E Error while collecting and processing performance data for natural key resource at date and time timestamp. Performance data was not collected and processed.
      • BPCDP0002E The processing of performance data for the resource could not be completed.
      • BPCDP0003E No performance data is available at the current time for this resource.
      • BPCDP0004I Performance data was retrieved and persisted but aggregation of data to higher-level components didn’t complete because the relationship to the higher-level components couldn’t be determined.
      • BPCDP0005E Could not save the performance data that was collected from the resource.
      • BPCDP0006I Performance data at date and time timestamp was processed and saved successfully for the resource.
      • BPCDP0007E The resource is missing. The resource is required.
      • BPCDP0008E Identifying information for the resource is missing. This information is required.
      • BPCDP0009E Information identifying the resource type is invalid: system type .
      • BPCDP0010E Information uniquely identifying the resource is missing. This information is required.
      • BPCDP0011E Information uniquely identifying the resource is invalid.
      • BPCDP0012E The UUID for the tenant's resource is invalid.
      • BPCDP0013E The start time for the performance data is invalid: start time
      • BPCDP0014E The end time for the performance data is invalid: end time
      • BPCDP0015I Performance data at date and time timestamp was processed and saved successfully for the resource, but the data processing raised warnings.
      • BPCDP0016W Performance data for natural key resource at date and time timestamp was collected and processed successfully, but the data processing raised warnings.
    • BPCPD - Probe data processor messages
      • BPCPD0001E Information identifying the resource type is invalid: system type .
      • BPCPD0002E Information uniquely identifying the resource is missing. This information is required.
    • BPCSS - Scheduler messages
      • BPCSS0000E An error occurred while collecting performance data from the device. The collection is being attempted by a different collector.
      • BPCSS0001W The data collection is taking longer than expected.
      • BPCSS0002E Currently, there is no data collector available for this device.
      • BPCSS0005I Performance monitor is starting at an interval of interval interval units. This action was requested by user name.
      • BPCSS0008I Collection can no longer continue due to invalid credentials. Use the 'Modify Connection' dialog to fix the storage system credentials and resume collection.
      • BPCSS0009E Failed to save the performance monitor schedule.
      • BPCSS0010E A job cannot be run for resource resourceName because there is a job already running for the resource.
      • BPCSS0011W The schedule change was saved but the update to the active collection did not happen.
      • BPCSS0012I Performance monitor is stopped. This action was requested by user name.
      • BPCSS0013I Performance monitor is stopped.
      • BPCSS0014I Performance monitor is starting at an interval of interval interval units.
      • BPCSS0015I Performance monitor collection interval was updated to interval interval units. This action was requested by user name.
      • BPCSS0016I Performance monitor collection interval was updated to interval interval units.
      • BPCSS0017I Performance monitor is enabled. This action was requested by user name.
      • BPCSS0018I Performance monitor is enabled.
      • BPCSS0019I Performance monitor is disabled. This action was requested by user name.
      • BPCSS0020I Performance monitor is disabled.
      • BPCSS0021W Performance monitor is starting. The initial attempt to start collection failed so it is retried. This action was requested by user name.
      • BPCSS0022W Performance monitor is starting. The initial attempt to start collection failed so it is retried.
      • BPCSS0023I Performance monitor collection interval is enabled and updated to interval interval units. This action was requested by user name.
      • BPCSS0024I Performance monitor collection interval is enabled and updated to interval interval units.
      • BPCSS0025E Access to the agent or device is denied. Ensure that valid credentials are specified for agent agent name.
      • BPCSS0026E New performance data is not yet available for the device. Statistics with time stamps later than time stamp could not be found.
      • BPCSS0027E The performance monitor failed due to an internal error.
      • BPCSS0028E The value that is specified as parameter (value) is invalid.
      • BPCSS0029E Cannot connect to the device with the address IP address.
      • BPCSS0030E Cannot connect to the SNMP data source IP address.
      • BPCSS0031E Cannot authenticate with the provided user credentials.
      • BPCSS0032E Passphrase is incorrect for subsystem param1.
      • BPCSS0033E Passphrase is required. Specify one for subsystem param1.
      • BPCSS0034E Verify that they private key that was provided for subsystem param1 was in the OpenSSH file format. If it is in another format, it needs to be converted before it can be used.
      • BPCSS0035E The user does not have the required authority to complete the task or command.
      • BPCSS0036E Cannot connect to the storage system or cluster.
      • BPCSS0037W The device cannot be reached.
      • BPCSS0038E The device or device agent did not respond within the allotted time.
      • BPCSS0039E The host name or IP address {0} is not valid.
      • BPCSS0040E The host name or IP address is not valid.
      • BPCSS0041E Cannot connect to the device.
      • BPCSS0042E Cannot connect to the SNMP data source.
      • BPCSS0043E Passphrase is incorrect.
      • BPCSS0044E Passphrase is required.
      • BPCSS0045E Access to the device is denied. Ensure that valid credentials are specified.
      • BPCSS0046E Verify that they private key that was provided was in the OpenSSH file format. If it is in another format, it needs to be converted before it can be used.
      • BPCSS0047E New performance data is not yet available for the device.
      • BPCSS0048E The parameter for the Performance Manager API is invalid.
      • BPCSS0049E Schedule is not enabled for the resource resource.
      • BPCSS0050W Performance data could not be collected for device device name because the device or data source cannot be reached (reason reason code). The current samples are skipped.
      • BPCSS0051E The device or device agent did not respond within the allotted time (timeout valueseconds).
      • BPCSS0052W Performance data continuity is broken. The device might have been reset or rebooted. record count performance data records were discarded.
      • BPCSS0053W No valid performance data was provided by the monitored resource. Zero performance data records were inserted into the database.
      • BPCSS0054E A timeout occurred while polling the performance statistics for this device: device name
      • BPCSS0055E Performance data was not collected for device device name due to error error trace. The current samples are skipped.
      • BPCSS0056E The last performance Data Collection was not readable for device device name, the collection failed with error error trace.
      • BPCSS0057E Cannot connect to the switch with the provided IP address, host name, protocol, and port.
      • BPCSS0058E Cannot authenticate to the switch with the provided user name and password.
      • BPCSS0059E The specified user name does not have the required permissions for the switch.
      • BPCSS0060E Performance monitoring is unavailable for resource resource_name because the ZiMon agent is not available.
      • BPCSS0061W Out of request count requests, only processed request count were successfully started.
      • BPCSS0062W The data collector monitoring system system is missing. Will attempt to switch to a new data collector.
      • BPCSS0063W Configuration data is already being collected for system system. A new collection can not be started till the current one finished.
      • BPCSS0064E The request encountered an internal error and could not be completed. Please try again.
      • BPCSS0065E The Data Collector Manager could not retrieve system actions for all devices being monitored by collector collector.
      • BPCSS0066E The firmware level on the switch is not supported.
      • BPCSS0067E The firmware level of the switch cannot be parsed.
      • BPCSS0068E The show hardware command failed.
      • BPCSS0069E The issued command is not supported by the device. The action can’t be completed.
      • BPCSS0070E The device is returning invalid data.
      • BPCSS0071E The incorrect family type was selected for the storage system.
      • BPCSS0105I Probe is starting at an interval of interval interval units. This action was requested by user name.
      • BPCSS0109E Can't save the schedule for the probe.
      • BPCSS0110E The download of Data Collector installer package failed.
      • BPCSS0111E The extraction of Data Collector installer package failed.
      • BPCSS0112I The probe was stopped. This action was requested by user name.
      • BPCSS0113I The probe is stopped.
      • BPCSS0114I The probe is starting at an interval of interval interval units.
      • BPCSS0115I The probe interval was updated to interval. This change was requested by user name.
      • BPCSS0116I The probe interval was updated to interval.
      • BPCSS0117I The probe is enabled. This action was requested by user name.
      • BPCSS0118I The probe is enabled.
      • BPCSS0119I The probe is disabled. This action was requested by user name.
      • BPCSS0120I The probe is disabled.
      • BPCSS0121W The probe started, but the initial attempt to collect metadata failed. This action was requested by user name.
      • BPCSS0122W The probe started, but the initial attempt to collect metadata failed.
      • BPCSS0123I The Probe collection interval is enabled and updated to interval. This action was requested by user name.
      • BPCSS0124I Probe interval is enabled and updated to interval.
      • BPCSS0125E The Data Collector upgrade operation failed with invalid parameters.
      • BPCSS0126E The Data Collector upgrade operation failed due to locked files detection.
      • BPCSS0127E The Data Collector upgrade operation failed during the uninstallation process of the existing Data Collector.
      • BPCSS0128E The Data Collector upgrade operation failed while trying to delete old files.
      • BPCSS0129E The Data Collector upgrade operation failed while trying to copy new files.
      • BPCSS0130E The upgrade operation failed to install the new Data Collector for unknown reasons.
      • BPCSS0131E The Data Collector upgrade failed.
      • BPCSS0132E The data collector was not upgraded because there wasn’t enough space in the installation directory.
      • BPCSS0133E The data collector was not upgraded because the path to the compressed installation file is not valid.
      • BPCSS0134E The data collector was not upgraded because the upgrade process does not have the required permissions on the installation directory.
      • BPCSS0135E The data collector was not upgraded because the compressed file that contains the installation files could not be located.
      • BPCSS0136E The data collector wasn’t upgraded because there wasn’t enough space in the installation directory.
      • BPCSS0137E The data collector wasn’t upgraded because the download of the data collector upgrade package took too long to complete. The default time in which the download should complete is 60 minutes.
      • BPCSS0138E The data collector wasn’t upgraded because the extraction of the data collector upgrade package took too long to complete. The default time in which the extraction should complete is 10 minutes.
      • BPCSS2000I Cannot connect to the device as the user account is locked.
      • BPCSS2001I Cannot connect to the device.
      • BPCSS2002I The download of installer package that runs Data Collector upgrade operation is completed.
      • BPCSS2003I The extraction of Data Collector installer package is completed.
      • BPCSS2022I The data collector installer package is being downloaded.
      • BPCSS2023I The data collector installer package is being extracted.
      • BPCSS2024I Old data collector files are being replaced with new files from the data collector download package.
      • BPCSS2025I Performance data is being uploaded.
      • BPCSS2004W Performance data was not received for the device within the expected time. The current sample is skipped.
      • BPCSS2005E Task timed out because it did not complete in the expected time.
      • BPCSS2006I System discovery data is being processed for system natural key.
      • BPCSS2007I Running task task type for system system natural key.
      • BPCSS2008I Running task task type for data collector collector.
      • BPCSS2009E A policy group with the same name already exists.
      • BPCSS2010I Opened ticket ticket number and started collecting logs from the device with serial number device serial number.
      • BPCSS2011I Collecting logs from device with serial number device serial number for ticket ticket number.
      • BPCSS2012I The log package for device with serial number device serial number was collected for ticket ticket number.
      • BPCSS2013E Opened ticket ticket number, but logs were not collected from the device with serial number device serial number.
      • BPCSS2014E Opened ticket ticket number, but log collection from the device with serial number device serial number timed out.
      • BPCSS2015I The logs for device with serial number device serial number are being uploaded for ticket ticket number.
      • BPCSS2016I The logs for device with serial number device serial number have been uploaded for ticket ticket number.
      • BPCSS2017E Upload of the logs for device with serial number device serial number for ticket ticket number failed.
      • BPCSS2018E Upload of the logs for device with serial number device serial number for ticket ticket number timed out.
      • BPCSS2019E The Ticket Service Upload of the logs for device with serial number device serial number for ticket ticket number failed.
      • BPCSS2020W An upgrade is already in progress for system system . A new upgrade can not be started till the current one finishes.
      • BPCSS2021E The upgrade process of all data collectors stopped. Go to the Data Collectors page to upgrade manually.
      • BPCSS2026I Started collecting logs from device with serial number device serial number for ticket ticket number.
      • BPCSS2027E Logs were not collected from the device with serial number device serial number for ticket ticket number.
      • BPCSS2028E Opened ticket ticket number, but logs were not collected from device with serial number device serial number, because the device firmware version device version is lower than the minimum supported version 7.7.52.19.
      • BPCSS2029E Logs were not collected from device with serial number device serial number for ticket ticket number, because the device firmware version device version is lower than the minimum supported version 7.7.52.19.
      • BPCSS2030E The ticket ID id is valid but the upload of the export file that contains the performance data failed.
      • BPCSS2031E The ticket ID id provided to upload the export performance data is not open or is invalid.
      • BPCSS2032E Opened ticket ticket number, but the log package for the device with serial number device serial number was not created, because the CLI Command issued for the storage system failed.
      • BPCSS2033E The log package for the device with serial number device serial number for ticket ticket number was not created, because the CLI Command issued for the storage system failed.
      • BPCSS2034E Opened ticket ticket number, but the log package for the device with serial number device serial number was not created, because another logs collection task is already running.
      • BPCSS2035E The log package for the device with serial number device serial number for ticket ticket number was not created, because another logs collection task is already running.
      • BPCSS2036E Opened case case number for the device with serial number device serial number, but the log package was not created. The connection to the device failed.
      • BPCSS2037E The log package for the device with serial number device serial number for case case number was not created. The connection to the device failed.
      • BPCSS2038E Opened case case number, but the log package for the device with serial number device serial number was not created, because of an internal error.
      • BPCSS2039E The log package for the device with serial number device serial number for case case number was not created, because of an internal error.
      • BPCSS2044E The support case was not opened for the device with serial number device serial number. The license agreement for the device might be expired.
      • BPCSS2045E The support case was not opened for the device with serial number device serial number because of Electronic Customer Care (ECC) error ECC error description.
      • BPCSS2046E The SNMP agent did not respond within the allotted time.
      • BPCSS2047E Cannot connect to the device.
      • BPCSS2048E Performance metadata cannot be collected.
      • BPCSS2049E The operation can't be completed because the Hitachi VSP Model is not known. A Hitachi Export Tool to match it cannot be found.
      • BPCSS2050E Performance metadata can't be collected at the configured sample interval.
      • BPCSS2051E Cannot log in to the Hitachi Export Tool to collect performance metadata.
      • BPCSS2052E Encrypted SSH keys in PuTTY Private Key format are not supported
      • BPCSS2053E The selected log package can't be uploaded.
      • BPCSS2054E The device can't be added because older TLS protocols are disabled.
      • BPCSS2055E The specified user name is new account whose password must be changed prior to use.
      • BPCSS2056E The specified user account has an expired password.
      • BPCSS2057E Cannot connect to the Call Home service for the storage system.
      • BPCSS2058E Cannot collect metadata about the storage system.
      • BPCSS2059E Cannot connect to cloud services.
      • BPCSS2060E The log package was not created for the device with serial number device serial number for ticket ticket number.
      • BPCSS2061E Cannot connect to the Call Home service for the storage system.
      • BPCSS2062E Cannot connect to the Call Home service for the storage system.
      • BPCSS2063E Ticket creation for the device with serial number device serial number is not supported.
      • BPCSS2064E Cannot add the Call Home storage system.
      • BPCSS2065E Cannot update the Call Home storage system.
      • BPCSS2066E Cannot delete the Call Home storage system.
      • BPCSS2067E The security token cannot be renewed for the data collector.
      • BPCSS2068E Metadata cannot be collected about the device.
      • BPCSS2069E Metadata collection was not changed to Call Home with cloud services.
      • BPCSS0072E Cannot authenticate with the provided administrator user credentials.
      • BPCSS0073E Cannot authenticate with the provided analyzer user credentials.
      • BPCSS2074E Analyzer credentials are not available to enable performance for Hitachi Ops Center.
      • BPCSS2077W No response received for log file offload from DS8000 device.
    • BPCUI - User Interface messages
      • BPCUI0000E The action can't be completed because the following error occurred: Error message text.
      • BPCUI0001E An action could not be completed and the following error message was generated: TPCRemoteException message
      • BPCUI0002E Failed to retrieve the requested data because the service is unavailable.
      • BPCUI0003E The NAPI with the IP address Napi IP was not added because of an Internal Error
      • BPCUI0004E The SSH private key for the NAPI Napi IP could not be uploaded
      • BPCUI0005E The action cannot be completed because the following internal error has occurred: message.
      • BPCUI0007E The discovery job failed to complete.
      • BPCUI0009E The SSH key could not be loaded for the following reason:IOException message
      • BPCUI0010E The host name or IP address that you entered is a resource_type, but you selected to add a different type of storage system.
      • BPCUI0011E The Device Server did not discover any device
      • BPCUI0012E Cannot connect to the device with the address Ip Address.
      • BPCUI0019E No data is available for this selection.
      • BPCUI0025E Probe job job Id failed.
      • BPCUI0029E Invalid parameter param passed.
      • BPCUI0030I This task was already executed.
      • BPCUI0032E An unexpected response was received from the server.
      • BPCUI0034E Invalid number of runs to keep for each schedule. The number should be between param1 and param2.
      • BPCUI0035E Invalid number of days' worth of log-files to keep. The number should be between param1 and param2.
      • BPCUI0036E The schedule id scheduleID associated with this job is no longer valid. It might have been deleted. Refresh the view and try again.
      • BPCUI0037E The replication server is not installed or is unavailable.
      • BPCUI0038E Invalid number of days to retain alerts. The number should be between param1 and param2.
      • BPCUI0040E Parsing results from a call to the Data server failed with the following error message: param1.
      • BPCUI0042E Communication with the Data Server failed with the following error: param1
      • BPCUI0043E Cannot connect to the Data server.
      • BPCUI0044E The entity was not found in the database.
      • BPCUI0045E Host name length exceeds the 255 character limit
      • BPCUI0046E Report 'configurationId' not found
      • BPCUI0047E Parameter 'parameterName' is not defined in report configurationId'
      • BPCUI0048E No property is not defined for report configurationId'
      • BPCUI0049E No such property propertyName for report configurationId'
      • BPCUI0050E variableName can not be overridden
      • BPCUI0051E variableName not valid report output format.
      • BPCUI0052E variableName not reachable
      • BPCUI0053E Cannot authenticate with the provided user credentials.
      • BPCUI0054E The host name or IP address {0} is not valid.
      • BPCUI0055E Cannot connect to the storage system.
      • BPCUI0056E Cannot connect to the storage system or cluster.
      • BPCUI0058I No supported resources were discovered on the data source data_Source_Address.
      • BPCUI0060I File param was successfully uploaded to the Data Server.
      • BPCUI0061E Upload file type param is not supported.
      • BPCUI0062E The requested action failed with the following error message: error message
      • BPCUI0063E Cannot find jobs for scheduleId param and deviceId param. No logs are displayed.
      • BPCUI0064E A log file cannot be displayed for the job.
      • BPCUI0065E The job log file cannot be accessed. The log file may have been manually removed or may have been deleted because it was older than retain_days days or it exceeded the maximum number of no_of_lofs runs.
      • BPCUI0067E The schedule for collecting status and asset data cannot be created.
      • BPCUI0068E A proposed schedule for collecting status and asset data cannot be created.
      • BPCUI0069E The proposed schedule for collecting status and asset data cannot be deleted.
      • BPCUI0071E The task task_name could not be completed.
      • BPCUI0072E Cannot connect to the Device server. Verify that the database service and Device server are running, and that the Device server is accessible.
      • BPCUI0073E Can't make a connection to the storage_resource storage resource.
      • BPCUI0074E The wizard could not set an attribute for the storage resource.
      • BPCUI0075E The certificate wasn't saved on the server.
      • BPCUI0076W The initial job to collect status and asset data did not start.
      • BPCUI0077E A failure occurred loading the certificate.
      • BPCUI0078I The certificate was loaded successfully.
      • BPCUI0079E The SSL certificate is not in the expected format.
      • BPCUI0084W The wizard could not retrieve the default interval information for performance monitoring.
      • BPCUI0085E The user name or password for the hypervisor or vCenter hypervisor or vCenter Server is invalid.
      • BPCUI0086E The SSL certificate is invalid for the hypervisor or vCenter hypervisor or vCenter Server, or the firewall is blocking access to it.
      • BPCUI0087E The version of the hypervisor or vCenter hypervisor or vCenter Server is not supported.
      • BPCUI0088E The host name, protocol, or port for the hypervisor or vCenter hypervisor or vCenter Server is invalid, or the hypervisor or vCenter Server is unreachable.
      • BPCUI0089W Cannot retrieve a valid set of data collection intervals for performance monitoring.
      • BPCUI0090I All alerts were removed.
      • BPCUI0091W error_count of total_count alerts were not removed.
      • BPCUI0093I No data path is available for deviceNameVariable.
      • BPCUI0094E Authorization failed due to an internal error.
      • BPCUI0097E Authorization failed due to an invalid request context.
      • BPCUI0098E The current user is not authorized to perform the requested function.
      • BPCUI0099E Information about the storage resource is not available.
      • BPCUI0100I success_count alerts were marked as acknowledged.
      • BPCUI0101I The alert was marked as acknowledged.
      • BPCUI0102E None of the alerts were marked as acknowledged.
      • BPCUI0104I success_count alerts were marked as unacknowledged.
      • BPCUI0105I The alert was marked as unacknowledged.
      • BPCUI0108I All informational alerts were marked as acknowledged.
      • BPCUI0110W Some informational alerts were not marked as acknowledged.
      • BPCUI0111I All alerts were marked as acknowledged.
      • BPCUI0112I success_count alerts were removed.
      • BPCUI0113I The alert was removed.
      • BPCUI0114I All acknowledged alerts were removed.
      • BPCUI0116W Some acknowledged alerts were not removed.
      • BPCUI0120W Some acknowledged alerts were not marked as unacknowledged.
      • BPCUI0121E Unable to communicate with the product server. Make sure that the server is running properly.
      • BPCUI0122E No job log file was created for this job run.
      • BPCUI0123E The action cannot be completed.
      • BPCUI0124E An unexpected error occurred during the execution of the action.
      • BPCUI0125E The alert is not available.
      • BPCUI0126E The status of the Performance Monitors could not be retrieved.
      • BPCUI0127E The currently installed version of the product does not have the required product license for the function that you requested.
      • BPCUI0128E An undefined capacity chart metric was requested.
      • BPCUI0129I Alerts that were migrated from a previous version of the product are not shown on this page.
      • BPCUI0130E The alerts cannot be acknowledged because they were deleted.
      • BPCUI0131E The alerts cannot be unacknowledged because they were deleted.
      • BPCUI0132W success_count alerts were marked as acknowledged. unsuccess_count alerts cannot be marked as acknowledged because they were deleted.
      • BPCUI0133W success_count alerts were marked as unacknowledged. unsuccess_count alerts cannot be marked as unacknowledged because they were deleted.
      • BPCUI0134E The alert cannot be acknowledged because it was deleted.
      • BPCUI0135E The alert cannot be unacknowledged because it was deleted.
      • BPCUI0136E The device was not removed because the action is not supported for devices of type devType.
      • BPCUI0137E Input text provided has invalid character(s): characters. Input text: text
      • BPCUI0141E Host name or IP address hostname specified on line line of file file is not valid.
      • BPCUI0143E Host port WWPN wwpn specified on line line of file file is not valid.
      • BPCUI0144E Duplicate server name specified on lines line1 and line2 of file file.
      • BPCUI0145E Could not parse file file.
      • BPCUI0146E Could not parse file file. Invalid entry on line line.
      • BPCUI0148I Successfully deleted server server_name.
      • BPCUI0149I Successfully modified ports of server server_name.
      • BPCUI0150I The server was created.
      • BPCUI0151E The host name or IP address is associated with another resource.
      • BPCUI0152I The data source data_Source_Address was successfully added as a data source for monitoring. The following new resources were detected:
      • BPCUI0155W You cannot provision volumes because there is no Fibre Channel host port information for at least one server.
      • BPCUI0156W You cannot provision volumes to servers that use different operating systems.
      • BPCUI0157W You cannot provision volumes to servers and virtual machines at the same time. To provision volumes, ensure that you select either only servers or only virtual machines.
      • BPCUI0158I Volumes are assigned to the hypervisors that host virtual machines. Volumes are not assigned directly to virtual machines.
      • BPCUI0159W You cannot provision volumes because at least one of the hypervisors that host the virtual machines is not being monitored. Ensure that all the hypervisors that are hosting the virtual machines that were selected for provisioning were probed.
      • BPCUI0160E Duplicate port WWPN wwpn specified on lines line1 and line2 of file file.
      • BPCUI0162W File file does not contain any servers to create.
      • BPCUI0166W Optimization cannot be done in place to the subsystem since storage subsystem param1 and/or its pools belong to more than one capacity pool. Following are capacity pools the subsystem is associated with: param2
      • BPCUI0167W Optimization cannot be done in place to the subsystem since storage subsystem param1 and/or its pools are not part of any capacity pool.
      • BPCUI0168W Optimization cannot be done in place to the server param1 since storage subsystems or storage pools associated with luns assigned to the server belong to more than one capacity pool. Following are associated capacity pools: param2
      • BPCUI0169W Optimization cannot be done in place to the server param1 since storage subsystems or storage pools associated with luns assigned to the server are not part of any capacity pool.
      • BPCUI0170W Optimization cannot be done in place to the storage entity param1 since storage subsystems or storage pools associated with it belong to more than one capacity pool. Following are associated capacity pools: param2
      • BPCUI0171W Optimization cannot be done in place to the storage entity param1 since storage subsystems or storage pools associated with it are not part of any capacity pool.
      • BPCUI0172E The operation timed out while waiting for a response from the server.
      • BPCUI0173E File file does not exist or is empty.
      • BPCUI0174E The device does not support the credential mechanism used.
      • BPCUI0175E A required parameter is missing.
      • BPCUI0176E The highlighted field contains an invalid value.
      • BPCUI0177E The highlighted field contains a value that is outside of the allowed range. The value must be between minVal and maxVal.
      • BPCUI0178E A service class with the same name and type already exists.
      • BPCUI0179I The service class was created.
      • BPCUI0180I Based on the known configuration of storage system host connections, fabric zone aliases, and HBA ports, additional ports may have been added to the selection below.
      • BPCUI0181I You selected to add a expectedDevice resource, but a foundDevice resource was detected and will be added.
      • BPCUI0182I The data source data_Source_Address was added as a data source for monitoring. No new resources were detected.
      • BPCUI0183E The text in the highlighted field exceeds the maxLength character limit.
      • BPCUI0185W Unable to lookup the IP Address for Host Name hostName. Enter the IP Address manually.
      • BPCUI0191E An internal error occurred while testing conneciton to param1.
      • BPCUI0192E The supplied service class type is invalid.
      • BPCUI0193E The specified SMI-S provider was not found. Make sure that the protocol, SMI-S provider host name or IP address, and port are specified correctly and that the SMI-S provider is properly configured at that location.
      • BPCUI0194E An unknown error has occurred. Please review all values entered.
      • BPCUI0195E The Interop Namespace is not correct. Please correct this entry.
      • BPCUI0196E A timeout occured while processing the request. Please retry request.
      • BPCUI0197E A connection was not established. Make sure that the protocol, SMI-S provider host name or IP address, and port are specified correctly.
      • BPCUI0198E The authentication to the SMI-S provider failed.
      • BPCUI0199E An SSLHandshakeException or SSLProtocolException has occurred. This exception might be due to an invalid SLP registration, e.g. 'http' instead of 'https'.
      • BPCUI0201E There is a pending delete in process for this SMI-S provider.
      • BPCUI0202I Success
      • BPCUI0203E The selected resources were not removed.
      • BPCUI0204W successfulDeletes of attemptedDeletes of the selected resources were removed.
      • BPCUI0205W successfulDeletes selected resources were removed, however warnings did occur.
      • BPCUI0209E A database operation cannot be completed.
      • BPCUI0210I Device param1 supports performance monitoring.
      • BPCUI0211E No performance data is available for a resource.
      • BPCUI0212E There is no Secure Shell running at this host/IP.
      • BPCUI0213E Unsupported Secure Shell protocol was used.
      • BPCUI0214E Invalid public key location for subsystem param1.
      • BPCUI0215E Invalid public key format for subsystem param1.
      • BPCUI0216E Passphrase was incorrect for subsystem param1.
      • BPCUI0217E Unable to transfer the key(s) to the server param1.
      • BPCUI0218E The specified private key file format is not supported. Please convert it to Open SSH (.pem) key file format for subsystem param1.
      • BPCUI0219E The specified key file or key file name is already linked to another user.
      • BPCUI0220E The IP address that was entered was the address of the management console for the storage system. You must enter the valid IP address of the block component of the storage system.
      • BPCUI0221E The IP address you entered is the address of another device's management console.
      • BPCUI0222E The IP address you entered points to a device of another type.
      • BPCUI0223E Passphrase is required. Specify one for subsystem param1.
      • BPCUI0224E Cannot connect to a resource because of an SSL certificate error. Troubleshooting information: http://www.ibm.com/support/docview.wss?uid=swg21976237
      • BPCUI0226I Discovery of data_source is taking longer than expected. Click Close to run the discovery in the background.
      • BPCUI0227E Thin provisioning must be enabled when compression is enabled.
      • BPCUI0229I 1 resource was added to name.
      • BPCUI0231I count resources were added to name.
      • BPCUI0233E The specified host name is already associated with an existing server.
      • BPCUI0234E The specified IP address is already associated with an existing server.
      • BPCUI0235E The specified host name and IP address are already associated with an existing server.
      • BPCUI0236E The disabling of the agents failed.
      • BPCUI0237E Errors occurred when attempting to disable some of the agents.
      • BPCUI0238W Warnings occurred when attempting to disable warningCount of the agents.
      • BPCUI0239I attemptedCount of the selectedCount selected agents were disabled.
      • BPCUI0240E The agents were not enabled.
      • BPCUI0241E Errors occurred when attempting to enable some of the agents.
      • BPCUI0242W Warnings occurred when attempting to enable warningCount of the agents.
      • BPCUI0243I attemptedCount of the selectedCount selected agents were enabled.
      • BPCUI0244I The credentials of an agent were updated.
      • BPCUI0245I The credentials of updateCount agents were updated.
      • BPCUI0246E Cannot authenticate to the file module with the provided user credentials.
      • BPCUI0247E Unknown file module key user.
      • BPCUI0248E The SSH key could not be loaded for the following reason:IOException message
      • BPCUI0249E Passphrase is incorrect.
      • BPCUI0250E Passphrase is required.
      • BPCUI0251E Cannot connect to the storage system or cluster.
      • BPCUI0252E The host name or IP address {0} is not valid.
      • BPCUI0253E Cannot connect to the data source for the resource with the address ip_address.
      • BPCUI0254E Invalid private key location.
      • BPCUI0255W The following resources are already assigned to a capacity pool. Are you sure you want to move these resources to a different capacity pool?
      • BPCUI0256W The following resources are already assigned to a capacity pool. Are you sure you want to move these resources to a different capacity pool?
      • BPCUI0257W The following resources are already assigned to a capacity pool. Are you sure you want to move these resources to a different capacity pool?
      • BPCUI0258W The following internal resources of a storage system you are attempting to add are already assigned to a capacity pool. Are you sure you want to move these resources to a different capacity pool?
      • BPCUI0259W The following storage systems and storage-system internal resources are already assigned to a capacity pool. Are you sure you want to move these resources to a different capacity pool?
      • BPCUI0260E The specified private key file format for the file module is not supported. Please convert it to Open SSH (.pem) key file.
      • BPCUI0261E The service class was not found in the database.
      • BPCUI0262E The capacity pool was not found in the database.
      • BPCUI0263E The scheduling of the agent upgrade jobs failed.
      • BPCUI0264E Errors occurred when attempting to schedule the upgrade jobs of some of the agents.
      • BPCUI0265W Warnings occurred when scheduling the upgrade of warningCount of the agents.
      • BPCUI0266I attemptedCount of the selected agents were scheduled for upgrade.
      • BPCUI0267I The upgrade agent job was successfuly scheduled for hostName.
      • BPCUI0268W Deleting a capacity pool does not affect any volumes or shares that were provisioned from the capacity pool. However, the volumes or shares are no longer associated with the capacity pool. Associations with the following volumes or shares will be removed:
      • BPCUI0269W The following volumes are associated with the service class scName. When the volumes were created, they satisfied the requirements of the service class. If you modify the service class, the volumes are still associated with the service class, but might not satisfy the new requirements of the service class. Depending on your changes to the service class, users might incorrectly assume that the volumes have properties that they do not possess.
      • BPCUI0270W The following shares are associated with the service class scName. When the shares were created, they satisfied the requirements of the service class. If you modify the service class, the shares are still associated with the service class, but might not satisfy the new requirements of the service class. Depending on your changes to the service class, users might incorrectly assume that the shares have properties that they do not possess.
      • BPCUI0271W The following volumes are associated with the service class scName. If you delete the service class, the volumes are no longer associated with any service class.
      • BPCUI0272W The following shares are associated with the service class scName. If you delete the service class, the shares are no longer associated with any service class.
      • BPCUI0273E The action does not support the specified type of device.
      • BPCUI0274I The connection test to resource data_Source_Name was successful.
      • BPCUI0276I Agent agentName was disabled.
      • BPCUI0277I Agent agentName was enabled.
      • BPCUI0278I The credentials for agentName were updated.
      • BPCUI0279I There is no job defined for the device Name. Please create a job first before running it again.
      • BPCUI0280I No switches are managed by the data_Source_Address data source.
      • BPCUI0282I The resources that are managed by data_Source_Address are already known. One or more resources were added.
      • BPCUI0284I No fabrics are managed by the data_Source_Address data source.
      • BPCUI0286I The fabrics that are managed by data_Source_Address are already being monitored.
      • BPCUI0289W The following network shared disks (NSDs) are already assigned to a capacity pool. Are you sure you want to move these NSDs to a different capacity pool?
      • BPCUI0290W The following file systems and network shared disks (NSDs) are already assigned to a capacity pool. Are you sure you want to move these resources to a different capacity pool?
      • BPCUI0291W The following network shared disks (NSDs) are already assigned to a capacity pool. Are you sure you want to move these NSDs to a different capacity pool?
      • BPCUI0292E The host name or IP address ip_address_or_hostname cannot be reached.
      • BPCUI0293I A probe is started for deviceName.
      • BPCUI0294I A performance monitor is started for deviceName.
      • BPCUI0295I The performance monitor is stopped for deviceName.
      • BPCUI0297W One resource was added to capacity_pool_name. One resource could not be added because it could not be found.
      • BPCUI0298W count resources were added to capacity_pool_name. One resource could not be added because it could not be found.
      • BPCUI0299W One resource was added to capacity_pool_name. count_Not_Found resources could not be added because they could not be found.
      • BPCUI0300W count resources were added to capacity_pool_name. count_Not_Found resources could not be added because they could not be found.
      • BPCUI0301E Failed to assign the role name role.
      • BPCUI0302E Failed to retrieve the existing role assignments.
      • BPCUI0303E Failed to remove all role assignments from the specified groups.
      • BPCUI0304W An error occurred when saving the user-defined properties of the resourcesType.
      • BPCUI0305E A capacity pool with the same name already exists.
      • BPCUI0306W The selected resource was removed, however warnings did occur.
      • BPCUI0307E The schedule could not be deleted.
      • BPCUI0308I The resource does not have a connection configured. To add a connection to the resource, click Add Storage System.
      • BPCUI0309I A probe schedule is defined for deviceName.
      • BPCUI0310I A performance monitor schedule is defined for deviceName.
      • BPCUI0311I Probe and performance monitor schedules are defined for deviceName.
      • BPCUI0312I SNMP Discovery of switches is taking longer than expected. Click Close to run the discovery in the background.
      • BPCUI0313I An upgrade is started for server deviceName.
      • BPCUI0314E Failed to retrieve the list of user groups from the WebSphere user repository.
      • BPCUI0315E Failed to retrieve the list of user groups from user repository due to an invalid search string.
      • BPCUI0316W Failed to update the role cache maintained by the Device server.
      • BPCUI0317E Access can not be removed, because at least one Administrator user must remain in the system.
      • BPCUI0318E The group mapping can not be modified, because at least one Administrator user must remain in the system.
      • BPCUI0319I A task is started for resource resourceName.
      • BPCUI0320I Probe and performance monitor schedules are defined for deviceName. A performance monitor is scheduled to collect performance data after the probe is done.
      • BPCUI0321I A task is paused for resource resourceName.
      • BPCUI0322E A task could not be paused for resource resourceName.
      • BPCUI0323I A task is resumed for resource resourceName.
      • BPCUI0324E A task could not be resumed for resource resourceName.
      • BPCUI0325E Failed to retrieve the list of users from the WebSphere user repository.
      • BPCUI0326E Failed to retrieve the list of users from user repository due to an invalid search string.
      • BPCUI0327E Failed to get the roles associated with the current user.
      • BPCUI0328I A task is saved.
      • BPCUI0329I A task was successfully deleted.
      • BPCUI0330E The user user is not authorized to access the product.
      • BPCUI0331I A task is cancelled for resource resourceName.
      • BPCUI0332E An unexpected error occurred. The task for schedule schedule name could not be paused or resumed.
      • BPCUI0333E An unexpected error occurred. The task for schedule schedule name could not be be paused.
      • BPCUI0334E An unexpected error occurred. The task for schedule schedule name could not be resumed.
      • BPCUI0335E The volumes cannot be converted or moved because the target pools do not have sufficient available space.
      • BPCUI0336I The ability to provision with block storage devices is only available with the advanced license.
      • BPCUI0338E Insufficient user privileges to service the REST request.
      • BPCUI0339E An unexpected error occurred while authorizing the REST request.
      • BPCUI0340I A task was successfully renamed.
      • BPCUI0341E The task could not be renamed.
      • BPCUI0342E The task could not be renamed because the specified name already exists.
      • BPCUI0343I Performance monitoring is unavailable for resource resource name because the resource was not probed.
      • BPCUI0344W The following service classes allow provisioning only from the capacity pool capacity pool: service classes. If you delete this capacity pool, the service classes will allow provisioning from any available storage.
      • BPCUI0348W You cannot provision volumes because at least one of the selected hosts was not found in the database. Ensure that all hosts that are selected for provisioning are being monitored.
      • BPCUI0349W You cannot provision volumes because not all of the selected hosts appear to have Fibre Channel connectivity.
      • BPCUI0350W You cannot provision volumes because the hypervisors that host the virtual machines use different operating systems.
      • BPCUI0351W You cannot provision volumes because there is no Fibre Channel host port information for at least one hypervisor.
      • BPCUI0352W You cannot provision volumes because not all of the hypervisors that host the virtual machines appear to have Fibre Channel connectivity.
      • BPCUI0355W You cannot provision volumes because no block-storage service class exists.
      • BPCUI0356W You cannot provision shares because no file-storage service class exists.
      • BPCUI0357W You cannot provision volumes because you do not have permission to provision by using any block-storage service class.
      • BPCUI0358W You cannot provision shares because you do not have permission to provision by using any file-storage service class.
      • BPCUI0359E The credentials for the servers were not updated.
      • BPCUI0360W The credentials for successfulUpdates of attemptedUpdates of the selected servers were updated.
      • BPCUI0361W The credentials for the selected server was updated, however warnings did occur.
      • BPCUI0362W The credentials for successfulUpdates selected servers were updated, however warnings did occur.
      • BPCUI0363E Cannot connect to the SNMP data source IP_Address.
      • BPCUI0364I The performance monitor schedule was updated for deviceName.
      • BPCUI0366W The server serverName was not updated because it does not support the action.
      • BPCUI0367W You cannot provision volumes to virtual machines with NPIV ports and virtual machines without NPIV ports at the same time. To provision volumes to virtual machines, ensure that you select either only virtual machines with NPIV ports or only virtual machines without NPIV ports.
      • BPCUI0368W You cannot provision volumes because none of the selected hosts appear to have Fibre Channel connectivity and the automatic zoning option is enabled. Disable the automatic zoning option in your zoning policy.
      • BPCUI0369W You cannot provision volumes because none of the hypervisors that manage the selected virtual machines appear to have Fibre Channel connectivity and the automatic zoning option is enabled. Disable the automatic zoning option in your zoning policy.
      • BPCUI0370E The display name displayName is already assigned to resource resource Name.
      • BPCUI0372I The selected hosts do not appear to have Fibre Channel connectivity. In the resulting provisioning task, ensure that the recommended storage system is connected to the hosts before you run the task. Also, be aware that all fabric-related options will be ignored.
      • BPCUI373I Volumes are assigned to the hypervisors that host virtual machines. Volumes are not assigned directly to virtual machines that do not have NPIV ports. None of the hypervisors that manage the virtual machines appear to have Fibre Channel connectivity. In the resulting provisioning task, ensure that the recommended storage system is connected to the hypervisors before you run the task. Also, be aware that all fabric-related options will be ignored.
      • BPCUI0374E Schedule is not enabled for the resource resource.
      • BPCUI0375E Performance data is not available.
      • BPCUI0376E Invalid number of days to keep configuration history. The number should be between minimum value and maximum value.
      • BPCUI0377E Invalid number of days to keep data for removed resources. The number should be between minimum value and maximum value.
      • BPCUI0378E Invalid number of days to keep sample performance data. The number should be between minimum value and maximum value.
      • BPCUI0379E Invalid number of days to keep hourly performance data. The number should be between minimum value and maximum value.
      • BPCUI0380E Invalid number of days to keep daily performance data. The number should be between minimum value and maximum value.
      • BPCUI0381E Failed to update the performance data retention settings.
      • BPCUI0382E Performance monitoring is unavailable for resource resource name.
      • BPCUI0383E Failed to update the history retention settings.
      • BPCUI0384E Failed to retrieve the history retention settings.
      • BPCUI0385E Invalid number of runs to keep log files for each schedule. The number should be between minimum value and maximum value.
      • BPCUI0386E A job cannot be run for resource resourceName because there is a job already running for the resource. Wait for the job to finish and try again.
      • BPCUI0387I The selected resources support different performance monitor intervals. If you select multiple resources, intervals that are common to all resources are displayed in the interval list.
      • BPCUI0388E The probe schedule cannot be created for resource {0} because not all the information was provided. If you are configuring a probe for a resource for the first time, you must enter values for the probe status, time, and frequency fields.
      • BPCUI0389E The performance monitor schedule cannot be created because not all the information was provided. If you are configuring a performance monitor for a resource for the first time, you must enter values for the performance monitor status and interval fields.
      • BPCUI0390I The service logs were successfully created.
      • BPCUI0391I The connection test to data source data source was successful. A probe is running. The health status is unknown until the probe is finished.
      • BPCUI0392I The connection test to the data source data source was successful.
      • BPCUI0393E The user user_name does not have sufficient privileges to deploy the vSphere Web Client extensionr.
      • BPCUI0394E The user user_name does not have permission to log in to the vCenter Server system.
      • BPCUI0395E This version of the vCenter Server server_name does not support the deployment of the vSphere Web Client extension for the product.
      • BPCUI0396E The user user_ID does not have the required role. The role associated with this user must be Administrator, Monitor, or External Application.
      • BPCUI0397E The vCenter Server user name or password is invalid.
      • BPCUI0398E The user name or password is invalid.
      • BPCUI0399I The server was started.
      • BPCUI0400E Failed to retrieve the system management information from the Data server.
      • BPCUI0402E Failed to retrieve the server status of the Data server.
      • BPCUI0403E The SMI-S provider service is not available.
      • BPCUI0404E An error occurred while updating the trace log configuration file. The original file file was deleted and could not be restored. A backup of this file may be available at backup file.
      • BPCUI0405E Failed to set the trace settings from the Data server.
      • BPCUI0406E Cannot start the server. The start script reported the following error: error
      • BPCUI0407E Cannot start the server. Unable to locate the start script path to script.
      • BPCUI0408E Cannot start the server. Unable to execute the start script path to script.
      • BPCUI0409W The server is taking a long time to start. If the server status continues to show an error status after a reasonable interval, try to start the server again.
      • BPCUI0410E Cannot stop the server. The stop script reported the following error: error
      • BPCUI0411W The server is taking a long time to stop. If the server status continues to show that it is still running try to stop the server again after a reasonable interval.
      • BPCUI0412E Cannot stop the server. Unable to locate the stop script path to script.
      • BPCUI0413E Cannot stop the server. Unable to execute the stop script path to script.
      • BPCUI0414W It is taking a long time for the services to start. If the server status continues to show an error status after a reasonable interval, try to start the services again. If the problem persists then restart the server.
      • BPCUI0415E Failed to start the service service name.
      • BPCUI0416I The server was stopped.
      • BPCUI0417I The services of the server were started.
      • BPCUI0418E The action cannot be completed because the data source that is managing this resource cannot be reached.
      • BPCUI0420E A file access error occurred when the system attempted to back up or modify the tracing configuration file configuration file.
      • BPCUI0421E There is a log collection operation already running. A new one cannot be submitted until the current one completes.
      • BPCUI0422E Cannot start the log collecting job. Unable to locate the required script path to script.
      • BPCUI0423E Cannot start the log collecting job. Unable to run the log collection script path_to_script.
      • BPCUI0424E Storage cannot be provisioned from capacity pool capacity pool using service class service class for the following reason:
      • BPCUI0425W The task task name cannot be scheduled because it is already running.
      • BPCUI0426E Storage cannot be provisioned by using service class service class for the following reason:
      • BPCUI0427W The selected group action is complete for all tasks, but warnings were reported.
      • BPCUI0428I The selected group action is complete for all tasks. Some informational messages were returned.
      • BPCUI0429E The validation process cannot contact the server. The server might be down or unreachable due to network problems.
      • BPCUI0430I Some tasks were not deleted because they were already run.
      • BPCUI0431E Failed to retrieve the list of managed devices.
      • BPCUI0432E Failed to retrieve the performance monitoring granularity from the Device server. Check the connection to the Device server and retry the operation.
      • BPCUI0433E OS type osType specified on line line of file file is not valid.
      • BPCUI0434E Data source data_Source_Key could not be found.
      • BPCUI0435E Required host name or IP address and OS type were not specified on line line of file file.
      • BPCUI0436E The alert notification settings cannot be displayed.
      • BPCUI0437E The alert notification settings cannot be saved.
      • BPCUI0438E File file does not exist or is empty.
      • BPCUI0439E The file file could not be uploaded.
      • BPCUI0440E The text location specified on line line of file file has invalid character(s): characters
      • BPCUI0441E The alert definitions cannot be displayed.
      • BPCUI0442E The alert definitions cannot be saved.
      • BPCUI0443E Select at least one managed server that is deployed for which alert notification settings need to be displayed.
      • BPCUI0444E Select at least one managed server that is deployed for which alert definitions need to be displayed.
      • BPCUI0445W The discovery job completed with errors. Some available devices were not discovered.
      • BPCUI0446E Unable to test the connection to the device because the request was not processed by the data collector.
      • BPCUI0447E Select at least one managed storage subsystem for which alert notification settings need to be displayed.
      • BPCUI0448E Select at least one managed storage subsystem for which alert definitions need to be displayed.
      • BPCUI0449E The user does not have the required authority to complete the task or command.
      • BPCUI0451E One or more applications from provided list: names do not exist.
      • BPCUI0452E entity name is not supporting data collection actions.
      • BPCUI0453E One or more departments from provided list: names do not exist.
      • BPCUI0455I No performance data is available for the selected resources.
      • BPCUI0456E You cannot complete the action because the service is temporarily unavailable.
      • BPCUI0457W The applications listOfApplications cannot be deleted because they contain subcomponents subcomponent, which cannot be moved up a level in the applications hierarchy due to name conflicts with existing applications in that higher level.
      • BPCUI0458W The deparments listOfDepartments cannot be deleted because they contain subdepartments or applications subdepartment, which cannot be moved up a level in the departments hierarchy due to name conflicts with departments in that higher level.
      • BPCUI0459W The selected subcomponents cannot be removed from the application because they cannot be moved up a level in the application hierarchy due to name conflicts with the existing applications or subcomponents at the higher level.
      • BPCUI0460W The selected applications or subdepartments cannot be removed from the department because they cannot be moved up a level in the department hierarchy due to name conflicts with the existing applications or subdepartments at the higher level.
      • BPCUI0461W There are no task details to display. The analysis-execution task could not be run.
      • BPCUI0462E Failed to add the device because the data collector is not responding.
      • BPCUI0463E The discovery failed because the data collector is not responding.
      • BPCUI0464E The connection test failed because the data collector is not responding.
      • BPCUI0465E The requested action failed because the data collector is not responding.
      • BPCUI0466I The servers were created.
      • BPCUI0467W successCount of totalCount servers were created.
      • BPCUI0468E The creation of the servers failed.
      • BPCUI0469E Schedule job does not exist for entity name.
      • BPCUI0470E Invalid file file size of size GB. Maximum allowed file size is max size GB.
      • BPCUI0471E Failed to set the trace settings from the Alert server.
      • BPCUI0472E Failed to retrieve the system management information from the Alert server.
      • BPCUI0474E Failed to retrieve the server status of the Alert server.
      • BPCUI0475I The volumes have been excluded from the reclamation analysis.
      • BPCUI0476I The volumes will be included in future analyses to reclaim storage.
      • BPCUI0477E An unexpected error occurred when modifying the optimization characteristics of the volumes.
      • BPCUI0478E The scheduled agent upgrade time is in the past.
      • BPCUI0479E The object storage credentials are incorrect. Enter the correct credentials. Alternatively, clear the object credentials check box and do not specify the authentication credentials for object storage now. You can use the Modify Connection action to add the object storage later.
      • BPCUI0480E An object storage request failed on the GPFS cluster.
      • BPCUI0481W No resources were removed.
      • BPCUI0482E No resources were updated.
      • BPCUI0483E The connection information cannot be updated because it points to another device.
      • BPCUI0484I The connection information for device name was updated.
      • BPCUI0485E The connection information cannot be updated.
      • BPCUI0486E Cannot query the object service for information about accounts and containers as the specified user does not have admin privileges.
      • BPCUI0487I The connection information of the selected device was successfully updated. Other devices were detected as being managed by the same data source. Would you like to update the connection information of all of them?
      • BPCUI0488I The connection information of all devices connecting through this data source was updated.
      • BPCUI0489W Some of the devices connecting through this data source failed to be updated.
      • BPCUI0490I The vCenter vCenter Server was removed.
      • BPCUI0491E The vCenter vCenter Server was not found in the database.
      • BPCUI0492E The selected vCenter Servers were not found in the database.
      • BPCUI0493I The vCenter vCenter Server and all number of monitored hypervisors hypervisors monitored by it were successfully removed.
      • BPCUI0494I The number of vCenters selected vCenter Servers and all number of monitored hypervisors hypervisors monitored by them were successfully removed.
      • BPCUI0495W Only number of removed vCenters of number of selected vCenters of the selected vCenter Servers and number of removed monitored hypervisors of number of monitored hypervisors of the hypervisors monitored by them were successfully removed.
      • BPCUI0496I The following fabrics were detected as being managed by the same data source: comma separated fabrics list. This action applies to all fabrics that are managed by the current data source. Would you like to update the connection information of all of them?
      • BPCUI0497E The following fabrics cannot be monitored through the SMI agent: comma separated fabrics list. The data source connection information will not be updated.
      • BPCUI0498E The fabric cannot cannot be monitored through the SMI agent.
      • BPCUI0499I Other switches were detected as being managed by the same data source. This action applies to all switches that are managed by the current data source. Would you like to update the connection information of all of them?
      • BPCUI0500E One or more switches cannot be monitored through the SMI agent. The data source connection information will not be updated.
      • BPCUI0501E The information cannot be displayed. Log out of the GUI, log in, and try the action again.
      • BPCUI0502E The device is already managed by this data source. The data source connection information will not be updated.
      • BPCUI0503I The connection information of the selected switches was updated.
      • BPCUI0504I The detected versions of the resources discovered on the data source data_Source_Address are unsupported.
      • BPCUI0505E The resource does not have a connection configured.
      • BPCUI0506E Cannot connect to the Alert server.
      • BPCUI0507E The version of the tpc_server IBM Spectrum Control Server is not supported.
      • BPCUI0508E Cannot connect to the rollup server rollup_server on port host_port.
      • BPCUI0509E Cannot authenticate with the rollup server using the provided credentials.
      • BPCUI0510E You entered an invalid time range. The start date and time must be before the end date and time.
      • BPCUI0511E The following alert name(s) are not unique: names.
      • BPCUI0512E Custom alerts already exist for other resources with the following alert name(s): names.
      • BPCUI0513E Unable to connect from rollup server rollup_server to the repository database.
      • BPCUI0514E The specified secondary server secondary_server is the primary server.
      • BPCUI0515E The duration of the automated probe run window must be at least minimum_hours hours.
      • BPCUI0516W The selected subgroups cannot be removed from the general group because they cannot be moved up a level in the groups hierarchy due to name conflicts with the general groups at the higher level.
      • BPCUI0519E Authorization has failed because the private key is not valid for the user name that you have specified.
      • BPCUI0520E The IP address ip_address for the FlashSystem storage system is not the management IP address.
      • BPCUI0521E The configuration for the report can't be saved.
      • BPCUI0522E Failed to delete a report configuration.
      • BPCUI0523E Alerts cannot be defined for this storage system.
      • BPCUI0524E The changes to the report configuration can't be saved.
      • BPCUI0525E The configuration for the report can't be saved because the report title isn't unique.
      • BPCUI0527E The action cannot be completed because of an invalid request.
      • BPCUI0528E The action cannot be completed because of an invalid file upload request.
      • BPCUI0526I The connection test to data source data source was successful. A probe is running.
      • BPCUI0529I The data source data_Source_Address is already being managed as a data source for monitoring. No new resources were detected.
      • BPCUI0530I The data source data_Source_Address is already being managed as a data source for monitoring. The following new resources were detected:
      • BPCUI0531E The action cannot be completed because LDAP registry file failed to upload.
      • BPCUI0532E The action failed because of a missing resource.
      • BPCUI0533E The LDAP configuration test failed.
      • BPCUI0534E There was an error executing the collect log process. If this problem persists, you can try collecting and uploading the service logs manually. Learn More.
      • BPCUI0535E An FTP connection can not be established. If your organization requires the use of a proxy server, consult the following documentation: Troubleshooting FTP Transfers.
      • BPCUI0536E The support data collection failed due to an invalid PMR number format.
      • BPCUI0537E The support package could not be created because file system permissions prevent the creation of temporary files.
      • BPCUI0538E The support data collection completed creating a support package, but the package could not be uploaded to IBM.
      • BPCUI0539E The support data collection failed with an internal error
      • BPCUI0540E The support data collection failed due to an invalid email address format.
      • BPCUI0541E The specified SMI agent was not found. Make sure that the protocol, SMI agent host name or IP address, and port are specified correctly and that the SMI agent is properly configured at that location.
      • BPCUI0542E A connection was not established. Make sure that the protocol, SMI agent host name or IP address, and port are specified correctly.
      • BPCUI0543E The authentication to the SMI agent failed.
      • BPCUI0544E There is a pending delete in process for this SMI agent.
      • BPCUI0545E The SMI agent service is not available.
      • BPCUI0546E The action cannot be completed because the LDAP registry file could not be updated.
      • BPCUI0547E Connection failed. The server might be down or unreachable due to network problems.
      • BPCUI0548E The add SSL certificate action failed.
      • BPCUI0549E The add SSL certificate action failed because of a wrong password.
      • BPCUI0550E The specified storage resource is not valid for the REST API service request.
      • BPCUI0551E The file cannnot be used because it is not a valid SSL certificate. Select a valid certificate file and try again.
      • BPCUI0554E The SSL certificate download process failed.
      • BPCUI0555E The test connection to the LDAP server failed. Verify that your XML file contains the correct syntax and values and that the LDAP server is running.
      • BPCUI0556E An unexpected error occurred creating or updating a support ticket.
      • BPCUI0557E An invalid request was made when creating or updating a support ticket.
      • BPCUI0558E This tier name is already in use. Enter a different name.
      • BPCUI0559E The custom dashboard was removed by another user. Cancel the action and refresh the page manually.
      • BPCUI0600W Can't save the scheduling information for the report because the Data server is offline.
      • BPCUI0601I The resource does not have a connection configured. To add a connection to the resource, click Add Switch or Add Fabric.
      • BPCUI0602E The osAuthentication script does not start. The script reported the following error: script_error.
      • BPCUI0603E The connection test to data source data source was not successful.
      • BPCUI0604E Can't stop data collection for entity name.
      • BPCUI0605E Can't restart data collection for entity name.
      • BPCUI0606E The action cannot be completed because there was a failure to create or write into the pending configuration file.
      • BPCUI0607E The action cannot be completed because there was a failure to read the pending LDAP registry file.
      • BPCUI0608E The action cannot be completed because there was a failure to get the list of LDAP groups.
      • BPCUI0609E The Local OS authentication configuration test failed.
    • BTADS/BTAFM/BTAVM/HWN - Job logging messages
      • BTADS0000I Starting Discover Process value , with Device Server RUN ID value , and Job ID value .
      • BTADS0001I Discover Process with Device Server run ID value and job ID value is complete.
      • BTADS0002I Starting Child Discover Process value with Job ID= value .
      • BTADS0003I The Child Discover Process with Job ID value has completed with Status= value and Return Code= value .
      • BTADS0004W The child discovery request with job ID job_id completed with status status_number and return code value.
      • BTADS0005E The child discovery request with job ID job_id completed with status status_number and return code value.
      • BTADS0010I Invoking outband scanner value on agent value .
      • BTADS0011I Outband scanner value on agent value completed successfully.
      • BTADS0012E Outband Scanner value on agent value failed with return code value .
      • BTADS0019E An outband scanner failed to capture the scan data.
      • BTADS0020I Processing value data from agent value .
      • BTADS0021W Warning encountered while parsing Fabric XML for job: RUN ID= value , and Job ID= value . value .
      • BTADS0022E Exception encountered while parsing Fabric XML for job: RUN ID= value , and Job ID= value . value .
      • BTADS0023E Fatal error encountered while parsing Fabric XML for job: RUN ID= value , and Job ID= value . value .
      • BTADS0024E Error encountered processing scanner value data from agent value . value .
      • BTADS0025I Running job to discover SMI-S providers through Service Location Protocol: RUN ID= value , Job ID= value .
      • BTADS0026I Service Location Protocol has found value SMI-S providers.
      • BTADS0027E Error encountered by a Service Location Protocol job: RUN ID= value , and Job ID= value . value .
      • BTADS0028W The Device Server Job with RUN ID=: value , Job ID= value , Discover Request= value has been cancelled since it is long running.
      • BTADS0029I Scanner value data from agent value has not changed since last scan.
      • BTADS0030I Invoking inband Scanner value on agent value .
      • BTADS0031I Inband Scanner value on Agent value completed successfully.
      • BTADS0032E Inband Scanner value failed on agent value with Return Code value .
      • BTADS0033E Error invoking value on host value .
      • BTADS0034E Fatal error encountered while persisting the data for job: RUN ID= value , and Job ID= value . value .
      • BTADS0035E The execution of the job failed with: value .
      • BTADS0036I Found SNMP Target at value .
      • BTADS0037E Found SNMP Target at value but it is not persisted in the database. Will NOT perform discovery of information using the address.
      • BTADS0038I Starting scan of SNMP agents from value to value .
      • BTADS0039I Starting probe of detected agents.
      • BTADS0040I Processing of Scanner value data from Agent value completed successfully.
      • BTADS0041I Discover Process with Device Server RUN ID value and Job ID value completed successfully.
      • BTADS0042E Discover Process with Device Server RUN ID value and Job ID value failed with return code value .
      • BTADS0043I Invoking value scanner value on target value .
      • BTADS0044I value scanner value on target value completed succesfully.
      • BTADS0045E value Scanner value on target value failed with return code value .
      • BTADS0046I Processing value data from agent value .
      • BTADS0047W The value parser encountered a warning while parsing XML for job with RUN ID= value , and Job ID value . The return code from the parser job is value .
      • BTADS0048E The value parser encountered an exception while parsing XML from job with RUN ID= value , and Job ID= value .The return code from the parser is value .
      • BTADS0049E The value parser for Device Server job with RUN ID= value , and Job ID= value failed. The return code from the parser is value .
      • BTADS0050I Service Location Protocol has found SMI-S provider, value , at address value .
      • BTADS0051I Service Location Protocol has found SMI-S provider, value , at address value , which requires security information to be configured.
      • BTADS0052W Warning encountered while parsing value data from agent value. value.
      • BTADS0053E Exception encountered while parsing value data from agent value. value.
      • BTADS0054E Fatal error encountered while parsing value data from agent value. value.
      • BTADS0055E Outband Scanner value on agent value encountered the presence of a McData i10k. These devices do not report correctly via SNMP and can only be used with SMI-S provider.
      • BTADS0056E Errors in Topology XML generator.
      • BTADS0057E Errors occurred while resolving InterconnectElement and Port relationship.
      • BTADS0058E Errors in creating an entity.
      • BTADS0059E The outband agent target address IP address is not a Cisco device or is invalid.
      • BTADS0060E Outband Scanner value is not responding.
      • BTADS0062E Encountered SQL error value while persisting some data.
      • BTADS0063E The execution of the PM BSP invocation failed with: value .
      • BTADS0063W The performance data collection for the current device is not enabled.
      • BTADS0064I Starting scan of Storage Subsystems from value to value .
      • BTADS0065I Outband and inband agents for fabric(s) specified in probe are value
      • BTADS0066I Could not find scanners for agent value
      • BTADS0067I Agent value is configured for no SAN calls and so no scanners will be invoked for this particular agent
      • BTADS0068I Could not retrieve connection information for agent value. Will not be able to invoke scanners for this particular agent
      • BTADS0069I Added inband scanner job with id value discover request value for agent value.
      • BTADS0070I Agent value has not discovered any fabrics and will not be used during the probe.
      • BTADS0071I Invoked inband Scanner value on agent value .
      • BTADS0072I Successfully received response from agent for job value with request id value .
      • BTADS0073E Received error response from agent for job value with request id value. Return code is value.
      • BTADS0074E IP Scan Discovery was canceled due to a hung socket/thread detected. Partial result of the scan will be persisted.
      • BTADS0075E IP Scan Discovery was canceled due to a hung socket/thread detected.
      • BTADS0076I IP Scan Discovery has started for DS, XIV, and IBM SONAS subsystems.
      • BTADS0077I Scanning value out of value IP addresses.
      • BTADS0078I IP Scan Discovery has started for SVC subsystems.
      • BTADS0079I IP Scan Discovery for DS and XIV was done.
      • BTADS0080I IP Scan Discovery for SVC was done
      • BTADS0081I Inband Scanner value for agent address value is not required for probing switches and will not be used.
      • BTADS0082W A first run of a switch probe failed. Additional agents will be used.
      • BTADS0084I There are no limitations for probing switch value based on the mix of agents that are configured.
      • BTADS0085W A problem was encountered when agent assignments were being determined for the probe. All available agents will be used to collect information about the switch.
      • BTADS0086I The following storage systems were discovered value
      • BTADS0087I IP Scan Discovery did not find any DS8000, SVC, XIV, and IBM SONAS storage systems in the given IP range.
      • BTADS0088I IP Scan Discovery finished.
      • BTADS0089E The Device server is not registered with agent manager. Scanners cannot be used for agent value. value.
      • BTADS0090E There are no agents currently available to probe switch value.
      • BTADS0091I Inband Scanner value for agent address value is currently not running and will not be used.
      • BTADS0092I Inband Scanner value for agent address value is currently disabled from performing fabric functions and will not be used.
      • BTADS0093I Inband Scanner value for agent address value is currently not reachable and will not be used.
      • BTADS0094W The probe for switch value has some limitations.
      • BTADS0095W For switch value some information will not be collected.
      • BTADS0096I The probe limitation can be overcome by configuring an SMI agent to manage fabric value.
      • BTADS0097I The probe limitation can be overcome by configuring SNMP agents to manage switches in fabric value.
      • BTADS0099W The following WWN is not recognized as belonging to a known vendor: value.
      • BTADS0100W Invalid relationships between switches and fabrics were identified. If possible, these relationships will be fixed automatically for the following switches: value.
      • BTADS0101W The discover process that has the Device server run ID value and job ID value completed with one or more warnings.
      • BTADS0102E The probe with the run ID value completed with errors.
      • BTADS0103E No data source is available to probe switch switch_name.
      • BTADS0104E A timeout occurred while processing the request. Try the request again.
      • BTADS0105E A response from the data collector was not received within the specified time.
      • BTADS0106E The requested action on agent agent_name did not complete because the data collector stopped or is not responding. The request failed with error code error_code.
      • BTADS0107W Outband Scanner outband_scanner_name on agent agent_name failed because of another transaction in progress on the switch.
      • BTADS0108E Outband Scanner outband_scanner_name on agent agent_name failed because unexpected data was returned by the switch. Check the trace file for more details.
      • BTADS0109I Outband Scanner outband_scanner_name on agent agent_name did not collect zoning data.
      • BTADS0110I Outband Scanner outband_scanner_name on agent agent_name did not pass write capabilities check.
      • BTADS0111E The probe was unable to collect some details of the switch.
      • BTADS0112E Error encountered while persisting some data. value
      • BTADS0113E Error encountered while processing a probe job. value
      • BTADS0114E The information cannot be saved to the database repository.
      • BTADS0115E The probe failed when collecting information about the resource. The data collector returned the following error status: value.
      • BTAFM0000I Operation op_name processed successfully.
      • BTAFM0100I Initializing Collection.
      • BTAFM0110I Querying the SMI-S provider.
      • BTAFM0113I Collecting for db_table, current_obj of num_objs.
      • BTAFM0114I Probing data for switch switch_name.
      • BTAFM0115I Probing data for port port_name.
      • BTAFM0150I Storing Information.
      • BTAFM0151I The db_table of current_obj num_objs stored.
      • BTAFM0200I Traversing fabric topology.
      • BTAFM0500I The IBM Spectrum Control Device Server service has started successfully.
      • BTAFM0501I The IBM Spectrum Control Device Server service was shut down successfully.
      • BTAFM0502I The IBM Spectrum Control Device Server service provides methods to collect, report and configure the fabric hardware.
      • BTAFM0505I The delete missing function has started.
      • BTAFM0506I The delete missing method was processed in milliseconds milliseconds.
      • BTAFM2000W Operation op_Name partially processed.
      • BTAFM2501W Unable to shut down Device Server Service smoothly.
      • BTAFM4000E Operation op_Name failed.
      • BTAFM4001E An internal error occurred.
      • BTAFM4002E Could not get requested information due to an internal error - errorMessage
      • BTAFM4100E Mandatory parameter parameter_Name is missing.
      • BTAFM4101E Invalid parameter parameter_name.
      • BTAFM4103E Entity entity_name was not found.
      • BTAFM4104E Attribute attribute_name was not found.
      • BTAFM4105E Computer computer_name was not found.
      • BTAFM4106E Fabric fabric_name was not found.
      • BTAFM4107E Switch switch_name was not found.
      • BTAFM4108E Port port_name was not found.
      • BTAFM4109E Zone set zoneset_name was not found.
      • BTAFM4110E Zone zone_name was not found.
      • BTAFM4111E Zone alias zone_alias_name was not found.
      • BTAFM4112E Zone member zone_member_name was not found.
      • BTAFM4113E Subsystem subsystem_name was not found.
      • BTAFM4114E Host Bus Adapter HBA_name was not found.
      • BTAFM4115E Node node_name was not found.
      • BTAFM4116E Link from port from_port_name to port to_port_name was not found.
      • BTAFM4117E Hub hub_name was not found.
      • BTAFM4118E Router router_name was not found.
      • BTAFM4119E Bridge bridge_name was not found.
      • BTAFM4120E LUN LUN_name was not found.
      • BTAFM4140E Agent Agent_name was not found.
      • BTAFM4141E Scanner scanner_name on agent agent_name was not found.
      • BTAFM4142W Agent agent_name was ignored because the switch switch_name was probed by agent agent1_name.
      • BTAFM4150E Indexed properties property_name don't match.
      • BTAFM4180E Agent to gather sensor and event data is not available for the switch switch_name.
      • BTAFM4200E Credentials not found.
      • BTAFM4300E The connection to the SMI agent for switch switch_name could not be made.
      • BTAFM4301E The invocation of CIM method method_name failed on SMI-S provider SMI-S provider name. The return code is return_code.
      • BTAFM4302E The invocation of CIM method method_name failed on SMI-S provider SMI-S provider name with the following exception text: exception_text.
      • BTAFM4303E Received unexpected values from SMI-S provider SMI-S provider name .
      • BTAFM4304E SMI agent SMI agent name can not contact switch switch_name.
      • BTAFM4305E The CIM method method_name is not supported on the switch switch_name.
      • BTAFM4306E Could not create connection to SMI-S provider SMI-S provider name . Reason: reason.
      • BTAFM4307E The username user_name or password is wrong on SMI-S provider SMI-S provider name.
      • BTAFM4308I Could not create connection to SMI-S provider SMI-S provider name . Reason: reason. An alternate SMI-S provider will be used.
      • BTAFM4501E No agent is available to configure the zoning on the fabric with ID fabric_name.
      • BTAFM4502E The fabric with ID fabric_name is currently locked by another client of IBM Spectrum Control.
      • BTAFM4503E A token for fabric fabric_name has expired for client client_name.
      • BTAFM4504E The transaction for fabric fabric_name has expired.
      • BTAFM4505E Another transaction is in progress for fabric fabric_name.
      • BTAFM4506E Zone set zoneset_name already exists.
      • BTAFM4507E Zone zone_name already exists.
      • BTAFM4508E Zone alias zone_alias_name already exists.
      • BTAFM4509E Zone member zone_member_name already exists.
      • BTAFM4510E Another job is in progress for fabric fabric_name.
      • BTAFM4550E The Device Server encountered an error accessing the database.
      • BTAFM4600E Unable to start the Device Server service.
      • BTAFM5000E Step failed after collecting Count of collected entities entities for switch switch where entities exist. Continuing with next step.
      • BTAFM5001E No set of fabrics or switches was defined for this probe.
      • BTAFM5002E The SMI agents SMIURL returned an error or can no longer contact the switches.
      • BTAFM5003E Requests to an SMI agent did not correctly collect a set of switches for fabric fabric identity.
      • BTAFM5004E No switch retrieved from the SMI agent for fabric fabric identity.
      • BTAFM5005E No switch found for fabric fabric identity.
      • BTAFM5006E No switch retrieved from database.
      • BTAFM5007E Failed to get CIM entity for fabric fabric_name.
      • BTAFM5008E Failed to get CIM entity for switch switch_name.
      • BTAFM5009E Failed to enumerate CIM entity Entity class name.
      • BTAFM5010E SMI-S provider is not available.
      • BTAFM5011E Failed to get blade for switch Switch name.
      • BTAFM5012E Failed to get physicalpackage for blade with slot number Blade slot name.
      • BTAFM5013E Blade serial number is NULL.
      • BTAFM5014E Step failed after collecting Count of collected entities entities for fabric fabric where entities exist. Continuing with next step.
      • BTAFM5015E Data source could not be retrieved from the IBM Spectrum Control database for fabric fabric where data source exists.
      • BTAFM5016E The selected data source could not be contacted for fabric fabric where data source exists.
      • BTAFM5017E Failed to get fabric for switch Switch name.
      • BTAFM5018E Failed to get CIM entity for port port_name.
      • BTAFM5019E Failed to get switch for port port_name.
      • BTAFM5020E Failed to get blade for port port_name.
      • BTAFM5021E Failed to get CIM entity for blade blade_name.
      • BTAFM5022E Failed to get switch for blade blade_name.
      • BTAFM5023E Failed to discover Fabric and Switch.
      • BTAFM5024E The data source for switch switch_name was not retrieved from the database repository.
      • BTAFM0600I Count of collected entities blades collected for switch switch where entities exist.
      • BTAFM0601I Starting collection of switch blades for switch switch identifier.
      • BTAFM0602I Collection of switch blades completed. Count of collected entities entities collected in total for switch switch identifier.
      • BTAFM0603I Starting collection of switch fcports for switch switch identifier.
      • BTAFM0604I Collection of switch fcports completed. count of collected entities entities collected in total for switch switch identifier.
      • BTAFM0605I Start probing switch entities switches.
      • BTAFM0606I Start topology probing for fabric fabric entity.
      • BTAFM0609I Count of entities fcports collected for switch switch where entities exist.
      • BTAFM0614I The probe task is to probe topology and zone. The probe algorithm is CIM association.
      • BTAFM0616I The probe policy involves discovering segmented or merged fabrics.
      • BTAFM0617I The probe policy doesn't involve discovering segmented or merged fabrics.
      • BTAFM0618I The probe task is to probe topology. The probe algorithm is CIM association.
      • BTAFM0620I Start zone probing for fabric fabric entity.
      • BTAFM0621I Starting collection of zone set for switch switch entity.
      • BTAFM0622I Starting collection of zone for switch switch entity.
      • BTAFM0623I Starting collection of zone alias for switch switch entity.
      • BTAFM0624I Starting collection of zone member from zone alias for switch switch entity.
      • BTAFM0625I Starting collection of zone member and zone alias from zone for switch switch entity.
      • BTAFM0626I Starting collection of zone member from zone for switch switch entity.
      • BTAFM0627I Starting collection of zone set for fabric fabric entity.
      • BTAFM0628I Count of collected entities zone sets collected.
      • BTAFM0629I Collection of zone set completed. Count of collected entities entities collected in total for fabric fabric entity.
      • BTAFM0630I Starting collection of zone for fabric fabric entity.
      • BTAFM0631I Count of collected entities zones collected.
      • BTAFM0632I Collection of zone completed. Count of collected entities entities collected in total for fabric fabric entity.
      • BTAFM0633I Starting collection of zone alias for fabric fabric entity.
      • BTAFM0634I Count of collected entities zone aliases collected.
      • BTAFM0635I Collection of zone alias completed. Count of collected entities entities collected in total for fabric fabric entity.
      • BTAFM0636I Starting collection of zone member from zone alias for fabric fabric entity.
      • BTAFM0637I Starting collection of zone member and zone alias from zone for fabric fabric entity.
      • BTAFM0638I Starting collection of zone member from zone for fabric fabric entity.
      • BTAFM0639I Collection of zone member completed. Count of collected entities entities collected in total for fabric fabric entity.
      • BTAFM0640I Zone probe will discover both active and inactive zone definitions at selected data source datasource name for zone probe.
      • BTAFM0641I Zone probe will discover only active zone sets at data source datasource name for zone probe.
      • BTAFM0654I The port is not switch port.
      • BTAFM0655I The switch profile doesn't support this switch switch_name. No further process to probe this switch.
      • BTAFM0656I Start enumerating entity of association between fabric and zone set at selected data source Url entity.
      • BTAFM0657I Start enumerating entity of association between fabric and zone at selected data source Url entity.
      • BTAFM0658I Start enumerating entity of association between fabric and zone alias at selected data source Url entity.
      • BTAFM0659I Start enumerating entity of association between switch and zone set at selected data source Url entity.
      • BTAFM0660I Start enumerating entity of association between switch and zone at selected data source Url entity.
      • BTAFM0661I Start enumerating entity of association between switch and zone alias at selected data source Url entity.
      • BTAFM0662I Start enumerating associations between virtual fabric and zoning entities at selected data source Url entity.
      • BTAFM0663I Starting collection of switch control processor blades for switch switch identifier.
      • BTAFM0664I Count of collected entities control processor blades collected for switch switch where entities exist.
      • BTAFM0665I Collection of switch control processor blades completed. Count of collected entities entities collected in total for switch switch identifier.
      • BTAFM0666I Checksums for the active and defined Zone Database could not be updated for fabric entity.
      • BTAFM0669I job id with request id was is not found. Device server may have been restarted after job was created.
      • BTAFM0670E could not retrieve output file for job id with request id .
      • BTAFM0671E Another probe of fabric The Name+Nameformat of the fabric is already in progress.
      • BTAFM0672E Device server is not registered with agent manager. Will not be able to invoke scanner on host .
      • BTAFM0673E There are no agents that are currently available to probe fabric .
      • BTAFM0674W No fabric found for event source that is associated with switch with IP address .
      • BTAFM0677E Unable to connect to SNMP port (another application may already be connected and forwarding messages).
      • BTAFM0678I The Name of the switch switch was removed.
      • BTAFM0679I The The Name+Nameformat of the fabric fabric was removed.
      • BTAFM0680E The Name of the switch switch was not removed because it is not missing.
      • BTAFM0681E The The Name+Nameformat of the fabric fabric was not removed because it is not missing.
      • BTAFM0682E An error occurred while checking for access to the database to save new zoning information for fabric to the database.
      • BTAFM0683E Unable to access the database to save zoning information for fabric . Another job is currently saving new zoning information to the database for the same fabric.
      • BTAFM0684I The job is waiting to access the database to save new zoning information for fabric . Another job is currently saving zoning information to the database for the same fabric.
      • BTAFM0685W Host/IP Address is not a switch.
      • BTAFM0686W Switch is not a supported switch.
      • BTAFM0687W The switch does not respond to SNMP queries.
      • BTAFM0688W Cannot communicate with host or IP address .
      • BTAFM0689W No ports were discovered for the switch .
      • BTAFM0690I Collection of data from trunks is completed. Data was collected from count of collected entities trunks.
      • BTAFM0691I Starting collection of data from trunks for switch switch identifier.
      • BTAFM0692I Count of entities trunks collected for switch switch where entities exist.
      • BTAFM0692E A response from the data collector was not received within the specified time.
      • BTAFM0693E A response from the data collector was not received. The request failed with return code return_code
      • BTAFM0694W Zoning data cannot be collected because there is a transaction in progress on the switch key
      • BTAFM0695E The switch key is returning unexpected data.
      • BTAFM0696E Zone set zoneset_name is already active.
      • BTAFM0697E Zone set zoneset_name is already inactive.
      • BTAFM0698E On the switch switch_name VSAN vsan_name was not found.
      • BTAFM0699E The switch key did not return zoning data.
      • BTAFM0700E Duplicate entries for the same switch: switch.
      • BTAFM0701E Current active full zone configuration is not synchronized with the zone configuration on the switch switch_name for VSAN vsan_name .
      • BTAFM0702E You cannot monitor Brocade Access Gateway switches without Network Advisor.
      • BTAFM0703I Waiting for probes of other Access Gateway switches to complete.
      • BTAFM0704W Distributing zone configuration across all the switches for VSAN vsan_name did not succeed on the switch switch_name .
      • BTAFM0705W Zone data collection after zone changes were made failed on the switch switch_name .
      • BTAFM0706E The fabric probe was unable to collect some details of the blades on the switches.
      • BTAFM0707I You cannot use IBM Spectrum Control to make zoning changes for provisioning on switch switch_name.
      • BTAFM0708E The probe was unable to collect some details of the switches.
      • BTAQE1107E InbandScanHandler failed to start InbandScanner scanner name on managed host target.
      • BTAQE1108E InbandScanHandler failed to get callback information for InbandScanner scanner name on managed host target.
      • BTAQE1112E During an outband scan, the scanner scanner name was unable to identify the target host target.
      • BTAQE1113E Unable to invoke an Outband scan scanner name on target target.
      • BTAQE114E OutbandScannerHandler received invalid callback information for Outband scanner scanner name on target target.
      • BTAQE1115E The outband scanner scanner name did not return the SAN ID on target target.
      • BTAVM0001I The operation Name of the operation processed successfully.
      • BTAVM0002I The Web service call Name of the operation processed successfully.
      • BTAVM0003I Data source Name of the datasource successfully added.
      • BTAVM0004I Data source Name of the datasource successfully deleted.
      • BTAVM0005I Data source Name of the datasource successfully modified.
      • BTAVM0006I Discovery on data source Name of the datasource has started.
      • BTAVM0007I Discovery on data source Name of the datasource completed successfully.
      • BTAVM0008I Probe of hypervisor Name of the Hypervisor has started.
      • BTAVM0009I Probe of hypervisor Name of the Hypervisor completed successfully.
      • BTAVM0010I A connection test to data source Name of the data source has started.
      • BTAVM0011I The Connection test to data source Name of the data source completed successfully.
      • BTAVM0012I Hypervisor Name of the Hypervisor discovered/rediscovered.
      • BTAVM0013I Discovery: Hypervisor Name of the hypervisor will not be discovered as it is managed by another data source.
      • BTAVM0014I Discovery: Hypervisor Name of the hypervisor will not be discovered as it itself is registered as a data source.
      • BTAVM0015I Collection of the physical storage configuration for hypervisor Name of the hypervisor has started.
      • BTAVM0016I Collection of the physical storage configuration for hypervisor Name of the hypervisor completed successfully.
      • BTAVM0017I Collection of the logical storage configuration for hypervisor Name of the hypervisor has started.
      • BTAVM0018I Collection of the logical storage configuration for hypervisor Name of the hypervisor completed successfully.
      • BTAVM0019I Collection of the virtual machines configuration for hypervisor Name of the hypervisor has started.
      • BTAVM0020I Collection of the virtual machines configuration for hypervisor Name of the hypervisor completed successfully.
      • BTAVM0021I The probe of name of the hypervisor found number of physical disks physical disks.
      • BTAVM0022I The probe of name of the hypervisor found number of logical volumes logical volumes.
      • BTAVM0023I The probe of name of the hypervisor found number of virtual machines virtual machines.
      • BTAVM0024I The Name of the hypervisor hypervisor was removed.
      • BTAVM0025I VMWare Cluster Name of the Cluster discovered/rediscovered.
      • BTAVM1301I The probe of name of the hypervisor could collect partial information only for the disk with the device name Device name of the disk.
      • BTAVM1302I LUN correlation is not supported for disk with device name Device name of the disk, vendor: Vendor name, model: model name, for hypervisor hypervisor name.
      • BTAVM1503E An internal error occurred: Text describing the internal error.
      • BTAVM2001E The mandatory parameter Name of the mandatory parameter which is missing is missing.
      • BTAVM2002E Invalid parameter Name of the parameter which was invalid.
      • BTAVM2003E A database error was encountered during database query or insert.
      • BTAVM2004E Cannot connect to the database repository.
      • BTAVM2006E The operation Name of the operation that failed failed for the following reason: Reason of the failure.
      • BTAVM2007E The Web service call Name of the operation failed for the following reason: Reason of the failure.
      • BTAVM2008E The product Name of the unsupported product is not supported.
      • BTAVM2010E The user name or password is invalid for Address of the host
      • BTAVM2011E The operation Name of the timed out operation could not complete within the time limit of Timeout threshold in milliseconds milliseconds.
      • BTAVM2012E An error occurred while trying to establish secure communication over SSL.
      • BTAVM2013E The Add Device wizard could not add the Name of the data source data source.
      • BTAVM2014E The deletion of data source Name of the data source failed.
      • BTAVM2015E The modification of data source Name of the data source failed.
      • BTAVM2016E Discovery on data source Name of the datasource failed.
      • BTAVM2017E Probe of the hypervisor Name of the Hypervisor failed.
      • BTAVM2018E IBM Spectrum Control can't connect to the data source Name of the datasource.
      • BTAVM2201E Probe: An error occurred during the collection of the physical storage configuration.
      • BTAVM2202E Probe: An error occurred during the collection of the logical storage configuration.
      • BTAVM2204E Probe: An error occurred during the collection of the virtual machine configuration.
      • BTAVM2206E Discovery: the hypervisor Name of the hypervisor will not be discovered because its version is not supported.
      • BTAVM2207E Calculation of the summary data for the hypervisor Name of the hypervisor failed.
      • BTAVM2208E Unable to obtain the hypervisor version(s) from the datasource Name of the datasource.
      • BTAVM2209E Unable to obtain information about other Virtual Centers managing the hypervisor(s) of datasource Name of the datasource.
      • BTAVM2210W Error getting LUN definition data for the disk with the device name Device name of the disk, storage subsystem vendor: Vendor name, model: model name, for hypervisor hypervisor name.
      • BTAVM2211E Probe: Virtualization Manager failed to get the VMWare VI data source for the hypervisor Name of the hypervisor from the database.
      • BTAVM2212E Probe: The hypervisor Name of the hypervisor is not available on the VMWare VI datasource Name of the datasource.
      • BTAVM2213E Data source Name of the datasource is disconnected from Virtual Center.
      • BTAVM2214E The probe job encountered an NFS file system while probing ESX server {0}. IBM Spectrum Control currently does not support probes of ESX servers with NFS file systems. The probe job for this ESX server has been stopped. Probes of other ESX servers that are included in this probe job will continue.
      • BTAVM2215W Unsupported storage subsystem disk with device name Device name of the disk, vendor: Vendor name, model: model name, for hypervisor hypervisor name with hypervisor version less than 3.5.0.
      • BTAVM2216E Unable to get keystore instance.
      • BTAVM2217E Unable to load keystore file.
      • BTAVM2218E Unable to set certificate entry in keystore file.
      • BTAVM2219E Unable to open keystore for writing.
      • BTAVM2220E Unable to close keystore file.
      • BTAVM2221E Unable to acquire lock on keystore file.
      • BTAVM2222E Unable to store certificate in keystore file.
      • BTAVM2223E Unable to release lock on keystore file.
      • BTAVM2224E Unable to decrypt keystore password.
      • BTAVM2225E Unable to open keystore for reading.
      • BTAVM2226E Certificate already exists in keystore.
      • BTAVM2227E host_address hypervisor is already being monitored and could not be added.
      • BTAVM2228E Missing host name.
      • BTAVM2229E Missing certificate.
      • BTAVM2230E Cannot create keystore directory.
      • BTAVM2231E Cannot download the certificate from Data Source Name of the data source.
      • BTAVM2232E Cannot connect to the Name of the data source data source.
      • BTAVM2233E Cannot download the certificate from the port.
      • BTAVM2234E The hypervisor name hypervisor was not removed because IBM Spectrum Control is running other actions on the device.
      • BTAVM2235E Unable to obtain the cluster(s) from the datasource Name of the datasource.
      • BTAVM2236W Subsequent steps of probe process may not be able to collect data for the hypervisor Name of the hypervisor because the hypervisor is in critical state.
      • BTAVM2237E Datastore Browser Task failed for hypervisor Name of the hypervisor, datastore Name of the datastore with error: Error
      • BTAVM2238E The registration of the vSphere Web Client extension for IBM Spectrum Control has started on Name of the vCenter server.
      • BTAVM2239E The registration of the vSphere Web Client extension for IBM Spectrum Control did not extract the extension package.
      • BTAVM2240E The registration of the vSphere Web Client extension for IBM Spectrum Control did not complete while updating the VASA web archive file, vasa.war, with the IBM Spectrum Control server configuration.
      • BTAVM2241E The registration of the vSphere Web Client extension for IBM Spectrum Control completed.
      • BTAVM2242E Unable to register IBM Spectrum Control as an extension on the vCenter server Name of the vCenter server. The validation of input values did not complete.
      • BTAVM2243E Unable to register IBM Spectrum Control as an extension on the vCenter server Name of the vCenter server. Could not authenticate with the vCenter server.
      • BTAVM2244E The registration of the vSphere Web Client extension for IBM Spectrum Control did not complete.
      • BTAVM2245E Unable to connect to the vCenter Server Name of the datasource.
      • BTAVM2246E Unable to configure the vCenter Server.
      • BTAVM2247E The registration of the vSphere Web Client extension for IBM Spectrum Control did not delete the temporary directory Name of the directory.
      • BTAVM2248E The registration of IBM Spectrum Control as a VASA provider did not complete.
      • BTAVM2249E Automatic registration of IBM Spectrum Control as a VASA provider is not supported for vCenter Server version 5.0 and earlier.
      • BTAVM2250E IBM Spectrum Control is already registered as a VASA provider for vCenter Server server_name. Register IBM Spectrum Control as a VASA provider manually in the vSphere Web Client to update the credentials.
      • BTAVM2251E One or more third-party VASA providers are already registered with the vCenter Server. IBM Spectrum Control VASA provider was not registered. Register IBM Spectrum Control as a VASA provider manually.
      • BTAVM2252E The registration of IBM Spectrum Control as a VASA provider has started on Name of the vCenter server.
      • BTAVM2253E The registration of IBM Spectrum Control as a VASA provider has completed.
      • BTAVM2254E The registration of the vSphere Web Client extension for IBM Spectrum Control did not complete. The current session is invalid.
      • BTAVM2255E The registration of IBM Spectrum Control as a VASA provider did not complete. The current session is invalid.
      • BTAVM2256W Could not determine the host for VM with ID: host id and Name: Vendor name. Check if the same mac address is used on other computers.
      • BTAVM2257I Found number of files files on name of datastore of name of the hypervisor.
      • BTAVM2258I The probe of name of the hypervisor found number of controllers controllers.
      • BTAVM2259I Collecting file system details for hypervisor Name of the hypervisor.
      • BTAVM2260I Collecting list of files for hypervisor Name of the hypervisor.
      • BTAVM2261I Collecting logical volumes for hypervisor Name of the hypervisor.
      • BTAVM2262I Collecting disk partition for hypervisor Name of the hypervisor.
      • BTAVM2263I Files details for Name of the datastore being collected by id of the Hypervisor.
      • BTAVM2264I Files details for Name of the datastore were collected by id of the Hypervisor on timestamp.
      • BTAVM2265E Invalid host name or IP address.
      • BTAVM2266E The connection information cannot be updated because it points to another device.
      • BTAVM2268E The connection information cannot be updated because IBM Spectrum Control cannot determine if the hypervisor is managed by the Name of the data source data source.
      • BTAVM2269E The connection information cannot be updated because a data source with this host name or IP address is already present.
      • BTAVM2270E The connection information cannot be updated because it doesn't point to a data source of the same type (vCenter/ESX).
      • BTAVM2271W The hypervisor Name of the Hypervisor cannot be discovered because its connection state is "Connection State".
      • BTAVM2272E The user User Name does not have the privilege to browse the datastore Name of the Datastore.
      • HWN020001I Operation Name of the operation processed successfully.
      • HWN020002E Mandatory parameter Name of the mandatory parameter which is missing missing
      • HWN020003E Invalid parameter Name of the parameter which was invalid
      • HWN020101E The external process terminated unexpected.
      • HWN020102W The external process was canceled per users request.
      • HWN020103E The external process exceeded the timeout limit and was canceled.
      • HWN020104E The external process could not be started.
      • HWN020105E The data collector is not responding to the server.
      • HWN020106E An external process was cancelled by the data collector.
      • HWN021503E The action cannot be completed
      • HWN021504E Entity The ID of the entity was not found.
      • HWN021508E Credentials not found
      • HWN021514E The invocation of CIM method Name of method failed on SMI-S provider Name of SMI-S provider . The return code is Return code of method
      • HWN021515E The invocation of CIM method Name of method failed on SMI-S provider Name of SMI-S provider with the following exception text: Exception text
      • HWN021516E The LSS specified LSS name on subsystem Name of subsystem is already at the maximum volume number (255). Volume creation can not be done on this LSS, please select a different one.
      • HWN021517E The connection to SMI-S provider for storage system VPD of the storage system could not be made.
      • HWN021520E The attribute Name of the attribute was not found.
      • HWN021522E Host port The WWPN of the host port not assigned to Volume The PK of the volume
      • HWN021524E Indexed Properties Names don't match
      • HWN021529E An SMI-S provider has reported unexpected values: IP and port of SMI-S provider.
      • HWN021530E The Volume - Port mapping can not be created. There are existing mappings that prevent this combination. VolumeCOP: The ID of the volume , Port: The WWPN of the port that should be mapped to the volume
      • HWN021531E SMI-S provider The IP and port of the SMI-S provider can not reach storage system The VPD of the storage system
      • HWN021535E There is not enough space left in the storage pool The primary key of the Poolon storage system The VPD of the storage system to create a volume of The requested volume size bytes.
      • HWN021536E The CIM method The CIM method that is not supported. is not supported on the storage system The VPD of the storage system
      • HWN021537E Could not create connection to SMI-S provider The IP and port for the SMI-S provider..Reason: The exception returned by the SMI-S provider.
      • HWN021538E The username The username that was used to connect to the SMI-S provider. or password is wrong on SMI-S provider The IP and port for the SMI-S provider.
      • HWN021539E The SVC with IP The IP of the SVC. which is managed by SMI-S provider The IP and port for the SMI-S provider. can not be discovered. The status is The status of the SVC. .
      • HWN021540E The invocation of CIM method Name of method failed on SMI-S provider Name of SMI-S provider . The return code is Return code of method. Details provided by the SMI-S provider : Description of Returncode
      • HWN021600W Operation Name of the operation. partially processed.
      • HWN021601E The operation(s) Operation_names failed.
      • HWN021602E It is necessary to specify target ports for storage device VPD of the storage subsystem
      • HWN021603W More storage volumes and ports than specified will loose access
      • HWN021604E WWPNs and storage volumes to be unassigned not completely specified. Assigned WWPNs: All WWPNs that are assigned to the volumes in the host port collection , missing WWPNs: The WWPNs that are assigned but were not specified in the input parameter in the method unassign . Storage volumes to be unassigned not completely specified. Assigned storage volumes: Lists all storage volumes that are really assigned to the WWPNs. }, missing storage volumes: The storage volumes that are really assigned but were not specified in the input parameter in the method unassign
      • HWN021605I More storage volumes and ports than specified will gain access.
      • HWN021606E WWPNs and storage volumes to be assigned not completely specified. Missing WWPNs: The WWPNs that need to be assigned but were not specified in the input parameter. . Storage volumes to be assigned not completely specified. Missing storage volumes: The storage volumes that need to be assigned but were not specified in the input parameter.
      • HWN021607E The client type the client type with description the client description is not supported on SMI-S provider the SMI-S provider IP and port for storage subsystem the subsystem IDof volumes the volumeIDs of the subsystem which were passed in
      • HWN021608E The target port the target port ID does not belong to storage subsystem the subsystem ID of volumes the volumeIDs of the subsystem which were passed in
      • HWN021609E There is not enough space left in the storage pool The primary key of the Pool on storage system The VPD of the storage system to create The number of volumes to create volumes of The total size needed bytes total.
      • HWN021610E The specified size The size of the volume to create is not supported on pool The storage pool ID Size has to be dividable by Divisor returned by getSupportedSizeRange and in between Minimum returned by getSupportedSizeRange and Maximum returned by getSupportedSizeRange
      • HWN021611E Volume The volume ID has mappings, it can not be deleted.
      • HWN021612E The mapping between volume The volume ID and port The initiator port wwpn exists already
      • HWN021613E The WWPN The WWPN not found can not be found on subsystem The subsystem
      • HWN021614E The WWPNs The WWPNs without mappings have no mappings on storage system The storage system
      • HWN021615E WWPNs WWPNs that can not share mappings can not share mappings on storage system Storage system}. There are existing mappings that prevent this.
      • HWN021616E Volumes VolumeIDs can not share mappings on storage system Storage system }. There are existing mappings that prevent this.
      • HWN021617E The stored data for storage system The storage system is not in sync with the environment. Rerun data collection.
      • HWN021618E Modifying target ports is not supported by subsystem the subsystem .
      • HWN021619E Modifying the target ports for mapping of initiator port initiator port WWPN and volume volume name will also modify the target ports of the following mappings: port - volume list
      • HWN021620I Modifying the target ports for mapping of initiator port initiator port WWPN and volume volume name will modify the target ports of more mappings than specified.
      • HWN021621E It is not supported to modify the target ports of existing mappings and create new mappings in one step. Modify the existing mappings first and then create the new mappings. Existing mappings: port - volume list
      • HWN021622I Started modification of the assignment of volume VolumeID on subsystem Subsystem to initiator port WWPN . Target ports to add: target ports to add Target ports to remove: target ports to remove
      • HWN021623I Finished modification of the assignment of volume VolumeID on subsystem Subsystem to initiator port WWPN . Target ports to add: target ports added Target ports to remove: target ports removed
      • HWN021624E The modification of the assignment of volume VolumeID on subsystem Subsystem to initiator port WWPN failed. Target ports to add: target ports to add Target ports to remove: target ports to remove
      • HWN021650E A timeout occurred while connecting to SMI-S provider SMI-S provider IP and port.
      • HWN021651E Job on SMI-S provider SMI-S provider IP and Port in format IP:Port failed. Job Status: Job status . Error code is Error code , error description: Error description . Check IBM Spectrum Control and SMI-S provider logs.
      • HWN021652E The process has timed out. Check the IBM Spectrum Control log files for more information.
      • HWN021653E The attribute Name of the attribute was not found.
      • HWN021654E Pool ID was not found.
      • HWN021655E Volume ID The ID of the volume was not found.
      • HWN021656E Port ID The ID of the port was not found.
      • HWN021657E Subsystem ID The ID of the subsystem was not found.
      • HWN021658E Managed Disk ID The ID of the MDisk was not found.
      • HWN021659E SMI-S provider The ID of the SMI-S provider was not found
      • HWN021660E IO Group The SVC IO Group was not found.
      • HWN021661E Extent The storage extent external key was not found.
      • HWN021662E Physical volume The physical volume external key was not found.
      • HWN021670E The client type the client type with description the client description is not unique on SMI-S provider the SMI-S provider IP and port } for storage subsystem the subsystem ID of volumes the volumeIDs of the subsystem which were passed in
      • HWN021671I The storage system The storage system was deleted from the database
      • HWN021672E The storage system name storage system was not removed because other monitoring actions are running on the device.
      • HWN021673E The probe job on SMI-S provider SMI-S provider IP and Port in format IP:Port did not complete within the time limit of Microseconds microseconds. The job is Percent complete percent complete. Check the SMI-S provider log for job status. Job information: JobCOP . Run the probe job again after the current job has completed.
      • HWN021674E Job on SMI-S provider SMI-S provider IP and Port in format IP:Port returned unexpected results. Job information: JobCOP Job status: JobState , status description: JobStatus Check SMI-S provider log. Redo probe if the job completed.
      • HWN021675I Started creation of volume with size Size in pool Pool on subsystem Subsystem
      • HWN021676I Volume creation completed successfully. New volume VolumeID created with size Size in pool Pool on subsystem Subsystem .
      • HWN021677E Volume creation failed. The volume of size Size in pool Pool on subsystem Subsystem could not be created.
      • HWN021678I Started assignment of volume VolumeID on subsystem Subsystem to initiator port WWPN .
      • HWN021679I Finished assignment of volume VolumeID on subsystem Subsystem to initiator port WWPN .
      • HWN021680E The assignment of volume VolumeID on subsystem Subsystem to initiator port WWPN failed.
      • HWN021681I Started unassignment of volume VolumeID on subsystem Subsystem to initiator port WWPN .
      • HWN021682I Finished unassignment of volume VolumeID on subsystem Subsystem to initiator port WWPN .
      • HWN021683E The unassignment of volume VolumeID on subsystem Subsystem to initiator port WWPN failed.
      • HWN021684I Started deletion of volume VolumeID on subsystem Subsystem .
      • HWN021685I Volume deletion completed successfully. Volume VolumeID on subsystem Subsystem was deleted.
      • HWN021686E Volume deletion failed. Volume VolumeID on subsystem Subsystem could not be deleted.
      • HWN021687I Started modification of Pool Pool display name on subsystem Subsystem display name .
      • HWN021688I Pool modification completed successfully. Pool Pool display name on subsystem Subsystem display name was modified.
      • HWN021689E Pool modification failed. Pool Pool display name on subsystem Subsystem display name could not be modified.
      • HWN021690I Started creation of number volumes volumes with size Size in pool Pool on subsystem Subsystem
      • HWN021691I Created number volumes out of total number volumes volumes with size Size in pool Pool on subsystem Subsystem
      • HWN021692E Volume creation failed. Created number volumes out of total number volumes volumes with size Size in pool Pool on subsystem Subsystem
      • HWN021693W Warning: The task succeeded, but the database update failed. Run probe to update the database.
      • HWN021700I Enumerating CIM Associator The CIM association name which is being enumerated. for The name of the DB table which will be populated as result of this query.
      • HWN021701I Enumerating CIM Class The CIM class name which is being enumerated. for The name of the DB table which will be populated as result of this query.
      • HWN021702I Querying SMI-S provider
      • HWN021703I Task starting on SMI-S provider Identifier of the SMI-S provider..
      • HWN021708I Initializing Collection for storage system storage system identification.
      • HWN021709I Collection for storage system storage system identification completed.
      • HWN021710I Discovering devices for SAN Volume Controller The VPD of the SAN Volume Controller.
      • HWN021711I Discovery devices for SAN Volume Controller The VPD of the SAN Volume Controller. failed with error message The exception which has occurred.
      • HWN021712I Collecting Nodes for storage system storage system identification.
      • HWN021713I Collecting fibre channel ports for storage system storage system identification.
      • HWN021714I Collecting volumes for storage system storage system identification.
      • HWN021715I Traversing host to volume assignments for storage system storage system identification.
      • HWN021716I Collecting pools and volumes for storage system storage system identification.
      • HWN021717I Collecting volume settings for storage system storage system identification.
      • HWN021718I Collecting client setting data for storage system storage system identification.
      • HWN021719I Perform collection post process tasks for storage system storage system identification.
      • HWN021720I Flash enclosure is missing drive flash_drive_ identifier.
      • HWN021724W SMI-S provider SMI-S provider identifier manages device(s) of type device_type which is supported through the native device interface or SNMP only.
      • HWN021725I IBM Spectrum Control discovered/rediscovered a device with name Identifier of the device. on SMI-S provider Identifier of the SMI-S provider..
      • HWN021726I IBM Spectrum Control discovered/rediscovered no device on SMI-S provider Identifier of the SMI-S provider..
      • HWN021727I IBM Spectrum Control discovery starting on SMI-S provider Identifier of the SMI-S provider..
      • HWN021728I IBM Spectrum Control discovery on SMI-S provider Identifier of the SMI-S provider. is complete.
      • HWN021729W IBM Spectrum Control discovery of Device type value is not supported.
      • HWN021730W IBM Spectrum Control discovery of device value with code level value is not supported on SMI-S provider Identifier of the SMI-S provider..
      • HWN021731I Probing Volumes for Storage System: value.
      • HWN021732I Number of Volumes Found Currently: value. Continuing to Probe Volumes.
      • HWN021733I value Volumes Found.
      • HWN021734I Probing Disks for Storage System: value.
      • HWN021735I Number of Disks Found Currently: value. Continuing to Probe Disks.
      • HWN021736I value Disks Found.
      • HWN021737I Probing Virtual Disks for Cluster: value
      • HWN021738I Number of Virtual Disks currently found: value. Continuing to probe Virtual Disks.
      • HWN021739I value Virtual Disks found.
      • HWN021740I Probing Views of Host Initiator access to Volumes.
      • HWN021741I value Views Found.
      • HWN021742E The SMI-S provider SMI-S provider URL is not managing storage subsystems.
      • HWN021743E The SMI-S provider SMI-S provider URL is not managing switches.
      • HWN021744E Cannot connect to a resource because of an SSL certificate error. Troubleshooting information: http://www.ibm.com/support/docview.wss?uid=swg21976237
      • HWN021745I Cannot connect to a resource because of an SSL certificate error. Troubleshooting information: http://www.ibm.com/support/docview.wss?uid=swg21976237. An alternate resource will be used.
      • HWN021746W SMI-S provider Identifier of the SMI-S provider. manages Cisco device types through SNMP only.
      • HWN021747E Unable to add the specified switch by using SNMP. The switch is a Brocade switch and can be added only by using an SMI agent.
      • HWN021800E Failed to get a database connection.
      • HWN021801E The server failed to get SMI-S provider entity from database.
      • HWN021802E Experienced SQL problems while working with database: The SQL error.
      • HWN021803W The server did not get userid and or password for SMI-S provider The Service URL of the SMI-S provider from database.
      • HWN021804E The server failed to access slp attributes for SMI-S provider The Service URL of the SMI-S provider from database.
      • HWN021805E CIMOMManager failed to get a database mapper of type The type of the database mapper.
      • HWN021806E CIMOMManager failed to get a valid mapper result from The type of the database mapper.
      • HWN021807E CIMOMManager failed to get a proxy for calling slp discovery.
      • HWN021808E The device cannot be contacted through any of the following SMI-S providers The comma separated list of IP and port for the SMI-S providers.. Possible causes are that the SMI-S providers are not accessible or the device is disconnected from the SMI-S providers.
      • HWN021809E The host for SMI-S provider The service URL of the SMI-S providers. was not resolvable in DNS.
      • HWN021810E The service URL for SMI-S provider The service URL of the SMI-S providers. is not valid.
      • HWN021811I The operational status for device The ID of the device. on SMI-S provider The service URL of the SMI-S provider. has this value The operational status vector. .
      • HWN021812E The operational status for device The ID of the device. on SMI-S provider The service URL of the SMI-S provider. could not be retrieved because SMI-S provider is in status The SMI-S provider connection status. .
      • HWN021813E Fabric ID The ID of the fabric was not found.
      • HWN021814E The device device id cannot be contacted through the SMI-S provider SMI-S provider service URL.
      • HWN021899E Switch The wwn of the switch. has no associated Fabric.
      • HWN021901E The virtual disk size cannot exceed maximum size when creating space efficient virtual disks.
      • HWN021902E Invalid grain size. Valid values are valid values.
      • HWN021903E Authentication to ip or name of host failed. Please specify correct authentication information.
      • HWN021904E Connection to IP address or name of host failed with following operating system exception: exception text . Please make sure IP address is correct and machine is up and running. If this is a SVC V4 machine, it could be that its RAS interface is not up. If this is a SVC V5, make sure the SMI-S provider is up and running.
      • HWN021905E Connection to IP address or name of host failed with following operating system exception: exception text .
      • HWN021906E Failed to get native API entity from database.
      • HWN021907E The IP address The service URL of the SMI-S providers. was not resolvable in DNS.
      • HWN021908E Failed to get a proxy for calling NAPI discovery.
      • HWN021909E There are no IO Groups available for Virtual Disk creation.
      • HWN021910E Managed Disk ID The ID of the MDisk is not in unmanaged mode and cannot be added to the specified managed-disk group.
      • HWN021911E Another probe of storage subsystem The Name+Nameformat of the storage subsystem is already in progress.
      • HWN021912E Other probes of storage subsystems The list of Name+Nameformat of the storage subsystems are already in progress.
      • HWN021913E IBM Spectrum Control Device Server could not write to directory The directory.
      • HWN021914E SSH key file The SSH key file name is still in use, so it cannot be deleted.
      • HWN021915E IBM Spectrum Control Device Server could not delete the file The file.
      • HWN021916E The storage subsystem subsystem ID is not configured for file level management.
      • HWN021917E An invalid parameter Name of the parameter which was invalid was specified. The corresponding file system mount point does not exist.
      • HWN021919E The cluster ID The ID of the cluster. was not found.
      • HWN021920E The export ID The ID of the export. was not found.
      • HWN021921E The specified activity or protocol could not be used to change the export The ID of the export..
      • HWN021922E The file system ID file_system_ID was not found.
      • HWN021923E Invalid parameter Name of the parameter which was invalid. File system does not exist.
      • HWN021924E The parameter Name of the parameter which was invalid is not a valid parameter.
      • HWN021925E The fileset ID fileset_ID was not found.
      • HWN021926E The WAN-cache source ID WAN_cache_source_id was not found.
      • HWN021927E The WAN-cache ID WAN_cache_source_id was not found.
      • HWN023000I The Optimization Execution task has started.
      • HWN023001E The task to optimize the volumes was not completed successfully.
      • HWN023002I The Optimization Execution task has completed.
      • HWN023003I The Optimization Execution task retrieved number recommendations
      • HWN023004I The Optimization Automation request persisted recommendations to be processed.
      • HWN023005I The Optimization Execution task updated the status of number recommendations.
      • HWN023006I The Optimization Automation request begins processing number recommendations.
      • HWN023007W The recommendation being processed contains a virtual disk that is no longer detected.
      • HWN023008W The recommendation for virtual disk vdisk name contains a source storage pool that is no longer detected.
      • HWN023009W The recommendation for virtual disk vdisk name contains a target storage pool that is no longer detected.
      • HWN023010I Virtual disk vdisk name was successfully migrated from storage pool source pool name to storage pool target pool name.
      • HWN023011W The recommendation for virtual disk vdisk name contains a virtual disk that does not exist in the source storage pool source pool name or the target storage pool target pool name.
      • HWN023012W The recommendation for virtual disk vdisk name contains a non-mirrored virtual disk that is now a mirrored virtual disk.
      • HWN023013W The recommendation for virtual disk vdisk name contains a mirrored virtual disk that is now a non-mirrored virtual disk.
      • HWN023014I The recommendation for virtual disk vdisk name requires more space on target pool target pool name to be processed.
      • HWN023015I Virtual disk vdisk name will now be migrated from storage pool source pool name to storage pool target pool name.
      • HWN023016I Successfully added virtual disk copy to virtual disk vdisk name.
      • HWN023017I Synchronization for virtual disk vdisk name has completed synchronization percent% and requires about seconds to complete seconds to complete.
      • HWN023018I Synchronization for virtual disk vdisk name has completed.
      • HWN023019I Successfully removed a virtual disk copy from virtual disk vdisk name.
      • HWN023020I Successfully changed the synchronization rate of virtual disk vdisk name to syncrate%.
      • HWN023021I Successfully changed the primary copy of virtual disk vdisk name.
      • HWN023022E There is no space available on target pool target pool name to migrate the virtual disk vdisk name.
      • HWN023023E Unable to submit request to add vdisk copy command for virtual disk vdisk name due to rc (rc).
      • HWN023024E Unable to complete request to add vdisk copy command for virtual disk vdisk name due to rc (rc).
      • HWN023025E Unable to submit request to get vdisk synchronization progress for virtual disk vdisk name due to rc (rc).
      • HWN023026E Unable to complete request to get vdisk synchronization progress for virtual disk vdisk name due to rc (rc).
      • HWN023027E Unable to submit request to remove vdisk copy command for virtual disk vdisk name due to rc (rc).
      • HWN023028E Unable to complete request to remove vdisk copy command for virtual disk vdisk name due to rc (rc).
      • HWN023029E Unable to submit request to change the synchronization rate for virtual disk vdisk name due to rc (rc).
      • HWN023030E Unable to complete request to change the synchronization rate for virtual disk vdisk name due to rc (rc).
      • HWN023031E Unable to submit request to change the primary copy for virtual disk vdisk name due to rc (rc).
      • HWN023032E Unable to complete request to change the primary copy for virtual disk vdisk name due to rc (rc).
      • HWN023033E The request failed. Message from failed request: message.
      • HWN023034E The Optimization Automation job completed with errors in the recommendations.
      • HWN023035W The Optimization Execution task completed with warnings.
      • HWN023036E The request failed because there were not enough extents in the storage pool.
      • HWN023037E The request failed because the number of copies of this volume would exceed the limit.
      • HWN023038E The request failed because the copy specified does not exist.
      • HWN023039E The following exception occurred during a migration request: exception
      • HWN023040E The migration request for volume vdisk name is already being processed.
      • HWN023041W The request to migrate the mirrored volume vdisk name is suspended because the secondary volume is offline.
      • HWN023042E The secondary copy needed for migration does not exist.
      • HWN023043I The mirrored volume migration for volume vdisk name will be ignored.
      • HWN023044I The mirrored volume migration for volume vdisk name will result in the current secondary volume becoming the primary volume.
      • HWN023045I The mirrored volume migration for volume vdisk name will result in the primary volume being migrated to the target pool.
      • HWN023046I The Migration of the previously abandoned Optimization Automation job has started.
      • HWN023047I The Migration of the previously abandoned Optimization Automation job has completed.
      • HWN023048I The Optimization Automation cancellation job jobname has started.
      • HWN023049E The Optimization Automation cancellation job completed with errors.
      • HWN023050I The Optimization Automation cancellation job jobname has completed.
      • HWN023051I The Optimization Automation job jobname will be canceled.
      • HWN023052W The Optimization Automation job is not in progress.
      • HWN023053I The migration of volume vdisk name has been canceled.
      • HWN023054W The Optimization Automation job was canceled.
      • HWN023055I The volume that was chosen for transformation, vdisk name, is a secondary volume in a mirrored volume relationship. The secondary volume will be migrated to the specified target pool or converted as specified.
      • HWN024000I An optimization analysis task was started.
      • HWN024001I The analysis is completed.
      • HWN024002W Unable to retrieve any policy for Tier value.
      • HWN024003I Analyzed number_of_volumes volumes on tier tier_number for storage virtualizer subsystem_name.
      • HWN024006W No target pools in subsystem value were selected.
      • HWN024011W Destination storage pool value in subsystem value was not considered. Reason: value.
      • HWN024012I It is recommended that number_of_volumes volumes on tier source_tier_number are moved to tier target_tier_number.
      • HWN024015I The optimization analysis of the value subsystem was started.
      • HWN024016W Volume value is already in the destination storage pool value. No recommendations will be generated for the volume.
      • HWN024018W No destination storage pools in Tier value have been specified for subsystem value.
      • HWN024019W The following pools on tier tier_number on the storage_system storage system cannot be balanced by redistributing or re-tiering volumes: pool_names.
      • HWN024020I Started analysis to balance pools on tier value.
      • HWN024021W The pool_name pool on tier tier_number on the storage_system storage system cannot be balanced by redistributing the volumes.
      • HWN024027I Storage Pool pool name has insufficient available space for volume volume name in storage pool pool name.
      • HWN024030W One or more entities specified as input for the analysis could not be found or pools or volumes in some input entities could not be found.
      • HWN024031W One or more entities specified as candidate destinations for the analysis could not be found.
      • HWN024032W For one or more mirrored volumes, both the primary and the secondary volume copies were chosen for transformation. You cannot transform both volume copies in the same transform task. Only the primary volume copies are included for transformation. You can transform the secondary volume copies in a separate transformation.
      • HWN024033W The volume volume name cannot be analyzed because it is not in a capacity pool.
      • HWN024034W The pool pool name cannot be analyzed because the pool is not in a capacity pool.
      • HWN024035W The storage virtualizer system name cannot be analyzed because the storage virtualizer is not in a capacity pool.
      • HWN024036W The operation to transform the volumes on the subsystem name storage virtualizer cannot be completed because the destination pools were not available.
      • HWN024037E An unexpected error occurred. The operation to transform the volumes on the subsystem name storage virtualizer cannot be completed because the destination pools were not identified.
      • HWN024043I The capacity pools of the source volumes were selected as the target pools.
      • HWN024046I The option that was selected to handle volumes with mirrored volumes is: After optimization, set the copy of the secondary volume in the destination pool as the primary volume. The original secondary volume remains the secondary volume.
      • HWN024047I The number of days for collecting performance data to analyze the volumes is set to performance_data_collection_period.
      • HWN024050I Automatic tiering was selected to tier the volumes.
      • HWN024051I The tiering analysis is starting.
      • HWN024052I Tier tier# has an I/O density threshold value of value per second per GiB.
      • HWN024053I Tier tier#, has a file age threshold value of value percent of files last accessed within time_unit.
      • HWN024054I The real capacity for the thin-provisioned volumes is set to value unit.
      • HWN024055I The auto expand property of the thin-provisioned volumes is set to yes/no.
      • HWN024056I The warning level for thin-provisioned volumes is set to value %.
      • HWN024057I The grain size that was specified for the thin-provisioned volumes is grain_size KiB.
      • HWN024058I The real capacity for the compressed volumes is set to value unit.
      • HWN024059I The auto expand property for the compressed volumes is set to yes/no.
      • HWN024060I The warning level for the compressed volumes is set to value.
      • HWN024061I The option that was selected to handle volumes with mirrored volumes is: After optimization, set the secondary volume as the primary volume. The volume in the destination pool is the secondary volume.
      • HWN024062I The option that was selected for mirrored volumes is: Do not optimize volumes with mirrored volumes.
      • HWN024066I Tier tier# has an I/O rate threshold value of value I/O per second.
      • HWN024067W Recommendations cannot be generated for number_of_volumes volumes because the volumes do not meet the tiering criteria for tier current_tier_number or for any lower tier.
      • HWN024068W Recommendations cannot be generated to move number_of_volumes volumes from source_tier to tier target_tier_number due to the pool activity limit value.
      • HWN024069W Recommendations cannot be generated to move number_of_volumes volumes from tier source_tier to to tier target_tier_number because the destination storage pools do not have enough space.
      • HWN024070I The analysis to optimize subsystem storage_subsystem was completed.
      • HWN024071I The option that was selected was to restrict the placement of volumes in capacity pools to destination storage pools in the same capacity pool.
      • HWN024072W No file age information for volume volume name.
      • HWN024073W Storage pool {0} in tier {1} needs at least one additional storage pool in the same tier for the Balance Analysis to run on this tier.
      • HWN024074W Storage pool {0} in tier {1} and capacity pool {2} needs at least one additional storage pool in the same tier and capacity pool for the Balance Analysis to run within this capacity pool and on this tier.
      • HWN024075W number_of_volumes volumes from storage pool pool could not be moved to the destination storage pools because the destination storage pools do not have enough space.
      • HWN024076W number_of_volumes volumes from storage pool pool could not be moved to the destination pools because the destination storage pools are not in the same capacity pool.
      • HWN024077W number_of_volumes volumes from storage pool pool could not be moved to the destination storage pools because the destination storage pools would have exceeded the pool activity limit value.
      • HWN024078W number_of_volumes volumes from storage pool pool could not be moved to the destination storage pools because the destination storage pools already have a volume copy.
      • HWN024079W Because of an internal error, the number of volumes in the pool storage pool that could not be moved to destination storage pools is number_of_volumes.
      • HWN024080W Destination storage pool pool already contains a copy of storage volume volume.
      • HWN024081W Because the destination storage pool does not have sufficient available space, the volume storage volume in the source_pool storage pool cannot be moved to the destination_pool destination storage pool.
      • HWN024082W Because the destination storage pool contains a copy of the mirrored volume, the volume volume in the source_pool storage pool cannot be moved to the destination_pool destination storage pool.
      • HWN024083W Because of an internal error, the volume storage volume in the spool storage pool could not be moved to the destination_pool destination storage pool.
      • HWN024084W Because the destination storage pools contain one or more copies of the mirrored volumes, the number of volumes that could not be moved from tier source_tier to tier target_tier is number_of_volumes.
      • HWN024085W The pool_name storage pool cannot be balanced because the tier level of the pool was reset to none.
      • HWN024086E Recommendations cannot be generated because the tier level of the destination_pool_name destination storage pool was reset to none.
      • HWN024087W Recommendations cannot be generated for one or more of the volumes because collocated volumes cannot be placed in the same destination storage pool.
      • HWN024088I The option to collocate volumes that are assigned to the same server or hypervisor was selected.
      • HWN024089I The option to collocate volumes that are assigned to the same server or hypervisor was not selected.
      • HWN024090W Because the storage pools do not meet the service class requirements, the number of volumes that cannot be moved is no_volumes.
      • HWN024091W If the recommendation to move the volume_name volume to the storage_pool_name storage pool is implemented, the service class requirements of the volume_name volume cannot be met.
      • HWN024092W Recommendations cannot be generated to move number_of_volumes volumes from tier source_tier to tier target_tier_number because the destination storage pools do not meet the service class requirements of the volumes.
      • HWN024093I The number of volumes on tier tier_level that were not analyzed because of the instruction to exclude mirrored volumes from the analysis is number_of_volumes volumes.
      • HWN024094W Valid target pools were not selected for the subsystem name storage virtualizer.
      • HWN024095I The grain size for the thin-provisioned volumes was set to the default value of grain_size KiB.
      • HWN024096W Volumes in the pool_name pool on tier tier_level cannot be moved to a higher tier to reduce the activity level of the pool to the user-defined level.
      • HWN024097W Volumes in the pool_name pool on tier tier_level cannot be moved to a lower tier to reduce the activity level of the pool to the user-defined level.
      • HWN024098W Cannot generate recommendations to tier volumes from the storage_system_name storage system because all of the source volumes are in the selected destination storage pools.
      • HWN024099I The number of volumes that were excluded from the analysis to plan the tiering of the storage_system_name storage system is vols_count. The volumes were excluded because performance data is not available for the volumes.
      • HWN024100I The number of volumes that were excluded from the analysis to plan the tiering of the storage_system_name storage system is vols_count. The volumes were excluded from the analysis because the capacity of the volumes is zero.
      • HWN024101I The number of volumes that were excluded from the analysis to plan the tiering of the storage_system_name storage system is vols_count. The volumes were excluded from the analysis because the volumes are not assigned to pools that are tiered or the thresholds were not defined for the tiers.
      • HWN024102W The recommendation to move the storage_volume_name volume from the source_pool_name storage pool to the target_pool_name storage pool was not generated because the status of the destination pool is offline or excluded.
      • HWN024103I Reclaiming volumes
      • HWN024104I Planning for tiering volumes
      • HWN024105W The recommendation to move the storage_volume_name volume from the source_pool_name storage pool to the target_pool_name storage pool will not be executed because the status of the destination pool is offline or excluded.
      • HWN024106W The recommendation to move the storage_volume_name volume from the source_pool_name storage pool was not generated because the status of the volume is offline.
      • HWN024107W The recommendation to move the storage_volume_name volume from the source_pool_name storage pool to the target_pool_name storage pool will not be executed because the status of the volume is offline.
      • HWN024108E The recommendations can't be shown because the analysis was not completed.
      • HWN024109W The data for the previous analyis of the storage_subsystem storage system was not deleted.
      • HWN024110E Volumes reclamation analysis failed for storage_subsystem storage subsystem.
      • HWN024111W Recommendations cannot be generated to move number_of_volumes volumes from tier source_tier to tier target_tier_number because there is no potential destination pool assigned to the recommended tier.
      • HWN024112W Cannot generate recommendations to tier volumes from the storage_system_name storage system because the source storage pools and the selected destination storage pools are assigned to the same tier.
      • HWN024200I The days of the week to include in the analysis: days_of_week.
      • HWN024201I The time window for the performance data to include in the analysis is set to start time - end time.
      • HWN024202I The time window for the performance data to include in the analysis is set to start time - end time. The end time occurs on the next day.
      • HWN024203W The volume storage_volume_name cannot be converted or moved because the target pools do not have sufficient available space or the target pool types are incorrect for the operation.
      • HWN025000I Storage pool value in storage system value has storage from different types of back-end storage systems. Back-end disk data cannot be determined.
      • HWN025001I Storage pool value in storage system value has storage from unknown back-end storage system(s). Back-end disk data cannot be determined.
      • HWN025002I Storage pool value in storage system value has storage from multiple back-end storage systems or from multiple pools in a single storage system. Back-end disk data cannot be determined.
      • HWN025003I Storage pool value in storage system value has storage from a back-end storage pool with multiple disk types. Back-end disk data cannot be determined.
      • HWN025004I Storage pool value in storage system value has storage from a back-end storage pool with a mixed raid type. Back-end disk data cannot be determined.
      • HWN025005I Storage pool value in storage system value has storage from a back-end storage pool with multiple raid types. Back-end disk data cannot be determined.
      • HWN025006I Storage pool value in storage system value has storage from back-end disks of unknown type. Back-end disk data cannot be determined.
      • HWN025007I Storage pool value in storage system value has storage from unknown number of back-end disks. Back-end disk data cannot be determined.
      • HWN025008I Storage pool value in storage system value has storage from back-end disks with unknown raid type. Back-end disk data cannot be determined.
      • HWN025009E Connection to Data Server failed. Make sure Data Server is up.
      • HWN025011W All of the target ports for the storage system are used for the provisioning request. The request might take a long amount of time.
      • HWN025010I Collecting parent pool volumes for storage system: storage system identification.
      • HWN025011E The port the target port ID has a usage restriction which prevents it from being used as a target port for volume assignment.
      • HWN025012E The invocation of CIM method ExposePaths failed on SMI-S provider Name of SMI-S provider . The return code is Return code of method.
      • HWN025013E The invocation of CIM method HidePaths failed on SMI-S provider Name of SMI-S provider . The return code is Return code of method.
      • HWN025014E The invocation of CIM method CreateOrModifyElementFromStoragePool failed on SMI-S provider Name of SMI-S provider . The return code is Return code of method.
      • HWN025015E The invocation of CIM method ReturnToStoragePool failed on SMI-S provider Name of SMI-S provider . The return code is Return code of method.
      • HWN025016E The invocation of CIM method DeleteStorageHardwareID failed on SMI-S provider Name of SMI-S provider . The return code is Return code of method.
      • HWN025017E A CLI command failed. Check the logs from EP working dir.
      • HWN025018E An error occured when attempting to parse the file File name.
      • HWN025019E The requested operation failed. Check the logs from EP working dir.
      • HWN025020E The volume cannot be created. The volume of size Size in pool Pool on storage system Subsystem cannot be created. The pool might already have the maximum number of volumes allowed.
      • HWN025021E Unable to resolve the address for the device because the request was not processed by the data collector.
      • HWN025022E The data collection detected storage system New Subsystem with serial number new serial number instead of expected serial number expected serial number.
      • HWN025025I Starting the task to send the report for schedule Schedule Id by email.
      • HWN025026I The report title report is being created.
      • HWN025027I The report title report with ID report id is being sent by email to the reports recipients.
      • HWN025028I The report title report with ID report id was sent by email to the reports recipients.
      • HWN025029E Can't retrieve the configured settings of the report for schedule Schedule Id .
      • HWN025030E The report can't be sent because the email server was not configured.
      • HWN025031E Can't send the report title report with ID report id by email because of the following error: reported_error.
      • HWN025031I To view the report, choose HTML as the message format or use an email application that supports HTML message formats.
      • HWN025032E Job failed during post processing of collected data from the data source.
      • HWN025033E Failed to send the report name report for schedule Schedule Id.
      • HWN025034I Created number_of_servers agentless servers automatically.
      • HWN025035I Removed number_of_servers agentless servers automatically.
      • HWN025036E Can't save the report in the directory.
      • HWN025037E Can't save the report because the path specifies a file name instead of a directory name.
      • HWN025038E Can't save the report, because the directory doesn't exist.
      • HWN025039E Can't save the report because the directory doesn't have enough disk space.
      • HWN025040I The report title report with ID report id is being saved as report file name in the full path directory.
      • HWN025041I The report title report with ID report id was saved as report file name in the full path directory.
      • HWN099990I The method name of the Device Server method of the device server returned return value @( execution context information).
      • HWN099991I info trace message@(execution context information)
      • HWN099992W warning trace message@(execution context information)
      • HWN099993E error/exception trace message @(execution context information)
      • HWN099994I An object of class name of the class has been instantiated @(execution context information).
      • HWN099995I |=== class name.method name entry, parameter(s): parameter value(s) @(execution context information).
      • HWN099996I ===| class name.method name exit, return value: method return value ( execution time in milliseconds) @(execution context information).
      • HWN099997I External service name of the (DM) external service will be invoked with parameter(s) parameter value(s)@(execution context information).
      • HWN099998I Invocation of external service name of the (DM) external service returned result invocation result@(execution context information).
      • HWN099999I The method name of the device server method of the device server was invoked with parameters invocation parameters@(execution context information).
      • HWN6001I Operation operation completed successfully.
      • HWN6002I Unable to set up NLS message file processing.
      • HWN6003E Unable to set up tracing.
      • HWN6004E Operation operation failed.
      • HWN6005E Unknown operation operation.
      • HWN6006E Could not initialize connection, rc is rc
      • HWN6007E Could not parse command arguments: arg
      • HWN6008E Error processing command: command
      • HWN6009E Missing 'operation' property in input file
      • HWN6010I Task arg completed successfully
      • HWN6011E Task arg failed
      • HWN6012E Cannot connect to this IP, switching to IP
      • HWN6013E An IBM XIV CLI command failed. The error is arg.
      • HWN6014I Command arg completed successfully
      • HWN6015E Command command failed.
      • HWN6016I Connected with IP address IP
      • HWN6017I Started creation of volume with size size in pool pool.
      • HWN6018I Volume creation completed successfully. New volume volume created with size size in pool pool.
      • HWN6019I Started deletion of volume volume in pool pool.
      • HWN6020I Volume deletion completed successfully. Volume wolume deleted in pool pool
      • HWN6021I Started creation of host host with initiator ports ports
      • HWN6022I Finished creation of host host with initiator ports ports
      • HWN6023I Started assignment of volume volume to host host.
      • HWN6024I Finished assignment of volume volume to host host.
      • HWN6025I Started unassignment of volume volume from host host.
      • HWN6026I Finished unassignment of volume volume from host host
      • HWNEP0001I Successfully persisted number of count instances.
      • HWNEP0002E The probe failed as the data collector couldn't write to its output file, value.
      • HWNEP0003E A DS8000 ESSNI command failed. The error code is error_code.
      • HWNEP0004I Started creation of volume group volume_group.
      • HWNEP0005I Finished creation of volume group volume_group with subsystem volume group number number .
      • HWNEP0006I Started adding volumes, with serial numbers volume_list, to subsystem volume group volume_group_number .
      • HWNEP0007I Finished adding volumes to volume group.
      • HWNEP0008I Started assignment of host host on subsystem subsystem to volume group volume_group.
      • HWNEP0009I Finished assigning host on subsystem subsystem to volume group volume_group.
      • HWNEP0010I Started removing volumes, with serial numbers volume_list, from subsystem volume group volume_group_number .
      • HWNEP0011I Finished removing volumes, with serial numbers volume_list, from subsystem volume group volume_group_number .
      • HWNEP0012I Increased virtual capacity of storage pool storage_pool on subsystem subsystem to size size .
      • HWNEP0013I Collecting pools for storage system storage system identification.
      • HWNEP0014I Collecting volumes for lss logical subsystems on storage system storage system identification.
      • HWNEP0015I Collecting volume groups on storage system storage system identification.
      • HWNEP0016I Collecting hosts on storage system storage system identification.
      • HWNEP0017I value Hosts Found.
      • HWNEP0018I Launching external process for devices devices.
      • HWNEP0019I External process for devices devices completed successfully.
      • HWNEP0020E Could not create connection to NAPI The IP for the NAPI..
      • HWNEP0021E ESSNI API query for Space Efficient Volume failed with ESSNI code ESSNI Code. Data from ESSNI is considered suspect.
      • HWNEP0022I Started deletion of volume group with number volume_group_number.
      • HWNEP0023I Finished deletion of volume group with number volume_group_number.
      • HWNEP0100I Probing Volumes for Storage System: value
      • HWNEP0101I Number of Volumes currently found: value. Continuing to probe Volumes.
      • HWNEP0102I value Volumes found.
      • HWNEP0103I Probing Configured Disks for Storage System: value.
      • HWNEP0104I Number of Configured Disks Found Currently: value. Continuing to Probe Disks.
      • HWNEP0105I value Configured Disks Found.
      • HWNEP0106I Probing Views of Host Initiator access to Volumes.
      • HWNEP0107I Finished probing Views.
      • HWNEP0108I Initializing Probe for storage system storage system identification.
      • HWNEP0109I Probe for storage system storage system identification completed.
      • HWNEP0110I Collecting Nodes and fibre channel ports for storage system storage system identification.
      • HWNEP0111E The connection to the storage device failed. The error code is error_code.
      • HWNEP0113E The cluster IP address is not specified in the configuration file.
      • HWNEP0114E The trustore location is not specified in the configuration file.
      • HWNEP0115E The IBM Spectrum Control data is out of synch with the device configuration and a re-probe is required for device device name .
      • HWNEP0116E The user configured for the subsystem subsystem name is not permitted to perform the requested action.
      • HWNEP0117E The virtual disk (VDisk)-to-host mapping was not created because the volume vdiskName is already mapped to the hostName host for the Device deviceName
      • HWNEP0115I Starting Control Process for storage system storage system identification.
      • HWNEP0116I Started deletion of volume VolumeID on subsystem Subsystem .
      • HWNEP0117I Volume deletion completed successfully. Volume VolumeID on subsystem Subsystem was deleted.
      • HWNEP0118I Started adding Managed Disk(s) Managed Disk ID to Managed-disk group Managed Disk group name on subsystem Subsystem.
      • HWNEP0119I Finished adding Managed Disk(s) Managed Disk ID to Managed-disk group Managed Disk group name on subsystem Subsystem.
      • HWNEP0120I Started creation of volume with size Size in pool Pool on subsystem Subsystem
      • HWNEP0121I Volume creation completed successfully. New volume VolumeID created with size Size in pool Pool on subsystem Subsystem .
      • HWNEP0122I Started assignment of volume VolumeID on subsystem Subsystem to initiator port Initiator Port on host Host .
      • HWNEP0123I Finished assignment of volume VolumeID on subsystem Subsystem to initiator port Initiator Port on host Host Name .
      • HWNEP0124I Started unassignment of volume VolumeID on subsystem Subsystem from initiator port Initiator Port on host Host Name .
      • HWNEP0125I Finished unassignment of volume VolumeID on subsystem Subsystem from initiator port Initiator Port on host Host Name .
      • HWNEP0126I Started creation of host host name on subsystem Subsystem with initiator ports WWPNs .
      • HWNEP0127I Finished creation of host host name on subsystem Subsystem with initiator ports WWPNs .
      • HWNEP0128I Host name hostName already exists for the WWPNs wwpns on the device Subsystem
      • HWNEP0129E The operation failed because the device returned unexpected values.
      • HWNEP0130E A IBM XIV CLI command failed. The error is error_code.
      • HWNEP0131I The host definition for host host name on subsystem Subsystem contains additional Hostports WWPNs that will also be assigned to Volume VolumeID .
      • HWNEP0132E The unassignment of Volume VolumeID from hostport WWPN failed because the definition for host host name on subsystem Subsystem contains additional hostports WWPNs .
      • HWNEP0133E Error invoking the external process for device device name .
      • HWNEP0134E Following exception occurred: exception .
      • HWNEP0135E External process failed with error code error code .
      • HWNEP0136E Error connecting to IP address with user ID user ID .
      • HWNEP0137I Job job ID submitted for device device name .
      • HWNEP0138I External process was successfully executed for device device name .
      • HWNEP0139I An instruction was issued to add a copy of the volume_name volume_size-byte volume in the pool_name pool on the storage_system_name storage system.
      • HWNEP0140I The copy of the volume_name volume_size-byte volume with the copy ID of VolumeID in the pool_name pool on the storage_system_name storage system was added successfully.
      • HWNEP0141I Probing Internal Drives for Storage System: value.
      • HWNEP0142I Number of Internal Drives Found Currently: value. Continuing to Probe Internal Drives.
      • HWNEP0143I value Internal Drives Found.
      • HWNEP0144I Probing Pools for Storage System: value.
      • HWNEP0145I Number of Pools Found Currently: value. Continuing to Probe Pools.
      • HWNEP0146I value Pools Found.
      • HWNEP0147I Collecting asset and status information about storage_system_id storage system.
      • HWNEP0148I Collecting cluster information for storage_system_id storage system.
      • HWNEP0149I Collecting file system exports for storage_system_id storage system.
      • HWNEP0150I Collecting nodes for storage_system_id storage system.
      • HWNEP0151I Collecting file systems for storage_system_id storage system.
      • HWNEP0152I Collecting pools for storage_system_id storage system.
      • HWNEP0153I Collecting file system storage for storage_system_id storage system.
      • HWNEP0154I Collecting filesets for storage_system_id storage system.
      • HWNEP0155I Collecting links between file systems and nodes for storage_system_id storage system.
      • HWNEP0156I Collecting quotas for storage_system_id storage system.
      • HWNEP0157I Collecting file system snapshots for storage_system_id storage system.
      • HWNEP0158I Collecting capacity for file_system_id file system.
      • HWNEP0159I Creating the export export name on cluster cluster name .
      • HWNEP0160I The export export name on cluster cluster name with path export path was created.
      • HWNEP0161I The export export name on cluster cluster name is being changed.
      • HWNEP0162I The export export name on cluster cluster name was changed.
      • HWNEP0163I Setting quota quota type - quota name on file system file system name .
      • HWNEP0164I Quota quota type - quota name on file system file system name has been created.
      • HWNEP0165I Checking quota on file system file system name .
      • HWNEP0166I Quota on file system file system name has been checked.
      • HWNEP0167I The export export name on cluster cluster name is being removed.
      • HWNEP0168I The export export name on cluster cluster name was removed.
      • HWNEP0169E Command: command did not complete. IBM SONAS CLI message
      • HWNEP0170I Creating fileset fileset name on file system files system name .
      • HWNEP0171I Successfully created fileset fileset name on file system file system name .
      • HWNEP0172I Removing fileset fileset name on file system files system name .
      • HWNEP0173I Successfully removed fileset fileset name on file system file system name .
      • HWNEP0174I Modifying fileset fileset name on file system files system name .
      • HWNEP0175I Successfully modified fileset fileset name on file system file system name .
      • HWNEP0176I Creating file system file system on cluster cluster name .
      • HWNEP0177I Successfully created file system file system on cluster cluster name .
      • HWNEP0178I Changing file system file system on cluster cluster name .
      • HWNEP0179I Successfully changed file system file system on cluster cluster name .
      • HWNEP0180I Removing file system file system on cluster cluster name .
      • HWNEP0181I Successfully removed file system file system on cluster cluster name .
      • HWNEP0182I Mounting file system file system .
      • HWNEP0183I Successfully mounted file system file system .
      • HWNEP0184I Unmounting file system file system .
      • HWNEP0185I Successfully unmounted file system file system .
      • HWNEP0186I Linking fileset fileset on file system file system .
      • HWNEP0187I Successfully linked fileset fileset on file system file system .
      • HWNEP0188I Unlinking fileset fileset on file system file system .
      • HWNEP0189I Successfully unlinked fileset fileset on file system file system .
      • HWNEP0190E The IBM Spectrum Control server could not connect to IP address using the SSH protocol.
      • HWNEP0191E The IBM Spectrum Control server could not authenticate with IP address using the SSH protocol.
      • HWNEP0192E The IBM Spectrum Control server could not execute a command on the IBM Storwize V7000 Unified/IBM SONAS device at IP address .
      • HWNEP0193E The command name command failed because the following command executed on the NAS device failed with the return code return code : command returned: command output
      • HWNEP0195I modify fileset
      • HWNEP0196I change export
      • HWNEP0197I create export
      • HWNEP0198I remove export
      • HWNEP0199I create fileset
      • HWNEP0200I link fileset
      • HWNEP0201I remove fileset
      • HWNEP0202I unlink fileset
      • HWNEP0203I change filesystem
      • HWNEP0204I create filesystem
      • HWNEP0205I mount filesystem
      • HWNEP0206I remove filesystem
      • HWNEP0207I unmount filesystem
      • HWNEP0208I check quota
      • HWNEP0209I set quota
      • HWNEP0210I probe
      • HWNEP0211W The command name command completed, however during post-processing the following command executed on the NAS device failed with the return code return code : command returned: command output As a result, the IBM Spectrum Control database is now out of sync with the current state of the NAS device.
      • HWNEP0212I create disk in modifying file system
      • HWNEP0213I Started deletion of host host name on subsystem Subsystem .
      • HWNEP0214I Finished deletion of host host name on subsystem Subsystem .
      • HWNEP0215I Collecting cache information for storage_system_id storage system.
      • HWNEP0216I remove cached source
      • HWNEP0217I create cached node
      • HWNEP0218I remove cached node
      • HWNEP0219I create cache
      • HWNEP0220I remove cache
      • HWNEP0221I modify cache source
      • HWNEP0222I Creating cache source cache_source_name on cluster file_system_name.
      • HWNEP0223I Created cache source cache_source_name on cluster file_system_name.
      • HWNEP0224I Removing cache source cache_source_name on cluster file_system_name.
      • HWNEP0225I Removed cache source cache_source_name on cluster file_system_name.
      • HWNEP0226I Modifying cache source cache_source_name on cluster file_system_name.
      • HWNEP0227I Modified cache source cache_source_name on cluster file_system_name.
      • HWNEP0228I Creating cache cache_name on file system file_system_name.
      • HWNEP0229I Created cache cache_name on file system file_system_name.
      • HWNEP0230I Removing cache cache_name on file system file_system_name.
      • HWNEP0231I Removed cache cache_name on file system file_system_name.
      • HWNEP0232I Modifying cache cache_name on file system file_system_name.
      • HWNEP0233I Modified cache cache_name on file system file_system_name.
      • HWNEP0234I modify cache
      • HWNEP0235I create cached source
      • HWNEP0236I Configuring nodes node_names as cached nodes.
      • HWNEP0237I Configured nodes node_names as cached nodes.
      • HWNEP0238I Unconfiguring cached nodes node_names.
      • HWNEP0239I Unconfigured cached nodes node_names.
      • HWNEP0240I Executed control operation on cache cache_name on filesystem file_system_name .
      • HWNEP0241I control cache
      • HWNEP0242I run prepop
      • HWNEP0243I list prepop
      • HWNEP0244I Retrieving cache prepopulation status for file system file system name .
      • HWNEP0245I Cache prepopulation status for file system file system name has been retrieved.
      • HWNEP0246I Prepopulate cache data for fileset fileset_name on file system file_system_name using policy policy_name.
      • HWNEP0247I Command to pre populate cached data for fileset fileset_name was successful.
      • HWNEP0248W An error was encountered while parsing protocol options for export export_name. The options were not persisted, the probe will continue.
      • HWNEP0249W The connection to the storage device failed. The error code is error_code.
      • HWNEP0250I Started adding initiator port(s) initiator ports to host host name on subsystem subsystem .
      • HWNEP0251I Finished adding initiator port(s) initiator ports to host host name on subsystem subsystem .
      • HWNEP0252W A CLI command completed with warning. The warning message is : warning_message
      • HWNEP0253W Volume creation completed with warning. New volume VolumeID created with size Size in pool Pool on subsystem Subsystem .
      • HWNEP0254W Volume deletion completed with warning. Volume VolumeID on subsystem Subsystem was deleted.
      • HWNEP0255I The task to execute the recommendations for optimizing the volumes on the storage system with an ID of storage_system_id was paused.
      • HWNEP0256I The task for optimizing the volumes on the storage system with an ID of storage_system_id was canceled.
      • HWNEP0257I The task for optimizing the volumes on the storage system with an ID of storage_system_id was resumed.
      • HWNEP0258E The optimization task cannot be paused because the synchronization rate for the volume cannot be reset. The ID of the volume is volume_id and the ID of the storage system is storage_system_id.
      • HWNEP0259E The optimization task cannot be resumed because the synchronization rate for the volume cannot be reset. The ID of the volume is volume_id and the ID of the storage system is storage_system_id.
      • HWNEP0260I Started creation of host port host port name on storage system Storage System with initiator port WWPN .
      • HWNEP0261I Finished creation of host port host port name on storage system Storage System with initiator port WWPN .
      • HWNEP0262E The recommendation for the volume_name volume was not implemented because the command that was issued by the storage virtualizer returned the following error: error_message
      • HWNEP0263I The synchronization of the volume_name volume with the volume copy was successful.
      • HWNEP0264E The synchronization of the volume_name volume with the volume copy was unsuccessful.
      • HWNEP0265E The CLI command that was issued for the storage_system_name storage system failed and generated the following error: error_message
      • HWNEP0266I Started expanding the capacity of volume volume on subsystem subsystem from oldsize to newsize bytes.
      • HWNEP0267I Finished expanding the capacity of volume volume on subsystem subsystem to newsize bytes.
      • HWNEP0268E The server operating system or version is not supported by IBM Spectrum Control for IBM Spectrum Scale.
      • HWNEP0269E The IBM Spectrum Scale cluster information cannot be displayed. All the nodes in the cluster are down or cannot be contacted.
      • HWNEP0270E The switch cannot respond to SNMP queries because of an authentication error.
      • HWNEP0271E The following password decryption exception occurred: exception
      • HWNEP0272E The switch cannot respond to SNMP queries because of the following exception: exception
      • HWNEP0273E The following exception occurred because the OID format is incorrect: exception
      • HWNEP0274E The switch cannot respond to SNMP queries because of a timeout problem.
      • HWNEP0270I Retrieved the file module address file_module_address.
      • HWNEP0271I No quota data was collected. Quota limits are not activated for the file systems that are associated with the IBM Spectrum Scale cluster.
      • HWNEP0272I Collecting file systems that are mounted on the nodes of storage system storage_system_id.
      • HWNEP0275W One or more operations failed for the CLI command that was issued for the storage system. The following error was generated: errorMsg .
      • HWNEP0276E Command execution failed because sudo is not installed.
      • HWNEP0277I Commands are executed through 'sudo'.
      • HWNEP0278E User can not execute command through sudo.
      • HWNEP0279I Collecting remote file systems for storage_system_id storage system.
      • HWNEP0280I Collecting remote file systems that are mounted on the nodes of storage system storage_system_id.
      • HWNEP0281E The switch is returning corrupted data.
      • HWNEP0282E Zoning data cannot be collected because there is a transaction in progress on the switch
      • HWNEP0283E VSAN vsan_name was not found.
      • HWNEP0284E No zoning data collected from the switch.
      • HWNEP0285E Cannot authenticate to the object storage using the specified user credentials.
      • HWNEP0286E An object storage request failed on the GPFS cluster.
      • HWNEP0287E Error when collecting Accounts information from Object Storage Service using REST protocol.
      • HWNEP0288E Error when collecting Containers information from Object Storage Service using REST protocol.
      • HWNEP0281I Collecting object storage accounts for storage_system_id storage system.
      • HWNEP0282I Collecting object storage containers for storage_system_id storage system.
      • HWNEP0289E Failed to retrieve container information because the number of containers now exceeds the maximum number of containers that can currently be collected for an account ( MAX Containers ).
      • HWNEP0290E The probe failed to retrieve object storage account information from the storage system storage_system_id because the userid user does not have the required authority.
      • HWNEP0291E The probe failed to retrieve object storage container information from the storage system storage_system_id because the userid user does not have the required authority.
      • HWNEP0292E Cannot query the object service for information about accounts and containers as the specified user does not have admin privileges.
      • HWNEP0293W The probe did not collect information about all the object accounts for the storage system storage_system_id as the userid user does not have sufficient authority on the storage system.
      • HWNEP0294W An authentication error prevented the switch from responding to SNMP queries regarding the ability of the switch to perform zone control.
      • HWNEP0295W A timeout prevented the switch from responding to SNMP queries regarding the ability of the switch to perform zone control.
      • HWNEP0296W The switch cannot respond to SNMP queries to check the ability of the switch to perform zone control because of the following exception: exception
      • HWNEP0297W The switch cannot respond to SNMP queries to check the ability of the switch to perform zone control because of the following exception: exception
      • HWNEP0298I Collecting IBM Cloud Object Storage configuration.
      • HWNEP0299I Collecting IBM Cloud Object Storage vaults.
      • HWNEP0300I Collecting detailed IBM Cloud Object Storage status.
      • HWNEP0301W The IP address ip_address for the FlashSystem storage system is not the management IP address.
      • HWNEP0302I Collecting Transparent Cloud Tiering information for storage_system_id storage system.
      • HWNEP0303I No Transparent Cloud Tiering configuration was detected on the IBM Spectrum Scale cluster.
      • HWNEP0304E Cannot connect to IBM Cloud Object Storage.
      • HWNEP0305I Collecting disk controllers for storage system storage system identification.
      • HWNEP0306I Collecting disks for storage system storage system identification.
      • HWNEP0307I Collecting CIFS shares for storage system storage system identification.
      • HWNEP0308I Collecting NFS exports for storage system storage system identification.
      • HWNEP0309I The data is being collected by the data collector: data collector host.
      • HWNEP0310I Discovery found number storage systems.
      • HWNEP0311I Probing nodes or directors for storage system name storage system.
      • HWNEP0312I Probe found number nodes or directors.
      • HWNEP0313I Probing pools for storage system name storage system.
      • HWNEP0314I Probe found number pools.
      • HWNEP0315I Probing disk groups for storage system name storage system.
      • HWNEP0316I Probe found number disk groups.
      • HWNEP0317I Probing disks for storage system name storage system.
      • HWNEP0318I Probe found number disks.
      • HWNEP0319I Probing host connections for storage system name storage system.
      • HWNEP0320I Probing ports for storage system name storage system.
      • HWNEP0321I Probing volumes for storage system name storage system.
      • HWNEP0322I Probe found number volumes. Continuing to probe volumes.
      • HWNEP0323I Probe found number volumes for storage system name storage system.
      • HWNEP0324I Probing NAS nodes for storage system name storage system.
      • HWNEP0325I Probe found number NAS nodes.
      • HWNEP0326I Probing file systems that are mounted on the NAS nodes of storage system name storage system.
      • HWNEP0327I Probe found number file systems.
      • HWNEP0328I Probing file system exports for storage system name storage system.
      • HWNEP0329W profile name version version number SMI-S Profile is not supported.
      • HWNEP0330E Unable to find minimum required SMI-S profile to proceed with requested task.
      • HWNEP0331I Probing copy pair relationships for storage system name storage system.
      • HWNEP0332I Probe found number copy pairs.
      • HWNEP1111E There is no connection for the specified device.
      • HWNEP1112E No SSH server found on the device.
      • HWNEP1113E Unsupported version.
      • HWNEP1114E The connection to the device failed.
      • HWNEP1115E Authentication failed.
      • HWNEP1116E Unknown host.
      • HWNEP1117E The passphrase is wrong.
      • HWNEP1118E The passphrase is missing.
      • HWNEP1119E Unknown error.
      • HWNEP1120E ESSNI not available.
      • HWNEP1121E Private key not found.
      • HWNEP1122E Invalid format for the private key.
      • HWNEP1123E Unable to establish a connection to the device through http port 80.
      • HWNEP1124I Log collection successfully started for storage system name storage system.
      • HWNEP1125E The activity requested is already in progress on storage system name storage system.
      • HWNEP1126I The support log activity has started successfully storage system name storage system.
      • HWNEP0112E The CLI command that was issued for the storage system failed and generated the following error: error_message
      • HWNPM5412E The process failed because it was unable to find the Export Tool. Expected location was loc of tool
      • NAD0001I Connecting to hostname using protocol protocol.
      • NAD0006E Exception thrown for method method name: error message.
      • NAD0008E Invalid protocol protocol passed to method name.
      • NAD0010E Invalid parameter(s) parameter name passed to method name.
      • NAD0013I Installing GUID on remote machine: hostname.
      • NAD0014I GUID successfully installed on remote machine: hostname.
      • NAD0018E Command on remote machine: host name failed. Error code = value executing command value.
      • NAD0019E Parameter parameter passed to method is null or 0 length.
      • NAD0055E Failed to connect to remote host host.
      • NAD0146E The connection to remote machine failed because the Remote Execution and Access component was unable to create a temporary directory on the remote machine. Remove unneeded ~CSRI* directories in the remote machine's temporary directory.
      • NAD0156E The server host_address cannot be reached because the host name or IP address is not recognized.
      • NAD0157E The server host_name cannot be contacted. The server might be down, unreachable due to network problems, or the SSH credentials might be invalid.
      • NAD0180I Installing re-distributable package on .
      • NAD0181I Install of re-distributable package on succeeded.
      • NAD0182E Failed to install re-distributable package on .
      • NAD0186I Trying to locate package TIVguid using pkginfo ...
      • NAD0187I Package TIVguid is not installed.
      • NAD0188I Checking TIVguid default install path : path ...
      • NAD0260I Agent is active.
      • NAD0274E An SSH certificate certificate name already exist.
      • NAD0275E Failed to connect to remote host hostname and port. Failed to establish a secure connection.
      • NAD0276E Failed to connect to remote host hostname and port. Failed to establish a secure connection because the SSL handshake failed.
      • NAD0277E Failed to connect to remote host hostname and port. Failed to establish a secure connection because of an invalid SSL key.
      • NAD0278E Failed to connect to remote host hostname and port. Failed to establish a secure connection because the identity of the peer could not be verified.
      • NAD0279E Failed to connect to remote host hostname and port. Failed to establish a secure connection because of an SSL protocol error.
      • BTAVM2272W Unsupported virtual disk backing info for disk "Disk name" of hypervisor Hypervisor name, virtual machine "VM name": Virtual disk type.
      • BTAVM2273W Unable to find file "File name" which is the backing device of the virtual disk "Disk name" of hypervisor Hypervisor name, virtual machine "VM name".
      • BTAVM2274W Probe of hypervisor Name of the Hypervisor completed with warnings.
    • HWNAS - Agentless Server messages
      • HWNAS0001I Successfully created server server.
      • HWNAS0002I Successfully deleted server server.
      • HWNAS0003E The host name or IP address {0} is not valid.
      • HWNAS0004E Cannot add port portWWPN because it belongs to server serverName.
      • HWNAS0005E Cannot add port portWWPN because it belongs to switch switchName.
      • HWNAS0006E Cannot add port portWWPN because it belongs to storage system storageSystemName.
      • HWNAS0007W Server serverName was not created because it exists already.
      • HWNAS0008I Successfully created mergeServerName server by merging numberOfServers servers.
      • HWNAS0009I Successfully separated serverName server into numberOfServers individual servers.
      • HWNAS0011I You cannot separate the serverName agentless server because it is not based on storage system host connections.
      • HWNAS0012I You cannot separate the serverName agentless server because it is already defined on the smallest possible separation boundary.
      • HWNAS0013I You cannot merge the selected agentless servers into the serverName agentless server because they are not all based on storage system host connections.
    • HWNDA - Data Manager API messages
      • HWNDA0001I Operation Name of the operation processed successfully.
      • HWNDA0002E Mandatory parameter Name of the mandatory parameter which is missing missing
      • HWNDA0003E Invalid parameter Name of the parameter which was invalid
      • HWNDA0004E An internal error occurred.
      • HWNDA0005E The server encountered an error when it was accessing the database.
      • HWNDA0006E The name provided while creating a new group is already in use.
      • HWNDA0007E An external key could not be identified for the provided type The constant integer type of the Group element and id The unique integer database ID of the Group element.
      • HWNDA0008E The specified attribute invalid attribute name is not a valid attribute.
      • HWNDA0009E An internal ID could not be identified for the provided type The constant integer type of the Group element and external key The unique external key of the Group element.
      • HWNDA0010I The following elements are already members of the group The group: The keys of the elements.
      • HWNDA0011I The following elements are not members of the The group Group and cannot be removed: The element key.
      • HWNDA0012E Adding a Group with the name Name of the proposed new member to the Name of the parent group Group would create a circular relationship that is not allowed.
      • HWNDA0013E The input parameter value input parameter value for input input parameter name exceeds the maximum allowable length of number of allowable characters characters.
      • HWNDA0014E The provided Group attribute value Group attribute value for the Group attribute name Group attribute contains invalid characters. The following characters are not allowed, \\/:*?><|."
      • HWNDA0015E You are not the original creator of the provided Group name Group name.
      • HWNDA0016E The provided Tiering Policy name Tiering Policy name is not unique.
      • HWNDA0017E The provided Group Group name or ID does not exist.
      • HWNDA0018E The provided Tiering Policy name Tiering Policy name does not exist.
      • HWNDA0019E The provided candidate and destination Group names, Group name, cannot be the same.
      • HWNDA0020E The provided condition condition type is not valid.
      • HWNDA0021E The provided operand operand type is not valid.
      • HWNDA0022E The provided condition condition type is either already applied to this tiering policy or conflicts with an existing condition, existing condition type.
      • HWNDA0023E The requested priority value priority value is invalid.
      • HWNDA0024E The specified Group name Group name is not unique.
      • HWNDA0025E Cannot add the specified resource because the resource type, element type, is not supported as a child of the group.
      • HWNDA0026E Cannot add the specified group, Group name, because the group type, type, is not supported as a child of the application.
      • HWNDA0027E The first option specified in the file must be -appgroupname.
      • HWNDA0028E The argument of the option option is missing at or before line Line Number : Line
      • HWNDA0029E Both option1 and option2 were specified at or before line Line Number : Line
      • HWNDA0030E The option option is missing at or before line Line Number : Line
      • HWNDA0031E Neither option1 nor option2 was specified at or before line Line Number : Line
      • HWNDA0032E Invalid number of parameters for option option at or before line Line Number : Line
      • HWNDA0033E Incomplete options sequence before end of file.
      • HWNDA0034E Invalid option option at line Line Number : Line
      • HWNDA0035E Invalid resource type type at line Line Number : Line
      • HWNDA0036E Invalid sequence of options at or before line Line Number : Line
      • HWNDA0037E Syntax error, quote sequence not properly closed at line Line Number : Line
      • HWNDA0038E Option option is not allowed for resource type type at or before line Line Number : Line
      • HWNDA0039E The input data for modifying the application groups is missing.
      • HWNDA0040E An invalid element was encountered in the input data.
      • HWNDA0041E The application group name is missing from the input data.
      • HWNDA0042E The operation is missing from the input data.
      • HWNDA0043E The resource type is missing from the input data.
      • HWNDA0044E The server name is missing from the input data.
      • HWNDA0045E The device name is missing from the input data.
      • HWNDA0046E Invalid values were specified for the server, device or cluster names in the input data.
      • HWNDA0047E Member names and the tags were specified for the same operation.
      • HWNDA0048W The following entities were not found: Entities.
      • HWNDA0049W No entities were found for the tags: Tags
      • HWNDA0050E The member names or tags were not specified for the operation.
      • HWNDA0051W The group Name of the proposed new member cannot be added to itself.
      • HWNDA0052W The group Name of the proposed new member cannot be added to the Name of the parent group group because it creates a circular relationship that is not allowed.
      • HWNDA0053W The group Name of the group contains child groups and cannot be deleted. The child groups must be deleted before the parent group can be deleted.
      • HWNDA0054E The filter mask that was used to create or edit a group filter is currently being used.
      • HWNDA0055E The argument argument for the parameter parameter on line Line Number : Line is invalid.
      • HWNDA0056E The first option specified in the file must be -id.
      • HWNDA0057E The specified Group Group name is not of type type.
      • HWNDA0058W These groups have same names as existing members of the group The group: The keys of the elements. They were not added to the group.
      • HWNDA0059E The specified tag key Tag key is not valid.
      • HWNDA0060W These group members are also members of another group: The groups. They are not deleted.
      • HWNDA0061W These group members cannot be moved up one level in hierarchy due to name conflicts: The groups. The group is not deleted.
      • HWNDA0062E The specified Group Group name is not a department group.
      • HWNDA0063W These group members cannot be moved as top level groups in hierarchy due to name conflicts: The groups. No group members were removed from the group.
      • HWNDA0064E An application with the same name already exists.
      • HWNDA0065E A department with the same name already exists.
      • HWNDA0066E Invalid values were specified for the device, cluster or file system names in the input data.
      • HWNDA0067E Resources of type Type of resource cannot be added to an application or removed from an application using tags.
      • HWNDA0068E The application cannot be added because the number of levels in the group hierarchy exceeds the maximum of five levels.
      • HWNDA0069E The department cannot be added because the number of levels in the group hierarchy exceeds the maximum of five levels.
      • HWNDA0070W The File Systems: {0} were not added to the application {1} because they are NAS file systems.
      • HWNDA0071E Member IDs and the tags were specified for the same operation.
      • HWNDA0072E Member IDs should be specified in the input data for resources of type appgroup.
      • HWNDA0073E A general group with the same name already exists.
      • HWNDA0074E The general group cannot be added because the number of levels in the group hierarchy exceeds the maximum of five levels.
      • HWNDA0075E A dashboard with the same name already exists.
      • HWNDA0076E The dashboard group cannot be added because the number of levels in the group hierarchy exceeds the maximum of five levels.
      • HWNDA0077E A policy group with the same name already exists.
      • HWNDA0078I The Name of the policy group policy group was removed.
    • HWNPM - Performance manager messages
      • HWNPM0001E The specified summarization level (level) is invalid. It must be an integer value between minimum and maximum, inclusive.
      • HWNPM0002E The specified device category (category) is invalid. It must be an integer value between minimum and maximum, inclusive.
      • HWNPM0003E The specified device type (type) is invalid. It must be an integer value between minimum and maximum, inclusive.
      • HWNPM0004E The specified component type (type) is invalid. It must be an integer value between minimum and maximum, inclusive.
      • HWNPM0006E The string specified as parameter (string) exceeded its allowed length (maximum length).
      • HWNPM0007E The value specified as parameter (value) is invalid.
      • HWNPM0008E A required parameter is missing (null).
      • HWNPM0010E The specified device ID (device ID) is invalid. It must conform to the pattern 'name+nameFormat'.
      • HWNPM0011E The specified component ID (component ID) is invalid. It must be a simple WWN (16 hexadecimal characters).
      • HWNPM0012E The specified component ID (component ID) was not found or is not unique in the IBM Spectrum Control database.
      • HWNPM0013E The specified component ID (component ID) is invalid.
      • HWNPM0015E Failed to retrieve the requested data because the service is unavailable.
      • HWNPM0021E The device identifier specified as parameter (device ID ) is invalid.
      • HWNPM0090E Failed to retrieve the requested data because the service is unavailable.
      • HWNPM0099E The requested operation failed because of an internal error.
      • HWNPM0101E Unable to create the specified performance service instance ({0}).
      • HWNPM0200I This operation (operation name)on Performance Manager was successful.
      • HWNPM0201E The device (device_id) that was passed to the method is invalid.
      • HWNPM0202E The device category (device_category) that was passed to the method is invalid.
      • HWNPM0203E The device type received (device_type) is invalid.
      • HWNPM0204E The device type - HOST - that was passed to the method is not supported.
      • HWNPM0205E The specified performance collection policy is invalid.
      • HWNPM0209I The device type and device category are valid.
      • HWNPM0210E Collector failed to start due to system failure.
      • HWNPM0220E Collector failed to stop due to system failure.
      • HWNPM0230E One or more of the specified performance collection policies are invalid.
      • HWNPM0231W The specified performance collection policy is ignored because it conflicts with another policy in the same parameter list.
      • HWNPM0232E The specified performance collection policy contains an unsupported interval length.
      • HWNPM0233E The specified performance collection policy contains an unsupported frequency.
      • HWNPM0234E The specified performance collection policy contains an unsupported duration.
      • HWNPM0240E The attempt to update the specified performance collection policies has failed.
      • HWNPM0241E The attempt to reset the specified performance collection policies has failed.
      • HWNPM0242E The attempt to remove the specified performance collection policies has failed.
      • HWNPM0249W An attempt to dynamically update one or more running performance collectors with a new performance collection policy has failed.
      • HWNPM0250E One or more default performance collection policies are missing from the database.
      • HWNPM0281I Performance monitoring is unavailable for resource resource_name because an agent for monitoring the resource was not defined. For IBM Spectrum Scale, the problem might occur because the data collection service cannot connect to port 9084 on the node where the collector component of the IBM Spectrum Scale performance monitoring tool is running.
      • HWNPM0282I Performance monitoring is unavailable for resource resource_name because the associated data sources are unable to collect performance data from the resource.
      • HWNPM0283I Performance monitoring is unavailable for resource_name because this resource does not support performance monitoring.
      • HWNPM0284I Performance monitoring is unavailable for resource resource_name because the associated agent does not have the required level of software agent_level.
      • HWNPM0285I Performance monitoring is unavailable for resource resource name because the associated agent is unable to fully monitor the resource.
      • HWNPM0286I Performance monitoring is unavailable for resource resource name because the associated SMI-S provider does not have the required SMI-S support.
      • HWNPM0287I Performance monitoring is unavailable for resource resource name because the resource or the associated agent does not support performance monitoring.
      • HWNPM0289W Performance monitoring is unavailable for resource resource_name because no agents are available.
      • HWNPM0290E Performance monitoring is unavailable for resource resource_name because the associated agent was could not be selected.
      • HWNPM0291I Performance monitoring is unavailable for switch resource_name because the switch has no ports.
      • HWNPM0300E There is an exception for each device processed in a multiple devices call.
      • HWNPM0390E A system failure occurred.
      • HWNPM0400I This operation (operation name)on Threshold Service was successful.
      • HWNPM0401E The device (device_id) that was passed to the method is invalid.
      • HWNPM0410E The Performance threshold policy that was passed to the method (threshold policy)is null.
      • HWNPM0411E The Performance threshold that was passed to the method (threshold)is null.
      • HWNPM0412E The Performance threshold filter that was passed to the method (filter)is null.
      • HWNPM0420E The device type received (device_type) is invalid.
      • HWNPM0421E There is no default performance threshold policy or default threshold filter for this device.
      • HWNPM0425E There is an exception for each device processed in a multiple devices threshold call.
      • HWNPM0590E Performance Manager failed due to system failure.
      • HWNPM0600E Parameter number a number of the call made to the IBM Spectrum Control Performance Manager reporting API method name of the api is invalid. The invalid value is the invalid value of parameter descriptive name of the parameter.
      • HWNPM0601E A request to continue the data retrieval can not be performed. Information for continuing the data retrieval does not exist.
      • HWNPM0602E Support for the device type device type name is not available in the Performance Manager reporting API function method name.
      • HWNPM0603E The performance reporting API method_name failed at time_of_failure as a result of an internal processing exception. The Performance Manager logs contain message message_ID that describes the internal processing exception.
      • HWNPM0604E The sort order parameter of a call to the performance reporting API method_name contains a value not included in the report columns list, at position list_item in the sort order list.
      • HWNPM0605E The report columns parameter of a call to the performance reporting API method_name contains a metric or counter type that is not available for a specified device of type device_type and specified component with type code component_type. The metric or counter type code is type_code.
      • HWNPM0606E Unable to instantiate performance reporting service service class name.
      • HWNPM0607E An error occurred while the performance data was being retrieved.
      • HWNPM0630E An invalid operator (operator identifier) was specified for the filter expression.
      • HWNPM0631E An invalid first operand (operand class) was specified for the filter expression. It must be a operand class class.
      • HWNPM0632E An invalid first operand was specified for the filter expression. The data type of the operand (data type) is invalid or unsupported.
      • HWNPM0633E An invalid second operand (operand class) was specified for the filter expression. It must be a operand class class.
      • HWNPM0650E The IBM Spectrum Control Performance Manager reporting API method name failed as a result of exception the related exception from a call to method method name, of the lower-level service name internal service.
      • HWNPM0651E The configuration data needed to generate the affected volumes and hosts report for the device device name was not found in the IBM Spectrum Control database.
      • HWNPM2000I Performance monitoring is enabled.
      • HWNPM2001E The IBM Spectrum Control Performance Manager is not operational.
      • HWNPM2002E An initialization error occurred.
      • HWNPM2003E Initialization of the Device server event service failed. No performance threshold exception alerts will be generated.
      • HWNPM2004E Initialization of the product scheduler status service failed. The status of performance monitors will not be updated in the GUI.
      • HWNPM2005E Initialization of the product configuration data service failed. Performance monitors cannot be started without this service.
      • HWNPM2006E Initialization of the product configuration data service failed. Performance monitors cannot be started without this service.
      • HWNPM2007E Initialization of the product counter data service failed for device type using agent type. Performance monitors will not be able to collect performance data from devices of this type.
      • HWNPM2008E Initialization of the product metadata service failed. Performance monitors cannot be started without this service.
      • HWNPM2009E Unable to instantiate lower level service service_class_name.
      • HWNPM2010E Unable to instantiate the collection logic implementation service class name.
      • HWNPM2011E Unable to instantiate the performance statistics data class class name.
      • HWNPM2012I The product is using trace log directory log directory name.
      • HWNPM2020W The performance monitor for device device name is not currently active, so a dynamic update of its monitor policy is not necessary.
      • HWNPM2021W The performance monitor for device device name is not currently active, so a dynamic update of its threshold policy is not necessary.
      • HWNPM2022E A performance monitor for device device name is already active. A new monitor for the same device cannot be started until the previous monitor completes or is cancelled.
      • HWNPM2023W The performance monitor for device device_name is not currently active.
      • HWNPM2024E Unable to find a monitor policy applicable to resource resource name.
      • HWNPM2025E Unable to find a threshold policy applicable to resource resource_name.
      • HWNPM2026I The performance monitor's primary process has failed unexpectedly. Attempting to recover from the failure.
      • HWNPM2027I The performance monitor threshold checker has failed unexpectedly. Attempting to recover from the failure.
      • HWNPM2028I The performance monitor purge process has failed unexpectedly. Attempting to recover from the failure.
      • HWNPM2029I Successfully recovered from the performance monitor failure.
      • HWNPM2030E Unable to recover from the performance monitor failure. The performance monitor for the storage resource will be shut down.
      • HWNPM2031E The performance monitor failed due to an internal error.
      • HWNPM2032W The performance monitor for device device name is not currently using the default monitor policy, so a dynamic update of the policy is not necessary.
      • HWNPM2033W The performance monitor for device device name is not currently using the default threshold policy, so a dynamic update of the policy is not necessary.
      • HWNPM2040E The device key specified for the snapshot vote ( key) was not found in the database. The device does not exist.
      • HWNPM2050E Failed to get the latest configuration data for device device_name.
      • HWNPM2051E No performance data was collected from device device_name for the current collection interval (time_stamp) because the performance monitor was stopped.
      • HWNPM2052E No performance data was collected from device device_name for the current collection interval due to an error. Data was last collected at time_stamp.
      • HWNPM2053E The new performance data collected from device device_name could not be saved in the database. Increase the size of the transaction log.
      • HWNPM2054E The new performance data collected from device device_name could not be saved in the database. Increase the size of the database lock list.
      • HWNPM2055E The new performance data collected from resource device name could not be saved.
      • HWNPM2056E No performance data was collected from device device name for the current performance monitor job duration. The performance monitor job status is set to 'failed'.
      • HWNPM2057E No performance data was collected from device device_name for the current collection interval because the performance monitor was stopped.
      • HWNPM2058E No performance data was collected from device device_name for the current collection interval due to an error.
      • HWNPM2060W The device does not support performance management for segment pool pool ID. Only incomplete performance data can be collected for array array ID.
      • HWNPM2061W The device does not support performance management for segment pool pool ID. Only incomplete performance data can be collected for device adapter DA ID.
      • HWNPM2062W Invalid error message saved in database
      • HWNPM2100E The performance monitor for resource device name cannot be started because configuration data for the resource is not available.
      • HWNPM2101E All agents that can collect performance data for resource device name are currently non-operational.
      • HWNPM2102E The performance monitor for resource device name cannot be started because the resource might not support the collection of performance data.
      • HWNPM2103W Agent agent name is non-operational. Attempting to find an alternative agent.
      • HWNPM2104I The performance monitor policy was adjusted due to agent limitations. Current values in effect are: interval-length=interval-length, frequency=frequency.
      • HWNPM2105E The performance monitor for resource resource name failed because the resource for enabling performance data collection cannot be reached.
      • HWNPM2106E The performance monitor for device device name failed because of errors trying to enable performance data collection on the device or device agent: error description
      • HWNPM2107E The performance monitor for device device name failed because of unrecognized errors trying to enable performance data collection on the device or device agent: error description
      • HWNPM2108E The performance monitor for resource resource name failed during shutdown because the resource cannot be reached for terminating data collection.
      • HWNPM2109E The performance monitor for resource resource name failed during shutdown because of errors during termination of performance data collection: error description
      • HWNPM2110E The performance monitor for resource resource name failed during shutdown because of unrecognized errors during termination of performance data collection: error description
      • HWNPM2111E The performance monitor for resource resource name failed because of errors retrieving the most recent configuration data for the resource.
      • HWNPM2112I Agent agent name was selected for performance data collection from resource resource name.
      • HWNPM2113I The performance monitor for resource resource name is starting in an active state.
      • HWNPM2114I The performance monitor for resource resource name is starting in a dormant state.
      • HWNPM2115I Monitor Policy: name="policy name", creator="policy creator", description="policy description"
      • HWNPM2116I Monitor Policy: retention period: sample data=length in days days, hourly data=length in days days, daily data=length in days days.
      • HWNPM2117I Monitor Policy: interval length=length in seconds secs, frequency=length in seconds secs, duration=length in hours hours.
      • HWNPM2118I Threshold Policy: name="policy name", creator="policy creator", description="policy description"
      • HWNPM2119I Threshold Policy: retention period: exception data=length in days days.
      • HWNPM2120I Threshold Policy: threshold name=name, component=component type, enabled=Yes or No, boundaries=critical stress boundary,warning stress boundary,warning idle boundary,critical idle boundary units.
      • HWNPM2121I Monitor Policy: interval length=length in seconds secs, frequency=length in seconds secs, duration=continue indefinitely.
      • HWNPM2122W No valid performance data was provided by the monitored resource. No performance data records were inserted into the database.
      • HWNPM2123I Performance data for resource timestamp date and time was collected and processed successfully. record count performance data records were inserted into the database repository.
      • HWNPM2124W Performance data continuity is broken. The device was possibly reset or rebooted. record count performance data records were discarded.
      • HWNPM2125W Aggregated performance values were calculated from the remaining metadata, but their accuracy can't be guaranteed.
      • HWNPM2126I The performance monitor for device device name is stopping because its intended duration has elapsed.
      • HWNPM2127I The performance monitor for device device name is stopping due to a user request.
      • HWNPM2128E The performance monitor for device device name is stopping due to an unexpected failure.
      • HWNPM2129I The performance monitor for device device name is stopping because of a shutdown request.
      • HWNPM2130W Failed to retrieve the latest configuration data for device device name.
      • HWNPM2131W Performance data could not be collected for device device name, because the device or data source cannot be reached (reason reason code). The current samples are skipped.
      • HWNPM2132W Performance data could not be collected for device device name. The current samples are skipped. (error description)
      • HWNPM2133W Performance data could not be collected for device device name due to an unknown error. The current samples are skipped.
      • HWNPM2134W The state of the performance monitor for resource resource name started, but the status of the performance monitor was not updated.
      • HWNPM2135W The state of the performance monitor for device device name has changed to 'active', but could not be recorded appropriately.
      • HWNPM2136W The performance monitor for the resource resource name generated a warning, but the status of the performance monitor was not updated.
      • HWNPM2137W The performance monitor for the resource resource name stopped, but the status of the performance monitor was not updated.
      • HWNPM2138W The performance monitor for the resource resource name completed the collection of data, but the status of the performance monitor was not updated.
      • HWNPM2139W The performance monitor for the resource resource name failed, but the status of the performance monitor was not updated.
      • HWNPM2140W The status of the performance monitor for the resource resource name was not updated.
      • HWNPM2141E The service is unavailable because an unexpected error occurred.
      • HWNPM2142E Performance data can't be collected for the resource resource name because the performance monitor was disabled.
      • HWNPM2143E The performance monitor for the resource resource name was started, but the status of the performance monitor was not updated and might not be shown in the GUI.
      • HWNPM2144W The performance data cannot be checked against the alert conditions, so no alerts can be generated.
      • HWNPM2145I The data is being collected by the data collector: data collector host.
      • HWNPM2146W Performance data could not be collected for device device name, the exact reason for the failure could not be determined. The current samples are skipped.
      • HWNPM2147W Performance data could not be collected for device device name, because of a bad target (device or agent) address. The current samples are skipped.
      • HWNPM2148W Performance data could not be collected for device device name, because of an unknown target address. The current samples are skipped.
      • HWNPM2149W Performance data could not be collected for device device name, because of an unreachable target address. The current samples are skipped.
      • HWNPM2150W Performance data could not be collected for device device name, because of an unresponsive target. The current samples are skipped.
      • HWNPM2151W Performance data could not be collected for device device name, because a communication time-out for communication that uses UDP rather than TCP. The current samples are skipped.
      • HWNPM2200I The performance monitor successfully collected the configuration data for the storage system with the following internal resources: number_of_pools pools, number_of_controllers controllers, number_of_device_adapters device adapters, number_of_ports ports, number_of_host_connections host connections, number_of_ranks ranks, number_of_arrays arrays, and number_of_volumes volumes.
      • HWNPM2201I The performance monitor successfully collected the configuration data for the storage system with the following internal resources: number_of_io_groups I/O Groups, number_of_nodes nodes, number_of_ports ports, number_of_host_connections host connections, number_of_pools pools, number_of_managed_disks managed disks, number_of_local_disks local disks, number_of_volumes volumes, and number_of_volume_copies volume copies.
      • HWNPM2202I The performance monitor successfully retrieved the configuration data for the switch. The following internal resources were found: number_of_trunks trunks, and number_of_ports ports.
      • HWNPM2203I The performance monitor successfully retrieved the configuration data for the storage system. The following internal resources were found: number_of_host_connections host connections, number_of_modules modules, number_of_ports ports, number_of_pools pools, and number_of_volumes volumes.
      • HWNPM2204I The performance monitor successfully retrieved the configuration data for the storage system. The following internal resources were found: number_of_nodes nodes, number_of_ports ports, and number_of_modules flash modules.
      • HWNPM2205I The performance monitor successfully retrieved the configuration data for the storage system. The following internal resources were found: number_of_ports ports, number_of_controllers controllers, number_of_volumes volumes, and number_of_disks disks.
      • HWNPM3000E There was a problem establishing the database connection.
      • HWNPM3001E An unexpected null row was returned from a database cursor.
      • HWNPM3002E An unexpected database exception occurred.
      • HWNPM3003E An unexpected database exception occurred on the snapshot database tables.
      • HWNPM3004E The snapshot ID could not be found.
      • HWNPM3500E The current transaction has been rolled back because of a deadlock.
      • HWNPM3501E The current transaction has been rolled back because of a timeout.
      • HWNPM3502E The current transaction has been rolled back because the database transaction log has been exhausted.
      • HWNPM3503E The current transaction has been rolled back because the database disk space has been exhausted.
      • HWNPM3600E The threshold identifier parameter value : threshold ID is not valid.
      • HWNPM3601E The target component type parameter value : component type is not valid for the threshold identifier : threshold ID passed to the affected volumes and hosts reporting function.
      • HWNPM3602E There was a problem retrieving the performance data needed to generate the affected volumes and hosts report for the device device name.
      • HWNPM3603E The sample volume performance data needed to generate the affected volumes and hosts report for the device device name was not found in the IBM Spectrum Control database.
      • HWNPM3604E There are no volumes associated with the specified target component, component name, in the IBM Spectrum Control database. Therefore, the resulting Affected Volumes and Hosts report will be empty.
      • HWNPM4000E Unable to retrieve the device agent that managed this device: device identifier.
      • HWNPM4001E Timeout while starting performance data collection for this device: device identifier.
      • HWNPM4002E Unable to start performance data collection for this device: device identifier.
      • HWNPM4003E Performance data collection has already been enabled for this device: device identifier.
      • HWNPM4004E Failed to enable performance data collection for this device: device identifier.
      • HWNPM4005I Successfully enabled performance data collection on the storage subsystem, using device access point SMI-S provider address.
      • HWNPM4006E An exception occurred while starting performance data collection for this device: device identifier.
      • HWNPM4007E A timeout occurred while stopping performance data collection for this device: device identifier.
      • HWNPM4008E Unable to stop performance data collection for this device: device identifier.
      • HWNPM4009E Performance data collection is not enabled for this device: device identifier.
      • HWNPM4010E Failed to disable performance data collection for this device: device identifier.
      • HWNPM4011I Successfully disabled performance data collection on the storage subsystem, using device access point SMI-S provider address.
      • HWNPM4012E An exception occurred while stopping performance data collection for this device: device identifier.
      • HWNPM4013E A timeout occurred while retrieving the status of the performance data collection for this device: device identifier.
      • HWNPM4014E Unable to retrieve the status of the performance data collection for this device: device identifier.
      • HWNPM4015I Performance data collection is not enabled for this device: device identifier.
      • HWNPM4016I Performance data collection is enabled for this device: device identifier.
      • HWNPM4017E Unable to determine the status of the performance data collection for this device: device identifier.
      • HWNPM4018E Failed to retrieve the status of the performance data collection for this device: device identifier.
      • HWNPM4019E A timeout occurred while polling the performance statistics for this device: device identifier.
      • HWNPM4020E Unable to retrieve the performance statistics for this device: device identifier.
      • HWNPM4021E No performance statistics available at the current time for this device: device identifier.
      • HWNPM4022E Failed to disable performance data collection for this device: device identifier.
      • HWNPM4023W A set of performance statistics data was empty for this device: device identifier.
      • HWNPM4024E An exception occurred while stopping performance data collection for this device: device identifier.
      • HWNPM4025E Unable to retrieve storage subsystem for this device: device identifier.
      • HWNPM4026E Failed to retrieve storage subsystem for this device: device identifier.
      • HWNPM4027E Failed to properly initialize counter data service for this device: device identifier.
      • HWNPM4028W Performance data cannot be collected because the security role authority of the user account user name for accessing device identifier is not sufficient.
      • HWNPM4051E Failed to obtain a reference to the Performance Manager Configuration Data Service for this device: device name.
      • HWNPM4052E Error occurred in trying to retrieve a device agent for this device: device name.
      • HWNPM4053E Unable to locate or retrieve the device agent that manages this device: device name.
      • HWNPM4054E Error occurred in trying to construct the poll state information for this device: device name.
      • HWNPM4055E Unable to construct the poll state information for this device: device name.
      • HWNPM4056E SMI-S provider operation triggered a timeout (step timeout= step timeout value seconds, operation timeout= total timeout value seconds,).
      • HWNPM4057E Mismatch in device identifier for this device: device name.
      • HWNPM4058E Failed to build the parameter Map for this device: device name.
      • HWNPM4059I Performance data collection has already been enabled for this device: device name.
      • HWNPM4060I Performance data collection was successfully started for this device: device name.
      • HWNPM4061E Performance data collection could not be started for this device: device name.
      • HWNPM4062I Performance data collection successfully stopped for this device: device name.
      • HWNPM4063W Parse exception in performance data collected this device: device name.
      • HWNPM4064E Wrong format in performance data collected for this device: device name.
      • HWNPM4065W number of null time stamps null time stamp(s)for performance data collected from the device were substituted by server time stamp(s).
      • HWNPM4066W count of null operational status null Port Operational Status value(s) for performance data collected from the device was/were substituted by default value(s).
      • HWNPM4081E A database cursor operation failed.
      • HWNPM4082E A database connect operation failed.
      • HWNPM4083E A database retrieve operation failed.
      • HWNPM4084E A database operation failed.
      • HWNPM4085E A database query operation failed.
      • HWNPM4086W A database query gave no result rows.
      • HWNPM4087W Missing or invalid association between SMI-S provider SMI-S provider URL and device device name. The configured SMI-S provider is inoperative, or may no longer be managing the specified device.
      • HWNPM4091E Encountered an error during execution of a discover service process.
      • HWNPM4092E Encountered exception during execution of a discover service process.
      • HWNPM4093E An input business object could not be converted to a CIMInstance.
      • HWNPM4100E Failed to initialize SVC counter data service discover service reference.
      • HWNPM4101E Failed to initialize SVC counter data service configuration service reference.
      • HWNPM4102E Failed to parse performance data file time stamp suffix: filename.
      • HWNPM4103E SMI-S provider operation timeout (timeout value seconds) expired.
      • HWNPM4104E Failed to retrieve SMI-S provider password for SVC counter data service access point: access point.
      • HWNPM4105E Encountered an error when communicating with the device agent.
      • HWNPM4106E Encountered invalid SVC component type: component type.
      • HWNPM4107E Failed to create performance data object: performance data object class.
      • HWNPM4108E TimeZone property is not defined for SVC cluster: cluster identifier.
      • HWNPM4109E SVC cluster TimeZone property is set to unrecognized value: timezone id and name.
      • HWNPM4110E StatisticsStatus property is not defined for SVC cluster: cluster identifier.
      • HWNPM4111E Failed to retrieve dump filename dump from SVC node node identifier (return code = return code).
      • HWNPM4112E IsConfigNode property is not defined for SVC node: node identifier.
      • HWNPM4113E Caught exception while processing SVC XML performance data.
      • HWNPM4114E SVC cluster cluster identifier has more than one configuration node.
      • HWNPM4115E SVC cluster cluster identifier does not have a configuration node.
      • HWNPM4116W Failed to associate SVC performance data from non-configuration node with SVC performance data from configuration node.
      • HWNPM4117W Encountered incomplete SVC performance data sample.
      • HWNPM4118E Firmware version information is not available for storage subsystem subsystem name. Performance data collection cannot proceed.
      • HWNPM4119E The firmware installed on storage subsystem subsystem name (firmware version) is not supported for performance data collection. The minimum level of firmware supported for performance data collection is firmware version.
      • HWNPM4150E Unable to retrieve storage subsystem for this device: device identifier.
      • HWNPM4151E Unable to determine the status of any performance data collection for this device: device identifier.
      • HWNPM4152E Performance data collection has already been enabled for this device: device identifier.
      • HWNPM4153E Performance data collection is not enabled for this device: device identifier.
      • HWNPM4154E Unable to start performance data collection for this device: device identifier.
      • HWNPM4155E Failed to enable performance data collection for this device: device identifier.
      • HWNPM4156E Unable to stop performance data collection for this device: device identifier.
      • HWNPM4157E Failed to disable performance data collection for this device: device identifier.
      • HWNPM4158E Unable to complete start performance data collection task for this device: device identifier.
      • HWNPM4159E Unable to complete stop performance data collection task for this device: device identifier.
      • HWNPM4160E Unable to complete performance data collection status query task for this device: device identifier.
      • HWNPM4161E Performance data collection is not enabled for this device: device identifier.
      • HWNPM4162E Unable to retrieve port performance statistics data for this device: device identifier.
      • HWNPM4163E Unable to retrieve volume performance statistics data for this device: device identifier.
      • HWNPM4164E Unable to retrieve rank performance statistics data for this device: device identifier.
      • HWNPM4165E Unable to retrieve performance statistics data for this device: device identifier.
      • HWNPM4166E Unable to complete polling for performance data collection task for this device: device identifier.
      • HWNPM4167E Unable to retrieve a device agent for this device: device identifier.
      • HWNPM4168E Failed attempt to use device device identifier counter data service with device different device identifier.
      • HWNPM4169E An invalid access point of device agent URL was used to acquire the agent for this device: device identifier.
      • HWNPM4170E The device agent's configuration for device identifier has changed from the given access point, device agent URL.
      • HWNPM4171E Performance data collection start task timed out after time seconds for device: device identifier.
      • HWNPM4172E Performance data collection stop task timed out after time seconds for device: device identifier.
      • HWNPM4173E Performance data collection check status task timed out after time seconds for device: device identifier.
      • HWNPM4174E Performance data collection poll task timed out after time seconds for device: device identifier.
      • HWNPM4175W An error occurred while parsing statistics for port port identifier. Its statistics will be excluded.
      • HWNPM4176W An error occurred while parsing statistics for volume volume identifier. Its statistics will be excluded.
      • HWNPM4177W An error occurred while parsing statistics for rank rank identifier. Its statistics will be excluded.
      • HWNPM4178E Failed to decrypt the device agent's password for device device identifier.
      • HWNPM4179W Performance data collection is currently enabled with errors for device device identifier.
      • HWNPM4180E Unable to retrieve key identifier value from the internal discover process.
      • HWNPM4181W number of ports of the port statistics from the device agent were unrecognized and were not included in this sample interval.
      • HWNPM4182W number of volumes of the volume statistics from the device agent were unrecognized and were not included in this sample interval.
      • HWNPM4183W number of ranks of the rank statistics from the device agent were unrecognized and were not included in this sample interval.
      • HWNPM4184E The device agent configured for this storage subsystem is not supported for this task. The current version, version number, is downlevel from from the minimum required, version number.
      • HWNPM4185W The device agent did not return all performance statistics data for this time interval. The incomplete data is being processed.
      • HWNPM4186W The ESS SMI-S provider did not return performance statistics data for both clusters for this time interval. The incomplete data is being processed.
      • HWNPM4187W The device does not support performance management for pool pool ID because it contains Space Efficient Volumes. Only incomplete performance data can be collected for array array ID.
      • HWNPM4188W The performance monitor was unable to collect performance statistics data from the device agent for the following component types: component list.
      • HWNPM4189W number of MDisks of the MDisk statistics from the device agent were unrecognized and were not included in this data collection interval.
      • HWNPM4191W number of modules out of total number of modules module statistics could not be retrieved from the device agent due to errors, and were not included in this data collection interval.
      • HWNPM4192W number of Drives of the drive statistics from the device agent were unrecognized and were not included in this data collection interval.
      • HWNPM4193W number of Volume-copies of the volume-copy statistics from the device agent were unrecognized and were not included in this data collection interval.
      • HWNPM4194W number of partitions of the partition statistics from the device agent were unrecognized and were not included in this data collection interval.
      • HWNPM4195W number of file systems of the file system statistics from the device agent were unrecognized and were not included in this data collection interval.
      • HWNPM4250E Failed to start the discover service for the SMI-S counter data service.
      • HWNPM4251E Failed to start the configuration service for the SMI-S counter data service.
      • HWNPM4252I Successfully returned access point device namer for device device name.
      • HWNPM4253I Successfully stopped SMI-S counter data service on access point access point for device device name.
      • HWNPM4254I The SMI-S counter data service is active on access point access point for device device name.
      • HWNPM4255I The SMI-S counter data service is inactive on access point access point for device device name.
      • HWNPM4256I Performance statistics successfully returned on access point access point for device device name.
      • HWNPM4257W Performance statistics not returned on access point access point for device device name.
      • HWNPM4258E No SMI-S providers found for device device name.
      • HWNPM4259E No storage subsystem found for device device name.
      • HWNPM4260E Failed to initialize the polling context for device device name.
      • HWNPM4261E Failed to retrieve the device capabilities for device device name.
      • HWNPM4262E A database exception occurred trying to retrieve the device capabilities for device device name.
      • HWNPM4263E A database exception occurred trying to retrieve the storage subsystem for device device name.
      • HWNPM4264W Failed to retrieve manifest for component type.
      • HWNPM4265E A database exception occurred trying to retrieve the Manifests for device device name.
      • HWNPM4266E No manifests found for device device name.
      • HWNPM4267E A database exception occurred trying to retrieve the discovery parameters for device device name.
      • HWNPM4268E Statistics record not correctly formatted due to exception local exception string.
      • HWNPM4269E Statistics record not correctly parsed due to exception local exception string.
      • HWNPM4270W The block storage statistics is not formatted for device device name.
      • HWNPM4271E The SMI-S provider found for device device name is not valid.
      • HWNPM4272E The storage subsystem found for device device name is not valid.
      • HWNPM4273W Discarding the stale performance statistics returned on access point access point for device device name.
      • HWNPM4274E The SMI-S provider found for this device has changed. Please re-run SMI-S provider discovery and probe.
      • HWNPM4300E Access to the agent or device has been denied. Ensure that valid credentials have been specified for agent agent name.
      • HWNPM4301E The device or device agent did not respond within the alotted time ( timeout value seconds).
      • HWNPM4302E New performance data is not yet available for the device. Statistics with time stamps later than time_stamp could not be found.
      • HWNPM4303E An agent API call (API name) failed while attempting to retrieve performance data for the device.
      • HWNPM4304E The request for performance data could not be retrieved from the queue by the data collector, probably this one is down or encountered problems connecting to the server.
      • HWNPM4502E Attempt to delete a default policy.
      • HWNPM4503E A database update operation failed.
      • HWNPM4504E A database insert operation failed.
      • HWNPM4505E A database delete operation failed.
      • HWNPM4506E A database cursor operation failed.
      • HWNPM4507E A database connect operation failed.
      • HWNPM4508E A database retrieve operation failed.
      • HWNPM4509E A database operation failed.
      • HWNPM4510E A database query operation failed.
      • HWNPM4511E A database commit operation failed.
      • HWNPM5200E The performance manager failed to publish event even name due to exception exception.
      • HWNPM5210E The performance manager failed to receive event from other modules.
      • HWNPM5211E The first parameter passed to this method is null.
      • HWNPM5212E The second parameter passed to this method is invalid.
      • HWNPM5400E The performance data collection identifiers are not valid integers: schedule ID {0}, schedule run number {1}, job run number {2}.
      • HWNPM5401E There was a problem establishing the database connection: {0}.
      • HWNPM5402E There was a problem creating the new run job entry: {0}.
      • HWNPM5403E There was a problem updating the run job entry {0}: {1}.
      • HWNPM5404E There was a problem closing the database connection: {0}.
      • HWNPM5405E There was a problem inserting a new run job into the database: {0}.
      • HWNPM5406E There was a problem executing an update for run job number {0} in the database.
      • HWNPM5407E There was a problem executing an update for run job number {0} in the database.
      • HWNPM5408E There was a problem executing an update for run number {0} in the database.
      • HWNPM5409I Successfully retrieved the configuration data for the elastic device. Found number of nodes Nodes and number of file systems File systems,
      • HWNPM5410W The performance monitor could not collect performance data for the following cluster nodes: nodes names.
      • HWNPM5411W The performance monitor could not collect performance data for the following filesystems: filesystem names.
      • HWNPM5413E The process failed because the userid or password provided failed to connect to the Export Tool.
      • HWNPM5414E The process failed because the Hitachi SVP was busy and did not return data or timed out.
    • REST API messages
      • BPCSS2075E You cannot create more than 5 API keys for a user
      • BPCSS2076E Server has encountered an unexpected error