F5_GTM广域网流量管理与优化方案.ppt_第1页
F5_GTM广域网流量管理与优化方案.ppt_第2页
F5_GTM广域网流量管理与优化方案.ppt_第3页
F5_GTM广域网流量管理与优化方案.ppt_第4页
F5_GTM广域网流量管理与优化方案.ppt_第5页
已阅读5页,还剩35页未读 继续免费阅读

下载本文档

版权说明:本文档由用户提供并上传,收益归属内容提供方,若内容存在侵权,请进行举报或认领

文档简介

1、BIG-IP Global Traffic Manager广域网流量管理与优化方案,应用全球部署以后的挑战,异地容灾、故障切换 客户感受:易于使用、最佳访问效果 应用的协同 多数据中心资源的充分利用 扩展性 可管理性,容灾方案:宕机的代价是沉重的,“47% of the businesses cited that disaster recovery was a prime target for IT Spending” Network Computing Survivors Guide to 2006 survey,33% of businesses did not have Disaster

2、 Recovery plans in place 16% of businesses lost between $100-$500K/day 26% of businesses dont know how much they lost,Source: AT&T and IAEM report,传统的应用容灾方案的切换机制,手动修改客户端访问目的地址 手动修改DNS解析记录方式 应用层重定向,都是需要人工介入!,指望人工进行容灾切换是靠不住的,$,Error Prone,Slow to Implement,Costly,Labor Intensive,网络管理员,“Microsofts webs

3、ites were offline for up to 23 hours - the most dramatic snafu to date on the Internet - because of DNS equipment misconfiguration affecting more than 72 million users.”,“We screwed up. This is the worst day of my professional life “ Network Administrator at Microsoft,错误修改DNS记录的后果是极其严重的,客户感受,易于使用 最快

4、响应速度,UNIX,WINS,Internal DNS Servers,跨ISP访问:南北电信互访问题,多应用在多数据中心中的协同问题,Clinical records down in Dallas data center!,Clinical Record Services,Employee Information Services,Personal Information Services,Service Oriented Architecture,特性:应用智能、可管理性与高性能 SOA Application Management ZoneRunner - Eliminate DNS E

5、rrors,BIG-IP Global Traffic Manager(GTM),Advanced application and component monitoring iRules - Flexibility to define distribution policies IPv6 AAAA record support Leading DNS performance (40K Res/s ),TMOS,极大提升全球交付应用的 可用性与可靠性,主要功能与优势,支持应用在多个数据中心间进行透明交付 确保全球业务的连续性和应用的可用性 灵活的负载均衡算法,能够根据任何一项业务政策(包括地理信

6、息、负载情况、网络就近性等),并通过为直接用户交付全球流量控制,来增强灵活性。 引导用户进入全球最佳站点,能够显著改进性能并提高客户的体验。 集中管理与监控,实现从单一地点提供全面的应用和数据中心状态信息,降低管理开销 通过充分利用备份数据中心,以提高全球网络的效率、可扩展性以及投资回报。 能够实现复杂任务的自动化流程,从而降低维护和管理开销。,广州数据中心,上海数据中心,User 查询,Local DNS,F5 BIG-IP GTM-广域网流量管理与优化方案,BIG-IP,Server farm,Webmaster,北京数据中心,Router,BIG-IP,GTM,GTM 基本工作机制,GT

7、M is a Wide Area load balancer using DNS as the Traffic Management mechanism. BIND is version 9.3.1 BIND zone file UI is now ZoneRunner WideIP records are written to the appropriate zone files GTM gets BIG-IP style monitors and pools. Big3ds are used to communicate availability between GTM and BIG-I

8、P systems. Big3ds communicate via iQuery over SSL, and utilize gzip to compress messaging Big3dshim daemon facilitates communication between 9.x (big3d) and 4.x 3-DNS.,GTM决策过程,When a DNS request is received by the GTM listener, tmm and gtmd go through the following decision making process before any

