Top Banner
UNIVERSITÀ DEGLI STUDI ROMA TRE Dipartimento di Informatica e Automazione Monitoring the Status of MPLS VPN and VPLS Based on BGP Signaling Information Giuseppe Di Battista Massimo Rimondini Giorgio Sadolfo IEEE/IFIP NOMS 2012 18/04/2012
270

Monitoring the Status of MPLS VPN and VPLS Based on BGP

Feb 12, 2022

Download

Documents

dariahiddleston
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Monitoring the Status of MPLS VPN and VPLS Based on BGP

UNIVERSITÀ DEGLI STUDI ROMA TRE

Dipartimento di Informatica e Automazione

Monitoring the Status of MPLS VPN and VPLS Based on BGP

Signaling Information

Giuseppe Di Battista Massimo Rimondini

Giorgio Sadolfo

IEEE/IFIP NOMS 2012

18/04/2012

Page 2: Monitoring the Status of MPLS VPN and VPLS Based on BGP

UNIVERSITÀ DEGLI STUDI ROMA TRE

Dipartimento di Informatica e Automazione

Monitoring the Status of MPLS VPN and VPLS Based on BGP

Signaling Information

Giuseppe Di Battista Massimo Rimondini

Giorgio Sadolfo

IEEE/IFIP NOMS 2012

18/04/2012

VPN VPLS MPLS

Page 3: Monitoring the Status of MPLS VPN and VPLS Based on BGP

UNIVERSITÀ DEGLI STUDI ROMA TRE

Dipartimento di Informatica e Automazione

Monitoring the Status of MPLS VPN and VPLS Based on BGP

Signaling Information

Giuseppe Di Battista Massimo Rimondini

Giorgio Sadolfo

IEEE/IFIP NOMS 2012

18/04/2012

VPN VPLS MPLS

Page 4: Monitoring the Status of MPLS VPN and VPLS Based on BGP

UNIVERSITÀ DEGLI STUDI ROMA TRE

Dipartimento di Informatica e Automazione

Monitoring the Status of MPLS VPN and VPLS Based on BGP

Signaling Information

Giuseppe Di Battista Massimo Rimondini

Giorgio Sadolfo

IEEE/IFIP NOMS 2012

18/04/2012

About MPLS VPNs/VPLS

Page 5: Monitoring the Status of MPLS VPN and VPLS Based on BGP

About MPLS VPNs/VPLS

Customer

Customer

NOMS 2012 - 18/04/2012

Page 6: Monitoring the Status of MPLS VPN and VPLS Based on BGP

About MPLS VPNs/VPLS

Customer site

Customer site

Customer site

Customer site

Customer site

NOMS 2012 - 18/04/2012

Page 7: Monitoring the Status of MPLS VPN and VPLS Based on BGP

ISP BB

About MPLS VPNs/VPLS

Customer site

Customer site

Customer site

Customer site

Customer site

NOMS 2012 - 18/04/2012

Page 8: Monitoring the Status of MPLS VPN and VPLS Based on BGP

ISP BB

About MPLS VPNs/VPLS

Customer site

Customer site

Customer site

Customer site

Customer site

NOMS 2012 - 18/04/2012

Page 9: Monitoring the Status of MPLS VPN and VPLS Based on BGP

ISP BB

About MPLS VPNs/VPLS

Customer site

Customer site

Customer site

Customer site

Customer site

NOMS 2012 - 18/04/2012

Page 10: Monitoring the Status of MPLS VPN and VPLS Based on BGP

ISP BB

About MPLS VPNs/VPLS

Customer site

Customer site

Customer site

Customer site

Customer site

NOMS 2012 - 18/04/2012

Page 11: Monitoring the Status of MPLS VPN and VPLS Based on BGP

ISP BB

About MPLS VPNs/VPLS

Customer site

Customer site

Customer site

Customer site

Customer site

NOMS 2012 - 18/04/2012

Page 12: Monitoring the Status of MPLS VPN and VPLS Based on BGP

ISP BB

About MPLS VPNs/VPLS

Customer site

Customer site

Customer site

Customer site

Customer site

NOMS 2012 - 18/04/2012

Page 13: Monitoring the Status of MPLS VPN and VPLS Based on BGP

ISP BB

About MPLS VPNs/VPLS

Customer site

Customer site

Customer site

Customer site

Customer site

NOMS 2012 - 18/04/2012

Page 14: Monitoring the Status of MPLS VPN and VPLS Based on BGP

ISP BB

About MPLS VPNs/VPLS

Customer site

Customer site

Customer site

Customer site

Customer site

NOMS 2012 - 18/04/2012

Page 15: Monitoring the Status of MPLS VPN and VPLS Based on BGP

ISP BB

About MPLS VPNs/VPLS

Customer site

Customer site

Customer site

Customer site

Customer site

NOMS 2012 - 18/04/2012

Page 16: Monitoring the Status of MPLS VPN and VPLS Based on BGP

ISP BB

About MPLS VPNs/VPLS

Customer site

Customer site

Customer site

Customer site

Customer site

NOMS 2012 - 18/04/2012

’s EtherSphere™

Page 17: Monitoring the Status of MPLS VPN and VPLS Based on BGP

About MPLS VPNs/VPLS

Page 18: Monitoring the Status of MPLS VPN and VPLS Based on BGP

About MPLS VPNs/VPLS

Page 19: Monitoring the Status of MPLS VPN and VPLS Based on BGP

About MPLS VPNs/VPLS

Page 20: Monitoring the Status of MPLS VPN and VPLS Based on BGP

About MPLS VPNs/VPLS

Page 21: Monitoring the Status of MPLS VPN and VPLS Based on BGP

About MPLS VPNs/VPLS

Page 22: Monitoring the Status of MPLS VPN and VPLS Based on BGP

About MPLS VPNs/VPLS

Page 23: Monitoring the Status of MPLS VPN and VPLS Based on BGP

About MPLS VPNs/VPLS

192.168.0.4

Page 24: Monitoring the Status of MPLS VPN and VPLS Based on BGP

About MPLS VPNs/VPLS

192.168.0.4

