Cisco Systems MDS 9000 - page 477

Send documentation comments to mdsfeedback-doc@cisco.com.
36-9
Cisco MDS 9000 Family Fabric Manager Configuration Guide
OL-6965-03, Cisco MDS SAN-OS Release 2.x
Chapter 36 Management Software Troubleshooting
General
Why can’t I set both the D_S_TOV and E_D_TOV timers in the Device Manager?
If you modify both E_D_TOV and D_S_TOV at the same time, and the new D_S_TOV value is larger
than the old E_D_TOV value, you will get a WrongValue error. To work around this, you must change
the values separately.
Why are the columns in the Device Manager tables too small?
If Device Manager is trying to display a large table and your switch is running slowly, the table will come
up with the tabs being hidden. To work around this, you must resize the window to see the data.
Why are my fabric changes not propagated onto the map (for example, links
don't disappear)?
Fabric Manager shows that a device or port is down by displaying a red cross on that port or device.
However, Fabric Manager does not remove any information that's already discovered. You must
rediscover to correctly update the map.
Why does the PortChannel creation dialog become too small after several
uses?
After several uses, the MemberList TextBox (in the PortChannel Create Window) does not display as it
should. It changes from a long TextBox with a ComboBox for choosing ports, to a small square TextBox
that is too small to choose ports. This is a known problem and will be fixed in a future release. To work
around this problem, stop and restart Fabric Manager or Device Manager.
Why do I see errors when I have configured IPFC?
When IPFC and out of band management are configured, the Device Manager might not work using
SNMPv3 if you use the IPFC address. The workaround is either to use the management interface
(mgmt0) address, or to use SNMPv1/v2c over IPFC.
Why is Fabric Manager or Device Manager using the wrong network interface?
The problem happens because the underlying Java library picks a local interface arbitrarily. To work
around this, you can supply a command line argument before starting the Fabric/Device Manager. In the
desktop shortcut or shell script or batch file, add the following parameter "-Device
Managerds.nmsAddress="
For example, in Windows the line looks like ".javaw.exe -Device Managerds.nmsAddress=X.X.X.X -cp
.".
In desktop shortcuts, this length could exceed the maximum characters allowed. If this happens, delete
the "-Dsun.java2d.ddoffscreen=false" portion to make more space. Newer versions of Fabric Manager
(Release 1.2 and later) allow you to pick a preferred network interface.