Forum Discussion
citrix xmlb server enum pool
Using the Citrix iapp it creates for you the xml brokers, but it also creates a new pool called xmlb enum pool on port 137. What purpose is this and does it need to be 137? Thanks.
3 Replies
- Greg_Crosby_319Historic F5 Account
There is a known NetBIOS enumeration delay for some versions of citrix servers, the virtual server and pool resolves this know issue.
- tolinrome_13817
Nimbostratus
Thanks, the document you refer to says it applies only to Web Interface 5.4. Is it safe to delete this enum vip or nodes if we arent using that version?
- Greg_Crosby_319Historic F5 Account
I only posted one of a few kb articles on the subject. Seems to also effect earlier storefront versions. There are a couple ways to mitigate this behavior, might be worth investigating a couple of these posts if you are seeing this behavior after removing the enumeration VS from the BIG-IP. search
A good way to see if the VS is in use is to check the pool stats for udp 137 to see if they increment. If not, then you could disable the nodes in the udp 137 pool to see if users notice a delay in application enumeration.
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