Page 25: Monitoring the Status of MPLS VPN and VPLS Based on BGP

About MPLS VPNs/VPLS

192.168.0.4

Page 26: Monitoring the Status of MPLS VPN and VPLS Based on BGP

About MPLS VPNs/VPLS

192.168.0.4

Page 27: Monitoring the Status of MPLS VPN and VPLS Based on BGP

About MPLS VPNs/VPLS

192.168.0.4

Page 28: Monitoring the Status of MPLS VPN and VPLS Based on BGP

About MPLS VPNs/VPLS

192.168.0.4

Page 29: Monitoring the Status of MPLS VPN and VPLS Based on BGP

State of the Art (in MPLS/VPLS monitoring)

NOMS 2012 - 18/04/2012

Page 30: Monitoring the Status of MPLS VPN and VPLS Based on BGP

State of the Art (in MPLS/VPLS monitoring)

NOMS 2012 - 18/04/2012

researc

h

monitoring

industr

y

Page 31: Monitoring the Status of MPLS VPN and VPLS Based on BGP

State of the Art (in MPLS/VPLS monitoring)

NOMS 2012 - 18/04/2012

researc

h

monitoring

control plane

industr

y

Page 32: Monitoring the Status of MPLS VPN and VPLS Based on BGP

State of the Art (in MPLS/VPLS monitoring)

NOMS 2012 - 18/04/2012

researc

h

monitoring

control plane

MPLS and VPLS

industr

y

Page 33: Monitoring the Status of MPLS VPN and VPLS Based on BGP

State of the Art (in MPLS/VPLS monitoring)

NOMS 2012 - 18/04/2012

industr

y

researc

h

technolo

gy

Page 34: Monitoring the Status of MPLS VPN and VPLS Based on BGP

State of the Art (in MPLS/VPLS monitoring)

industr

y

researc

h

technolo

gy

Page 35: Monitoring the Status of MPLS VPN and VPLS Based on BGP

State of the Art (in MPLS/VPLS monitoring)

IP Solution Center

Service Aware Manager

Service Activator Solution for VPN Services

Tivoli Network Manager

VPN Explorer

industr

y

researc

h

technolo

gy

Page 36: Monitoring the Status of MPLS VPN and VPLS Based on BGP

State of the Art (in MPLS/VPLS monitoring)

IP Solution Center

Service Aware Manager

Service Activator Solution for VPN Services

Tivoli Network Manager

VPN Explorer

industr

y

researc

h

technolo

gy

Page 37: Monitoring the Status of MPLS VPN and VPLS Based on BGP

State of the Art (in MPLS/VPLS monitoring)

NOMS 2012 - 18/04/2012

industr

y

researc

h

technolo

gy

Page 38: Monitoring the Status of MPLS VPN and VPLS Based on BGP

State of the Art (in MPLS/VPLS monitoring)

Routing convergence

Scalability

Monitoring

NOMS 2012 - 18/04/2012

industr

y

researc

h

technolo

gy

Page 39: Monitoring the Status of MPLS VPN and VPLS Based on BGP

State of the Art (in MPLS/VPLS monitoring)

Routing convergence D. Pei, J. Van der Merwe. BGP Convergence in Virtual Private Networks. Proc. IMC, 2006.

Scalability C. Kim, A. Gerber, C. Lund, D. Pei, S. Sen. Scalable VPN Routing via Relaying. Proc. SIGMETRICS, 2008.

Monitoring M. K. Thottan, G. K. Swanson, M. Cancone, T. K. Ho, J. Ren, S. Paul. SEQUIN: An SNMP-based MPLS Network Monitoring System. Bell Labs Technical Journal 8(1), 95–111, 2003.

NOMS 2012 - 18/04/2012

industr

y

researc

h

technolo

gy

Page 40: Monitoring the Status of MPLS VPN and VPLS Based on BGP

State of the Art (in MPLS/VPLS monitoring)

NOMS 2012 - 18/04/2012

industr

y

technolo

gy

researc

h

Page 41: Monitoring the Status of MPLS VPN and VPLS Based on BGP

State of the Art (in MPLS/VPLS monitoring)

SNMP

TIBCO Rendezvous Message Transport

Oracle DBMS

RCP, RSH

Telnet, SSH

TFTP, FTP

NOMS 2012 - 18/04/2012

industr

y

technolo

gy

researc

h

Page 42: Monitoring the Status of MPLS VPN and VPLS Based on BGP

State of the Art (in MPLS/VPLS monitoring)

SNMP

TIBCO Rendezvous Message Transport

Oracle DBMS

RCP, RSH

Telnet, SSH

TFTP, FTP

NOMS 2012 - 18/04/2012

industr

y

technolo

gy

researc

h

Page 43: Monitoring the Status of MPLS VPN and VPLS Based on BGP

State of the Art (in MPLS/VPLS monitoring)

SNMP

TIBCO Rendezvous Message Transport

Oracle DBMS

RCP, RSH

Telnet, SSH

TFTP, FTP

NOMS 2012 - 18/04/2012

industr

y

technolo

gy

researc

h

Page 44: Monitoring the Status of MPLS VPN and VPLS Based on BGP

NOMS 2012 - 18/04/2012

Our Contributions

Page 45: Monitoring the Status of MPLS VPN and VPLS Based on BGP

MPLS VPN/VPLS monitoring methodology

NOMS 2012 - 18/04/2012

Our Contributions

Page 46: Monitoring the Status of MPLS VPN and VPLS Based on BGP

MPLS VPN/VPLS monitoring methodology

Focus on monitoring

NOMS 2012 - 18/04/2012

+ provisioning

Our Contributions

Page 47: Monitoring the Status of MPLS VPN and VPLS Based on BGP

MPLS VPN/VPLS monitoring methodology

Focus on monitoring

NOMS 2012 - 18/04/2012

Our Contributions

Page 48: Monitoring the Status of MPLS VPN and VPLS Based on BGP

MPLS VPN/VPLS monitoring methodology

Focus on monitoring

NOMS 2012 - 18/04/2012

Observation of the network status

Our Contributions

