Data Center is our focus

We help to build, access and manage your datacenter and server rooms

Structure Cabling

We help structure your cabling, Fiber Optic, UTP, STP and Electrical.

Get ready to the #Cloud

Start your Hyper Converged Infrastructure.

Monitor your infrastructures

Monitor your hardware, software, network (ITOM), maintain your ITSM service .

Our Great People

Great team to support happy customers.

Thursday, November 23, 2017

PRTG Export dengan UVExplorer

PRTG Export

If you monitor your network with PRTG Network Monitor, UVexplorer makes a great companion product to PRTG. UVexplorer can export devices and network maps to PRTG, and also automatically configure PRTG device sensors. This allows you to discover devices in UVexplorer, export them to PRTG, and monitor them in PRTG. This gives you the best of both worlds: UVexplorer's detailed and fast network discovery capabilities, combined with PRTG's advanced network monitoring capabilities.
UVexplorer integrates directly with PRTG to provide the following powerful features:
Enhanced Discovery of Network Devices and Connectivity - UVexplorer's discovery is fast, detailed, and accurate. Run network discoveries within UVexplorer, and export discovered devices to PRTG for monitoring.
Automatic Device Sensor Configuration - When UVexplorer exports devices to PRTG, it automatically configures sensors on those devices in PRTG. Rather than creating all possible sensors, UVexplorer creates only those sensor types that you request, which minimizes your sensor count. Specifically, UVexplorer can automatically configure the following PRTG sensors:
  • Ping Sensors
  • SNMP Uptime, CPU, Memory, and Traffic/Interface Sensors
  • WMI Uptime, CPU, Memory, and Disk Space Sensors

Enhanced Network Maps - UVexplorer automatically creates detailed maps of your network, including details about how your devices are connected at the port level. UVexplorer's map editor makes it easy to create high-quality maps, and then export them to PRTG. This gives you great maps in PRTG, with UVexplorer doing most of the work automatically.

Scheduled Network Discoveries - UVexplorer keeps your PRTG devices, sensors, and network maps continuously up-to-date by running network discoveries on a scheduled basis (hourly, daily, weekly, etc.) After completing a scheduled discovery, UVexplorer automatically exports new devices and updated maps to your PRTG server, and also configures sensors on new devices.
Detailed Device Inventory - UVexplorer discovers detailed inventory information about your network devices, and lets you run reports across all devices on your network. The following inventory data and reports are available:
  • Asset details (make, model, serial number)
  • Operating System Version
  • Software Inventory
  • Network Interfaces, Bridgeports, and VLANs
  • Device Connectivity

PRTG Export Wizard

UVexplorer discovers all of your network devices and connections in a matter of minutes. At any time after discovery completes, you can export your network devices and maps into PRTG by clicking the "Export to PRTG" button in the Home toolbar (see below). Clicking this button will start the PRTG export wizard, which steps you through the various export options.
Clicking Next on the wizard start page takes you to a page that asks you to select the PRTG server you want to export to.

If you have never before defined credentials for your PRTG server, click the settings button to define those credentials. You will be asked to type in the URL, username, and passhash for the target server. (Your passhash can be found in the PRTG web browser interface by selecting the Setup -> Account Settings -> My Account menu option.)

Clicking Next on the PRTG Server Settings page takes you to a page that lets you specify the name of the PRTG device group your UVexplorer devices will be exported to. You can send your devices to an existing PRTG device group, or specify that a new device group be created. If you export devices to an existing PRTG device group, UVexplorer will only add new devices that are not already in the target group (i.e., duplicate devices are not created). You can also specify an existing parent device group within which the new device group will be created. In addition to creating a device group, you can also ask UVexplorer to create a network map in PRTG. The exported map will contain all of the exported devices, including the physical connections between them. You can specify whether a new map should be created, or an existing one should be overwritten. If you overwrite an existing PRTG map, UVexplorer will only add new devices that are not already on the map (i.e., duplicate map devices are not created).

Clicking Next on the Device Group/Map page takes you to a page that lets you select the devices to be included in the exported device group. You can select any or all devices in the discovery result that is currently open in UVexplorer.

Clicking Next on the Devices to Export page takes you to a page that lets you specify what kinds of sensors should be created on the devices in PRTG. Often, you only want one or two kinds of sensors created, not all possible sensors. By exporting devices from UVexplorer into PRTG, you can get only the sensors that you really want, thus minimizing your sensor counts.

Clicking Next on the PRTG Monitor Settings page takes you to a page that lets you initiate the export to PRTG.

Clicking Finish on this page will begin your export. The PRTG export will appear. It displays all of your selected export settings, and also provides feedback on the progress of the export.

After the export is complete, the "Goto Group" and "Goto Map" buttons on the export form will be enabled. Clicking "Goto Group" will open a web browser, and take you to the PRTG device group that was created by the export.

