F5_GTM廣域網(wǎng)流量管理與優(yōu)化方案.ppt

1、BIG-IP Global Traffic Manager廣域網(wǎng)流量管理與優(yōu)化方案,應(yīng)用全球部署以后的挑戰(zhàn),異地容災(zāi)、故障切換 客戶感受：易于使用、最佳訪問(wèn)效果 應(yīng)用的協(xié)同 多數(shù)據(jù)中心資源的充分利用 擴(kuò)展性 可管理性,容災(zāi)方案：宕機(jī)的代價(jià)是沉重的,“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,傳統(tǒng)的應(yīng)用容災(zāi)方案的切換機(jī)制,手動(dòng)修改客戶端訪問(wèn)目的地址 手動(dòng)修改DNS解析記錄方式 應(yīng)用層重定向,都是需要人工介入！,指望人工進(jìn)行容災(zāi)切換是靠不住的,$,Error Prone,Slow to Implement,Costly,Labor Intensive,網(wǎng)絡(luò)管理員,“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,錯(cuò)誤修改DNS記錄的后果是極其嚴(yán)重的,客戶感受,易于使用 最快

4、響應(yīng)速度,UNIX,WINS,Internal DNS Servers,跨ISP訪問(wèn)：南北電信互訪問(wèn)題,多應(yīng)用在多數(shù)據(jù)中心中的協(xié)同問(wèn)題,Clinical records down in Dallas data center!,Clinical Record Services,Employee Information Services,Personal Information Services,Service Oriented Architecture,特性：應(yīng)用智能、可管理性與高性能 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,極大提升全球交付應(yīng)用的 可用性與可靠性,主要功能與優(yōu)勢(shì),支持應(yīng)用在多個(gè)數(shù)據(jù)中心間進(jìn)行透明交付 確保全球業(yè)務(wù)的連續(xù)性和應(yīng)用的可用性 靈活的負(fù)載均衡算法，能夠根據(jù)任何一項(xiàng)業(yè)務(wù)政策（包括地理信

6、息、負(fù)載情況、網(wǎng)絡(luò)就近性等），并通過(guò)為直接用戶交付全球流量控制，來(lái)增強(qiáng)靈活性。 引導(dǎo)用戶進(jìn)入全球最佳站點(diǎn)，能夠顯著改進(jìn)性能并提高客戶的體驗(yàn)。 集中管理與監(jiān)控，實(shí)現(xiàn)從單一地點(diǎn)提供全面的應(yīng)用和數(shù)據(jù)中心狀態(tài)信息，降低管理開(kāi)銷(xiāo) 通過(guò)充分利用備份數(shù)據(jù)中心，以提高全球網(wǎng)絡(luò)的效率、可擴(kuò)展性以及投資回報(bào)。 能夠?qū)崿F(xiàn)復(fù)雜任務(wù)的自動(dòng)化流程，從而降低維護(hù)和管理開(kāi)銷(xiāo)。,廣州數(shù)據(jù)中心,上海數(shù)據(jù)中心,User 查詢,Local DNS,F5 BIG-IP GTM-廣域網(wǎng)流量管理與優(yōu)化方案,BIG-IP,Server farm,Webmaster,北京數(shù)據(jù)中心,Router,BIG-IP,GTM,GTM 基本工作機(jī)制,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決策過(guò)程,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 采用分層的負(fù)載均衡機(jī)制 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,廣域網(wǎng)訪問(wèn)流量?jī)?yōu)化,歐洲用戶,美洲用戶,GTM,德國(guó) Data Center,美國(guó)Data Center,= 集成的性能結(jié)構(gòu),商業(yè)標(biāo)準(zhǔn),控制全球用戶訪問(wèn)在多個(gè)數(shù)據(jù)中心之間的流量分配,地址位置就近訪問(wèn)Topology,亞洲用戶,新加坡 Data Center,Topology 舉例,來(lái)自北

