February 2022

TTL Dual Last Mile Solution

For
ZEALOUS SERVICES-Chennai
Scenario- Active-Active

Private & Confidential

Customer Input & Pre Requisites Received and Captured
Customer Requirement Inputs:
• Customer Looking for Active-Active link in between 2 separate Transmission Last Mile & TTL being as ISP provider.
• 2 STM/310 Mbps BW on Primary & 2 STM/310 Mbps on secondary ILL link. ( Primary & secondary )

• Any point of time both primary & secondary ILL BW will be available at ISP gateway.
• Expect Dual redundancy on Last Mile media & two Transmission path from ISP.
Sub-header 1
• Customer will provide their own PF sense FW and the same to be used as DLM ILL termination device as CE CPE.

• Customer to ensure and provide His own FW as CPE has min 2 WAN and 1 LAN interface and must support eBGP protocol and its configurations
• Customer will use TTL provided IPV4 schema only.
Sub-header 2
• Customer will manage their own SW, FW & LAN traffic & LAN Management by themselves.
• Customer want single static LAN ( 64 IP pool - /26 IPV4 ) routable IP pool towards their LAN network.
• Customer to share his LAN schematic diagram for better understanding of connectivity.
TTL Sales & Feasibility: Sub-header 3

• TTL Sales SPOC to check for feasibility for primary and secondary links & BW and respective commercial approvals accordingly.

• For TTL link and TCL last mile feasibility, both last miles to be independent in fiber routes along with the route diagram from feasibility team to be
shared and commercial approval accordingly.
2 Presentation Title to come here
 TTL Solution Proposition & Highlights ( Active-Active )
✓ Its TTSL as single ISP with two different Last mile media with two different path only.
✓ As per Regional Feasibility Availed - Preferred Options of 2 different Tx LM to be @ TTL Fiber & @ TCL Fiber only.
✓ PE-CE Protocol will be e-BGP.
✓ TTL team will configure PE with 2 eBGP peering sessions with TTL IPV4 Pool & TTL Pvt ASN to run / configure eBGP- Active-Active
mode only.
✓ Customer will provide / extend support to TTL SOC/MCPE team till their own CPE as FW with 2 WAN and 1 LAN interface with eBGP
support and BW throughput support with his OEM team support to one time eBGP Active-Active configuration.
✓ Customer and TTL NOC & MCPE SOW: There shall be two TTL ILL circuits with two e-BGP sessions ( on 2 set of /30 WAN subnets )
with single routable /26 LAN static IP pool to be configured at Customer own FW as DLM link CE CPE. ( Additional Commercial
Involved for 48 Additional LAN Static IPs )
✓ Customer SOW : CE CPE ( FW ) – to be configured with static LAN IPV4 pool ( as Single TTL LAN /26 routable static IP pool ) which to
be further sub divided into two subnets.
✓ Customer SOW : CE end CPE shall advertise the supernet which contains all IP Addresses on both circuits.
✓ Customer SOW : should take care and configure the TTL provided /26 LAN static routable IP addresses for his applications from both
subnets & supernet so that customer end traffic priority via both ILL links shall get load-balanced from customer end CPE and based
on customer LAN network traffic prioritization and push only.
✓ Default route shall be advertised on both ILL link.
✓ Only one prefix per subnet to be allowed and to be added in both the links. ( any prefix added must be there for both the links )
✓ Both the ILL link at TTL PE will be always at ON conditions only.

Continued in next slide ………

3 Presentation Title to come here
# Need customer concurrence & signoff as per discussion ,SOW & solution designed
TTL Solution Proposition & Highlights ( Active-Active )

✓ TTL SOW: Both WAN Links monitoring & eBGP Routing part only.
✓ Customer SOW – Customer FW as their OWN CPE and LAN network configurations and LAN traffic.
✓ Post One time configuration as above - Customer to extend Read only, ICMP and SNMP access of his FW WAN interfaces to TTL
MCPE team for DLM as WAN managed service.
✓ Customer should not change any eBGP configuration w r t routing part without prior intimation to TTL SOC/MCPE team.
✓ Customer to take care of his FW AMC, Licensing and Hardware ownership at his end with his OEM provider.
✓ Under Managed service pro-active monitoring will send auto triggered email to customer email ID if any link is down. Also our
Monitoring team will call the customer to verify the issue. There is no Auto ticket login, Customer can log the ticket for
troubleshooting.
✓ Customer to provide rack space and power to connect TTL Mux and ILL termination equipment’s under safe environment.
✓ This is TTL DLM service offerings only, cant be extended/mixed or used with any other ISP provider as per TTL solution.
✓ Customer not allowed/ cant advertise TTL IP pool on any other ISP as peering vice e versa ( No Deviation on Transit policy )
✓ Under Dual last mile, TTBS provides 2 independent ILL links as failover proposition with TTL SLA as attached.
✓ Anything not discussed are null and void and to be taken up as new requirement and subject to further validations only.

# If Customer CPE unable to configure the Active-Active configurations as per slide 3 highlighted points - then customer to revert back the
setup as for Active Passive scenario only as per other SDD shared for the same

4 Presentation Title to come here

# Need customer concurrence & signoff as per discussion ,SOW & solution designed
Solution Diagram Prototype ( A-A )

TTL INTERNET Cloud

& Core PE Router

Active -310 Mb-Primary Path- TTL Fiber Active-310 Mb-Secondary Path- TCL Fiber

TTL SOW: 2 Independent LM

with 2 Mux 2 ILL Termination up
to TTL & TCL Mux port. TTL-Mux @ Primary Last Mile Media TCL-Mux @ Secondary Last Mile Media
One time PE-CE eBGP config
with Customer and Further up
to WAN routing & monitoring
only Primary-WAN Intf-1 CPE FW /30 TTL WAN IP Secondary-WAN Intf-2 CPE FW TTL /30 WAN IP

Customer SOW: Customer FW &

LAN Network.
@ CPE FW LAN Interface - TTL /26 LAN static IPV4 Pool as single Subnet
1. Customer To extend one time eBGP configuration support at his
own FW.
2. Customer to provide 24/7 365 Days Read only, ICMP & SNMP
access to his FW WAN interfaces to TTL MCPE / SOC team. Customer Own FW-SW & LAN Network
3. Any change towards WAN network or configuration- customer to
proactively update TTL MCPE / NOC team with change mgmt.
request.
4. Customer hardware and licensing is customer responsibility.
Customer LAN Network
5 Presentation Title to come here
# Need customer concurrence & signoff as per discussion ,SOW & solution designed
 TTL SLA

TTSL offers its customers service level guarantee on each PORT subscribed. Following are the SLAs for
internet leased line (select applicable variant):

Table 1.0 Service Assurance

Latency
From TTSL IP POP (Delhi, Bangalore,
Peering Location Service Availability Packet Loss
Hyderabad, Chennai, Mumbai,
Ahmadabad, Kolkata)
All (within India) ≤ 80 ms
New York, USA ≤ 270 ms
Los Angeles, USA ≤ 300 ms
London, UK ≤ 180 ms
> 99.5% <1%
Hong Kong ≤ 125 ms
Singapore ≤ 80 ms
Malaysia ≤ 120 ms
Gulf ≤ 130 ms

## subject to final & Actual L2 feasibility availability for each ILL Link ## Need customer signoff

6 Presentation Title to come here

 DLM Fiber Route

TTL Fiber Route TCL Fiber Route

## As per feasibility confirmation Both are separate path and independent to each other.
7 Presentation Title to come here
Thank You!
#TimeToDoBig
www.tatatelebusiness.com