User`s guide

FS0054601-00 E A-1
Appendix A
Frequently Asked Questions
Table A-1 lists some frequently asked questions (FAQs) about the SANblade
Manager application.
Table A-1. Frequently Asked Questions
Question Answer
On what platforms does
SANblade Manager run?
The SANblade Manager GUI runs on any platform that
supports the Java JVM 1.3 specification. The agent runs
only on Windows NT/2000, Solaris SPARC, Red Hat Linux,
and NetWare.
Can a SANblade Manager
GUI running on Red Hat
Linux talk to a Windows NT
host running the agent?
The SANblade Manager GUI running on any platform can
talk to any other platform running the agent. The SANblade
Manager GUI allows connections to different platforms at
the same time.
What does the blinking
heart on the connected
host mean?
SANblade Manager actively pings the agent at the specified
broadcast interval. This allows SANblade Manager to detect
agent presence on all platforms (even if agent shutdown
notification is not supported). It also allows the detection of
agent crashes as soon as possible. During an agent crash,
the notification may not have been sent to all the connected
GUIs.
Can the current contents of
the alarm and event logs be
saved to a file?
The alarm and event log files are stored in the SANblade
Manager install directory as a coma delimited list of entries
(one per line). The alarm log file is called alarms.txt and the
event log file is called events.txt.
Can SANblade Manager
be run as a Java applet?
No, SANblade Manager currently does not run as a Java
applet.
Does SANblade Manager
support SNMP?
No, SANblade Manager currently supports only the RPC
communication layer between the GUI and agent.