HP Cisco Nexus 5000 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS R - Page 53

x45F0 corresponds to HPUX Volume Set Address <VBUS ID: 0xB, Target ID: 0xE, LUN: 0x0>.

Page 53 highlights

Caveats Send documentation comments to [email protected] Note This applies only to Terminal Server running in Application Mode. This issue does not affect users running a Terminal Server or Remote Desktop session in Remote Administration mode. Workaround: Before you install Fabric Manager, Fabric Manager Server, and Device Manager when using Microsoft Terminal Server in Application mode, you must install the application for global use. This is required when a Service is installed and invoked, and when creating a local dbadmin user. To activate this setting, do the following: 1. Before running the installation script from the Fabric Manager Installation CD, open a command-line prompt: Start > Run, then type cmd and press Return. 2. At the command prompt type: user /install. Note Do not close the command line window. This must remain open for the entire duration of the install. 3. Follow all steps needed to install Fabric Manager, Fabric Manager Server, and Device Manager. 4. When the installation is complete, at the command prompt, type user /execute and press Return. Then type exit. • CSCso63465 Symptom: FCP-CMD (for example, Inquiry) frames targeted to LUN 0x45F0 or LUN 0x50F0 are dropped by an MDS switch when traffic flows (egresses) through Generation 2 modules. LUN 0x45F0 corresponds to HPUX Volume Set Address . Workaround: Do not use LUN 0x45F0 and LUN 0x50F0 when Generation 2 modules are present in the fabric. • CSCsq20408 Symptom: After creating SANTap Control Virtual Targets (CVTs) or SANTap Data Virtual Targets (DVTs), the running-configuration and the startup-configuration are not synchronized. Output from the show startup-config command will be different from the output of the show running-config and the startup configuration will not display SANTap configuration information. Workaround: Issue the copy running-startup command whenever you create SANTap Control Virtual Targets (CVTs) or SANTap Data Virtual Targets (DVTs) so that the running configuration and the startup configuration are synchronized. • CSCsq54455 Symptom: On a DS-X9032 module where the SRAM parity error was seen, the SRAM parity error exceptions were logged continuously. Workaround: None. • CSCsq57352 Symptom: After upgrading from Fabric Manager Release 3.0(2a) to Fabric Manager Release 3.2(3a), the Fabric Manager client fails to reuse the map layout files produced by Release 3.0(2a). Renaming the map layout files will make them compatible with Fabric Manager Release 3.2(3a). OL-14116-10 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(2) 53

  • 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
  • 55
  • 56
  • 57
  • 58

Send documentation comments to [email protected]
53
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(2)
OL-14116-10
Caveats
Note
This applies only to Terminal Server running in Application Mode. This issue does not affect
users running a Terminal Server or Remote Desktop session in Remote Administration
mode.
Workaround
: Before you install Fabric Manager, Fabric Manager Server, and Device Manager when
using Microsoft Terminal Server in Application mode, you must install the application for global use.
This is required when a Service is installed and invoked, and when creating a local dbadmin user. To
activate this setting, do the following:
1.
Before running the installation script from the Fabric Manager Installation CD, open a
command-line prompt:
Start
>
Run
, then type
cmd
and press
Return
.
2.
At the command prompt type:
user /install
.
Note
Do not close the command line window. This must remain open for the entire duration
of the install.
3.
Follow all steps needed to install Fabric Manager, Fabric Manager Server, and Device Manager.
4.
When the installation is complete, at the command prompt, type
user /execute
and press
Return
. Then type
exit
.
CSCso63465
Symptom
: FCP-CMD (for example, Inquiry) frames targeted to LUN 0x45F0 or LUN 0x50F0 are
dropped by an MDS switch when traffic flows (egresses) through Generation 2 modules. LUN
0x45F0 corresponds to HPUX Volume Set Address <VBUS ID: 0xB, Target ID: 0xE, LUN: 0x0>.
Workaround
: Do not use LUN 0x45F0 and LUN 0x50F0 when Generation 2 modules are present
in the fabric.
CSCsq20408
Symptom
: After creating SANTap Control Virtual Targets (CVTs) or SANTap Data Virtual Targets
(DVTs), the running-configuration and the startup-configuration are not synchronized. Output from
the show
startup-config
command will be different from the output of the
show running-config
and the startup configuration will not display SANTap configuration information.
Workaround
: Issue the
copy running-startup
command whenever you create SANTap Control
Virtual Targets (CVTs) or SANTap Data Virtual Targets (DVTs) so that the running configuration
and the startup configuration are synchronized.
CSCsq54455
Symptom
: On a DS-X9032 module where the SRAM parity error was seen, the SRAM parity error
exceptions were logged continuously.
Workaround
: None.
CSCsq57352
Symptom
: After upgrading from Fabric Manager Release 3.0(2a) to Fabric Manager
Release 3.2(3a), the Fabric Manager client fails to reuse the map layout files produced by Release
3.0(2a). Renaming the map layout files will make them compatible with Fabric Manager Release
3.2(3a).