Bluecoat Proxy Template (inc fan & temp) (2005/09/19)

[scottsta]

Hi - I 'm struggling - trying to get these availability scripts and graphs working for any device (not just a bluecoat) - has anyone managed to do this ?
thanks

[flaifel]

Dears,

I found the templated for Blue Coat, and it was good. thanks for the poeple who made this effort.

Later i found the modified version that has the fan/tem./hit ratio ... and others with the perl scripts. My question is where to add those perl scripts and how to see the graphs.

regards,
Mohammad

[frosty]

Hi,

Isn't proxySG_workers.pl really checking client connections, not HTTP workers? At least this seems to be the case for newer SGOS releases. According to /HTTP/Statistics it's like this:
HTTP_MAIN_0103 #max workers
HTTP_MAIN_0102 #current workers
HTTP_MAIN_0090 #max clients
HTTP_MAIN_0091 #current clients

Or, am I missing something?

Regards, Bjorn

[millap]

Hello all,

SGOS 5.4 has some nice new additions to the MIB so you can graph the following OIDs.

sgProxyHttpClientConnections
sgProxyHttpClientConnectionsActive
sgProxyHttpClientConnectionsIdle
sgProxyHttpServerConnections
sgProxyHttpServerConnectionsActive
sgProxyHttpServerConnectionsIdle

snmpwalk -v 2c -c <community> -m /usr/share/snmp/mibs/BLUECOAT-SG-PROXY-MIB.txt <ip> .1.3.6.1.4.1.3417.2.11.3.1.3

BLUECOAT-SG-PROXY-MIB::sgProxyHttpClientConnections.0 = Gauge32: 31
BLUECOAT-SG-PROXY-MIB::sgProxyHttpClientConnectionsActive.0 = Gauge32: 1
BLUECOAT-SG-PROXY-MIB::sgProxyHttpClientConnectionsIdle.0 = Gauge32: 30
BLUECOAT-SG-PROXY-MIB::sgProxyHttpServerConnections.0 = Gauge32: 0
BLUECOAT-SG-PROXY-MIB::sgProxyHttpServerConnectionsActive.0 = Gauge32: 0
BLUECOAT-SG-PROXY-MIB::sgProxyHttpServerConnectionsIdle.0 = Gauge32: 0

This makes it possible to observe client and server connection usage at the same time.

I've exported a host template for this which produces the following graphs (Cacti 0.8.7d)

Cheers
millap

[frosty]

Thanks!

However, it seems you put the upper limit to 100 on most/all graphs which creates problems for client connections and so forth where you can have a lot more than that.

[millap]

Hi there,

Thanks for your response. I've amended and retested the template along with adding additional graphs based on the SGOS 5.4 mib.

This has been tested on an install where four SG's are load-balanced against for over 50K+ clients.

The following new OID's are now used and graphed;

BLUECOAT-SG-PROXY-MIB::sgProxyMemAvailable
BLUECOAT-SG-PROXY-MIB::sgProxyMemCacheUsage
BLUECOAT-SG-PROXY-MIB::sgProxyMemSysUsage
BLUECOAT-SG-PROXY-MIB::sgProxyMemoryPressure
BLUECOAT-SG-PROXY-MIB::sgProxyHttpClientHitRate
BLUECOAT-SG-PROXY-MIB::sgProxyHttpClientRequestRate

Here's the output from my 0.8.7e install and updated template;



Cheers
millap

[cdooer]

I realize this is an old thread, but I just stumbled across it and it's working great for me. The only thing that doesn't work is the CPU. Could it be becasue it's a new Bluecoat that's 64bit? The BC I'm trying to monitor is an SG600.

[bidzer]

Getting hash errors on import. What version do you have this working on? I'm running 0.8.6j

Thanks

[bidzer]

Never mind, I see it's for 0.8.7e

Sorry

[gunzl1ng3r]

I realize this is an old thread, but I just stumbled across it and it's working great for me. The only thing that doesn't work is the CPU. Could it be becasue it's a new Bluecoat that's 64bit? The BC I'm trying to monitor is an SG600.

Hi, just in case you're running SGOS v6 or higher:
> The reason for the CPU-Graph no longer working, is the fact that BC finally deactived their old CPUbusy and Idle OID in their BLUECOAT-SG-PROXY-MIB.
From OS v6 on the CPU data is provided through the sgProxyCpuTable, allowing you to monitor every core individually.

With the awesome help of the guys in this thread - http://forums.cacti.net/viewtopic.php?f ... 40#p224840 - I finally got my DataQuery for this up and running.

I attached the before mentioned BLUECOAT-SG-PROXY-MIB, the DataQuery (sgProxyCpuTable.xml) and the exported Templates (cacti_graph_template_proxysg_v6_-_cpu_gt.xml) - the two .xml files are packed inside ProxySG_v6_CPU.zip.

Just for the record, I didn't make any fancy calculation from the counters provided in the table but decided to take the easy way out by querying for the sgProxyCpuCoreBusyPerCent and sgProxyCpuCoreIdlePerCent.
BC didn't want this to be easy , so they do not allow to query the OID that contains the list of available CPUs, so I had to query sgProxyCpuCoreBusyPerCent and use a RegEx to generate the index.

Instructions:
#1 Simply copy the sgProxyCpuTable.xml to the place where you keep your other DataQueries
#2 Use Cacti's ability to "Import Templates", select the cacti_graph_template_proxysg_v6_-_cpu_gt.xml and enjoy
BTW: The template was created on Cacti v0.8.7g

Greetings, gunzl1ng3r