测试keepalived在DR模式下VIP转发数据到RIP的过程
2015-03-30 13:48
417 查看
测试keepalived在DR模式下VIP转发数据到RIP的过程
此处测试环境约定: 【Client】 CIP = 10.0.200.22 MAC = 8c:89:a5:96:4c:b2(假设为11:11:11:11:11:11) 【Director】 VIP = 10.0.205.100 DIP = 10.0.200.21 MAC = 8c:89:a5:96:51:cf(假设为22:22:22:22:22:22) 【RealServer】 RIP = 10.0.205.2 MAC = 08:00:27:3b:62:f5(假设为33:33:33:33:33:33) 1)【Client】 ARP Request who has 10.0.205.100 tell 10.0.200.22 CIP = 10.0.200.22 MAC = 11:11:11:11:11:11 2)【Director】响应1,ARP Reply 10.0.205.100 is-at 22:22:22:22:22:22 VIP = 10.0.205.100 DIP = 10.0.200.21 MAC = 22:22:22:22:22:22 3)【Client】发送TCP SYN CIP = 10.0.200.22 MAC = 11:11:11:11:11:11 -> VIP = 10.0.205.100 MAC = 22:22:22:22:22:22 4)【Director】选一个【RealServer】,改数据包里的MAC为RIP的MAC,转发给RIP CIP = 10.0.200.22 MAC = 11:11:11:11:11:11 -> VIP = 10.0.205.100 MAC = 33:33:33:33:33:33 5)【RealServer】收包,发ARP,Request who has 10.0.200.22 tell 10.0.205.2 6)【Client】响应5)ARP Reply 10.0.200.22 is-at 11:11:11:11:11:11 7)【RealServer】使用VIP回应3 实测抓包内容: [root@svr200-22 ~]# tcpdump -nn host 10.0.200.22 and \(10.0.200.21 or 10.0.205.100 or 10.0.205.2\) tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes 18:08:31.342062 ARP, Request who-has 10.0.205.100 tell 10.0.200.22, length 28 18:08:31.342627 ARP, Reply 10.0.205.100 is-at 8c:89:a5:96:51:cf, length 46 18:08:31.342637 IP 10.0.200.22.58914 > 10.0.205.100.80: Flags [S], seq 3567838243, win 14600, options [mss 1460,sackOK,TS val 373309346 ecr 0,nop,wscale 7], length 0 18:08:31.343842 ARP, Request who-has 10.0.200.22 tell 10.0.205.2, length 46 18:08:31.343854 ARP, Reply 10.0.200.22 is-at 8c:89:a5:96:4c:b2, length 28 18:08:31.344629 IP 10.0.205.100.80 > 10.0.200.22.58914: Flags [S.], seq 4193479915, ack 3567838244, win 14480, options [mss 1460,sackOK,TS val 27450580 ecr 373309346,nop,wscale 6], length 0 18:08:31.344649 IP 10.0.200.22.58914 > 10.0.205.100.80: Flags [.], ack 1, win 115, options [nop,nop,TS val 373309348 ecr 27450580], length 0 18:08:39.260264 IP 10.0.200.22.58914 > 10.0.205.100.80: Flags [P.], seq 1:6, ack 1, win 115, options [nop,nop,TS val 373317264 ecr 27450580], length 5 18:08:39.261438 IP 10.0.205.100.80 > 10.0.200.22.58914: Flags [.], ack 6, win 227, options [nop,nop,TS val 27458498 ecr 373317264], length 0 18:08:39.261637 IP 10.0.205.100.80 > 10.0.200.22.58914: Flags [P.], seq 1:174, ack 6, win 227, options [nop,nop,TS val 27458498 ecr 373317264], length 173 18:08:39.261663 IP 10.0.200.22.58914 > 10.0.205.100.80: Flags [.], ack 174, win 123, options [nop,nop,TS val 373317265 ecr 27458498], length 0 18:08:39.261670 IP 10.0.205.100.80 > 10.0.200.22.58914: Flags [F.], seq 174, ack 6, win 227, options [nop,nop,TS val 27458498 ecr 373317264], length 0
相关文章推荐
- 测试keepalived备备模式的主从切换过程
- LVS+keepalived生产环境实现电信联通双VIP(DR模式)
- 测试Oracle 11gr2 RAC 非归档模式下,offline drop数据文件后的数据库的停止与启动测试全过程
- LVS+Keepalived+Nginx+Tomcat高可用负载均衡集群配置(DR模式,一个VIP,多个端口)
- (原创)(三)作为测试负责人测试过程监控中关注的度量数据
- SqlServer存储过程分页:大数据量分页存储过程效率测试附代码
- Sql语句与存储过程查询数据的性能测试
- 一个高效率SQL储存过程分页,执行效率测试通过500万以上的数据
- Lvs+keepalived实现负载均衡、故障剔除(DR模式)
- Keepalived+LVS-DR模式配置高可用负载均衡集群
- (原创)(三)作为测试负责人测试过程监控中关注的度量数据
- 测试数据的准备过程
- LVS+Keepalived 多个VIP 测试总结
- 测试list sort,用输出数据,显示过程
- ubuntu上配置LVS DR模式 + Keepalived
- NAS DIY的设计和实施过程-9 NAS性能调整测试呵呵,一些性能测试数据曝光。
- lvs/dr模式下keepalived应用的测试
- Sql语句与存储过程查询数据的性能测试实现代码
- Lvs+keepalived实现负载均衡、故障剔除(DR模式)
- [求解]在debug模式下程序正常运行(多次测试),运行模式下(正确数据)时常会抛异常,抛异常后事务也没有阻止,而继续执行操作?