14.5 System Requirements
Supported Platforms1
| Vendor | OS | Processor |
|---|---|---|
| Microsoft | Windows Vista Business | x86 or EM64T (Intel Pentium III, 4, Xeon, or compatible), 1.5 GHz or better x86 AMD or AMD64, 1.5 GHz or better |
| Windows Vista Business x64 Edition | ||
| Windows 2000 Professional | ||
| 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) |
1. OPNET software is supported on the English language version of each operating system
Special Requirements (Linux)
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.
Required System Patches
| Vendor | OS Version | Patch Number/Name |
|---|---|---|
| Microsoft | Windows Vista Business | Service Pack 1 is required. |
| 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 and Service Pack 3 are supported but not required. |
System Configuration
RAM
512 MB required, 1-2 GB recommended2
System File Space
3 GB
Up to an additional 2 GB of free disk space may be required during installation
Working File Space
100 MB or more for temporary and log files
Display
Resolution: 1024x768 minimum
2. Memory requirements may be greater for large networks and/or large traffic demands.
Other Requirements
Supporting software
| OS | Compiler |
|---|---|
| Linux | gcc 3.4 or higher |
|
Windows 2000,
XP |
Microsoft Visual C/C++ 6.x, Microsoft Visual Studio .NET 2002, Microsoft Visual Studio .NET 2003, Microsoft Visual Studio 2005, Microsoft Visual Studio 2008, or Microsoft Visual C++ 2008 Express Edition For instructions on configuring your installation for Microsoft Visual C/C++ 6.x, please see FAQ 2037 [I upgraded to Modeler 12.1 or 14.0 and now I get the following error: "op_win_stdio_patch.obj : fatal error LNK1103: debugging information corrupt; recompile module" What should I do to fix this?]. |
Note
TCP/IP networking software is required.
Browser
Mozilla Firefox 1.0.6 or higher, Microsoft Internet Explorer
5.0 or higher, or a compatible browser that supports style
sheets.
Software Compatibility
The following modules are optional for OPNET Modeler:
ACE module
Supported
Formats
When performing ACE 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
The HLA module is compatible with the following RTIs:
- RTI 1.3: DMSO RTI-1.3NGv6, MaK RTI 2.1 through 3.2
- RTI IEEE 1516: MaK RTI 3.1.2 or 3.2
IPv6 Planning and Operations module
The Flow Analysis module and NetDoctor module are pre-requisites for the IPv6 Planning and Operations module.
NetDoctor module
When 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
| 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 |
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, HP-UX, AIX, Linux, and Windows 2000/XP |
| HP OpenView Performance Agent | c.03.42 or later | Import of performance data running on Solaris, HP-UX, AIX, Linux, and Windows 2000/XP |
| Windows Perfmon | Windows 2000/XP | Import of performance data from workstations running Windows 2000/XP |
| SAS MXG | SAS: 9.1, MXG: 23.07 | Import of performance data for mainframes running z/OS |
| CA MICS | 11.0 | Import of performance data for mainframes running z/OS |
| CA Unicenter NSM | 3.1 or 11.0 | Import of performance data for servers running Solaris, HP-UX, AIX, Linux, and Windows 2000/XP |
3DNV
3D Network Visualizer is supported on Windows
2000 SP2 and Windows XP. Modeler and simulations that communicate with the Visualizer are supported on Windows 2000, Windows XP, Red Hat Enterprise Linux 4 (32-bit),
or Fedora Linux 4 (32-bit). 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 (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 1.2-compliant graphics card, recommended with 128-bit memory access and 128 MB of VRAM
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 (when running on a dedicated machine)
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 Server 2003,
Windows Server 2003 x64 Edition, Windows XP, Windows XP Professional x64 Edition, and the Linux OSes listed above. 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. |
TIREM module
The TIREM Module is supported under Windows 2000, Windows XP (32 bit), and Red Hat Enterprise Linux 3 and 4 (32 and 64 bit).
Special Requirements (Windows)
Install the Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) if this is not yet installed.