17.1 System Requirements
Supported Platforms1,2
- Windows 7 Professional (32 and 64 bit)
- Windows Vista Business (32-bit and 64-bit)
- Windows XP Professional (32-bit and 64-bit)
- Windows Server 2008 (32-bit and 64-bit)
- Windows Server 2003 (32-bit and 64-bit) and Windows Server 2003 R2 (32-bit and 64-bit)
- Red Hat Enterprise Linux 5 (v2.6.18 Linux kernel)
- Red Hat Enterprise Linux 4 (v2.6 Linux kernel)
- Fedora Linux 6 (v2.6.18 Linux kernel)
2. Listed platforms are those supported for the base product. Optional modules may have certain particular platform limitations/requirements. For more information, refer to the entry for the particular module under the “Optional Modules” tab.
System Configuration
Recommended: 3.0+ GHz using x86, EM64T, x86 AMD, or AMD64 (dual-core))
Recommended3: 1-2 GB
3. Memory requirements may be greater for large networks and/or large traffic demands.
Required System Patches
Windows XP Professional
Other Requirements
On Linux installations, the license file must be stored on a disk local to the operating system installation (non-network drive) and must be accessible via the /opt/OPNET_license directory name.
Special Requirements (Windows Vista, Windows Server 2008, and Windows 7)
User Account Control (UAC) enabled on Windows Vista, Windows Server 2008, and Windows 7 can restrict user privileges for application software installed in C:\Program Files or C:\Program Files (x86).
To avoid this restriction when UAC is enabled, do one of the following:
- Install OPNET software in a different directory;
- Run OPNET software as the Administrator User; or
- Disable UAC (not recommended by OPNET unless you first check with your local system administrator)
2000,
XP,
Vista, 7
- Microsoft Visual Studio .NET 2010
- Microsoft Visual C++ 2010 Express Edition
- Microsoft Visual Studio .NET 2008
- Microsoft Visual C++ 2008 Express Edition
- Microsoft Visual Studio .NET 2005
- Microsoft Visual Studio .NET 2003
For instructions on configuring Visual Studio 2005, please see FAQ 1685, [What are the proper system environment settings for Microsoft Visual Studio 2005 compiler to work with release 12.0 or later?].
Note: OPNET highly recommends the Professional Edition of the Visual C/C++, .NET 2003, 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.
Microsoft Internet Explorer 7.0 or 8.0
or a compatible browser that supports style sheets.
Software Compatibility
When performing AppTransaction Xpert studies in OPNET Modeler, larger application trace sizes require more memory for processing. In these situations, adequate system performance may require larger RAM configurations. Flow Analysis module When performing Flow Analysis studies in OPNET Modeler, large networks and/or large traffic demands require more memory for processing. In these situations, adequate system performance may require larger RAM configurations.
High Level Architecture (HLA) module HLA module is compatible with the following RTIs:
- RTI 1.3: DMSO RTI-1.3NGv6, MÄK RTI 2.1 or later, Pitch RTI 2.4.04
- RTI IEEE 1516: MÄK RTI 3.1.2 or later, Pitch RTI 3.2.3
Windows libraries linked with Microsoft Visual Studio .NET 2008 runtime are shipped with the HLA module. Libraries linked with Microsoft Visual Studio .NET 2005 or .NET 2003 runtime are available on demand.
4.
Pitch RTI 2.4.0 is only supported on Windows 32-bit platforms.
Pv6 Planning and Operations module Flow Analysis module and NetDoctor module are pre-requisites for the IPv6 Planning and Operations module. NetDoctor moduleWhen performing NetDoctor studies in OPNET Modeler, large networks and/or large traffic demands require more memory for processing. In these situations, adequate system performance may
require larger RAM configurations.
eXpress Data Import (XDI) module 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.
Network Traffic
rrdtool-based MRTG is not supported
CA Network Health, and eHealth
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.
CA MICS
Other
requirements (when running on a dedicated machine)
CPU: 1 GHz minimum
RAM: 512 MB minimum, 1-2 GB or more if
using complex 3D models (such as provided human models)
System File Space: 800 MB (including
provided OpenFlight models and terrain databases)
Video Card: OpenGL 2.1-compliant graphics
card (NVidia preferred), recommended with 128-bit memory access and 128 MB of
VRAM
5. For 3DNV 3.0.0, Modeler and simulations that communicate with the Visualizer are only supported on Windows platforms.
Multi-Federate Logger for 3DNV Multi-Federate Logger for 3DNV is supported on 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 (when running on a dedicated machine)
CPU: 500 MHz minimum
RAM: 64 MB minimum
System File Space: 40 MB
Use of the SITL module when running discrete event simulations within virtual machines (such as those hosted by VMware or other virtualization platforms) is not supported.
(2 arc-second)