S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m
2-5
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
OL-9285-05
Chapter 2 Troubleshooting Installs, Upgrades, and Reboots
Troubleshooting Fabric Manager Installations
Please identify the cause of the failure, and try 'install all' again.
switch#
show install all failure-reason
Service: "cfs" failed to respond within the given time period.
switch#
If there are any failures for whatever reason (a save runtime state failure or linecard upgrade failure) once
the upgrade is already in progress, then the switch will be rebooted disruptively because the changes
cannot be rolled back. In such cases the upgrade has failed; you are not prompted to enter the
show
install all failure-reason
command, and entering it will not yield any useful information.
If you need additional assistance to determine why an upgrade is unsuccessful, collect the details from
the
show tech-support
command output and the console output from the installation, if available.
Troubleshooting Fabric Manager Installations
This section describes possible problems and solutions for a Fabric Manager installation failure. Fabric
Manager requires that the appropriate version of Sun JAVA JRE be installed, based on the Fabric
Manager release.
Table 2-1
shows the recommended JRE for Fabric Manager 2.x and later releases.
Fabric Manager and Device Manager do not operate properly with JRE 1.4.2_03 on Windows 2003.
Symptom
Fabric Manager or Device Manager will not start.
Table 2-1
Fabric Manager and Recommended JRE Version
Fabric Manager Release
Recommended JRE Version
2.0(1b) through 2.1(1b)
1.4.2_05
2.1(2) through 3.3(1)
1
1.
Release 3.3(1) includes support for JRE version 1.6.
1.5.x
Table 2-2
Fabric Manager or Device Manager Will Not Start
Symptom
Possible Cause
Solution
Device Manager will not
start.
Device Manager proxied through
Fabric Manager Server.
Uncheck the
Proxy SNMP through FM Server
check box in the Device Manager startup dialog
box, and restart Device Manager.