Documents

Medusa sprint 2 requirements

Oct. 23 2016 — 8:09a.m.

/4
1/4

© and confidential Endace. External distribution prohibited.Internal distribution restricted. Medusa Sprint 2 Requirements Date Created 13/07/2012 Version 0.4 Author(s) Approvals Table of Content 1. SPRINT 2 OVERVIEW ........................................................................................................................................................... 2 1.1. HIGH LEVEL GOALS ........................................................................................................................................................................ 2 1.2. PRIORITIES ................................................................................................................................................................................... 2 2. REQUIREMENTS .................................................................................................................................................................. 2 2.1. SUPPORT FOR 40GB ETHERNET ....................................................................................................................................................... 2 2.1.1.Priority ............................................................................................................................................................................... 2 2.1.2. Reasoning.......................................................................................................................................................................... 2 2.1.3. Requirement ..................................................................................................................................................................... 2 2.2. LICENSING FOR 100G .................................................................................................................................................................... 3 2.2.1.Priority ............................................................................................................................................................................... 3 2.2.2. Reasoning.......................................................................................................................................................................... 3 2.2.3. Requirement ..................................................................................................................................................................... 3 2.3. SEPARATE MAC INSERTION BY IP TYPE .............................................................................................................................................. 3 2.3.1.Priority ............................................................................................................................................................................... 3 2.3.2. Reasoning.......................................................................................................................................................................... 3 2.3.3. Requirement ..................................................................................................................................................................... 3 2.4. USE HLB THAT IS ORTHOGONAL TO DAG CARD................................................................................................................................... 3 2.4.1. Priorities ............................................................................................................................................................................ 3 2.4.2. Reasoning.......................................................................................................................................................................... 3 2.4.3. Requirement ..................................................................................................................................................................... 3 2.5. SUPPORT ENDACE ETH OUTPUT FORMAT ........................................................................................................................................... 3 2.5.1.Priority ............................................................................................................................................................................... 3 2.5.2. Reasoning.......................................................................................................................................................................... 3 2.5.3. Requirement ..................................................................................................................................................................... 3 2.6. SUPPORT SNAP LENGTH ................................................................................................................................................................. 3 2.6.1. Priority .............................................................................................................................................................................. 3 2.6.2. Reasoning.......................................................................................................................................................................... 4 2.6.3. Requirement ..................................................................................................................................................................... 4 EDMxx-yyyMedusa Sprint 2 Requirements v0.4 Page 1of 4

© and confidential Endace. External distribution prohibited.Internal distribution restricted. Revision History Version Date 0.1 0.2 0.3 17/7/2012 18/7/2012 20/07/2012 0.4 20/07/2012 Author Revision Description Approved (Yes/No) Initial draft Added requirement for 100G licensing Removed dual port 40G as a stretch goal. Changed HLB field select to a more accurate solution to the problem we need to solve. Updated the priorities for the requirements and made them clearer. 1. Sprint 2 Overview th Medusa project team is preparing for the next development sprint that is expected to start on August 6 and last for 12 weeks. The team includes members from the Firmware, Core Software and Appliance software groups. In parallel for this sprint there is a 6 weeks effort for testing the deliverables from Sprint 1. 1.1. High Level Goals The goal of this sprint is to deliver all of the functionality required by GCHQ, the potential order from AT&T and perform basic probe integration. All of these features if completed within the sprint time frame will conclude the development on the Medusa platform for the foreseeable future. 1.2. Priorities Blocker – Must be completed for this sprint to be considered done. Stretch – Should be completed if time permits and blockers have been completed. High – Should be completed if time permits and stretch goal tasks have been completed. Medium – Should be completed if time permits and high priority tasks have been completed. Tasks with the same priority are ordered by importance (High to low). 2. Requirements The requirements are specified as a must have and a stretch goal. The stretch goal should not interfere with other “must” deliverables, and are not considered done until the feature is tested. 2.1. Support for 40Gb Ethernet 2.1.1. Priority This is a blocker for this sprint. 2.1.2. Reasoning 40Gb Ethernet has a potential revenue in FY13 of up to $1M. There are also contractual commitments to GCHQ for supporting this line rate. 2.1.3. Requirement Single port 40Gb delivery must be delivered at the end of this sprint. As part of this development, license for 100G is required to configure the system to that line rate. 100G license is required because the 100G and 40G hardware are identical, and we need a way to prevent customers from buying the cheaper 40Gb platform and using it for 100G monitoring. EDMxx-yyyMedusa Sprint 2 Requirements v0.4 Page 2of 4

© and confidential Endace. External distribution prohibited.Internal distribution restricted. 2.2. Licensing for 100G 2.2.1. Priority This is a blocker for this sprint. 2.2.2. Reasoning 40G and 100G are going to be sold using the same base hardware. This means a user can potentially buy the 40G system and plug in a 100G optics and get the higher functionality. 2.2.3. Requirement The 100G feature support will be licensed controlled. Platforms shipped with 100G license will work for both 100G and 40G. 2.3. Separate MAC Insertion by IP type 2.3.1. Priority This is a stretch goal for this sprint (Just below blocker). 2.3.2. Reasoning This is a committed feature for GCHQ. 2.3.3. Requirement The user will be able to select MAC insertion by hash and by IP type. IP type can be IPv4, IPv6 or Non-IP. This will allow the user to configure end systems to efficiently process only one type of payload. 2.4. Use HLB that is orthogonal to DAG card 2.4.1. Priorities This is a high priority for this sprint(Just below stretch). 2.4.2. Reasoning The user will most likely use DAG cards to capture the output traffic. If the same hash fields and algorithm are used for both Medusa and the DAG card, the DAG card has much less granularity to load balance the captured traffic which means the performance gain from DAG load balancing is not as high as required. (e.g. extreme case for AT&T is that one entry of the HLB consumes about 10-15% of the traffic the card captures) 2.4.3. Requirement The user will be able to use high granularity load balancing on the Medusa system to a nominal number of links (e.g. 10 links for 100G and 4 for 40G). Each egress port traffic will be captured by a DAG card which will be able to load balance in equal proportions to a minimum of 24 capture streams. 2.5. Support Endace Eth Output format 2.5.1. Priority This is a high priority feature for this sprint. 2.5.2. Reasoning This output format allows Endace Probes to integrate seamlessly with the Medusa platform output including timestamp information. 2.5.3. Requirement The output format from Medusa will be user selectable between Ethernet and Endace Eth format. The Endace Eth format will include the correct extension header and information as used by OSm 5.0.1 release. 2.6. Support Snap Length 2.6.1. Priority This is a medium priority for this release. EDMxx-yyyMedusa Sprint 2 Requirements v0.4 Page 3of 4

© and confidential Endace. External distribution prohibited.Internal distribution restricted. 2.6.2. Reasoning For many applications such as Net Flow generation, there is no need to the entire packet to be captured, the ability to snap length the packets allows for a more dense deployment for these kinds of applications. 2.6.3. Requirement The user will be able to configure a single snap length across all output ports from a Medusa system. EDMxx-yyyMedusa Sprint 2 Requirements v0.4 Page 4of 4

Filters SVG