Page 49: Monitoring the Status of MPLS VPN and VPLS Based on BGP

MPLS VPN/VPLS monitoring methodology

Focus on monitoring Observation of effects of network events

NOMS 2012 - 18/04/2012

Our Contributions

Page 50: Monitoring the Status of MPLS VPN and VPLS Based on BGP

MPLS VPN/VPLS monitoring methodology

Focus on monitoring Observation of effects of network events

• Reconfigurations • Failures

NOMS 2012 - 18/04/2012

Our Contributions

Page 51: Monitoring the Status of MPLS VPN and VPLS Based on BGP

MPLS VPN/VPLS monitoring methodology

Focus on monitoring Observation of effects of network events

• Reconfigurations • Failures

NOMS 2012 - 18/04/2012

Exhaustive analysis of observable effects

Our Contributions

Page 52: Monitoring the Status of MPLS VPN and VPLS Based on BGP

MPLS VPN/VPLS monitoring methodology

Focus on monitoring Observation of effects of network events

• Reconfigurations • Failures

NOMS 2012 - 18/04/2012

Instant snapshot of device states

Exhaustive analysis of observable effects

Our Contributions

Page 53: Monitoring the Status of MPLS VPN and VPLS Based on BGP

MPLS VPN/VPLS monitoring methodology

Focus on monitoring Observation of effects of network events

• Reconfigurations • Failures

NOMS 2012 - 18/04/2012

Instant snapshot of device states (Almost)

Exhaustive analysis of observable effects

Our Contributions

Page 54: Monitoring the Status of MPLS VPN and VPLS Based on BGP

MPLS VPN/VPLS monitoring methodology

Focus on monitoring Observation of effects of network events

• Reconfigurations • Failures

NOMS 2012 - 18/04/2012

Instant snapshot of device states + history (Almost)

Exhaustive analysis of observable effects

Our Contributions

Page 55: Monitoring the Status of MPLS VPN and VPLS Based on BGP

MPLS VPN/VPLS monitoring methodology

Focus on monitoring Observation of effects of network events

• Reconfigurations • Failures

Additional technologies required

NOMS 2012 - 18/04/2012

Instant snapshot of device states + history (Almost)

Exhaustive analysis of observable effects

Our Contributions

Page 56: Monitoring the Status of MPLS VPN and VPLS Based on BGP

MPLS VPN/VPLS monitoring methodology

Focus on monitoring Observation of effects of network events

• Reconfigurations • Failures

NOMS 2012 - 18/04/2012

Instant snapshot of device states + history (Almost) Standard technologies (BGP)

Exhaustive analysis of observable effects

Our Contributions

Page 57: Monitoring the Status of MPLS VPN and VPLS Based on BGP

MPLS VPN/VPLS monitoring methodology

Focus on monitoring Observation of effects of network events

• Reconfigurations • Failures

Requires access to devices

NOMS 2012 - 18/04/2012

Instant snapshot of device states + history (Almost) Standard technologies (BGP)

Exhaustive analysis of observable effects

Our Contributions

Page 58: Monitoring the Status of MPLS VPN and VPLS Based on BGP

MPLS VPN/VPLS monitoring methodology

Focus on monitoring Observation of effects of network events

• Reconfigurations • Failures

NOMS 2012 - 18/04/2012

Instant snapshot of device states + history (Almost) Standard technologies (BGP) Unobtrusive

Exhaustive analysis of observable effects

Our Contributions

Page 59: Monitoring the Status of MPLS VPN and VPLS Based on BGP

MPLS VPN/VPLS monitoring methodology

Focus on monitoring Observation of effects of network events

• Reconfigurations • Failures

Graphical visualization of VPN states

NOMS 2012 - 18/04/2012

Instant snapshot of device states + history (Almost) Standard technologies (BGP) Unobtrusive

Exhaustive analysis of observable effects

Our Contributions

Page 60: Monitoring the Status of MPLS VPN and VPLS Based on BGP

MPLS VPN/VPLS monitoring methodology

Focus on monitoring Observation of effects of network events

• Reconfigurations • Failures

Graphical visualization of VPN states

Extensive discussion on scalability vs visibility of (the effects of) network events

NOMS 2012 - 18/04/2012

Instant snapshot of device states + history (Almost) Standard technologies (BGP) Unobtrusive

Exhaustive analysis of observable effects

Our Contributions

Page 61: Monitoring the Status of MPLS VPN and VPLS Based on BGP

MPLS VPN/VPLS monitoring methodology

Focus on monitoring Observation of effects of network events

• Reconfigurations • Failures

Graphical visualization of VPN states

Extensive discussion on scalability vs visibility of (the effects of) network events Architecture, prototype, experimentation in Junosphere NOMS 2012 - 18/04/2012

Instant snapshot of device states + history (Almost) Standard technologies (BGP) Unobtrusive

Exhaustive analysis of observable effects

Our Contributions

Page 62: Monitoring the Status of MPLS VPN and VPLS Based on BGP

methodology Focus on monitoring Observation of effects of network events

• Reconfigurations • Failures

Graphical visualization of VPN states

Extensive discussion on scalability vs visibility of (the effects of) network events Architecture, prototype, experimentation in Junosphere

NOMS 2012 - 18/04/2012

Instant snapshot of device states + history (Almost) Standard technologies (BGP) Unobtrusive

Exhaustive analysis of observable effects

Discovery of a subtle anomaly in the routing software, confirmed by Juniper

Our Contributions

Page 63: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology

NOMS 2012 - 18/04/2012

Page 64: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology

NOMS 2012 - 18/04/2012

Collect signaling messages

Page 65: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology

NOMS 2012 - 18/04/2012

Reconstruct visibility of VPNs at PEs

Collect signaling messages

Page 66: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology

NOMS 2012 - 18/04/2012

Visualize VPN states

Reconstruct visibility of VPNs at PEs

Collect signaling messages

Page 67: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology

NOMS 2012 - 18/04/2012

Visualize VPN states

Reconstruct visibility of VPNs at PEs

Collect signaling messages

Page 68: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

Approach Drawback(s)

Monitor network traffic Undetermined in absence of traffic

Inject network traffic Intrusive; hard to tune

Watch router configurations Intrusive; access restrictions may apply

Watch router states Same as above + untimely

Notifications (e.g., SNMP) Additional technologies required

* Limited visibility of the effect of a configuration

Monitor signaling messages N/A

Page 69: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

Approach Drawback(s)

Monitor network traffic Undetermined in absence of traffic

Inject network traffic Intrusive; hard to tune

Watch router configurations Intrusive; access restrictions may apply

Watch router states Same as above + untimely

Notifications (e.g., SNMP) Additional technologies required

* Limited visibility of the effect of a configuration

Monitor signaling messages N/A

Page 70: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

Approach Drawback(s)

Monitor network traffic Undetermined in absence of traffic

Inject network traffic Intrusive; hard to tune

Watch router configurations Intrusive; access restrictions may apply

Watch router states Same as above + untimely

Notifications (e.g., SNMP) Additional technologies required

* Limited visibility of the effect of a configuration

Monitor signaling messages N/A

Page 71: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

Approach Drawback(s)

Monitor network traffic Undetermined in absence of traffic

Inject network traffic Intrusive; hard to tune

Watch router configurations Intrusive; access restrictions may apply

Watch router states Same as above + untimely

Notifications (e.g., SNMP) Additional technologies required

* Limited visibility of the effect of a configuration

Monitor signaling messages N/A

Page 72: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

Approach Drawback(s)

Monitor network traffic Undetermined in absence of traffic

Inject network traffic Intrusive; hard to tune

Watch router configurations Intrusive; access restrictions may apply

Watch router states Same as above + untimely

Notifications (e.g., SNMP) Additional technologies required

* Limited visibility of the effect of a configuration

Monitor signaling messages N/A

Page 73: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

Approach Drawback(s)

Monitor network traffic Undetermined in absence of traffic

Inject network traffic Intrusive; hard to tune

Watch router configurations Intrusive; access restrictions may apply

Watch router states Same as above + untimely

Notifications (e.g., SNMP) Additional technologies required

* Limited visibility of the effect of a configuration

Monitor signaling messages N/A

Page 74: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

Approach Drawback(s)

Monitor network traffic Undetermined in absence of traffic

Inject network traffic Intrusive; hard to tune

Watch router configurations Intrusive; access restrictions may apply

Watch router states Same as above + untimely

Notifications (e.g., SNMP) Additional technologies required

* Limited visibility of the effect of a configuration

Monitor signaling messages N/A

Page 75: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

Approach Drawback(s)

Monitor network traffic Undetermined in absence of traffic

Inject network traffic Intrusive; hard to tune

Watch router configurations Intrusive; access restrictions may apply

Watch router states Same as above + untimely

Notifications (e.g., SNMP) Additional technologies required

* Limited visibility of the effect of a configuration

Monitor signaling messages N/A

• Actual propagation of information

• Routing decisions @ PEs

Page 76: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

Approach Drawback(s)

Monitor network traffic Undetermined in absence of traffic

Inject network traffic Intrusive; hard to tune

Watch router configurations Intrusive; access restrictions may apply

Watch router states Same as above + untimely

Notifications (e.g., SNMP) Additional technologies required

* Limited visibility of the effect of a configuration

Monitor signaling messages N/A

Page 77: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

Approach Drawback(s)

Monitor network traffic Undetermined in absence of traffic

Inject network traffic Intrusive; hard to tune

Watch router configurations Intrusive; access restrictions may apply

Watch router states Same as above + untimely

Notifications (e.g., SNMP) Additional technologies required

* Limited visibility of the effect of a configuration

Monitor signaling messages N/A

Page 78: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

Approach Drawback(s)

Monitor network traffic Undetermined in absence of traffic

Inject network traffic Intrusive; hard to tune

Watch router configurations Intrusive; access restrictions may apply

Watch router states Same as above + untimely

Notifications (e.g., SNMP) Additional technologies required

* Limited visibility of the effect of a configuration

Monitor signaling messages N/A

Page 79: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

VPN signaling MPLS: BGP

VPLS:

NOMS 2012 - 18/04/2012

Autodiscovery Signaling Vendor

RFC 4762 (Kompella)

N/A LDP Cisco

RFC 4761 BGP BGP Juniper

Page 80: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

VPN signaling MPLS: BGP

VPLS:

NOMS 2012 - 18/04/2012

Autodiscovery Signaling Vendor

RFC 4762 (Kompella)

N/A LDP Cisco

RFC 4761 BGP BGP Juniper

BGP-based VPLS Autodiscovery

Page 81: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

VPN signaling MPLS: BGP

VPLS:

NOMS 2012 - 18/04/2012

Autodiscovery Signaling Vendor

RFC 4762 (Kompella)

N/A LDP Cisco

RFC 4761 BGP BGP Juniper

BGP-based VPLS Autodiscovery

LDP-BGP VPLS Interworking

Page 82: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

VPN signaling MPLS: BGP

VPLS:

NOMS 2012 - 18/04/2012

Autodiscovery Signaling Vendor

RFC 4762 (Kompella)

N/A LDP Cisco

RFC 4761 BGP BGP Juniper

BGP-based VPLS Autodiscovery

LDP-BGP VPLS Interworking

Page 83: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

VPN signaling MPLS: BGP

VPLS:

NOMS 2012 - 18/04/2012

Autodiscovery Signaling Vendor

RFC 4762 (Kompella)

N/A LDP Cisco

RFC 4761 BGP BGP Juniper

BGP-based VPLS Autodiscovery

LDP-BGP VPLS Interworking

Page 84: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

VPN signaling MPLS: BGP

VPLS:

NOMS 2012 - 18/04/2012

Autodiscovery Signaling Vendor

RFC 4762 (Kompella)

N/A LDP Cisco

RFC 4761 BGP BGP Juniper

BGP-based VPLS Autodiscovery

LDP-BGP VPLS Interworking

BGP is also...

Page 85: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

VPN signaling MPLS: BGP

VPLS:

NOMS 2012 - 18/04/2012

Autodiscovery Signaling Vendor

RFC 4762 (Kompella)

N/A LDP Cisco

RFC 4761 BGP BGP Juniper

BGP-based VPLS Autodiscovery

LDP-BGP VPLS Interworking

BGP is also... easy to set up scalable policy-aware

Page 86: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

VPN signaling MPLS: BGP

VPLS:

NOMS 2012 - 18/04/2012

Autodiscovery Signaling Vendor

RFC 4762 (Kompella)

N/A LDP Cisco

RFC 4761 BGP BGP Juniper

BGP-based VPLS Autodiscovery

LDP-BGP VPLS Interworking

BGP is also... easy to set up scalable policy-aware

Page 87: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

Customer site

Customer site

Customer site

Customer site

Customer site

NOMS 2012 - 18/04/2012

Page 88: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

Customer site

Customer site

Customer site

Customer site

Customer site

NOMS 2012 - 18/04/2012

BGP peerings

Page 89: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

Customer site

Customer site

Customer site

Customer site

Customer site

NOMS 2012 - 18/04/2012

BGP peerings

Page 90: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

Customer site

Customer site

Customer site

Customer site

Customer site

NOMS 2012 - 18/04/2012

BGP peerings

Page 91: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

Customer site

Customer site

Customer site

Customer site

Customer site

NOMS 2012 - 18/04/2012

BGP peerings

Page 92: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

Customer site

Customer site

Customer site

Customer site

Customer site

NOMS 2012 - 18/04/2012

BGP peerings

Page 93: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

Customer site

Customer site

Customer site

Customer site

Customer site

NOMS 2012 - 18/04/2012

BGP peerings

Mmmh... I’m a reflector-client

Page 94: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

Customer site

Customer site

Customer site

Customer site

Customer site

NOMS 2012 - 18/04/2012

BGP peerings

Page 95: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

Customer site

Customer site

Customer site

Customer site

Customer site

NOMS 2012 - 18/04/2012

BGP peerings

Page 96: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 1. Collection

Customer site

Customer site

Customer site

Customer site

Customer site

NOMS 2012 - 18/04/2012

BGP peerings

Page 97: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 2. Reconstruction of VPN state

NOMS 2012 - 18/04/2012

Page 98: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 2. Reconstruction of VPN state

NOMS 2012 - 18/04/2012

Page 99: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 2. Reconstruction of VPN state

NOMS 2012 - 18/04/2012

Page 100: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 2. Reconstruction of VPN state

NOMS 2012 - 18/04/2012

type (A/W)

Page 101: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 2. Reconstruction of VPN state

NOMS 2012 - 18/04/2012

NLRI NLRI NLRI

type (A/W)

Page 102: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 2. Reconstruction of VPN state

NOMS 2012 - 18/04/2012

Extended communities Extended

communities Extended

communities

NLRI NLRI NLRI

type (A/W)

Page 103: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 2. Reconstruction of VPN state

NOMS 2012 - 18/04/2012

RD prefix +

Extended communities Extended

communities Extended

communities

NLRI NLRI NLRI

type (A/W)

Page 104: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 2. Reconstruction of VPN state

NOMS 2012 - 18/04/2012

RD prefix +

CE ID

Extended communities Extended

communities Extended

communities

NLRI NLRI NLRI

type (A/W)

Page 105: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 2. Reconstruction of VPN state

NOMS 2012 - 18/04/2012

RD prefix +

CE ID

RT Extended

communities Extended

communities Extended

communities

NLRI NLRI NLRI

type (A/W)

Page 106: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 2. Reconstruction of VPN state

Exhaustive comparison of information from different BGP updates

NOMS 2012 - 18/04/2012

RD prefix +

CE ID

RT Extended

communities Extended

communities Extended

communities

NLRI NLRI NLRI

type (A/W)

Page 107: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 2. Reconstruction of VPN state

Example

NOMS 2012 - 18/04/2012

Page 108: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 2. Reconstruction of VPN state

Example

NOMS 2012 - 18/04/2012

Page 109: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 2. Reconstruction of VPN state

Example

NOMS 2012 - 18/04/2012

RD1 pfx1 + RT1

Page 110: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 2. Reconstruction of VPN state

Example

NOMS 2012 - 18/04/2012

RD1 pfx1 + RT1

RD1 pfx1 +

A

RT2

Page 111: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 2. Reconstruction of VPN state

Example

NOMS 2012 - 18/04/2012

RD1 pfx1 + RT1

RD1 pfx1 +

A

RT2

Page 112: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 2. Reconstruction of VPN state

Example

NOMS 2012 - 18/04/2012

RD1 pfx1 + RT1

RD1 pfx1 +

A

RT2

RD1 pfx1 + RT2

Page 113: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 2. Reconstruction of VPN state

Example

NOMS 2012 - 18/04/2012

RD1 pfx1 + RT1

RD1 pfx1 +

A

RT2

RD1 pfx1 + RT2

Changed VPN?

Reconfiguration?

Policy change?

Moved pfx1 to a different VPN?

Page 114: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 2. Reconstruction of VPN state

Apply the method to a sequence of BGP updates

NOMS 2012 - 18/04/2012

...

Page 115: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 2. Reconstruction of VPN state

Apply the method to a sequence of BGP updates

Reconstruct history of VPN visibility at each PE

NOMS 2012 - 18/04/2012

...

Page 116: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 2. Reconstruction of VPN state

A few difficulties:

NOMS 2012 - 18/04/2012

Page 117: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 2. Reconstruction of VPN state

A few difficulties: Investigation of the PE where the effect was first observed

Dealing with missing attributes in withdrawals

Inadmissible announcements [rfc4761]

Reannouncements

Synchronization with actual VPN states

Monitoring RC peering states

NOMS 2012 - 18/04/2012

Page 118: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 3. Visualization

Page 119: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 3. Visualization

Query: visibility at each PE of RD 12345:10011 prefix 172.16.110.0/30 RT 12345:111

Page 120: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 3. Visualization

Query: visibility at each PE of RD 12345:10011 prefix 172.16.110.0/30 RT 12345:111

time

PE

Page 121: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 3. Visualization

