O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.
Why Operators Need Optical Transport SDN
Apricot 2015
Peter Landon, Director Product Architecture
BTI Systems
Not Just Ano...
2
OpenFlow	
  controlled	
  Op.cal	
  Transport	
  mul.plies	
  the	
  
value	
  of	
  packet	
  only	
  SDN:	
  Service	
...
3
OpenFlow	
  controlled	
  Op.cal	
  Transport	
  mul.plies	
  the	
  
value	
  of	
  packet	
  only	
  SDN:	
  Service	
...
4
An	
  open	
  control	
  plane	
  including	
  the	
  transport	
  layer	
  
reduces	
  risk	
  of	
  dreaded	
  Vendor	...
5
Scale	
  mul.-­‐vendor,	
  mul.-­‐domain	
  networks.	
  
Op.cal	
  Transport	
  SDN:	
  
Why	
  is	
  it	
  important?	...
6
§  Provides	
  more	
  flexibility	
  for	
  migra.on	
  between	
  TDM	
  and	
  IP	
  services.	
  
–  PTN:	
  MPLS,	
...
7
Automated	
  Link	
  	
  
Provisioning	
  (BoD)	
  
Transport	
  SDN	
  will	
  
enable	
  business	
  
service	
  turn-...
8
–  Assumes	
  overcapacity	
  built	
  in	
  
via	
  unsaturated	
  links,	
  
produc.on	
  advance,	
  shared	
  
resto...
9
3-Degree 3-Degree
3-Degree
4-Degree
Colorless A/D ROADM
ROADM mesh
network
2-D
2-D
DC	
  B:	
  Op.cal	
  	
  
LSR	
  wit...
10
3-Degree 3-Degree
3-Degree
3-Degree
Colorless A/D ROADM
ROADM mesh
network
2-D
2-D
OF	
  Control	
  with	
  
Transport	...
11
§  Vendor	
  Lock-­‐in	
  
–  When	
  the	
  IP	
  and	
  the	
  op.cal	
  layers	
  do	
  not	
  share	
  a	
  common...
12
§  While	
  the	
  packet	
  switching	
  technologies	
  iden.fy	
  a	
  
signal	
  by	
  fields	
  in	
  the	
  packe...
13
§  Time	
  sensi.ve	
  and	
  repe..ve,	
  complex	
  func.ons	
  
don’t	
  play	
  well	
  in	
  a	
  centralized	
  ...
14
§  Goals	
  for	
  OAM	
  (ONF	
  CMWG	
  OAM	
  Specifica.on	
  0.5)	
  
–  Not	
  to	
  reinvent	
  OAM	
  protocols,...
15
OF	
  SWITCH	
  
