Cautions and restrictions for Server Priority Manager

Server Priority Manager monitors the I/O requests between the storage systems for Universal Volume Manager.

I/O requests issued from a port on the local storage system are not subject to the upper limit control, therefore I/Os are not restricted.

If you set the priority attribute to an external storage system port, all I/Os received on the port are controlled as the threshold control, and its performance data is added to the total number of I/Os of all prioritized ports. I/Os on the port will not be limited.

If you set the non-priority attribute to an external storage system port, I/O requests from the local storage system port are controlled as the upper limit value control, and I/Os on the port will be limited. On the other hand, I/O requests from a host are controlled by upper limit control, and I/Os on the port will be limited.

Server Priority Manager cannot be started when Performance Monitor is in real-time mode. Before starting Server Priority Manager, ensure that Time Range in the Monitor Performance window is not set to Use Real Time.

Server Priority Manager monitors the I/O requests between the storage systems for TrueCopy and Universal Replicator remote copy operations or global-active device.

I/O requests issued from a port on the primary storage system is not subject to the upper limit control, therefore I/Os are not restricted.

If you set the priority attribute to the storage system port at the secondary site, using the remote copy function (TrueCopy, Universal Replicator) or global-active device, all I/Os received on the port are controlled as the threshold control, and its performance data is added to the total number of I/Os (or the transfer rate) of all prioritized ports. I/Os on the port will not be limited.

If you set the non-priority attribute to the storage system port at the secondary site, using the remote copy function (TrueCopy, Universal Replicator) or global-active device, I/O requests from the storage system port at the primary site are not controlled by threshold control, and I/Os on the port will not be limited. On the other hand, I/O requests from a host are controlled by upper limit control, and I/Os on the port will be limited.

The I/O requests from the storage system ports at the primary site are not controlled by Server Priority Manager.

The Server Priority Manager main window has two tabs: the Port tab and the WWN tab. The settings on only one tab at a time can be applied to the storage system. If you make settings on both tabs, the settings cannot be applied at the same time. When you select Apply, the settings on the last tab on which you made settings are applied, and the settings on the other tab are discarded.

Server Priority Manager operations cannot be performed from the GUI and the CLI (SN and RAID Manager) at the same time. When you are using Server Priority Manager in RAID Manager, you cannot perform the setting required for WWN monitoring. If you change some settings for Server Priority Manager from RAID Manager, you cannot change Server Priority Manager and the monitoring WWN of Performance Monitor settings from the GUI. If you do, some settings might not appear. Before you change features that use Server Priority Manager, delete all Server Priority Manager settings from the currently used features.

To delete all settings specified from Storage Navigator, open the Server Priority Manager main window, and click either the Port or WWN tab, and then click the Initialize button to initialize the settings.

If one host bus adapter is connected to multiple ports and you specify an upper limit of the non-prioritized WWN for one port, the specified upper limit value will be applied to the host bus adapter settings for other connected ports automatically.

To make setting for connecting the host bus adapter's WWN and the port, use the WWN tab of the Server Priority Manager main window. Alternatively you can use the Monitored WWNs tab of the Performance Monitor main window. Note that the monitored WWN name displayed in Performance Monitor is displayed as the SPM name in Server Priority Manager.

There are differences in operations for SPM information between Storage Navigator and RAID Manager. The table below describes the differences. For details, see the Command Control Interface User and Reference Guide and the Command Control Interface Command Reference.

Operation target

Operation for SPM information

Storage Navigator

RAID Manager

Can be performed?

Can be performed?

Command Example

Port

Configure

Yes

No

-

Delete

Yes

No

-

Obtain

Yes

No

-

WWN

Configure

Yes*

Yes*

raidcom modify spm_wwn

Delete

Yes*

Yes*

raidcom delete spm_wwn

Obtain

Yes*

Yes*

raidcom get spm_wwn

LDEV

Configure

No

Yes

raidcom modify spm_ldev

Delete

No

Yes

raidcom delete spm_ldev

Obtain

No

Yes

raidcom get spm_ldev

* For Fibre Channel only.

When you perform one or more of the following operations, the upper limit value control might be disabled for about two minutes:

olh-note.gif The upper limit value control might be disabled when an abnormal condition occurs, such as a network failure or damage to the HBA or Fibre cable, as these conditions can cause the login or logout of the host. Resolve the cause of the unexpected login/logout behavior and then enable the upper limit value control.