1. INTERNET CONNECTIVITY SERVICE

There are 3 principal mechanisms for linking a Customer Premise to the Internet. (1) Using essensys Cloud connectivity; (2) using an Internet Service Provider contracted through essensys and; (3) using ISP circuits procured by the Customer.

1.1.1. Essensys procures Layer 2 circuits (eCloud Access) provided by a third party Connectivity Service Provider (CSP) which connect the Premises to the essensys core network where essensys peers directly with transit Internet and other peering providers. This connectivity is referred to generally as the essensys Cloud. The Primary eCloud Access has symmetrical uncontended throughput of at least 1 Gbps. The Backup eCloud Access may provide a secondary route in the event of a Primary circuit failure which will improve the associated SLA.

1.1.2. Capacity. Essensys minimum recommended capacity for any Premises is 1Gbps. Subject to survey and availability essensys can deliver up to 10Gbps capacity for both Primary and Backup Circuits in an Active/Passive configuration. Essensys does not support Active/Active configuration.

1.1.3. Resilience and Diversity. Under normal circumstances, essensys Cloud Access is built to be CSP diverse, this is sufficient to mitigate an acceptable level of risk as most problems resulting in outage occur in the CSP/last mile network segment. Typically, diverse carriers will use different ducts into a building, but this cannot be guaranteed or warranted.

1.1.4. Failover Service. Typically, BGP[1] is used to manage the failover between the Primary and Backup circuits. A Primary eCLoud Access that does not fully fail may not result in a clean failover and may require manual intervention. All IPV4 Public IP addresses provided by essensys will be available on the Primary and Backup eCloud Access.

1.1.5. IPV4 Provision. Essensys provides an IPV4 pool for Customer and Consumer use at each Premises.

1.1.6. Service Monitoring. Essensys provides the following monitoring services for the essensys Network Internet Access.

Automated email alerts will be provided to Site Contacts for:

It is the Customer’s responsibility to ensure that Site Contact information recorded in the Solution is up to date and correct.

1.1.7. Shared Firewall Service. Essensys provide a firewall within its core infrastructure and segmented for each Customer. All shared (non-public IP) traffic shares a single common firewall rule. Any "inbound" traffic that is in response to an outbound connection from any LAN device uses the already established (stateful) connection and is not subject to its own inbound FW rule. Only unsolicited traffic is regarded as inbound by the firewall and is blocked. This firewall configuration is known as ‘anything out, nothing in’ policy. For simplicity, manageability, and performance reasons, essensys does not provide any custom setup or configuration for the shared firewall.

1.1.8. Major Incident Management Service. Any disruption that materially impacts the Consumer Services delivered in one or more Customer Premises may be classed by essensys as a Major Incident. Essensys will provide full RFO for a Major Incident in accordance with the SLA

Essensys procures Layer 3 DIA circuits provided by a third party Internet Service Provider (ISP) which connect the Premises to the Internet through the ISPs network.

1.2.1. Capacity. Subject to survey and availability essensys can deliver up to 10Gbps capacity for both Primary and Backup Circuits in an Active/Passive configuration, at this time essensys does not support Active/Active configuration.

1.2.2. Resilience and Diversity. Layer 3 services procured by essensys will normally use a Tier 1 carrier for both circuit. Where possible, the ISP will deliver circuits to the same Premises from different network segments. Typically,each circuit will use different physical ducts into a building but this cannot be guaranteed or warranted and is subject to survey and availability

1.2.3. Failover Service. BGP or IP SLA tracking is used to manage the failover between the Primary and Backup circuits. A Primary Circuit that does not fully fail may not result in a clean failover and may require manual intervention.

1.2.4. IPV4 Provision. The ISP or essensys will provides an IPV4 pool for essensys use at each Premises. IPV4 for Customer use is subject to application and approval by the ISP or essensys.

1.2.5. Service Monitoring. Essensys provides the following monitoring services for the ISP provided connectivity:

Automated email alerts will be provided to Site Contacts for:

It is the Customer’s responsibility to ensure that Site Contact information recorded in the Solution is up to date and correct.

1.2.6. Shared Firewall Service. Essensys will manage an on premise firewall (or dual firewalls in High Availability mode) provided as part of the Hardware delivering the LAN infrastructure for the Premises. All shared (non-public IP) traffic shares a single common firewall rule. Any “inbound” traffic that is in response to an outbound connection from any LAN device uses the already established (stateful) connection and is not subject to its own inbound FW rule. Only unsolicited traffic is regarded as inbound by the firewall and is blocked. This firewall configuration is known as ‘anything out, nothing in’ policy. For simplicity, manageability, and performance reasons, essensys does not provide any custom setup or configuration for the on premise firewall.

1.2.7. Major Incident Management Service. Any disruption that materially impacts the Consumer Services delivered in one or more Customer Premises may be classed by essensys as a Major Incident. Essensys will provide full RFO for a Major Incident.

Customer procures Layer 3 DIA circuits provided by a third-party ISP which connect the Premises to the Internet through the ISPs network.

1.3.1. Minimum standards and acceptance into service. Customer provided Internet circuits must meet the minimum recommended specification as set out in the provided Essensys Direct Internet Access (DIA) Specification Guide LINK HERE

1.3.2. Capacity. No alerting or capacity planning is provided.

1.3.3. Resilience and Diversity. All resilience and diversity planning is provided by Customer.

1.3.4. Failover Service. BGP or IP SLA tracking is used to manage the failover between the Primary and Backup circuits. A Primary Circuit that does not fully fail may not result in a clean failover and may require manual intervention. Any IP addresses provided on the primary circuit will not failover when the backup is in use.

1.3.5. IPV4 Provision. All IPV4 provision is the responsibility of the Customer. Essensys will require a /24 range provided by the Customers ISP as a minimum. IPV4 for customer use is subject to application by the Customer and approval by the ISP.

1.3.6. Service Monitoring. No Service Monitoring is provided.

1.3.7. Shared Firewall Service. Essensys will manage a firewall(s) provided as part of the Compatible LAN infrastructure. All shared (non-public IP) traffic shares a single common firewall rule. Any "inbound" traffic that is in response to an outbound connection from any LAN device uses the already established (stateful) connection and is not subject to its own inbound FW rule. Only unsolicited traffic is regarded as inbound by the firewall and is blocked. This firewall configuration is known as ‘anything out, nothing in’ policy. For simplicity, manageability, and performance reasons, essensys does not provide any custom setup or configuration for the on Premise firewall.

1.3.8. Major Incident Management Service. No Major Incident Management Service is available.

1.3.9. All fault reporting and liaison with the ISP will be provided by the Customer. Subject to agreement by essensys this may be undertaken by essensys subject to an additional fee and provision of a Letter of Authority from Customer to ISP permitting essensys to engage with ISP on behalf of Customer

1.3.10. Layer 2 over Layer 3 Services. In some circumstances, essensys may agree that a Customer may provide a DIA or other Internet service that can be employed by essensys to provide a virtual Layer 2 service using additional Hardware and tunnelling protocols to connect the Premises to the essensys Network. This may be employed as a Primary, or a Backup virtual L2 Circuit. No SLA will apply to any connectivity provided in this way.

​

[1] Border Gateway Protocol (BGP) refers to a gateway protocol that enables the internet to exchange routing information between autonomous systems (AS). Where a route no longer exists, or a better route is available and advertised, BGP will take this better route.