Split-screen-image

Why monitoring virtual F5 BIG-IP instances needs to go hand-in-hand with monitoring the underlying hardware platform

March 2, 2017

Specific F5 BIG-IP hardware platforms support the running of virtual BIG-IP instances, also called v CMP guests.

Main monitoring efforts typically focus on these virtual instances (and rightly so!), as they perform the bulk of the work around application delivery.

But one should not forget to monitor the hosting platform, too.

Unless you understand the resource use of the physical hosting platform, you cannot reliably determine the health of your guest v CMPs.

For example:

  • CPU use of individual v CMPs could be rather moderate, but the hosting platform CPU use is maxed out, limiting v CMP scalability.
  • Network traffic of individual v CMPs could be quite reasonable, but the hosting platform NIC use is at full capacity.

 

The fact is that virtual BIG-IP instances are limited by resources of the hosting BIG-IP platform and, monitoring one without the other, will not point out potential bottlenecks.

HYCU SCOM Management Pack for F5 BIG-IP is able to capture resource use of both F5 BIG-IP physical hardware platform as well as guest v CMPs. That way, you can easily compare historical CPU or network traffic in a single graph or receive alerts when physical or virtual aspect of the BIG-IP deployment starts running out of resources.

Do you want to see it first hand? Request a demo or get 45-day free trial.

Shive Raja Headshot

SVP of Product

Subbiah Sundaram is the SVP, Product at HYCU. Subbiah spearheads product management, product marketing, alliances, sales engineering, and customer success with more than 20 years' experience delivering best-in-class multi-cloud data protection and on-premises solutions. A Kellogg Management School MBA graduate, Subbiah has worked with leading companies such as EMC, NetApp, Veritas, BMC, CA, and DataGravity.

eclipse
Follow us

Get started today

Seriously, you really need to experience HYCU to believe it.