Which access layer device was used for the Vancouver 2010?
The Ethernet Routing Switch 5500 Series
2010 Winter Olympics
The 2010 Winter Olympics, officially known as the XXI Olympic Winter Games (French: Les "XXIes Jeux olympiques d'hiver") and commonly known as Vancouver 2010, informally the 21st Winter Olympics, were a major international multi-sport event held from February 12 to 28, 2010, in Vancouver, Canada, with some events held in the surrounding suburbs of Richmond, West Vancouver and the University Endowment Lands, and in the nearby resort town of Whistler.
 Approximately 2,600 athletes from 82 nations participated in 86 events in fifteen disciplines.
 Both the Olympic and Paralympic Games were organized by the Vancouver Organizing Committee (VANOC), headed by John Furlong.
 The 2010 Winter Olympics were the third Olympics hosted by Canada and the first by the province of British Columbia.
 Previously, Canada hosted the 1976 Summer Olympics in Montreal, Quebec, and the 1988 Winter Olympics in Calgary, Alberta.
 Vancouver is the largest city to host the Winter Olympics, a title soon to be turned over to Beijing in 2022.
Avaya ERS 5500 Series
The Ethernet Routing Switch 5500 Series or (ERS 5500) is a series of stackable, Layer 3 switches used in computer networking.
 The ERS 5000 was originally designed by Nortel and is now manufactured by Avaya.
 Up to 8 ERS 5000 Series Switches may be stacked in a 640 Gbit/s fast stacking configuration.
 This Switch was used as the access layer device for the 2010 Winter Olympics games.
 The 817 Access Switches supported 8782 Voice-over-IP telephones.
Data access layer
A data access layer (DAL) in computer software, is a layer of a computer program which provides simplified access to data stored in persistent storage of some kind, such as an entity-relational database.
 This acronym is prevalently used in Microsoft environments. ConSentry Networks
ConSentry Networks provides intelligent switching, providing user and application control for enterprises.
 ConSentry access layer LAN switches understand the username, device, role, application at Layer 7, and destination for each flow and apply policy dynamically.
 The company's patented multi-core CPU hardware enables this intelligent switching at up to 10 Gbit/s throughput. Separation of concerns
In computer science, separation of concerns (SoC) is a design principle for separating a computer program into distinct sections, such that each section addresses a separate concern.
 A concern is a set of information that affects the code of a computer program.
 A concern can be as general as the details of the hardware the code is being optimized for, or as specific as the name of a class to instantiate.
 A program that embodies SoC well is called a modular program.
 Modularity, and hence separation of concerns, is achieved by encapsulating information inside a section of code that has a well-defined interface.
 Encapsulation is a means of information hiding.
 Layered designs in information systems are another embodiment of separation of concerns (e.g., presentation layer, business logic layer, data access layer, persistence layer). Database testing
Database testing usually consists of a layered process, including the user interface (UI) layer, the business layer, the data access layer and the database itself.
 The UI layer deals with the interface design of the database, while the business layer includes databases supporting business strategies. Core-and-pod
Core-and-pod design is a network design that uses individual pods that hang off the core layer as atomic units.
 Within the pod, there may be only a single access layer or a “leaf and spine” network in the pod.
 The routed core layer serves as a fast and simple way to connect many generations of pods to each other.
 When the “leaf and spine” network is used within the pod, the core layer can be referred to as the “spine of spines,” since it is the thing that connects the “spines” of the pods.
 This design then resembles some kind of large and wide tree, with many “branches,” or pods, off the main “trunk,” or core. Front and back ends
In software engineering, the terms front end and back end refers to the separation of concerns between the presentation layer ("front end"), and the data access layer ("back end") of a piece of software, or the physical infrastructure or hardware.
 In the client–server model, the client is usually considered the front end and the server is usually considered the back end, even when some presentation work is actually done on the server. Virtual access layer
The virtual access layer (VAL) refers to the virtualization of the access layer that connects servers to the network in the data center.
 Server virtualization is now aggressively deployed in data centers for consolidation of applications hosted on x86 servers. However, the underlying limitations in current networks prevent organizations from meeting the performance, availability, security, and mobility requirements of server virtualization.
 VAL is a product strategy that delivers features to address the unintended consequences of server virtualization.
 It focuses on issues in the server and virtual server I/O, addressing the operational challenges for server, application, and network administrators. Service layer
In intelligent networks (IN) and cellular networks, service layer is a conceptual layer within a network service provider architecture.
 It aims at providing middleware that serves third-party value-added services and applications at a higher application layer.
 The service layer provides "capability servers" owned by a telecommunication network service provider, accessed through open and secure Application Programming Interfaces (APIs) by application layer servers owned by third-party content providers.
 The service layer also provides an interface to core networks at a lower resource layer.
 The lower layers may also be named control layer and transport layer (the transport layer is also referred to as the access layer in some architectures).