#NetworkArchitecture

2025-05-16

⚙️ Inside Asterfusion’s 800G AI Switch Architecture

AI workloads demand ultra-high bandwidth and low latency. Asterfusion’s 800G switch architecture delivers both—with a focus on open hardware, precision timing, and energy-efficient design.

In this post, we cover:
🔸 Why 800G switching is critical for next-gen AI clusters
🔸 How Asterfusion’s design balances speed, scale, and sustainability
🔸 The use of Broadcom Jericho3-AI & Tomahawk5 chips
🔸 Why their disaggregated model matters for AI networking

🔗 Explore the full breakdown: cloudswit.ch/blogs/asterfusion

#800G #AISwitch #DataCenterNetworking #Asterfusion #Broadcom #OpenNetworking #HyperscaleAI #NetworkArchitecture

If you prefer centralization to segmentation,
If you prefer “cloud only” to cloud as a last resort,
If you prefer outsourcing your help desk to building tribal knowledge,
I’m not your huckleberry.

Why? Because...
I will tear your team apart.
I will deconstruct your team
and reconstruct your team.

As quickly as I can, I’ll replace the “cloud only” people with
people who value security over convenience, with
people who value security over lowest cost, with
people who value security over business as usual.

From Accounting to Marketing to Sales to Customer Care, every department will be involved in reviewing their part of the company’s data to determine what must be online, and what can be stored locally.

You will have a server room of your very own.
Your own IT personnel will hear the whirring of the servers’ fans.
I will replace some VPNs with more expensive dedicated circuits.
Some data will only be accessible by coming into the office.
In Customer Care, no single login will be able to access all customers’ sensitive information. Depending on the size of the company and call center, one Customer Care representative may only be able to access A-M, or A-G, or maybe even just A. If a cybercriminal phishes their login, that’s all the cybercriminal will get.

Everything will be backed up locally.
Everything.
Even what’s left in the cloud.
Yes, there will still be some data left in the cloud, like your store, where you sell stuff.
And there may still be some data off premise, in private cloud storage, on servers the company owns, rather than servers the company leases.
But, for the most part, the cybercriminal will have to enter the building to access the data.
Instead of having only one security mechanism (authentication), you will have two: authentication security plus location security.

If you can’t make a profit with this security model, one of two things are true.
Either
Your business model isn’t viable,
Or
You suck at running a business.

It has always been possible to run a profitable business without creating a global attack surface for your sensitive data.

The Cloud Sales Machine has done an incredibly effective job of convincing you
that if it’s not secure, it’s your fault,
that authentication is enough,
that cheap is just as good.

The Cloud Sales Machine has done a really, truly, amazingly, incredibly effective job with that last one: cheap.
It is rational for you to question whether your monthly subscription and service fees have gotten out of hand.
It is rational for you to be dismayed at the complexity of the pricing scheme, because it really is a scheme, carefully designed to hide the true cost in a swirling fog of mystery.

It is rational for you to think, “Maybe we could actually save money by pulling this in-house.”

But don’t lose sight of the objective.
The objective isn’t to do it the least expensive way possible.
The objective is to do it in a way that is secure, and still profitable.

If any of this makes sense to you,
I’m your huckleberry.

#CallMeIfYouNeedMe #FIFONetworks #cybersecurity #networkarchitecture

Someone recently asked me about the difference between network segmentation and data segmentation after I mentioned them in a post. Both are important. Sometimes you use one method, sometimes the other, and sometimes both. And then, karma. A perfect example of data segmentation appeared on my screen a day or two later, and now I’ll share it with you.

Here’s an example of data segmentation, possibly without network segmentation. See accompanying picture.

I have multiple websites with the same hosting company. The hosting company is offering me the option of merging all of my websites under one login. That would be convenient, but it’s less secure.

At the data level, a cybercriminal must authenticate on each of the websites separately, with separate 2FA. At the network level, I have no way of knowing if the web hosting company has segmented the infrastructure, and to what degree. For some companies, detailed knowledge of the hosting company’s physical architecture is essential to good security, but for me it doesn’t matter, since I have zero confidential information stored on, or accessible from, the web servers. The worst thing a cybercriminal can do to my websites is defacement or knocking them offline.

THE LESSON
As part of your risk assessment, consider both network segmentation and data segmentation. Everything that can be accessed from the same authentication credentials is in the same data segment. The most common weakness I uncover is in granting a single Administrator account too much access.

#CallMeIfYouNeedMe #FIFONetworks

#cybersecurity #NetworkArchitecture #DataArchitecture

Screenshot of notice on web hosting company’s site after I logged in. It says, “Do you have more than one login credential? You can merge them to have a single way of accessing all your accounts and products.” There is a button labeled, “Merge User ID.”

I just posted this controversial post on LinkedIn. Let the blocking begin. (It might happen here, too).

“Hi Bob, I hope that you're well! Do you do migrations? I’m looking for someone who can help me with migrating my <number redacted> employee company from <Cloud Provider Name Redacted> to <Cloud Provider Name Redacted> and help us avoid any gotchas, as we will still be hosting our production site on <Cloud Provider Name Redacted> for the time being. I'm realizing that paying an expert in this case will save time and opportunity. Thanks much!”

“<Name redacted>, thank you so much for thinking of me. In this instance, I’m not the right person for the job. I’d be the one to call if you wanted to migrate out of a commercial cloud service and maintain your operations in your own server room, or on your (owned) equipment in a private data center. You need someone with good knowledge of <Cloud Provider Name Redacted> cloud products. I studiously avoid an architecture that I consider fundamentally flawed.”

If the current chaos in the USA has caused you to realize that it’s important to keep local control of your IT operations, I’m the Network Architect/Engineer who can help you with that.

#CallMeIfYouNeedMe #FIFONetworks

#ProjectManagement #NetworkArchitecture #NetworkEngineering #Policy #CyberSecurity #InformationSecurity

A new Director asked me for help to quickly get a grasp of the network he was responsible for. I signed an NDA as part of the preparation for the engagement. Then the company sent me a purchase order, and we were ready to begin.

As we talked, I learned that he was the only in-house, on-the-payroll IT person. It was a hybrid system, both cloud and on-prem. The company was using a Managed Services Provider (MSP), and they provided two full-time, on site personnel. They did Help Desk support and any on-prem work that needed to be done in the server room.

“Okay,” I said, “ask them to give you a copy of the network diagram and send it to me. Then we’ll go over it together, and I’m sure I’ll have more questions, too.”

The two guys from the MSP couldn’t provide him with a network diagram. This MSP had been providing operations support for a couple of years. Both of the gentlemen from the MSP had been working on site for several months.

Soon, I was in a video conference with the Director and the two techs from the MSP. They didn’t like me much. I was always polite and respectful, but I kept asking questions they couldn’t answer. Someone at the MSP figured out that the account was in jeopardy and told the on-prem guys to cooperate with me. Things went much smoother after that.

THE LESSON
If you’re in IT upper management, ask your team for a network diagram. Even if the majority of your system is cloud-based, you’ve still got an Internet connection into the building, a firewall, and a distribution system. They should be able to provide this information instantly, and if they can’t, there are far bigger problems waiting to be discovered.

#CallMeIfYouNeedMe #FIFONetworks

#NetworkArchitecture #cybersecurity

True problem analysts do not like default solutions. Every solution to every problem needs to be independently derived. Underlying principles stand firm, but the methodologies and solutions are always in flux.

“Bob, what are you talking about?”

Well, here’s an example. A default solution to a wide array of problems today is, “We’ll spin up another VM in our cloud account.”

Stop. Analyze. Is the data appropriate for an Internet-accessible environment? What are the security requirements? Is that VM going to generate revenue, or save money, or… is it just an expense? Will the data be backed up? Will the environment be backed up? How does that affect the cost analysis?

Yesterday’s solution isn’t necessarily today’s solution. Work it out, each time, as a new problem – because it is.

#callmeifyouneedme #fifonetworks

#cybersecurity #networkarchitecture #systems #budget

Information storage centralization.
Information processing centralization.
Information management automation.
Remote systems operation.

These are the Four Horsemen (Famine, Plague, War, and Death) of the modern age.

Famine can be prevented.
Plague can be prevented.
War can be prevented.
Death can… well… okay, some things can’t be prevented.

The point here is that the very things we rely on – centralization, automation, and remote operation – can become problematic if they’re not managed well.

Segmentation, including microsegmentation, may be a better choice than centralization. And a lot of designs that are described as segmented really aren’t. For example, if a single user account can access or manage information across segments, it’s not segmented.

Centralization or Segmentation,
Automation or Manual Intervention, and
Remote or Local –
these things shouldn’t be assumed. Ask yourself the questions every time, and design the architectures and policies that are appropriate for each instance.

#callmeifyouneedme #fifonetworks

#cybersecurity #informationtechnology #networkarchitecture #policy

Dear Delta Airlines: You should bring me in as the consultant to restructure your IT Department and Information Systems.

#callmeifyouneedme #fifonetworks

#cybersecurity #informationtechnology #networkarchitecture #systems

2024-06-17

Understanding load balancing is key to modern network architecture. Explore the differences between Layer 4 and Layer 7 load balancing to see how each approach enhances performance, reliability, and scalability in distinct ways. #NetworkArchitecture #LoadBalancing #TechInsights #ITInfrastructure #L4 #L7 #Networking #TechTrends
relianoid.com/resources/knowle

Data sync and data backup: they’re not the same, and one may not be of any use after a ransomware attack. Here’s what you need to know, and how to avoid data loss.

fifonetworks.com/resources/bac

#callmeifyouneedme #fifonetworks

#cybersecurity #ransomware #informationsecurity #networkarchitecture

2024-01-16

