ETSI GS NFV-EVE 003 V1.1.1 (2016-01)

Network Functions Virtualisation (NFV); Ecosystem; Report on NFVI Node Physical Architecture Guidelines for Multi-Vendor Environment

DGS/NFV-EVE003

General Information

• Status: Published
• Publication Date: 07-Jan-2016
• Technical Committee: NFV EVE - Evolution and Ecosystem
• Current Stage: 12 - Completion
• Due Date: 28-Dec-2015
• Completion Date: 08-Jan-2016

Standards Content (Sample)

GROUP SPECIFICATION
Network Functions Virtualisation (NFV);
Ecosystem;
Report on NFVI Node Physical Architecture Guidelines
for Multi-Vendor Environment
Disclaimer
This document has been produced and approved by the Network Functions Virtualisation (NFV) ETSI Industry Specification
Group (ISG) and represents the views of those members who participated in this ISG.
It does not necessarily represent the views of the entire ETSI membership.

2 ETSI GS NFV-EVE 003 V1.1.1 (2016-01)

Reference
DGS/NFV-EVE003
Keywords
architecture, NFV, NFVI
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2015.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI GS NFV-EVE 003 V1.1.1 (2016-01)
Contents
Intellectual Property Rights . 6
Foreword . 6
Modal verbs terminology . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 7
3 Definitions and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 8
4 Principles for development of physical components . 9
4.1 Introduction . 9
4.2 General principles. 10
4.2.1 Observations . 10
4.2.2 High level goals for NFVI Nodes . 11
4.2.3 Other solution values . 11
4.3 Key criteria . 11
4.3.1 Space . 11
4.3.2 Power . 11
4.3.3 Cooling . 12
4.3.4 Physical interconnect . 12
4.3.5 Management . 12
4.3.6 Climatic . 12
4.3.7 Acoustic . 12
4.4 Open Compute Project . 13
5 Overview of node functions . 13
5.1 Introduction . 13
5.2 Compute node . 13
5.3 Storage node . 13
5.4 Network node . 13
5.5 NFVI Node . 14
6 Physical components . 14
6.1 Commercial products . 14
6.2 Racks . 15
6.2.1 Introduction. 15
6.2.2 Relationship of racks to NFVI Nodes . 15
6.2.2.1 Introduction . 15
6.2.2.2 Geographic location . 16
6.2.2.3 1:N NFVI Node to rack mapping . 16
6.2.2.4 N:1 NFVI Node to rack mapping . 17
6.2.2.5 N:M NFVI Node to rack mapping . 17
6.2.3 Industry equipment practices . 18
6.2.3.1 Mechanical dimensions . 18
6.2.3.2 Weight considerations . 18
6.2.3.3 Safety considerations . 18
6.2.3.4 Electromagnetic interference considerations . 19
6.2.4 Installation of compute/network/storage nodes . 19
6.2.5 Rack-level management considerations . 19
6.2.6 Volumetric efficiency considerations . 19
6.2.7 Open Compute example . 20
6.2.8 Recommendations . 21
6.3 Processors . 22
6.3.1 Introduction. 22
6.3.2 Instruction set . 22
ETSI
4 ETSI GS NFV-EVE 003 V1.1.1 (2016-01)
6.3.3 Multi-core support . 22
6.3.4 Operating system & hypervisor (virtualisation) support . 22
6.3.5 Registers, cache & memory architecture . 23
6.3.6 Processor recommendations. 23
6.4 Power . 24
6.4.1 Introduction. 24
6.4.2 Typical elements of power distribution . 24
6.4.2.1 Introduction . 24
6.4.2.2 Facility power . 24
6.4.2.2.1 Contex . 24
6.4.2.2.2 -48 VDC power . 24
6.4.2.2.3 AC power . 25
6.4.2.2.4 High voltage DC power . 25
6.4.2.3 Voltage conversion. 25
6.4.2.4 Backup power . 25
6.4.2.5 In-rack power distribution . 26
6.4.3 Power redundancy models . 26
6.4.3.1 Redundant rack feeds . 26
6.4.3.2 Redundant rack power conversion . 26
6.4.3.3 Redundant rack power distribution . 26
6.4.3.4 Redundant compute/storage/network node power . 26
6.4.4 Power safety considerations . 26
6.4.5 Power efficiency . 27
6.4.5.1 Introduction . 27
6.4.5.2 Power conversion . 27
6.4.5.3 Compute, storage and networking Efficiency . 27
6.4.5.4 Power management . 27
6.4.5.5 Redundancy models . 27
6.4.6 Example from the Open Compute Project Open Rack . 27
6.4.7 Power Recommendations . 27
6.5 Interconnections . 28
6.5.1 Ethernet . 28
6.5.2 Intra domain (between compute, storage and network domains) . 29
6.5.3 Intra NFVI Node . 30
6.5.4 Inter NFVI Node . 32
6.5.5 Other types of interconnections . 33
6.5.6 Recommendations . 33
6.6 Cooling . 33
6.6.1 Introduction. 33
6.6.2 Typical elements of cooling . 33
6.6.2.1 Facility and environmental . 33
6.6.2.2 Rack cooling . 34
6.6.2.3 Chip cooling . 34
6.6.2.4 Liquid cooling . 34
6.6.2.5 Air filters . 34
6.6.3 Cooling reliability . 35
6.6.3.1 Introduction . 35
6.6.3.2 Cooling zones . 35
6.6.3.3 Fan redundancy . 35
6.6.3.4 Fan replacement . 35
6.6.4 Cooling safety considerations . 35
6.6.5 Cooling efficiency . 35
6.6.6 Example from Open Compute Project . 36
6.6.7 Cooling recommendations . 36
6.7 Hardware platform management . 36
6.7.1 Introduction. 36
6.7.2 Typical hardware elements managed via software API . 37
6.7.2.1 Environmental sensors and controls . 37
6.7.2.2 Boot/Power. 37
6.7.2.3 Cooling/Fans . 37
6.7.2.4 Network status . 37
6.7.2.5 Inventory data repository . 37
ETSI
5 ETSI GS NFV-EVE 003 V1.1.1 (2016-01)
6.7.2.6 Firmware upgrade . 37
6.7.2.7 Event logging and diagnostics. 37
6.7.2.8 Alarm management . 37
6.7.3 Hardware platform management features . 38
6.7.3.1 General . 38
6.7.3.2 System management. 38
6.7.3.3 Node management . 38
6.7.3.4 Power and fan management . 38
6.7.3.5 Network management interface . 38
6.7.3.6 Payload management interface . 39
6.7.3.6.1 Introduction . 39
6.7.3.6.2 Compute payload management interface . 39
6.7.3.6.3 Storage payload management interface . 39
6.7.4 Recommendations . 39
7 NFVI Node examples . 40
7.1 Introduction . 40
7.2 Virtual mobile network . 40
7.3 Access node . 41
7.4 Transport node . 42
7.5 Customer Premises Equipment . 43
Annex A (informative): Bibliography . 45
Annex B (informative): Authors & Contributors . 46
History . 47

