The BIG-IP system may not reflect the expected status for virtual servers that use iRules, HTTP classes or local traffic policies to select a pool:
The status of a virtual server using iRules that reference pools is derived as follows:
- The status of the default pool and each pool referenced within an iRule is considered when determining the status of the virtual server.
- When multiple pools are referenced from within a single iRule, the highest precedence status reflected by any pool is reflected as the virtual server's status. In order of precedence, the possible statuses are: Available, Offline, and Unknown.
These conditions result in the following virtual server status matrix:
Pool referenced by iRule | no default pool | default pool Available | default pool Offline | default pool Unknown |
None | Unknown | Available | Offline | Unknown |
Only Unknown pools | Unknown | Available | Offline | Unknown |
Only Offline pools | Offline | Available | Offline | Offline |
Only Available pools | Available | Available | Available | Available |
Available and Unknown pools | Available | Available | Available | Available |
Available and Offline pools | Available | Available | Available | Available |
Unknown and Offline pools | Offline | Available | Offline | Offline |
Available , Unknown, and Offline pools | Available | Available | Available | Available |
Available , Unknown, and Offline pools referenced in separate iRules | Available | Available | Available | Available |
No comments:
Post a Comment