Access Network Evolution

1. T-SP-02-I - Access Network Evolution

2. Housekeeping Notes
May 14, 2015

3. Thank you for attending Cisco Connect Toronto 2015, here are a few
housekeeping notes to ensure we all enjoy the session today.
§ Please ensure your cellphones / laptops are set on silent to ensure no
one is disturbed during the session
§ [Speaker Insert any special notes]
House Keeping Notes

4. § Give us your feedback and you could win
a Plantronics headset. Complete the
session survey on your Cisco Connect
Toronto Mobile app at the end of your
session for a chance to win
§ Winners will be announced and posted at
the Information desk and on Twitter at the
end of the day (You must be present to win!)
Complete your session evaluation – May 14th

5. § Cisco dCloud is a self-service platform that can be accessed via a browser, a high-speed
Internet connection, and a cisco.com account
§ Customers will have direct access to a subset of dCloud demos and labs
§ Restricted content must be brokered by an authorized user (Cisco or Partner) and then shared
with the customers (cisco.com user).
§ Go to dcloud.cisco.com, select the location closest to you, and log in with your cisco.com
credentials
§ Review the getting started videos and try Cisco dCloud today: https://dcloud-cms.cisco.com/help
dCloud
Customers now get full dCloud experience!

6. #CiscoSpark
Let’s continue this
conversation on…
Spark
Cisco’s mobile collaboration
team application
Visit the Collaboration booth in the
World of Solutions to join the
Connect Spark room

7. § Access Evolution
§ Next Generation EPN Architecture
§ Network Services Evolution
§ SDN Evolution
Agenda

8. Access Evolution

9. EPN Carrier Ethernet Architecture
Circuit Emulation + Ethernet
L3 IP + Services Placement
L2 Access
MPLS Access
nV Satellite
AccessMPLS-TP Access
Unified MPLS aggregation and core
UNI
MPLS-TP Aggregation
MPLS/IP
Distribution
Node
Aggregation
Node
Aggregation
Node
MPLS/IP
Distribution
NodeAggregation
Node
Aggregation
Node
9

10. The Need for Pre-Aggregation Networks
• Transition to MPLS Access
• MPLS at Cell Towers
• Need for better scale
• Isolated Domains
10
Transport
CPE / NT
100,000s–
1,000,000
Access
Nodes
10,000s–
100,000s
Distributio
n Nodes
100s–
1,000s
IP Edge
Nodes
10–100s
Core
Nodes
few–
10s
Aggregation
Nodes
1,000s–
10,000s
As MPLS moves into aggregation and access
number of nodes increases sharply

11. L2 Access – CE Architecture Overview
MPLS/IP
Distribution
Node
Aggregation
Node
Aggregation
Node
MPLS/IP
Distribution
NodeAggregation
Node
Aggregation
Node
E-Line (option 2) Circuit Emulation
E-LAN/E-Tree
E-Line (option 1) VPLS/ PBB-VPLS
EVPN/PBB-EVPN
L3VPN
Ethernet Port, 802.1q, qinq/.1ad
Ethernet Port, 802.1q, qinq/.1ad
Ethernet Port, 802.1q, qinq/.1ad
TDM, ATM
802.1ad/qinq
• Supported topologies: Ring, Cascaded Rings, Hub and Spoke
• Rings, Hub & Spoke: STP, REP or G.8032
• Hub & Spoke: MC-LAG, ICCP service multi-homing
802.1ad/qinq
PWE3, TDM
MPLS overlay using BVI
PWE3
L3VPN

12. MPLS Access – CE Architecture Overview
MPLS/IP
Distribution
Node
Aggregation
Node
Aggregation
Node
MPLS/IP
Distribution
NodeAggregation
Node
Aggregation
Node
E-Line, Circuit Emulation
E-LAN/E-Tree VPLS/ PBB-VPLS
EVPN/PBB-EVPN
L3VPN
Ethernet Port, 802.1q, qinq/.1ad
Ethernet Port, 802.1q, qinq/.1ad
Ethernet Port, 802.1q, qinq/.1ad
TDM, ATM
• IP/MPLS Domain Redundancy:
• LFA or Remote LFA
PWE3, TDM
PWE3
PWE3 L3VPNPWHE
PWE3 PWHE
PWHEPWE3 PWE3

