Cisco Cisco Fabric Manager Release 4.2
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 f m - d o c f e e d b a c k @ c i s c o . c o m
10
Release Notes for Cisco Fabric Manager Release 4.2(7a)
OL-20325-08
Upgrading Cisco Fabric Manager
To install Fabric Manager on Windows, follow these steps:
Step 1
Click the Install Management Software link.
Step 2
Choose Management Software > Cisco Fabric Manager.
Step 3
Click the Installing Fabric Manager link.
Step 4
Select the drive for your CD-ROM.
Step 5
Click the FM Installer link.
Step 6
Follow the onscreen instructions provided in the Fabric Manager Installer 4.2(7a).
Note
If you have any folders open or Windows Explorer task windows open during the installation, you might
see the following error message:
see the following error message:
C:\Program Files\Cisco Systems\dcm\fm\help\shared\images\Thumbs.db (Access is denied)
To resolve this issue, close all open folders and open Windows Explorer task windows and restart the
FM Installer.
FM Installer.
Caution
Windows 2000 is incompatible with Fabric Manager Release 4.2(7a). If you install Fabric Manager in a
Windows 2000 environment, you are at risk of having an unstable Fabric Manager. We recommend that
you exit the installation and update your environment. See
Windows 2000 environment, you are at risk of having an unstable Fabric Manager. We recommend that
you exit the installation and update your environment. See
for the list of supported software that
has been tested with Cisco Fabric Manager. See
for the supported upgrade paths for Fabric
Manager.
To install Device Manager on your workstation, follow these steps:
Step 1
Enter the IP address of the switch in the Address field of your browser.
Step 2
Click the Cisco Device Manager link in the Device Manager installation window.
Step 3
Click Next to begin the installation.
Step 4
Follow the onscreen instructions to complete the installation of Device Manager.
Note
If you use a Java JDK instead of a JRE on Solaris, you might encounter a problem trying to install the
Device Manager from a web browser. This can happen because the installer heap limit of 256 MB is not
sufficient. If you have this problem, save the jnlp link as file, increase the heap limit to 512 MB, and run
javaws element-manager.jnlp at the shell prompt.
Device Manager from a web browser. This can happen because the installer heap limit of 256 MB is not
sufficient. If you have this problem, save the jnlp link as file, increase the heap limit to 512 MB, and run
javaws element-manager.jnlp at the shell prompt.