ETSI
6 ETSI GS NFV-EVE 003 V1.1.1 (2016-01)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Group Specification (GS) has been produced by ETSI Industry Specification Group (ISG) Network Functions
Virtualisation (NFV).
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
7 ETSI GS NFV-EVE 003 V1.1.1 (2016-01)
1 Scope
The present document provides guidelines for NFVI Node physical architecture. It is limited to the hardware resources -
compute, storage, and network - needed to construct and support the functions of an NFVI Node. This includes physical
components needed to house and interconnect nodes.
The present document also provides some examples on "building" specific NVFI Node configurations and
addresses related issues such as reliability and energy efficiency.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
Not applicable.
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI GS NFV-INF 001 (V1.1.1): "Network Functions Virtualisation (NFV); Infrastructure
Overview".
[i.2] IEEE 802.3ae™ Standard for Information technology: "Telecommunications and information
exchange between systems - Local and metropolitan area networks, - Specific requirements Part 3:
Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical
Layer Specifications, Amendment 1: Media Access Control (MAC) Parameters, Physical Layers,
and Management Parameters for 10 Gb/s Operation".
[i.3] Introducing data centre fabric, the next-generation Facebook™ data center network.
NOTE: Available at https://code.facebook.com/posts/360346274145943/introducing-data-center-fabric-the-next-
generation-facebook-data-center-network/.
[i.4] ETSI EN 300 019-1-3: "Environmental Engineering (EE); Environmental conditions and
environmental tests for telecommunications equipment; Part 1-3: Classification of environmental
conditions; Stationary use at weatherprotected locations".
[i.5] ETSI EN 300 753: "Environmental Engineering (EE); Acoustic noise emitted by
telecommunications equipment".
[i.6] NEBS GR-63: "NEBS Requirements: Physical Protection".
ETSI
8 ETSI GS NFV-EVE 003 V1.1.1 (2016-01)
[i.7] ASHRAE: "Thermal Guidelines for Data Processing Environment", 3rd edition, 2012.
[i.8] ETSI GS NFV 002 (V1.2.1): "Network Functions Virtualisation (NFV); Architectural
Framework".
[i.9] ETSI GS NFV-INF 003 (V1.1.1): "Network Functions Virtualisation (NFV); Infrastructure;
Compute Domain".
[i.10] ETSI GS NFV-MAN 001 (V1.1.1): "Network Functions Virtualisation (NFV); Management and
Orchestration".
[i.11] EIA/ECA-310, Revision E, December 1, 2015: "Electronic Components Industry Association
(ECIA)".
[i.12] ETSI ETS 300 119-4: "Equipment Engineering (EE); European telecommunication standard for
equipment practice; Part 4: Engineering requirements for subracks in miscellaneous racks and
cabinets".
[i.13] ETSI GS NFV-REL 003 (V0.3.0) (08-2015): "Network Functions Virtualisation (NFV);
Reliability; Report on Models and Features for E2E Reliability".
NOTE: Available at https://docbox.etsi.org/ISG/NFV/Open/Drafts/REL003_E2E_reliability_models/NFV-
REL003v030.zip.
[i.14] Final Report: "Virtualised Mobile Network with Integrated DPI, ETSI ISG NFV,
st
October 31 2014".
[i.15] "Refactoring Telco Functions, the Opportunity for OCP in telco SDN and NFV Architecture",
Tom Anschutz, March 9, 2015.
[i.16] IETF RFC 7075: "Diameter Base Protocol".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ETSI GS NFV-INF 003 [i.9], ETSI
GS NFV-INF 001 [i.1] apply.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AC Alternating Current
AES Advanced Encryption Standard
AES-NI Advanced Encryption Standard New Instructions
API Application Program Interface
ASHRAE American Society of Heating, Refrigerating, and Air-conditioning Engineers
CPE Customer Premise Equipment
CPU Central Processing Unit
CRC Cyclic Redundancy Check
DC Direct Current
DC-DC Direct Current-Direct Current
DMA Direct Memory Access
DSC Diameter Signaling Controller
E2E End to End
ECC Error Correcting Code
EMI Electromagnetic Interference
EPC Evolved Packet Core
ER Extended Reach
FRU Field Replaceable Unit
FW FirmWare
ETSI
9 ETSI GS NFV-EVE 003 V1.1.1 (2016-01)
GPON Gigabit Passive Optical Network
GR Generic Requirements
HDD Hard Disk Drive
ISG Industry Specification Group
IT Information Technology
JBOD Just a Bunch Of Disks
KVM Kernel-based Virtualisation Machine
LAN Local Area Network
LR Long Reach
LW Long Wavelength
MANO Management and Orchestration
MME Mobility Management Entity
NAS Network Attached Storage
NEBS Network Equipment Building System
NFV Network Functions Virtualisation
NFVI NFV Infrastructure
NFVI-PoP NFV Infrastructure Point of Presence
NUMA Non-Uniform Memory Access
OCP Open Compute Project
OLT Optical Line Terminator
OS Operating System
PCI Peripheral Component Interconnect
PGW Packet Data Network Gateway
SDDC Single Device Data Correction
SGW Serving Gateway
SONET Synchronous Optical Networking
SR Special Report
SR-IOV Single Root Input/Output Virtualisation
SW Short Wavelength
ToR Top of Rack
UMA Uniform Memory Access
UPS Uninterruptible Power Supply
VDC Volts of Direct Current
VLAN Virtual Local Area Network
VM Virtual Machine
VNF Virtualised Network Function
WAN Wide Area Network
4 Principles for development of physical components
4.1 Introduction
Virtualised Network Functions (VNFs) have to reside and operate on physical hardware. The telecommunications
industry is moving away from specialized, sophisticated, and possibly proprietary hardware; instead the goal is to move
towards commercially available off-the-shelf products in terms of processors, disks, racks, and other physical elements.
The goal of the present document is to provide guidance for an ecosystem of generic and commonly available sets of
physical products and components for the industry.
The guidelines will be beneficial to telecommunication equipment providers and other vendors as well as service
providers in the development and acquisition of desired components for building NFVI Nodes.
The focus of the present document is limited to the description of the physical hardware - compute, storage, and
network domains shown in figure 1.
The present document draws upon available hardware principles (e.g. Open Compute Project) as necessary. Other
topics covered include the following:
• Node functions (compute, storage, network);
• Physical components (racks, frames, processors, etc.);
ETSI
10 ETSI GS NFV-EVE 003 V1.1.1 (2016-01)
• Power and cooling issues - guidelines on potential relationships between power delivery, heat build-up and
heat dissipation will be provided as appropriate;
• Interconnection methods.
Figure 1: NFV architectural framework and identification of NFVI domains
Clause 4.2 provides general principles and goals for the NFVI Node physical architecture. Clause 4.3 provides key
criteria for NFVI Nodes. Additional clauses outline common architectural practices with evaluation of their
applicability to the NFVI Node physical architecture.
4.2 General principles
4.2.1 Observations
These general observations are included as guidance when considering architectural implementations for NFVI Nodes.
Unlike software elements of NFV, NFVI has unique characteristics due to its physical nature. General observations
include:
• The end goals for the platform dictate the architectural choices. Without alignment around goals, it is difficult
to determine a cohesive architecture;
• Infrastructure, by nature, is physical. Infrastructure has size and weight. It consumes power and generates heat
and noise. These are all interrelated and need to be balanced to meet equipment needs. Ambient temperature,
power delivery and acoustic limits are derived from building and equipment practices;
• Infrastructure nodes live within the equipment practices in which they are deployed. They interface with other
mechanical, electrical and software elements. These interfaces and behaviours need to be taken into account.
ETSI
11 ETSI GS NFV-EVE 003 V1.1.1 (2016-01)
4.2.2 High level goals for NFVI Nodes
The following high level goals are desired for whatever NFVI Nodes are developed. These goals are consistent with a
vision to enable a robust software ecosystem on commercially available hardware infrastructure.
High level goals for NFVI Nodes are:
• Multi-vendor, multi-customer, commercially available off-the-shelf ecosystem. Specific products do not need
to be developed for each customer. Suppliers are free to innovate within the ecosystem;
• Economical scalability, addressing a wide range of application sizes and capacities;
• Appropriate features: solutions take into account concerns regarding space, power, cooling, and maintenance;
• Able to address multiple layers of the network: including transport, switching/routing and applications.
4.2.3 Other solution values
The following additional solution values are desired:
• Manageable. Application as well as field replaceable units may be managed. Management method integrates
with NFV management interfaces;
• Resilient. Failure of components within the solution is detectable in order to support failover to another
resource. Fail-over is handled in such a way to reduce the possibility of outages. Resiliency objectives
(e.g. 5 nines) may be specified by service providers;
• Efficient (power, space, etc.);
• Interoperable. Equipment from one vendor interoperates with equipment from other vendors;
• Backward compatible. New equipment works with older equipment;
• Future proofed. Current-generation equipment works with future-generation equipment.
4.3 Key criteria
4.3.1 Space
Space criteria relate to the physical height, width, depth and volume that the equipment occupies. Space-related criteria
are important to comprehend because NVFI Nodes will be deployed within facilities where space-related constraints
exist. The following are key space-related criteria:
• Rack footprint and height compatible with data center and central office;
• Efficient use of the available volume;
• Flexible module widths, heights, etc.;
• Approximately 1 rack unit module height, or multiples thereof (allows use of commercially available
off-the-shelf components).
4.3.2 Power
Power criteria are related to the type and amount of power that is supplied to the NFVI Nodes as well as limitations on
how much power the equipment draws. Key criteria are:
• High power density within the constraints of climate and cooling scheme;
• Flexibility to interface to various direct current (including high voltage direct current) and alternating current
configurations and topologies;
• Capability to support installations in both data centers and central offices, depending on configuration;
ETSI
12 ETSI GS NFV-EVE 003 V1.1.1 (2016-01)
• Rack level uninterruptable power supply option with appropriate backup time;
• Maximum rack power consistent with facilities infrastructure practices;
• Maximum node power depends on node density. Full rack of nodes consume no more than the maximum rack
power;
• Support power control at NFVI Node as well as individual compute/storage/network node levels;
• Avoidance of single Points of Failures at power system;
• Support power redundancy including N+M (M 4.3.3 Cooling
Cooling criteria are related to the capability to remove heat from the NFVI Node. Since dissipation of power by the
NFVI Node generates heat, power consumption and cooling capabilities need to be matched. Key criteria are:
• Cooling matches the power needs in the central office and data center environments;
• Air filter option is desirable;
• Roadmap to support for liquid cooling;
• Front-to-back airflow is desirable;
• Placing temperature sensitive parts (e.g. optical module, HDD) at air intake position is desirable;
• Maintenance at cold aisle is desirable.
4.3.4 Physical interconnect
System interconnect criteria provide guidance on how elements of the NFV Node infrastructure are connected together.
Key criteria are:
• Common interconnection methods (e.g. Ethernet) for all nodes;
• Capacity scalable to order of Terabits/s per rack unit;
• Modular capacity can grow as installation needs demand;
• Support high bandwidth and low latency switching to meet the resource pooling requirements;
• Support isolation of north-south data flow and east-west data flow;
• Support isolation of service data flow and management data flow.
4.3.5 Management
Infrastructure management applies to how each module or physical subcomponent (power supplies, fans, nodes) is
managed. NFVI management fits within the overall framework of NFV management.
4.3.6 Climatic
Since NFVI equipment may be deployed in both central office and datacenter environment, compliance with the
climatic standards of central office and datacenter environment (e.g. ETSI EN 300-019-1-3 [i.4], NEBS GR-63 [i.6],
ASHRAE Thermal Guidelines for Data Processing Environment [i.7], etc.) is desirable.
4.3.7 Acoustic
For the hearing protection of employees working in high noise emission environment, compliance with noise emission
standards (e.g. ETSI EN 300 753 [i.5], NEBS GR-63 [i.6]) is desired. For central office and datacenter deployment, the
NFVI equipment adherent to acoustic emission limits is strongly desired and likely will be mandated by operators.
ETSI
13 ETSI GS NFV-EVE 003 V1.1.1 (2016-01)
Capability of operating at the NEBS acoustic noise limits is recommended. Capability of operating at the ETSI acoustic
noise limit might be needed based on operator demand.
4.4 Open Compute Project
The Open Compute Project is an online community whose mission is to create and deliver efficiently functioning
servers, storage capabilities and data centre designs. Open Compute is one example of an open ecosystem of
commercially available hardware that is being deployed today. While Open Compute was not architected specifically
for application to NFVI Nodes, understanding of its key elements is instructive. Throughout the rest of the present
document, Open Compute may be used as an architecture for illustrative purposes.
5 Overview of node functions
5.1 Introduction
As discussed in the ETSI NFV architectural framework [i.8], the physical hardware resources include computing,
storage and network resources that provide processing, storage and connectivity to VNFs through the virtualisation
layer (e.g. hypervisor).
5.2 Compute node
A compute node is an element used in the compute domain of the NFVI (see figure 1 in clause 4.1). The NFV
architectural framework [i.8] states that the hardware resources for the compute node are assumed to be comprised of
commercially available products as opposed to purpose-built hardware. The computing resources are commonly pooled.
5.3 Storage node
A storage node is an element used in the compute domain of the NFVI (see figure 1 in clause 4.1). The NFV
architectural framework [i.8] states that the storage resources can be differentiated between shared Network Attached
Storage (NAS) and storage that resides on the server itself. The storage resources are also commonly pooled.
5.4 Network node
A network node is an element used in the infrastructure network domain of the NFVI (see figure 1 in clause 4.1). The
NFV architectural framework [i.8] states that the network resources are comprised of switching functions, e.g. routers,
and wired or wireless links. Also, network resources can span different domains. However, the NFV architectural
framework [i.8] differentiates only the following two types of networks:
• NFVI-PoP network: the network that interconnects the computing and storage resources contained in an
NFVI-PoP. It also includes specific switching and routing devices to enable external connectivity;
• Transport network: the network that:
- interconnects NFVI-PoPs;
- connects NFVI-PoPs to other networks owned by the same or different network operator; and
- connects NFVI-PoPs to other network appliances or terminals not contained within the NFVI-PoPs.
In an NFVI-PoP, a network node can furthermore be categorized as follows:
• A network node which hosts compute and storage nodes, and connects to other network nodes (e.g. Top of
Rack (ToR) switch, access switch, leaf switch, etc.);
• A network node which interconnects other network nodes (e.g. aggregation switch, spine switch, etc.);
• A network node which connects to transport network (e.g. gateway router).
ETSI
14 ETSI GS NFV-EVE 003 V1.1.1 (2016-01)
5.5 NFVI Node
Figure 2, which is equivalent to figure 22 in ETSI GS NFV-INF 003 [i.9], gives a
...