ATIS 0600015 03-2016 Energy Efficiency for Telecommunication Equipment Methodology for Measurement and Reporting for Router and Ethernet Switch Products.pdf

1、 AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS ATIS-0600015.03.2016 Energy Efficiency for Telecommunication Equipment: Methodology for Measurement and Reporting for Router and Ethernet Switch Products ATIS-0600015.03.2016 ii Foreword The information contained in this Foreword is not part of this

2、 American National Standard (ANS) and has not been processed in accordance with ANSIs requirements for an ANS. As such, this Foreword may contain material that has not been subjected to public review or a consensus process. In addition, it does not contain requirements necessary for conformance to t

3、he Standard. The Alliance for Telecommunication Industry Solutions (ATIS) serves the public through improved understanding between providers, customers, and manufacturers. The Sustainability in Telecom: Energy and Protection (STEP) Committee formerly the Network Interface, Power, and Protection Comm

4、ittee (NIPP) engages industry expertise to develop standards and technical reports for telecommunications equipment and environments in the areas of energy efficiency, environmental impacts, power, and protection. The work products of STEP enable vendors, operators and their customers to deploy and

5、operate reliable, environmentally sustainable, energy efficient communications technologies. STEP is committed to proactive engagement with national, regional, and international standards development organizations and forums that share its scope of work. ANSI guidelines specify two categories of req

6、uirements: mandatory and recommendation. The mandatory requirements are designated by the word shall and recommendations by the word should. Where both a mandatory requirement and a recommendation are specified for the same criterion, the recommendation represents a goal currently identifiable as ha

7、ving distinct compatibility or performance advantages. Suggestions for improvement of this document are welcomed. They should be sent to the Alliance for Telecommunications Industry Solutions, STEP, 1200 G Street NW, Suite 500, Washington, DC 20005. At the time it approved this document, STEP, which