𝐀𝐳𝐮𝐫𝐞 𝐍𝐞𝐭𝐰𝐨𝐫𝐤 𝐒𝐞𝐜𝐮𝐫𝐢𝐭𝐲 𝐋𝐚𝐛 𝐄𝐧𝐯𝐢𝐫𝐨𝐧𝐦𝐞𝐧𝐭 𝐃𝐞𝐩𝐥𝐨𝐲𝐦𝐞𝐧𝐭 𝐓𝐞𝐦𝐩𝐥𝐚𝐭𝐞 𝐰𝐢𝐭𝐡 𝐀𝐳𝐮𝐫𝐞 𝐏𝐫𝐞𝐦𝐢𝐮𝐦 𝐅𝐢𝐫𝐞𝐰𝐚𝐥𝐥

If you want to learn how Azure Firewall works in practice, including its applicability scenarios, use cases, and advanced features, this lab is for you. 🙂

This ARM deployment includes everything needed to test Azure Network Security components including the new Azure Firewall Premium:

github.com/Azure/Azure-Network

#azure #networksecurity #network #security #networking #cloud #cloudnative #cloudnetworking #Azurefirewall #firewall #vnet #hub #spoke #networkarchitecture #soc #cybersecurity

Do not disable IPv6.
Manage IPv6.
But do not disable it.

If you're a network architect, network engineer, or network administrator:
Master IPv6.

If you're not up to speed on IPv6, you're late, and it's time to wrap your arms around it.

Make it a personal and professional priority.

#networkadmin #networkengineering #networkarchitecture

Let’s talk about SD-WAN and MPLS.
I had lunch with a telecom and ISP services aggregator/seller the other day. His opinion is that MPLS is a legacy technology, rapidly being replaced by SD-WAN. That’s a long ways from accurate, and honestly I was kind of stunned. Since that type of thinking is out there, and apparently commonly believed, it’s time to inoculate you from SD-WAN hype with a dose of truth.

1) SD-WAN isn’t a protocol. It’s an overlay.
2) MPLS is a transport protocol.
3) SD-WAN can’t exist without transport protocols under it.
4) SD-WAN often uses more than one transport protocol. For example, broadband Internet service from an ISP is less expensive than MPLS. That’s why it’s common – very common – for an SD-WAN overlay to direct high priority traffic over an MPLS link, while directing traffic with lower security requirements or less stringent latency requirements over the cheaper broadband link.

Now let’s talk about that “legacy technology” perspective.
--Ethernet was in development for several years, but was standardized by the IEEE as 802.3 in 1983, so let’s call that its birthday and say that Ethernet is now 40 years old. It’s not considered a legacy technology because it's still very much in use.
--MPLS is an IETF standard. It’s first RFC was published in 2001, so it’s now 22 years old. And it’s not a legacy technology, either, because, like Ethernet, it’s still very much in use. In fact, various investment analyses are predicting the growth of MPLS over the next five years.

MPLS Growth, Quote 1:
According to Market Statsville Group:
“The global Managed MPLS market size is expected to grow from USD 55.6 million in 2021 to USD 97.9 million by 2030… Carriers have increased their network investment in response to the expansion of cloud-based mobile consumer services.” (Link in comments)

MPLS Growth, Quote 2
On it’s website, Cisco says, “Multiprotocol Label Switching (MPLS) enables Enterprises and Service Providers to build next-generation intelligent networks that deliver a wide variety of advanced, value-added services over a single infrastructure… SD-WAN can be seen as a software abstraction of MPLS technology that is applicable to wider scenarios…” (Link in comments)

Remember that I said that SD-WAN is an overlay? Cisco agrees. SD-WAN doesn’t replace MPLS. It gives you a convenient way to manage your transport resources – MPLS, broadband Internet, and other.

SUMMARY
SD-WAN gives you the ability to mix-and-match your data transport technologies for the best optimization of cost, QoS, and security.
SD-WAN gives you a convenient dashboard for monitor and control of your WAN resources.
SD-WAN is an overlay. It doesn’t replace any transport layer technology.
Broadband Internet and MPLS are two common transport technologies, each with advantages over the other.
Your SD-WAN solution probably incorporates MPLS, and you just don’t know it.

#callmeifyouneedme #fifonetworks

#networkengineering #networkarchitecture #mpls #sdwan

#introduction :

software engineer working with #python #django and #javascript, always interested in learning more about #networkarchitecture, #cybersecurity, democratic and decentralized tech &tc. also into decolonial #ecology and climate justice. like reading anarchist theory and baking in my free time.

read “desert” by anonymous 🌿

2022-11-13

Paul’s 3 laws of enterprise network troubleshooting…
1 - It’s a firewall issue
2 - It’s a routing issue
3 - It’s a cabling issue

There are no other types of issue

#EnterpriseIT #NetworkArchitecture

Jose M.jedipapi
2018-08-27

"Today, servers aren't even cattle, servers are insects connected over fast networks. Centralization is not only possible now, it's economical, it's practical, it's controlable, it's governable, it's economies of scalable, it's reliable, it's walled gardenable, it's monetizable, it's affordable, it's performance tunable...."


highscalability.com/blog/2018/

Client Info

Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst