Name of the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
608
Troubleshooting After Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
609
SMI-S Switches Must Be Removed
and Rediscovered After Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting Discovery and
Discovery Data Collection/Get Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Names are Changed After Running Discovery Data Collection/Get Details for Cisco SMI-S Switches 610
Configuring E-mail Notification for Discovery Data Collection/Get Details . . . . . . . . . . . . . .
610
Increasing the Time-out Period and Number
of Retries for Switches in Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
611
“Connection to the Database Server Failed” Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
613
DCOM Unable to Communicate with Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Duplicate Listings for Brocade Switches in Same Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . .
614
Element Logs Authentication Errors During Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMC Device Masking Database Does Not Appear
in Topology (AIX Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Management Server Does Not Discover Another
Management Server's Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Microsoft Exchange Drive Shown as a Local Drive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unable to Discover Microsoft Exchange Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Nonexistent Oracle Instance Is Displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Requirements for Discovering Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
615
Do Not Run Overlapping Discovery Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
"This storage system uses unsupported
firmware. ManagementClassName: ???"
Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting Topology Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About the Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
616
No Stitching for Brocade Switches with Firmware 3.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . .
619
Link Between a Brocade Switch and a Host
Disappears from the Topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Incorrect Topology Sometimes Displayed for CNT Switches . . . . . . . . . . . . . . . . . . . . . . . .
Unable to Find Elements on the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unable to See Path Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
620
Device Locking Mechanism for Brocade Element
Manager Query/Reconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A Discovered Sun StorEdge A5000 JBOD Does
Not Display Its WWN Properly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unable to Monitor McDATA Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unable to Detect a Host Bus Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Navigation Tab Displays Removed Drives as Disk Drives . . . . . . . . . . . . . . . . . . . . . . . . . .
621
Unable to Obtain Information from a CLARiiON Storage System . . . . . . . . . . . . . . . . . . . . .
Discovery Fails Too Slowly for a Nonexistent IP Address. . . . . . . . . . . . . . . . . . . . . . . . . . .
“CIM_ERR_FAILED” Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
622
Re-establishing Communication with EFCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
623
Communicating with HiCommand Device Manager Over SSL . . . . . . . . . . . . . . . . . . . . . . .
624
xx