9、 IP address is returned: TMM checks to see if there is a WideIP that matches the request If there is match gtmd handles the request. If there is no match the request is passed down to BIND. If a WideIP matches the request, gtmd checks its persistence table for a persistence record. If a match exists

10、 then gtmd will give out the record in the persistence table. If not then GTM determines what pool to send the traffic to based upon the WideIP LB method, and the availability of each pool. GTM returns A records only (AAAA and A6 records included) Once the request reaches the pool level, the pool mu

11、st make a load-balancing decision based upon its LB configuration and the availability of the pool members.,GTM LB Mechanism,GTMs 采用分层的负载均衡机制 A WideIP load balances between its pools. A pool load balances between pool members. In the context of GTM a pool member is a Virtual Server. A virtual server

12、 is a sub component of a Server Object. Thus you must configure Topology accordingly: 1st pass: pick a pool 2nd pass: within a pool to select a pool member,广域网访问流量优化,欧洲用户,美洲用户,GTM,德国 Data Center,美国Data Center,= 集成的性能结构,商业标准,控制全球用户访问在多个数据中心之间的流量分配,地址位置就近访问Topology,亚洲用户,新加坡 Data Center,Topology 举例,来自北

13、美(North America)的访问请求导向到北美的两个数据中心( NA ) 来自北美( Europe )的访问请求导向到北美的两个数据中心( London ) 来自其它地方的访问请求导向到北美的两个数据中心( Tokyo ),Topology举例(cont.),From topology.inc topology / 6 Items / server ldns score dc.London continent.Europe 250 pool.nor_am_web continent.North America 250 pool.nor_am_web /0 25 dc.Tok

14、yo continent.Asia 250 dc.Tokyo continent.Australia 250 pool.nor_am_web continent.South America 250 ,Topology example (cont.),From the GUI,网络就近性动态探测,GTM支持的负载均衡算法,循环 全球可用性 LDNS持续性 应用可用性 地理分布 虚拟服务器容量 最少连接 Pkt/sec(数据包/每秒) KB/sec(千字节/每秒) 往返时间 中继段(hop) 数据包完整率 用户定义服务质量(QoS) 动态比率 LDNS循环 比率 随机,组合的负载均衡算法,The

15、Below pool contains a Virtual Server on a BIG-IP, and a Virtual Server from a Generic Host: pool name bigip_and_host ttl 30 preferred ga alternate ratio member 00:80 ratio 2 member 05:80 Pool Name: bigip_and_host ttl:30 seconds Preferred LB:Global Availability Alernate LB:rat

16、io Fallback LB:Return to DNS (default) Fallback IP:none,GTM WideIP Persistence,There are two types of persistence: Static Persist: A Static LB mode. WideIP Persistence: Applied on each WideIP object as a drop-down configuration option. WideIP persistence works in the following way: first time throug

17、h a pool member is picked (LB) and put into the persistence table (and syncd to all other listening GTMs) second time through if the persistent pool member is still available (green) then that pool member is returned and the timestamp updated on the persistence entry (and we sync that too) if the po

18、ol member is not available (!green) then the persistence entry is tossed and a new one created once LB is complete. If there are no requests for a persistence entry it is removed from the table once that entry has expired. Persistence records are synchronized between GTM synchronization peers Persis

19、tence records can be viewed in the UI: Navigate: Statistics-Global Traffic-Persistence Records Static Persist LB method is discussed in a previous slide.,自动容灾切换,Router,L-DNS,BIG-IP GTM,BIG-IP LTM,Corporate Servers,Site 1 (Primary),Client,Router,BIG-IP LTM,Corporate Servers,Site 2 (Back up),BIG-IP GT

20、M,GTM服务器可用性检查(Monitors),GTM inherits its monitors from LTM. An administrator can create the same monitors that are available in LTM to monitor GTM objects. Monitors can be applied on: Servers Virtual Servers Pools (and pool members),服务器可用性检查,Application,Device,FTP,HTTP,DB.D,HTTPS ,Siebel App,Oracle

