Cisco Cisco Fabric Manager Release 4.2 Release Notes

This section lists the open and resolved caveats for this release. Use 

 to determine the status of a 

particular caveat. In the table, “O” indicates an open caveat and “R” indicates a resolved caveat.

CSCsk35725

Symptom: Fabric Manager takes 2 to 3 minutes to bring up the DMM job creation wizard in a setup 
with 25 switches, 400 enclosures, and 2400 entries in the name server. 

Workaround: None.

CSCsu72195

Symptom: When replaying DMM job configurations saved as an ASCII text file (after performing 
a write erase), the DMM job includes discrepancies. These discrepancies occur due to the interface 
and zone configurations that are in an area below the DMM job configuration in the ASCII text file. 
The configurations stored in the ASCII text file are replayed sequentially from top to bottom.

Workaround: None.

CSCtc23116

Symptom: When you install Cisco Fabric Manager on a Solaris host, an invalid JAR filename is 
generated, which causes the Java command to fail as follows:

java -Xms512m -Xmx512m -jar "4_2_1a_S15/tmp/software/m9000-fm-4.2.1.jar"

Unable to access jarfile 4_2_1a_S15/tmp/software/m9000-fm-4.2.1.jar

The HTML file lists the command incorrectly with m9000-fm-4.2.1.jar as the JAR filename. The 
correct filename should be m9000-fm-4.2.1a.jar.

Workaround: Run the command using m9000-fm-4.2.1a.jar as the filename instead of 
m9000-fm-4.2.1.jar, as in the following example:

java -Xms512m -Xmx512m -jar "4_2_1a_S15/tmp/software/m9000-fm-4.2.1a.jar"

The documentation set for the Cisco Fabric Manager includes the following documents. To find a Fabric 
Manager document online, access the following website:

O

O

O

O

–

O