For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

rubbishking_110's avatar
rubbishking_110
Icon for Nimbostratus rankNimbostratus
Mar 25, 2008

UDP Profile?

Hi All     I have created an iRules just now, however, it is failed when I tried to assigne to a virtual server.     "01070394:3: UDP::payload in rule (FIP_Route) requires an associated UD...
application delivery
dev
devops
iRules
Nicolas_Menant's avatar
Nicolas_Menant
Icon for Employee rankEmployee
Mar 26, 2008
CMP is not an iRule it's a BIGIP functionnality:

 

 

If you have an askF5 account: Click here

 

Otherwise it's here:

 

 

Clustered Multi-Processing (CMP) is a new feature to BIG-IP 9.4 that allows specific platforms with multiple processors to use multiple TMM instances to increase traffic handling.

 

 

CMP is only available on the following platforms:

 

 

* BIG-IP 8400

 

* BIG-IP 8800

 

 

CMP should not be confused with Symmetric Multi-Processing (SMP) as CMP is unique to the BIG-IP operating system, and only processes connections.

 

 

SMP architecture is utilized in multiple operating systems. SMP operates by allowing operating systems and software applications that are optimized for SMP to use the multiple processors available to the operating system. This is performed by spreading multiple threads across multiple processors, which allows for faster processing and more efficient use of system resources, as multiple threads can be processed simultaneously instead of waiting in a queue to be processed.

 

 

CMP is unique to BIG-IP LTM versions 9.4 and later. CMP creates separate instances of the Traffic Management Microkernel (TMM) for each processor on the system. This increases performance and accelerates traffic handling since there are multiple TMM instances handling traffic.

 

 

When a virtual server is enabled, the CMP feature is automatically enabled. When CMP is enabled, all instances of TMM are available to process application traffic as follows:

 

 

* 2 TMM processes running on a dual-CPU BIG-IP system (8400)

 

* 4 TMM processes running on a dual-core, dual-CPU BIG-IP system (8800)

 

 

CMP is not compatible with certain BIG-IP system configurations. If one of the following configurations exist, CMP will be disabled:

 

 

* The BIG-IP system is running BIG-IP ASM and/or the BIG-IP WebAccelerator module.

 

* Hardware compression is enabled.

 

 

If a virtual server references any of the following BIG-IP system features, CMP is disabled for that virtual server:

 

 

* A rate class

 

* iRules global variables

 

* A session persistence profile or iRule

 

* Traffic Management Operating System (TMOS) plug-ins