Query: visibility at each PE of RD 12345:10011 prefix 172.16.110.0/30 RT 12345:111

time

PE

BGP updates

Page 122: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 3. Visualization

Query: visibility at each PE of RD 12345:10011 prefix 172.16.110.0/30 RT 12345:111

time

PE

Page 123: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 3. Visualization

Query: visibility at each PE of RD 12345:10011 prefix 172.16.110.0/30 RT 12345:111

time

PE

visible

Page 124: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 3. Visualization

Query: visibility at each PE of RD 12345:10011 prefix 172.16.110.0/30 RT 12345:111

time

PE

visible

originated

Page 125: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 3. Visualization

Query: visibility at each PE of RD 12345:10011 prefix 172.16.110.0/30 RT 12345:111

time

PE

visible

originated

not visible

Page 126: Monitoring the Status of MPLS VPN and VPLS Based on BGP
Page 127: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Query: visibility at each PE of RD 12345:10011 prefix 172.16.110.0/30

Page 128: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Query: visibility at each PE of RD 12345:10011 prefix 172.16.110.0/30

...with RT 12345:111

Page 129: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Query: visibility at each PE of RD 12345:10011 prefix 172.16.110.0/30

...with RT 12345:111

...with RT 12345:222

Page 130: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Query: visibility at each PE of RD 12345:10011 prefix 172.16.110.0/30

...with RT 12345:111

...with RT 12345:222

Page 131: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Query: visibility at each PE of RD 12345:10011 prefix 172.16.110.0/30

...with RT 12345:111

...with RT 12345:222

Page 132: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Query: visibility at each PE of RD 12345:10011 prefix 172.16.110.0/30

...with RT 12345:111

...with RT 12345:222

Page 133: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Query: visibility at each PE of RD 12345:10011 prefix 172.16.110.0/30

...with RT 12345:111

...with RT 12345:222

Page 134: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Query: visibility at each PE of RD 12345:10011 prefix 172.16.110.0/30

...with RT 12345:111

...with RT 12345:222

Page 135: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Query: visibility at each PE of RD 12345:10011 prefix 172.16.110.0/30

...with RT 12345:111

...with RT 12345:222

Page 136: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Query: visibility at each PE of RD 12345:10011 prefix 172.16.110.0/30

...with RT 12345:111

...with RT 12345:222

Page 137: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Query: visibility at each PE of RD 12345:10011 prefix 172.16.110.0/30

...with RT 12345:111

...with RT 12345:222

Page 138: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Query: visibility at each PE of RD 12345:10011 prefix 172.16.110.0/30

...with RT 12345:111

...with RT 12345:222

Page 139: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Query: visibility at each PE of RD 12345:10011 prefix 172.16.110.0/30

...with RT 12345:111

...with RT 12345:222

Page 140: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 3. Visualization

Queries

Page 141: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 3. Visualization

Queries Check information propagation

• Input: RD+{prefix,CE ID}, RT

• Output: Visibility from all PEs

Page 142: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 3. Visualization

Queries Check information propagation

• Input: RD+{prefix,CE ID}, RT

• Output: Visibility from all PEs

Check a PE’s visibility of a specific VPN • Input: RT, PE

• Output: Visibility of all RD+{prefix,CE ID} with that RT at that PE

Page 143: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 3. Visualization

Queries Check information propagation

• Input: RD+{prefix,CE ID}, RT

• Output: Visibility from all PEs

Check a PE’s visibility of a specific VPN • Input: RT, PE

• Output: Visibility of all RD+{prefix,CE ID} with that RT at that PE

Highlight belonging of a prefix to a VPN • Input: RD+{prefix,CE ID}

• Output: Visibility of that RD+{prefix,CE ID} from all PEs, with each seen RT

Page 144: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 3. Visualization

Queries Check information propagation

• Input: RD+{prefix,CE ID}, RT

• Output: Visibility from all PEs

Check a PE’s visibility of a specific VPN • Input: RT, PE

• Output: Visibility of all RD+{prefix,CE ID} with that RT at that PE

Highlight belonging of a prefix to a VPN • Input: RD+{prefix,CE ID}

• Output: Visibility of that RD+{prefix,CE ID} from all PEs, with each seen RT

Highlight participation of PEs in VPNs • Input: RT

• Output: Visibility of that RT at each PE

Page 145: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 3. Visualization

Queries Check information propagation

• Input: RD+{prefix,CE ID}, RT

• Output: Visibility from all PEs

Check a PE’s visibility of a specific VPN • Input: RT, PE

• Output: Visibility of all RD+{prefix,CE ID} with that RT at that PE

Highlight belonging of a prefix to a VPN • Input: RD+{prefix,CE ID}

• Output: Visibility of that RD+{prefix,CE ID} from all PEs, with each seen RT

Highlight participation of PEs in VPNs • Input: RT

• Output: Visibility of that RT at each PE

*

*

*

Page 146: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 3. Visualization

Queries Check information propagation

• Input: RD+{prefix,CE ID}, RT

• Output: Visibility from all PEs

Check a PE’s visibility of a specific VPN • Input: RT, PE

• Output: Visibility of all RD+{prefix,CE ID} with that RT at that PE

Highlight belonging of a prefix to a VPN • Input: RD+{prefix,CE ID}

• Output: Visibility of that RD+{prefix,CE ID} from all PEs, with each seen RT

Highlight participation of PEs in VPNs • Input: RT

• Output: Visibility of that RT at each PE

*

*

*

* VPN≡RT

Page 147: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 3. Visualization

Queries Check information propagation

• Input: RD+{prefix,CE ID}, RT

• Output: Visibility from all PEs

Check a PE’s visibility of a specific VPN • Input: RT, PE

• Output: Visibility of all RD+{prefix,CE ID} with that RT at that PE

Highlight belonging of a prefix to a VPN • Input: RD+{prefix,CE ID}

• Output: Visibility of that RD+{prefix,CE ID} from all PEs, with each seen RT

Highlight participation of PEs in VPNs • Input: RT

• Output: Visibility of that RT at each PE

*

*

*

#

#

#

#

