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

Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.21a, OL-14116-02, Caveats, Symptom

Page 34 highlights

Caveats Send documentation comments to [email protected] Symptom: If you bring up more than one link at a time between two VSANs that have overlapping domains and at least one of the switches is SDV enabled, one link will become isolated. The other links will come up, even though the domains are overlapping. In addition, the SDV virtual domains will change, causing traffic disruption on all devices associated with their old value. Workaround: Bring up multiple links between two switches one at a time. Verify that the first link came up correctly before attempting to bring up the next link. If the first link fails to come up because of a domain ID overlap, resolve the domain conflict and then try again to bring up the links. • CSCsh31236 Symptom: On a Cisco MDS 9513 Switch, when there are more than 512 ports on a single chassis, some ports with indexes between 0x200 and 0x20f may not come up. In addition, some ports with indexes between 0x0 and 0xf may show unexpected behavior when the ports with indexes between 0x200 and 0x20f are brought up. To display the port indexes, issue the show system internal fcfwd idxmap port-to-interface command. The port indexes appear in the column with the heading "glob idx." Workaround: Do not bring up more than 512 ports. To ensure that the port indexes between 0x0 and 0xf behave correctly, follow these steps: 1. Issue the shut command for ports with indexes 0x200 to 0x20f. 2. Issue the shut command for the ports with indexes 0x0 to 0xf, followed by the no shut command for the same port indexes. • CSCsi72048 Symptom: FCIP links may fail on an MDS 9216i switch that has compression set to auto when the other end of the FCIP link is terminated by an IPS-8 module. You may see the following message in the logs: %IPS_SB_MGR-SLOT1-3-CRYPTO_FAILURE: Heartbeat failure in encryption engine (error 0x1) %ETHPORT-5-IF_DOWN_SOFTWARE_FAILURE: Interface GigabitEthernet1/1 is down (Port software failure) %PORT-5-IF_DOWN_SOFTWARE_FAILURE: %$VSAN 1%$ Interface fcip99 is down (Port software failure) Workaround: If both ends of an FCIP link are not on an MPS-14/2 module, do not use mode 1 and auto. • CSCsk43922 Symptom: A data path processor (DPP) might fail on an MDS switch running SSI Release 3.2(1) on the SSM. The failure occurs after several days of running traffic when a misbehaving target sends unexpected frames well after the response has already been received from the same target. Workaround: None. • CSCsk49029 Symptom: If there is a request to export a domain while the same domain is being cleaned up, domain entries might not be programmed. As a result, communication between IVR devices might not occur. Workaround: Because the the programming request was lost, the only way to retrigger the programming is to withdraw the domain and refresh IVR. Follow these steps: 1. Identify domains with problem using the show ivr internal dep command. switch# show ivr internal dep Internal information for DEP FSM Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.2(1a) 34 OL-14116-02

  • 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

Send documentation comments to [email protected]
34
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.2(1a)
OL-14116-02
Caveats
Symptom
: If you bring up more than one link at a time between two VSANs that have overlapping
domains and at least one of the switches is SDV enabled, one link will become isolated. The other
links will come up, even though the domains are overlapping. In addition, the SDV virtual domains
will change, causing traffic disruption on all devices associated with their old value.
Workaround
: Bring up multiple links between two switches one at a time. Verify that the first link
came up correctly before attempting to bring up the next link. If the first link fails to come up
because of a domain ID overlap, resolve the domain conflict and then try again to bring up the links.
CSCsh31236
Sym
ptom: On a Cisco MDS 9513 Switch, when there are more than 512 ports on a single chassis,
some ports with indexes between 0x200 and 0x20f may not come up. In addition, some ports with
indexes between 0x0 and 0xf may show unexpected behavior when the ports with indexes between
0x200 and 0x20f are brought up. To display the port indexes, issue the
show system internal fcfwd
idxmap port-to-interface
command. The port indexes appear in the column with the heading “glob
idx.”
Workaround
: Do not bring up more than 512 ports. To ensure that the port indexes between 0x0
and 0xf behave correctly, follow these steps:
1.
Issue the
shut
command for ports with indexes 0x200 to 0x20f.
2.
Issue the
shut
command for the ports with
indexes 0x0 to 0xf, followed by the
no shut
command for the same port indexes.
CSCsi72048
Symptom
: FCIP links may fail on an MDS 9216i switch that has compression set to auto when the
other end of the FCIP link is terminated by an IPS-8 module. You may see the following message in
the logs:
%IPS_SB_MGR-SLOT1-3-CRYPTO_FAILURE: Heartbeat failure in encryption engine (error
0x1)
%ETHPORT-5-IF_DOWN_SOFTWARE_FAILURE: Interface GigabitEthernet1/1 is down (Port
software failure)
%PORT-5-IF_DOWN_SOFTWARE_FAILURE: %$VSAN 1%$ Interface fcip99 is down (Port software
failure)
Workaround
: If both ends of an FCIP link are not on an MPS-14/2 module, do not use mode 1 and
auto.
CSCsk43922
Symptom
: A data path processor (DPP) might fail on an MDS switch running SSI Release 3.2(1)
on the SSM. The failure occurs after several days of running traffic when a misbehaving target sends
unexpected frames well after the response has already been received from the same target.
Workaround
: None.
CSCsk49029
Symptom
: If there is a request to export a domain while the same domain is being cleaned up,
domain entries might not be programmed. As a result, communication between IVR devices might
not occur.
Workaround
: Because the the programming request was lost, the only way to retrigger the
programming is to withdraw the domain and refresh IVR. Follow these steps:
1.
Identify domains with problem using the
show ivr internal dep
command.
switch#
show ivr internal dep
Internal information for DEP FSM
--------------------------------