Applicable Versions
NetSim Academic  
NetSim Standard 
NetSim Pro  


Applicable Releases
v11v12v13


NetSim has an in-built traffic generator that allows users to configure unicast, multicast and broadcast transmissions for different traffic models such as CBR, FTP, Video, Voice, Database, etc. 


In order to model a request-response application in NetSim, the HTTP traffic model can used. HTTP is a request-response application; it uses a client-server configuration, not a source-destination confirmation. The client node sends a page request to the server, and the server responds with the pages (whose size is in bytes). Note that the http application in NetSim does not transfer a file, rather it is a type of streaming application where webpage pages are continually downloaded from a sever- similar to a person continually browsing the web. 


In the application metrics as part of an HTTP application, users can see two rows of metrics, one corresponding to requests from the client to the server and the other corresponding to the replies from the server to the client


The HTTP Application Type in NetSim has the following user configurable properties:


HTTP generally uses TCP in the transport layer. However, it can also run over UDP.  


Parameters:


HTTP Request Inter Arrival Time (Seconds) - The source node will generate a request after every interval as specified for this parameter. As per the above example, a request packet will be generated for every 1 second. 


HTTP Page Count - This parameter specifies the number of pages that the server response will contain. As per the above example, the response will comprise of one page per request.


HTTP Page Size - This parameter specifies the size of each page that the server sends. If the page size is set to 20000 Bytes, it will be broken down into 14 Segments, since the maximum segment size is 1460 in the case of TCP.


Example:


To model a request-response application where there is one response per each request generated at an interval of 5 seconds the HTTP application can be customized as shown below:



As per the settings above, a request will be sent every 5 seconds and there will be only one response. Since the page size is not greater than TCP MSS (1460 Bytes) it will not be segmented further.