* VPN≡RT

Page 148: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Methodology 3. Visualization

Queries Check information propagation

• Input: RD+{prefix,CE ID}, RT

• Output: Visibility from all PEs

Check a PE’s visibility of a specific VPN • Input: RT, PE

• Output: Visibility of all RD+{prefix,CE ID} with that RT at that PE

Highlight belonging of a prefix to a VPN • Input: RD+{prefix,CE ID}

• Output: Visibility of that RD+{prefix,CE ID} from all PEs, with each seen RT

Highlight participation of PEs in VPNs • Input: RT

• Output: Visibility of that RT at each PE

*

*

*

#

#

#

#

* VPN≡RT # over time

Page 149: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability

Amount of routing updates

Page 150: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability

Routing table size

Amount of routing updates

Page 151: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability

Routing table size

Page 152: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability

Routing table size >> #Internet prefixes: ~ k 105

[Ben-Houidi et al. 07]

[Ben-Houidi et al. 07] Z. Ben-Houidi, R. Teixeira, and M. Capelle, “Origin of route explosion in virtual private networks,” in Proc. CoNEXT, 2007.

Page 153: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability

Routing table size >> #Internet prefixes: ~ k 105

[Ben-Houidi et al. 07] Only routing updates count

[Ben-Houidi et al. 07] Z. Ben-Houidi, R. Teixeira, and M. Capelle, “Origin of route explosion in virtual private networks,” in Proc. CoNEXT, 2007.

Page 154: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability

Routing table size >> #Internet prefixes: ~ k 105

[Ben-Houidi et al. 07] Only routing updates count Same scalability of [ORV], [BGPlay], [iBGPlay]

[Ben-Houidi et al. 07] Z. Ben-Houidi, R. Teixeira, and M. Capelle, “Origin of route explosion in virtual private networks,” in Proc. CoNEXT, 2007.

Page 155: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability

Amount of routing updates

[Ben-Houidi et al. 07] Z. Ben-Houidi, R. Teixeira, and M. Capelle, “Origin of route explosion in virtual private networks,” in Proc. CoNEXT, 2007.

Page 156: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability

Amount of routing updates Lots of customers, prefixes, VPNs, etc.

[Ben-Houidi et al. 07] Z. Ben-Houidi, R. Teixeira, and M. Capelle, “Origin of route explosion in virtual private networks,” in Proc. CoNEXT, 2007.

Page 157: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability

Amount of routing updates Lots of customers, prefixes, VPNs, etc. Bursts (due to, e.g., configurations changes,

faults) are unlikely

[Ben-Houidi et al. 07] Z. Ben-Houidi, R. Teixeira, and M. Capelle, “Origin of route explosion in virtual private networks,” in Proc. CoNEXT, 2007.

Page 158: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability

Amount of routing updates Lots of customers, prefixes, VPNs, etc. Bursts (due to, e.g., configurations changes,

faults) are unlikely 2-3 orders of magnitude less than VPN routes

[Ben-Houidi et al. 07]

[Ben-Houidi et al. 07] Z. Ben-Houidi, R. Teixeira, and M. Capelle, “Origin of route explosion in virtual private networks,” in Proc. CoNEXT, 2007.

Page 159: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability

Amount of routing updates Lots of customers, prefixes, VPNs, etc. Bursts (due to, e.g., configurations changes,

faults) are unlikely 2-3 orders of magnitude less than VPN routes

[Ben-Houidi et al. 07] Our prototype works even for M/L ISPs

[Ben-Houidi et al. 07] Z. Ben-Houidi, R. Teixeira, and M. Capelle, “Origin of route explosion in virtual private networks,” in Proc. CoNEXT, 2007.

Page 160: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 161: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 162: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 163: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 164: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 165: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 166: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 167: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 168: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 169: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 170: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 171: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 172: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 173: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 174: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 175: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 176: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 177: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 178: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Page 179: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 180: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 181: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 182: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 183: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 184: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 185: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 186: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 187: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 188: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 189: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 190: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Customer site

Customer site

Page 191: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Page 192: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Page 193: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Page 194: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Page 195: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

layer higher lower

Page 196: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

layer higher lower

scalability higher lower

Page 197: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

layer higher lower

scalability higher lower

visibility worse better

Page 198: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

layer higher lower

scalability higher lower

visibility worse better

Page 199: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

layer higher lower

scalability higher lower

visibility worse better

Page 200: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

layer higher lower

scalability higher lower

visibility worse better

Page 201: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Page 202: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

Page 203: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Scalability vs Visibility

beware of matching updates

Page 204: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Experimental Scenario

Page 205: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Experimental Scenario

ROUTE COLLECTOR

Page 206: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Experimental Scenario

ROUTE COLLECTOR

Page 207: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Experimental Scenario

ROUTE COLLECTOR

routing daemon

Page 208: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Experimental Scenario

local storage

ROUTE COLLECTOR

routing daemon

Page 209: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Experimental Scenario

local storage

ROUTE COLLECTOR

routing daemon

route retriever

Page 210: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Experimental Scenario

local storage

ROUTE COLLECTOR

routing daemon

route retriever

database

Page 211: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Experimental Scenario

visualization client

local storage

ROUTE COLLECTOR

routing daemon

route retriever

database

Page 212: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Experimental Scenario

visualization client

local storage

ROUTE COLLECTOR

routing daemon

route retriever

database

JFreeChart

Page 213: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Experimental Scenario

visualization client

local storage

ROUTE COLLECTOR

routing daemon

route retriever

database

JFreeChart

• advertise MP extensions for L2VPN

• dump relevant fields to MRT

Page 214: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Experimental Scenario

visualization client

local storage

ROUTE COLLECTOR

routing daemon

route retriever

database

JFreeChart

process L2VPN MP from MRTs

Page 215: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Experimental Scenario

visualization client

local storage

ROUTE COLLECTOR

routing daemon

route retriever

database

JFreeChart

max lag: 3mins

Page 216: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Experimental Scenario

visualization client

local storage

ROUTE COLLECTOR

routing daemon

route retriever

database

JFreeChart