-­‐  Configure	
  OAM	
  or	
  APS	
  object	
  outside	
  of	
  OF	
  switch	
  (via	
  NETCONF/YANG,	...
16
§  GMPLS:	
  
–  facilitates	
  LSPs	
  through	
  LSRs,	
  autonomously,	
  but	
  
§  in	
  prac.ce	
  is	
  usuall...
17
§  Many	
  large	
  Datacenter	
  operators	
  track	
  
router-­‐transport	
  connec.ons	
  with	
  
spreadsheets!	
 ...
18
§  Many	
  large	
  Datacenter	
  operators	
  track	
  
router-­‐transport	
  connec.ons	
  with	
  
spreadsheets!	
 ...
19
§  Customer	
  features	
  
–  Ability	
  to	
  control	
  the	
  network	
  assets	
  
and	
  services	
  they	
  ‘us...
20
§  Lowers	
  OPEX	
  through	
  reduced	
  opera.onal	
  
procedures,	
  with	
  a	
  unified	
  mul.-­‐layer	
  contro...
Próximos SlideShares
Carregando em…5
×
Próximos SlideShares
MORENA...!!!!
Avançar

2

Compartilhar

Optical Transport SDN by Peter Landon [APRICOT 2015]

A presentation given at the SDN Panel session of APRICOT 2015 on Tuesday, 3rd March 2015.

Livros relacionados

Gratuito durante 30 dias do Scribd

Ver tudo

Optical Transport SDN by Peter Landon [APRICOT 2015]

  1. 1. Why Operators Need Optical Transport SDN Apricot 2015 Peter Landon, Director Product Architecture BTI Systems Not Just Another SDN Presentation.
  2. 2. 2 OpenFlow  controlled  Op.cal  Transport  mul.plies  the   value  of  packet  only  SDN:  Service  Provisioning       Op.cal  Transport  SDN:   Why  is  it  important?   Router   Op.cal   Transport   Op.cal  channel  automa.cally   Provisioned  to  support  added     Router  ports     5x10GE   Op.cal   Transport   Router   OF  Controller   Port  configura.on   Under  SW  control   5x10G  PMD   5x10G  PMD   1  wavelength  of  OTU4  
  3. 3. 3 OpenFlow  controlled  Op.cal  Transport  mul.plies  the   value  of  packet  only  SDN:  Service  Provisioning     Op.cal  Transport  SDN:   Why  is  it  important?   Router   Op.cal   Transport   100G  PMD   Op.cal  channel  automa.cally   Provisioned  to  support  added     Router  ports     100G  PMD   Addi.onal     100GE   Op.cal   Transport   Router   OF  Controller   5x10G  PMD   5x10G  PMD   Port  configura.on   Under  SW  control   1  wavelength,  2  x  OTU4  
  4. 4. 4 An  open  control  plane  including  the  transport  layer   reduces  risk  of  dreaded  Vendor  Lock-­‐in.     Op.cal  Transport  SDN:   Why  is  it  important?   Router   Vendor  A   Op.cal   Transport   100G  PMD   Op.cal  channel  automa.cally   Provisioned  to  support  added     Router  ports     100G  PMD   Addi.onal     100GE   Op.cal   Transport   Router   OF  Controller   5x10G  PMD   5x10G  PMD   Port  configura.on   Under  SW  control   Vendor  B   Vendor  C   APP/Plugin   1  wavelength,  2  x  OTU4  
  5. 5. 5 Scale  mul.-­‐vendor,  mul.-­‐domain  networks.   Op.cal  Transport  SDN:   Why  is  it  important?   OF  Controller   CVNI   CDPI  
  6. 6. 6 §  Provides  more  flexibility  for  migra.on  between  TDM  and  IP  services.   –  PTN:  MPLS,  PBB,  VLAN,  Carrier  Ethernet   –  OTN:  Combines  TDM  and  packet,  FEC  for  extended  reach,     –  WDM:  highly  flexible  ROADM  layer  eliminates  unnecessary  OEO  conversions   §  Line  Interface  Standardiza.on   –  Coherent  Op.cs,  flexible  modula.on   –  FEC   Op.cal  Transport  SDN:   Packet  Op4cal  Convergence  
  7. 7. 7 Automated  Link     Provisioning  (BoD)   Transport  SDN  will   enable  business   service  turn-­‐up  with   dynamic,  hitless  L1   capacity  changes  using   ODUFlex   Dynamic  Configura.on   -­‐  Network  Slicing   -­‐  Network  as  a   Service   SDN  Controller   VPN  APP   Transport  SDN  Use  Case:   Data  Center  
  8. 8. 8 –  Assumes  overcapacity  built  in   via  unsaturated  links,   produc.on  advance,  shared   restora.on  resources   –  Assumes  a  ROADM  Mesh   topology   –  Important  Mouse  flows   maintain  priority,  but   Elephant  flows  can  be   orchestrated  to  automa.cally   “borrow”  resources.   VM   Migra.on   Transport  SDN  Use  Case:   Dynamic  Adjustment  of  Adjacencies  
  9. 9. 9 3-Degree 3-Degree 3-Degree 4-Degree Colorless A/D ROADM ROADM mesh network 2-D 2-D DC  B:  Op.cal     LSR  with  TDM   DC  A:  Op.cal  LSR   With  TDM   VM  migra.on  ini.ated  at  DC  A.  Flow  marking  indicates  elephant  flow,  and   traffic  shaping  begins.   OF  Control  without   Transport  Extensions   Transport  SDN  Use  Case:   Elephant  Flow  without  Transport  SDN  
  10. 10. 10 3-Degree 3-Degree 3-Degree 3-Degree Colorless A/D ROADM ROADM mesh network 2-D 2-D OF  Control  with   Transport  Extensions   DC  B:  Op.cal     LSR  with  TDM   DC  A:  Op.cal  LSR   With  TDM   Network  is  aware  of  addi.onal  capacity  (λ)  availability  and  will  u.lize  it  to  avoid   trampling  the  high  priority  mouse  flows.   Transport  SDN  Use  Case:   Elephant  Flow  Transport  SDN  
  11. 11. 11 §  Vendor  Lock-­‐in   –  When  the  IP  and  the  op.cal  layers  do  not  share  a  common   control  plane,  the  operator  is  forced  to  maintain  two   disparate  systems.  A  single  proprietary  system  locks  the   operator  into  a  single  vendor,  impac.ng  the  evolu.on  of   the  carrier’s  network.   Beyond  the  Use  Case:   Vendor  Lock-­‐in  
  12. 12. 12 §  While  the  packet  switching  technologies  iden.fy  a   signal  by  fields  in  the  packet  header,  circuit  switching   technologies  iden.fy  a  signal  by  its  posi.on  in  .me   or  frequency-­‐space,  similar  to  GMPLS.     §  the  Match  por.on  of  a  circuit-­‐switching  flow  entry   uses  the  signal-­‐type  (e.g.  ODU1,ODU2,  OCH)  and   loca.on  in  .me  (e.g.  array  of  tributary  slots)  or   loca.on  in  frequency-­‐spectrum  (e.g.  channel   number,  width)  to  iden.fy  the  ingress  signal.     So  How  Does  Transport  SDN  Work?   No  Packet  Header  
  13. 13. 13 §  Time  sensi.ve  and  repe..ve,  complex  func.ons   don’t  play  well  in  a  centralized  control  environment:   –  OAM  (Y.1731  MEP/MIP)   –  Protec.on  switching   –  OF  is  lacking  in  tools  to  accomplish  these  func.ons  (no   .mers,  response  issue  from  controller,  may  not  match  ITU   specified  SNCP  behavior)   §  Proposal  for  Autonomous  Func.ons:   –  Well  defined  func.on  that  is  referenced  in  a  MAT  (Match   Ac.on  Table)   What  about  OAM  and  Protec.on  Switching?   Special  Considera4ons  
  14. 14. 14 §  Goals  for  OAM  (ONF  CMWG  OAM  Specifica.on  0.5)   –  Not  to  reinvent  OAM  protocols,  leverage  what  exists   –  Ability  to  support  mul.ple  OAM  methods  to  go  inline  with   OAM  layering   –  The  OAM  support  needs  to  be  extensible     –  AF  needs  to  be  very  well  defined,  no  minor  differences  will   be  accepted.   –  Does  not  define  an  implementa.on   Autonomous  Func.ons   a  Monolithic  En4ty  
  15. 15. 15 OF  SWITCH   -­‐  Configure  OAM  or  APS  object  outside  of  OF  switch  (via  NETCONF/YANG,   RESTCONF,  etc)   -­‐  Associate  OF  AF  with  externally  configured  objects   -­‐  Internal  processes  are  not  addressable  individually   OpenFlow   Match  Pipeline   Flow  Table   Autonomous   Func.on   AF  Table   OpenFlow   Autonomous   Func.on   NETCONF  OBJ   NETCONF  +   YANG   Autonomous  Func.ons   Autonomous  Processes  
  16. 16. 16 §  GMPLS:   –  facilitates  LSPs  through  LSRs,  autonomously,  but   §  in  prac.ce  is  usually  single  layer  Implementa.on,  and   there  is  no  higher  level  awareness  of  the  network.   –  is  typically  not  available  across  different  vendors   –  consists  of  three  models:  Peer,  Overlay  and   Augmented.   §  (Transport)  SDN  is:   –  Mul.  Domain   –  Mul.  vendor   –  Mul.  layer   –  Programmable   GMPLS  is   predominately   implemented  as   an  overlay  model,   with  separate   control  of  IP  and   Transport   SDN  makes  use  of   distributed   network  OS   coordina.on   between  mul.ple   servers   SDN  vs.  GMPLS   Is  Transport  SDN  just  GMPLS  repackaged?  
  17. 17. 17 §  Many  large  Datacenter  operators  track   router-­‐transport  connec.ons  with   spreadsheets!   §  LLDP  is  a  possible  solu.on  but  requires   MAC  termina.on  which  may  be   unnecessary  on  the  transport  gear.   §  SDN  controller  will  have  knowledge  of   both  packet  layer  and  transport  layer   to  simplify  network  organiza.on.     Op.cal  Transport   What  are  Op.cal  Operators  are  Doing  now?   How  can  Transport  SDN  help?  
  18. 18. 18 §  Many  large  Datacenter  operators  track   router-­‐transport  connec.ons  with   spreadsheets!   §  LLDP  is  a  possible  solu.on  but  requires   MAC  termina.on  which  may  be   unnecessary  on  the  transport  gear.   §  SDN  controller  will  have  knowledge  of   both  packet  layer  and  transport  layer   to  simplify  network  organiza.on.     Op.cal  Transport   What  are  Op.cal  Operators  are  Doing  now?   How  can  Transport  SDN  help?   OF  Control  with   Transport  Extensions  
  19. 19. 19 §  Customer  features   –  Ability  to  control  the  network  assets   and  services  they  ‘use’   –  Ability  to  change  the  characteris.cs  of   the  IP  services  assigned     §  Service  Provider  features   –  No  “nailed-­‐up”  connec.ons  allow   op.miza.on  of  BW  alloca.on:  stat   muxing   –  Ability  to  assign  assets  to  individual   Customers   What  are  Op.cal  Operators  are  Doing  now?   Bandwidth  on  Demand   Network  Topology   Capacity  Planning   On-­‐Demand   Service  Provisioning   Performance  Monitoring   BGP  router   BGP  router   BGP  router   BGP  router  
  20. 20. 20 §  Lowers  OPEX  through  reduced  opera.onal   procedures,  with  a  unified  mul.-­‐layer  control  plane   §  Lowers  CAPEX  by  homogenizing  physical  network   resources  and  introducing  SW  control.   §  Network  slicing  and  visualiza.on  opens  revenue   opportuni.es.     §  Simplifies:  No  more  spreadsheets  mapping  router   ports  to  transport  ports,  and  hoping  you  got  it  right.   Summary   Why  do  Operators  Need  Transport  SDN?  
  • AlfredoHerreraEngMSc

    Mar. 2, 2016
  • ssuserd776c8

    Mar. 20, 2015

A presentation given at the SDN Panel session of APRICOT 2015 on Tuesday, 3rd March 2015.

Vistos

Vistos totais

669

No Slideshare

0

De incorporações

0

Número de incorporações

15

Ações

Baixados

0

Compartilhados

0

Comentários

0

Curtir

2

×