Forum Discussion
F5 rule for access particular CAS server from Cisco TMSXE server
Hi,
i need your help to create F5 rule for access one particular CAS server (http://searchexchange.techtarget.com/definition/Client-access-server-CAS) from Cisco TMSXE server (http://www.cisco.com/c/en/us/products/collateral/conferencing/telepresence-management-suite-tms/data_sheet_c78-704865.html).
Presently rule is created for EWS with persist cookie for exchange 2010 and its clients.i can not modify the existing rule to access only one CAS server. ( in my environment have two CAS server is in place).
Is it possible to create new rule on F5 to access one particular CAS from TMSXE server and also i would like know any rule that access one CAS , it that is down reach the secondary CAS from TMSXE .
I am from Cisco Voice domain and not familiar with F5, your help is highly appriciated.
Thanks & regards, Shiresiva
3 Replies
It might help to give us the current configuration that you've got on the F5 currently, especially the rule that you're talking about.
But the simple answer if you want to have one server take all the traffic unless it is out of service, use priority group on the pool.
It's possible that I misunderstood your question.
- Shiresiva_18082
Nimbostratus
Hi cdougall, Expecting New rule (iRule to select pool and persistence method) that is access one CAS (say primary) in a pool. if primary CAS fails ,the rule point out another CAS (say secondary) in another pool. if the TMSXE server ip would be 10.81.X.X, how to create i new rule with priority ? Thanks & regards, ShireSiva
So, in this case, since what you're looking for all comes canned within LTM, you can do just what you're looking for with something like the following. In this config, 10.10.10.1 will be the only member taking traffic, unless it is out of service. In that case, and only in that case, 10.10.10.2 will take over.
I've put cookie persistence on for this example, but that should be modified to meet your needs.
ltm pool test-pool { members { 10.10.10.1:http { address 10.10.10.1 priority-group 10 session monitor-enabled } 10.10.10.2:http { address 10.10.10.2 session monitor-enabled } } min-active-members 1 monitor http } ltm virtual test-vip { destination 10.20.10.1:http ip-protocol tcp mask 255.255.255.255 persist { cookie { default yes } } pool test-pool profiles { http { } oneconnect { } tcp { } } source 0.0.0.0/0 source-address-translation { type automap } }
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
