HP Cisco MDS 9134 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Rel - Page 38

Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.21, OL-14116-01, Caveats

Page 38 highlights

Caveats Send documentation comments to [email protected] %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 vsan domain nh status sync_status req i/f 101 0x61(97) 1001 ALL_DONE OXID|FCID_RW 0 [ fc3/2 ] 102 0x62(98) 1002 ALL_DONE OXID|FCID_RW 0 [ fc3/5 ] 1001 0x9e(158) 101 NONE OXID|FCID_RW 0 [ fc2/16 ] 1002 0x98(152) 102 ALL_DONE OXID|FCID_RW 0 [ fc9/10] Number of DEP entries : 4 After waiting for a few minutes for IVR to stabilize, if the status column for the {vsan, domain} combination is NONE, then this problem has occurred the switch. 2. Withdraw the troubled domains using the ivr withdraw domain domain vsan vsan-id command. 3. Readvertise the withdrawn domains using the ivr refresh command. • CSCsk49634 Symptom: In rare cases, an FCIP link might flap on a network with high latency and a consistently high loss rate. Workaround: None. • CSCsk49761 Symptom: When IVR exports a new virtual domain and multiple border switches export that virtual domain, some of the entries in the Fibre Channel name server (FCNS) database that correspond to this virtual domain may have partial entries where the port type contains a dash (-). This can then lead to a lack of IVR communication between these devices and other IVR devices. Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.2(1) 38 OL-14116-01

  • 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]
38
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.2(1)
OL-14116-01
Caveats
%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
--------------------------------
vsan domain nh status sync_status req i/f
101 0x61(97) 1001 ALL_DONE OXID|FCID_RW 0 [ fc3/2 ]
102 0x62(98) 1002 ALL_DONE OXID|FCID_RW 0 [ fc3/5 ]
1001 0x9e(158) 101 NONE OXID|FCID_RW 0 [ fc2/16 ]
1002 0x98(152) 102 ALL_DONE OXID|FCID_RW 0 [ fc9/10]
Number of DEP entries : 4
After waiting for a few minutes for IVR to stabilize, if the status column for the {vsan, domain}
combination is NONE, then this problem has occurred the switch.
2.
Withdraw the troubled domains using the
ivr withdraw domain
domain
vsan
vsan-id
command.
3.
Readvertise the withdrawn domains using the
ivr refresh
command.
CSCsk49634
Symptom
: In rare cases, an FCIP link might flap on a network with high latency and a consistently
high loss rate.
Workaround
: None.
CSCsk49761
Symptom
: When IVR exports a new virtual domain and multiple border switches export that virtual
domain, some of the entries in the Fibre Channel name server (FCNS) database that correspond to
this virtual domain may have partial entries where the port type contains a dash (-). This can then
lead to a lack of IVR communication between these devices and other IVR devices.