Here are some reasons enterprises may want to leverage the new IEEE standard.
In this Off The Cuff episode of Network Collective, we talk about all aspects of Cisco’s announcement of their intent to acquire Viptela’s SD-WAN product. Who wins in this deal? What happens to Cisco’s existing SD-WAN product line? What happens to the rest of the SD-WAN market? Keith Townsend and Tom Hollingsworth join the Network Collective hosts in breaking down what this means for all involved.
Outro Music:
Danger Storm Kevin MacLeod (incompetech.com)
Licensed under Creative Commons: By Attribution 3.0 License
http://creativecommons.org/licenses/by/3.0/
Audio Only Podcast Feed:
The post Off The Cuff – Cisco Acquiring Viptela appeared first on Network Collective.
In this Off The Cuff episode of Network Collective, we talk about all aspects of Cisco’s announcement of their intent to acquire Viptela’s SD-WAN product. Who wins in this deal? What happens to Cisco’s existing SD-WAN product line? What happens to the rest of the SD-WAN market? Keith Townsend and Tom Hollingsworth join the Network Collective hosts in breaking down what this means for all involved.
Outro Music:
Danger Storm Kevin MacLeod (incompetech.com)
Licensed under Creative Commons: By Attribution 3.0 License
http://creativecommons.org/licenses/by/3.0/
Audio Only Podcast Feed:
The post Off The Cuff – Cisco Acquiring Viptela appeared first on Network Collective.
AOS 1.2 offers “full network transparency.”
How Does Internet Work - We know what is networking
I already wrote about Control Plane Protection in one of my previous posts focused on Cisco device configuration. Here we will make the same thing on Juniper device, I was using Juniper SRX300 and Juniper SRX1500 devices in my lab. CoPP ?? Control Plane Protection (CoPP) is a method of protecting processor unit, running services on your network device, against excessive flooding. Excessive flooding of traffic aimed towards your router/firewall processor, being that valid or malicious, is always undesirable and can also be dangerous. A network device, which starts the receive more control traffic that his processor can process, will
The awesome Troopers crew published conference videos, including my Securing Network Automation presentation (more, including slide deck).
I called my last post ‘basic’ external access into the cluster because I didn’t get a chance to talk about the ingress object. Ingress resources are interesting in that they allow you to use one object to load balance to different back-end objects. This could be handy for several reasons and allows you a more fine-grained means to load balance traffic. Let’s take a look at an example of using the Nginx ingress controller in our Kubernetes cluster.
To demonstrate this we’re going to continue using the same lab that we used in previous posts but for the sake of level setting we’re going to start by clearing the slate. Let’s delete all of the objects in the cluster and then we’ll start by build them from scratch so you can see every step of the way how we setup and use the ingress.
kubectl delete deployments --all kubectl delete pods --all kubectl delete services --all
Since this will kill our net-test
pod, let’s start that again…
kubectl run net-test --image=jonlangemak/net_tools
Recall that we used this pod as a testing endpoint so we could simulate traffic originating from a pod so it’s worth keeping around.
Alright – now that we Continue reading