iControl CORBA Portal

Since this is in the iControl v9.x forum, I assume you are using version 9.x or above of BIG-IP. If this is the case, then CORBA is not relevant as we removed the entire CORBA infrastructure in version 9.0. Now there is no longer a SOAP to CORBA bridge, but a SOAP only system which should help with memory usage and performance on the device.

As for auditing and logging, we've enhanced that in 9.x and it is controlled by the iControl.LogLevel db variable. Possible values include

 
 iControl.LogLevel = [none | debug | trace] 
   none  - No debugging is performed 
   debug - Error conditions are reported to the log. 
   trace - Full method call logging is performed 
           (user, method, params) - be warned this produced 
           a LOT of data in the logs.

And, for starting and stopping the services, there should not be a need now as everything is self-contained within the webservers application space. If you do need to restart it a bigstart restart httpd should do the trick.

-Joe

 

Sounds like a great improvement in the architecture.

 

 

How do I update the LogLevel db variable?

 

 

Where are the logs located?

 

 

Thanks,

 

 

David

To set the log levels:

 

 

b db icontrol.loglevel "debug" (or "none" to disable debugging)

 

bigstart restart httpd

 

 

All iControl debug loggings are in /var/log/ltm on 9.x. Please be warned that debug logging is very verbose.

 

 

Loc