In the world of ubiquitous Ethernet and IP, it’s common to think that one needs addresses in packet headers in every layer of the protocol stack. We have MAC addresses, IP addresses, and TCP/UDP port numbers… and low-level addresses are assigned to individual interfaces, not nodes.
Turns out that’s just one option… and not exactly the best one in many scenarios. You could have interfaces with no addresses, and you could have addresses associated with nodes, not interfaces.
In the world of ubiquitous Ethernet and IP, it’s common to think that one needs addresses in packet headers in every layer of the protocol stack. We have MAC addresses, IP addresses, and TCP/UDP port numbers… and low-level addresses are assigned to individual interfaces, not nodes.
Turns out that’s just one option… and not exactly the best one in many scenarios. You could have interfaces with no addresses, and you could have addresses associated with nodes, not interfaces.
Enterprise, law enforcement, and sports venue use expands, raising the need for IT infrastructure evaluation to support the resource-demanding systems.
After plenty of hours of studying and labbing the wide ranging topics on the JNCIE-DC blueprint, I took the JNCIE-DC lab exam and passed! I can proudly say I’m JNCIE-DC #389. In this conclusion of the previous JNCIE-DC blogs about my lab setup and about the remote lab environment, I will talk about my experience […]
This Tech Bytes podcast explores the network assurance and verification feature in VMware's vRealize Network Insight network monitoring software. This feature builds a real-time model of your production network by collecting information from switches, routers, firewalls, and other network devices. This model can then be used for testing changes, verifying reachability, improving troubleshooting, and more. VMware is our sponsor.
This Tech Bytes podcast explores the network assurance and verification feature in VMware's vRealize Network Insight network monitoring software. This feature builds a real-time model of your production network by collecting information from switches, routers, firewalls, and other network devices. This model can then be used for testing changes, verifying reachability, improving troubleshooting, and more. VMware is our sponsor.
We are happy to announce that the latest release of Calico Enterprise delivers unprecedented levels of Kubernetes observability! Calico Enterprise 3.5 provides full-stack observability across the entire Kubernetes environment, from application layer to networking layer.
With this new release, developers, DevOps, SREs, and platform owners get:
A live, high-fidelity view of microservices and workload interactions in the environment, with the ability to take corrective actions in real time
An easy-to-understand, action-oriented view that maintains correlations at the service, deployment, container, node, pod, network, and packet levels
Kubernetes context for easy filtering and subsequent analysis of traffic payloads
A Dynamic Service Graph representing traffic between namespaces, microservices, and deployments for faster problem identification and troubleshooting
An interactive display that shows DNS information categorized by microservices and workloads, to determine whether DNS is the root cause of application connectivity issues
The ability to customize the duration and packet size for packet capture
Application-level observability to detect and prevent anomalous behaviors
For more information, see our official press release.
Are you a Calico Cloud user? Not to worry—these same features are now available in Calico Cloud, too.
To learn more about new cloud-native approaches for establishing security and observability with Kubernetes, check Continue reading
We are happy to announce that the latest release of Calico Enterprise delivers unprecedented levels of Kubernetes observability! Calico Enterprise 3.5 provides full-stack observability across the entire Kubernetes environment, from application layer to networking layer.
With this new release, developers, DevOps, SREs, and platform owners get:
A live, high-fidelity view of microservices and workload interactions in the environment, with the ability to take corrective actions in real time
An easy-to-understand, action-oriented view that maintains correlations at the service, deployment, container, node, pod, network, and packet levels
Kubernetes context for easy filtering and subsequent analysis of traffic payloads
A Dynamic Service Graph representing traffic between namespaces, microservices, and deployments for faster problem identification and troubleshooting
An interactive display that shows DNS information categorized by microservices and workloads, to determine whether DNS is the root cause of application connectivity issues
The ability to customize the duration and packet size for packet capture
Application-level observability to detect and prevent anomalous behaviors
For more information, see our official press release.
Are you a Calico Cloud user? Not to worry—these same features are now available in Calico Cloud, too.
To learn more about new cloud-native approaches for establishing security and observability with Kubernetes, check Continue reading
The networking industry has had a bumper crop of startup companies including a few unicorns, new and novel solutions, and fresh standards-driven tech in the last decade. There’s been enough churn that you’d think the landscape would be unrecognizable from what it was ten years back. And yet, a dominant vendor supplying networks to enterprises remains Cisco.
Data networking folks sometimes wonder why Cisco remains such a dominant force after all these years. With all the churn in the industry, with all the fancy new products, companies and approaches, with the cloud changing how computing is done, and with software eating the world, there are many more options than Cisco to meet networking needs. Of course, Cisco has always had competition. Cisco’s never gotten 100% of the pie, but, depending on market segment, there’s rarely been a second juggernaut in the enterprise networking space. The choice has typically been between Cisco and everyone else.
But in 2021, the networking market is increasingly fragmented with more startups than I’ve even heard of chasing after slivers of the diverse networking pie. Sure, that impacts Cisco. Still, Cisco tends to dominate, even if their share isn’t quite what it was depending on which Continue reading
Service Mesh is quickly becoming a fact of life for modern apps, and many companies are choosing this method for their distributed micro-services communications. While most examples of service mesh focus only on the east-west aspect of app services communications and security, Tanzu Service Mesh aims at including the entire application transaction which includes both east-west as well as north-south communications in the mesh.
In previous blogs and articles (here and here ), we dug into the core construct of the system, called Global Namespace (GNS). GNS is the instantiation of application connectivity patterns and services. In the case we are describing here, one of these services consists of “northbound” access to the application in a resilient configuration through integration with a Global Server Load Balancing (GSLB) solution. In the current version of the service, we support the following integrations:
VMware NSX-ALB (aka avi networks) – VMware’s own complete software load balancing solution.
AWS Route 53 – AWS DNS service providing GSLB services for resiliency. This is useful for customers who do not own NSX-ALB.
In this first blog, we’ll describe how the solution works with AWS Route 53 and how to configure it. In a later post, we’ll Continue reading
One year into the COVID-19 pandemic, businesses and work are still online while the pressure on Internet ecosystems remains unprecedented. This has put the question of Internet resilience to the fore. As networks continue to struggle to cope with traffic spikes and connectivity hiccups, we examine how COVID-19 impacted some regional Internet ecosystems in 2020. […]
If the world was not a complex place, and if all machine learning training looked more or less the same, then there would only be one accelerator to goose training workloads. …
We are happy to announce that the latest release of Calico Enterprise delivers unprecedented levels of Kubernetes observability! Calico Enterprise 3.5 provides full-stack observability across the entire Kubernetes environment, from application layer to networking layer.
With this new release, developers, DevOps, SREs, and platform owners get:
A live, high-fidelity view of microservices and workload interactions in the environment, with the ability to take corrective actions in real time
An easy-to-understand, action-oriented view that maintains correlations at the service, deployment, container, node, pod, network, and packet levels
Kubernetes context for easy filtering and subsequent analysis of traffic payloads
A Dynamic Service Graph representing traffic between namespaces, microservices, and deployments for faster problem identification and troubleshooting
An interactive display that shows DNS information categorized by microservices and workloads, to determine whether DNS is the root cause of application connectivity issues
The ability to customize the duration and packet size for packet capture
Application-level observability to detect and prevent anomalous behaviors
For more information, see our official press release.
Are you a Calico Cloud user? Not to worry—these same features are now available in Calico Cloud, too.
To learn more about new cloud-native approaches for establishing security and observability with Kubernetes, check Continue reading
The Internet Society Elections Committee is pleased to announce the final results of the 2021 elections and the IETF selections for the Internet Society Board of Trustees. Voting concluded on 23 April. The results were announced to the voting communities and the challenge period was opened on 26 April. The deadline to file challenges was […]
The Docker community spans the four corners of the world. To celebrate the global nature of our community at DockerCon this year, we’ve created something new: Community Rooms.
Building on the learnings of our “regional rooms experiment” during our last Community All-Hands, Community Rooms are virtual spaces that DockerCon attendees will be able to join to discuss, share and learn about Docker in their own language and/or around a specific topic area.
100% LIVE
The main focus of these Community Rooms is to bring people together and encourage interaction so we have set them up to be 100% live. Yep, that’s right, all the content you’ll find in these rooms, whether they’re talks, demos, workshops, panel discussions etc. will be in real-time, all broadcast over a live Zoom link.
Hosted by the Community for the Community
Each Community Room will be overseen by Docker Captains and Community Leaders. They will be responsible for every aspect of the room, from the curation of content, to the management of the schedule, to the recruitment of the speakers, to the moderation of their room’s live chat.
There will be seven community rooms to choose from, each with one or Continue reading
Cisco has taken the wraps off a technology package it says will utilize existing core wireless and wired systems to help enterprises better control their physical environments and enable a safer, more secure return to the office.While supporting remote offices and branches of one—IDC says that post-COVID, more than 52% of workers will either remain remote or hybrid—they rest could return to an altered business space. Who’s selling SASE, and what do you get?
In these offices, sensors and devices that have been used to manage lighting and HVAC systems can be adapted to occupancy and density monitoring, air-quality testing, contact tracing, and in-room presence, according to Anoop Vetteth, vice president of product management with Cisco’s Enterprise Switching and Software Solutions group.To read this article in full, please click here
Cisco has taken the wraps off a technology package it says will utilize existing core wireless and wired systems to help enterprises better control their physical environments and enable a safer, more secure return to the office.While supporting remote offices and branches of one—IDC says that post-COVID, more than 52% of workers will either remain remote or hybrid—they rest could return to an altered business space. Who’s selling SASE, and what do you get?
In these offices, sensors and devices that have been used to manage lighting and HVAC systems can be adapted to occupancy and density monitoring, air-quality testing, contact tracing, and in-room presence, according to Anoop Vetteth, vice president of product management with Cisco’s Enterprise Switching and Software Solutions group.To read this article in full, please click here
There has been a land rush of sorts by storage OEMs over the past few weeks to roll out systems and services designed to help enterprises manage and process the huge amounts of data that is being created and stored throughout their widely distributed IT environments. …
In one of my introductory Segment Routing videos, I made claims along the lines of “Segment Routing totally simplifies the MPLS control plane, replacing LDP and local labels allocated to various prefixes with globally managed labels advertised in IGP”
It took two years for someone to realize the stupidity over-simplification of what I described. Matjaž Strauss sent me this kind summary of my errors:
You’re effectively claiming that SRGB has to be the same across all devices in the network. That’s not true; routers advertise SIDs and must configure label swap operations in case SRGBs don’t match.
Wait, what? What is SRGB and why could it be different across devices in the same network? Also, trust IETF to take a simple idea and complicate it to support vendor whims.
In one of my introductory Segment Routing videos, I made claims along the lines of “Segment Routing totally simplifies the MPLS control plane, replacing LDP and local labels allocated to various prefixes with globally managed labels advertised in IGP”
It took two years for someone to realize the stupidity over-simplification of what I described. Matjaž Strauss sent me this kind summary of my errors:
You’re effectively claiming that SRGB has to be the same across all devices in the network. That’s not true; routers advertise SIDs and must configure label swap operations in case SRGBs don’t match.
Wait, what? What is SRGB and why could it be different across devices in the same network? Also, trust IETF to take a simple idea and complicate it to support vendor whims.