13. Unified MPLS Transport – CE and MBH
• Core, Aggregation, and Access partitioned as independent IGP/LDP domains.
• Pre-Aggregation Nodes reduce size of routing & forwarding tables
– Ensure better Scalability and Faster convergence
– LDP used to build intra-domain LSPs
• BGP labeled unicast (RFC 3107) used as inter-domain label distribution protocol to build hierarchical
LSPs
Access
MPLS/IP
Access
MPLS/IP
Core
Core
Core
Core
Core Node
Core Node
Core Node
Core Node
Core Network
IP/MPLS
Aggregation Network
IP/MPLS
Aggregation Node
Pre-Aggregation
Node
Aggregation Network
IP/MPLS
Core
Node
Aggregation Node
Aggregation Node
Aggregation Node
Core
Node
Core
Node
Core
Node
Mobile
Transport GW
Mobile
Transport GW
Pre-Aggregation
Node
BUSS
BUSS
BUSSCSG
CSG
CSG
RAN IGP Process
OSPF/ ISIS
Aggregation Domain
(OSPFx/ISIS1) Core Domain
OSPF0/ISIS2
Aggregation Domain
(OSPFx/ISIS1)
RAN IGP Process
OSPF/ ISIS
LDP LSP ! LDP LSP ! LDP LSP ! LDP LSP ! LDP LSP !
iBGP (eBGP inter-AS) Hierarchical LSP!

14. The benefits of Unified MPLS
• An efficient MPLS transport architecture
• Virtualized to support many services on one infrastructure
• Relying on an intelligent hierarchy to scale to new challenges
• Enabling seamless operation for network and service resilience
• Separating transport from service operations with single touch point service
enablement and contiguous OAM and PM
• Integrating legacy access and transport on same infrastructure while limiting
legacy access investments in the access network

15. What Technologies Are Involved in Unified MPLS?
• RFC 3107 label allocation to introduce hierarchy for scale
• BGP Filtering Mechanisms to help the network learn what is needed,
where is needed and when is needed
• Flexible Access Network Integration options:
Labeled BGP Extension in Access
MPLS TP with Hierarchical LDP DOD control and dataplane
• Extended LFA FRR and BGP PIC for seamless high availability for the
intra and inter domain LSP convergence
• Contiguous and consistent transport and service OAM and Performance
Monitoring based on RFC-6374
• Virtualized L2/L3 Services Edge using VPWS/VPLS Access Interfaces

16. EPN Built-in Network High Availability
Remote Loop Free Alternate (RLFA)
EPN with Remote Loop
Free Alternate (RLFA)
Resiliency
3 simple lines to enable
99.999% with 50 ms
Multiservice, multi-topology
Simple
Multi-
service
50ms Cost
SONET/
SDH
Ethernet
STP
Ethernet
G.8032
MPLS-TE/
TP

17. Seamless Migration
EPN integrates with Legacy
VLAN
VLAN
Insert aggregation box, split big L2 domain
into isolated small L2 domains
- w STP/REP access gateway feature
2
Existing L2 based CE network. Big legacy
L2 domain
- VLAN, QinQ
- STP/MST, G.8032, REP, MCLAG
1
Smooth migration from L2 to MPLS per
each isolated L2 domain without impact the
rest of the network
Could migrate to MPLS over L2 overlay at
first, then to native MPLS
- with full MPLS over IRB feature
3
MPLS
VLAN VLAN
VLAN
MPLS
MPLS
VLAN
MPLS overlay
MPLS

18. Next Generation EPN
Architecture

19. EPN Evolution Objectives
Software
License
Portability
Customized
Reports
Simplified
Architecture with
Application
Engineered Routing
Service Agility
with Programmability
and Orchestration
Enhance Network
security at
multiple layers
Operational
Simplicity
Validate Overlay
solutions
Right-size
Purchase

20. EPN 5.0 Framework
Service
Orchestration
SDN
Interfaces
Packet
Transport
Optical
Transport
Services Ethernet
Mobile
Infrastructure
Business VPN &
Residential
Secure
Managed
Services
Data Center
Interconnect
BGP LS NC/Yang PCEP Configlets SNMP
EPN
Manager
ODL/OSC
Rapid Service Deployment Cloud Policer WAE
CSM
ME1200
ASR907
NG-CMTS
ASR920
ASR9000v
ASR903
ME4600
ASR9K
NCS6K
Sunstone
CSR1Kv
Physical Virtual
AER Routing, AER-TE, AER-LDP Interworking, BGP LU
Optical
IPoDWDM

21. EPN 5.0 Use Cases
Mobile Infrastructure
• Point to Multi-Point
Microwave Access
• Small cell Access
• Wi-Fi Access
• Clocking &
Synchronization
• Secure Mobile
Transport
Ethernet Services
• End-to-end MEF CE
2.0 services over agile
MPLS/AER transport
(tail-f, EPN Manager)
• Rapid service
deployment (RSD)
and Autonomic
Networking (AN)
Business & Residential
Services
• Service Agility using
automation (tail-f)
• Elastic Carrier Class
Virtual PE router &
virtual RR using IOS
XRv 9000.
AER Transport
• Resilient transport
with AER, AER-TE
and BGP LU node-
SID
• Validate LDP to AER
migration
ODL Apps
• Secure, Zero-touch
provisioning with
Rapid Service
Deployment
• WAN Automation
Engine for AER-TE
• Cloud domain policer

22. EPN 5.0 System
Data Center
NCS6008ASR9922
nV, AN, MPLS,
Ethernet
MPLS
(SR, LDP, BGP, mLDP, nV) Core
MPLS (SR, SRTE, mLDP, BGP)
AccessCE Preggregation
Internet
MPLS
(SR, LDP, BGP, mLDP)
ASR903
ASR9000v
ASR9010
ME4600
ASR9000v
ASR920
ASR901
Aggregation
ASR9006
ASR903
Service Edge
ASR9904
Internet
Gateway
DCI

23. EPN5.0 Management, Monitoring &
Provisioning
23
Secure
Powerful
Certificate
Authority (CA)
AAA Server
* Future Releases
Sunstone
CSR1000v
Powerful
EPN
Manager
ODL/OSC
Autonomic
Networking
• Secure
• Reliable
• Consistent
• Programmable
Complete

24. Summary
EPN Deployment Coverage
Layer 2 MPLS
IP/MPLS MPLS
MPLS
Layer 2
Layer 2
Layer 2 Ring Topology
Hub & Spoke Network
Compound Topology
MPLS MPLSIP/MPLS
Layer 3 Ring Topology
1) Operational Simplicity
2) Programmable Network
3) Zero Touch Deployment

25. EPN5.0 Overlay Layer
Registrar
Customer
Customer
Customer
Customer
Customer
ASR920
AR920
Customer
ASR902
Customer
Customer
Customer
Access
Ring 1
ASR902
ASR920
Access
Ring 1
Access
Ring 2
ASR9000
ASR9000
NCS/CRS
MPLS
ASR9000
Dark
Layer 2
Cloud
Router#configure terminal
Router(config)#autonomic registrar
Router(config-registrar)#domain-id cisco.com
Router(config-registrar)#whitelist disk:whitelist.txt
Router(config-registrar)#external-CA url <>
Router(config-registrar)#no shutGRE Tunnel with autonomic adjacency-discovery
Non AN
Non AN
ASR903
ASR901

