RAS Message – StorNext Storage Manager Component : Configuration not supported

The StorNext Storage Manager component : Configuration not supported message is a RAS Event (called a Service Ticket in the StorNext GUI). This message is generated by the StorNext daily health check, which usually runs at 7:00 a.m. It may also arrive by e-mail, if e-mail notification is configured in the GUI.

When sent by e-mail, the message will look similar to this:

SR Ticket Number: 4716
SR Serial Number: mdc1.gm.local
    SR Problem Summary: QUANTUM software : StorNext Storage Manager component : Configuration not supported
    SR Problem Code: 010C : 41
    SR Error Code: Configuration not supported
    SR Severity: 1
    SR Notes: The number of affinities on managed file systems do not match for TSM and CVFS. The number of affinities found for TSM=0. The number of affinities found for CVFS=2.

The e-mail will include an attachment, which will look similar to the text and table that follow.

Affinity Configuration Violations

When a configuration violation occurs in the StorNext application, it must be repaired by stopping the system, editing the configuration, and then restarting the system. Below are specific configuration violations and recommended actions to repair each specific issue.

IF

THEN

There is more than one affinity on one stripe group:

You cannot have more than one affinity on one stripe group.

 

Examine all DSM configuration files (/usr/adic/DSM/config/*.cfgx). In any file that has the Storage Manager Flag set to true, and for every stripe group with more than one affinity, remove the extra affinities.

The file system does not contain at least one non-exclusive data stripe group:

The file system has at least one affinity, and therefore must contain at least one non-exclusive data stripe group.

Examine all DSM configuration files (/usr/adic/DSM/config/*.cfgx). In any file that has the Storage Manager Flag set to true, make sure at least one stripe group has the following configuration:

Metadata No
Journal No
Exclusive No

A file system contains both data stripe groups with affinities and data stripe groups without affinities:

A file system can contain data stripe groups with affinities, or data stripe groups without affinities, but it cannot contain both.

Examine all DSM configuration files (/usr/adic/DSM/config/*.cfgx). In any file that has the Storage Manager Flag set to true, make sure that either every stripe group has an affinity, or that every stripe group does not have an affinity.

There are more than two affinities across all managed file systems:

No more than two affinities across all managed file systems are allowed.

Examine all DSM configuration files (/usr/adic/DSM/config/*.cfgx). For all of the configuration files that have the Storage Manager Flag set to true, change the stripe group Affinities so there are no more than a total of two.

The number of affinities on managed file systems do not match for TSM and CVFS:

Examine all DSM configuration files (/usr/adic/DSM/config/*.cfgx). For all of the configuration files that have the Storage Manager Flag set to true, make sure the complete list of affinities matches the TSM affinity names found in the TIERDEF database table.

TSM does not recognize the CVFS managed file system affinity name:

Examine all DSM configuration files (/usr/adic/DSM/config/*.cfgx). For all of the configuration files that have the Storage Manager Flag set to true, make sure the complete list of affinities matches the TIERNAME fields found in the TSM TIERDEF database table.

An affinity in a policy class is not found in the TIERDEFtable:

Make sure the non-zero elements in the TIERLIST field of the TSM CLASSDEF tables all match the TIERNUM fields in the TSM TIERDEF table.

 

StorNext Storage Manager uses affinities for the Disk-to-Disk relocation feature. Disk-to-Disk relocation allows you to move data from one set of disks (a disk stripe group) to another, without affecting the file name space (such as when moving data from expensive fast disks to less expensive SATA disks).

To use this feature, you must have a managed file system with two affinities configured, which will be used as the source and the target for data migration.

What the StorNext Storage Manager component: Configuration not supported message indicates is that there is a discrepancy in the configuration of affinities between Storage Manager (TSM) and the (managed) file system (CVFS, also known as the SNFS or StorNext File System).

Troubleshooting

The RAS event message will tell you what the affinity configuration discrepancy is. In the example above, it states:

The number of affinities found for TSM=0. The number of affinities found for CVFS=2.

This means that in the Storage Manager database, there are no affinities configured (TSM=0), and in the file system's configuration file, there are two affinities enabled (CVFS=2).

Here are some important rules to keep in mind:

  • You must have either 2 affinities or no affinities.
  • The configured number must be the same in both your Storage Manager configuration and your managed file system configuration.
  • If you have affinities in the managed file system configuration, they must exist in all Stripe Groups, except for the exclusive metadata/journal Stripe Groups.

If discrepancies exist, you must correct them, by either deleting or adding affinities to satisfy these rules. Here are some steps you can take.

  1. You can add, display, or remove Storage Manager affinities using the fsaffinity command. Please note that you do not need these affinities if you do not have any Policy Classes with Disk-to-Disk relocation.

You can use the command

fsaffinity –l

to display (list) Storage Manager affinities,

and you can use the command

fsaffinity -d

to delete all affinities from the Storage Manager database, if they are not needed.

2. There are two ways to see if your managed file system has affinities configured.

  • Analyze the file system's configuration file (located in the /usr/cvfs/config/ directory and named <file system name>.cfgx.

In the file system's configuration file, the affinity entries that exist for individual Stripe Groups will look like this:

<snfs:affinities exclusive='false'>
<snfs:affinity>nowrite</snfs:affinity>
</snfs:affinities>

The example above shows a configured non-exclusive affinity named nowrite.

If this entire "affinities" section does not exist in the configuration file, it means that there are no file system affinities configured.

  • Use the StorNext Web GUI to list, add, or delete affinities, in either of these ways:
  • To see affinities for all file systems, select Tools > File Systems > Affinities.
  • To see affinities separately for each file system, select Configuration > File Systems > Edit and look under "Stripe Group / Disk Management" for each Stripe Group.

 

Audience: 
Public Unrestricted
Review/Evaluate: 
2016-11-03
Document Type: