Monitoring and administering network usage

Using the Push API, you can stream live raw network data from various sources to a web-based endpoint, for the purposes of monitoring and administering network usage.

You can subscribe to one or more of the following network data stream services:

  • NetFlow Raw Push
  • RADIUS Authentication
  • RADIUS Accounting

NetFlow is a networking protocol that collects active IP network traffic data as it flows in or out of an interface, such as an IoT device. The collected data includes:

  • Traffic source and destination IP addresses and port numbers
  • The number of bytes and IP packets observed in the traffic flow

Eseye captures real-time NetFlow data across all its data centres, for every device. This high volume data is processed through Eseye's cloud infrastructure using Amazon Kinesis, then enriched with valid SIM ID and IMSI information. Eseye presents NetFlow data to subscribed customers in a constant, aggregated stream via the Push API. Each NetFlow payload that is sent to a customer is linked to a specific SIM in the customer's Infinity Classic account. For information about receiving NetFlow messages, see the 8725 Push API Developer Guide (PDF).

Network administrators can analyse the data to understand the traffic flow and volume across their SIM estate network, which may inform business decisions. For example, a business may need to purchase new hardware in areas of high usage to ease traffic flow congestion, or retire a thing that is never used.

RADIUS authentication controls a user's network resource access. Users are first verified and then authorized to access specific resources.

The user requests access from the Network Access Server (NAS), which in turn sends a RADIUS Access-Request to the RADIUS server. The Eseye RADIUS server returns either of the following responses to the NAS:

  • Access-Accept

    The user is granted access to network resources. After authenticating the user, the RADIUS server regularly checks that the user is authorized to use a requested network service. For example, a user may have access to the wireless network, but not the VPN service. This information is either stored locally on the RADIUS server, or in an external source, such as LDAP or Active Directory.

  • Access-Reject

    The user is denied access to network resources. Reasons may include:

    • Failure to provide proof of identification
    • Unknown or inactive user account

Eseye captures real-time RADIUS authentication data across all its data centres, for every device. This high volume data is processed through Eseye's cloud infrastructure using Amazon Kinesis, then enriched with valid SIM ID and IMSI information. Eseye presents this data to subscribed customers in a constant, aggregated stream via the Push API. Each RADIUS authentication payload that is sent to a customer is linked to a specific SIM in the customer's Infinity Classic account. For information about receiving RADIUS authentication messages, see the 8725 Push API Developer Guide (PDF).

Customers can use the data to track network and device usage, and analyse networking issues. For example, they can track which devices are disconnected from the network for a long period of time, or how often a device authenticates.

RADIUS accounting collects data that accurately measures a RADIUS network user's start and stop times and traffic usage. This information is used for billing purposes and general network monitoring.

RADIUS accounting has the following flow:

Accounting type Description
Accounting-Start The RADIUS accounting session starts after the user is authorised to access the RADIUS server. At this point, the Network Access Server (NAS) sends a RADIUS Accounting Request packet to the RADIUS server. This packet signifies that the user's session on the network has begun, and normally contains the user ID, point of access, and network address, as well as a unique session identifier.
Accounting-Interim Depending on the session length, the NAS may also periodically send one or more Accounting-Interim updates, which contain the session duration and current data usage. The first update occurs 30 minutes after Accounting-Start.
Accounting-Stop

The RADIUS accounting session terminates when the SIM disconnects from the network. Reasons for termination may include:

  • The user manually signs off
  • The user is denied access because of role-level restrictions
  • An error occurs on the network, such as a port error
  • Session time out occurs because of inactivity, or the maximum session length is exceeded
  • An administrator manually stops the session

Eseye captures real-time RADIUS accounting data across all its data centres, for every device. This high volume data is processed through Eseye's cloud infrastructure using Amazon Kinesis, then enriched with valid SIM ID and IMSI information. Eseye presents this data to subscribed customers in a constant, aggregated stream via the Push API. Each RADIUS accounting payload that is sent to a customer is linked to a specific SIM in the customer's Infinity Classic account. For information about receiving RADIUS accounting messages, see the 8725 Push API Developer Guide (PDF).

Customers can use the data to generate network usage and billing reports.

Where to next?