MODIFICATION
70 -- Network Traffic Generator
- Notice Date
- 12/22/2003
- Notice Type
- Modification
- Contracting Office
- Department of the Air Force, Air Mobility Command, AMC Contracting Flight (AMC/LGCF), 507 Symington Drive Room W202, Scott AFB, IL, 62265-5015
- ZIP Code
- 62265-5015
- Solicitation Number
- FA4452-04-Q-A042
- Response Due
- 1/9/2004
- Archive Date
- 2/28/2004
- Point of Contact
- Teresa Francoeur, Contract Specialist, Phone 618-256-9950, Fax 618-256-3091, - Gary Steinkamp, Contract Specialist, Phone (618)256-9990, Fax (618)256-5724,
- E-Mail Address
-
teresa.francoeur@scott.af.mil, Gary.Steinkamp@scott.af.mil
- Description
- Salient Characteristics for Network Traffic Generator Requirement Attachment 1 Physical Specifications: The NTG may be single or multiple chassis to support a separate or combined pitch-catch capability. The NTG total package must be no greater than 4RU and must be a 19-inch rack mountable system. The NTG must be capable of operating at both 115-230 Volts 50/60 Hertz power. The NTG at a minimum must be capable of supporting at least eight (8)-10/100/1000 Base T interfaces with RJ-45 connection. Network Services and Protocols: The NTG must be able to generate IP, TCP, and UDP traffic over multiple ports. The NTG must be able to support streaming servers that use any of the three major streaming formats: Apple QuickTime, Real System streaming, and/or Microsoft MMS streaming version 8 or 9. Network Architecture Simulation: The NTG must be capable of generating and receiving traffic from any possible IP subnet to include private IP space (such as the 10.0.0.0 network). The NTG must create a software configurable virtual router capability for class A, B or C networks. The virtual router device or network under test must provide next hop router, which the device or network under test can forward traffic. For example, if the device under test has an interface address of 172.16.1.2/24, the NTG must be capable of providing a next hop router, such as 172.16.1.1/24, which may be configured as a default gateway on the device under test. Traffic shall be forwarded to the device under test such that it appears to be forwarded by a router on the local network of the device under test. The NTG must be capable of generating traffic using multiple (three or more) IP subnets on a single port. The NTG must be capable of utilizing non-contiguous subnets, and subnets of varying sizes on a single port. This capability will allow the trainer to emulate a wide array of subnets and services thus providing the appearance of a very large network. Realistic Network Traffic: The NTG must be capable creating highly reliable stateful application layer (layer 4-7) traffic simulating client(s) and server(s) traffic located anywhere and used together or separately as training needs dictate. The NTG must be capable of creating, maintaining, and terminating application layer client server sessions that are TCP compliant with properly generated sequence numbers, slow start/congestion avoidance, round trip time calculation, network latency, packet loss, TCP timeout, packet retransmission, packet fragmentation and re-assembly. The NTG must be capable of supporting PCAP reply of TCP and UDP traffic flow simulating higher-level traffic like NFS, SQL, RPC SMB, and DMS. The NTG must be capable of generating traffic, which can flow through network address translation devices with no loss in performance and/or functionality. All protocols supported by the NTG, including PCAP replay, must be capable of being passed through a NAT device. The NTG shall provide to emulate network clients, servers and services to include the ability to that other references within the network to the clients, servers or services can be correctly established and maintained, for example: virtual clients and servers have corresponding entries in the DHCP database. The NTG must provide a up to 10,000 plus stateful client server application layer sessions and hundreds of thousands of transactions/second at least 80% of wire speed (100 MB). Supports a minimum of 500 servers per port. The NTG must support generation of stateful traffic on all supported protocols/services simultaneously. The NTG must support defining traffic on generated random IP and MAC addresses and provide for defining traffic on static IP and MAC addresses. The NTG must be capable of supporting any mix protocols/services per port with application compatibility to third party devices such as application layer gateways/firewalls and email forwarding systems. The NTG must be capable of creating complete stateful HTTP, HTTPS, FTP, SMTP, POP3, DNS, and Telnet sessions/connections and interact with third party systems, such as servers, firewalls, email gateways, virus scanners, spam filters, application layer gateways, etc. The NTG should be capable of simulating a large number of users (greater than 1000) simultaneously creating, sending, receiving and deleting email messages. The NTG must be capable of supporting multiple protocols on a single port utilizing the same or separate random IP addresses. For example, HTTP on port 80, HTTPS on port 443, Telnet on port 23, etc. The NTG must generate protocol/service traffic types in a random pattern. The NTG must generate random network traffic data packet sizes. The NTG must be ability to store data files for traffic generation (I.E. Cache Web pages, email attachments, etc) & configuration files for traffic generation without requiring external hardware. The NTG must allow the replay a libpcap formatted capture file with fully stateful TCP as well as TCP realism features of: packet loss, congestion avoidance and link speeds. The NTG must be capable of playing back the application layer data within the libpcap formatted file over new TCP connections with varying IP addresses with proper TCP sequence numbers and checksums. The NTG?s SMTP must provide the ability to import users from a CSV or TXT file format and allow for configuration control over TO, FROM, SUBJECT, and message body add attachments to messages. The NTG must provide realistic HTTP features, including the ability to emulate browser versions, user think time, user frustrations, user click-paths, random page fetches, page fetches, user forms databases, ability to send and parse XML (SOAP) messages, ability to manage dynamic session IDs, and ability to support basic and proxy authentication. Realistic Network Attacks: The NTG must provide the capability to simulate normal user errors that may trigger a false positive alert on network security monitoring devices, for example incorrect login. The NTG must provide the ability for these user errors to be randomized from IP, user, protocol, error type, and subnet. The NTG must provide the capability to simulate normal network activity that results in an alert on network security monitoring devices, for example SNMP from a mil domain to mil domain, SSH session on any port other then port 22, Telnet session on any port other than 23, the creation of an xterm session or the execution of the ?SU? command. The NTG must provide the ability for this network traffic to be randomized from IP, user, protocol, error type, and subnet. The NTG must be capable of generating both a Denial of Service and Distributed Denial of Service attack, providing network traffic to tax the network capability to the breaking threshold. The NTG DOS attack must not rely on other hardware to generate the attack. The NTG at a minimum must support the known DOS attacks: Ping, Ping of Death, Land, Smurf, unreachable host, teardrop, evasive UDP, and Syn flood attacks. The NTG at a minimum must support the known DDOS attacks: SYN Floods, ARP Floods, TCP and UDP port scans, and PING Floods. The NTG must provide a capability for the user/trainer to develop custom/additional DOS and DDOS using a well-defined scripting language. The NTG must be capable of generating the DDoS on the same ports that are generating multi-protocol, stateful, application compatible TCP traffic. The NTG must be capable of generating traffic, which simulates application layer attacks over HTTP, such as Code Red and Nimda. The NTG must be capable of passing these simulated attacks to third party HTTP servers using properly established TCP connections. Continuous Operation: The NTG must be capable of operating for sustained periods of time without a system reset or reboot. Training segments vary in length from a couple of hours to 10 days. The NTG will also be running continuously between training blocks to assist in providing status of the overall health of the simulator. The NTG must be stable to provide for continuous operations and to not interfere with training sessions. The NTG must be capable of operating continuously without reset for a period of a 14-day (24X7) exercise and run a continuous script which is developed to assist in determining simulator system status during periods between training events. Traffic Generator User Interface (Trainers Capabilities) Requirements: Management Console/Remote Administration: The NTG must provide the user/trainer a single easy-to-use management software and scripting environment supporting Perl and TCL scripting to create network traffic generation scripts, which provides full control of every single bit in the Ethernet frame for custom generated traffic. The NTG must allow the user/trainer the ability to define/create new realistic network traffic and attacks. The NTG must provide an easy to use interface to define traffic generation scenarios configurations by defining, combining, organizing and running scripts that generate stateful and network attack traffic. The NTG must allow the user/trainer can control/run up to 100 scripts simultaneously. The NTG must allow the user/trainer the ability to dynamically throttle the NTG?s user-sessions, user sessions per second, connections per second, bandwidth utilization, and protocol/service utilization, providing the ability to graduate load stressing to different levels during a single script run. The NTG must allow the user/trainer the ability to control the protocol/service percentage/mix. The NTG must provide the ability to control the network traffic is randomized from IP, user, protocol, error type, and subnet. The NTG must provide the ability for the user/trainer to build upon the NTG developed virtual network to emulate actions (stateful traffic) coming from end users on the virtual network. The NTG must automatically add any custom developed traffic generation scripts or network attack scripts to the NTG GUI for inclusion in test configurations. The NTG must allow the user/trainer to remotely manage the NTG via a network connection, The NTG?s console interface must not place any restrictions upon device location, either geographical or network based, other than a requirement for TCP/IP connectivity to the NTG. The NTG must allow the user/trainer the ability to control the NTG(s) independently or as a NTG cluster at the networked simulator locations from a central location and provide synchronized activities including start/stop and configuration capabilities. The NTG must provide a management console capable of administering remote located agents [E.G. MMC type (Microsoft Management Console), Web browser interface, command line interface] providing the ability to manage multiple sites independently or clustered for synchronized activity from a single location. Data Capture/Metrics: The NTG must be capable of providing real-time feedback to the user on infrastructure loading and performance. The NTG test results must be able to be created and stored in native CSV (comma separated values) format for quick and ready import into any major spreadsheet, database or reporting tool. The NTG must provide a reporting tool written in a platform independent environment such as Java that can connect directly to the NTG and retrieve test results. This tool must be capable of providing a graphical summary of all result data provided by the NTG, allow the user to create custom graphs using any data point within the NTG results, and generate presentation-ready graphical reports in both Adobe Acrobat PDF and HTML format.
- Record
- SN00494310-W 20031224/031222212204 (fbodaily.com)
- Source
-
FedBizOpps.gov Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |