sol6459:Order of precedence for virtual server matching (9.x - 11.2.1)
This article applies to BIG-IP 9.x through 11.2.1. For information about other versions, refer to the following article:
When determining the order of precedence applied to new inbound connections, the BIG-IP system uses an algorithm that places a higher precedence on the address netmask and a lesser emphasis on the port. BIG-IP LTM sets virtual server precedence according to the following criteria:
- The first precedent of the algorithm chooses the virtual server that has the longest subnet match for the incoming connection.
- If the number of bits in the subnet mask match, the algorithm chooses the virtual server that has a port match.
- If no port match is found, the algorithm uses the wildcard server (if a wildcard virtual server is defined).
-
A wildcard address has a netmask length of zero; thus, it has a lower precedence than any matching virtual server with a defined address.
This algorithm results in the following order of precedence:
:
:*
*:
*:*
Example of VIP precedence behavior
For example, for a BIG-IP system with the following VIPs configured on the inbound VLAN:
10.0.0.0/8:80
10.10.0.0/16:80
10.10.10.10/32:80
20.0.0.0/8:*
20.0.0.0/8:80
*:80 (alternatively noted as 0.0.0.0/0:80)
*:* (alternatively noted as any:any, 0.0.0.0/0:any)
The following table illustrates how inbound destination addresses map to the configured VIPs:
Inbound destination address | VIP |
10.10.10.10:80 | 10.10.10.10/32:80 - address match and port match |
10.10.10.11:80 | 10.10.0.0/16:80 - most specific address match and port match |
10.1.10.10:80 | 10.0.0.0/8:80 - most specific address match and port match |
20.0.0.0:80 | 20.0.0.0/8:80 - most specific address match and port match |
20.0.0.0:443 | 20.0.0.0/8:* - most specific address match with wildcard port |
1.1.1.1:443 | *:* - wildcard address and wildcard port |
Supplemental Information
- Beginning with BIG-IP LTM 9.4.0, the bigpipe db TM.ContinueMatching variable is set to false, which negates the precedence order and causes BIG-IP LTM to reject the packet if the requested virtual server is unavailable. For more information, refer to .
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/10543606/viewspace-1066070/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- Learning Semantic Concepts and Order for Image and Sentence Matching筆記筆記
- 使用Virtual Infrastructure Client 管理 VMWare ServerASTStructclientServer
- weblogic 9.X 配置Web
- F5負載均衡系列教程六【配置virtual Server】負載Server
- MSSQL sql server order by 1,2 的具體含義SQLServer
- order by在SQL Server與Oracle中的一個區別SQLServerOracle
- goldengate v11.2.1 版本的新特性Go
- 虛擬機器和容器的對比 Virtual Server VS Docker虛擬機ServerDocker
- web server apache tomcat11-24-Virtual Hosting and TomcatWebServerApacheTomcat
- "vSphere HA virtual machine failed to failover" error in vCenter Server問題分析MacAIErrorServer
- 請問banq,lvs(linux Virtual Server)何處有下載?LinuxServer
- 微軟稱Virtual Server 2005 R2將支援Linux(轉)微軟ServerLinux
- 7.2 FM Index MatchingIndex
- F - Perfect Matching on a Tree
- CSS orderCSS
- Order by 優化優化
- MySQL之order byMySql
- start-stop-daemon: matching on world-writable pidfile /var/run/redis/redis-server.pid is insecurefailedRedisServerAI
- ACM Binary String MatchingACM
- Scala的Pattern Matching Anonymous FunctionsFunction
- Indexing on Virtual ColumnsIndex
- 深度理解 Virtual DOM
- MySQL 之 ORDER BY FIELDMySql
- CSS3 orderCSSS3
- mysql order by 優化MySql優化
- [Javascript] Object property orderJavaScriptObject
- Leetcode 10 Regular Expression MatchingLeetCodeExpress
- Regular Expression Matching leetcode javaExpressLeetCodeJava
- Pattern Matching Metacharacters For asm_diskstringASM
- Virtual-DOM的理解
- 圖解 React Virtual DOM圖解React
- C++ Virtual函式C++函式
- C++ Virtual詳解C++
- Setup python virtual environmentPython
- 遷移Vmware Virtual MachineMac
- index , virtual , invisibleIndex
- Azure Virtual Machine (Azure for Students)Mac
- MySQL Order BY 排序過程MySql排序