In the case of troubleshooting poor performance for an off-site application, improving mean time to innocence is really important. Businesses need to understand whether the problem is in the local infrastructure, in the remote cloud, or somewhere in the middle. This is not especially easy to track down by hand. Manual traceroutes, simple ping tests, and DNS resolution checks are most of what can be done with the average workstation, but in fact there is a great deal more information that is publicly accessible.
The post Improving Mean Time To Innocence With ThousandEyes appeared first on Packet Pushers Podcast and was written by Ethan Banks.
Maybe my excuse should be that it was somewhere around two in the morning. Or maybe it was just unclear thinking, and that was that. Sgt P. and I were called out to fix the AN/FPS-77 RADAR system just at the end of our day (I normally came into the shop around 6:30AM after swimming a mile in the Ft. Dix pool, showering, and eating breakfast, so I truly had an early start), so we’d been fighting this problem for some seven or eight hours already. For some reason, a particular fuse down in the high voltage power supply kept blowing. Given this is the circuit that fed the magnetron with 250,000 volts at around 10 amps (yes, that’s a lot of power, especially for a device originally built in 1964), it made for some interesting discussion with the folks in base weather, who were thus dependent on surrounding weather RADAR systems to continue flight operations.
They weren’t happy.
We traced the problem back, using our best half splitting skills in a high voltage circuit that took minutes to power up and down, and finally decided it was a particular resistor located over on a corner of one assembly (we Continue reading
Back in December of 2014, I wrote a blog post about the complexities of the network as a distributed system. In it I pointed out that networks have traditionally been built as distributed systems, and that our entire management and knowledge base for networks is based on this. But, is this the best approach for current and future networking needs?
As humans we have our own ideas of how to best solve problems. While we are immensely creative, our solutions aren’t always the best (or will never be). We often look to nature as a guide for how to improve our manmade solutions. When we look at how large complex systems in nature have been created and evolved, perhaps we should look no further than ourselves. The human body is possibly one of the most complex systems we know. If we think of the brain as the centralized control system, it is easy to see that we are, in fact, highly centralized beings.
We live and function, however, in a social environment that has no clearly established central control system. We are organized by different permanent and temporary control systems. We create environments with centralized direction of work to be Continue reading
VMware continues to build out its own container infrastructure, including a container-optimized spin on Linux.
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.