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

Open Caveats, Symptom, Workaround, Resync Open Fabric, show startup, running-config startup-config

Page 50 highlights

Caveats Send documentation comments to mdsfeedback-doc.com. • CSCsw48060 Symptom: FCIP interoperability fails between two MDS switches, one running MDS NX-OS Release 4.1(1c) and the other running MDS NX-OS Release 4.1(3a), if the IP ACL configuration for an IPSec crypto map specifies TCP as the protocol, as in the following example: switch(config)# ip access-list acl-name permit tcp local-gige-ip-address local-mask remote-gige-ipaddress remote-mask FCIP interoperability does not fail if the IP ACL uses IP as the protocol, as in the following example: switch(config)# ip access-list acl-name permit ip local-gige-ip-address local-mask remote-gige-ipaddress remote-mask Workaround: This issue is resolved. • CSCsw78035 Symptom: When FlexAttach is enabled on the switch, the physical pWWN in the FCNS registration response is not rewritten with the virtual pWWN. Workaround: This issue is resolved. • CSCsx39090 Symptom: When you click Resync Open Fabric in Fabric Manager, the fabric configuration appears to be saved to the startup configuration, when in fact it is not saved. The same situation occurs when you exit Fabric Manager: the fabric configuration is not saved to the startup configuration. Workaround: This issue is resolved. Open Caveats • CSCsk35725 Symptom: Fabric Manager takes 2 to 3 minutes to bring up the DMM job creation wizard in a setup with 25 switches, 400 enclosures, and 2400 entries in the name server. Workaround: None. • CSCsq20408 Symptom: The show startup command displays aspects of the running configuration when SANtap is configured and/or SANtap objects are created. When a user creates objects such as a CVT or DVT, the configuration is showing in the running-configuration and in the startup-configuration without copying the configuration into the startup-configuration. Workaround: Issue a copy running-config startup-config command whenever you create objects such as a CVT or DVT so that the running-configuration and startup-configuration are synchronized. • CSCsu72195 Symptom: When replaying DMM job configurations saved as an ASCII text file (after performing a write erase), the DMM job includes discrepancies. These discrepancies occur due to the interface and zone configurations that are in an area below the DMM job configuration in the ASCII text file. The configurations stored in the ASCII text file are replayed sequentially from top to bottom. Workaround: None. Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 4.1(3a) 50 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.
50
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 4.1(3a)
OL-17675-05
Caveats
CSCsw48060
Symptom
:
FCIP interoperability fails between two MDS switches, one running MDS NX-OS
Release 4.1(1c) and the other running MDS NX-OS Release 4.1(3a), if the IP ACL configuration for
an IPSec crypto map specifies TCP as the protocol, as in the following example:
switch(config)#
ip access-list acl-name permit tcp local-gige-ip-address local-mask
remote-gige-ipaddress remote-mask
FCIP interoperability does not fail if the IP ACL uses IP as the protocol, as in the following example:
switch(config)#
ip access-list acl-name permit ip local-gige-ip-address local-mask
remote-gige-ipaddress remote-mask
Workaround
: This issue is resolved.
CSCsw78035
Symptom
: When FlexAttach is enabled on the switch, the physical pWWN in the FCNS registration
response is not rewritten with the virtual pWWN.
Workaround
: This issue is resolved.
CSCsx39090
Symptom
: When you click
Resync Open Fabric
in Fabric Manager, the fabric configuration
appears to be saved to the startup configuration, when in fact it is not saved. The same situation
occurs when you exit Fabric Manager: the fabric configuration is not saved to the startup
configuration.
Workaround
: This issue is resolved.
Open Caveats
CSCsk35725
Symptom
: Fabric Manager takes 2 to 3 minutes to bring up the DMM job creation wizard in a setup
with 25 switches, 400 enclosures, and 2400 entries in the name server.
Workaround
: None.
CSCsq20408
Symptom
: The
show startup
command displays aspects of the running configuration when SANtap
is configured and/or SANtap objects are created. When a user creates objects such as a CVT or DVT,
the configuration is showing in the running-configuration and in the startup-configuration without
copying the configuration into the startup-configuration.
Workaround
: Issue a copy
running-config startup-config
command whenever you create objects
such as a CVT or DVT so that the running-configuration and startup-configuration are synchronized.
CSCsu72195
Symptom
: When replaying DMM job configurations saved as an ASCII text file (after performing
a write erase), the DMM job includes discrepancies. These discrepancies occur due to the interface
and zone configurations that are in an area below the DMM job configuration in the ASCII text file.
The configurations stored in the ASCII text file are replayed sequentially from top to bottom.
Workaround
: None.