Scope - GISFI



Energy Efficiency for Telecommunication Equipment: Methodology for Measurement and Reporting for Router and Ethernet Switch ProductsContents TOC \o "1-3" \h \z \u 1Scope PAGEREF _Toc371075471 \h 42Definitions PAGEREF _Toc371075472 \h 43Normative References PAGEREF _Toc371075473 \h 64Equipment Category Description PAGEREF _Toc371075474 \h 75Metric Definition PAGEREF _Toc371075475 \h 75.1Introduction PAGEREF _Toc371075476 \h 75.2TEER Metric Definition (representative) PAGEREF _Toc371075477 \h 85.3TEER Metric Definition (modular) PAGEREF _Toc371075478 \h 95.4TEER Evaluation PAGEREF _Toc371075479 \h 106Test Procedure PAGEREF _Toc371075480 \h 106.1Measurement considerations PAGEREF _Toc371075481 \h 106.1.1Power measurements PAGEREF _Toc371075482 \h 106.1.2Environmental Considerations PAGEREF _Toc371075483 \h 106.1.3Electrical Considerations PAGEREF _Toc371075484 \h 116.1.4Power measurement equipment considerations PAGEREF _Toc371075485 \h 126.1.5Power source considerations PAGEREF _Toc371075486 \h 126.1.6Equipment stabilization considerations PAGEREF _Toc371075487 \h 126.1.7Measurement duration PAGEREF _Toc371075488 \h 126.1.8Test configurations PAGEREF _Toc371075489 \h 136.2Equipment Configuration PAGEREF _Toc371075490 \h 136.3TEER measurements — Modular Method PAGEREF _Toc371075491 \h 136.4Traffic generation/Operational Conditions PAGEREF _Toc371075492 \h 156.4.1Traffic topology PAGEREF _Toc371075493 \h 156.4.2Use of traffic generators PAGEREF _Toc371075494 \h 156.5Measurement procedure PAGEREF _Toc371075495 \h 156.5.1Step 1: Qualification PAGEREF _Toc371075496 \h 156.5.2Step 2: Full Load PAGEREF _Toc371075497 \h 166.5.3Step 3: Utilization (u2) PAGEREF _Toc371075498 \h 166.5.4Step 4: Idle Load PAGEREF _Toc371075499 \h 167Reporting and Documentation PAGEREF _Toc371075500 \h 177.1General requirements PAGEREF _Toc371075501 \h 177.2Reporting format PAGEREF _Toc371075502 \h 17Annex A: Classification Examples PAGEREF _Toc371075503 \h 19Annex B : Supplementary Metric PAGEREF _Toc371075504 \h 24Annex C : IMIX Traffic PAGEREF _Toc371075505 \h 26Annex D: Alternative metrics for routers and switches PAGEREF _Toc371075506 \h 29Annex E : Modular measurement method for routers and switches PAGEREF _Toc371075507 \h 32Annex F : Sample Reporting Format PAGEREF _Toc371075508 \h 34ScopeThis document provides a set of requirements and guidelines for calculating the Telecommunication Energy Efficiency Ratio (TEER) of IP routers and switch. The document also provides standardized definitions of operational data rates and condition to be used when calculating theTEER of any given configuration. This document is intended to be used by network operators, equipment manufacturersand re-sellers as a standard method for determining the energy efficiency of Router and Ethernet Switch products. By comparing the TEER reports of multiple platforms that meet a common set of requirements, a communications network operator can select the equipment that best meets their energy efficiency targets.DefinitionsDownlink ports: Group of port facing downstream (access/user side port).Uplink port(s): Group of port facing upstream (network/upstream side port).IMIX traffic:A stateless traffic profile that contains a mixture of frame sizes similar to a composition observed in the Internet (Internet traffic mix).Maximum Demonstrated Throughput: Highest achievable system throughput at Non-Drop Rate(bps).Non-Drop Rate: Non-Drop Rate is the observed system throughput atwhich nopacket drop are recorded (NDR).Port Throughput: Rate of traffic (in bps) passing through a port on a sustain basis in either in either direction, including minimally needed line overhead.Port Utilization: Port Throughput expressed as percentage of theoretical maximum.System Throughput: Sum of throughput on all system port in the egress direction (bps)Example: Maximum throughput for 1G E is 1Gbps.System Utilization: System throughput expressed as percentage of Maximum Demonstrated Throughput.Tester: Packet generator/analyzer platform.Traffic profile: Description of the packet load sent through equipment under test.Active mode:It is the operational mode where all ports (WAN and LAN) are connected. Idle mode:Operational mode with no user data traffic (it is not zero traffic as service and protocol supporting traffic are present), being used although it is ready to be used.Sleep mode: The state that happens after the device detects no user activity for a certain period of time and reduces energy consumption. No user facing LAN ports are connected. The WAN port may be not active. The device will reactivate on detecting a connection from a user port or device.Power state:It is a mode of operation with reduced performance and reduced energy consumption. Power state is a static, not a traffic dependent, mode of operation. Transition between power states is not instant and may incur a delay, during which excess traffic might be lost.Duty cycle: Duration for each power mode to a specific time period, day, week, etc.Functional unit: The term functional unit is considered a performance representation of the system under analysis, for example, throughput of the router or switch measured inGbit/sec. Sometimes the term is used with the same meaning to indicate useful output or work. ISO 14040 sect 3.20 [ REF _Ref370983028 \r \h \* MERGEFORMAT 7]Normative ReferencesThe following standards contain provisions which, through reference in this text, constitute provisions of this specification.GISFI TR GICT.106, Metrics and Measurement Methods of Telecommunication Equipments: IP Routers; (Release 1), Sept. 2013GISFI TS GICT.100, Metrics and Measurement Methods for Energy Efficiency: General Requirements; (Release 2 Draft), Oct. 2013ATIS-0600015.2009, Energy Efficiency For Telecommunication Equipment: Methodology For Measurement and Reporting - General RequirementsATIS-0600015.03.2009; (07/2009): Energy efficiency for telecommunication equipment: Methodology for measurement and reporting for router and Ethernet switch productsETSI ES 203 136 V1.0.0 (2013-03) Environmental Engineering (EE); Measurement methods for energy efficiency of router and switch equipment ITU recommendation: L.1310; (11/2012); Energy efficiency metrics and measurement for telecommunication equipmentISO 14040:2006, Environmental management ? Life cycle assessment ? Principles and framework.ISO/IEC 17025:2005, General requirements for the competence of testing and calibration laboratoriesATIS 0600315.2007; Voltage Levels for DC-Powered Equipment Used in the Telecommunications Environment; December, 2007.ETSI EN 300 132-2 v2.4.6; Power supply interface at the input to telecommunications and datacom (ICT) equipment; Part 2: Operated by -48 V direct current (dc).Equipment Category DescriptionThis document addresses equipment categorized as Enterprise, Service Provider and Branch office routers and Ethernet switch products. Small office, CPE, and personal networking products are outside the scope of this document. The detailed classification of telecommunication equipment is as per the GISFITS GICT.100 [ REF _Ref370472616 \r \h 2].The present document is applicable to core, edge and access routers as per the classification. Annexure A of this document provides examples of equipment configurations intended for reference to assist the user when evaluating products based on ATIS-0600015.03.2009[ REF _Ref371075708 \r \h 4].Metric DefinitionIntroductionThere are fixed and modular configuration systems. A fixed configuration system has one TEER and follows the test proceduredefined in Clause 6. A modular system consists of a chassis (shelf) with multiple slots that can be equipped with a variety of cards and/or service modules. In such application, TEER is a ratio of throughput and energy consumption at different utilization levels and thus describes relative energy efficiency for a given product [ REF _Ref371075787 \r \h 1], [ REF _Ref371075851 \r \h 3].There could be as many TEER reports for a given chassis-based system as there are ways of configuring it. Furthermore, in order to provide flexibility and scalability, some systems can be extended by adding (stacking) shelves together.Depending on the configuration, the number of modules, and the type of those modules, energy efficiency of a modular packet platform will vary and can be represented with a range of TEER values.To reflect this situation, this standard defines two ways for presenting a TEER for a modular system:A TEER for a given family of products, based on a "representative" HW configuration (as defined by the vendor).A TEER for a specific configuration of products.The TEER value may be either a Certified TEER or a Declared TEER, as defined in ATIS-0600015.2009 [ REF _Ref370474161 \r \h 3]. For example, a vendor may get a Certified TEER for a family of products and provide a Declared TEER for a given configuration to respond to an RFP.The "representative" method will have a TEER for a fixed configuration (combination of modules). This metric can be used to compare similar products from different vendors.The "modular" method allows vendors to establish the energy consumption for each module, so EE for a desired system hardware configuration (combination of modules) can be calculated by the user.NOTE: Providing the module-level data may involve some approximation of throughput and energy usage and therefore can only serve as a guideline.TEER Metric Definition (representative)TEER is defined as a ratio of maximum demonstrated throughput (Td) to weighted power (energy consumption rate) Pw.TEER= TdPw(1)Where:Td = Maximum Demonstrated ThroughputPw = Weighted Power (Energy Consumption Rate)Weighted energy consumption is calculated with the following formula:Pw=a*Pu1+b*Pu2+c* Pu3(2)Where:Pw= Weighted Power(a, b, c) = Weighting for power at each utilization level, where a + b + c=1.0(Pu1,Pu2, Pu3) = Power at system utilization levelThe traffic profile, weights (a,b,c) and system utilization levels (u1, u2, u3) vary according to equipment class and position in the network (see Table 1 and 2). The method for throughput measurement is described in Annex B.Table 1: Class definitions, TEER calculation parameters, and load profiles for Routing ProductsClassRepresentativeUtilization% of utilization forenergymeasurements, u1,u2, u3Weight multipliersa, b, cTraffic ProfileSimple IMIXAccess Router1-3%0; 10; 100a=0.1; b=0.8; c=0.1(IPv4)Edge Router3-6%0; 10; 100a=0.15; b=0.75; c=0.1IPv4/6/MPLSCore Router20-30%0; 30; 100a=0.1; b=0.8; c=0.1IPv4/6/MPLSTable 2: Class definitions, TEER calculation parameters and load profiles for Ethernet Switching ProductsClassRepresentativeutilizationA of utilization forenergymeasurements, u1,u2, u3Weight multipliersa, b, cTrafficProfileSimple IMIX,UnicastAccess1-3%0; 10; 100a=0.1; b=0.8; c=0.1EthernetHigh Speed Access5-8%0; 10; 100a=0.1; b=0.8; c=0.1EthernetDistribution/Aggregation10-15%0;10;100a=0.15; b=0.75; c=0.1EthernetCore15-20%0; 30; 100a=0.15; b=0.75; c=0.1EthernetData Center#12-18%0; 30; 100a=0.1; b=0.8; c=0.1Ethernet# Data Center equipment like switches is not considered within the purview of the current document.Category of equipment addressed within the provisions of the current document is as per Clause 4.Additional metrics that apply to routers and switches that support explicit sleep mode and low power states are defined in Annex D. These metrics and measurement methods may be utilized to compare the energy saving performance of access routers and switches that have hardware support to switch to low power states by turning off relevant parts of the equipment.TEER Metric 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):TEER= i=1nTii=1nPwi(3)Where:Ti= Individual Module ThroughputPwi= Modular Weighted Energy ConsumptionModular weighted energy consumption Pwi is calculated with the following formula:Pwi=a*Pu1+b*Pu2+c* Pu3(4)NOTE: Modular energy consumption and throughput are vendor approximations. When a modular TEER is provided, a representative-configuration TEER shall also be provided for comparison purposes.TEER EvaluationTo compare energy efficiencyof products, they shall belong to the same product class. Recommended product classes are listed in Annex A.The class description covers the expected applications for EUTs 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:Medium Core Router, TEER=42 (representative HW/SW configuration follows).Small Edge Router, estimated TEER = 50 (modular configuration based on component/ module ratings).See Annex A for Classification Tables applicable to IP routers and switches.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 configuration as described in Tables A.1 and A.2.Test ProcedureThe general requirements for measuring energy efficiency of telecommunication equipmentare defined inGISFI TS GICT.100 [ REF _Ref370472616 \r \h 2]. In thesub-clause 6.1, the relevant requirements for measurement and operations of IP routers and switches towards the determination of TEER have been described.Measurement considerationsPower measurementsMeasurement accuracy plays a critical role in determining the energy consumed by telecom equipment at test facilities. Errors due to misconfiguration, insufficient samples can impact the determination of figure of merit for energy efficiency. The DC power equipment powering the equipment under test (EUT) should confirm to the electromagnetic noise requirements as specified by applicable standard [ATIS 0600315.2007 [ REF _Ref371019511 \r \h 9] or equivalent BIS specification in India]. All power measurement equipment used for taking measurements shall be in a current state of calibration as specified by the applicable requirements [In India, labs accredited by National Accreditation Board for Testing and Calibration Laboratories or equivalent].Environmental ConsiderationsThis section provides the applicable environmental considerations for test and measurement of telecommunication equipment. Environmental conditions for consideration include:a. TemperatureThe equipment should be evaluated at an ambient temperature of 25°±3?C (77oF ±5oF). The equipment itself should stay online or operate at this air temperature for no less than three hours prior to the test. No ambient temperature changes are allowed until the test is complete.b. HumidityThe telecommunication equipment should be evaluated at a relative humidity of 30% to 75%. c. Barometric pressureThe equipment should be evaluated at site pressure between 860 to 1060 hPa. No targeted airflows are allowed except for regular ambient room, data center or rack cooling.Electrical ConsiderationsThis section provides the applicable electrical considerations for test and measurement of telecommunication equipment. Electrical conditions for consideration include:a. Voltage supply [DC powered equipment]DC powered equipment (-48 V DC systems):Majority of telecommunication equipment (servers, routers, switched, transport etc.) are powered from central DC power plants. In such systems, the nominal load voltage can be from 50 to 55 VDC at the utilization equipment. For these classes of equipment, the DC voltage powering the equipment shall be chosen in the range of - 55.5 to -52.5?V (54±1.5?V). For telecommunications equipment intended to be powered by local DC power obtained from small AC to DC supplies, testing at -48VDC (± 1%) is recommended.DC powered equipment (other than -48 V DC systems):Unless otherwise specified in a supplemental standard to this General Requirements specification, equipment using nominal DC voltages other than -48 V DC shall be evaluated at ± 2% of the specified voltage.b. Voltage supply [AC powered equipment]The input to the equipment (all active feeds) should be the nominal specified voltage ±5% and the specified frequency ±1%. In case the equipment can work at a different nominal voltage, the measure shall be executed at one of the nominal voltages. The total harmonic distortion <= 2% up to and including the 13th harmonic.Unless otherwise specified in a supplemental standard to this general requirements specification document, the environmental conditions for the measurements would be as per the applicable national or international standards [ATIS-0600015.2009 [ REF _Ref370474161 \r \h 3], ITU Recommendation L. 1310 [ REF _Ref370734614 \r \h 6], ETSI EN 300 132-2 v2.4.6 [ REF _Ref371019884 \r \h 10] or equivalent national standard].Power measurement equipment considerationsIt is recommended that integrated power analyzer equipment be utilized for the purpose of measurements. However, an equivalent setup (voltage and current measurement equipment) with high sampling frequency and data storage capability is acceptable. Unless otherwise specified in a supplemental standard to this general requirements specification document, the power measurement equipment requirements would be as per the applicable national or international standards [ATIS-0600015.2009[ REF _Ref370474161 \r \h 3], ITU Recommendation L. 1310 [ REF _Ref370734614 \r \h 6] or equivalent national standard]. Every active power feed should have the power (current) meter installed in the power line with a desired accuracy not less than ±1% of the actual power level. The power meter should include correction for power factor (PF) on AC feeds; otherwise, it will be necessary to also record the power factor in the measurement report. All energy consumption calculations are based on averaging multiple readings over the course of measurements. Power meters should be able to produce no less than 100 evenly-spaced readings in every full test cycle duration. Power measurement instruments (such as voltmeters and ampere meters or power analyzers) shall have a resolution of 0.5% or better. AC power measurement instruments shall have the following minimum characteristics:A minimum digitizing sample rate of 40 kHz.Input circuitry with a minimum bandwidth of 80 kHz.Capability of accurate readingsof waveforms having a crest factor up to at least?5.Power factor correction and reporting.Power source considerationsPower sources used to provide power to the EUT shall be appropriately over provisioned for any transient. A minimum of 1.5 times the power rating of the EUT is recommended.Equipment stabilization considerationsThe equipment is to be powered and placed into the relevant operating mode.Allow the equipment to stabilize in this mode for 15 minutes.Measurement durationMeasurements are recorded for a minimum specified duration after the EUT reaches a stable condition of operation. 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.Test configurationsEquipment with multiple power connections (such as those provisioned with redundant power supplies) shall be configured with all power supply interfaces active and the total power flow from all these interfaces is computed to obtain the total system power consumption.Traffic parameters and mode of load generation shall be defined in supplemental standards. As a general requirement, it is to be ensured that traffic and system is so configured as to exercise all the required features and functions of the equipment.The ambient temperature for the measurement is considered to be 25°±3?C (77oF ±5oF). The energy consumed by the cooling fans within the EUT may be different at different ambient temperatures. The information reported in the measurement report should account for the fan power expected when the equipment operates in a controlled environment of the lab at a temperature in the range 25°±3?C (77oF ±5oF). One of the following recommended methods must be employed to obtain the controlled measurement conditions:Test in a thermally controlled environment with recommended temperature of 27?C (80.6 oF)If fans are configurable, they shall be configured with speed settings to simulate the operating environment of 27?C (80.6 oF) and barometric pressure 1013.25 hPa at sea level.If fans are not configurable, a fan speed adjustment must be added to the measured system power.Equipment ConfigurationAll 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.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 not limited to) external configuration commands, scripts executing configuration commands on EUT during testing, etc.Measurements shall be carried out for the appropriate applicable traffic conditions and mode of generation. Power measurements would be averaged over the recommended time duration. All energy measurements shall be taken at the main system power supply unit incorporating all the operational modules.TEER measurements — Modular MethodIf 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 available slots in a chassis (or if some modules cannot be used together).-82423114986000In 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.At this time, all other system slots should be fully populated with "function" modules, not necessary the same, all passing traffic at the same rate: idle, representative, or maximum mon system is equipment with no service card installed and including main processing cards, fan try, power input cards, etc., which is used by all the service cards [ REF _Ref370982555 \r \h 5].Each test performed on complete system and then without one module at the time, following steps in Annex E.The power for each "function" module is the 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.Table 3: Example of Hardware modular system data reportingModuleNamePart numberMaximumThroughput(egress only)Power (Energy Consumption), WTEERu1=0%u2=-30%u3=100%N/ABase system800-xxxxx-02naModule 1800-zzzz-0240 Gbps200220240Module 2800-xxxxx-0320 Gbps120130150.......Module NTotalN/A500 Gbps2000W2100 W2500W0-1000Actual module names may be different for different products.Traffic generation/Operational ConditionsTraffic topologyIf 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 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.Use of traffic generators-78803663500Traffic generators are used to simulate traffic and collect the performance-related results according to the test conditions. Generators have to be configured for the correct traffic topology and traffic profile.Traffic of Simple IMIX type as defined in Table C.1 of Annex C shall be utilized for the measurement purposes.Downlink PortsEUTTraffic GeneratorUplink PortsDownlink PortsEUTTraffic GeneratorUplink PortsFigure 1: Example EUT Test Interconnect for two groups of portsMeasurement procedurePrior to testing, the EUT shall be configured according to class requirements and offered load defined in the class requirements (Annex A). Prior to the actual test, the EUT shall be exposed to environmental conditions outlined in sub-clause 6.1.2 based on GISFI TS GICT.100 [ REF _Ref370472616 \r \h 2].The procedure consists of four major steps.Step 1: QualificationThe first run determines the maximum load that can be sustained at Non Drop Rate (NDR). Any methodology 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 .If the 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.Step 2: Full LoadThe second run applies the NDR (identified at step 1) to the EUT for period of 15 min. Power shall be sampled for the entire period, and average consumption P100 recorded.Step 3: Utilization (u2)The third run reduces the line rate to utilization (u2) and runs for another 15 min. Power shall be sampled for the entire period, and average consumption Pu, recorded. 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.190500010515601207135ATIS-0600015.03.200900ATIS-0600015.03.2009Step 4: Idle LoadRun 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% on all configured ports.Reporting and DocumentationGeneral requirementsAll test reports shall be written according to GISFI TS GICT.100 [ REF _Ref370472616 \r \h 2].Test reports shall comply with the general requirements for testing and calibration laboratoriesspecified by [ REF _Ref371002022 \r \h 8].Additionally, the sub-clause 7.2 lists the basic requirements of the reporting format and Annex F provides a sample reporting format based on these requirements. The measurement report must have the following details:a. Details of supplemental standards applicable to the equipmentb. Time, Date and location of test.c. Physical and environmental configuration of the test equipment.d. Model, Serial number, Software and Hardware versions supported on the equipment during the test.e. List of features supported by the equipment and those activated during the test.f. Traffic generation profile and duration of traffic generation.g. Test and measurement equipment calibration and configuration details.h. System setup diagram, detailing the electrical and network connections and configurations.i. Energy or power measurement results for all applicable test profiles as detailed in the applicable supplemental standards.j. Start and Stop times for the record of measurements undertaken.Reporting formatThe general requirements for a test report are contained in ISO/IEC 17025 [9]. The following basic information must accompany the measurement report for energy efficiency of telecommunication equipment.a. A Title: Energy Efficiency Measurement Reportb. Name of the equipment under test, Manufacturer detailc. Equipment category as per this documentd. Applicable standards for energy efficiency measuremente. Name and address of the measurement laboratory, location where the measurements were carried out.f. Unique identification of the measurement reportg. Name and address of the manufacturerh. Identification of the method used.i. Description of measurement conditions and unambiguous identification of the equipment tested.j. The date of performance of the measurement and generation of reportk. The measurement report with appropriate metrics and units of measurements as described in the supplemental standards to this document.l. The name(s), function(s) and signature(s) or equivalent identification of person(s) authorizing the measurement report.Annex A: Classification ExamplesExtract from ATIS-0600015.03.2009 [ REF _Ref371075708 \r \h 4]A.1 Reference TablesThe following tables are intended for reference to assist the user when evaluating products.Table A.1: Router ClassificationsClassS,M,LRoute ScaleServiceScaleLogicalInterface ScalePortConfigurationTypical Feature SetConfigured RoutingProtocols: BGP, OSPF,EIGRP, Static RoutingAccessSN/ATypically up to T1worth IMIX trafficUp to 50 users per LANUp to 500 ACL entriesTypically up to 4 classesWAN Optimization: 5sites/ peersDLS up to T1 forSmall BranchConfiguration, upto 50 users on LANMFunction ofMemory andCPU; Can go toInternet (FullBGP) Tablewith 512MB oraboveTypically up to half -T3/E3 IMIX TrafficIPSec Tunnels: up to 200ACL Entries: 1000 QoS:4-8 ClassesWAN Optimization: 10sites/peersConfiguredForwardingOptions: MPLS,IPv4Configured ForwardingOptions: MPLS, IPv4LFunction ofMemory andCPU; Can go toInternet (FullBGP) Tablewith 512MB oraboveTypically up to T3/E3IMIX Traffic IPSecTunnels: up to 500 ACLEntries: 2000 QoS: 4-8Classes or even moreWAN Optimization: 50sites/peersAdditionalFeatures: ALCs,QoS, Firewall,IPSec, Voice, WANOptimization, etc.Additional Features:ALCs, QoS, Firewall,IPSec, Voice, WANOptimization, etc.EdgeSMBGP: IPv4:300000IGP: 10000VRF Scale: 250VPNv4: 250kPseudo-wires: 8kVPLS Scale: 500BGP, T-LDPSessions: 1000AttachmentsCcts: 16kTE Tunnels(head/tail): 500Maximumcustomer facing GEports + redundantuplink 1-GE portsConfigured RoutingProtocols: BGP, OSPF,ISIS, LDPLBGP: IPv4: 1MIGP: 10000VRF Scale: >500VPNv4: 500kPseudo-wires: >16kVPLS Scale: 1kBGP, T-LDPSessions: 1000AttachmentsCcts: 16kTE Tunnels(head/ tail): 1kMaximumcustomer facing GEports + redundantuplink 1-GE portsConfigured ForwardingOptoins: MPLS, IPv4,IPv6CoreSIPv4 BGP: 300kIPv6 BGP: 5kIGP Routes:4000Multicastroutes: 5kIPv4 BGP: 300IPv6 BGP: 50Subintf: 1000TE Tunnels (Mid): 2KUp to 16 x 10GMaximum 10Gports + redundant40G core uplinksConfigured RoutingProtocols: BGP, OSPF,ISIS, LDP, PIM-MulticastIPv4 BGP: 300kIPv6 BGP: 15kIPv4 BGP: 500Maximum 10GConfigured L2VPNMIGP Routes:8000IPv6 BGP: 100Subirttf: 200024- 72 x 10Gports +redundant40G core uplinksServices: VPWS, VPLS,Inter-workingMulticastroutes: 10kTE Tunnels (Mid): 5KConfigured ForwardingIPv4 BGP: 500kOptions: MPLS PVVE3, IPIPv6 BGP: 50kIPv4 BGP: 1000Maximum 10G(GRE), L2TPv3LIGP Routes:15000IPv6 BGP: 200Subintf: 400096- 192 x 10Gports + redundant40G core uplinksAdditional Features:Multicastroutes: 15kTE Tunnels (Mid): 10KACLs, QoS, Netflow,EoMPLS, MPLS TETable A.2: Ethernet Switch ClassificationsClassNumber ofdownlinkportsUplinkCount &TypeThroughputCriteriaTypical Feature SetAccessS12 - 501Gbps2-41GbpsNon-Drop rate= 0.IPv4/IPv6 Forwarding, IPv4/1Pv6 MulticastSnooping, VLAN's, IGMP, MLD,802.1d/s/w, 802.1q/p, Port Security/802.1x,Radius, Mirroring, 802.3AD/LACP, SYSLOG,SNMP1/ 2c/3M50- 1921Gbps4 1GbpsNon-Drop rate=13.L192- x1Gbps4-81GbpsNon-Drop rate= 0.High Speed AccessS12- 501Gbps2 1°GbpsNon-Drop rate= 0,IPv4/IPv6 Forwarding, IPv4/IPv6 MulticastSnooping, VLAN's, IGMP, MLD,802.1d/s/w, 802.1q/p, Port Security/ 802.1x,Radius, Mirroring, 802.3AD/LACP, SYSLOG,SNMP1/ 2c/ 3M50- 1921Gbps4 10GbpsNon-Drop rate= 0'L192- x1Gbps4- 810GbpsNon-Drop rate= 0'Distribution & / orAggregationS8- 48 1Gbps2 10GbpsNon-Drop rate= O.IPv4/IPv6 Forwarding, OSPF, RIP, PIM,OSPFv3, RIPng, Access Control, IPv4/IPv6Multicast Snooping, VLAN's, IGMP, MLD,802.1d/s/w, 802.1q/p, Port Security/ 802.1x, Radius, Mirroring, 802.3AD/LACP, SYSLOG,SNMP1/ 2c/ 3M48 - 961Gbps2- 810GbpsNon-Drop rate= O.L96- 1921Gbps8-16 10GbpsNon-Drop rate=.XL192- x1Gbps16- x10GbpsNon-Drop rate= 0.CoreS8- 1610Gbps4 10GbpsNon-Drop rate= 0.IPv4/1Pv6 Forwarding, OSPF, RIP, PIM,OSPFv3, RIPng, Access Control, IPv4/IPv6Multicast Snooping, VLAN's, IGMP, MLD,802.1d/ s/ w, 802.1q/p, Port Security/802.1x, Radius, Mirroring, 802.3AD/LACP, SYSLOG,SNIVIP1/ 2c/ 3M16- 3610Gbps4- 810GbpsNon-Drop rate= 0L36 - 4810Gbps8-1210GbpsNon-Drop rate= O.XL48- x10Gbps12- 1610GbpsNon-Drop rate= 0.Data CenterS12 - 481Gbps2 10GbpsNon-Drop rate= 0.IPv4/IPv6 Forwarding, IPv4/IPv6 MulticastSnooping, VLAN's, IGMP, MLD,802.1d/s/w, 802.1q/p, Port Security/802.1x,Radius, Mirroring, 802.3AD/LACP, SYSLOG,SNMP1/ 2c/ 3Annex B: Methods for effective throughput computationExtract from ATIS-0600015.03.2009 [ REF _Ref371075708 \r \h 4]B.1 Methods for effective throughput computationB.1.1 Method 1In first method, the measured throughput is decomposed into a packet-per-second rate and packet size corresponding to the load. If packet sizes are variable, the average proportions are to be computed. Next, all applicable minimum overheads are added to compute the effective wire –rate, at which the EUT performed.Example 1: The EUT is a packet platform that can drive ten 10Gbps Ethernet ports at 7,291,702 frames per second each with 64B Ethernet frames without loss. According to the tester, this corresponds to 7,291,702 packet-per-second rate per each port.Td= 10 x 7,291,702 x 8 x (64+1+7+12) = 49.000237440 Gbps (accounting for Ethernet start of frame, preamble and minimum interpacket gap).B.1.2 Method 2 In second method, the traffic generator itself can report port utilization (percent of theoretical maximum). In this method, the well-known line rates for selected transport interface type are multiplied by port utilization to calculate the final data rate.Example 2: The EUT is a VPLS edge platform with 10Gbps Ethernet port (LAN PHY) on access side (toward Ethernet CPEs ) and 10Gbps Ethernet ports on the network side (toward MPLS core network). The EUT can forward the incoming L2 frame (256 bytes each ) toward MPLS core egress interface utilization of 100percent. However, because of the 1:1 matching of access and network sides, the access side can only be utilized at 99.22 percent to allow lossless application of the (minimally) 4-byte MPLS L2 VPN header required for packets on the network side. Same limitation is seen in the opposite direction, where the incoming network-side packet can only fill the access-side interface at 99.22 percent after the headers are stripped.Well-known data rate for 10Gbps Ethernet IEEE 802.3ae is 10,000 Mbit/sTd= 10 x10.000 x 1 +10 x 10.000 x0.9922 = 19.922 GbpsB.1.3 Other notesIdeal timeout inserted by EUT to compensate for asymmetric test pattern are not counted for (see Example 2). Also, note that Td should not account for any optional overheads not required by the traffic profile.Example 3: The EUT is an Ethernet switch that can operate at 100 percent line utilization when configured for 802.1q packet encapsulation (VLAN headers applied). The same switch can only operate at sub-line rate speed when not configured for VLAN encapsulation (for the same L3 packet payload).The measurement results from the second case should be used, unless the test profile for this particular equipment class specifically requires VLAN encapsulation to be present.Annex C: IMIX TrafficExtract from ATIS-0600015.03.2009 [ REF _Ref371075708 \r \h 4]The reference used for understanding the distribution of packet lengths on the real Internet comes fromdata collected by the Measurement & Operations Analysis Team of the National Library for AppliedNetwork Research (NLANR) project during the month of February, 2001 under the National ScienceFoundation Cooperative Agreement No. ANI-9807479, and the National Laboratory for AppliedNetwork Research. (The raw data can be found on the NLANR web site at< >.)Briefly summarized, a total of 342 million packets were sampled and recorded at the Merit Networkmonitor site during this period. The average packet size was 402.7 bytes, with the following packetsizes and types occurring most frequently:? 40 bytes: TCP packets with header flags but no payload (20 bytes of IP header and 20 bytes ofTCP header), typically sent at the start of a new TCP session. Approximately 35% of Internetpackets measured during this period were exactly 40 bytes long. Because these packets are small,they represent only 3.5% of the traffic.? 576 bytes: TCP packets from old implementations that use this Maximum Segment Size (MSS).These packets account for about 11.5% of the packets and 16.5% of Internet traffic.? 1500 bytes: Packets corresponding to the Maximum Transmission Unit (MTU) size of an Ethernetconnection. Most data transferred on the Internet consists of full–size Ethernet frames,accounting for about 10% of the packets but 37% of the traffic.Several other packet sizes occurred more frequently than normal (where normal is defined as morethan 0.5% of all packets). In order of frequency, they are 52, 1420, 44, 48, 60, 628, 552, 64, 56, and 1408bytes.About 1.2% of all packets were smaller than 40 bytes (e.g., 28, 32 bytes).They represent a small percentage of overall traffic (0.1%), but a router will nevertheless need toforward these very small packets.A realistic mixture of packet sizes can be approximated by a set of packet lengths (three or more) thatrepresent the common modal lengths, plus an even distribution of every other packet size. (Thenumber of modal lengths determines the accuracy of the packet mixture -- i.e., its correlation to a set ofreal measurements.)Three traffic models are described below: Simple IMIX, Complete IMIX, and Accurate IMIX.The following Simple IMIX packet size mixtures shall be used:Table C.1: Simple IMIXPacket Size (Bytes)Proportion of TotalBandwidth (Load)407 parts6.856%5764 parts56.415%15001 part36.729%Some router manufacturers commonly use this mixture as a "quick and dirty" approximation of theInternet packet mixture.The Simple IMIX has an average packet size of 340.3 bytes and a correlation value of 0.892 whencompared to realistic Internet traffic.Table C.2: Complete IMIX (Informative)Packet Size (Bytes)Proportion of TotalBandwidth (Load)4055.0%5.15%57615.0%20.25%150012.0%42.20%40-1500 (range)20.0%32.40%This mixture retains the simplicity of the Simple IMIX but includes an additional set of packets, representing all other packet sizes. This set includes a random mix of packet lengths in a flatdistribution (equal probability of each size), ensuring that some non-zero number of packets of everysize are offered to the EUT.The Complete IMIX has an average packet size of 427.0 bytes and a correlation value of 0.985 whencompared to realistic Internet traffic.Table C.3: Accurate IMIX (Informative)Packet Size (Bytes)Proportion of TotalBandwidth (Load)281.20%0.08%4035.50%3.51%442.00%0.22%482.00%0.24%523.50%0.45%5520.80%1.10%57611.50%16.40%6281.00%1.50%14203.00%10.50%150010.00%37.10%40-80 (range)10.80%1.60%80-576 (range)11.80%9.60%576-1500 (range)6.90%17.70%This mixture has an average packet size of 404.5 bytes and has a correlation value of 0.999 when compared to realistic Internet traffic.Table C.4: Additional IMIX InformationReferenceTitle internet traffic can be found at the URL, Test Methodology Journal, IMIX (Internet Mix) Journal, March 2006 Library: Test Plans, Broadband PPPoX and L2TP TestingAnnex D: Alternative metrics for routers and switches with low power statesExtract from ITU recommendation: L.1310 [ REF _Ref371427499 \r \h 6]This section reports some alternative metrics available for routers and switches. These additional metrics cover the explicit power states supported by the hardware are based on [ REF _Ref370734614 \r \h \* MERGEFORMAT 6].D.1Routers and switches supporting sleep modeThis metric is applicable only to routers and switches that can go on sleep mode.The proposed metric is:TEER = Ti/Pi [Gbps/W](D-1)Where: Pi = c*Pmax+ b*Ptypical+ a*Pidle + d*Psleep [W] (D-2)Tiis the weighted throughput Ti = c*Tmax + b*Ttypical + a*Tidle(D-3)(Tmax, Ttypical,Tidle) = Throughput measured at respective utilization levelsWhere: Pmax is the power at maximum traffic load in real time; here maximum traffic load is defined as maximum non drop rate, equivalent to 100% load (u3 in ATIS-0600015.03.2009 [ REF _Ref370735886 \r \h \* MERGEFORMAT 5]) Ptypical is the power at typical traffic load in real time; here typical traffic load is defined as 30% load or 10% load which is dependent on the different equipment types (u2 in ATIS-0600015.03.2009 [ REF _Ref370735886 \r \h \* MERGEFORMAT 5])Pidle?is the power in idle state in real time; here idle state is defined in 0% load (u1 in ATIS-0600015.03.2009 [ REF _Ref370735886 \r \h \* MERGEFORMAT 5])Psleepis the power in sleep mode in non-real time, applicable only for equipment that offers sleep mode.c is the weighting multiplier for maximum state in real time, b is the weighting multiplier typical traffic load in real time, a is the weighting multiplier for idle traffic load in real time,d is the weighting multiplier for sleep mode in non-real time, a + b + c + d = 1The parameters a, b, c, d values, considering the traffic distribution during the day, are defined in Table D.1 for routers and in Table D.2 for switches equipment.Values for a, b, c, and d shall be substantiated with data; sleepmode can be used in a limited number of networking devices, but only if nothing is attached to the device network connection. For this group of routers/switches, expected traffic is close to idle. Table D.1 ? Weight factor definition for router equipmentClass Representative utilization % of utilization for energy measurements, u1, u2, u3 Weight multipliers a, b, c, d Access router with sleep mode support1-3% 0; 10; 100 a=0.15, b=0.25, c=0.15, d=0.45Table D.2 ? Weight factor definition for switches equipmentClass Representative utilization % of utilization for energy measurements, u1, u2, u3 Weight multipliers a, b, c, d Access switch with sleep mode support1-3% 0; 10; 100 a=0.15, b=0.25, c=0.15, d=0.45D.2Measurement methodologyMeasurement methodology shall be in line with ATIS-0600015.03.2009 [ REF _Ref370735886 \r \h \* MERGEFORMAT 5], and the general requirements as per GISFI TS GICT.100 [ REF _Ref370472616 \r \h \* MERGEFORMAT 2], and the sleep mode.Power measurement for sleep modeWith each of the equipment’s ports operating in sleep mode for 20 minutes, record the average input power over 15 minutes.D.3Routers and switches supporting explicit power statesTo evaluate EENRT, we define three measurement points that may correspond to different power states of EUT: S0 - full performanceS1 - 30% performanceS2 - 10% performanceWe also define sample duty cycle as a fraction of time during which the planned traffic levels are applicable. Level 0 will be used for 55% of duty period, Level 2 for 25% and Level 3 for 20% of duty period.EENRT = (0.55TS0 +0.25TS1 +0.2TS2) / (0.55PS0 +0.25PS1 +0.2PS2) Gbps/W] (D-3)Where:TS0, TS1, TS2 is the throughput in the three measurement points PS0, PS1, PS2 is the power in the three measurement pointsAnnex E: Modular measurement method for routers and switchesBased on GISFI TR on IP Routers GISFI TR GICT.106 [ REF _Ref371075787 \r \h 1]Step 1: Configure the system with all service cards to obtain a full chassis and set the system at the maximum NDR traffic load defined in Clause 6.5.1 within the cards, and test the power used PT.Step 2: Remove one service card and test the power used of this configuration P1.Step 3: Calculate the power used by the service card: PCard1 = (PT - P1) (E-1)Step 4: Repeat steps 1 and 2 with other traffic loadStep 5: According to above steps, test the power used by other service cards, PCard2, PCard3, PCardn .Step 6: Calculate the power used by the common system; this power is determined by subtracting the power used by different service cards present in the system from the power measured in the initial configuration during the step 1 at maximum traffic P1.Pcomm= PT- 1nPcardi(E-2)Pcardiis the power used by servicecardi identified during the Step 3.Step 7: The weighted power of the card is calculated using the following formula:Pwcardi=a*Pu1+b*Pu2+c* Pu3(E-3)Pwcardiis the weighted power of card 1…nPujis the power of the estimated configuration with traffic load determined by Table 1 and 2 under Clause 5a, b, care the weighted factor depending on traffic load and equipment type see Clause 5The estimated TEER is :TEER= i=1nTiPcomm+ i=1nPcardi(E-4)Where:Tiis the throughput of any individual service cardiused to determine thePcardi.Annex F: Sample Reporting FormatExtract from GISFI TS GICT.100 [ REF _Ref371427605 \r \h \* MERGEFORMAT 2]Table F.1: Sample measurement report format. [Report must be inclusive but not limited to the relevant mentioned fields]Equipment under testName of EUTManufacturer of EUTUnique Identification of EUTEquipment CategoryApplicable standards for energy efficiency of the EUTDate of Testing Location of TestingDate of Report PublicationHardwareDescription:Dimensions:LengthBreadthHeightConfiguration mounting:Fan compensation power notes:Modification required:SoftwareFirmware version:Boot loader version:Operating system details:Configuration notes and software tuning parametersConfiguration Notes:Software tuning parameters:Enabled features:Disabled features:Annotated picture of equipment under test<INSERT PICTURE/BLOCK DIAGRAM OF THE SETUP>Description of setupEnvironmental conditionsCriteriaSpecified conditionsTest conditionsTest durationAmbient temperatureRelative humidityAtmospheric PressureFeed voltageSupply power ratioEnergy AnalyzerHardware vendorModel Serial numberCalibration labAccredited byCalibration levelCalibration dateCalibration validity periodSupport Equipment (s)Hardware vendorModel Serial numberCalibration labCalibration datePower feed sizingMinimumMaximumTotal power feedsFeed redundancyCalculationsAny other notesContact Information for this reportNameDesignationContact AddressContact TelephoneEmail IDWebsitePlaceDateSignatureContributors to this documentAt the time of release of this document, the TEC Core Committee on Green Passport Implementation Plan, which was responsible for it development, hadthe following roster:Ram Krishna DDG(FLA)TECAnupamGupt DDG(GP)TECLaxmi Director (FLA)TECMembers of the Core CommitteeOrganization RepresentedName of the representativeNEC / GISFIRitesh Kumar KalleNEC / GISFIAnand R. PrasadCISCO / GISFIArvindMathurI2TB/ GISFIKrishna SirohiVNLEricssonNSNETSISpirentVodafoneAirtelReliance AUSPI ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download