Broadcom is announcing a new version of its Trident II Ethernet switch chip family today, with one notable feature being improved performance for VXLAN and other tunneling protocols. The StrataXGS Trident-II+, a drop-in replacement for the Trident II, arrives as Broadcom tries to spread its Ethernet switch franchise into new areas. The recently announced StrataDNX Read more >
During a project recently, I was promptly reminded about the construction of Junos route export (i.e. route redistribution) policies. Specifically when filtering prefixes during the export/redistribution. The logic goes something like this:
a) Create prefix-list of prefixes to export
b) Create policy which references the protocol and prefix list to export
c) Attach policy to protocol
An example is here:
policy-options {
prefix-list CUST_A {
192.0.2.1/32;
}
policy-statement REDISTRIBUTE_STATICS_CUST_A {
/* FROM PREFIX-LIST TEST TO METRIC TYPE 1 FOR CUST A */
term 1 {
from {
prefix-list CUST_A;
}
to protocol ospf2;
then {
external {
type 1;
}
accept;
}
}
}
}
protocols {
ospf {
export REDISTRIBUTE_STATICS_CUST_A
area 0.0.0.0 {
interface x-x/x/x.x
}
}
}
With Junos export policies for routing, if you want to export more prefixes of the same type, adding an additional policy which also references the same protocol for the export will just not work. If you do the below, then you’re out of luck.
policy-options {
prefix-list CUST_A {
192.0.2.1/32;
}
prefix-list CUST_B {
192.0.2.2/32;
}
policy-statement REDISTRIBUTE_STATICS_CUST_A {
/* FROM PREFIX-LIST TEST TO METRIC TYPE 1 Continue reading
Let’s take one look back over the IETF before we move on to the next piece of the infrastructure of the ‘net. Why does it take so long for a single document to get through the process, and result in a standard? There is, of course, the formal process, which requires the document to proposed, […]
The post HTIRW: Reality at the Mic (3) appeared first on Packet Pushers Podcast and was written by Russ White.
MPLS traffic engineering has many use cases and it helps to solve the problems in an MPLS enabled networks. These use cases are in general; QoS guarantee, End to End SLA , Fast reroute, Admission control and so on. All of them at the end is done for the COST SAVING. The real reason behind MPLS Traffic… Read More »
The post What is the real reason behind IP and MPLS Traffic Engineering ? appeared first on Network Design and Architecture.
You might remember my blog post claiming we had a system with SDN-like properties more than 20 years ago.
It turns out SDN is older than that – Rob Faulds found an old ComputerWorld ad from 1989 promoting AT&T SDN service, and it seems SDN was in operation as early as 1985.
In this post, I’ll build on a couple of previous posts and show you how to build your own Docker Swarm cluster that leverages etcd for cluster node discovery. This post builds on the information presented on how to run an etcd 2.0 cluster on Ubuntu as well as the information found in this post on running a Consul-backed Docker Swarm cluster.
To help you follow along, I’ve created a Vagrant environment that you can use to turn up the configuration described in this blog post. These files are found in the “docker-swarm-etcd” directory of my GitHub learning-tools repository. Feel free to use the files in this directory/repository to help with the learning process.
There are 3 major components to this configuration:
This article provide a practical and workable definition of "What Is a Network Service ?"
The post Basics: What Is a Network Service ? appeared first on EtherealMind.
The Packet Pushers are recording a live show on SDN WAN on May 13 in New York in partnership with Viptela. Please join us.
The post Upcoming Event: Packet Pushers at ONUG Talking Software Defined WAN appeared first on Packet Pushers Podcast and was written by Greg Ferro.
