Looking for a not equals

yes I have a default pool that things will fall through to. I just put up th snippet that I was unsure of.

Another question, if I use the log statement in the iRule one of the other posters said that this will be logged in /var/log/ltm , but I am not seeing the entries. I must be missing something.

  
 when HTTP_REQUEST {  
   if { [HTTP::cookie exists "mine"] } {  
      if { [[HTTP::cookie "mine"] starts_with "3" ] and not [IP::addr[IP::remote_addr] equals 10.1.1.0/255.255.255.0] } {  
        log "The cookie starts with 3" 
        pool bogus-onenode  
      } else {  
        log "Missed the cookie staring with 3" 
        pool failsafe  
      }  
   } else {  
     log "no cookie" 
     pool real-onenode  
   }  
 } 
 

Right, I am not looking for that what I am looking for is where it will log my log statements to?

 

 

Depending on whether or not you specify the facility, the messages may end up as entries in /var/log/ltm or as specified by /etc/syslog.conf. Here is the syntax and allowed values.

log [.] 

Available logging levels

"alert" "crit" "debug" "emerg" "err" "info" "warning" 

Available logging facility

"user" "syslog" "local0" "local1" "local2"  
  "local3" "local4" "local5" "local6" "local7"  "uucp"  
  "authpriv", "cron" "daemon" "ftp" "kern" "lpr"  
  "mail" "mark" "news" "ntp" "security"

Example

log local0.info 

Thanks for the info! I am coing to find out that between 9.0.4 and 9.0.5 syslogd changed to syslog-ng so I need to generate a new license to get this to work. Thank goodness this is a test box.

 

 

There is no relationship between syslog-ng and the requirement for a new license. Perhaps your license simply expired or was overwritten during the upgrade...?

Actually, it turns out there was a bug in the upgrade process (or maybe not a bug) but during the upgrade some fo the rpms never got installed, that's why I wasn't logging.