21、DB,内容 / 文件检查,Data Center,Intranet App: Siebel in 纽约 HTTP Server DB Server Siebel App Oracle DB Siebel content verification,可用性,解决方案: web服务穿过特定区域、设备,使应用得到一个统一服务检测的批量可用性 好处:可探测到任意标准的web服务套件的失败,多应用协同Distributed Applications,distributed application是一个要使用到多个域名(wideip)的应用,这些域名分布在不同的服务器上,由这组服务器协同工作构成一个完整的应

22、用. Distributed Applications 将多个Wideip当作一个对象来进行管理,可以同时Enable或Disable.,Distributed Application Management,Manage multiple services as part of a collective application,Benefits Lower complexity, ease management Reduced management overhead Cost savings from reduced staff Eliminate cost of downtime,BIG-I

23、P Global Traffic Manager,Solution -,Data Center A,Data Center B,NewCar App,One step failover,Manage Service Dependencies,Challenge Hundreds of applications Manual failover is slow, error prone Multi-step failover to shut down each application service No instantaneous failover,Distributed Application

24、s,Example 1: Data Center Dependency 当构成Distributed Application的Wideip中有任何一个,其对应的virtual server都不同用的话,对这个Distributed Application来说,这个virtual server所属的数据中心就是不可用的。 但其它不属于这个Distributed Application的访问请求,仍然可以被分发到这个数据中心的。 Example 2: Server Dependency 当构成Distributed Application的Wideip中有任何一个,其对应的virtual serv

25、er都不同用的话,对这个Distributed Application来说,这个virtual server所属的服务器就是不可用的。 但其它不属于这个Distributed Application的访问请求,仍然可以被分发到这个服务器上来。,ZoneRunner减少DNS配置错误,Easy DNS management Auto population of protocols Validation/error checking Rollback to the last transaction Importation of zones Automatic reverse lookups,Zon

26、eRunner Only integrated DNS Management Utility,成功案例-TOM.COM CDN,Site沈阳,Site西安,Site成都,Site长沙,Site广州,Site杭州,Site北京,Site 教育网,Site 中国移动,成功案例 - ChinaCache,ChinaCache 中国最大的CDN服务提供商 Solution requirement: Node deployment: 30 - 50 in China Capacity of each node: 40 - 1000MB Implementation: Deploy BIGIP , 3DN

27、S, F5 total CDN solution BIG/IP LB for Cache 3DNS for WAN LB See-IT for management,21cn GSLB解决方案,SEE-IT,WEB/Streaming Server,3DNS,3DNS,Big IP 2400,Core Switch,21cn广州机房,GB,FE,Cache Server,WEB/Streaming Server,Big IP 5000,Big IP 5000,21cn上海节点,Core Switch,Internet,WEB/Streaming Server,Big IP 2400,Core

28、Switch,21cn河北节点,Summary: BIG-IP GTM,BIG-IP Global Traffic Manager,Application Health Features Composite monitors Application-specific monitors Distributed application monitoring,Management Features New and improved user interface ZoneRunner - New zone file management tool New and improved IP classifier Support for IPv6 networks Distributed applicati

温馨提示

  • 1. 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。图纸软件为CAD,CAXA,PROE,UG,SolidWorks等.压缩文件请下载最新的WinRAR软件解压。
  • 2. 本站的文档不包含任何第三方提供的附件图纸等,如果需要附件,请联系上传者。文件的所有权益归上传用户所有。
  • 3. 本站RAR压缩包中若带图纸,网页内容里面会有图纸预览,若没有图纸预览就没有图纸。
  • 4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
  • 5. 人人文库网仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对用户上传分享的文档内容本身不做任何修改或编辑,并不能对任何下载内容负责。
  • 6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
  • 7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

评论

0/150

提交评论