bad IP address format error with node command

That's awfully strange. That looks exactly correct to me. Have you tried moving this to another event, yet? This shouldn't matter, but would be worth a try.

 

 

That IP format looks fine...very odd.

 

 

Colin

Some IPs work and some do not with the node command. It is not clear why. I see no difference between the IP that works and the IP that does not work. I would replace the same node IP with another IP and it works.

 

If I use the pool command instead of the node, then it always works for all IPs.

I am noticing a potential bug with interaction of node statement with UDP::payload in ClLIENT_ACCEPTED event. For the below simple TCL script, if IP a.b.c.d is same as w.x.y.z, then the bad IP address format error is generated. One way around is to use pool statement instead of the node. Any other suggested work around? Is there a way to open a bug report to have F5 fix this in the future?

 

 

when CLIENT_ACCEPTED {

 

if {[UDP::payload] contains "a.b.c.d"} {

 

node w.x.y.z 5060

 

}

 

}

You can certainly contact Technical Support to get the process rolling on submitting a bug. That sounds like a strange occurrence for sure. I'll try to find some time to test this one out too. Thanks for the heads up!

 

 

Colin