8、 was responsible for its development, had the following roster: K. Biholar STEP Chair (Nokia) J. Krahner, STEP Vice Chair ( AT 10; 100 a=0.1; b=0.8; c=0.1 (IPv4) Edge Router 3-6% 0; 10; 100 a=0.1; b=0.8; c=0.1 IPv4/6/MPLS Core Router 20-30% 0; 30; 100 a=0.1; b=0.8; c=0.1 IPv4/6/MPLS wdPTTEER =3*2*1*

9、ucubua PPPPw +=ATIS-0600015.03.2016 5 Table 2 Class Definitions, TEER Calculation Parameters and Load profiles for Ethernet Switching Products Class Representative utilization % of utilization for energy measurements, u1, u2, u3 Weight multipliers a, b, c Traffic Profile Simple IMIX, Unicast Access

10、1-3% 0; 10; 100 a=0.1; b=0.8; c=0.1 Ethernet High Speed Access 5-8% 0; 10; 100 a=0.1; b=0.8; c=0.1 Ethernet Distribution/Aggregation 10-15% 0;10;100 a=0.1; b=0.8; c=0.1 Ethernet Core 15-20% 0; 30; 100 a=0.1; b=0.8; c=0.1 Ethernet Data Center 12-18% 0; 30; 100 a=0.1; b=0.8; c=0.1 Ethernet 5.3 TEER Me

11、tric Definition (modular) TEER for modular packet-based network systems can also be estimated as throughput measured for components/modules (Ti) divided by the sum of weighted components/modules power (energy consumption) (Pwi): Where: Ti= Individual Module Throughput Pwi= Individual Module Weighted

12、 Power Pwbase= Weighted Power of a Base System Excluding Modules Modular weighted power Pwiand Pwbaseare calculated with the following formulas: Where: Pwi= Weighted Module Power Pwbase= Weighted Power of a Base System Excluding Modules (a, b, c) = Weighting for power at each utilization level, wher

13、e a + b + c = 1.0 (Pu1, Pu2, Pu3) = Module power at system utilization level (Pbase_u1, Pbase_u2, Pbase_u3) = Base power at system utilization level =+=niwiwbaseniiPPTTEER113*2*1*ucubua PPPPwi +=3_*2_*1_*ubasecubasebubasea PPPPwbase +=ATIS-0600015.03.2016 6 NOTE: Modular energy consumption and throu

14、ghput are vendor approximations. When a modular TEER is provided, a representative-configuration TEER shall also be provided for comparison purposes. 5.4 TEER Evaluation To compare EE of products, they shall belong to the same product class. Recommended product classes are listed in Annex A. The cla

15、ss description covers the expected applications for Equipment Under Test (EUT) deployed at certain points in the network. If the system can be deployed in multiple roles, multiple TEER ratings can be provided. Examples of listing: 1. Medium Core Router, TEER = 42 (representative HW/SW configuration

16、follows). 2. Small Edge Router, estimated TEER = 50 (modular configuration based on component/module ratings). See Annex A for Classification Tables. Due to a wide variety of features and functions available on the EUT, it is very essential to report all features and functions active in the test con

17、figuration as described in Tables A.1 and A.2. 6 Test Procedure 6.1 General Measurement Condition The general requirements for measuring energy efficiency are defined in ATIS-0600015.2013. The following are the general conditions for measurements within this standard: The equipment is to be powered

18、and placed into the relevant operating mode. Allow the equipment to stabilize in this mode for 15 minutes. Measure the power for a period of 15 minutes. If the power varies over the 15 minute measurement time interval, an average of the measurement will be calculated. 6.2 Equipment Configuration All

19、 testing shall be performed on a fully-loaded chassis, as defined by the referenced application. If there are customer specific applications defining redundancy requirements, they should be clearly documented in the report. All ports shall be in an active state and passing or ready to pass traffic.

20、System software (SW) shall be properly configured prior to the test and all the necessary HW components installed. HW and SW shall be representative of a production unit. There is no EUT configuration change allowed any time beyond preparation phase. This includes (but is not limited to) external co

21、nfiguration commands, scripts executing configuration commands on EUT during testing, etc. 6.3 TEER Measurements Modular Method If the vendor chooses to provide the “modular” TEER estimates, it may be required to build more than one setup if the total number of modules exceeds the number of availabl

22、e slots in a chassis (or if some modules cannot be used together). In this case, the “base” system configuration is defined as a common system parts, used by all modules. It may include chassis, fan tray, routing engine, etc. ATIS-0600015.03.2016 7 At this time, all other system slots should be full

23、y populated with “function” modules, not necessary the same, all passing traffic at the same rate: idle, representative, or maximum Non-Drop Rate (NDR). Each test performed on complete system and then without one module at the time, following steps in 6.5. The power for each “function” module is the

24、 difference between total system power with and without this “function” module. NOTE: Throughput and energy consumption may be affected by interaction between the system and module under test, so total calculated numbers may be not exactly the same as in representative test results. Therefore, vendo

25、rs are advised to utilize representative testing whenever possible. If modular TEER results are provided, this should be explicitly noted. NOTE: It is acceptable to use cascaded/snaked traffic between ports on line cards for base chassis power measurements that are not throughput related. Table 3 Ex

26、ample of Modular System Hardware Data Reporting Module Name Part number Maximum Throughput (egress only) Power (W) u1=0% u2=30% u3=100% Base system 800-xxxxx-01 na 150 150 170 Module 1 800-zzzz-02 40 Gbps 200 220 240 Module 2 800-xxxxx-03 20 Gbps 120 130 150 . . Module N Actual module names may be d

27、ifferent for different products. 6.4 Traffic Generation/Operational Conditions 6.4.1 Traffic Topology If the ports on EUT can be grouped into “network/uplink” and “access/downlink” sides, according to vendor discretion, then traffic shall be run from every “network” side port to every “access” side

28、port and vice-versa, thus forming full mesh traffic between two groups. All streams originated from every port shall be the same capacity. If all ports on EUT have identical roles, then full mesh traffic with identical capacity streams between all ports shall be used. For modular systems with 6 or m

29、ore modules, it may be advantageous to permit a multi mesh configuration to facilitate a modular test method, provided there is more than one mesh with at least three modules per mesh. For EUT with 40 GBs and higher speed ports it is permitted to use vertical “snake”/cascade topology with one port o

30、n each line card used for mesh traffic. Use throughput numbers on meshed ports for total system throughput calculation. ATIS-0600015.03.2016 8 Figure 6.1 Topology for “Vertical” Snake with Partial Mesh Traffic Black lines show ports connected in mesh traffic; each talk to all others; total N ports.

31、White lines show internal cross connect/VLAN “snake” connected ports. Yellow line proved traffic for “snaked” ports. 6.4.2 Use of Traffic Generators Traffic generators are used to simulate traffic and collect the performance-related results according to the test conditions. Generators have to be con

32、figured for the correct traffic topology and traffic profile. ATIS-0600015.03.2016 9 Figure 6.2 Example EUT Test Interconnect for Two Groups of Ports 6.5 Measurement Procedure Prior to testing, the EUT shall be configured according to class requirements and offered load defined in the class requirem

33、ents (Annex A). Prior to the actual test, the EUT shall be exposed to environmental conditions outlined in ATIS-0600015.2013. The procedure consists of four major steps. 6.5.1 Step 1: Qualification The first run determines the maximum load that can be sustained at Non Drop Rate (NDR). Any methodolog

34、y is suitable, including binary search (similar to RFC2544), heuristics, or known maximum load values. There is no time limit for this run. The run is complete after a maximum (lossless) line rate is determined. The following three runs should be separated with idle time of 300 seconds or less. If t

35、he test class requires the EUT to be “primed” with control plane information (ARP/MAC/route learning, etc.), this shall be completed within the idle time window. Traffic Generator E U T Downlink Port Uplink Port ATIS-0600015.03.2016 10 6.5.2 Step 2: Full Load The second run applies the NDR (identifi

36、ed at step 1) to the EUT for period of 15 minutes. Power shall be sampled for the entire period, and average consumption P100 recorded. 6.5.3 Step 3: Utilization (u2) The third run reduces the line rate to utilization (u2) and runs for another 15 minutes. Power shall be sampled for the entire period

37、, and average consumption Purecorded. Load reduction is achieved by reducing the line rate on all configured ports. Packet loss during any run (if seen) invalidates the measurement and resets testing to the qualification run to provide a better NDR estimate. At any moment during this run, the EUT sh

38、ould be able to return to full NDR load. Failure to do so disqualifies the test results. 6.5.4 Step 4: Idle Load Run the EUT idle for another 15 minutes. Power shall be measured for the entire period, and the average value shall be recorded. Load reduction is achieved by setting line data rate to 0%

39、 on all configured ports. At any moment during this run, the EUT should be able to return to full NDR load. Failure to do so disqualifies the test results. 7 Reporting Can go to Internet (Full BGP) Table with 512MB or above Typically up to half - T3/E3 IMIX Traffic IPSec Tunnels: up to 200 ACL Entri

40、es: 1000 QoS: 4-8 Classes WAN Optimization: 10 sites/peers Configured Forwarding Options: MPLS, IPv4 Configured Forwarding Options: MPLS, IPv4 L Function of Memory and CPU; Can go to Internet (Full BGP) Table with 512MB or above Typically up to T3/E3 IMIX Traffic IPSec Tunnels: up to 500 ACL Entries

41、: 2000 QoS: 4-8 Classes or even more WAN Optimization: 50 sites/peers Additional Features: ALCs, QoS, Firewall, IPSec, Voice, WAN Optimization, etc. Additional Features: ALCs, QoS, Firewall, IPSec, Voice, WAN Optimization, etc. Edge S M BGP: IPv4: 300000 IGP: 10000 VRF Scale: 250 VPNv4: 250k Pseudo-

42、wires: 8k VPLS Scale: 500 BGP, T-LDP Sessions: 1000 Attachments Ccts: 16k TE Tunnels (head/tail): 500 Maximum customer facing GE ports + redundant uplink 1-GE ports Configured Routing Protocols: BGP, OSPF, ISIS, LDP L BGP: IPv4: 1M IGP: 10000 VRF Scale: 500 VPNv4: 500k Pseudo-wires: 16k VPLS Scale:

43、1k BGP, T-LDP Sessions: 1000 Attachments Ccts: 16k TE Tunnels (head/tail): 1k Maximum customer facing GE ports + redundant uplink 1-GE ports Configured Forwarding Options: MPLS, IPv4, IPv6 Core S IPv4 BGP: 300k IPv6 BGP: 5k IGP Routes: 4000 Multicast routes: 5k IPv4 BGP: 300 IPv6 BGP: 50 Subintf: 10

44、00 TE Tunnels (Mid): 2K Up to 16 x 10G Maximum 10G ports + redundant 40G core uplinks Configured Routing Protocols: BGP, OSPF, ISIS, LDP, PIM-Multicast M IPv4 BGP: 300k IPv6 BGP: 15k IGP Routes: 8000 Multicast routes: 10k IPv4 BGP: 500 IPv6 BGP: 100 Subintf: 2000 TE Tunnels (Mid): 5K 24 72 x 10G Max

45、imum 10G ports + redundant 40G core uplinks Configured L2VPN Services: VPWS, VPLS, Inter-working ATIS-0600015.03.2016 12 Class S,M,L Route Scale Service Scale Logical Interface Scale Port Configuration Typical Feature Set L IPv4 BGP: 500k IPv6 BGP: 50k IGP Routes: 15000 Multicast routes: 15k IPv4 BG

46、P: 1000 IPv6 BGP: 200 Subintf: 4000 TE Tunnels (Mid): 10K 96 192 x 10G Maximum 10G ports + redundant 40G core uplinks Configured Forwarding Options: MPLS PWE3, IP (GRE), L2TPv3 Additional Features: ACLs, QoS, Netflow, EoMPLS, MPLS TE Table A.2 Ethernet Switch Classifications Class Number of downlink

47、 ports Uplink Count total hours per year: 8760, non working hours: 6680. Where: Pwps = Weighted power with power saving enabled Pw= Weighted power (Energy Consumption Rate) Pps= Power saving mode (Energy Consumption Rate) C.2 Supplementary Metric Definition for Explicit Power States Identical to wha

48、t is described in clause 6.5 with relaxation on power state controls: EUT is allowed to move between power states at different test runs automatically or with operator input and is not required to return to full performance T100during test runs U1 and U2 immediately. TEERNRT = Tw / Pw, where Tw = a*

49、 Tu1+ b*Tu2+ c*T100, u1=10%, u2=20%, a=0.2,b=0.25, c=0.55 C.3 Supplementary Metric Definition for Peak Metric There is no new test method required. Information on T100 and P100is already available from normal TEER test procedure TEERpeak = T100/ P100876066802080 +=psw PPPwpsATIS-0600015.03.2016 16 C.4 ITU-T Recommendation L.1310 ITU-T recommendation L.1310 uses the metric called EER based on the same measurements, but using weighted throughput in addition to weighted power. Where Pwis the same as in TEER, and the