
Known Functionality Issues
Problem
ID
Symptom
3743 Negative Baseline port values may result due to switch and/or port resets occurring
after baseline values have been cleared.
4250 When scrolling through the Trap log, the refresh of the window places the scroll
position at the bottom of the window. The workaround is to export the trap log and view
with an editor.
4338 SANbox Manager disappears unexpectedly, leaving behind a core file in the install
directory. This is caused by Sun Bug ID: 4641535 "JDK 1.4 Solaris: memory leak when
remote displaying".
The workaround is to define the environment variable J2DFONTSCALER=t2k before
running the GUI:
#export J2DFONTSCALER=t2k
#SANbox_Manager
4340 After running for approximately 18 hours, SANbox Manager had an out of memory
exception error. This is caused by Sun Bug ID: 4641535 "JDK 1.4 Solaris: memory leak
when remote displaying".
The workaround is to define the environment variable J2DFONTSCALER=t2k before
running the GUI:
#export J2DFONTSCALER=t2k
#SANbox_Manager
4411 When launching SANbox Manager, you may receive an error regarding your font
settings. For example,
"Cannot convert string monotype arial regular ..."
This is a configuration issue with X-windows and does not affect the functionality of
the GUI. The font path of the machine whose X-server is displaying the application
needs to have a directory which either has the specified font (Arial) or a font alias to
re-map it to another font.
For example, you might add the /usr/openwin/lib/X11/TrueType directory to the font
path on the machine that is displaying SANbox Manager (not the machine on which
the application is executing). This can be done using the sdtfontadm utility, and must
be done as root.
4533 Drag and drop from Zoning dialog to application window hangs the GUI. This is caused
by Sun Bug IDs: 4633417 and 4623377.
5478 Performing a "restore" and then selecting "browse" sometimes results in no files being
displayed in the working directory. To work around this problem, find the appropriate
archive file(s) and type them in manually.
5900 In certain cases, when the switch cannot respond to the application because of resource
limitations, the application will mistakenly present an error dialog saying "Max
sessions has been reached, continue loading?". The condition is transient and does not
affect the performance of the application or of the switch. When this bug occurs, the
necessary workaround to get the graphs displayed properly again, regardless of how
you answer the question, is to redisplay the fabric and graphs.
Comentarios a estos manuales