26. EPN5.0 Overlay Layer
Registrar
Virtual
Registrar
Customer
Customer
Customer
Customer
Customer
ASR901
ASR920
AR920
Customer
ASR902
Customer
Customer
Customer
Access
Ring 1
ASR902
ASR920
ASR903
Access
Ring 1
Access
Ring 2
ASR9000
ASR9000
NCS/CRS
MPLS
ASR9000
Dark
Layer 2
Cloud

27. EPN5.0 Overlay Layer
ASR920
ASR920
ASR902
Customer
Customer
Customer
Access
Ring 1
ASR902
ASR920
Access
Ring 1
Access
Ring 2
ASR9000
ASR9000
NCS/CRS
MPLS
ASR9000
Non AN
Non AN
ASR903
ASR901
CSR1000v
AAA Server
TFTP
CA
Dark
Layer 2
Cloud
Virtual Machines
(VMs)
Config
--------
--------
Config
--------
--------
Config
--------
--------
Config
--------
--------
Config
--------
--------
Config
--------
--------
Config
--------
--------

28. Leverage SDN, PCE, Central Control
• The
network
is
simple,
highly
programmable
and
responsive
to
rapid
changes
• Source
Based
rou;ng,
label
pushed
in
the
source
will
decide
the
path.
• On
router,
PCE
Client
no
need
signaling
protocol
to
create
path,
just
Segment
Rou;ng.
• BeCer
than
PCE+RSVP-­‐TP,
on-­‐demand
signaling
the
path.
(*Please
check
slides
3)
• BeCer
than
Sta;c
MPLS
label
push
from
SDN,
SR
s;ll
have
ECMP,
Resilience,
FRR.

29. Segment Routing in Next Generation Architecture
Path expressed in the packetData
Dynamic path
Explicit path
Paths options
Dynamic
(STP computation)
Explicit
(expressed in the
packet)
Control Plane
Routing protocols with
extensions
(IS-IS,OSPF, BGP)
SDN controller
Data Plane
MPLS
(segment labels)
IPv6
(+SR header)

30. § Plug and Play Insertion with IP Unumbered
§ Static Pseudowire provisioning with SDN Controller ( tail-f)
§ Use of Anycast GW label
§ EVPN: Static PW as redundant Ethernet Virtual Segment
§ Inter-operability
Next Generation Architecture
Controller
Open API
Autonomic Network
Infrastructure
Service: Controller
Transport: Segment Routing
Auto-discovery

31. Core
Metro area
A
GW
GW
Tail-f
EPN
Manager
Next Generation Architecture: Plug-n-Play Node Insertion
A
A
Baseline requirement: Plug-n-Play node insertion
• New node can be pre-configured: loopback address, ISIS, SR.
• Require IP unnumbered interface feature, so doesn’t require re-configure the link ip address on the existing
nodes
Advanced requirement: zero-touch provisioning
• Require auto-discovery
Auto-discovery and initial auto-
configuration options
• Autonomic Networking
• Isis/ospf based auto-discovery
IP unnumbered
interface

32. CoreMetro1 Metro2
A B
GW21
1002
GW22
1002
GW11
1001
GW12
1001
Tail-f
EPN
Manager
Provision static PW label on both
access nodes and the GW nodes
PW label: 24001
ACE Service Architecture (2): L2VPN MP
A
CE1 CE2
EVPN Static PWStatic PW
BD
BD
BD
BD
Simple GW node redundancy solution
• Transport: anycast GW label
• EVPN: Static PW as redundant virtual Ethernet Segment
PW label: 24002
EVPNStatic PW
Static PW

33. Network Services are evolving

34. § xEVPN family introduces next generation
solutions for Ethernet services
§ BGP control-plane for Ethernet Segment and MAC
distribution and learning over MPLS core
§ Same principles and operational experience of IP
VPNs
§ No use of Pseudowires
§ Uses MP2P tunnels for unicast
§ Multi-destination frame delivery via ingress
replication (via MP2P tunnels) or LSM
§ Multi-vendor solutions under IETF
standardization
What is xEVPN?
E-LAN E-LINE E-TREE
EVPN
VPWS
EVPN
E-TREE
PBB-
EVPN
EVPN
Focus of Presentation

