1 PRTG

1.1 PRTG Setup

1.1.1 PRTG Core Server

Description	Detail
Application	PRTG Network Monitor
Version	19.4.54.1506
License	PRTG Network Monitor XL1 (Unlimited sensors) Expiry Date : 31/12/2019
Probe Name	LOCAL
Operating System	Microsoft Windows Server 2019 Standard (10.0 Build 17763)
Server Spec	� 2x Intel Xeon Silver 4114 10-core CPU @ 2.20GHz � 64GB RAM � 2x 465GB SSD
URL	https://prtg.toffstech.com
RDP	prtg.toffstech.com:33211
IP Address	IPv4 :� 118.107.220.26 �� 118.107.221.26 IPv6 : �2402:9500:e000:1001::4
Location	Gigabit DC @ Kuala Lumpur

1.1.2 Remote Probe

Description	Detail
Application	PRTG Remote Probe
Probe Name	WIN-502IHF277GA
Operating System	Microsoft Windows Server 2019 Standard �(Version 1809)
Server Spec	� 2x Intel Xeon E5-2670 8-core CPU @ 2.60GHz � 32GB RAM � 2x 465GB SSD
RDP	103.71.177.233:37544
IP Address	IPv4 :� 103.71.177.233
Location	Gigabit DC @ Kuala Lumpur

1.2 PRTG Grouping

1.2.1 Group Structure

Toffs PRTG design is structured to assign grouping of Groups/Devices/Sensors based on the following grouping hierarchy. Additional sub-groups can be created below this parent group hierarchy.

Any device/sensor that required 24x7 monitoring by NOC/SOC shall be created under �Prod� group and arranged in accordance to the CDN business system (e.g. T2, C4).

Other device/sensor created outside �Prod� group will not be subjected to NOC/SOC monitoring.

Toffs PRTG Grouping Hierarchy :

� Root

� LOCAL

� Probe Device

� Prod

� C4

� C4-related Group #1

� C4-related Group #2

� ��:

� T2

� T2-related Group #1

� T2-related Group #2

� ��:

� Non-Prod

� C4

� C4-related Group #3

� C4-related Group #4

� ��:

� T2

� T2-related Group #3

� T2-related Group #4

� ��:

� Other Functional Group #1

� Other Functional Group #2

� Other Functional Group #3

� ��:

1.2.2 PRTG Groups

Below are the present groups exist in PRTG.

You may add additional functional groups when necessary to align with new functional requirements.

No.	Group	Member Groups
1	Prod > C4	C4 AWS Logstash & DB Backup
2	Prod > T2	Master & Relay Server Fast Server Production Servers ZONE: Main ZONE: Main2 ZONE: FUYA ZONE: JBS ZONE: IVI ZONE: KZING ZONE: Maindvi Gigabit DDos Defense Servers Port Forward Media_Server PT-Team Group Home Newfuture VPN Servers
3	Non-Prod > C4
4	Non-Prod > T2
5	Other Functional Groups	JB POP HCI

Any production-related systems shall be placed under �Prod� group. NOC/SOC are monitoring systems under �Prod� group on 24/7 basis.

Non-production related systems (e.g. POC testing) shall be created under �Non-Prod� group, where any alarms from these systems will be filtered from reaching NOC/SOC.

1.3 PRTG Object Naming Convention

Important : PRTG object naming convention must be strictly adhered to ensure proper integration with other Toffs applications.

Each object in PRTG (Probe, Group, Device, Sensor) need to be assigned with a name.

Natively, PRTG allows multiple objects to share a same name. However, to facilitate API integration with PRTG from various Toffs applications (e.g. IPMon), name sharing shall be restricted in Toffs PRTG implementation.

PRTG object naming shall adhere to the following conventions :

1) Server�s Group name for must unique

E.g.

"Gigabit_Hong Kong_43.251.112.76_72 EIP_50Mbps" is server group name in Main Zone. No other server groups in PRTG shall use the same name.

Howerver, sensor names under each server can use the same name.

E.g. "Curl9099(ipmon)", "Ping", "(002) eth0 Traffic" and etc.

2) �Curl9099(ipmon)� IPMon sensor & �Curl9099� non-IPMon sensor

"Curl9099(ipmon)" is a special curl sensor for IPs used� by China customers and monitored by IPMon.� The sensor must be named with this exact sensor name (case sensitive). If there is any discrepancy in the sensor name, the IP will not be detected and monitored by IPMon.

"Curl9099" is the normal curl sensor for IPs not used� by China customers (e.g. Vietnam, Singapore servers). All this IP shall not be monitored by IPMon.� Please ensure you do not name it as "Curl9099(ipmon)" to avoid it from being mis-detected and monitored by IPMon.

3) Do not use double (or tripple or more) space

E.g.

�� "Server 1" is ok.

�� "Server� 1" is not ok.

�� "Server�� 1" is not ok.

PRTG API treating multiple space as single space and may respond unpredictably when doing API search based on object name with multiple space.

4) Do not use square bracket ("[" and "]")

�� E.g.�

�� "Server[1]" is not not ok. Square bracket is not ok.

�� "Server(1)" is ok.� Round bracket is ok.

�� "Server{1}" is ok. Brace is ok.

�

Square bracket conflict with PRTG API search syntax� and do not respond correctly when doing API search for object name with embeded square bracket.

5) Do not use plus character (+)

�� E.g.�

