HP Cisco Nexus 5000 Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Re - Page 38

Limitations and Restrictions, IPv6, User Roles

Page 38 highlights

Limitations and Restrictions Send documentation comments to mdsfeedback-doc.com. verification, dual Fibre Channel fabric support, and management using Cisco Fabric Manager provide a complete solution that greatly simplifies and eliminates most downtime associated with data migration. Refer to the Cisco MDS 9000 Data Mobility Manager package fact sheet for more information. Limitations and Restrictions This section lists the limitations and restrictions for this release. The following limitations are described: • IPv6, page 38 • User Roles, page 38 • Data Mobility Manager, page 39 • Red Hat Enterprise Linux, page 39 • Generation 1 Module Limitation, page 39 • Schedule Job Configurations, page 39 • Solaris Windows Manager, page 39 • Upgrading to Recover Loss of Performance Manager Data, page 40 • Maximum Number of Zones Supported in Interop Mode 4, page 40 • InterVSAN Routing, page 40 • Java Web Start, page 40 • Cisco Storage Media Encryption, page 41 • VRRP Availability, page 42 • Using a RSA Version 1 Key for SSH Following an Upgrade, page 42 • CFS Cannot Distribute All CallHome Information, page 42 • Availability of F Port Trunking and F Port Channels, page 43 • Reserved VSAN Range and Isolated VSAN Range Guidelines, page 43 • Applying Zone Configurations to VSAN 1, page 44 • Running Storage Applications on the MSM-18/4, page 44 IPv6 The management port on Cisco MDS switches supports one user-configured IPv6 address, but does not support auto-configuration of an IPv6 address. User Roles In SAN-OS Release 3.3(x) and earlier, when a user belongs to a role which has a VSAN policy set to Deny and the role allows access to a specific set of VSANs (for example, 1 through 10), the user is restricted from performing the configuration, clear, execute, and debug commands which had a VSAN Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 4.1(3a) 38 OL-17675-05

  • 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
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54

Send documentation comments to mdsfeedback-doc.com.
38
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 4.1(3a)
OL-17675-05
Limitations and Restrictions
verification, dual Fibre Channel fabric support, and management using Cisco Fabric Manager provide a
complete solution that greatly simplifies and eliminates most downtime associated with data migration.
Refer to the Cisco MDS 9000 Data Mobility Manager package fact sheet for more information.
Limitations and Restrictions
This section lists the limitations and restrictions for this release. The following limitations are described:
IPv6, page 38
User Roles, page 38
Data Mobility Manager, page 39
Red Hat Enterprise Linux, page 39
Generation 1 Module Limitation, page 39
Schedule Job Configurations, page 39
Solaris Windows Manager, page 39
Upgrading to Recover Loss of Performance Manager Data, page 40
Maximum Number of Zones Supported in Interop Mode 4, page 40
InterVSAN Routing, page 40
Java Web Start, page 40
Cisco Storage Media Encryption, page 41
VRRP Availability, page 42
Using a RSA Version 1 Key for SSH Following an Upgrade, page 42
CFS Cannot Distribute All CallHome Information, page 42
Availability of F Port Trunking and F Port Channels, page 43
Reserved VSAN Range and Isolated VSAN Range Guidelines, page 43
Applying Zone Configurations to VSAN 1, page 44
Running Storage Applications on the MSM-18/4, page 44
IPv6
The management port on Cisco MDS switches supports one user-configured IPv6 address, but does not
support auto-configuration of an IPv6 address.
User Roles
In SAN-OS Release 3.3(x) and earlier, when a user belongs to a role which has a VSAN policy set to
Deny and the role allows access to a specific set of VSANs (for example, 1 through 10), the user is
restricted from performing the
configuration
,
clear
,
execute
, and
debug
commands which had a VSAN