HP Cisco MDS 9120 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Rel - Page 29

Threshold Configuration Flexibility, Changes in Existing Features, iSNS, iSCSI

Get HP Cisco MDS 9120 - Fabric Switch PDF manuals and user guides View all HP Cisco MDS 9120 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 29 highlights

Changes in Existing Features Send documentation comments to [email protected] Threshold Configuration Flexibility Cisco Fabric Manager Server allows two performance thresholds to be configured for throughput values for connections to end devices and inter-switch links (ISLs). Prior to Cisco Fabric Manager release 3.2(1) the user interface forced users to select either a fixed percentage or auto-baseline setting for both. Now end-users can set one threshold for a link based on a fixed percentage and the other using the auto-baseline setting. Changes in Existing Features iSNS As of Cisco SAN-OS Release 3.2(1), iSNS server and iSNS client features are deprecated. iSCSI As of Cisco SAN-OS Release 3.2(1), iSCSI should be enabled at the module level. SAN Device Virtualization Scalability Cisco SAN-OS Release 3.2(1) supports 800 SAN device virtualization (SDV) virtual devices, with 4 secondary real devices mapped to each SDV virtual device in a VSAN. Limitations and Restrictions This section lists the limitations and restrictions for this release. Data Mobility Manager Use the following guidelines when running Cisco Data Mobility Manager: • If you have a DMM configuration, the DMM job may transition to a Reset state during a supervisor switchover. In that case, the administrator should recover from the Reset state by following the instructions in the Cisco MDS 9000 Data Mobility Manager Configuration Guide. • A storage type job in DMM cannot be restored from a saved ASCII configuration. When a storage job is created in DMM, the SSM generates Virtual Initiators (VIs) for each storage type job. Each request to generate VIs can potentially return different VI pWWNs. As a result, if an ASCII configuration for a storage type job is reapplied, there is a possibility the the VIs generated by the SSM are different. In that case, the session configurations in the saved configuration are no longer valid. • Following a fcdomain restart disruptive command, the DMM process cleans up all configurations and transitions the DMM job in the affected VSAN to the Reset state. During the cleanup, some virtual devices are not deleted correctly, which results in an incomplete cleanup. As a result, when OL-14116-01 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.2(1) 29

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
Send documentation comments to [email protected]
29
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.2(1)
OL-14116-01
Changes in Existing Features
Threshold Configuration Flexibility
Cisco Fabric Manager Server allows two performance thresholds to be configured for throughput values
for connections to end devices and inter-switch links (ISLs). Prior to Cisco Fabric Manager release
3.2(1) the user interface forced users to select either a fixed percentage or auto-baseline setting for both.
Now end-users can set one threshold for a link based on a fixed percentage and the other using the
auto-baseline setting.
Changes in Existing Features
iSNS
As of Cisco SAN-OS Release 3.2(1), iSNS server and iSNS client features are deprecated.
iSCSI
As of Cisco SAN-OS Release 3.2(1), iSCSI should be enabled at the module level.
SAN Device Virtualization Scalability
Cisco SAN-OS Release 3.2(1) supports 800 SAN device virtualization (SDV) virtual devices, with 4
secondary real devices mapped to each SDV virtual device in a VSAN.
Limitations and Restrictions
This section lists the limitations and restrictions for this release.
Data Mobility Manager
Use the following guidelines when running Cisco Data Mobility Manager:
•
If you have a DMM configuration, the DMM job may transition to a Reset state during a supervisor
switchover. In that case, the administrator should recover from the Reset state by following the
instructions in the
Cisco MDS 9000 Data Mobility Manager Configuration Guide.
•
A storage type job in DMM cannot be restored from a saved ASCII configuration. When a storage
job is created in DMM, the SSM generates Virtual Initiators (VIs) for each storage type job. Each
request to generate VIs can potentially return different VI pWWNs. As a result, if an ASCII
configuration for a storage type job is reapplied, there is a possibility the the VIs generated by the
SSM are different. In that case, the session configurations in the saved configuration are no longer
valid.
•
Following a
fcdomain restart disruptive
command, the DMM process cleans up all configurations
and transitions the DMM job in the affected VSAN to the Reset state. During the cleanup, some
virtual devices are not deleted correctly, which results in an incomplete cleanup. As a result, when