Chapter 3 :System Specification and Design

3.1 General Information about OPNET OPNET Modeler is a GUI based simulation tool, that uses project, node and process editors for building a large number of networking and communication models . OPNET Modeler enhances the R&D process for analyzing ,planning and designing different communication networks, propagation models , devices, protocols, and applications. Users can easily analyze and simulate any networks for comparing the effects of different technology , designs and end-to-end communication behavior. OPNET Modeler is widely used by:-Defense organization around the world. -Leading network and telecom vendors. -Academic Institutions and research Organizations. Supports a Broad Scope of Studies Including: Designing wired and wireless protocols and technologies. Testing and demonstrating network equipment design keeping realistic situations in mind just before the actual production. Network planning of mobile and fixed network deployments incorporating various terrain effects. Incorporating communication effects into war gaming. The modeler supports a variety of communication protocols and networking technologies like :

Multimedia (voice, video etc) TCP/IP/UDP OSPF,RIP,EIGRP,BGP Ad hoc routing protocols like OLSR,AODV IPv6/IPV4 Wireless Networks Many More.

Brief Moldeler Architecture Multi level Hierarchy

The main components of the modeler is divided into three components namely project editors, node editors and process editors. Project Editor We can create node and different link objects to represent any customized or standard network models. Mobility of nodes can be configured by assigning trajectories.

Node Editors It deals with different protocols and application functionalities used, and the internal data flow into a device.

Process Editors It handles the finite state machine and define logical methods and flow control for all protocols. Each states behavior is controlled by C/C++ native code.

Other Editors Packet Format , Antenna Pattern and Modulation.

Modeler Wireless Capabilities

Suite supports all the network having static and mobile devices, which includes cellular (GSM, CDMA, UMTS, WiMAX, LTE, etc.), mobile ad hoc network(MANET), wireless LAN (IEEE 802.11), satellite communication, PAN(Bluetooth, ZigBee, etc.). Plan Mobile network deployments that accurately incorporate wireless propagation impairments. Optimization of standard wireless protocols, like media access control ,scheduling algorithms, Bandwidth management etc. Evaluate the effects of proprietary or customized antenna pattern in a network.
Wimax Cellular network on OPNET

Predict protocol and application performance. Wireless network designers, wireless architects, and service providers can analyze end-to-end characteristics , optimize network performance, and evaluate growth opportunities for networking service generating lucrative business.

Examples showing OPNET wimax network

The above screenshots shows one of our deployed wimax network in OPNET. Here we used seven Cell and each cell four users and one BS.we also we configured voice and data applications for the users which is shown in the below figure.

We simulated this scenario among the users. We obtained the following results out of our network simulations.The results are shown in the below screenshot.

Here we analysed voip parameters like MOS value, jitter, delay and also email data application parameters, and wimax link conditions and so many other stuffs.

Overview of the Standard Model Library The standard model library consists of the following types of objects:

Device Models Link Models LAN and Cloud Models Utility Objects

In actuality, the library also contains many models of networking protocols and algorithms that allow your network models to simulate real network behavior. However, as a user of OPNET Modeler, you do not manipulate the internals of these protocols directly. Instead, you have access to the protocols' functions via parameters, much as you do in working with real networks. Their parameters appear as attributes of the objects and are configurable via OPNET Modeler's GUI. One of the goals of this section is to explain the objects you have available to you, and how to work with their attributes to represent your networks as desired within the tool. Device Models
Devices comprise the majority of the objects in the standard model library. They correspond to a wide class of network hardware, including the following:

Routers Switches Hubs Workstations Servers Firewalls Printers

As you can see, devices essentially correspond to the boxes, that is, the chassis-type or rackmounted systems in your network. They represent the hardware that performs the information transmission and processing in the network, ranging from simple repeaters like hubs, to content and computation servers, like mainframe computers. Of course, these devices must not consist solely of hardware; most of them contain large numbers of software models, spanning appropriate layers of the protocol and application stack. What's inside a device depends on what its function is. For example, a typical router model will contain hardware and software models of

Ethernet, PPP, and perhaps other Layer-2 protocols. It will also contain routing protocols such as RIP, OSPF, IGRP, and BGP4. The standard model library presents device models to you graphically. Typically, you will select these objects from the object palette where they appear graphically, though in some cases, you may choose their name from a menu of available models. Devices appear as icons as soon as they are deployed in your network model. The standard model library follows conventions (thirdparty or supplemental models may not) for the appearance of each type of device, as illustrated below:

Graphical Conventions for Network Objects

Vendor Versus Generic Device Models Device models are also categorized into two classes: vendor device models and generic device models. Vendor models represent devices manufactured by a particular company, such as Cisco Systems or 3Com. The developers of the standard model library use data published by these manufacturers to characterize the devices as well as they can. You can also create vendor device models using the Device Creator operation, provided you have obtained values for required parameters of the device.

Generic models provide behavior that is correct for devices of their class. However, they are not configured to model any particular manufacturer's devices. Instead these devices provide attributes (that is, parameters), allowing you to configure each one you deploy differently if you choose. For example, the generic router below offers the forwarding rate attribute, which specifies the throughput of the router in packets per second. Each instance of the router that is deployed can be assigned its own forwarding rate. In contrast, a vendor device model of a router would already be aware of its own forwarding rate, as you would expect because the device type is already known. A vendor model would therefore have a preconfigured forwarding rate attribute that is consistent with the actual router's forwarding rate.

Generic Model vs. Vendor Model

Link Models To form a network of devices, you will need to use links and these links will require specific characteristics. In OPNET Modeler, links represent the physical media and properties, such as line rate in bits per second, delay, and likelihood of data corruption. Link models also generally represent a choice of Layer-2 technology, allowing OPNET Modeler to verify compatibility of two or more attached devices, and the link that connects them. One of the most important characteristics of a link model from a network performance perspective, is the speed of transmission, in bits per second. This characteristic is usually implicit in the choice of link model (for example, a 10BaseT link automatically provides for a 10 Mb/sec. transmission rate).

Links are represented as line segments or a series of line segments with arrowheads in the GUI. When selecting links from the object palette, you will see objects similar to those shown below:
Link Model Graphical Convention

LAN and Cloud Models

LAN Objects Abstract Local Area IInfrastructure

Using LAN objects you can quickly generate large amounts of users for your network. Specifically, each LAN object allows you to specify the number of users present within it. You can then assign application traffic to a subset, or all of the users of the LAN. Therefore, scaling the traffic generated by a LAN (to model more users, for example), is a simple matter of increasing the specified number of users. LANs can then be interconnected via switches and routers to carry traffic to and from devices and LANs in other parts of the network. In a manner similar to the use of LANs, it is sometimes useful to abstract parts of the wide area network infrastructure. Cloud models are special objects in the model library used to represent such infrastructure. They provide high-level characteristics used to simulate the behavior of that portion of the network. The ATM, Frame Relay, and IP model suites all include cloud models.

Cloud Objects Abstract WAN Infrastructure

Utility Objects
Utility objects is a great tool to choose varieties of components required for any network formation. Utilities Object Palette