Professional Documents
Culture Documents
Troubleshooting
April 2016
• CPU percentages
percentages are available in many places within the
management console UI:
• Statistics->Summary->Device
• Statistics->Health Monitoring->General
• Statistics->System->Resources->CPU
CPU statistics in the management console UI
• All three CPU reports/graphs are generated from the same set
of data on ProxySG.
ProxySG. This data is available in the
the persistent
data manager (PDM) statistics in a sysinfo and default
snapshots.
• All three CPU reports/graphs show a single CPU percentage
• On ProxySG 6.6.1.x or older (6.5, 6.4, etc.) the busiest CPU on multiple
CPU ProxySG platforms is shown in these reports/graphs
• On ProxySG 6.6.2.x and newer an average of all the platforms CPUs is
shown in these reports/graphs
• The CPU percentage shown is the average CPU over 60 seconds
• Very short spikes in CPU usage might not show in these reports/graphs
CPU statistics in the CLI
• Components shown
• Most component names are meaningful
• Two components commonly seen that need clarification:
• Object store –
store – Kernel,
Kernel, Cache Engine, Storage
• Miscellaneous –
Miscellaneous Processing that does not fit into a main component
– Processing
CPU Monitor in the advanced URL
#conf t <enter>
#(config)diagnostics <enter>
#(config
#(config diagnost
diagnostics)
ics)cpu-m
cpu-monit
onitor
or ?
disable
disable Disable
Disable the CPU Monitor
Monitor
enabl
enable
e Enable
Enable the CPU Monito
Monitor
r
interval Configure the CPU Monitor interval
CPU Monitor in the CLI
• Viewing CPU Monitor output from the CLI must be done from f rom
‘enable’ mode
• Command to view CPU monitor is ‘show cpu-monitor’
• Data is not updated #show cpu-monitor
until interval expires CPU Monitor:
Configured interval duration: 59 seconds
• Time in interval Current interval complete in: 18 seconds
remaining also
CPU 0 6%
displayed Console Agent 3%
Miscellaneous 2%
CPU Health check alerting
• CPU utilization
• Current state
• Default snapshots
snapshots contain all of the above.
above. Heartbeats only
only
contain ‘daily15minute’.
Identifying and investigating a past CPU issue
• Once a CPU issue is found in the PDM data other types of data
can be analysed to find correlati
correlations.
ons. An example:
system:cpu-usage~hourly@Fri, 01 Apr 2016 00:08:00 UTC[07](60, 60): 9 9 9 9 9
9 9 9 9 9 9 9 10 9 9 9 9 9 9 9 12 9 10 9 10 9 10 9 9 9 9 9 9 9 9 9 9 9 9 9 9
10 9 9 9 9 9 9 9 12 10 9 50 90 100 46 10 10 9 9
users:current~hourly@F
users:current~hourly@Fri,
ri, 01 Apr 2016 00:08:00 UTC[07](60, 60): 1 0 1 1 1 0 0
0 1 0 1 0 0 1 1 0 0 0 0 0 1 0 0 0 1 0 0 0 0 0 1 0 1 0 1 1 0 0 0 0 1 0 0 0 1 0
0 0 0 0 1 0 3057 5932 6348 2680 1 0 0 0
• Statistics->System->Resources->Memory
Statistics->System->Resources->Memory Use:
Memory statistics in the management console UI
• Statistics->System->Resources->Memory
Statistics->System->Resources->Memory Use includes a number
of data points.
• For memory issues look at
the following:
• Committed and available
memory at the top
• Committed and free
application memory at the
bottom
• Issues are usually with
application memory
Memory statistics in the CLI
• TCPIP’s memory usage over the last hour, static (this is OK):
1, TCPIP: 3358720, 3358720, 3358720, 3358720, 3358720, 3358720, 3358720, 3358
720, 3358720, 3358720, 3358720, 3358720, 3358720, 3358720, 3358720, 3358720,
335
3358720,
720, 33587
58720,
20, 3358
33587
720,
20, 335
335872
8720, 335
3358720
8720,
, 3358
335872
720
0, 3358
358720,
720, 335
335872
8720, 33587
587
20, 3358720, 3358720, 3358720, 3358720, 3358720,
• ProxySG
ProxySG had 4GBs
4GBs of RAM in the above example
exampless
Memory Health check alerting
• Current state
• A leak is an ever
increasing value over
time.
• Both Traffic Mix and Traffic History use the same service names
and proxy types.
• Service name
name tracks bandwidth
bandwidth matching
matching IPs or
or ports. Within
that traffic different proxies can process the traffic.
• Explicit HTTP can contain HTTPS traffic within it
• Proxy reports give better visibility into types of traffic processed
Troubleshooting CPU and memory issues
Troubleshooting
Troubleshooting CPU and memory issues
• KB Article:
http://bluecoat.force.com/knowledg
http://bluecoat.force.com/knowledgebase/articles/Solution/0
ebase/articles/Solution/000024136
00024136
• SSL interception on exception default mode in SGOS 6.2+
• Add splash text to SSL interception on exception policy rule
CPU issues caused by general load
• Check the following when CPU pattern looks like general load:
• Did something in the environment change that triggered the CPU?
• More traffic moving from HTTP to HTTPS?
• Cloud services being adopted?
• Bandwidth being processed from Traffic
Traffic Mix graphs.
graphs. Is the proxy sizing
correct?
• User counts and connections, are the values expected?
• Statistics->System->Resources->Concurrent
Statistics->System->Resources->Concu rrent Users
• TCP Users
Users advanced
advanced URL: /TCP/users
• Active sessions, clients accessing data that should be controlled?
High memory in HTTP/TCP/SSL/ADN components
• Community where you can learn from and share your valuable
knowledge and experience with other Blue Coat customers
• Research, post and reply to topics relevant to you at your own
convenience
• Blue Coat Moderator Team ready to offer guidance, answer
questions, and help get you on the right track
• Access at forums.bluecoat.com and register for an account
today!
Thank you for Joining Today!