12.1 System Requirements
Supported Platforms¹
| Vendor | OS | Processor |
|---|---|---|
| Sun Microsystems | Solaris 8, 9, 10 | UltraSPARC or later processor (e.g. UltraSPARC II, UltraSPARC III) |
| Microsoft | Windows 2000 Professional | x86 or EM64T (Intel Pentium III, 4, Xeon, or compatible, 500 Mhz or better) x86 AMD or AMD64, 500 MHz or better |
| Windows XP Professional | ||
| Windows XP Professional x64 Edition | ||
| Windows 2000 Server | ||
| Windows Server 2003 | ||
Windows Server 2003 x64 Edition |
||
| Red Hat | Red Hat Enterprise Linux 3
(v2.4 Linux kernel) Red Hat Enterprise Linux 4 (v2.6 Linux kernel) |
x86 or EM64T (Intel Pentium III, 4, Xeon, or compatible, 500 Mhz or better) x86 AMD or AMD64, 500 MHz or better |
| Fedora Project | Fedora Linux 3 (v2.4 Linux kernel) Fedora Linux 4 (v2.6 Linux kernel) |
¹Note:
1. OPNET software is supported on the English language version
of each operating system
Required System Patches
| Vendor | OS Version | Patch Number/Name |
|---|---|---|
| Sun Microsystems | Solaris 8: | Solaris 8 Recommended Patch Cluster from
18-Mar-2004 or later Solaris 8 Patch 108434-18 or later Solaris 8 Patch 108435-18 or later¹ Solaris 8 Patch 111308-04 or later² |
| Solaris 9 | Solaris 9 Patch 111711-12 or
later Solaris 9 Patch 111712-12 or later¹ |
|
| Microsoft | Windows 2000 Professional | Service Packs 1, 2, and 4 are supported but not required. |
| Windows XP Professional | Service Pack 1 is required; Service Pack 2 is supported but not required. |
2. Patch 111308-04 is required only if using the Parallel Discrete-Event Simulation Kernel.
System Configuration: OPNET Modeler
RAM
128 MB required, 256 MB recommended*
System File Space
1GB (Windows), 1.2GB (Solaris), 1.4GB (Linux)
Up to 2GB of free disk space
may be required during installation on Windows; up to 3GB
of free disk space on Solaris and Linux.
Working File Space
100 MB or more for temporary and log files
Display
Resolution: 1024x768 minimum
*As network size and number of traffic demands increases, memory requirements for discrete event simulation, Flow Analysis, NetDoctor, and design features increase as well. Larger application trace sizes require more memory for processing in ACE. In these situations, adequate system performance may require larger RAM configurations.
Other Requirements: OPNET Modeler
Supporting software
| OS | Compiler |
|---|---|
| Solaris | ANSI
C or C++ Compiler Note: gcc users must use gcc version 2.95 or higher g++ users must use g++ version 2.95 or higher SunPro users must use SunPro 5.X or higher for C++ code |
| Linux | gcc 3.4 or higher |
| 2000,
XP |
Microsoft
Visual C/C++ 6.x, Visual Studio .NET, or Visual Studio 2005 For instructions on configuring Visual Studio 2005, please see FAQ 1685, [What are the proper system environment settings for Microsoft's Visual Studio 2005 compiler to work the 12.0 release of OPNET?] Note: OPNET highly recommends the Professional Edition of the Visual C/C++, .NET, or Visual Studio compiler. Using the Standard Edition of the compiler, which does not allow for code optimizations, will result in slower Discrete-Event Simulations. More information can be found on the Microsoft
web site. |
Note
TCP/IP networking software is required
Special Requirements (Solaris and Linux)
On Solaris installations the license file must be stored in either
the /opt or /var/adm directory. The directory that is chosen
must be located on a local hard drive or partition, may not be
a symlink, and may not be a network mounted partition.
On Linux installations, the license file must be stores on a disk local to the operating system installation (non-network drive) and must be accessible via the /opt/OPNET_license directory name.
Browser
Firefox 1.0.6 or higher, Internet Explorer
5.0 or higher, or a compatible browser that supports Style
Sheets.
External Software Compatibility
Import of Network Topology
Device Configuration Import is available for
the following devices: Cisco IOS versions 10.0 and above,
Cisco CatOS version 4.1 and above, Cisco PIX 6.0 and above,
and Juniper JunOS 4.0 and above.
Requires eXpress Data
Import (XDI) license.
eXpress Data Import (XDI) module
Network Traffic
| PRODUCT | VERSION | NOTES |
| HP OpenView Performance Insight | 4.6 | Import of link loads. |
| InfoVista | 2.2, 3.1 | Import of link loads |
| MRTG | 2.9.25 or higher |
Import of link loads. rrdtool-based MRTG is not supported. |
|
cflowd |
2.1 | Import of traffic flows. |
|
CA Network Health, and eHealth |
4.8, 5.0.2, 5.6.5, 5.7 |
Import of link loads. |
| NetScout nGenius | 2.0, 3.0.1, 3.1, and 3.2 |
Import of traffic flows. Import of sFlow data from Foundry devices and NetFlow data from Cisco devices is supported if this information is gathered by NetScout probes and stored in the nGenius database. |
| Cisco NetFlow Collector | 3.0 to 5.0.2 | Import of traffic flows. |
| Fluke Networks OptiView Console | 6.5.1 | Import of Traffic Flows. Only ATM OC3 probe supported. |
Network Topology
Device Configuration Import is
available for the following devices: Cisco IOS versions 10.0
and above, Cisco CatOS version 4.1 and above, Cisco PIX 6.0
and above, and Juniper JunOS 4.0 and above. Requires eXpress
Data Import license.
Application Characterization Environment
Supported
Formats
ACE Decode Module (ADM)
The ACE Decode Module is not supported on
Solaris.
High Level Architecture (HLA) Module
Compatible with the following RTIs: DMSO RTI-1.3NGv6,
MaK RTI 2.1 through 3.1.1
Server Specialized Models
Compatible with import of server monitoring data as follows:
| PRODUCT | VERSION | NOTES |
| BMC Patrol Perform |
6.5 | Import of performance data for servers running on Solaris, HPUX, AIX, Linux, and Windows 2000/NT 4. |
| HP OpenView Performance Agent | c.04.50 | Import of performance data running on Solaris, HP/UX, AIX, Linux, and Windows 2000/NT4. |
| NetIQ AppManager | 5.01 | Import of performance data for servers running on Windows 2000. |
| Concord SystemEDGE | 4.1 | Import of live performance data running on Solaris, HP/UX, AIX, Linux, and Windows 2000/NT4. |
| SAS MXG | SAS: 9.1, MXG: 23.07 | Import of performance data for mainframes running z/OS and OS/390 |
| CA NeuMICS | 11 | Import of performance data for mainframes running z/OS and OS/390 |
| CA Unicenter NSM | 3.1 or 11.0 |
3DNV
3D Network Visualizer is supported on Windows
2000 SP2 and Windows XP. Modeler and ODK applications and
simulations that communicate with the Visualizer are supported
on Windows 2000, Windows XP, and Solaris 8 or 9.If
used in the context of HLA cosimulations, requires use of a DMSO-certified
1.3 HLA RTI (Run-Time Infrastructure) for each federate. The
3D Network Visualizer counts as a federate separate from a
simulation.
Other requirements:
CPU:1GHz minimum
RAM: 256MB minimum, 512MB or more if using complex 3D models (such as provided human models)
Video Card: OpenGL 1.2-compliant graphics card, recommended with 128-bit memory access and 128 MB of VRAM
System File Space: 800MB (including provided OpenFlight models and terrain databases)
Multi-Federate Logger for 3DNV
The Multi-Federate Logger for 3DNV is supported
on Windows 2000 and Windows XP. If used in the context of
HLA cosimulations, requires use of a DMSO-certified 1.3 HLA RTI
(Run-Time Infrastructure) for each federate. The Logger counts
as a federate separate from a simulation.
Other requirements:
CPU: 500 MHz minimum
RAM: 64 MB minimum.
System File Space:40 MB
System-in-the-Loop Module (SITL)
The System-in-the-Loop module is supported on Windows 2000 SP2, Windows XP , and Windows Server 2003. Use of the System-in-the-Loop module also requires a network interface card.
Terrain Modeling Module
Compatible with the following terrain
data formats:
| Format | NOTES |
| OpenFlight v14.3 and higher |
Enhanced terrain information for display in the 3D Network Visualizer. Requires use of 3DNV module. |
| DTED level 0 |
30 arc seconds by 30 arc seconds spacing. |
| DTED level 1 | 3 arc seconds by 3 arc seconds spacing. |
| DEM (15 minute) | Corresponds to USGS 1:63,360 scale topographic quadrangle map. |
| DEM (2 arc-second) | Corresponds to 30-minute by 30-minute coverage areas. |
| DEM (1 degree) | Corresponds to USGS 1:250,000 scale data. |