Cautions and restrictions for
Server Priority Manager
-
Using
Universal Volume 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.
- Real-time monitoring mode
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.
- Remote copy ports
When the remote copy functions (TrueCopy, TrueCopy for Mainframe, Universal Replicator, Universal Replicator for Mainframe) or global-active device are used in your environment, Server Priority Manager monitors write I/O requests issued from the initiator ports of your storage system.
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 an RCU target 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 (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 an RCU target port, I/O requests from the initiator port 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.
-
Statistics for storage system ports at the primary site
The I/O requests from the storage system ports at the primary site are not controlled by Server Priority Manager.
- Settings on the
Server Priority Manager main window
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.
- Using
RAID Manager
Do not perform Server Priority Manager operations from RAID Manager and the GUI at the same time.
NoteWhen 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 Device Manager - Storage Navigator, open the Server Priority Manager main window, and click either the Port or WNN tab, and then click the Initialize button to initialize the settings.
- Connecting one HBA to multiple ports
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.
- Setting the connection between host bus adapter and port
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.
-
Differences of operations between
Device Manager - Storage Navigator and
RAID Manager
There are differences in operations for Server Priority Manager information between Device Manager - Storage Navigator and RAID Manager. The table below describes the differences. For details, see the RAID Manager User Guide.
|
Object |
Operation |
Device Manager - Storage Navigator |
RAID Manager | |
|
Operable |
Operable |
Command example* | ||
|
port (FC only) |
Set Server Priority Manager information |
Yes |
No |
- |
|
Delete Server Priority Manager information |
Yes |
No |
- | |
|
Get Server Priority Manager information |
Yes |
No |
- | |
|
wwn (FC only) |
Set Server Priority Manager information |
Yes |
Yes |
raidcom modify spm_wwn |
|
Delete Server Priority Manager information |
Yes |
Yes |
raidcom delete spm_wwn | |
|
Get Server Priority Manager information |
Yes |
Yes |
raidcom get spm_wwn | |
|
LDEV (FC and iSCSI) |
Set Server Priority Manager information |
No |
Yes |
raidcom modify spm_ldev |
|
Delete Server Priority Manager information |
No |
Yes |
raidcom modify spm_ldev | |
|
Get Server Priority Manager information |
No |
Yes |
raidcom spm_ldev | |
|
* For details, see RAID Manager User Guide. | ||||
When you perform one or more of the following operations, the upper limit value control might be disabled for about two minutes:
- Adding, replacing, or removing cache memory
- Changing the system configuration
- Updating the microcode/firmware
- Replacing MP blade /controller
- Adding, replacing, or removing the channel adapter
- Powering on and off the storage system