35. § Data Center Interconnect (DCI) requirements were not fully addressed by current
L2VPN technologies
§ Ethernet Virtual Private Network (EVPN) and Provider Backbone Bridging EVPN
(PBB-EVPN) designed to address these requirements
Next-Generation Solutions for L2VPN
§ Per-Flow Redundancy and Load Balancing
§ Simplified Provisioning and Operation
§ Optimal Forwarding
§ Fast Convergence
§ MAC Address Scalability

36. Solving VPLS Challenges for per-flow Redundancy
Next-Generation Solutions for L2VPN
• Existing VPLS solutions do not
offer an All-Active per-flow
redundancy
• Looping of Traffic Flooded from
PE
• Duplicate Frames from Floods
from the Core
• MAC Flip-Flopping over
Pseudowire
– E.g. Port-Channel Load-Balancing
does not produce a consistent
hash-value for a frame with the
same source MAC (e.g. non MAC
based
Hash-Schemes)
PE1
PE2
PE3
PE4
CE1 CE2
Echo !
PE1
PE2
PE3
PE4
CE1 CE2Duplicate !
M1
M1
M2
PE1
PE2
PE3
PE4
CE1 CE2
MAC
Flip-Flop
M1 M2

37. All Active Redundancy and Load Balancing
• All-Active Redundancy to maximize bisectional bandwidth
• Load-balance traffic among PEs and exploit core ECMP based on flow
entropy (flow can be L2/L3/L4 or combinations)
• Support geo-redundant PE nodes with optimal forwarding
• Flexible Redundancy Grouping of PEs
WAN
Site 1
Site 2
Site N
Flow-based Load
balancing
Flow-based Multi-pathing
Backdoor
Geo-Redundancy

38. All Active Redundancy and Load Balancing
• Active / Active Multi-Homing with
flow-based load balancing in CE to
PE direction
– Maximize bisectional bandwidth
– Flows can be L2/L3/L4 or
combinations
• Flow-based load balancing in PE to
PE direction
– Flows can be L2/L3/L4 or
combinations
– Multiple RIB entries associated for a
given MAC
P
E
P
E
P
E
P
E
Vlan X -
F1
Vlan X –
F2
Flow Based Load-balancing – CE to PE direction
P
E
P
E
P
E
P
E
Flow Based Load-balancing – PE to PE direction
Vlan X -
F1Vlan X –
F2
CE hashes
traffic towards
both local PEs
PE hashes
traffic towards
both remote PEs

39. All Active Redundancy and Load Balancing (Cont.)
• Flow-based Core Multi-Pathing
• Load balancing across equal cost
multiple paths in the MPLS core
• Load balancing at PE and P routers
based on MPLS Entropy labels
PE
PE
PE
PE
P
P
P
P
Flow Based Multi-Pathing in the CoreVlan X - F1
Vlan X –
F2Vlan X –
F3Vlan X –
F4
Load-balancing
at the P router

40. Solution Requirements
• Optimal forwarding for unicast and
multicast
• Shortest path – no triangular
forwarding at steady-state
• Loop-Free & Echo-Free Forwarding
• Avoid duplicate delivery of flooded
traffic
• Multiple multicast tunneling options:
– Ingress Replication
– P2MP LSM tunnels
– MP2MP
PE1
PE2
PE3
PE4
CE1 CE2
Echo !
PE1
PE2
PE3
PE4
CE1 CE2Duplicate !
CE1 CE2PE1
PE2
PE3
PE4Triangular
Forwarding!

