没有合适的资源?快使用搜索试试~ 我知道了~
virtual_network_technology
需积分: 31 9 下载量 170 浏览量
2014-06-02
16:35:44
上传
评论
收藏 401KB PDF 举报
温馨提示
试读
12页
from HP, introduce vepa and vn-tag(port extension) in network virtulization.
资源推荐
资源详情
资源评论
Virtual networking technologies at the server-network edge
Technology brief
Introduction ......................................................................................................................................... 2
Virtual Ethernet Bridges ........................................................................................................................ 2
Software-based VEBs – Virtual Switches .............................................................................................. 2
Hardware VEBs — SR-IOV enabled NICs............................................................................................ 4
Edge Virtual Bridging ........................................................................................................................... 5
VEB mode ....................................................................................................................................... 7
S-channel technology ........................................................................................................................ 7
Port extension technology ..................................................................................................................... 8
Disadvantages with port extension approach .................................................................................... 10
Status of IEEE standards and industry adoption ..................................................................................... 11
Conclusion ........................................................................................................................................ 11
For more information .......................................................................................................................... 12
2
Introduction
Hypervisors add a new layer of software and virtual networking that dramatically affects data center
servers and their associated network connectivity.
In the past, network administrators managed the external network infrastructure and occasionally
managed the server NICs. Server administrators managed the server, the applications running on the
server, and usually the server NICs. Hypervisors push the boundary of network infrastructure into the
physical server by their use of virtual switches (commonly referred to as soft switches or vSwitches).
This blurs the line between the domains of the server administrator and of the network administrator.
Server administrators typically configure the vSwitches but can’t see or change the external network
configurations. Network administrators can’t configure or debug the vSwitches. Challenges arising
from hypervisors include performance loss and management complexity of integrating software-based
vSwitches into your existing network management.
Industry leaders are proposing two fundamentally different approaches to deal with server-network
edge challenges and to provide more management insight into networking traffic in a virtual machine:
• Edge Virtual Bridging (EVB) with Virtual Ethernet Port Aggregator (VEPA) technology
• Port extension technology
The EVB approach uses industry-standard technologies at the server-network edge. It promotes
network management and network service provisioning as close to the edge as possible. The industry-
standard approach ensures that new technologies will work within your existing environments and
organizational roles. The goal of HP is to enable a simple migration to advanced technologies at the
server-network edge without requiring an entire overhaul strategy for your data center.
The port extension approach reflects all network traffic onto a central controlling bridge. This gives
network administrators full access and control but at the cost of bandwidth and latency.
The IEEE standards supporting networking in virtual machine (VM) environments are in the final draft
stages. It is not clear the extent to which hardware and hypervisor vendors will support these
standards. This uncertainty means that whether you are a server administrator or network
administrator, you may need to consider numerous factors when choosing new server and network
technologies.
Virtual Ethernet Bridges
A Virtual Ethernet Bridge (VEB) is a virtual Ethernet switch that you implement in a virtualized server
environment. It is anything that mimics a traditional external layer 2 (L2) switch or bridge for
connecting VMs. VEBs can communicate between VMs on a single physical server, or they can
connect VMs to the external network.
The most common implementations of VEBs are software-based vSwitches built into hypervisors. But
vendors can use the PCI Single Root I/O Virtualization (SR-IOV) standard to build hardware-based
VEBs in NICs.
Software-based VEBs – Virtual Switches
In a virtualized server, the hypervisor abstracts and shares physical NICs among multiple virtual
machines, creating virtual NICs for each virtual machine. For the vSwitch, the physical NIC acts as
the uplink to the external network. The hypervisor implements one or more software-based virtual
switches that connect the virtual NICs to the physical NICs.
3
Data traffic received by a physical NIC passes to a vSwitch. The vSwitch uses its hypervisor-based
configuration information to forward traffic to the correct VMs.
When a VM transmits traffic from its virtual NIC, a vSwitch forwards the traffic in one of two ways
(see Figure 1):
• If the destination is external to the physical server or to a different vSwitch, the vSwitch forwards
traffic to the physical NIC.
• If the destination is internal to the physical server on the same vSwitch, the vSwitch forwards the
traffic directly back to another VM.
Figure 1: In a VEB implemented as a vSwitch, traffic can be “switched” locally inside the Hypervisor vSwitch
(gray line) or sent directly to the external network via the physical NIC (blue line).
Using a software-based vSwitch has a number of advantages:
• Good performance between VMs. A vSwitch typically uses only L2 switching and can forward
internal VM-to-VM traffic directly. Bandwidth is restricted only by available CPU cycles, memory bus
bandwidth, or limits configured by the user in the hypervisor.
• Deployment without an external switch. Administrators can provide an internal network with no
external connectivity. For example, you can run a local network between a web server and a
firewall application running on separate VMs within the same physical server.
• Support for a wide variety of external network environments. vSwitches are compliant with
standards and can work with any external network infrastructure.
vSwitches also have several disadvantages:
• Consume valuable CPU and memory bandwidth. The higher the traffic load, the greater the number
of CPU and memory cycles required to move traffic through the vSwitch, reducing the ability to
support larger numbers of VMs in a physical server.
• Lack network-based visibility. vSwitches have a limited feature set. They don’t provide local traffic
visibility or have capabilities for enterprise data monitoring, security, or network management. This
can affect network policies in the data center for accounting, security, and reliability.
• Lack network policy enforcement. Modern external switches have many advanced features such as
port security, quality of service (QoS), and access control lists (ACL). But vSwitches often do not
VM
VM
VM
VM
L2 net(s)
Physical NIC
Virtual NIC
External Network
Physical Server
VM Edge
Switch Edge
Server
Edge
Hypervisor
vSwitch
剩余11页未读,继续阅读
资源评论
zhengleiguo
- 粉丝: 37
- 资源: 2
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
最新资源
- Fortran语言语法快速入门.pdf
- 明日方舟 年 鼠标指针.rar
- 全国银行经济监管可视化系统
- e商小二-供应链管理物流交仓创业商业计划书.rar
- Edge浏览器下载文件提示 “无法安全下载” 的解决方法
- 基于springboot+layui的医院日常耗材管理系统.zip
- Emkex亿迈克思新型互联网磁材供应链商业计划书.rar
- 计算机毕业设计-ASP.NET某店POS积分管理系统-销售情况,会员卡再发行数据生成(源代码+)-毕设源码实例.zip
- 计算机毕业设计-asp.net某店POS积分管理系统-清除履历表、日志表、月购买额(源代码+)-毕设源码实例.zip
- 计算机毕业设计-ASP.NET某店POS积分管理系统-积分实绩更新及销售状况统计(源代码+)-毕设源码实例.zip
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功