1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
|
% !TEX root = ../TSG_Administrator's_Guide_Latest_EN.tex
%
%\pdfbookmark[0]{Advanced Setting}{Advanced Setting}
\chapter*{\hypertarget{link:Advanced Setting}{Advanced Setting}}
\addcontentsline{toc}{chapter}{Advanced Setting}
\label{sec:setting}
This section contains information about configuring TSG advanced features, including:
{
\color{linkblue}
\hyperlink{link:Proxy TCP Options}{> Proxy TCP Options} \\
\hyperlink{link:System Usage }{> System Usage } \\
\hyperlink{link:System Appearance }{> System Appearance } \\
}
\clearpage
%\pdfbookmark[1]{Proxy TCP Options}{Proxy TCP Options}
\section*{\hypertarget{link:Proxy TCP Options}{Proxy TCP Options}}
\addcontentsline{toc}{section}{Proxy TCP Options}
\label{sec:setting:tcp}
TSG provides TCP default option, which keeps the Enable TCP Passthrough and Bypass Duplicated Packet off.
However, you can create your Proxy TCP Options for special situations. Under certain boundary conditions of network transmission,
some network parameters need to be renegotiated, such as MTU. The network equipment will renegotiate network parameters through some mechanisms,
and the negotiation process may not be under the precise monitor of TSG. And it may affect related policies.
In this case, the affected network parameters need to be preset through the PROXY TCP OPTION.
\begin{description}
\item[STEP 1.] Select \textbf{Profiles} > \textbf{Proxy} > \textbf{Proxy TCP Options}, and click \textbf{Create}.
\item[STEP 2.] Specify Proxy TCP Options name and effective scope.
\begin{enumerate}
\item Enter a descriptive \textbf{Name}.
\item Specify single or multiple \textbf{Source} IP Addresses/ Subscriber IDs or leave the value set to any.
\item Specify one or multiple \textbf{Destination} IP Addresses or leave the value set to any.
\item (\textcolor{gold}{Optional}) Specify a \textbf{Filter}. For example, add \textbf{SNI} and select a \textbf{Category} or an \textbf{FQDN}. If you select a category, only traffic is destined for that specified category will be effective.
\end{enumerate}
\item[STEP 3.] Enable Proxy TCP Options.
\begin{enumerate}
\item (\textcolor{gold}{Optional})\textbf{Enable TCP Passthrough}. When enabled, traffic will bypass the TSG proxy system but will not be decrypted.
You can enable it when troubleshooting.
\item (\textcolor{gold}{Optional})Enable \textbf{bypass Duplicated Packet}.
\item Specify Client-side Parameters and Server-side Parameters, respectively. They have the same options.
\begin{enumerate}
\item (\textcolor{gold}{Optional})Enable \textbf{Override MSS}. The MSS range: 536-1460.
\item (\textcolor{gold}{Optional})Enable \textbf{No Delay}.
\item Specify \textbf{TTL}. The TTL range: 1-255.
\item (\textcolor{gold}{Optional})Enable \textbf{Keepalive}. Specify \textbf{Probe Number}, \textbf{Idle Time}, and \textbf{Interval}.
Probe Number is the maximum number of keepalive probes TCP should send before dropping the connection.
Idle Time is the time (in seconds) the connection needs to remain idle before TCP starts sending keepalive probes
if the socket option SO\_KEEPALIVE has been set on this socket. Interval is the time (in seconds) between individual keepalive probes.
These three options should not be used in code intended to be portable.
\item Define \textbf{User Timeout}. The User Timeout range: 200\-60000.
\end{enumerate}
\item Click \textbf{OK}.
\end{enumerate}
\end{description}
You can \textbf{Edit} or \textbf{Delete} your customized Proxy TCP Options.
%\pdfbookmark[1]{System Usage}{System Usage}
\section*{\hypertarget{link:System Usage}{System Usage}}
\addcontentsline{toc}{section}{System Usage}
\label{sec:setting:usage}
System usage displays policy and object usage in bar chart and also shows storage usage of files, traffic logs, reports, and metrics.
Files are unstructured logs carried by session records and will store at least one month by default.
Traffic Logs include all four types of logs and will also store at least one month by default.
Reports and Metrics are the predefined or customized data aggregated based on multiple dimensions and will store at least one year by default.
TSG automatically deletes logs and reports that exceed the expiration period. When TSG reaches the storage quota,
it automatically deletes older data. Deleting operates every day at 24:00.
You can estimate server storage space and configure storage parameters. For your convenience, provide the following formula to calculate your required server count.
\textbf{Server Count} = Logs/sec*Storage Days *86400*Log Size *0.4*RF/ (Disk storage per server*0.7)
• Logs/sec: log rate, the log records count generated per second.
• Log Size: the average size of each log, and 1KB will be used in storage calculating as average size.
• Compression Rate: For TSG logs storage, it is 0.4.
• RF: Replication Factor, it is the count of copies on your server. E.g., setting RF=2 means the storage usage will be double of the real size of logs, files, reports and metrics.
• Interval in seconds: 86400, Seconds of a day.
• Disk Safety Factor: it is normally 0.7. It means 70\% of the storage will be used for runtime data of TSG, including logs, files, reports, and metrics.
The others will occupy the remaining 30\%, such as OS, Raid5, and temporary data.
Following are some calculations for a typical scenario:
Suppose there is a data center that is configured to handle the traffic of mainstream websites and applications by TSG. The log rate of session records is 2000/s;
the log rate of event logs is 1500/s; the planed storage days is 30 for event logs with files, so does the storage of session records.
The RF of event logs storage is set to 2 since event logs, raised by hit policies, require more attention. At the same time, the RF of session records is set to 1.
• Storage of session records: 2000*30*86400*1KB*0.4*1 = 1.93TB
• Storage of event logs: 1500*30*86400*1KB*0.4*2 = 2.9TB
In this scenario, the storage space for Files is generally smaller than 150\% of the storage of session records.
The storage space for metrics, which is the data of calculation to set up Mainboard and Live Chart,
is less than 100MB every day, while the storage space required for reports depends on their complexity and quantity.
To configure Storage Usage and expiration period:
\begin{description}
\item[STEP 1.] Select \textbf{System} > \textbf{System Usage}. It displays Storage Usage percentage for Reports and Metrics, Files, and Traffic Logs.
You can view History Log Storage by time.
\warnmark\textit{Warning: Please take caution when performing STEP 2 and STEP 3, because this operation is not recoverable.}
\item[STEP 2.] (\textcolor{gold}{Optional})Click \textbf{Setting}. Check \CheckedBox I understand the risks. Enter the Max Days for each type and Click \textbf{OK}. TSG will delete logs and reports that exceed the expiration period. It may take a long time, during which the maximum sustainable log rate will degrade.
\item[STEP 3.] (\textcolor{gold}{Optional})To clear data once, click \textbf{Clear} to Clear Traffic Logs, Clear Reports and Metrics, Clear Files or Clear All Data.
\end{description}
\section*{\hypertarget{link:System Appearance}{System Appearance}}
\addcontentsline{toc}{section}{System Appearance}
\label{sec:setting:appearance}
System appearance enables the user to customize system logo, title and default language.
Go to \textbf{System} > \textbf{System Appearance} to upload your own logo, favicon, specify title, and select the default language.
|