Similarly, clicking the "Goto Map" button will open a web browser, and take you to the PRTG map that was created by the export (if any).

Through the PRTG user interface you can view the sensors that were automatically configured by UVexplorer on the exported devices, as shown below.

Exporting Directly from UVexplorer Maps

You can also export devices to PRTG without using the PRTG export wizard. This may be more convenient once you are comfortable with the export process. Specifically, you can export the devices on any UVexplorer map by right-clicking on the map, and selecting the "Export -> Export to PRTG" option (see image below).

This displays the PRTG export form, which lets you enter all of the export settings on one form (instead of using the PRTG export wizard). After entering your export settings, click the Export button to export all of the map's devices to PRTG.

PRTG Monitors dengan UVExplorer

PRTG Monitors

If you monitor your network with PRTG Network Monitor, UVexplorer makes a great companion product to PRTG. In addition to exporting devices, sensors, and maps to PRTG, UVexplorer can also query device status (Up, Down, etc.) from PRTG so that device status can be viewed within UVexplorer's maps and reports. This allows PRTG's powerful monitoring platform to enhance UVexplorer's network discovery and mapping capabilities.
At any point in time, PRTG can tell you what the overall status of a device is (Up, Warning, Down, Paused, etc.). If you want to display device status within UVexplorer, you can create one or more PRTG monitors that query device status from PRTG on a regular schedule (e.g., every 5 minutes). For example, suppose you want to display the state of your core networking devices in UVexplorer (routers, switches, firewalls, etc.). To do this, go to UVexplorer's Monitors tab, and create a PRTG Monitor on your core networking devices. Give it a schedule that meets your needs (e.g., every 5 minutes). Every time this monitor runs, it will query the state for the specified devices from PRTG, and store the state information in the UVexplorer database. UVexplorer will then display these device states within its maps and reports.
Creating a PRTG Monitor
To create a PRTG Monitor, do the following:
  • Go to the Monitors tab (at the bottom of UVexplorer's main window)
  • Select "PRTG Monitors" on the left side
  • Right-click in the grid on the right, and select Add from the context menu. This will display the PRTG Monitor configuration form. This form lets you select the PRTG server to be queried, the set of devices for which status should be queried, and the schedule on which UVexplorer should query the PRTG server for status (see image below).
Viewing PRTG Device State in UVexplorer
After creating a PRTG Monitor, you can view the status of the monitor's devices (according to PRTG) in the UVexplorer user interface (see images below).
You can also view the history of a PRTG monitor by right-clicking on the monitor, and selecting the "PRTG History" option from the context menu. This report displays a state history for each device in the monitor. This lets you see how the state of each device has changed over time (see image below).
Auto-Creating PRTG Monitors at Export Time
When you export devices to PRTG, you are given the option of having UVexplorer automatically create and configure a PRTG Monitor on all exported devices so that you can view the states of those devices in UVexplorer. If you use the PRTG export wizard to do your export, the wizard will ask you if you want UVexplorer to auto-create a PRTG Monitor on the exported devices. Or, if you export directly from a map by selecting "Export to PRTG", the export form give you the option of auto-creating a PRTG Monitor on the devices. Either way, after completing the export, you can go to UVexplorer's Monitors tab, and see the auto-configured PRTG monitor (see images below).
Linking from UVexplorer Devices to PRTG Devices
When using UVexplorer with PRTG, it is often convenient to jump between the two environments. For example, if UVexplorer shows a device as being "Down", you will probably want to jump into PRTG to further investigate the situation. To make this easy, in UVexplorer you can right-click on a device, and select the "Show in PRTG" option. Doing this automatically opens PRTG in a web browser, and displays the PRTG device corresponding to the selected UVexplorer device. You can then inspect the states of the device's various PRTG sensors. This works in both UVexplorer device lists and maps (see image below).

Tuesday, November 21, 2017

Monitoring a KEMP LoadMaster Using PRTG

Monitoring a KEMP LoadMaster Using PRTG: A Detailed How To Guide

There are a lot of solutions to choose from that does load management and security for services, in this article we will be looking at Kemp Loadmaster.
KEMP Technologies offers “KEMP Loadmaster”, which, as the name implies, balances application loads between web servers. Their product offering includes both virtual and hardware appliances. The virtual offering supports most hypervisors and cloud deployment, and they have hardware appliances of varying sizes to support larger loads.

iVirtualization is the process of creating a virtual version of something like computer hardware. It involves using specialized software to create a virtual or software-created version of a computing resource rather than the actual version of the same resource. Read more ...

One of the great things about the KEMP, like PRTG, is that there's a free version available for download. You can download a virtual appliance and run it in your virtual environment. The free version has some restrictions but it’s great for testing, configuration, and lab use. The KEMP LoadMaster also does Reverse Proxy (we’ll refer to it as "Rproxy"), which, in addition to monitoring, is the focus of this article.

Monitoring KEMP LoadMaster

PRTG is a network monitoring tool, so we want to monitor the device status and performance. The KEMP provides this in a couple of ways: through SNMP and through their REST API.
The default discovery of the device gives us the generic SNMP sensors.
The information we are really interested in is how much traffic is it handling.
Using the MIBs supplied by KEMP and the Paessler tools, I created a template for the LoadMaster (available for download from PRTG Script World or directly from The template uses the SNMP Custom Advanced and SNMP Custom Table sensors to get some more information (the process is outlined in this Webinar "SNMP MIB basics – Monitoring with PRTG").

The template creates a health sensor, with a high level overview of the KEMP status and performance.
It also creates a sensor for each Virtual and real server with Metrics.
  • You may have noticed the sensors:
    • rSrvr: Nat 1000
    • vSrv: PRTG1-RP(
    • rSrvr: Nat 1000
    • vSrv: PRTG1-Web(
These are the sensors with performance metrics for the real and virtual servers. In particular, these are the sensors that measure the statistics related to the Rproxy that does the SSL offloading for PRTG’s remote probe and PRTG Web GUI respectively.

Monitoring KEMP Using the REST API

In PRTG version 17.3.33/34 we added a new sensor, the "REST Custom Sensor", which can also be used to get a top-level overview on how the KEMP is doing.
So, the next question is how do you configure it.
For installation details of the KEMP, please refer to the instructions on the manufacturer site. 
Please note: We have carefully compiled this information and it is provided to the best of our knowledge. As the solution is not part of PRTG itself, it is not officially supported by Paessler or PRTG Technical Support. Yet, we wanted to share it with you as it might be of interest for many PRTG users.
You must also be aware, that if you configure any of the parts incorrectly, you may leave yourself open to an intruder gaining access to anything configured within PRTG. This includes User ID’s, Passwords, ip’s names, etc. IE no warranties expressed or implied. Paessler, its employees or partners cannot be held liable for any damages that you may incur as a result of employing a Reverse Proxy.

Monitoring Ubiquiti UniFi WiFi with PRTG

Monitoring Ubiquiti UniFi WiFi with PRTG: Total Insight into UniFi Environments

Ubiquiti Networks offers a range of wireless hardware and software for enterprise WiFi and operator WiMAX wireless data communication. In this article, we’ll explain how to monitor Ubiquiti’s UniFi WiFi systems using PRTG.
One way to monitor each of your UniFi access points is with PRTG’s standard SNMP sensors together with Ubiquiti’s private MIB files. This lets you monitor each access point in depth, giving you insight into any data available in the MIB file.
iSNMP stands for Simple Network Monitoring Protocol. Its usefulness in network administration comes from the fact that it allows information to be collected about network-connected devices in a standardized way across a large variety of hardware and software types. SNMP is a protocol for management information transfer in networks, for use in LANs especially, depending on the chosen version. Read more ...

However, monitoring single access points via SNMP has a few disadvantages:
  • The UniFi series only supports SNMP v1 (see screenshot below)
  • You will need SNMP access to each access point, which could be an issue if the access points are spread across multiple locations
  • You can only view details about one access point at a time, and can only display metrics that one access point knows. Global metrics for the entire installation aren’t available from a single access point because one AP simply doesn’t have a global overview.
Ubiquiti UniFi SNMP Settings
So, to improve visibility into your UniFi environment, we’ve created a new custom script sensor to monitor the controller directly, giving you an overview of all of your access points in a single sensor.
A huge thanks to Luciano Lingnau from our technical support team, who published the following script in our Knowledge Base
This script uses the UniFi RESTful API to pull data into PRTG, where it will then display controller metrics such as:
  • Response time from the controller’s API
  • The number of access points connected to the controller (UAPs in “connected” status)
  • The total number of connected clients, including guests
  • The total number of connected guests
  • The number of upgradeable access points (UAPs in “connected” status, with the “upgradeable” flag set)
Since this script collects all data directly from the UniFi controller, you’ll see a global overview about all access points that are connected to that controller. And you only need HTTP access to the controller – you don’t need SNMP access to each individual access point. To run Luciano’s script, check out his article, which includes the requirements, detailed instructions, and (of course) the code for the script.
In addition, Frank Carius, a German blogger, has extended this script to include:
  • Amount of data
  • Clients/ virtual network
  • RX and TX bytes, dropped and errors
  • ….
Frank’s blog article is only available in German, BUT even if you can’t read the article, you can download the script (which is commented in English!) here.
The extended script in action
To run the extended script you’ll need to download the file and save it to
C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXEXML
Then, before you run the script, you need to set a few parameters, either inside the PRTG custom script sensor settings, or directly inside the script:
You’ll need to adjust all of the parameters to fit your environment.  The “httppush.url”, for example, is set to “ubiquiti-” in the example script. This is used to create the GUID for the PRTG HTTP Push sensor later in the script:
The GUID consists of the beginning of the URL, the name of the SSID, and the frequency. If you run the script interactively with “-verbose”, you can easily find the URL:
This script is capable of monitoring both the controller and all access points connected to that controller. Detailed per access point metrics will require one additional HTTP Push sensor per access point.. The HTTP Push sensors need to listen on port 5050 and must have GUIDs that match the string(s) shown above.
Once the sensors are up and running, and are receiving data from the script, you can use thresholds and notifications, just like with any other PRTG sensor.
And if you have other devices that aren’t covered by the pre-built PRTG sensors, be sure to check out our Script World site for lots more scripts!

Monday, November 20, 2017

Solusi Akses Aplikasi dan Data dengan Awingu

Salah satu tantangan yang saya temui belakangan ini adalah banyaknya permintaan dari customer untuk tetap bisa mengakses aplikasi serta data files mereka secara nyaman dengan berbagai perangkat yang user miliki, tanpa batasan tempat.
Ya, isu mobilitas telah menjadi faktor utama, terutama bagi yang tinggal dan beraktifitas di Jakarta dan sekitarnya. Kehidupan metropolis yang sibuk, jam kerja kantor yang lebih panjang, serta kemacetan yang terus terjadi membuat banyak perusahaan mencari solusi untuk bisa memaksimalkan potensi dan kinerja karyawannya dari mana saja.
Tetapi beragam solusi yang ada sekarang terkait dengan Bring Your Own Device semua miliki kendala , pertama, umumnya perangkat dimiliki oleh karyawan, sehingga tidak mau dan mudah dipasang dan dikontrol oleh aplikasi Mobile Device Management yang ada. Dan perangkat yang mereka miliki sangat beragam type dan merek, sehingga solusi MDM dan BYOD yang ada menjadi sangat kompleks dan mahal.
Kedua, perusahaan tetap kuatir apabila karyawan bekerja secara remote, semua file akan tercopy, dan mudah disharing ke pihak lain, isu keamanan akses file serta file kerja sangat menjadi hal penting. Semua solusi yang ada harus memiliki informasi audit yang jelas.
Ketiga, banyak perusahaan masih menggunakan aplikasi yang lama. Mereka ragu untuk merubah semua aplikasinya secara langsung hanya karena menginginkan karyawan mengakses aplikasi dari luar lokasi kantor. Waktu yang diperlukan untuk merubah aplikasi menjadi aplikasi yang bisa diakses, baik berbasis web ataupun aplikasi native menjadi kendala.
Semua ini dijawab dengan Awingu. Awingu menyediakan aplikasi platform yang melakukan akses secara aman kepada aplikasi dan data yang ada, sehingga dapat diakses oleh seluruh karyawan hanya dengan menggunakan browser berbasis HTML5. Semua perangkat saat ini telah mendukung dan menggunakan aplikasi browser berbasis HTML5.

Dengan arsitektur diatas, maka Awingu tidak akan melakukan banyak perubahan di lingkungan aplikasi dan data yang telah ada di perusahaan. Awingu hanya akan menjadi 'gateway' akses dari perangkat untuk bisa mengakses aplikasi dan data. Awingu sendiri berbentuk virtual appliance yang bisa dipasang di HyperV, KVM dan VMWare. Sehingga instalasi dapat dilakukan dengan mudah dan cepat.
User yang semula mengakses aplikasi dan data melalui komputer mereka di kantor, akan bisa mengakses melalui satu halaman URL yang dipublish sebagai server awingu.

Mereka akan melihat aplikasi-aplikasi yang biasa mereka akses dan files data yang bisa mereka akses di dashboard Workspace. Kumpulan aplikasi yang di-set agar bisa digunakan bisa dilihat di tab Applications. Dan file kerja yang mereka akses akan bisa diakses di Files. Semua ini dapat saling terhubung dengan aplikasi dan data yang telah mereka miliki di kantor, termasuk sinkronisasi ke file yang ada di cloud seperti dropbox ataupun google drive.
Dengan cara ini, semua karyawan bisa tetap menggunakan aplikasi dan data file yang ada, dari perangkat mereka, baik menggunakan laptop, tablet termasuk smartphone mereka. Dan semua akan tercatat dengan baik di audit log dari Awingu.
Jadi tunggu apa lagi, Awingu kisaran 3jt / user dengan minimal pembelian 5 user concurrent (bukan named user), sehingga user bisa digunakan secara banyak.
Informasi lebih lengkap tentang Awingu bisa diakses di, atau menghubungi kami untuk presentasi implementasi Awingu di perusahaan / instansi anda. Email:, HP : 08121057533.