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

Caveats Send documentation comments to [email protected] 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. Workaround: Use the show ivr internal vdri vsan vsan-id domain domain command to determine which border switch is exporting the virtual domain. Then on any of the border switches that is exporting the virtual domain, enter the following command for each device that has a partial FCNS entry: switch(config)# ivr device pwwn pwwn fcns register vsan vsan-id In this example, pWWN is the port pWWN of the device and vsan-id is the VSAN that contains the incomplete FCNS entries. • CSCsk51193 Symptom: Following an upgrade to Cisco MDS SAN-OS Release 3.2(1) on a Cisco MDS 9124 switch, an interface is shown as up, but there is no FLOGI information for the port in the FLOGI database. Workaround: Set the port mode to F. • CSCin95789 Symptom: When you configure Cisco Traffic Analyzer to capture traffic on one or more interfaces on a Windows platform, the configuration web page might not show that the interface has been selected for traffic capture even though traffic capture on that interface is enabled. Workaround: Check the logs to clarify that the correct interface has been selected. • CSCsd21187 Symptom: If an iSNS client tries to register a portal separately after registering the network entity and storage node object with the Cisco MDS iSNS server, the portal registration might fail. Workaround: Register the portal at the same time as the network entity and storage node object registration. • CSCse31881 OL-14116-02 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.2(1a) 35