What is ASBR?

What is ASBR? Autonomous System Boundary Router. This seems easy, it is just used in OSPF, isn’t it?. In fact, that is wrong. You will learn in this post something, that is hopefully you will learn the first time. Let’s have a look at it.

ASBR is a node, that is connecting two or more networks. It can be a router or switch and it can be positioned at the Internet Edge. The router at the Internet Edge is referred to as IGW (Internet Gateway) Router and it can be an IGW Router.

It can be located between two different networks to provide MPLS service for example. Between two networks, service is referred to as Inter-AS MPLS VPNs and in RFC 2547, Section 10, 3 different Inter-AS MPLS VPN Options are explained. In all of them, the routers that are connecting two different Autonomous System is referred to as ASBR as well.

On those routers, usually, BGP runs in Inter-AS MPLS VPN service. OSPF is not mandatory.

Thus, saying it is used in OSPF would be a false claim. It can be used for many different services in the networks and ASBR can run any routing protocol, not just Continue reading

What Layer is MPLS?

What Layer is MPLS?. This basic question needs to be clarified for the Network Engineers.

MPLS – Multi-Protocol Label Switching first was invented for fast packet processing. As MPLS Label is 20 bits, and IP address is 32 bits, processing MPLS Label was considered faster back in old times.

Today, as of 2022 MPLS is used for many different purposes, one of the most common reasons to have MPLS in the Networks is VPN.

MPLS VPNs, MPLS Layer 2 VPN, and MPLS Layer 3 VPN are two of the most common VPN mechanisms in large Enterprise and Service Provider Networks.

The label is used for two reasons in MPLS VPNs.

A tunnel label or transport label is used for the reachability between the edge devices, PE devices in MPLS networks.

And another label, which is the VPN label is used to differentiate the customers in MPLS VPN.

Both of these labels are placed between MAC Header and IP Header in IP Packets.

Thus, as you can see from the below picture as well, MPLS is commonly referred to as Layer 2.5.

 

MPLS Layer 2.5

Figure – MPLS is Layer 2.5

 

As you can see, from the above Continue reading

Rust Notes: Tuples

A tuple is a sequence of values, which can be of different types. A tuple is defined with circle brackets (). Tuple Considerations The number of elements in a tuple is known as its arity. Traits are only implemented on a tuple with an arity of 12 or less. Tuples with an arity...continue reading

Rust Notes: Arrays

An array is a sequence of values, of the same type. A tuple is defined with square brackets []. Array Considerations Arrays live on the stack by default and have a fixed size. Traits are only implemented on an array with a size of 32 or less. Arrays with a size greater than 32 lose...continue reading

All is fair in and #NANOG Hackathons — refurbishing NAPALM drivers to build a multi-vendor…

All is fair in 💔 and #NANOG Hackathons — refurbishing NAPALM 🔥 drivers to build a multi-vendor #gNMI plug-in 🔌

Multi-vendor NAPALM driver based on gNMI

We’re in Austin, Texas this week where the 84th North American Network Operators Group (NANOG) convention is taking place. Preceding that, during the Super Bowl ⅬⅤⅠ weekend (in which another blue team is about to win big), there is a Hackathon in which the teams are challenged to prepare for the networking equivalent of an epic halftime show.

Yours truly figures it would be a good idea to use this opportunity to kick-off the creation of a multi-vendor NAPALM driver. Most (if not all) NAPALM drivers to date are single vendor, see for example the Nokia SR OS NAPALM driver and the SR Linux variant. However, there is significant overlap in functionality and logic, and so I’d like to see if there is a possibility to “share the burden” by collaborating on some of the more basic (and — quite frankly — boring) parts of the drivers.

My (rough) plan is to clone the best current NAPALM driver code base — eos has been suggested — remove whatever logic it uses to talk to its vendor specific device APIs, and replace that with pyGNMI. To demonstrate this Continue reading

Data center capex on the rise despite cloud momentum

Global capital expenditure on data center infrastructure is set to grow by 10% over the next five years, to a total of $350 billion by 2026, in spite of the general move toward cloud in the enterprise, according to a report released earlier this month by Dell’Oro Group.Part of that spending growth will be driven by hyperscalers like Google, Amazon and Microsoft buying up data center equipment for their own public clouds, but an underrecognized trend is that the cloud isn’t for every organization, according to the report’s author, research director Baron Fung.To read this article in full, please click here

Data center capex on the rise despite cloud momentum

Global capital expenditure on data center infrastructure is set to grow by 10% over the next five years, to a total of $350 billion by 2026, in spite of the general move toward cloud in the enterprise, according to a report released earlier this month by Dell’Oro Group.Part of that spending growth will be driven by hyperscalers like Google, Amazon and Microsoft buying up data center equipment for their own public clouds, but an underrecognized trend is that the cloud isn’t for every organization, according to the report’s author, research director Baron Fung.To read this article in full, please click here

Who Wants to Be Supported Forever?

I saw an interesting thread today on Reddit talking about using networking equipment past the End of Life. It’s a fun read that talks about why someone would want to do something like this and how you might find yourself in some trouble depending on your company policies and such. But I wanted to touch on something that I think we skip over when we get here. What does the life of the equipment really mean?

It’s a Kind of Magic

As someone that uses equipment of all kinds, the lifetime of that equipment means something different for me than it does for vendors. When I think of how long something lasts I think of it in terms of how long I can use it until it is unable to be repaired any further. A great example of this is a car. All of my life I have driven older used cars that I continue to fix over and over until they have a very high mileage or my needs change and I must buy something different.

My vehicles don’t have a warranty or any kind of support, necessarily. If I need something fixed I either fix it myself or Continue reading

The Next – And More Profitable – 10 Percent Of Server Share For AMD

When this is all said and done, Intel will deserve some kind of award for keeping its 14 nanometer processes moving along enough as it gets its 10 nanometer and 7 nanometer processes knocked together to still, somehow, manage to retain dominant market share in the server space. …

The Next – And More Profitable – 10 Percent Of Server Share For AMD was written by Timothy Prickett Morgan at The Next Platform.

Video: Network Layer Addressing

After a brief excursion into the ancient data link layer addressing ideas (that you can still find in numerous systems today) and LAN addressing it’s time to focus on network-layer addressing, starting with “can we design protocols without network-layer addresses” (unfortunately, YES) and “should a network-layer address be tied to a node or to an interface” (as always, it depends).

For more details, watch the Network Layer Addressing video (part of How Networks Really Work webinar).

Watch the video
You need Free ipSpace.net Subscription to watch the video, and the Standard ipSpace.net Subscription to register for upcoming live sessions.
1 … 573 574 575 576 577 … 3,841