13、美（North America）的訪問(wèn)請(qǐng)求導(dǎo)向到北美的兩個(gè)數(shù)據(jù)中心（ NA ） 來(lái)自北美（ Europe ）的訪問(wèn)請(qǐng)求導(dǎo)向到北美的兩個(gè)數(shù)據(jù)中心（ London ） 來(lái)自其它地方的訪問(wèn)請(qǐng)求導(dǎo)向到北美的兩個(gè)數(shù)據(jù)中心（ 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,網(wǎng)絡(luò)就近性動(dòng)態(tài)探測(cè),GTM支持的負(fù)載均衡算法,循環(huán) 全球可用性 LDNS持續(xù)性 應(yīng)用可用性 地理分布 虛擬服務(wù)器容量 最少連接 Pkt/sec（數(shù)據(jù)包/每秒） KB/sec（千字節(jié)/每秒） 往返時(shí)間 中繼段（hop） 數(shù)據(jù)包完整率 用戶定義服務(wù)質(zhì)量（QoS） 動(dòng)態(tài)比率 LDNS循環(huán) 比率 隨機(jī),組合的負(fù)載均衡算法,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.,自動(dòng)容災(zāi)切換,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服務(wù)器可用性檢查（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),服務(wù)器可用性檢查,Application,Device,FTP,HTTP,DB.D,HTTPS ,Siebel App,Oracle

21、DB,內(nèi)容 / 文件檢查,Data Center,Intranet App: Siebel in 紐約 HTTP Server DB Server Siebel App Oracle DB Siebel content verification,可用性,解決方案: web服務(wù)穿過(guò)特定區(qū)域、設(shè)備，使應(yīng)用得到一個(gè)統(tǒng)一服務(wù)檢測(cè)的批量可用性 好處:可探測(cè)到任意標(biāo)準(zhǔn)的web服務(wù)套件的失敗,多應(yīng)用協(xié)同Distributed Applications,distributed application是一個(gè)要使用到多個(gè)域名（wideip）的應(yīng)用，這些域名分布在不同的服務(wù)器上，由這組服務(wù)器協(xié)同工作構(gòu)成一個(gè)完整的應(yīng)

22、用. Distributed Applications 將多個(gè)Wideip當(dāng)作一個(gè)對(duì)象來(lái)進(jìn)行管理，可以同時(shí)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 當(dāng)構(gòu)成Distributed Application的Wideip中有任何一個(gè)，其對(duì)應(yīng)的virtual server都不同用的話，對(duì)這個(gè)Distributed Application來(lái)說(shuō)，這個(gè)virtual server所屬的數(shù)據(jù)中心就是不可用的。 但其它不屬于這個(gè)Distributed Application的訪問(wèn)請(qǐng)求，仍然可以被分發(fā)到這個(gè)數(shù)據(jù)中心的。 Example 2: Server Dependency 當(dāng)構(gòu)成Distributed Application的Wideip中有任何一個(gè)，其對(duì)應(yīng)的virtual serv

25、er都不同用的話，對(duì)這個(gè)Distributed Application來(lái)說(shuō)，這個(gè)virtual server所屬的服務(wù)器就是不可用的。 但其它不屬于這個(gè)Distributed Application的訪問(wèn)請(qǐng)求，仍然可以被分發(fā)到這個(gè)服務(wù)器上來(lái)。,ZoneRunner減少DNS配置錯(cuò)誤,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沈陽(yáng),Site西安,Site成都,Site長(zhǎng)沙,Site廣州,Site杭州,Site北京,Site 教育網(wǎng),Site 中國(guó)移動(dòng),成功案例 - ChinaCache,ChinaCache 中國(guó)最大的CDN服務(wù)提供商 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廣州機(jī)房,GB,FE,Cache Server,WEB/Streaming Server,Big IP 5000,Big IP 5000,21cn上海節(jié)點(diǎn),Core Switch,Internet,WEB/Streaming Server,Big IP 2400,Core

28、Switch,21cn河北節(jié)點(diǎn),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