Send documentation comments to mdsfeedback-doc@cisco.com.
36-19
Cisco MDS 9000 Family Fabric Manager Configuration Guide
OL-6965-03, Cisco MDS SAN-OS Release 2.x
Chapter 36 Management Software Troubleshooting
Other
Can I upgrade without losing my map settings?
When you upgrade from one version of Fabric Manager to another, there is a way to prevent the loss of
map settings (enclosure names, placement on the map, etc.)
The MDS 9000/db directory contains subfolders for each user (and one for fmserver). In these subfolders
are files for all discovered fabrics (*.dat) and maps (*.map). These are upgradable between versions. If
you need to clear the fabric cache, you should first export the enclosures to a file to avoid losing them.
Everything else aside from enclosures and map coordinates are stored on the switch. The preferences,
last opened, and site_ouis.txt format doesn’t change from release to release.
portChannelMembersDown No operational members.
portFabricBindFailure Port isolated due to fabric bind failure.
portGracefulShutdown Port shutdown gracefully.
portVsanMismatchIsolation An attempt is made to connect two switches using
non-trunking ports having different port VSANs.
rcfInProgres An isolated xE_port is transmitting a reconfigure
fabric, requesting a disruptive reconfiguration in
an attempt to build a single, non-isolated fabric.
Only the Interconnect_Ports can become isolated.
srcPortNotBound No source port is specified for this interface.
suspendedByMode Port that belongs to a port channel is suspended
due to incompatible operational mode.
suspendedBySpeed Port that belongs to a port channel is suspended
due to incompatible operational speed.
suspendedByWWN Port that belongs to a port channel is suspended
due to incompatible remote switch WWN.
swFailure Software failure.
tooManyInvalidFLOGIs Suspended due to too many invalid FLOGIs.
tovMismatch Link isolation due to TOV mismatch
trunkNotFullyActive Some of the VSANs which are common with the
peer are not up.
upgradeInProgress Line card upgrade in progress.
vsanInactive Port VSAN is inactive. The port becomes
operational again when the port VSAN is active.
vsanMismatchIsolation This VSAN is not configured on both sides of a
trunk port.
zoneMergeFailureIsolation The two Interconnect_Ports cannot merge zoning
configuration after having exchanged merging
request for zoning.
zoneRemoteNoRespIsolation Isolation due to remote zone server not
responding.
Table 36-2 Device Manager Tooltip Definitions (continued)
Tooltip Definition