Cisco Cisco MDS 9000 SAN-OS Software Release 1.0
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
7
Release Notes for Cisco MDS 9000 Family Fabric Manager Release 4.1(3b)
OL-17675-06
New Features in Cisco MDS Fabric Manager Release 4.1(3b)
Note
If you are running Fabric Manager Server on Windows and using the PostgreSQL database, you should
examine your Windows Active Directory environment for organizational units (OUs) and make the
change recommended below to ensure that Fabric Manager Server does not periodically stop working.
examine your Windows Active Directory environment for organizational units (OUs) and make the
change recommended below to ensure that Fabric Manager Server does not periodically stop working.
On a Windows system, the Microsoft Active Directory applies a Group Policy Object (GPO) to the
Fabric Manager Server. The GPO does not recognize the local user PostgreSQL because it is not in the
GPO allow list. As a result, the GPO removes it, and the PostgreSQL database stops working.
Fabric Manager Server. The GPO does not recognize the local user PostgreSQL because it is not in the
GPO allow list. As a result, the GPO removes it, and the PostgreSQL database stops working.
To avoid this situation, you should move the Fabric Manager Server to its own OU and apply the same
feature settings as the original OU, but remove the local user account to log in as a service.
feature settings as the original OU, but remove the local user account to log in as a service.
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.
New Features in Cisco MDS Fabric Manager Release 4.1(3b)
This section briefly describes the new Fabric Manager features introduced in this release.
Cisco Fabric Manager Release 4.1(3b) supports managing delayed traps in the e-mail home feature in
multiple code families (SAN-OS 3.x and NX-OS 4.x) where the feature is available)
multiple code families (SAN-OS 3.x and NX-OS 4.x) where the feature is available)
For detailed information about this feature, refer to the
. The “New and Changed Information” section of the book includes a link to the
feature description.
Note
These release notes are specific to this release. For the complete Release 4.x documentation set, see the
section.
Resource Requirements
lists the minimum amount of resources (disk, memory, and CPU) required for both the server
and client, for Fabric Manager to operate satisfactorily.