Solutions for your ISP business

An end-to-end solution that can cater to the complete backend needs of an ISP be it CRM, NAS, Billing or Logging. These lightweight modules can be installed either on one hardware or based on the ISP’s network needs, on separate physical hardware per module. The system can be used either as a central solution providing AAA services to all customers from the NOC or as a client-server model wherein the NAS component is installed at the edge thus making it suitable to support virtually unlimited subscribers by segmenting the ISP network into Core, Aggregation and Access layers.

For easier understanding and in keeping with the modular approach, the solution is divided into the following components:

FlashOS

  1. The foundation of the system is a highly optimized Linux based OS to meet the demands of today’s high speed, low latency networks. The size of FlashOS is ~250MB only making it extremely lean and fast.
  2. FlashOS includes only the required tools and software necessary to work with the hardware on our HCL (Hardware Compatibility List) effectively eliminating any bloatware and/or buggy software thus leading to a more stable and secure environment.
  3. FlashOS always uses the latest stable kernel available so the system has the latest security patches and bug fixes. Any upgrades to the next stable version is only undertaken after extensive testing by our R&D team.
  4. FlashOS, being extremely small in size takes seconds to boot (~15 seconds after BIOS checks) which translates into less downtime in case of planned/unplanned maintenance activities.
  5. Our system installed over FlashOS is capable of giving uptimes running into years.
  6. FlashOS has been extensively tested and optimized on the approved hardware to extract maximum performance and stability.

IPACCT

  1. A NAS designed as per EU standards and built in line with the requirements of the Indian ISP market.
  2. Supports PPPoE, IPoE, DHCP, Web Login, and MAC based authentications. Allows to use different combinations of authentications on the same hardware/server instance.
  3. Allows you to configure Public IP pool on server basis and irrespective of VLAN, interface or authentication used, performs SNAT on the pool.
  4. Has support for 4 different bandwidth policies ranging from strict bandwidth management (CIR) to inbuilt burstable config. Any of the policies can be applied dynamically on the fly.
  5. Allows assigning multiple user accounts/IPs with different user credentials in same bandwidth pool/package. Eg individual user accounts for guests in a hotel restricted to a large bandwidth pool and billed under the same account head.
  6. Can also do routing of an IP Subnet (LAN Pool) on the Customer IP with bandwidth restriction applied as per the Customer Package from the web interface itself.
  7. Is ONT aware thus can map customer to ONT, with ability to differentiate between Power down and fiber cut. (Some brands of xPoN are supported and support for more brands is in the works).
  8. Graphs customer/IP traffic statistics in real-time.
  9. ISP can define QoS for peering/caching traffic separately per plan/customer and statistics are collected for this QoS in real-time.
  10. Can function with minimal disruption in services to end customer in case of connectivity failure with Centralised IPBILL and can recover and sync automatically when the connectivity is restored.

IPBILL

  1. Designed to cater to the Indian industry and conforms to all required indian standards.
  2. It has an open API architecture allowing integration with existing CRM, Ticketing, Payment/SMS gateway of customer choice.
  3. Can control virtually unlimited IPACCT servers.
  4. Allows centralised control including creation of users, packages, billing, invoices.
  5. Provides insight into the business by providing information through various reports.
  6. Can automatically recover from link failure to connected IPACCT without loss of any information.
  7. Complete/Partial load can be shifted from one remote/edge IPACCT server to another remote/edge IPACCT server in just a few clicks.

IPLOG

  1. Specifically designed to adhere to DOT compliance, this module keeps tracks of each connection passing through IPACCT in the format as instructed by DOT (Source IP: Source Port to Destination IP: Destination Port)
  2. It is recommended to install IPLOG on a separate physical hardware. This system can connect to multiple remote/edge IPACCT systems to collect logs.
  3. IPLOG can collect logs in offline mode as well which means if there is interim loss of connectivity with the remote/edge IPACCT servers, the logs are stored on the IPACCT and fetched again when the connectivity is restored.
  4. IPLOG keeps the logs in simplified and compressed format so as to minimize the storage used. For IPACCT server processing 1.5G of traffic, the log file for half an hour would be below 50MB in size.<li>The logs are parsed and stored in an easily readable and exportable format.

Recommended Server Specifications

Less than 2 000 customers

Boot drive

1 x SATADOM

Data Drive (for logs)

2 x HDD SATA-III
Enterprise/Black Edition (1TB x 2)

Network Interface (chipset)

1G – i350
10G – i82599ES

CPU

1 x Intel Xeon E3-1220 V6

RAM

8GB ECC

2 000 – 5 000 customers

Boot drive

1 x SATADOM

Data Drive (for logs)

2 x HDD SATA-III
Enterprise/Black Edition (1TB x 2)

Network Interface (chipset)

1G – i350
10G – i82599ES

CPU

1 x Intel Xeon E5-2630 V4

RAM

16GB ECC

5 000 – 10 000 customers

Boot drive

1 x SATADOM

Data Drive (for logs)

2 x HDD SATA-III
Enterprise/Black Edition (1TB x 2)

Network Interface (chipset)

1G – i350
10G – i82599ES

CPU

2 x Intel® Xeon Silver 4108 or higher

RAM

16GB ECC

LOG Server

Boot drive

1 x SATADOM

Data Drive (for logs)

4 x HDD SATA-III
Enterprise/Black Edition (2TB x 4)

Network Interface (chipset)

1G – i350
10G – i82599ES

CPU

1 x Intel Xeon E3-1220 V6

RAM

16GB ECC

  1. IPACCT only recommends hardware manufactured by SuperMicro and will guarantee performance on approved hardware.
  2. It is recommended to always install the IPLOG module to a separate physical server.
  3. HDD to be installed must adhere to the SATA-III standard (6Gb/s).