Scalability Challenges and Solutions for Tier 1 Operator

1,323 views

Published on

by Marcelo Sarmento, NET Brazil

Published in: Technology, Travel, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,323
On SlideShare
0
From Embeds
0
Number of Embeds
282
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Scalability Challenges and Solutions for Tier 1 Operator

  1. 1. NET Brazil LDAP Implementation Marcelo Sarmento New Technology Manager, NET BrazilJune 10, 2010 Incognito Global User Conference 2010 1
  2. 2. About Brazil  Population: 193MM  8th largest economy in world(*)  Most of the economy indexes are improving  GDP is growing  So more people has access to Computers and services  Government has plans to bring Broadband access to 35MM people in the next 2 years (*) According to World BankJune 10, 2010 Incognito Global User Conference 2010 2
  3. 3. About Brazil – Telecom Market Pay -TV Broadband (Fixed) Voice (Fixed) Voice (Mobile)June 10, 2010 Incognito Global User Conference 2010 3
  4. 4. About NET Serviços  Company Background  Largest MSO in Latin America  93 operations  Main Brazilian Cities are covered São Paulo Guarulhos Rio de Janeiro Ponta Grossa Belo Horizonte Maceió Recife Joao Pessoa Brasília Vitória Manaus Vila Velha Curitiba Londrina Florianópolis Goiânia Porto Alegre CampinasJune 10, 2010 Incognito Global User Conference 2010 4
  5. 5. NET – Products  10,9MM Homes Passed  Pay-TV  Digital, HD, VOD (in progress)  Broadband  500K, 1M, 3M, 6M, 12M  30M, 60M, 100M (Docsis 3.0)  Voice (Fixed)  Product is offered in partnership with EmbratelJune 10, 2010 Incognito Global User Conference 2010 5
  6. 6. NET – Customers (x1000) Customers New adds Pay-TV Broadband Voice + 13% + 22% + 30% + 29% 3.690 3.776 3.645 2.882 2.882 2.988 2.662 44 86 2.790 2.790 106 2.489 2.557 105 3.480 92 92 68 166 2.605 185 2.605 185 2.286 3.347 203 133 2.452 153 2.452 153 2.217 235 2.058 228 3.071 276 2.217 235 2.059 1.802 256 2.059158 158 2.922 148 1.799 261 1.532 270 1.587 1.799 261 2.790 213 3.645 3.690 211 2.605 2.882 2.710 3.480 2.452 2.790 2.489 2.5572.561 3.347 1.587 211 164 2.452 2.217 2.605 416 2.286 149 2.058 3.071 2.059 2.217 1.117 86 2.923 164 1.7982.059 1.802 1.798 2.709 1.588 1.588 306 1.532 1.423 1.423 8112.475 2.561 1.116 190 811 1T08 2T08 3T08 4T08 1T09* 2T09* 3T09* 4T09* 6211T08 2T08 3T08 4T08 1T09 * 2T09* 3T09* 4T09* 1T10* 1T08 2T08 3T08 4T08 1T09* 2T09* 3T09* 4T09* 1T10* 1T08 2T08 3T08 4T08 1T09 * 2T09* 3T09* 4T09* 1T10* June 10, 2010 Incognito Global User Conference 2010 6
  7. 7. Implementation Challenges  Decentralized Architecture  No dedicated links between operations  But the billing system is centralized (IT requirement)  Communication between sites is done through Internet  Latency, packet loss, etc. are unpredictable  Will not fit for DHCP transactionsJune 10, 2010 Incognito Global User Conference 2010 7
  8. 8. Network DiagramJune 10, 2010 Incognito Global User Conference 2010 8
  9. 9. Why LDAP?  Well-known protocol  Proprietary and open implementations  Libraries  Browsers  Easy to customize and “extend”  LDAP isn’t a database, it’s a directory (RFC1777)!  Native “Replication” adds a lot of flexibilityJune 10, 2010 Incognito Global User Conference 2010 9
  10. 10. LDAP Basics  Stores attribute based data  Data generally read more than written to  No transactions dc=NET  No rollback  No “triggers” dc=Rio dc=Sao  Simple Operations  Hierarchical data structure dc=Mta dc=Modem  “Contexts” Mac=0000.0000.FF FF Mac=0000.0000.11 Mac=0000.0000.11 11 12June 10, 2010 Incognito Global User Conference 2010 10
  11. 11. LDAP Schema  Set of rules that describes what kind of data is stored  Helps maintain consistency and quality of data  Reduces duplication of data  Object class attribute determines schema rules the entry must follow  Required attributes  Allowed attributes  Schema is extensibleJune 10, 2010 Incognito Global User Conference 2010 11
  12. 12. LDAP Replication  Can create a Mirror for any branch of the tree  Except leaves  Master-Slave concept  Multi-Master is allowed  Data is replicated “on-the-fly”  Data Connection is TCP  Can be used on slow links  Robust when compared with UDP DHCPJune 10, 2010 Incognito Global User Conference 2010 12
  13. 13. “Distributed LDAP”June 10, 2010 Incognito Global User Conference 2010 13
  14. 14. DHCP – Docsis Network  Each Modem/MTA must receive an IP address  (DHCP)  Must receive a configuration File  (TFTP)  Operational parameters are in the inside TFTP File  Authentication/Authorization is done through DCHP  Controls who will receive an IP address  Configuration parameters are sent during DHCP transactionJune 10, 2010 Incognito Global User Conference 2010 14
  15. 15. DHCP – Docsis NetworkJune 10, 2010 Incognito Global User Conference 2010 15
  16. 16. Implementation  We decided to distribute the provisioning  DHCP Servers  TFTP, Time  DNS  Reuse of RFC1918 addresses  LDAP is local (every city has its own)  Data from master is replicated  Connection with the local DHCP is fast (LAN)  If local LDAP fails, we can redirect it to LDAP Master  Software  Using Sun Directory ServerJune 10, 2010 Incognito Global User Conference 2010 16
  17. 17. Implementation  One Object Class for each type of device dn: dn: docsismodemmacaddress="1,6,00:D0:37:35:BC:C8",dc= docsismodemmacaddress="1,6,00:19:5E:AB:17:40",dc=mta,dc virtua_poa_docsis =virtua_poa_docsis docsispolicyname: 64_1pc docsismodemmacaddress: 1,6,00:19:5E:AB:17:40 docsisassociatedisp: ACESSO GRATIS objectClass: mta docsisclientclass: Virtua_TV objectClass: top docsiscontrato: 1068939 docsisntel: 51-32080032 docsisdomainname: poa.virtua.com.br docsisntel: 51-32077455 docsisdownstreammaxbandwidth: 64 docsishostname: 043862 docsishostname: 1068939 docsisdomainname: pae.virtua.com.br docsisnode: A1D docsiscontrato: 710433266 objectClass: docsismodem docsisclientclass: MTA objectClass: top docsispolicyname: mta_2_line docsismodemmacaddress: 1,6,00:D0:37:35:BC:C8 DocsisCPEFixedIPAddr[n]=201.6.99.99 DocsisCPEFixedIPMask[n]=255.255.255.255 Easy to extend the ClassJune 10, 2010 Incognito Global User Conference 2010 17
  18. 18. Implementation  LDAP Fields are “mapped” to DHCPJune 10, 2010 Incognito Global User Conference 2010 18
  19. 19. Implementation  LDAP Fields can be “mapped” to Docsis File SettingsJune 10, 2010 Incognito Global User Conference 2010 19
  20. 20. Implementation Issues  Docsis doesn’t have a method to “push” a configuration  Request are always done by the Modem/MTA  If a configuration change occurs, you need to enforce it by resetting the Modem/MTA  Can be done through CMTS  But it’s a parallel process  As LDAP has no trigger mechanismJune 10, 2010 Incognito Global User Conference 2010 20
  21. 21. Business Benefits  Connection with the Billing is centralized  Simplifies IT design  Replication will do the distribution  Multiple access to LDAP  Operations  NOC  CRS  If the link fails, the local LDAP keeps the system  Updates are received when the link is restoredJune 10, 2010 Incognito Global User Conference 2010 21
  22. 22. Business Benefits  Provisioning is easier  Multiple DCHP servers can be pointed to one single LDAP Context  Don’t need to know “where” the customer is  Splits/Adds are simplified  Just add another DHCP server and choose the proper LDAP context  Easy to deploy  We did 35 new operations in 3 weeks (2006)June 10, 2010 Incognito Global User Conference 2010 22
  23. 23. Why Incognito Software?  Provisioning Solution requirements  Dynamic File Generation  Device Identification (using DHCP Option 60)  Automatic Software Upgrade using DHCP option 43.9 (RFC 1533, RFC 2132)  MTA device provisioning  We asked for LDAP Integration  Incognito developed it  Support for integration was expanded  Integration with DNS – Dynamic Updates  Needed for PacketCable VoiceJune 10, 2010 Incognito Global User Conference 2010 23
  24. 24. Next Challenges  Packetcable Hybrid Mode  Improve security  Use dynamic configuration files for MTA  IPV6  IPv4 addresses are getting short  Centralized Management  Easy to setup standards  License managementJune 10, 2010 Incognito Global User Conference 2010 24

×