Supported SLA Commander Console System
Platforms1
| Vendor |
Series |
Processor |
| Microsoft |
Windows 2000 Server2 |
Intel Pentium III, 4, Xeon, or
compatible (1.5 GHz or better) |
| Windows Server 20032 |
Intel Pentium III, 4, Xeon, or
compatible (1.5 GHz or better) |
| Sun Microsystems |
Solaris 8 |
UltraSPARC III or compatible
(750 MHz or better) |
| |
Solaris 9 |
UltraSPARC III or compatible
(750 MHz or better) |
NOTE: See
Release Notes for client web browser requirements.
1 OPNET software is
supported only on the English language version
of each operating system.
2 SLA Commander is
not supported running under VMware emulation of Windows.
Required System Patches
User Authentication
Supports the following methods of user authentication: Local, LDAP (all versions).
Windows – SLA Commander Console
(Controller) Configuration
| |
Processor2 |
RAM3 |
Free Disk
Space4 |
| Minimum |
Intel
Pentium III –1.5 GHz |
Controller:512
MB |
Controller:200
MB |
| Database:512
MB |
Database:6
GB |
| Recommended1 |
Intel Pentium
4 –2+ GHz |
Controller:512
MB |
Controller:250
MB |
| Database:1+
GB |
Database:10+
GB |
NOTE: A
dedicated system is recommended for the
SLA Commander Controller on Windows. The
Controller and Database can reside on the
same system or on two separate systems.
When both reside on the same system, combine
RAM, combine Free Disk Space, and double
Processor specifications.1
1 A dual-processor configuration
is recommended if SLA Commander and the
back-end Oracle database are to reside
on the same system.
2 SLA Commander will
not operate on systems with the
Intel Itanium processor.
3 SLA Commander performance
will improve with more available
memory as the total number of
active tests increases.
4 Required database
storage will increase with the
total number of enabled tests
and the amount of historical
data maintained. SLA Commander
performance will improve when
a large database is distributed
across multiple disk drives.
Solaris - SLA Commander Console (Controller) Configuration
| |
Processor2 |
RAM3 |
Free Disk
Space4 |
| Minimum |
UltraSPARC III –750
MHz |
Controller:512
MB |
Controller:325
MB |
| Database:512
MB |
Database:6
GB |
| Recommended1 |
UltraSPARC
III –1.2+ GHz |
Controller:
512 MB |
Controller:350
MB |
Database:
1+ GB |
Database:10+
GB |
NOTE: SLA
Commander Controller and Database can reside
on the same system or on two separate systems.
When both reside on the same system, combine
RAM, combine Free Disk Space, and double
Processor specifications.1
1 A multi-processor configuration
is recommended if SLA Commander and the
back-end Oracle database are to reside
on the same system.
2 SLA Commander will
not operate on systems with the
Intel Itanium processor.
3 SLA Commander performance
will improve with more available
memory as the total number of
active tests increases.
4 Required database
storage will increase with the
total number of enabled tests
and the amount of historical
data maintained. SLA Commander
performance will improve when
a large database is distributed
across multiple disk drives.
SLA Commander Console Database Requirements
| Vendor Software |
System Platform |
Supported Version |
Minimum Patch Level |
| Microsoft SQL Server1 |
Windows |
SQL Server 2000 Standard Edition |
Service Pack 3 |
| Oracle Database2 |
Windows or Solaris |
Oracle 8i Enterprise
Edition
(excluding Windows 2003) |
Release 3
(version 8.1.7.4) |
| |
Oracle 9i Enterprise Edition |
Release 2
(version 9.0.1.4) |
1 Contact
Microsoft Corporation for information about
SQL Server 2000 licensing and system requirements.
2 Contact Oracle Corporation
for information about Oracle
8i and 9i licensing and system
requirements.
Windows - SLA Commander Test Engine Configuration1
| |
Processor |
RAM2 |
Free Disk
Space |
| Minimum |
Intel Pentium III –900
MHz |
256 MB |
30 MB |
| Recommended |
Intel Pentium 4 –1.5+
GHz |
512 MB |
50 MB |
| Minimum for Agenda playback |
Intel Pentium 4 –1.5+
GHz |
1 GB |
100 MB |
1 Test Engines do not need to reside on dedicated systems.
2 SLA Commander performance
will improve with more available memory
as the total number of active tests increases.
Solaris – SLA
Commander Test Engine Configuration1
| |
Processor |
RAM2 |
Free Disk
Space |
| Minimum |
UltraSPARC III –750
MHz |
256 MB |
75 MB |
| Recommended |
UltraSPARC III –1.2+
GHz |
512 MB |
100 MB |
1 Test Engines do not need to reside on dedicated systems.
2 SLA Commander performancewill improve with more available memory
as the total number of active tests
increases.
SLA Commander Maximum Configuration Guidelines
| Test
Engines
per Controller |
Tests per Controller |
Tests per Test Engine |
| 50 |
3,000 per minute |
100 per minute1,2,3 |
NOTE:
These guidelines are based on tested maximums
using available lab system configurations. Larger
Controller and Database systems, in terms of
processors, RAM, disk drives and space, may be
able to support larger numbers of active tests
and additional Test Engines.
1 Of this number, ½ may
be enabled for ACE captures.
2 Of this number, ¼ may
be for Agenda emulation playback.
3 Only 1 Agenda can be played
back by Internet Explorer at a time.
|
|
