Forum Discussion
Nat_Thirasuttakorn
Employee
Nov 22, 2004node command does not work with host name
I tested 9.0.1. and found that node command does not work with host name
any idea how to make it work? (with out creating pool)
for example:
if my_class = "something www.google.co.th"
and i use find class to get the node hostname
set $hostname [getfield [ findclass "something" $::my_class ] " " 2 ]
then i force bigip to connect directly to the hostname
node $hostname "80"
any suggestion would be appreciated.
NAT
- unRuleY_95363Historic F5 AccountFirst, you need to use 9.0.2. he he he...
rule direct_name { when HTTP_REQUEST { set hostname [findclass "something" $::my_class " "] Hold HTTP data until hostname is resolved HTTP::collect Start a name resolution on the hostname NAME::lookup $hostname } when NAME_RESOLVED { node [NAME::response] 80 Release the hold on HTTP HTTP::release } }
- unRuleY_95363Historic F5 AccountOne caveat to this is that connections will be stalled indefinitely if the name is never resolved. In an upcoming release we are adding a timer command and TIMER_EXPIRED event where you could recover from no response.
- Nat_Thirasuttakorn
Employee
Thanks for great info! - unRuleY_95363Historic F5 AccountI'm sorry, but you'll just have to wait until it's released for more detailed information. Currently, it's still under design. Basically, the goal is to have an event that is fired after a specified amount of time. This would allow cleanup and/or closing of stalled or otherwise hung connections. We still have some implementation details to work out, so I'm not willing to give out any more information at this time.
- gefa_105039
Nimbostratus
Why is this done via the NAME::lookup command. In the examples in the documentation the servername is user and not the ip-address. I would expect the TM to use the name for the node and assosiate the specific node to the result of the command. Is this a bug? - rapmaster_c_127Historic F5 AccountIf you can point us to the incorrect documentation, we'll have it corrected. Unlike rules, pools, virtual servers and many other objects on the system, nodes/members are unnamed entities in BIG-IP's schema. Their lookup key is their IP address.
- Nat_Thirasuttakorn
Employee
Hi unRuleY, - unRuleY_95363Historic F5 AccountI will try to test tonight and report status back here.
- unRuleY_95363Historic F5 AccountWell, what I discovered is that there is a bit of configuration that is additionally needed in the tmm_base.tcl file. I am going out of town for a few days and I will post the necessary configuration changes when I return early next week. Maybe we can get Bl0ndie to post them in the meantime.
- Marcel_Derksen_
Nimbostratus
Hi, I placed a change request to add the ability to use the configured hostname in the node command. I looks like this will be added to one of the next releases. I will keep you informed about the progress.
Recent Discussions
Related Content
DevCentral Quicklinks
* 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
Discover DevCentral Connects