SDN Management Challenges of Wireless Carriers
SDN Management Challenges of Wireless Carriers
by Steve Harriman, VP of Marketing - March 10, 2014
Our CTO Cengiz Alaettinoglu recently published an article in RCR Wireless’ Reality Check column titled “Stumbling Block: SDN Management Challenges.” He discusses three SDN applications that are particularly valuable for wireless carriers: bandwidth calendaring, demand placement, and rapid provisioning. In fact, Cengiz says that rapid provisioning “…is indeed surfacing as the killer SDN application for carriers beyond the data center.”
However, these applications cannot be used successfully in SDN environments until the industry solves numerous management challenges. Traditional, manual management methods and processes cannot keep up in a programmable, automated network environment. As a result, the human operator loses visibility and control, making it difficult to understand how to plan for the rollout of new applications and services. Lack of oversight creates a sort of wild west environment without anyone or anything governing whether or not these programmatic changes should be made.
Cengiz is currently working on a prototype of a Network Access Broker that will verify if the WAN can handle the traffic demands of SDN applications without impacting other applications adversely. You can read more about what he says Continue reading
Show 182 – The Future of Networking Part 1 As Inspired By #NFD7
At Networking Field Day 7, the delegates were treated to vendor demonstrations that challenged our thinking about the future of networking. Perhaps the industry is not agreed on just how we’ll implement and operate our networks in the coming years, but one thing is for certain. The landscape will be different. In this and the […]
Author information
The post Show 182 – The Future of Networking Part 1 As Inspired By #NFD7 appeared first on Packet Pushers Podcast and was written by Ethan Banks.
NAT saves the day!
Introduction NAT is bad, it breaks end to end connectivity. It’s misused as a security tool. Using NAT kills kittens. Yes yes, we all know that. That doesn’t mean that there aren’t valid use cases for NAT and when NAT can save the day. What was the problem? Imagine that you have a device that […]
Author information
The post NAT saves the day! appeared first on Packet Pushers Podcast and was written by ddib.
Blogs of Interests 2014-03-14
Working from home? Thinking about VXLAN for your Datacenter? Or how about a DMVPN as WAN technology? Read on...[[ Summary content only, you can read everything now, just visit the site for full story ]]
Network Syntax Highlighting in Sublime Text
Here’s something I modified from the original version HERE. If you use Sublime Text 2/3 and work on Cisco equipment, you may find this cool. Follow the install directions bellow. Enjoy! This...[[ Summary content only, you can read everything now, just visit the site for full story ]]
Coffee Break – Show 4
This week Andrew & Greg are joined Howard Marks whose abundance of commentary leads to a surfeit of opinions on the lack of anything happening at Mobile World Congress. Show Notes MWC – Wearable computing on the rise? Netflix and Comcast: Is this the first Network Neutrality domino to fall? Frontier customer complaints drop nearly […]
Author information
The post Coffee Break – Show 4 appeared first on Packet Pushers Podcast and was written by Greg Ferro.
Coffee Break – Show 4
[player] This week Andrew & Greg are joined Howard Marks whose abundance of commentary leads to a surfeit of opinions on the lack of anything happening at Mobile World Congress. Show Notes MWC – Wearable computing on the rise? Netflix and Comcast: Is this the first Network Neutrality domino to fall? Frontier customer complaints drop […]
The post Coffee Break – Show 4 appeared first on Packet Pushers.
Coffee Break – Show 4
[player] This week Andrew & Greg are joined Howard Marks whose abundance of commentary leads to a surfeit of opinions on the lack of anything happening at Mobile World Congress. Show Notes MWC – Wearable computing on the rise? Netflix and Comcast: Is this the first Network Neutrality domino to fall? Frontier customer complaints drop... Read more »Network Syntax Highlighting in Sublime Text
Never look at Cisco configs the same way again, try syntax highlighting just as if you were writing C++ or Python or any other programming language...[[ Summary content only, you can read everything now, just visit the site for full story ]]
Network Syntax Highlighting in Sublime Text
Sublime Text 2/3 Syntax Definition for Cisco / Junos router/switch/firewall configurations. This package will highlight Cisco configuration and commands within Sublime Text 2/3. This package contains...[[ Summary content only, you can read everything now, just visit the site for full story ]]
INTER-AS VPNs and Carrier Supporting Carrier (CSC) Part-2
In the first article of this series I mentioned from Inter AS VPN Option A only. This article will be about Option B , C and Carrier Supporting Carrier VPNs. I assume from the readers basic knowledge of these VPNs.Only design points will be highlighted here since my intended audiences are the network designers and […]
Author information
The post INTER-AS VPNs and Carrier Supporting Carrier (CSC) Part-2 appeared first on Packet Pushers Podcast and was written by Orhan Ergun.
What’s the difference between SDN, NV, and NFV?
As many of you know, or newcomers to IT see, we love our acronyms. For whatever reason, IT is littered with two, three or four letter acronyms. SDN seems to have accelerated this phenomenon. As this title suggests I will describe SDN, NV and NFV in this blog. All of them in our opinion (at Pica8) are software driven schemes that will forever change the way we think about service and application delivery. Each is a different approach to network programmability. Let’s look into the latest acronyms.
Network Virtualization (NV)
NV is for anybody who’s using virtual machine technology. One data center challenge is to move VMs across different logical domains. NV attacks this problem. NV creates logical segments in an existing network by dividing the network at the flow level (similar to partitioning a hard drive). The goal is to allow people to move VMs independently of their existing infrastructure and not have to reconfigure the network.
NV is an overlay. Rather than physically connecting two domains in a network, NV creates a tunnel through the existing network to connect two domains. NV saves administrators from having to physically wire up each new domain Continue reading
Utilizing LLDP instead of CDP
In the last years, many vendors of network devices made available in the market equipments with interesting prices and quality that ended transforming the network environment of companies on a scenario that share different models and devices. Despite the fact that there is a seducing cost, unfortunately some property protocols (despite being interesting) create a barrier of integration among many services or replacement of Switches, Routers,etc.
In order to mapping and discovering neighbor devices in a network with controlled environment and with IP telephony, the Cisco suggest the CDP utilization, but unfortunately the protocol is property of Cisco, limiting its utilization with other models and equipment.
The LLDP protocol is an open standard to discovery devices that are neighbors, with similarly as CDP, including the utilization of features for the VLAN voice.
With the tests below, we activate the LLDP in a Cisco 3750 Switch and a HPN 12500 Switch.
Configuring
Cisco3750(config)# lldp run !Run LLDP on Cisco Switch [HPN12K] lldp enable ! Run LLDP on HP Comware-based Switch
To visualize the mapping of neighbors with Cisco we can use:
Cisco3750#show lldp neighbors
Capability codes:
(R) Router, (B) Bridge, (T) Telephone, (C) DOCSIS Cable Device
(W) WLAN Access Point, (P) Continue reading
Installing KVM, Libvirt and Open vSwitch on Fedora
In my NetOps to DevOps Training Plan I mentioned installing KVM, Libvirt and Open vSwitch. I did this a few weeks ago and documented it to produce this tutorial. My motivation was to replace my VMware environment at home with something Open Source. I am also a strong believer in "eat your own dog food" and as a lot of the work I am doing in the Open Source community centers around these 3 technologies, I should get used to using them every day...
Prerequsites
Before we get started, I'll assume that you already have a Fedora Minimal Installation that you are ready to work on...
Installing the packages
sudo yum install -y @standard @virtualization openvswitch
That was easy wasn't it!
@standard installs some useful utilities and @virtualization installs libvirt + KVM
I'm sure you can guess what openvswitch does.
Configuration
Now here comes the fun part!
Configure the services
# Disable NetworkManager
sudo systemctl stop NetworkManager.service
sudo systemctl disable NetworkManager.service
# Enable "Proper" Networking
sudo systemctl enable network.service
sudo systemctl start network.service
# Enable the Open vSwitch service
sudo systemctl enable openvswitch.service
sudo systemctl start openvswitch.service
Setting up Networking with Open vSwitch
Our Continue reading
Installing KVM, Libvirt and Open vSwitch on Fedora
In my NetOps to DevOps Training Plan I mentioned installing KVM, Libvirt and Open vSwitch. I did this a few weeks ago and documented it to produce this tutorial. My motivation was to replace my VMware environment at home with something Open Source. I am also a strong believer in "eat your own dog food" and as a lot of the work I am doing in the Open Source community centers around these 3 technologies, I should get used to using them every day...
Setting Up Overlays on Open vSwitch
Most “SDN” solutions involve overlays or at the least HW overlay gateways/ToR of some type. Some sell overlays terminating in hardware, others sell overlays terminating in the server. The encaps include standards like GRE, VXLAN and soon to be Geneve (Generic Network Virtualization Encapsulation: basically the good parts of the other encaps evolved). While none of these overlay networks should ......
Packet Capture in Diverse / Tunneled Networks?
(With the usual caveats that I am just a hick from Colorado, I don't know what I'm talking about, etc.)I just read Pete Welcher's superb series on NSX, DFA, ACI, and other SDN stuff on the Chesapeake Netcraftsmen blog, and it helped me think more clearly about a problem that's been bothering me for a long time: how do we do realistically scalable packet capture in networks that make extensive use of ECMP and/or tunnels? Here's a sample network that Pete used:
Conventionally, we place packet capture devices at choke points in the network. But in medium-to-large data center designs, one of the main goals is to eliminate choke points: if we assume this is a relatively small standard ECMP leaf-spine design, each of the leaf switches has four equal-cost routed paths through the spine switches, and each spine switch has at least as many downlinks as there are leaf switches. The hypervisors each have two physical paths to the leaf switches, and in a high-density virtualization design we probably don't have a very good idea of what VM resides on what hypervisor at any point in time.
Now, add to that the tunneling features present in hypervisor-centric Continue reading
Packet Capture in Diverse / Tunneled Networks?
(With the usual caveats that I am just a hick from Colorado, I don't know what I'm talking about, etc.)I just read Pete Welcher's superb series on NSX, DFA, ACI, and other SDN stuff on the Chesapeake Netcraftsmen blog, and it helped me think more clearly about a problem that's been bothering me for a long time: how do we do realistically scalable packet capture in networks that make extensive use of ECMP and/or tunnels? Here's a sample network that Pete used:
Conventionally, we place packet capture devices at choke points in the network. But in medium-to-large data center designs, one of the main goals is to eliminate choke points: if we assume this is a relatively small standard ECMP leaf-spine design, each of the leaf switches has four equal-cost routed paths through the spine switches, and each spine switch has at least as many downlinks as there are leaf switches. The hypervisors each have two physical paths to the leaf switches, and in a high-density virtualization design we probably don't have a very good idea of what VM resides on what hypervisor at any point in time.
Now, add to that the tunneling features present in hypervisor-centric Continue reading
Installing KVM, Libvirt and Open vSwitch on Fedora
In my NetOps to DevOps Training Plan I mentioned installing KVM, Libvirt and Open vSwitch. I did this a few weeks ago and documented it to produce this tutorial. My motivation was to replace my VMware environment at home with something Open Source. I am also a strong believer in "eat your own dog food" and as a lot of the work I am doing in the Open Source community centers around these 3 technologies, I should get used to using them every day...