Underlay

In this Network Collective short take, Eyvonne discusses the role of a sales engineer.  She highlights the value sales engineers can bring to enterprises and outlines some ways you can get the most out of your relationship with your vendor or VAR sales engineer.

In a new protocol deep-dive series, Nick Russo and Russ White return to discuss MPLS. In part one, we discuss the primary use cases for MPLS, label allocation, and what SD-WAN means for the future of MPLS.

Show Notes:

MPLS solves 3 fundamental problems, individually or in concert

Multi-tenancy/VPNs

Traffic engineering

Fast reroute

4 bytes in a shim header, technically not a label, but we call it that

20 bits for label value, 2^20 ~= 1 million values (this is important)

3 bits for EXP, QoS really

1 S-bit to signal bottom of stack

8 bits TTL

Label depth is theoretically infinite, but some HW platforms have a tolerance

Many ways to allocate labels

LDP transport

LDP pseudowire

BGP labeled unicast

BGP based IP VPNs (VPNv4/v6)

BGP pseudowire

SR (really built into OSPF and ISIS for distribution)

RSVP-TE

Some forward rules are worth mentioning (basic LDP/BGP-LU environment)

If route learned via IGP/static, LDP label must be used

If route learned via BGP, BGP label must be used

No exceptions

Penultimate Hop Popping: second to last hop removes topmost label when signaled with imp-null from last hop along a given LSP, saves a lookup

Is MPLS is a tunnel or not:

Nick says always

Russ says sometimes, depending on label depth

Dispel rumor: MPLS is a technology, not a service. It’s incorrect to ask “Will SD-WAN supplant MPLS?” This is akin to saying “Will pizza delivery service supplant water?” A more reasonable question would be “Will SD-WAN supplant private WANs?”

 

Outro Music:

Danger Storm Kevin MacLeod (incompetech.com)

Licensed under Creative Commons: By Attribution 3.0 License

http://creativecommons.org/licenses/by/3.0/

In a new protocol deep-dive series, Nick Russo and Russ White return to discuss MPLS. In part one, we discuss the primary use cases for MPLS, label allocation, and what SD-WAN means for the future of MPLS.

Show Notes:

1. MPLS solves 3 fundamental problems, individually or in concert
   1. Multi-tenancy/VPNs
   2. Traffic engineering
   3. Fast reroute
2. 4 bytes in a shim header, technically not a label, but we call it that
   1. 20 bits for label value, 2^20 ~= 1 million values (this is important)
   2. 3 bits for EXP, QoS really
   3. 1 S-bit to signal bottom of stack
   4. 8 bits TTL
3. Label depth is theoretically infinite, but some HW platforms have a tolerance
4. Many ways to allocate labels
   1. LDP transport
   2. LDP pseudowire
   3. BGP labeled unicast
   4. BGP based IP VPNs (VPNv4/v6)
   5. BGP pseudowire
   6. SR (really built into OSPF and ISIS for distribution)
   7. RSVP-TE
5. Some forward rules are worth mentioning (basic LDP/BGP-LU environment)
   1. If route learned via IGP/static, LDP label must be used
   2. If route learned via BGP, BGP label must be used
   3. No exceptions
6. Penultimate Hop Popping: second to last hop removes topmost label when signaled with imp-null from last hop along a given LSP, saves a lookup
7. Is MPLS is a tunnel or not:
   1. Nick says always
   2. Russ says sometimes, depending on label depth
8. Dispel rumor: MPLS is a technology, not a service. It’s incorrect to ask “Will SD-WAN supplant MPLS?” This is akin to saying “Will pizza delivery service supplant water?” A more reasonable question would be “Will SD-WAN supplant private WANs?”

 

In this Network Collective short take, Jordan Martin shares his thoughts on the recent announcement from Cisco that they will be offering disaggregated solutions. Has Cisco seen the light? Will Cisco abandon hardware completely? Or are the doing all of this for other reasons?

Related Episodes:

• Off the Cuff – Disaggregation
• Episode 18 – Whitebox Networking

Jordan Martin Host

The post Short Take – Cisco Disaggregation Announcement appeared first on Network Collective.

In this Network Collective short take, Jordan Martin shares his thoughts on the recent announcement from Cisco that they will be offering disaggregated solutions. Has Cisco seen the light? Will Cisco abandon hardware completely? Or are the doing all of this for other reasons?

Related Episodes:

* Off the Cuff – Disaggregation

* Episode 18

The operation and management of compute and networking are unique in the the tools and skill-sets required, but do they necessarily need to be? Dinesh Dutt joins Network Collective to talk about the divergence of compute and networking, how it hasn’t always been this way, and why he believes it should return to being a unified effort.

Dinesh Dutt Guest Russ White Host Jordan Martin Host Donald Sharp Host

Outro Music:
Danger Storm Kevin MacLeod (incompetech.com)
Licensed under Creative Commons: By Attribution 3.0 License
http://creativecommons.org/licenses/by/3.0/

The post History Of Networking – Dinesh Dutt – Divergence of Compute and Networking appeared first on Network Collective.

The operation and management of compute and networking are unique in the the tools and skill-sets required, but do they necessarily need to be? Dinesh Dutt joins Network Collective to talk about the divergence of compute and networking, how it hasn’t always been this way, and why he believes it should return to being a unified effort.

Outro Music:

Danger Storm Kevin MacLeod (incompetech.com)

Licensed under Creative Commons: By Attribution 3.0 License

http://creativecommons.org/licenses/by/3.0/

The need for resiliency in network infrastructure is almost a given, but how do you get there? John Herbert, Jody Lemoine and Pete Welcher join the Network Collective team to talk through the complexities involved in a highly available infrastructure.

 

We would like to thank Cumulus Networks for sponsoring this episode of Network Collective. Cumulus is offering you, our listener

The need for resiliency in network infrastructure is almost a given, but how do you get there? John Herbert, Jody Lemoine and Pete Welcher join the Network Collective team to talk through the complexities involved in a highly available infrastructure.

 

We would like to thank Cumulus Networks for sponsoring this episode of Network Collective. Cumulus is offering you, our listeners, a completely free O’Reilly ebook on the topic of BGP in the data center. You can get your copy of this excellent technical resource here: http://cumulusnetworks.com/networkcollectivebgp

 

John Herbert Guest Jody Lemoine Guest

From processors, to FPGAs, to ASICs, and back again, Tony Li joins Network Collective’s History of Networking to talk through the impact that the Cisco SSE and hardware switching has had on the networking industry.

Outro Music:

Danger Storm Kevin MacLeod (incompetech.com)

Licensed under Creative Commons: By Attribution 3.0 License

http://creativecommons.org/licenses/by/3.0/