41. Mac Address Scalability
• Server Virtualization fueling growth in MAC Address scalability:
– 1 VM = 1 MAC address.
– 1 server = 10’s or 100’s of VMs
• MAC address scalability most pronounced on Data Center WAN Edge for Layer 2
extensions over WAN.
– Example from a live network: 1M MAC addresses in a single SP data center
WAN
DC Site 1
DC Site 2
DC Site N
1K’s
10K’s
1M’s
N * 1M

42. Ethernet VPN
• Next generation solution for Ethernet
multipoint (E-LAN) services
• PEs run Multi-Protocol BGP to
advertise & learn Customer MAC
addresses (C-MACs) over Core
– Same operational principles of L3VPN
• Learning on PE Access Circuits via
data-plane transparent learning
• No pseudowire full-mesh required
– Unicast: use MP2P tunnels
– Multicast: use ingress replication over
MP2P tunnels or use LSM
• Under standardization at IETF – draft-
ietf-l2vpn-evpn
MPLS
PE1
CE1
PE2
PE3
CE3
PE4
VID 100
SMAC: M1
DMAC: F.F.F
BGP MAC adv. Route
EVPN NLRI
MAC M1 via PE1
Data-plane address
learning from Access
Control-plane address
advertisement / learning
over Core
C-MAC:
M2
C-MAC:
M1

43. PBB Ethernet VPN
• Next generation solution for Ethernet multipoint
(E-LAN) services by combining Provider
Backbone Bridging (PBB - IEEE 802.1ah) and
Ethernet VPN
• Data-plane learning of local C-MACs and
remote C-MAC to B-MAC binding
• PEs run Multi-Protocol BGP to advertise local
Backbone MAC addresses (B-MACs) & learn
remote B-MACs
– Takes advantage of PBB encapsulation to
simplify BGP control plane operation – faster
convergence
– Lowers BGP resource usage (CPU, memory)
on deployed infrastructure (PEs and RRs)
• Under standardization at IETF – WG draft:
draft-ietf-l2vpn-pbb-evpn
MPLS
PE1
CE1
PE2
PE3
CE3
PE4
B-MAC:
B-M1 B-M2
B-M2
BGP MAC adv.
Route
EVPN NLRI
MAC B-M1 via PE2
B-MAC:
B-M1
Control-plane address
advertisement /
learning over Core (B-
MAC)
Data-plane address
learning from Access
• Local C-MAC to local B-
MAC binding
Data-plane address
learning from Core
• Remote C-MAC to remote
B-MAC binding
PBB
Backbone
Edge Bridge
EVPN
PBB-EVPN PE
C-MAC:
MB
C-MAC:
MA

44. § xEVPN is next generation solution for Ethernet services
§ Relies on BGP control-plane for Segment / MAC learning reachability
among PEs
§ Same principles as L3VPNs
§ Benefits of xEVPN solutions
§ No signaling of PWs. Instead signals MP2P LSPs instead (ala L3VPN)
§ All-active CE multi-homing (per-flow LB)
§ Solution for P2P services uses a subset of EVPN routes
§ i.e. Per-EVI Ethernet Auto-Discovery route
§ Handles double-sided provisioning with remote PE auto-discovery
§ draft-boutros-l2vpn-evpn-vpws
EVPN VPWS for Next Generation E-Line Services
MPLS
PE1
CE1
PE2
CE2
ES1 ES2
VPWS Service Config:
EVI = 100
Local AC ID = ES1
Remote AC ID = ES2
VPWS Service Config:
EVI = 100
Local AC ID = ES2
Remote AC ID = ES1
BGP Ethernet Auto-
Discovery Route
EVPN NLRI
Ethernet Segment ES1
reachable via PE1 using MPLS
label X
BGP Ethernet Auto-
Discovery Route
EVPN NLRI
Ethernet Segment ES2
reachable via PE2 using MPLS
label Y
Provisioning Model
VPWS service configured to
advertise a local AC ID
(segment) and target a remote
AC ID

45. SDN Evolution in Access