max lag: 3mins

preliminary tests on Cisco routers

Page 217: Monitoring the Status of MPLS VPN and VPLS Based on BGP
Page 218: Monitoring the Status of MPLS VPN and VPLS Based on BGP
Page 219: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX

Page 220: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX

Page 221: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX

Page 222: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX

Page 223: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX

Page 224: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX

Page 225: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX

Page 226: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX

Page 227: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX

Page 228: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX

Page 229: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX VPLS

Page 230: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX

MPLS

Page 231: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX

Page 232: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX

Page 233: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX

Page 234: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX

Page 235: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX

Page 236: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX

Page 237: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX

Page 238: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Experiments

Injected events: (De+re)activation of customer sites RT change (De+re)activation of multihoming Local preference change in a multihoming configuration

NOMS 2012 - 18/04/2012

Page 239: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Experiments

Injected events: (De+re)activation of customer sites RT change (De+re)activation of multihoming Local preference change in a multihoming configuration

Timing Random order Varying rate ( [1/hr...100/min] )

NOMS 2012 - 18/04/2012

Page 240: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Experiments

Injected events: (De+re)activation of customer sites RT change (De+re)activation of multihoming Local preference change in a multihoming configuration

Timing Random order Varying rate ( [1/hr...100/min] )

> 150,000 collected BGP updates Processing time: < 20s, without optimizations

NOMS 2012 - 18/04/2012

Page 241: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX

Page 242: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX

Page 243: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX

Page 244: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX

Page 245: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX

Page 246: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX

Page 247: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX

Page 248: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX

Page 249: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX

Page 250: Monitoring the Status of MPLS VPN and VPLS Based on BGP

SEA

DEN

CHI

NYC

WAS

ATL

HOU

LAX

VPLS only!

Page 251: Monitoring the Status of MPLS VPN and VPLS Based on BGP

The Oscillation Problem

Did not affect forwarding

Page 252: Monitoring the Status of MPLS VPN and VPLS Based on BGP

The Oscillation Problem

Did not affect forwarding

Investigation with Juniper

Page 253: Monitoring the Status of MPLS VPN and VPLS Based on BGP

The Oscillation Problem

Did not affect forwarding

Investigation with Juniper

Best route selection in VPLS only considered VPLS control flags

site preference

PE router ID

Page 254: Monitoring the Status of MPLS VPN and VPLS Based on BGP

The Oscillation Problem

Did not affect forwarding

Investigation with Juniper

Best route selection in VPLS only considered VPLS control flags

site preference

PE router ID

ties were broken on most recent announcement (could carry updated labels)

Page 255: Monitoring the Status of MPLS VPN and VPLS Based on BGP

The Oscillation Problem

Did not affect forwarding

Investigation with Juniper

Best route selection in VPLS only considered VPLS control flags

site preference

PE router ID

ties were broken on most recent announcement (could carry updated labels)

DISAGREE [Griffin et al. 02]

[Griffin et al. 02] T. Griffin, F. B. Shepherd, and G. Wilfong, “The stable paths problem and interdomain routing,” IEEE/ACM Transactions on Networking, vol. 10, no. 2, pp. 232–243, 2002.

Page 256: Monitoring the Status of MPLS VPN and VPLS Based on BGP

The Oscillation Problem

Did not affect forwarding

Investigation with Juniper

Best route selection in VPLS only considered VPLS control flags

site preference

PE router ID

ties were broken on most recent announcement (could carry updated labels)

DISAGREE [Griffin et al. 02]

Fix (being) released

[Griffin et al. 02] T. Griffin, F. B. Shepherd, and G. Wilfong, “The stable paths problem and interdomain routing,” IEEE/ACM Transactions on Networking, vol. 10, no. 2, pp. 232–243, 2002.

Page 257: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Wrapping Up

NOMS 2012 - 18/04/2012

Page 258: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Wrapping Up

A monitoring methodology

NOMS 2012 - 18/04/2012

Page 259: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Wrapping Up

A monitoring methodology

NOMS 2012 - 18/04/2012

Effects

Page 260: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Wrapping Up

A monitoring methodology

NOMS 2012 - 18/04/2012

Effects Signaling

Page 261: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Wrapping Up

A monitoring methodology

NOMS 2012 - 18/04/2012

Effects Signaling MPLS+VPLS

Page 262: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Wrapping Up

A monitoring methodology

NOMS 2012 - 18/04/2012

Effects Signaling MPLS+VPLS Visualization

Page 263: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Wrapping Up

A monitoring methodology

NOMS 2012 - 18/04/2012

Effects Signaling MPLS+VPLS Visualization

Operation

Page 264: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Wrapping Up

A monitoring methodology

NOMS 2012 - 18/04/2012

Effects Signaling MPLS+VPLS Visualization

Operation Reconfiguration

Page 265: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Wrapping Up

A monitoring methodology

NOMS 2012 - 18/04/2012

Effects Signaling MPLS+VPLS Visualization

Operation Reconfiguration Troubleshooting

Page 266: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Wrapping Up

A monitoring methodology

Discussion on scalability vs visibility

NOMS 2012 - 18/04/2012

Effects Signaling MPLS+VPLS Visualization

Operation Reconfiguration Troubleshooting

Page 267: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Wrapping Up

A monitoring methodology

Discussion on scalability vs visibility

Architecture & prototype implementation

NOMS 2012 - 18/04/2012

Effects Signaling MPLS+VPLS Visualization

Operation Reconfiguration Troubleshooting

Page 268: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Wrapping Up

A monitoring methodology

Discussion on scalability vs visibility

Architecture & prototype implementation

Experimentation revealing routing anomaly

NOMS 2012 - 18/04/2012

Effects Signaling MPLS+VPLS Visualization

Operation Reconfiguration Troubleshooting

Page 269: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Future Work/Open Problems

Monitor other protocols/kinds of information

Collect non-best routes

Improve the visualization

Trigger alarms

Improve inference of event causes

NOMS 2012 - 18/04/2012

Page 270: Monitoring the Status of MPLS VPN and VPLS Based on BGP

Acknowledgments to

Thank you