 |  |  |
| |
 |
| OPNET
Modeler is the industry's leading environment for network modeling and simulation,
allowing you to design and study communication networks, devices, protocols, and
applications with unmatched flexibility and scalability. Modeler is used by the
world's largest network equipment manufacturers to accelerate the R&D of network
devices and technologies such as VoIP, TCP, OSPFv3, MPLS, IPv6, and more.
|
|
| Key Features |
| |
-
Most scalable and efficient simulation engine - Hundreds of protocol and
vendor device models - Open model source code - Object-oriented modeling
- Comprehensive graphical user interface - Discrete Event, Hybrid, and
Analytical simulation - 64-bit fully parallel simulation kernel - System-in-the-Loop
for external interfacing - Integrated debugging and analysis |  |  | |
| | |
| Solution
Architecture | | |
Modeler
is based on a series of hierarchical editors that directly parallel the structure
of real networks, equipment, and protocols. The
Project Editor graphically represents the topology of a communications network.
Networks consist of node and link objects, configurable via dialog boxes. Drag
and drop nodes and links from the editor's object palettes to build the network,
or use import and rapid object deployment features. Use the protocol menu to quickly
configure protocols and activate protocol-specific views. The
Node Editor captures the architecture of a network device or system by depicting
the flow of data between functional elements, called "modules". Each module can
generate, send, and receive packets from other modules to perform its function
within the node. Modules typically represent applications, protocol layers, algorithms,
and physical resources, such as buffers, ports, and buses. Modules are assigned
process models (developed in the Process Editor) to achieve any required behavior. The
Process Editor uses a powerful finite state machine (FSM) approach to support
detailed specification of protocols, resources, applications, algorithms, and
queuing policies. States and transitions graphically define the progression of
a process in response to events. Each state of a process model contains C/C++
code, supported by an extensive library of functions designed for protocol programming.
Use the Process Editor to develop entirely new process models, or use the models
in OPNET's Model Library as a starting point. OPNET's process modeling framework
supports full multi-threading and use of parallel computing architectures. |
| | |
| | Modeler
offers a comprehensive library of detailed protocol and application models including
Multi-Tier Applications, Voice, HTTP, TCP, IPv4, BGP, EIGRP, RIP, VoIP, OSPFv3,
RSVP, Frame Relay, FDDI, Ethernet, ATM, IPv6, MPLS, PNNI, DOCSIS, IP Multicast,
Circuit Switch, IS-IS, and many more. All standard models are provided as FSMs
with open source code. Modeler also includes an extensive vendor device model
library with hundreds of vendor specific and generic device models including
routers, switches, workstations, and packet generators. Quickly assemble your
own device models using the "Device Creator". Alternatively, there are multiple
interfaces to automate device model creation through the import of operational
data from text files, XML, and popular tools such as Cisco, HP, CA, NetScout,
BMC, Concord (CA), Sniffer, Infovista, MRTG, cflowd, tcpdump, and others. Modeler's
discrete event simulation kernel is the focal point of the modeling environment.
Over the years, it has been continuously enhanced to deliver faster, more efficient
simulations that scale significantly with the amount of traffic in the model.
Aside from raw performance, Modeler packs numerous features into the kernel to
accelerate the larger, more demanding simulations. These include a 64-bit kernel
for expanded memory addressing and general parallel simulation for leveraging
multiple processors. Hybrid and Analytical simulations are other forms of simulation
provided by Modeler, which are ideal for activities where the importance of granularity
is superceded by run-time, such as routing studies and failure analysis. |
| | |
| System-in-the-Lop
Testing & Training | | System-in-the-Loop
(SITL) is an optional capability that can be used to connect a live network device
or software application to an OPNET simulation for testing and training purposes
such as: | |
- | Performing
developmental, interoperability, scalability, and conformance testing of prototype
hardware and software applications. | |
- | Creating
a virtual training facility for devices or applications interfacing directly with
simulated network infrastructure containing numerous simulated devices. |
| - | Studying
the behavior of prototype applications by deploying them on a simulated network
topology | | - | Analyzing
the performance of a new protocol deployed in a simulated network environment
by injecting real network traffic. | | | |

|
| | |
| | |
|