health check+ report
TRANSCRIPT
Health Check+
Report
Created for Customer
July 3rd 2014 - August 3rd 2014
| Riverbed Elite Partner | Riverbed Authorized Support Partner | Riverbed Authorized Training Partner |
| Riverbed Authorized Consulting Partner |
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 2 of 69
August 7th 2014
Contents
Introduction ......................................................................................................................... 5
Preface ............................................................................................................................. 5
Monitored devices .............................................................................................................. 6
Recommendations ................................................................................................................ 7
Global .............................................................................................................................. 7
Global Network and Application Performance ...................................................................... 7
SteelHead specific .............................................................................................................. 9
SteelHead general recommendations ................................................................................. 9
Traffic profile recommendations ........................................................................................ 9
Traffic reduction ........................................................................................................... 9
Percentage passthrough traffic ....................................................................................... 9
Traffic connections ..................................................................................................... 10
Sizing recommendations ................................................................................................ 11
Global ............................................................................................................................... 15
Traffic totals .................................................................................................................... 15
Traffic volume ................................................................................................................. 16
Global Top 3 Servers by top 10 most used protocols ............................................................ 17
Protocols by traffic volume ............................................................................................. 17
Protocols by connections ................................................................................................ 18
Global Network and Application Performance ....................................................................... 19
Site specific statistics .......................................................................................................... 20
SteelHead general ............................................................................................................ 20
SteelHead sizing .............................................................................................................. 21
SteelHead traffic volume ................................................................................................... 23
SteelHead connections...................................................................................................... 25
SteelHead specific ............................................................................................................... 26
STEELHEAD01 ................................................................................................................. 27
STEELHEAD02 ................................................................................................................. 28
STEELHEAD03 ................................................................................................................. 29
STEELHEAD04 ................................................................................................................. 30
STEELHEAD05 ................................................................................................................. 31
STEELHEAD06 ................................................................................................................. 32
STEELHEAD07 ................................................................................................................. 33
STEELHEAD08 ................................................................................................................. 34
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 3 of 69
August 7th 2014
STEELHEAD09 ................................................................................................................. 35
STEELHEAD10 ................................................................................................................. 36
STEELHEAD11 ................................................................................................................. 37
STEELHEAD12 ................................................................................................................. 38
STEELHEAD13 ................................................................................................................. 39
STEELHEAD14 ................................................................................................................. 40
STEELHEAD15 ................................................................................................................. 41
STEELHEAD16 ................................................................................................................. 42
STEELHEAD17 ................................................................................................................. 43
STEELHEAD18 ................................................................................................................. 44
STEELHEAD19 ................................................................................................................. 45
STEELHEAD20 ................................................................................................................. 46
STEELHEAD21 ................................................................................................................. 47
STEELHEAD22 ................................................................................................................. 48
STEELHEAD23 ................................................................................................................. 49
STEELHEAD24 ................................................................................................................. 50
STEELHEAD25 ................................................................................................................. 51
STEELHEAD26 ................................................................................................................. 52
STEELHEAD27 ................................................................................................................. 53
STEELHEAD28 ................................................................................................................. 54
Appendix ........................................................................................................................... 55
SteelHead models ............................................................................................................ 55
SteelHead CX-series ...................................................................................................... 55
SteelHead virtual CX-series ............................................................................................ 56
SteelHead EX-series ...................................................................................................... 57
SteelHead xx50 series ................................................................................................... 58
SteelHead xx20 series ................................................................................................... 59
SteelHead Global ............................................................................................................. 62
Traffic totals ................................................................................................................. 62
Traffic Volume .............................................................................................................. 62
Global Top 3 Servers by top 10 most used protocols .......................................................... 62
Global Network Application Performance ............................................................................. 62
SMB signing errors ........................................................................................................ 62
SMB v2 errors ............................................................................................................... 62
Delegation errors .......................................................................................................... 62
NFS connections, SDR only ............................................................................................. 63
Passthrough SSL connections on RFC1918 address space ................................................... 63
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 4 of 69
August 7th 2014
Lotus Notes Connections, SDR only ................................................................................. 63
Encrypted Lotus Notes ................................................................................................... 63
Packet ricochet ............................................................................................................. 63
SteelHead General ........................................................................................................... 64
Site ............................................................................................................................. 64
Model .......................................................................................................................... 64
RiOS version ................................................................................................................. 64
Gateway Up .................................................................................................................. 64
SteelHead Up................................................................................................................ 64
Healthy ........................................................................................................................ 65
Degraded ..................................................................................................................... 65
Admission Control ......................................................................................................... 65
Critical ......................................................................................................................... 66
SteelHead Sizing .............................................................................................................. 67
SteelHead Model ........................................................................................................... 67
Optimized connections ................................................................................................... 67
Outbound bandwidth ..................................................................................................... 67
Datastore Usage ........................................................................................................... 67
Percentage of total optimized traffic ................................................................................ 67
Top 10 application reduction in percent ............................................................................ 67
SteelHead Traffic ............................................................................................................. 68
Avg. Site Reduction ....................................................................................................... 68
Optimized Traffic ........................................................................................................... 68
Pass Through Traffic ...................................................................................................... 68
Most Used Protocol Name ............................................................................................... 68
Most Used Protocol Reduction ......................................................................................... 68
Site specific statistics ....................................................................................................... 69
Traffic Volume pie and bar chart ..................................................................................... 69
Traffic connections pie and bar chart ............................................................................... 69
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 5 of 69
August 7th 2014
Introduction
Preface
This report provides an overview of the Riverbed installation. It addresses the health of the complete Riverbed installation, active support cases, recommendations of changes to the SteelHead estate and key traffic information for each Riverbed SteelHead appliance monitored.
The target audience for this report is primarily technical and as such the report assumes a base knowledge of Riverbed WAN optimization for a full understanding of the content.
The absence of capacity planning graphs in this report is due to the fact it requires a minimum of 90 days data collection. The support case information is also not present in this report due to RLM
service not being part of the POC.
In addition to this report, a CIFS/SMB2 Deep-dive report has also been created. This report has in-depth optimization analysis of the CIFS/SMB2 protocol and it will provide a detailed view into the optimization of this protocol.
In addition to the RPAM report, a detailed GNAP (Global Network and Application Performance) report has been created with the purpose of identifying incidents that are not significant enough to provide global recommendation on. If however these incidents were concentrated to a small number of SteelHead appliances, the business impact can be significant enough to justify effort in resolving the anomalies.
Both the CIFS Deep-dive- and Detailed GNAP reports demonstrate the value of having RPAM collect significant amounts of data. The raw data can be used to zoom into specific functional elements of the Riverbed solution and expedite troubleshooting processes on this. Further reducing the TCO and shortening the time to fix.
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 6 of 69
August 7th 2014
Monitored devices
The listed sites below, with a figure in the right column, have been identified as having a
recommendation associated with it.
Total number of monitored devices: 28 Total number of devices with recommendations: 21
Site
Recom
mendatio
ns
Site
Recom
mendatio
ns
STEELHEAD01 STEELHEAD02 5
STEELHEAD03 1 STEELHEAD04 2
STEELHEAD05 1 STEELHEAD06 1
STEELHEAD07 STEELHEAD08 1
STEELHEAD09 1 STEELHEAD10 1
STEELHEAD11 1 STEELHEAD12
STEELHEAD13 1 STEELHEAD14
STEELHEAD15 2 STEELHEAD16
STEELHEAD17 1 STEELHEAD18 2
STEELHEAD19 1 STEELHEAD20 1
STEELHEAD21 STEELHEAD22 2
STEELHEAD23 1 STEELHEAD24 1
STEELHEAD25 1 STEELHEAD26
STEELHEAD27 1 STEELHEAD28
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 7 of 69
August 7th 2014
Recommendations
Global
Global Network and Application Performance
SMB signing errors We have observed 1599772 SMB signed connections errors during the report period. When the
client and the file server exchange the SMB traffic signed (for security reasons) the SteelHeads still
de-duplicate the traffic and apply TCP optimization. The result of this will cause no latency
optimization and thereby significantly decrease the end user performance experience.
It is highly recommended to configure the SteelHead appliances for optimization of SMB signed
traffic. This is done by activating the SMB signing optimization feature in the SteelHead appliances.
Enabling SMB-Signing on a SteelHead appliance requires it to be part of the Windows Domain. If
the SteelHead appliance is joined as a workstation it requires a delegation account to do SMB-
signing and a replication user if end to end Kerberos is needed. If the SteelHead appliance is joined
as a BDC (Backup Domain Controller) or RODC (Read Only Domain Controller), no delegation user
is required unless end to end Kerberos authentication is required. In such a scenario we need a
replication user.
It is highly recommended to join SteelHeads as BDC or RODC as it simplifies the configuration and
avoids the limitations of the delegation user.
Since enabling SMB-Signing requires a service restart it is highly recommended to do this
implementation during a Maintenance window.
For further information please see CIFS Deep Dive report.
SMB v2 errors We have observed 454 SMB v2 connections errors during the report period. This means that clients
and servers that are running the SMB2 protocol were not optimized with latency optimization. It is
recommended to enable SMB2 on all SteelHeads and make sure that if any SteelHead Mobile clients
are present in the network that they are also upgraded to v4.0 and have SMB2 enabled.
For further information please see CIFS Deep Dive report.
Delegation errors
We have observed 716 delegation errors during the report period, on either SMB signed or
Encrypted MAPI connections. This means that there is no layer 7 optimization on these connections
and it is recommended to take action on this issue.
NFS connections, SDR only We have observed 350 NFS connections during the report period, with only SDR optimization. An
investigation is required to find a reason and a solution for this.
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 8 of 69
August 7th 2014
Passthrough SSL connections on RFC1918 address space We have observed 2176920 SSL connections passed through on the RFC1918 address space during
the report period. It might be possible to optimize these connections, and it is recommended to
take action on this issue.
Passthrough Citrix ICA connections on RFC1918 address space We have observed 217048 passthrough Citrix ICA connections on RFC1918 address space. From
RiOS version 6, Citrix optimization has been greatly enhanced. Depending on your environment, it
could be very beneficial to review the optimization on your Citrix traffic.
Packet ricochet We have observed 22418 times of Packet ricocheting during the report period. This means that
some packets are seen more than once by the SteelHead, which introduces latency. Actions can be
taken to prevent this, by changing the default gateway or enabling simplified routing on the
SteelHead. Sometimes this is also caused by a server being offline.
For further investigation please see GNAP detailed report.
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 9 of 69
August 7th 2014
SteelHead specific
SteelHead general recommendations
This section shows if a SteelHead has been either down or in Degraded, Admission control or Critical mode during the report period. STEELHEAD02
Admission Control - 12.18%
Traffic profile recommendations
To postpone or even avoid costly upgrades of SteelHead appliances that suffers from overutilization, all steelheads have been screened for applications that potentially could be subject for a traffic profile change. By passing through these potential applications valuable and increased
capacity can be achieved and costly upgrades can be avoided. However certain criteria must be in place to make sure the business case for investing in the SteelHead appliances are not jeopardized before such recommendation can be made. Below definitions shows these criteria for traffic reduction (volume/high datastore utilization) and Traffic connection (high optimized connections utilization).
Traffic reduction
This table contains sites with a critical datastore usage, protocols with no layer 7 optimization options, reduction below 10% and optimized traffic amount above 5%. It is recommended to pass through these protocols. This check ensures the effectiveness of the SteelHead installation, and signal if resources are being wasted or over consumed.
Site
Pro
tocol
Port
Reductio
n (%
)
Tra
ffic a
mount
(%)
Tra
ffic a
mount
(GB)
STEELHEAD02 Unknown 55158 0 5.9 30.6
STEELHEAD04 Unknown 57991 0 54.4 112
STEELHEAD15 Unknown 62381 0 14.5 72
Unknown 49582 0 10.2 50.6
Unknown 64102 0 8.4 41.5
STEELHEAD18 Unknown 57057 0 10.3 67.9
STEELHEAD22 Unknown 58679 0 12.2 61
Percentage passthrough traffic
The following sites have a large amount of passthrough traffic. This might be due to passthrough rules or because of sites with no SteelHead connecting to servers on the site listed, and therefore it might be intentional.
STEELHEAD03 - 86.7% STEELHEAD19 - 75.3%
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 10 of 69
August 7th 2014
Traffic connections
The following sites have either been in admission control or have a high load on optimized connections. The load is more than 2% of all optimized connections, less than 10% reduction, the traffic amount is less than 5%, and there is no layer 7 optimization option. It is recommended to passthrough this traffic, to prevent the SteelHead from going in admission control.
This check (as the Traffic reduction check) ensures the effectiveness of the SteelHead installation, and signal if resources are being wasted or over consumed.
Site
Pro
tocol
Port
Connectio
ns
Connectio
n %
Reductio
n (%
)
Tra
ffic a
mount (%
) STEELHEAD02 Unknown 64356 6114 4.5 0.0 1.2
STEELHEAD02 Unknown 63113 2892 2.1 0.0 0.0
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 11 of 69
August 7th 2014
Sizing recommendations
All upgrade recommendations are considered with the current traffic profile and load in mind as seen in the report period. Any change in reduction and pass-through traffic will change these recommendations. The Riverbed recommended optimal value for data store wrap time is 30 days. With the current traffic characteristics, the below upgrades would be recommended. Only the latest series of SteelHeads are considered as a replacement in this report.
STEELHEAD02 A SteelHead 1050L has a datastore of 100 GB, and can manage 800 optimized connections and an optimized bandwidth of 8 Mbps. This SteelHead has used 241.1% of its datastore in the report period. (Calculated as a 30 day average) This means that the datastore wraps once every 12.4 days. The SteelHead has been in Admission Control for 12.18% during business hours. A SteelHead CX1555L with a datastore of 400GB, which can manage 3000 optimized connections and 50.00 Mbit of optimized traffic, is recommended for this site.
STEELHEAD04 A SteelHead 550M has a datastore of 80 GB, and can manage 300 optimized connections and an optimized bandwidth of 2 Mbps. This SteelHead has used 160.2% of its datastore in the report period. (Calculated as a 30 day average) This means that the datastore wraps once every 18.7 days. A SteelHead CX770L with a datastore of 150GB, which can manage 900 optimized connections and 10.00 Mbit of optimized traffic, is recommended for this site.
STEELHEAD05 A SteelHead 1050L has a datastore of 100 GB, and can manage 800 optimized connections and an optimized bandwidth of 8 Mbps. This SteelHead has used 109.8% of its datastore in the report period. (Calculated as a 30 day average) This means that the datastore wraps once every 27.3 days.
A SteelHead CX770L with a datastore of 150GB, which can manage 900 optimized connections and 10.00 Mbit of optimized traffic, is recommended for this site.
STEELHEAD06 A SteelHead 550M has a datastore of 80 GB, and can manage 300 optimized connections and an optimized bandwidth of 2 Mbps.
This SteelHead has used 114.7% of its datastore in the report period. (Calculated as a 30 day average) This means that the datastore wraps once every 26.2 days. A SteelHead CX770L with a datastore of 150GB, which can manage 900 optimized connections and 10.00 Mbit of optimized traffic, is recommended for this site.
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 12 of 69
August 7th 2014
STEELHEAD08 A SteelHead 550H has a datastore of 80 GB, and can manage 600 optimized connections and an
optimized bandwidth of 4 Mbps. This SteelHead has used 182.4% of its datastore in the report period. (Calculated as a 30 day average) This means that the datastore wraps once every 16.4 days. A SteelHead CX770L with a datastore of 150GB, which can manage 900 optimized connections and 10.00 Mbit of optimized traffic, is recommended for this site.
STEELHEAD09 A SteelHead 2050M has a datastore of 400 GB, and can manage 4000 optimized connections and an optimized bandwidth of 45.00 Mbps. This SteelHead has used 320.7% of its datastore in the report period. (Calculated as a 30 day average) This means that the datastore wraps once every 9.4 days.
A SteelHead CX7055L with a datastore of 1638GB, which can manage 75000 optimized connections and 622.00 Mbit of optimized traffic, is recommended for this site.
STEELHEAD10 A SteelHead 5050L has a datastore of 600 GB, and can manage 7500 optimized connections and an optimized bandwidth of 90.00 Mbps.
This SteelHead has used 223.8% of its datastore in the report period. (Calculated as a 30 day average) This means that the datastore wraps once every 13.4 days. A SteelHead CX7055L with a datastore of 1638GB, which can manage 75000 optimized connections and 622.00 Mbit of optimized traffic, is recommended for this site.
STEELHEAD11 A SteelHead 1050L has a datastore of 100 GB, and can manage 800 optimized connections and an optimized bandwidth of 8 Mbps. This SteelHead has used 172.5% of its datastore in the report period. (Calculated as a 30 day average) This means that the datastore wraps once every 17.4 days. A SteelHead CX1555L with a datastore of 400GB, which can manage 3000 optimized connections and 50.00 Mbit of optimized traffic, is recommended for this site.
STEELHEAD13 A SteelHead 550M has a datastore of 80 GB, and can manage 300 optimized connections and an optimized bandwidth of 2 Mbps. This SteelHead has used 208.2% of its datastore in the report period. (Calculated as a 30 day average) This means that the datastore wraps once every 14.4 days. A SteelHead CX1555L with a datastore of 400GB, which can manage 3000 optimized connections and 50.00 Mbit of optimized traffic, is recommended for this site.
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 13 of 69
August 7th 2014
STEELHEAD15 A SteelHead 1050L has a datastore of 100 GB, and can manage 800 optimized connections and an
optimized bandwidth of 8 Mbps. This SteelHead has used 286.3% of its datastore in the report period. (Calculated as a 30 day average) This means that the datastore wraps once every 10.5 days. A SteelHead CX1555L with a datastore of 400GB, which can manage 3000 optimized connections and 50.00 Mbit of optimized traffic, is recommended for this site.
STEELHEAD17 A SteelHead 550H has a datastore of 80 GB, and can manage 600 optimized connections and an optimized bandwidth of 4 Mbps. This SteelHead has used 110.1% of its datastore in the report period. (Calculated as a 30 day average) This means that the datastore wraps once every 27.2 days.
A SteelHead CX770L with a datastore of 150GB, which can manage 900 optimized connections and 10.00 Mbit of optimized traffic, is recommended for this site.
STEELHEAD18 A SteelHead 1050M has a datastore of 100 GB, and can manage 1300 optimized connections and an optimized bandwidth of 10 Mbps.
This SteelHead has used 171% of its datastore in the report period. (Calculated as a 30 day average) This means that the datastore wraps once every 17.5 days. A SteelHead CX1555L with a datastore of 400GB, which can manage 3000 optimized connections and 50.00 Mbit of optimized traffic, is recommended for this site.
STEELHEAD20 A SteelHead 550H has a datastore of 80 GB, and can manage 600 optimized connections and an optimized bandwidth of 4 Mbps. This SteelHead has used 111.4% of its datastore in the report period. (Calculated as a 30 day average) This means that the datastore wraps once every 26.9 days. A SteelHead CX770L with a datastore of 150GB, which can manage 900 optimized connections and 10.00 Mbit of optimized traffic, is recommended for this site.
STEELHEAD22 A SteelHead 550M has a datastore of 80 GB, and can manage 300 optimized connections and an optimized bandwidth of 2 Mbps. This SteelHead has used 154.8% of its datastore in the report period. (Calculated as a 30 day average) This means that the datastore wraps once every 19.4 days. A SteelHead CX770L with a datastore of 150GB, which can manage 900 optimized connections and 10.00 Mbit of optimized traffic, is recommended for this site.
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 14 of 69
August 7th 2014
STEELHEAD23 A SteelHead 550H has a datastore of 80 GB, and can manage 600 optimized connections and an
optimized bandwidth of 4 Mbps. This SteelHead has used 104.3% of its datastore in the report period. (Calculated as a 30 day average) This means that the datastore wraps once every 28.8 days. A SteelHead CX770L with a datastore of 150GB, which can manage 900 optimized connections and 10.00 Mbit of optimized traffic, is recommended for this site.
STEELHEAD24 A SteelHead 1050M has a datastore of 100 GB, and can manage 1300 optimized connections and an optimized bandwidth of 10 Mbps. This SteelHead has used 207.2% of its datastore in the report period. (Calculated as a 30 day average) This means that the datastore wraps once every 14.5 days.
A SteelHead CX1555L with a datastore of 400GB, which can manage 3000 optimized connections and 50.00 Mbit of optimized traffic, is recommended for this site.
STEELHEAD25 A SteelHead 1050H has a datastore of 200 GB, and can manage 2300 optimized connections and an optimized bandwidth of 20 Mbps.
This SteelHead has used 311.8% of its datastore in the report period. (Calculated as a 30 day average) This means that the datastore wraps once every 9.6 days. A SteelHead CX5055M with a datastore of 640GB, which can manage 14000 optimized connections and 200.00 Mbit of optimized traffic, is recommended for this site.
STEELHEAD27 A SteelHead 1050M has a datastore of 100 GB, and can manage 1300 optimized connections and an optimized bandwidth of 10 Mbps. This SteelHead has used 422% of its datastore in the report period. (Calculated as a 30 day average) This means that the datastore wraps once every 7.1 days. A SteelHead CX5055M with a datastore of 640GB, which can manage 14000 optimized connections and 200.00 Mbit of optimized traffic, is recommended for this site.
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 15 of 69
August 7th 2014
Global
Traffic totals
The pie charts illustrate the numerical proportion on the top 10 optimized protocols. The bottom shows the total amount of optimized traffic. The bar charts illustrate the reduction on the protocols. The bottom shows the overall reduction. The first set is created by traffic amount, and the second is created by amount of unique optimized connections. The intention with this overview is to provide documentation on the Global Traffic profile which can be used to high-light protocols that could be subjects for a change in traffic profile on a Global level, if there are steelheads (and in particular DC SteelHeads) that suffers from overutilization on datastore and optimized connections*.
*E.G. if the DC SteelHead appliances were suffering from high pressure on the number of optimized sessions and possibly going into admission control (reaching the license maximum of handling optimized connections and therefore bypassing connections without optimization) it could be considered to change the global traffic profile by passing through applications where optimization has little or no value (eg. LDAP connections). This will offload the DC SteelHead appliances and further optimization could be achieved on the business critical applications and at the same time a costly upgrade of the DC SteelHead appliances can be postponed or even avoided.
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 16 of 69
August 7th 2014
Traffic volume
The following charts shows the overall optimized and pass-through traffic for all sites monitored. The table shows the total traffic reduction for all traffic, including pass-through traffic.
The intention with this overview is to provide documentation and trending on the split between optimized and passthrough (non-optimized) traffic on a Global level and hereby achieve an understanding of how much benefit the steelhead appliances add to overall reduction in data
volume sent over the WAN. The trending will high-light abnormal change in the split between optimized versus passthrough traffic. At the same time it will pinpoint, on a global level, if the amount of passthrough traffic is significant enough to justify further analysis in order to understand if more applications could be added to the optimization.
This graph shows the total amount of LAN and WAN traffic including passthrough traffic by month.
Month Jul. 13
Aug. 13
Oct. 13
Oct. 13
Dec. 13
Jan. 14
Feb. 14
Mar. 14
Apr. 14
May. 14
Jun. 14
Jul. 14
Reduction - - - - - - - - - - 38.3% 46.9%
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 17 of 69
August 7th 2014
Global Top 3 Servers by top 10 most used protocols
In a clear tabular form this section will help to identify the global load on the SteelHead environment by traffic volume and by connections for the top three servers and by the top ten protocols. This provides a clear picture of the consumption of SteelHead capacity globally supporting protocol decisions based on business value and an efficient means of identifying the servers (and applications) generating the unknown protocols so that they can be readily identified as a part of the decision making process (whether to optimize or not, based on business value). It also supports decision making based on business benefit, so a protocol (e.g. LDAP) may have good data reduction but could consume a disproportionately high quantity of valuable TCP connections based on the business value delivered which could be better utilized.
Protocols by traffic volume
Pro
tocol
Tota
l GB
Most u
sed s
erv
er
2nd m
ost u
sed s
erv
er
3rd
most u
sed s
erv
er
Tota
l num
ber o
f dst
serv
ers
CIFS:NetBIOS(139) 18031.7 10.45.10.233 10.1.40.179 10.86.0.231 408
CIFS:TCP(445) 6690.2 10.45.7.104 10.8.1.46 10.86.0.26 >1000
SQL:TDS(1433) 1596.1 10.8.1.73 10.45.7.51 10.86.0.215 49
MAPI(7830) 1404.2 10.45.10.207 10.1.43.30 10.86.0.177 12
HTTP(80) 1121.3 10.1.41.249 10.45.10.97 10.45.7.149 >1000
Exchange DAG Replication(64327) 1061.8 10.86.0.159 10.45.10.155 2
Unknown(55082) 823.1 10.45.10.109 10.45.10.86 10.45.10.89 14
scotty-ft(14000) 693.6 10.45.7.99 10.86.0.110 10.8.1.110 4
Unknown(58174) 401.4 10.61.0.20 1
VxPBX Symantec Private Branch Exchange Service(1556)
380.7 10.61.0.16 10.86.0.159 10.64.0.16 248
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 18 of 69
August 7th 2014
Protocols by connections
Pro
tocol
Tota
l uniq
ue
connectio
ns
Most u
sed s
erv
er
2nd m
ost u
sed s
erv
er
3rd
most u
sed s
erv
er
Tota
l num
ber o
f dst
serv
ers
HTTP(80) 1488325 10.45.7.146 10.45.10.233 10.45.10.97 >1000
CIFS:TCP(445) 939949 10.45.7.104 10.8.1.45 10.45.7.72 >1000
EPM(135) 860076 10.86.0.159 10.45.10.151 10.45.10.207 499
Unknown(8084) 435387 10.86.0.180 10.45.10.92 10.8.1.90 3
MAPI(7830) 427860 10.45.10.207 10.45.10.151 10.86.0.177 12
Unknown(56000) 404263 10.45.10.207 10.45.10.151 10.86.0.177 8
SQL:TDS(1433) 245692 10.8.1.82 10.86.0.215 10.86.0.66 49
Unknown(56001) 199133 10.86.0.159 10.45.10.151 10.45.10.155 5
Unknown(55082) 198178 10.45.10.89 10.45.10.109 10.45.10.86 14
webcache(8080) 147274 10.45.10.98 10.45.7.194 10.45.10.96 167
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 19 of 69
August 7th 2014
Global Network and Application Performance
The Global Network Application Performance (GNAP) reporting will highlight the most common applications that could be performance optimized. A key to the efficient delivery of applications over the WAN is the optimization of latency at layer 7 as this can lead to enhanced productivity over the WAN. This helps identify, justify and prioritize investment in engineering changes and SteelHead configuration changes needed to implement latency optimization.
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 20 of 69
August 7th 2014
Site specific statistics
SteelHead general
This dash board overview provides information on the general health and status of the SteelHead environment and thereby either confirms everything is a satisfactory level and if not the traffic light system will pin point the SteelHeads that are subject for further investigation.
Site
Model
Softw
are
vers
ion
Gate
way u
p (%
)
Ste
elH
ead u
p (%
)
Health
y (%
)
Degra
ded (%
)
Adm
issio
n c
ontro
l (%)
Critic
al (%
)
STEELHEAD01 550H 8.6.0a 100.0 100.0 100.0 0.0 0.0 0.0
STEELHEAD02 1050L 8.6.0a 99.6 100.0 97.1 0.0 12.2 0.0
STEELHEAD03 550H 8.6.0a 98.6 99.9 100.0 0.0 0.0 0.0
STEELHEAD04 550M 8.6.0a 99.2 100.0 99.9 0.0 0.4 0.0
STEELHEAD05 1050L 8.6.0a 99.9 100.0 100.0 0.0 0.0 0.0
STEELHEAD06 550M 8.6.0a 100.0 100.0 100.0 0.0 0.0 0.0
STEELHEAD07 550M 8.6.0a 99.7 100.0 99.7 0.0 1.3 0.0
STEELHEAD08 550H 8.6.0a 98.8 100.0 99.9 0.0 0.4 0.0
STEELHEAD09 2050M 8.6.0a 99.9 100.0 99.9 0.1 0.0 0.0
STEELHEAD10 5050L 8.6.0a 100.0 100.0 100.0 0.0 0.0 0.0
STEELHEAD11 1050L 8.6.0a 100.0 100.0 100.0 0.0 0.0 0.0
STEELHEAD12 550H 8.6.0a 100.0 100.0 100.0 0.0 0.0 0.0
STEELHEAD13 550M 8.6.0a 100.0 100.0 100.0 0.0 0.0 0.0
STEELHEAD14 550M 8.6.0a 100.0 100.0 100.0 0.0 0.0 0.0
STEELHEAD15 1050L 8.6.0a 99.5 100.0 100.0 0.0 0.0 0.0
STEELHEAD16 550M 8.6.0a 100.0 100.0 100.0 0.0 0.0 0.0
STEELHEAD17 550H 8.6.0a 100.0 100.0 100.0 0.0 0.0 0.0
STEELHEAD18 1050M 8.6.0a 100.0 100.0 100.0 0.0 0.0 0.0
STEELHEAD19 CX755L 8.6.0a 99.8 100.0 100.0 0.0 0.0 0.0
STEELHEAD20 550H 8.6.0a 99.8 100.0 100.0 0.0 0.0 0.0
STEELHEAD21 550H 8.6.0a 100.0 100.0 100.0 0.0 0.0 0.0
STEELHEAD22 550M 8.6.0a 99.9 100.0 100.0 0.0 0.0 0.0
STEELHEAD23 550H 8.6.0a 100.0 100.0 100.0 0.0 0.0 0.0
STEELHEAD24 1050M 8.6.0a 100.0 100.0 100.0 0.0 0.0 0.0
STEELHEAD25 1050H 8.6.0a 100.0 100.0 100.0 0.0 0.0 0.0
STEELHEAD26 1050L 8.6.0a 99.8 100.0 100.0 0.0 0.0 0.0
STEELHEAD27 1050M 8.6.0a 99.7 99.7 99.9 0.1 0.0 0.0
STEELHEAD28 550M 8.6.0a 100.0 100.0 100.0 0.0 0.0 0.0
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 21 of 69
August 7th 2014
SteelHead sizing
This dash board provides both an overview as well as trending information on the SteelHeads key license limitations versus current utilization. The traffic light system highlights if any limitations are close to the limit (Yellow) or has reached the limit (Red). Informed decisions can be made either to change the traffic profile (Freeing up valuable optimized sessions and datastore capacity) or to upgrade the SteelHead in order to regain optimal application delivery over the WAN.
Optimized connections is a key variable, if the maximum license limit is met then every connection over and above the licenses limit will be passed through and have no WAN optimization. Understanding the Datastore utilization is important to ensure the business case is met. If the SteelHead datastore exceeds the maximum capacity it will start to over-write data resulting in more data volume sent over the WAN as well as decreased performance on application delivery.
Site Model Datastore usage (% 30 day avg.)
Optimized Connections (%)
Outbound Bandwidth (%)
STEELHEAD01 550H
STEELHEAD02 1050L
STEELHEAD03 550H
STEELHEAD04 550M
STEELHEAD05 1050L
STEELHEAD06 550M
STEELHEAD07 550M
STEELHEAD08 550H
STEELHEAD09 2050M
STEELHEAD10 5050L
STEELHEAD11 1050L
STEELHEAD12 550H
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 22 of 69
August 7th 2014
Site Model Datastore usage (% 30 day avg.)
Optimized Connections (%)
Outbound Bandwidth (%)
STEELHEAD13 550M
STEELHEAD14 550M
STEELHEAD15 1050L
STEELHEAD16 550M
STEELHEAD17 550H
STEELHEAD18 1050M
STEELHEAD19 CX755L
STEELHEAD20 550H
STEELHEAD21 550H
STEELHEAD22 550M
STEELHEAD23 550H
STEELHEAD24 1050M
STEELHEAD25 1050H
STEELHEAD26 1050L
STEELHEAD27 1050M
STEELHEAD28 550M
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 23 of 69
August 7th 2014
SteelHead traffic volume
This dash board supports decisions and understanding for WAN optimization delivery versus strategy and will help prioritize further investigation and actions in a simple to understand traffic-light system. The overview provides the information needed for understanding if the SteelHeads are optimizing at an overall satisfactory level. In the same overview the most used protocols by volume (top three) are being highlighted if they are not optimized as what could be expected.
Site
Avg s
ite re
ductio
n (%
)
Optim
ized tra
ffic (%
)
Passth
rough tra
ffic (%
)
Most u
sed p
roto
col n
am
e
Most u
sed p
roto
col
reductio
n (%
)
2nd m
ost u
sed p
roto
col
nam
e
2nd m
ost u
sed p
roto
col
reductio
n (%
)
3rd
most u
sed p
roto
col
nam
e
3rd
most u
sed p
roto
col
reductio
n (%
)
STEELHEAD01 70.2 70.7 29.3 CIFS:TCP (445) 71.5 scotty-ft (14000) 60.0 HTTP (80) 83.1
STEELHEAD02 49.5 84.6 15.4 Unknown (58174) 17.4 VxPBX Symantec Private Branch Exchange Service (1556)
97.3 CIFS:TCP (445) 82.2
STEELHEAD03 68.0 13.3 86.7 MAPI (7830) 71.7 HTTP (80) 86.6 Citrix (1494) 50.6
STEELHEAD04 29.8 72.2 27.8 Unknown (57991) 0.0 CIFS:NetBIOS (139)
85.1 CIFS:TCP (445) 59.1
STEELHEAD05 83.7 86.1 13.9 CIFS:NetBIOS (139)
87.5 CIFS:TCP (445) 81.2 MAPI (7830) 82.4
STEELHEAD06 82.1 90.8 9.2 CIFS:NetBIOS (139)
82.4 CIFS:TCP (445) 84.5 scotty-ft (14000) 53.1
STEELHEAD07 82.8 98.1 1.9 CIFS:NetBIOS (139)
90.7 HTTP (80) 31.5 CIFS:TCP (445) 25.4
STEELHEAD08 71.6 97.5 2.5 CIFS:NetBIOS (139)
85.1 HTTP (80) 29.1 CIFS:TCP (445) 63.8
STEELHEAD09 65.8 71.6 28.4 CIFS:NetBIOS (139)
81.5 CIFS:TCP (445) 82.4 Exchange DAG Replication (64327)
76.1
STEELHEAD10 78.6 54.2 45.8 CIFS:NetBIOS (139)
82.4 CIFS:TCP (445) 81.4 SQL:TDS (1433) 88.6
STEELHEAD11 77.3 83.6 16.4 CIFS:NetBIOS (139)
76.5 HTTP (80) 93.9 CIFS:TCP (445) 60.5
STEELHEAD12 44.6 74.9 25.1 CIFS:TCP (445) 56.2 webcache (8080) 21.3 scotty-ft (14000) 58.2
STEELHEAD13 79.8 93.4 6.6 CIFS:NetBIOS (139)
75.0 Unknown (55082) 93.5 CIFS:TCP (445) 64.4
STEELHEAD14 88.0 90.8 9.2 CIFS:NetBIOS (139)
88.0 MAPI (7830) 94.7 CIFS:TCP (445) 60.8
STEELHEAD15 35.1 84.7 15.3 CIFS:NetBIOS (139)
57.6 Unknown (62381) 0.0 Unknown (49582) 0.0
STEELHEAD16 83.4 95.2 4.8 CIFS:NetBIOS (139)
84.3 CIFS:TCP (445) 36.1 MAPI (7830) 57.2
STEELHEAD17 82.3 68.8 31.2 CIFS:NetBIOS (139)
84.2 CIFS:TCP (445) 80.0 MAPI (7830) 58.2
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 24 of 69
August 7th 2014
Site
Avg s
ite re
ductio
n (%
)
Optim
ized tra
ffic (%
)
Passth
rough tra
ffic (%
)
Most u
sed p
roto
col n
am
e
Most u
sed p
roto
col
reductio
n (%
)
2nd m
ost u
sed p
roto
col
nam
e
2nd m
ost u
sed p
roto
col
reductio
n (%
)
3rd
most u
sed p
roto
col
nam
e
3rd
most u
sed p
roto
col
reductio
n (%
)
STEELHEAD18 70.7 81.8 18.2 CIFS:NetBIOS (139)
82.8 CIFS:TCP (445) 93.1 Unknown (57057) 0.0
STEELHEAD19 76.6 24.7 75.3 CIFS:TCP (445) 81.1 scotty-ft (14000) 76.2 MAPI (7830) 76.7
STEELHEAD20 80.5 76.6 23.4 CIFS:NetBIOS (139)
83.5 CIFS:TCP (445) 55.6 scotty-ft (14000) 74.0
STEELHEAD21 68.6 44.5 55.5 CIFS:TCP (445) 63.5 SQL:TDS (1433) 93.6 MAPI (7830) 57.8
STEELHEAD22 72.5 94.4 5.6 CIFS:NetBIOS (139)
85.6 Unknown (58679) 0.0 CIFS:TCP (445) 81.9
STEELHEAD23 82.7 96.7 3.3 CIFS:NetBIOS (139)
83.8 CIFS:TCP (445) 47.7 scotty-ft (14000) 56.3
STEELHEAD24 71.2 83.1 16.9 CIFS:TCP (445) 65.9 CIFS:NetBIOS (139)
76.2 SQL:TDS (1433) 93.2
STEELHEAD25 83.4 67.1 32.9 CIFS:NetBIOS (139)
91.7 CIFS:TCP (445) 88.6 SQL:TDS (1433) 86.2
STEELHEAD26 88.0 60.1 39.9 CIFS:NetBIOS (139)
90.8 CIFS:TCP (445) 92.9 netview-aix-7 (1667)
92.6
STEELHEAD27 87.4 64.1 35.9 CIFS:NetBIOS (139)
91.9 CIFS:TCP (445) 88.9 MAPI (7830) 43.6
STEELHEAD28 87.5 81.2 18.9 CIFS:TCP (445) 88.9 netview-aix-7 (1667)
92.6 scotty-ft (14000) 26.8
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 25 of 69
August 7th 2014
SteelHead connections
This dash board provides a summary of the connection pressure apparent in the top three protocols. This will support the business case for potentially passing through unknown and poorly optimized protocols if a SteelHead is experiencing connection pressure (admission control).
Site
Most u
sed p
roto
col
Connectio
ns
Most u
sed p
roto
col
reductio
n (%
)
2nd m
ost u
sed p
roto
col
Connectio
ns
2nd m
ost u
sed p
roto
col
reductio
n (%
)
3rd
most u
sed p
roto
col
Connectio
ns
3rd
most u
sed p
roto
col
reductio
n (%
)
STEELHEAD01 CIFS:TCP (445) 8990 71.5 Unknown (55082) 7142 68.5 Unknown (55493) 5391 57.3
STEELHEAD02 HTTP (80) 31237 80.2 Unknown (58174) 29598 17.4 EPM (135) 13672 12.4
STEELHEAD03 MAPI (7830) 30969 71.7 EPM (135) 15073 11.1 HTTP (80) 11666 86.6
STEELHEAD04 EPM (135) 19859 15.8 Unknown (57991) 17448 0.0 CIFS:TCP (445) 10796 59.1
STEELHEAD05 HTTP (80) 77053 76.4 CIFS:TCP (445) 18770 81.2 MAPI (7830) 11795 82.4
STEELHEAD06 Unknown (55082) 7260 75.6 CIFS:TCP (445) 6029 84.5 HTTP (80) 4031 51.6
STEELHEAD07 HTTP (80) 93548 31.5 CIFS:TCP (445) 3736 25.4 MAPI (7830) 2803 60.9
STEELHEAD08 HTTP (80) 240209 29.1 CIFS:TCP (445) 11519 63.8 MAPI (7830) 9893 80.6
STEELHEAD09 HTTP (80) 229461 65.4 EPM (135) 207098 38.2 Unknown (8084) 182764 12.8
STEELHEAD10 HTTP (80) 453164 87.2 CIFS:TCP (445) 344863 81.4 Unknown (56000) 320841 27.2
STEELHEAD11 CIFS:TCP (445) 47821 60.5 HTTP (80) 32356 93.9 Unknown (55082) 28462 77.2
STEELHEAD12 webcache (8080) 27327 21.3 HTTP (80) 4247 75.3 CIFS:TCP (445) 3268 56.2
STEELHEAD13 Unknown (55082) 33959 93.5 CIFS:TCP (445) 24128 64.4 Unknown (55493) 14239 59.0
STEELHEAD14 HTTP (80) 8704 71.0 CIFS:TCP (445) 2527 60.8 MAPI (7830) 1471 94.7
STEELHEAD15 MAPI (7830) 12408 62.5 CIFS:NetBIOS (139)
9085 57.6 Unknown (64102) 8515 0.0
STEELHEAD16 HTTP (80) 13539 70.0 CIFS:TCP (445) 2661 36.1 MAPI (7830) 2121 57.2
STEELHEAD17 HTTP (80) 33414 78.1 CIFS:TCP (445) 15951 80.0 MAPI (7830) 11911 58.2
STEELHEAD18 MAPI (7830) 38247 65.0 HTTP (80) 37200 66.0 EPM (135) 16698 7.2
STEELHEAD19 MAPI (7830) 14188 76.7 CIFS:TCP (445) 13570 81.1 HTTP (80) 11724 83.0
STEELHEAD20 CIFS:TCP (445) 17217 55.6 HTTP (80) 11022 75.5 Unknown (55082) 10289 79.0
STEELHEAD21 CIFS:TCP (445) 12502 63.5 Unknown (55082) 5427 78.6 MAPI (7830) 4159 57.8
STEELHEAD22 Unknown (58679) 11267 0.0 HTTP (80) 10108 68.6 EPM (135) 7887 2.1
STEELHEAD23 CIFS:TCP (445) 6353 47.7 Unknown (55082) 4270 75.3 HTTP (80) 3389 69.6
STEELHEAD24 CIFS:TCP (445) 104360 65.9 HTTP (80) 68265 81.2 MAPI (7830) 23467 64.1
STEELHEAD25 EPM (135) 132659 11.4 CIFS:TCP (445) 132371 88.6 HTTP (80) 109960 90.5
STEELHEAD26 CIFS:TCP (445) 16647 92.9 MAPI (7830) 15765 41.3 HTTP (80) 13097 72.7
STEELHEAD27 HTTP (80) 82413 77.3 EPM (135) 71890 7.6 CIFS:TCP (445) 71469 88.9
STEELHEAD28 HTTP (80) 8242 84.2 CIFS:TCP (445) 4660 88.9 EPM (135) 2121 2.7
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 26 of 69
August 7th 2014
SteelHead specific
These two page detailed summaries of each SteelHead in the environment provide a granular view of each SteelHead being monitored over the reporting period. The view includes key variables that impact SteelHead performance and business case including the top 10 ten protocols by volume, connections and data reduction efficiency.
A good example of this is when the top three protocols are being optimized effectively but there is pressure on either connections (admission control) or datastore. This section will help make decisions about whether collectively protocols that sit outside of the top 3, should be optimized or passed through and the cumulative benefits of this on the pressure that is being experienced by the SteelHead.
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 27 of 69
August 7th 2014
STEELHEAD01
550H
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 28 of 69
August 7th 2014
STEELHEAD02
1050L
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 29 of 69
August 7th 2014
STEELHEAD03
550H
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 30 of 69
August 7th 2014
STEELHEAD04
550M
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 31 of 69
August 7th 2014
STEELHEAD05
1050L
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 32 of 69
August 7th 2014
STEELHEAD06
550M
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 33 of 69
August 7th 2014
STEELHEAD07
550M
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 34 of 69
August 7th 2014
STEELHEAD08
550H
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 35 of 69
August 7th 2014
STEELHEAD09
2050M
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 36 of 69
August 7th 2014
STEELHEAD10
5050L
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 37 of 69
August 7th 2014
STEELHEAD11
1050L
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 38 of 69
August 7th 2014
STEELHEAD12
550H
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 39 of 69
August 7th 2014
STEELHEAD13
550M
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 40 of 69
August 7th 2014
STEELHEAD14
550M
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 41 of 69
August 7th 2014
STEELHEAD15
1050L
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 42 of 69
August 7th 2014
STEELHEAD16
550M
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 43 of 69
August 7th 2014
STEELHEAD17
550H
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 44 of 69
August 7th 2014
STEELHEAD18
1050M
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 45 of 69
August 7th 2014
STEELHEAD19
CX755L
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 46 of 69
August 7th 2014
STEELHEAD20
550H
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 47 of 69
August 7th 2014
STEELHEAD21
550H
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 48 of 69
August 7th 2014
STEELHEAD22
550M
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 49 of 69
August 7th 2014
STEELHEAD23
550H
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 50 of 69
August 7th 2014
STEELHEAD24
1050M
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 51 of 69
August 7th 2014
STEELHEAD25
1050H
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 52 of 69
August 7th 2014
STEELHEAD26
1050L
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 53 of 69
August 7th 2014
STEELHEAD27
1050M
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 54 of 69
August 7th 2014
STEELHEAD28
550M
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 55 of 69
August 7th 2014
Appendix
SteelHead models
SteelHead CX-series
SteelHead CX 255
CX255U CX255L CX255M CX255H
Connections optimized 50 75 150 230
Datastore (GB) 50 50 50 50
Optimized WAN bandwidth (Mbit) 2.00 6.00 6.00 6.00
SteelHead CX 555
CX555L CX555M CX555H
Connections optimized 250 400 650
Datastore (GB) 80 80 80
Optimized WAN bandwidth (Mbit) 6.00 10.00 10.00
SteelHead CX 570
CX570L CX570M CX570H
Connections optimized 250 400 650
Datastore (GB) 70 70 70
Optimized WAN bandwidth (Mbit) 6.00 10.00 10.00
SteelHead CX 755
CX755L CX755M CX755H
Connections optimized 900 1500 2300
Datastore (GB) 100 100 160
Optimized WAN bandwidth (Mbit) 10.00 10.00 20.00
SteelHead CX 770
CX770L CX770M CX770H
Connections optimized 900 1500 2300
Datastore (GB) 150 150 150
Optimized WAN bandwidth (Mbit) 10.00 10.00 20.00
SteelHead CX 1555
CX1555L CX1555M CX1555H
Connections optimized 3000 4500 6000
Datastore (GB) 400 400 320
Optimized WAN bandwidth (Mbit) 50.00 50.00 100.00
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 56 of 69
August 7th 2014
SteelHead CX 5055
CX5055M CX5055H
Connections optimized 14000 25000
Datastore (GB) 640 640
Optimized WAN bandwidth (Mbit) 200.00 400.00
SteelHead CX 7055
CX7055L CX7055M CX7055H
Connections optimized 75000 100000 150000
Datastore (GB) 1638 2457 4915
Optimized WAN bandwidth (Mbit) 622.00 1000.00 1500.00
SteelHead virtual CX-series
SteelHead Virtual CX 255
VCX255U VCX255L VCX255M VCX255H
Connections optimized 50 75 150 230
Datastore (GB) 50 50 50 50
Optimized WAN bandwidth (Mbit) 2.00 6.00 6.00 6.00
SteelHead Virtual CX 555
VCX555L VCX555M VCX555H
Connections optimized 250 400 650
Datastore (GB) 80 80 80
Optimized WAN bandwidth (Mbit) 6.00 10.00 10.00
SteelHead Virtual CX 570
VCX570L VCX570M VCX570H
Connections optimized 250 400 650
Datastore (GB) 80 80 80
Optimized WAN bandwidth (Mbit) 6.00 10.00 10.00
SteelHead Virtual CX 755
VCX755L VCX755M VCX755H
Connections optimized 900 1500 2300
Datastore (GB) 102 102 150
Optimized WAN bandwidth (Mbit) 10.00 10.00 20.00
SteelHead Virtual CX 770
VCX770L VCX770M VCX770H
Connections optimized 900 1500 2300
Datastore (GB) 100 100 160
Optimized WAN bandwidth (Mbit) 10.00 10.00 20.00
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 57 of 69
August 7th 2014
SteelHead Virtual CX 1555
VCX1555L VCX1555M VCX1555H
Connections optimized 3000 4500 6000
Datastore (GB) 400 400 400
Optimized WAN bandwidth (Mbit) 50.00 50.00 100.00
SteelHead Virtual CX 5055
VCX5055M VCX5055H
Connections optimized 14000 25000
Datastore (GB) 640 640
Optimized WAN bandwidth (Mbit) 200.00 400.00
SteelHead Virtual CX 7055
VCX7055L VCX7055M VCX7055H
Connections optimized 75000 100000 150000
Datastore (GB) 1638 2457 4915
Optimized WAN bandwidth (Mbit) 622.00 1000.00 1500.00
SteelHead EX-series
SteelHead EX 560
EX560L EX560M EX560H
Connections optimized 250 400 650
Datastore (GB) 40 70 70
Optimized WAN bandwidth (Mbit) 6.00 10.00 10.00
SteelHead EX 760
EX760L EX760M EX760H
Connections optimized 900 1500 2300
Datastore (GB) 140 140 140
Optimized WAN bandwidth (Mbit) 10.00 10.00 20.00
SteelHead EX 1160
EX1160L EX1160M EX1160H EX1160VH
Connections optimized 900 1500 2300 6000
Datastore (GB) 140 140 140 280
Optimized WAN bandwidth (Mbit) 10.00 10.00 20.00 50.00
SteelHead EX 1260
EX1260L EX1260M EX1260H EX1260VH
Connections optimized 900 1500 2300 6000
Datastore (GB) 140 140 140 280
Optimized WAN bandwidth (Mbit) 10.00 10.00 20.00 50.00
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 58 of 69
August 7th 2014
SteelHead EX 1360
EX1360L EX1360M
Connections optimized 4500 6000
Datastore (GB) 320 320
Optimized WAN bandwidth (Mbit) 50.00 100.00
SteelHead xx50 series
SteelHead xx50 150
150M
Connections optimized 20
Datastore (GB) 40
Optimized WAN bandwidth (Mbit) 1.00
SteelHead xx50 250
250L 250M 250H
Connections optimized 40 125 200
Datastore (GB) 40 40 40
Optimized WAN bandwidth (Mbit) 1.00 2.00 2.00
SteelHead xx50 550
550M 550H
Connections optimized 300 600
Datastore (GB) 80 80
Optimized WAN bandwidth (Mbit) 2.00 4.00
SteelHead xx50 1050
1050U 1050L 1050M V1050M 1050H
Connections optimized 600 800 1300 1300 2300
Datastore (GB) 100 100 100 100 200
Optimized WAN bandwidth (Mbit) 4.00 8.00 10.00 10.00 20.00
SteelHead xx50 2050
2050L 2050M 2050H
Connections optimized 2500 4000 6000
Datastore (GB) 400 400 400
Optimized WAN bandwidth (Mbit) 45.00 45.00 45.00
SteelHead xx50 5050
5050L 5050M 5050H
Connections optimized 7500 10000 18000
Datastore (GB) 600 600 800
Optimized WAN bandwidth (Mbit) 90.00 90.00 155.00
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 59 of 69
August 7th 2014
SteelHead xx50 6050
6050
Connections optimized 50000
Datastore (GB) 3584
Optimized WAN bandwidth (Mbit) 310.00
SteelHead xx50 7050
7050L 7050M
Connections optimized 75000 100000
Datastore (GB) 2252 4505
Optimized WAN bandwidth (Mbit) 1024.00 1024.00
SteelHead xx20 series
SteelHead xx20 100
100
Connections optimized 25
Datastore (GB) 35
Optimized WAN bandwidth (Mbit) 1.00
SteelHead xx20 200
200
Connections optimized 110
Datastore (GB) 35
Optimized WAN bandwidth (Mbit) 1.00
SteelHead xx20 300
300
Connections optimized 165
Datastore (GB) 35
Optimized WAN bandwidth (Mbit) 2.00
SteelHead xx20 50
50
Connections optimized 250
Datastore (GB) 35
Optimized WAN bandwidth (Mbit) 0.25
SteelHead xx20 520
520
Connections optimized 330
Datastore (GB) 80
Optimized WAN bandwidth (Mbit) 1.00
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 60 of 69
August 7th 2014
SteelHead xx20 1020
1020
Connections optimized 700
Datastore (GB) 80
Optimized WAN bandwidth (Mbit) 2.00
SteelHead xx20 1520
1520
Connections optimized 1100
Datastore (GB) 80
Optimized WAN bandwidth (Mbit) 4.00
SteelHead xx20 2020
2020
Connections optimized 2000
Datastore (GB) 150
Optimized WAN bandwidth (Mbit) 10.00
SteelHead xx20 3020
3020
Connections optimized 3500
Datastore (GB) 250
Optimized WAN bandwidth (Mbit) 20.00
SteelHead xx20 6120
6120
Connections optimized 4000
Datastore (GB) 3481
Optimized WAN bandwidth (Mbit) 310.00
SteelHead xx20 3520
3520
Connections optimized 6000
Datastore (GB) 512
Optimized WAN bandwidth (Mbit) 45.00
SteelHead xx20 5520
5520
Connections optimized 15000
Datastore (GB) 700
Optimized WAN bandwidth (Mbit) 155.00
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 61 of 69
August 7th 2014
SteelHead xx20 6020
6020
Connections optimized 40000
Datastore (GB) 1433
Optimized WAN bandwidth (Mbit) 310.00
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 62 of 69
August 7th 2014
SteelHead Global
Traffic totals
The pie charts are illustrating the numerical proportion on the top 10 optimized protocols. The bottom shows the total amount of optimized traffic. The bar charts are illustrating the reduction on the protocols. The bottom shows the overall reduction.
The first set is created by traffic amount, and the second is created by amount of optimized connections.
Traffic Volume
The charts shows the overall optimized and passthrough traffic for all sites monitored. The table shows the total traffic reduction for all traffic, including passthrough traffic.
Global Top 3 Servers by top 10 most used protocols
These tables show the top 3 destination servers for the top 10 most used protocols. Please be aware that this table might show some "ghost ports" meaning that no destination server
is present for the port. This is because of "ghost ports" added for statistical reasons. Example: SMB2 traffic is shown as traffic on port 8779, even though the traffic runs on port 445 together with SMB1/CIFS. There is one table sorted by traffic amount and one sorted by amount of optimized connections.
Global Network Application Performance
These graphs show the number of occurrences on a monitored event. Every point in the graph represent 1/13 of the period covered. In the top it shows the total number of occurrences found during the report period. The following is a list of monitored events with a short description.
SMB signing errors
This is the amount of CIFS connections with SMB signing seen during the report period. In most cases it is possible to do layer 7 optimization on these connections if the SteelHeads are configured to manage this.
SMB v2 errors
This is the amount of CIFS connections with SMB v2 seen during the report period. It is recommended to configure the SteelHeads to be able to manage this, by enabling SMB v1 backward compatibility, if the network supports this.
Delegation errors
This is the amount of connections with delegation errors seen during the report period. Delegation errors can be seen on both SMB signed and encrypted MAPI connections, and occurs when the delegation user does not have proper delegation rights for the server.
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 63 of 69
August 7th 2014
NFS connections, SDR only
This is the amount of NFS connections with only SDR optimization. In most cases it is possible to do layer 7 optimization on these connections if the SteelHeads are configured to manage this.
Passthrough SSL connections on RFC1918 address space
This is the amount of SSL connections on the RFC1918 address space passed through. It might be
possible to optimize these connections, and it is highly recommended to take action on this issue.
Lotus Notes Connections, SDR only
This is the amount of Lotus Notes connections with only SDR optimization. It is possible to enhance the optimization on these connections, and it is highly recommended to take action on this issue. If Lotus Notes optimization already is enabled, it might be necessary to enable Lotus Notes Pull replication optimization, (CLI only command), to enhance the optimization on this kind of traffic.
Encrypted Lotus Notes
This is the amount of encrypted Lotus Notes connections. It might be possible to optimize these connections, and it is highly recommended to take action on this issue.
Packet ricochet
This is the amount of Packet ricocheting. Packet ricocheting is logged when the same SYN packet is
seen more than once by the SteelHead. Usually actions can be taken to prevent this, by changing the default gateway or enabling simplified routing on the SteelHead. But the SteelHead also logs this as packet ricocheting when a client is trying to reach a server which is offline.
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 64 of 69
August 7th 2014
SteelHead General
Site
The SteelHead hostname.
Model
The SteelHead model monitored.
RiOS version
The RiOS version running on the SteelHead.
Gateway Up
This value indicates how long the default gateway for the remote SteelHead has been reachable. This tells us if the remote ISP is down. In such case both the SteelHead and the default gateway will not be reachable. The gateway information is usually retrieved every 24 hours where the RPAM
agent appliance will logon to the SteelHead and update the information. This means if the gateway changes there might be a 24 hour gap before RPAM is updated.
SteelHead Up
This is a value of how long the SteelHead has been reachable by the RPAM agent. It is just a simple
ping to the SteelHeads Primary port (management) to check if the SteelHead is alive or not. If the SteelHead is gone (e.g. powered off or malfunctioning), the ping monitor will alert that the SteelHead is unreachable. The ping is done from the RPAM agent appliance located in the data centre. If the SteelHead has been unreachable for more than 1% of the report period the cell is yellow. If it has been unreachable for more than 2% the cell is red.
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 65 of 69
August 7th 2014
Healthy
The SteelHead does not see any issues with the optimization, or issues that may arise. Healthy does not mean that there is no performance issue. Examples that the SteelHead does not see as an issue, and consequently will not lower the health status are:
Disk pressure, if the load of the disk system slows traffic down Drop in connection count No peers available No optimized (or very little) traffic
High count of Half-Opened sessions Encrypted traffic (like MAPI or other) SMB signing issues Packet ricochet or routing issues IP configuration failure
There are lots of potential issues based on the values above, that the SteelHead considers minor and is only reported in the logs and not in the health status, some are not even logged in the system log. If the SteelHead has been in another state than healthy for more than 1% of the report period the cell is yellow. More than 2% the cell is red.
Degraded
If a SteelHead is degraded, the SteelHead has one or more currently known issues. If the issues are not resolved it can potentially interfere with the optimization. When the SteelHead is degraded the optimization will continue to operate at normal or close to normal speed. Common issues that will make the SteelHead go into degraded are, but not limited to;
RAID errors SSL certificates that are about to expire or has expired Improper SSL configuration
Asymmetric routing issues Domain problems with PFS and/or SMB signing/MAPI encryption Interface link or duplex errors
It is not critical if a SteelHead is in "degraded", but troubleshooting the SteelHead should start at the next convenient time as the problem might evolve into a critical problem with loss of optimization. If the SteelHead has been in degraded mode for more than 1% of the report period the cell is yellow. More than 2% the cell is red.
Admission Control
Admission control stops the interception of connections for optimization but still allows the connections to pass through with no optimization. This is due to a license limitation in the SteelHead. For example, if a SteelHead 250M has 135 connections through it that may be optimized, only 125 connections will be optimized and the last 10 connections will be passed through un-optimized. The SteelHead will then be in Admission Control, stating that it has reached its software limit. Many SteelHeads can be license upgraded to support more connections. The amount showed is uplifted by 4.2, because we want to show the actual impact, during working hours. (We assume working hours to be 8 hours a day, 5 days a week.)
A value above 4.2% the cell is yellow. And more than 8.4% the cell is red and a recommendation is triggered.
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 66 of 69
August 7th 2014
Critical
Critical mode is the worst mode a SteelHead can be in. In critical mode optimization is severely impacted, or not working at all. Usually when a SteelHead is in critical mode the hardware bypass system is also triggered as the SteelHead could potentially block traffic. If a SteelHead is in critical mode, it is safe to assume that there is no optimization for that particular SteelHead and the problem should be investigated as soon as possible. If the optimization service is manually stopped on a SteelHead it will enter critical mode (because the service is not running) and nothing will be optimized. When the optimization service is restarted, critical mode is entered while the service is
stopped and is trying to start again; this is completely normal and can safely be ignored. If the SteelHead has been in critical mode for more than 1% of the report period the cell is yellow. More than 2% the cell is red.
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 67 of 69
August 7th 2014
SteelHead Sizing
SteelHead Model
Please refer to models in SteelHead General Overview.
Optimized connections
This graph shows the optimized connections in percentage over the entire period. This means that height of the graph is 100% (system automatically calculates 100% depending on model) and the width of the graph is the period (usually 3 months). Since this is the percentage the amount of connections differs among models. If you want the session count please have a look at the specific SteelHead page or the model overview to convert the percentage into actual connections. If 3% or more of the data samples are above 70% of the SteelHeads capabilities, the graph is yellow. If more than 20% of the data samples are above 70% it is red.
Outbound bandwidth
Shows the outbound traffic used for optimized traffic. This amount counts toward the license limit of the unit. As the other graphs the height is 100% (system automatically calculates 100%
depending on model) and the length is the entire period of time (3 month). If 3% or more of the data samples are above 70% of the SteelHeads capabilities, the graph is yellow. If more than 20% of the data samples are above 70% it is red.
Datastore Usage
The value in the graph shows how many bytes have been written to the data store disk over a 30 day average in percentage of the datastore size. This means if you have a data store of 100GB and you write 100GB data to the disk over a period of 30 days it will be 100% meaning that you have used all your capacity the last 30 days and it will then start to overwrite existing data. If you have written 400GB of data during 30 days it will be 400% meaning that it will have flushed (deleted) 300GB of data segments witch needs to be transferred over the WAN again. The general recommendation is to not go beyond 100% during 30 days.
The graph shows the datastore usage in bytes. Each point in the graph represents five minutes.
Percentage of total optimized traffic
The pie chart shows the amount of optimized traffic for the top 10 protocols.
Top 10 application reduction in percent
The bar graph shows the reduction in percent for the top 10 optimized protocols.
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 68 of 69
August 7th 2014
SteelHead Traffic
Avg. Site Reduction
Data reduction is how much all optimized traffic was reduced in percentage over the period. If 10Gig was transferred to the LAN interface and only 5Gig was actually sent over the WAN there will be a 50% reduction. Usually this figure is between 40-80%.
Optimized Traffic
This is the percentage of optimized traffic (before optimization) out of total TCP traffic running though the unit. Optimized + Pass-through traffic should give 100%.
Pass Through Traffic
This is the percentage of Pass-through traffic (non-optimized) out of total TCP traffic running though the unit. Optimized + Pass-through traffic should give 100%.
Most Used Protocol Name
This is the common name of a protocol as defined under the SteelHead in "monitored ports". If the port is not defined it will import the name from the IANA port list. This means that the name of the port might not be the correct one.
Most Used Protocol Reduction
This value is the average reduction for the specific protocol over the entire period. If a protocol has been reduced from 100Gig to 50Gig it will show an average reduction of 50%.
Report
July 3rd 2014 - August 3rd 2014
Customer
Page 69 of 69
August 7th 2014
Site specific statistics
This section shows specifics for each site included in this report. For a description on the sizing graphs please see the SteelHead Sizing section above.
Traffic Volume pie and bar chart
For a description on the pie and bar charts, please see the Global section above.
Traffic connections pie and bar chart
For a description on the pie and bar charts, please see the Global section above.