�� " Simetric_HK_182.16.36.50_100 Mbps INTL + 15 Mbps CN" is not not ok.

Alternatively, you can use Ampersand (&)

�� E.g.�

�� " Simetric_HK_182.16.36.50_100 Mbps INTL & 15 Mbps CN" is not ok.

6) Do not use comma (,)

�� E.g.

�� Gigabit_Hong Kong_45.116.160.135, 50Mbps� is not ok.

�� Gigabit_Hong Kong_45.116.160.135_50Mbps� is ok.

Some Toffs applications relies on using PRTG API to generate CSV-based result. Object name with embedded comma will cause wrong seggregation of data fields when interpreting the output files.

7) Do not use Chinese characters

E.g.

�� Gigabit_成都_45.116.160.135_72IP� is not ok.

�� Gigabit_ChengDu_45.116.160.135_72IP� is not ok.

PRTG API cannot interpret Chinese characters correctly.

1.4 T2 CDN Server Monitoring Setup

1.4.1 Server Group and Device/Sensor Placement

Server group is a parent group created to represent a CDN server and embrace all entities belonged to the server like Main IP, Sub IPs, curl sensors and other server monitoring sensors like CPU, RAM, bandwidth, disk space and etc.

Besides, Zone groups (e.g. Main, Fuya, JBS, IVI and etc) are also created to represent each customer zone and placed below T2 group.

Server group shall be created inside the zone group that the server belongs to.

All server group for China centric CDN servers must be tagged with �ipmon� tag to enable IP monitoring by IPMon. Do not add �ipmon� tag to the server group if the server is not used for serving China CDN customers (e.g. Vietnam or Singapore servers) and does not need IPMon monitoring.

A screenshot of a computer program

Description automatically generated

All Main-IP and Sub-IPs are created as individual device under server group and create underlying sensors as below :

� Main-IP : All server monitoring sensors (e.g. CPU, VRAM etc) and Curl9099(ipmon) sensor

� Sub-IP :� Curl9099(ipmon) sensor only

Below is an example of server group and its correponding device and sensors.

A screenshot of a computer

Description automatically generated

1.4.2 Server Group Tier

Generally, server groups is placed directly below a zone group as tier-1 group. However, for large zones (e.g. Fuya) that has large quantities of servers, additional groups are created below Zone groups to group servers into locations or cloud providers. Thus server groups is relegated to tier-2 or tier-3 group, below the location group, cloud provider group or both.

IPMon has an IP List Generator tool that can search through PRTG group tiers to build IP address list for IPMon to monitor the availability and performance of CDN IPs. As the IP List Generator can only search PRTG groupings up to tier-3 group only, the lowest tier for any server group shall not be lower than tier-3. Any server group placed lower than tier-3 (e.g. tier-4 group) will not be searched by IP List Generator and hence its IPs are not monitored by IPMon.

1.4.3 Server Monitoring sensors

Each T2 CDN server shall be monitored with the following PRTG sensors with scanning intervals per below.

No.	Sensor	Scanning Interval	Alert Limit
No.	Sensor	Scanning Interval	Channel	ID	Limit	Message
1	SNMP CPU Load	60s	Total	0	Upper Warning Limit = 75% Upper Error Limit = 90%	CPU > 75% CPU > 90%
2	SNMP Memory : Physical Memory	60s	Not applicable
3	SNMP Memory : Swap Space	60s	Not applicable
4	SNMP Memory : Virtual Memory	60s	Percent Available Memory (%)	0	Lower Warning Limit = 20% Lower Error Limit = 10%	VRAM > 80% VRAM > 90%
5	SNMP Meminfo	60s	Not applicable Note : Alert limits are pre-set for the following channels, please disable it : � Physical Free Percent (%) � Swap Free Percent (%) � Total Free Percent (%)
6	SNMP Disk Free : /	60s	Free Space (%)	0	Lower Warning Limit = 25% Lower Error Limit = 10%	DISK > 75% DISK > 90%
7	SNMP Traffic 64 (eth0)	60s	Traffic In	0	Upper Warning Limit = �� 75% Base BW (Mbps) Upper Error Limit = �� 90% Base BW (Mbps)	BW-IN > 75% BW-IN > 75% (Burstable) BW-IN > 90% BW-IN > 90% (Burstable)
7	SNMP Traffic 64 (eth0)	60s	Traffic Out	1		BW-OUT > 75% BW-OUT > 75% (Burstable) BW-OUT > 90% BW-OUT > 90% (Burstable)
8	Main-IP : Ping	30s	Not applicable
9	Sub-IPs :� HTTP (http://:9099/speedtest.jpg)	30s	Not applicable

Example of Sensor settings

A screenshot of a computer

Description automatically generated

Note :

1. Alerts on all channels of all sensors shall be disabled except for selected channels specified per above table.

A white background with black text

Description automatically generated

2. Setup alerts for the selected sensors above only for the selected channels only. Other channels in the sensor shall have alert disabled.

A screenshot of a computer

Description automatically generated

3. HTTP sensors shall be setup for each Sub-IPs configured on the CDN node.

4. HTTP sensor shall use new URL http://:9099/speedtest.jpg for downloading the smaller 4KB JPG file only to reduce monitoring overhead.

5. Base BW refers the committed bandwidth purchased for the CDN node without including burstable bandwidth (if any).

6. Indicate �(burstable)� in alert messages if the CDN node is subscribing burstable bandwidth.