Cockroach Labs' cloud report measured AWS, GCP, and Azure, on CPU, network, and storage I/O,...
Gartner expects the slow down in WAN edge spending to be offset somewhat by increasing bandwidth...
“Clearly, Intel realizes that it needs breakthrough performance and efficiency to go up against...
In this blog post, CA Technologies will discuss five benefits that you can derive out of your...
Exablaze’s field programmable gate array-based devices play into Cisco’s intent-based...
In today's Tech Bytes episode, sponsored by Fortinet, we talk about how the company differentiates itself from competitors, including its ability to inspect TLS 1.3, its use of custom ASICs, and more.
The post Tech Bytes: Fortinet Taps ASICs To Accelerate SD-WAN (Sponsored) appeared first on Packet Pushers.
In Leaf/Spine VXLAN based data centers, everyone likes to provide HA with Active/Active in it, so choices are different. There are two types of HA in data centers, Layer 3 and Layer 2.
For layer 3 HA, always there is more than one spine that can provide ECMP and HA at same time. However, Layer 2 redundancy for hosts and l4-l7 services that connected to leafs are more than an easy choice. As Cisco provided vPC for nearly 10 years ago, almost this was the first (and only) choice of network engineers. Also, other vendors have their own technologies. For example, Arista provided Multi-chassis Link Aggregation (MLAG) for L2 HA in leafs. But, there is always a problem in implementation of them. One example in vPC is “peer-link” that is an important component in the vPC feature. However, it can be a tough one in most cases like Dynamic Layer-3 routing over vPC or Orphan members that may cause local traffic switching between vPC peers without using Fabric links.
To address the “peer-link” issue, there is a “fabric-peering” solution that uses Fabric links instead of “peer-link” and convert it to “virtual peer-link”. With this solution there is no concern Continue reading
Don’t make us make you: Members of a U.S. Senate committee recently told representatives of Facebook and Apple that they need to give police access to customers’ encrypted communications, or they will be forced to by Congress, the Washington Post reports. The companies told lawmakers that backdoors in encryption would be exploited by cybercriminals.
Facebook declines: Meanwhile, Facebook has refused a request from U.S. Attorney General William Barr to build encryption backdoors into WhatsApp and Messenger, the New York Times reports.
Women want to be included: As Internet access is growing in the central African country of Chad, women are demanding to be in on the action, Reuters reports. Women across sub-Saharan Africa are currently 15 percent less likely to own a mobile phone than men are and 41 percent less likely to use the mobile Internet, the story says.
Gigabit tech boom: Gigabit-speed Internet service is turning some small U.S. cities into tech centers, bringing businesses and jobs to the areas, Inc. says. The story looks at businesses taking advantage of gigabit-speed networks in Chattanooga, Tennessee, Melbourne, Florida, and Sarasota, Florida.
Arrested for reporting: Thirty journalists are currently in prison worldwide on charges related to Continue reading
On today's Network Break we analyze Cisco's new ASIC platform and the 8000 router series, dig into a string of AWS announcements related to networking and security, and discuss new products from Cato Networks and Silver Peak.
The post Network Break 265: Cisco Chips At Broadcom With New ASIC; AWS Gives Networking Some Love appeared first on Packet Pushers.
A long while ago I got into an hilarious Tweetfest (note to self: don’t… not that I would ever listen) starting with:
Which feature and which Cisco router for layer2 extension over internet 100Mbps with 1500 Bytes MTU
The knee-jerk reaction was obvious: OMG, not again. The ugly ghost of BRouters (or is it RBridges or WAN Extenders?) has awoken. The best reply in this category was definitely:
I cannot fathom the conversation where this was a legitimate design option. May the odds forever be in your favor.
A dozen “this is a dumpster fire” tweets later the problem was rephrased as:
Read more ...![]() |
Initial setup |
network:
version: 2
renderer: networkd
ethernets:
eth0:
dhcp4: no
eth1:
dhcp4: no
bridges:
br0:
addresses: [192.168.1.2/24]
gateway4: 192.168.1.1
interfaces:
- eth0
- eth1