1 / 6

Core Router Software Accelerated Life Testing

This draft provides a status update on the revision of the Core Router Software Accelerated Life Testing document, addressing concerns and making specific revisions to methodology and benchmark configurations. It aims to ensure the document is ready to move forward to the Area Director for approval.

elainemallory
Download Presentation

Core Router Software Accelerated Life Testing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Core Router Software Accelerated Life Testing(draft-poretsky-routersalt-term-01.txt) Authors: Scott Poretsky, Avici Systems Shankar Rao, Qwest Communications Ray Piatt, Cable and Wireless 56th IETF Meeting – San Francisco

  2. Status Update • Revision 00 Approved as BMWG Work Item at IETF 55 Atlanta. • BMWG Chairperson had concerns to be addressed for Area Director approval: • White Box benchmarks should be removed • Recommended values should be removed • Add Clarification of externally observable Black-Box benchmarks • Consider potential for failure to agree on input parameters (i.e. protocols) • Authors decided to address concerns prior to advancing draft to Area Director. • Revision 01 addresses concerns (hopefully)

  3. 01 General Revisions • Removed White Box benchmarks • Minimum Available Memory • Maximum CPU Utilization • Removed recommended values • Values are to be addressed in follow-on methodology draft.

  4. 01 Specific Revisions • MANAGEMENT CONFIGURATION SET • Added RADIUS and TACACS • SECURITY CONFIGURATION SET • Added ACEs to ACL Config Set • INSTABILITY CONDITIONS • Added IGP Flap Rate • Added Route Convergence Due to Better Next-Hop • Noted Interface Shutdown can be "administrative shutdown or remote loss of carrier"

  5. Router/Switch DUT Example Configuration (for Methodology) Data Plane • Line Rate on 100 interfaces • Internet Mix of Packet Sizes. • K’s of Flows • Configure QoS Control Plane • 100 Sessions (20 EBGP, 80 IBGP) • 300K selected routes, 2M Route Instances • 80 Adjacencies • 5K routes (2500 inter-area, 2500 intra-area) • 20 Adjacencies • 1K FECs • 5K Groups joined • 1.5K tunnels (250 ingress tunnels, 250 egress tunnels, and 1K mid-point tunnels) • 10 targeted peers (LDP over RSVP) BGP Security Policy Security Plane • 200 ACLs • 200 ACEs OSPF Traffic Forwarding LDP PIM-SM Manageability MPLS-TE Management Plane • 1K SNMP GETs per minute • 1 telnet session open every 10 minutes • 1 telnet session closed every 10 minutes • Enable Debug and Logging Instability • 200K BGP route flaps every 10 minutes • 1K IGP route flaps every minute • 100 MPLS-TE reroutes every minute • Cycle interfaces - 1 Link Loss every minute • >100% offered load to outbound interface

  6. Question Is this document ready to move forward to Area Director?

More Related