Sunvts; Sunvts Software And Security - Sun Microsystems Sun Fire V210 Manual

SunVTS

SunVTS is a software suite that performs system and subsystem stress testing. You
can view and control a SunVTS session over a network. Using a remote machine,
you can view the progress of a testing session, change testing options, and control all
testing features of another machine on the network.
You can run SunVTS software in three different test modes:
Connection mode verifies the presence of device controllers on all subsystems. This
typically takes no more than a few minutes and is a good way to "sanity check"
system connections.
Functional mode exercises only the specific subsystems you choose. This is the
default mode.
Auto Config mode automatically detects all subsystems and exercises them in one
of two ways:
Since SunVTS software can run many tests in parallel and consume many system
resources, you should take care when using it on a production system. If you are
stress-testing a system using SunVTS software's Comprehensive test mode, do not
run anything else on that system at the same time.
A server must be running the Solaris operating environment for SunVTS software to
be able to test it. Since SunVTS software packages are optional, they may not be
installed on your system. See "To Find Out Whether SunVTS Is Installed" on page 50
for instructions.

SunVTS Software and Security

During SunVTS software installation, you must choose between Basic or Sun
Enterprise Authentication Mechanism (SEAM) security. Basic security uses a local
security file in the SunVTS installation directory to limit the users, groups, and hosts
permitted to use SunVTS software. SEAM security is based on the standard network
authentication protocol Kerberos and provides secure user authentication, data
integrity and privacy for transactions over networks.
48 Sun Fire V210 and V240 Servers Administration Guide • April 2003
Confidence testing – performs one pass of tests on all subsystems, and then
stops. For typical system configurations, this requires one or two hours.
Comprehensive testing – tests all subsystems repeatedly for up to 24 hours.