Next Faster. Next Better.
Kami menghadirkan internet murah berkualitas bagi rumah, kantor, dan bisnis Anda dengan jaringan FTTH.
HARGA PAKET BROADBAND INTERNET
BRONZE
Rp
195rb
/ bulan
UpTo 15 Mbps
Unlimited Kouta
Bulanan Tetap
Gratis Sewa Router
Fiber Optik*
SILVER
Rp
220rb
/ bulan
UpTo 20 Mbps
Unlimited Kouta
Bulanan Tetap
Gratis Sewa Router
Fiber Optik*
DIAMOND
Rp
400Rb
/ bulan
UpTo 50 Mbps
Unlimited Kouta
Bulanan Tetap
Gratis Sewa Router
Fiber Optik*
- Harga di atas sudah termasuk PPN 11%.
- Biaya pemasangan dibayarkan saat selesai pemasangan.
- Harga Flat / Tetap.
Perbandingan Kecepatan
Kecepatan Internet menentukan sebertapa cepat anda mendownload/upload file dari internet.
Juga menentukan sebarapa banyak perangkat yang dapat terhubung bersamaan dengan koneksi internet yang nyaman.
Cocok untuk 1-3 Perangkat,
Download File 1GB = 9 menit
Cocok untuk 1-4 Perangkat
Download File 1GB = 7 menit
Cocok untuk 1-6 Perangkat
Download File 1GB = 5 menit
Cocok untuk >10 Perangkat
Download File 1GB = 3 menit
The Network Lifecycle
The Network Lifecycle is the sixth and final post in this Back-to-Basics series. The previous five posts covered Gathering Requirements, Network Design, Implementation, Operation, and Troubleshooting.
Information Collecting
The most apparent form of information to gather is requirements. The first post in this series discussed gathering requirements to design the initial build. Truth be told, requirements gathering never stops. Business requirements tend to morph over time, and so do the applications that the business relies on. The network needs to keep pace with these changes.
Information about existing and newly built networks should also be gathered. Day-to-day information should include CPU utilization, bandwidth utilization, memory utilization, bit error rate and packet drops, to name a few. Failure analysis reports are also critical pieces of information to improve the system.
Information Analysis
The day-to-day information is the easiest to deal with as it is already in a technical form. This information should reveal whether network gear and links have been sized appropriately.
Failure analysis reports usually require a little more attention and effort than operational information. If the network has not responded as expected to a failure event, it must be determined if the design needs to be improved or if there were mistakes made during implementation.
Business and application requirements usually require the most elbow grease. This type of information always needs to be translated into technical requirements to be incorporated into a design. It would be great if every application clearly stated their network requirements in a meaningful technical format. However, such application documentation is rarer than rocking horse manure.
Architecture and Design
Network Design, discussed creating high-level and low-level design documents. The high-level document is referred to as the architecture, while the low-level document is referred to as the design. Depending on the organization and its division of labor, different resources might be responsible for producing each document or the same resource might produce both. Not surprisingly, it is the role of these resources to turn technical information into network architectures and designs.
Implement and Test
The initial build of a network should pass through a few gates before being promoted to production. While configurations and some operations can be verified in a lab setting, bandwidth, error rates and resiliency testing should be performed on the production equipment with synthetic traffic. Trying to support production workloads is not the optimal time to find a problem that could have been exposed with a rigorous proof of concept.
Operate
A good operations team can make a lousy design tolerable to the business for some time. A negligent operations team can cause even the best-designed networks to drive like a rusted-out jalopy. Networks need care and feeding in the form of security patches, bug fixes, upgrades, effective troubleshooting and supervision.
Recurring issues should be documented and shared with the architecture and design resources. This process requires excellent communication and a healthy relationship between the two parties. It is tempting to implement simple design changes without consulting architecture and design. No matter how innocuous a design change might seem, the final decision lies with architecture and design. This rule supports the continuity and consistency arguments made above.
Optimize and Troubleshoot
The final phase of the lifecycle continues to refine the design and operations of the new network functions. This is when network pros create processes for identifying unforeseen operational problems and identify ways to improve the network, as well as the processes used to operate it.
Network teams should beware of overoptimizing aspects of the network that cause other operational problems. For example, modifying a branch design that results in multiple variations simply to save some money on capital equipment may result in greater Opex.
MANAGE & SMARTHANDS
Setup, maintenance, troubleshoot perangkat jaringan dan server Anda oleh tim berpengalaman dibidangnya onsite maupun by remote.
Cisco, Mikrotik, Huawei, Juniper, dsb.
Onsite : Jawa Timur
LAYANAN LAINNYA
Kami juga menyediakan layanan dan jasa lainnya dibidang IT.
Web Hosting
Hosting website dan gratis Instalasi sampai online
Web Application
Pembuatan aplikasi berbasis web.
VPN
Private Connection
Pengadaan Perangkat
Server, Switch, Router, SFP, PC, CCTV, dll
Instalasi CCTV
IP camera, NVR, DVR, XVR. Dahua, Hikvision, Uniview
Instalasi Jaringan Kantor
Our Partner & Customer