46. Network APIs (REST) and Services Catalog
Resource Orchestration
Multi-Layer Control, Service Chaining and Policy
Enforcement
Controllers, Collectors
Netconf / Yang Data Models
nLight
IP+Optical
Virtualized Infrastructure
Programming and Managing of
Virtual Resources
Physical Infrastructure
Programming and Managing of
Physical Resources
Applications
Unified Service Delivery
CRSASR 9000ASR 903 M-series
Virtual PEVirtualized
IOS-XR
VMCisco nV
vGiLAN
VM
vFirewall
VM
vDPI
VM
vNAT
VM
vBNG
VM
vDDoS
VM
vSLB
VM
NCS 4000 NCS 6000
UCS
Intelligent, Ultra-Scalable NetworkArchitecture

47. § NETCONF – NETwork CONFiguration Protocol
§ Network Management protocol – defines management operations
§ Initial focus on configuration, but extended for monitoring operations
§ First standard - RFC 4741 (December 2006)
§ Latest rev is RFC 6241 (June 2011)
§ Does not define content in management operations
§ YANG – Yet Another Next Generation
§ Data modeling language to define NETCONF payload
§ Defined in the context of NETCONF, but not tied to NETCONF
§ Addresses gaps in SMIv2 (SNMP MIB language)
§ Previous failed attempt – SMI NG
§ First approved standard - RFC 6020 (October 2010)
N
E
T
C
O
N
F
YANG data
Common YANG
Models

48. ASR9K ASR9K
G8032 Layer2 Ring
MPLS over G8032 Ring
ASR903
ME4600
ASR903 ASR920
SDN
Controller
Netconf/Yang
Netconf/Yang
• Programmability through APIs
• Industry Standard API interface
• Custom Applications for Management & Customization ME1200

49. Operation Simplicity

50. § Network Elements Self-Provisioning
§ Service Provisioning and Turn Up verification
§ Services Maintenance and Troubleshooting
Operation Simplicity Requirements

51. Auto-IP
Self assigning IP address
Neighboring nodes and inserted
node negotiate physical link
addresses
2
Assign unique IP address to node
being inserted
1
Connectivity established to the new
node without manual intervention to
existing nodes
3
Autonomic
Network
Easy node insertion and IP address assignment in L3 rings
Auto-SLA
LLDP based Auto-IP
negotiation
Auto-IP

52. Autonomic Network
Secured Discovery and Configuration
Device auto-discovered by neighbors
and establishes secure configuration
channel
2
Device shipped from Cisco
manufacturing to branch with no
configuration
1
Device receives Configuration
Engine location and securely
registers
3
Zero-touch access auto-configuration
Auto-discovery and Secure
Configuration Channel
Configuration
Engine
Device downloads configurations
from Configuration Engine
4
Auto-IP Auto-SLA
Autonomic
Network

53. DNS
Server
DHCP
Server
Tftp serverDHCP Relay
On Management VLAN
ME1200
ME1200 ME1200
Router
G.8032
lldp
lldp
lldp
lldp
o LLDP has been implemented along with MED extensions (Media endpoint device) There is a Vendor TLV called
the Network policy TLV, where a VLAN can be specified.
o LLDP is not supposed to traverse beyond a single Hop. In Ring of NIDs scenario, we have done a proprietary
modification in the NIDs for this protocol.
Zero Touch provisioning with ME1200
LLDP-MED For management VLAN

54. Easy SLAverification
Ability to test end to end QoS for
service assurance
2
Traffic generation in network element
eliminate need for extra test
equipment
1
Remote device send the traffic back
to the source
3
Service turn up and verification without need for extra equipment
Source measures throughput, jitter,
and latency for SLA
4
Auto-IP
Autonomic
Network
Analytic and police engines collect
data from nodes for more detailed
analysis and take appropriate actions
5
PKT GEN
Traffic
Loopback
Throughput, Jitter,
Delay
Measurements
SLA
Report
Auto SLA

55. Thank You