Healthy Paranoia Show 22: The Three Ring Circus of Net Neutrality
Ladies and gentleman, unicorns of all ages, get ready for the greatest podcast on earth, Healthy Paranoia. Where the email is always encrypted and the firewalls are ever stateful. On this episode, we’ll be discussing Net Neutrality. Joining us is Sherry Lichtenberg, Principal for Telecommunications at the National Regulatory Research Institute; Andrew Gallo, network architect […]
Author information
The post Healthy Paranoia Show 22: The Three Ring Circus of Net Neutrality appeared first on Packet Pushers Podcast and was written by Mrs. Y.
ONS2014 Announces Finalists for SDN Idol 2014
- Brocade and InMon: Real-time SDN Analytics for DDoS mitigation
- HP: HP SDN App Store and Open SDN Ecosystem
- OpenDaylight: Hydrogen
- Pica8: Pica8’s Open SDN Starter Kit
- Radware: Adaptive Network, Application and APT Protection
Real-time SDN Analytics for DDoS mitigation is an example of a performance aware SDN controller that combines sFlow and OpenFlow for the visibility and control needed to build self optimizing networks that automatically adapt to changing traffic conditions. A number of other use cases were outlined by Brocade at the recent OpenDaylight Summit - see Flow-aware Real-time SDN Analytics (FRSA)
There are interesting links with other finalists:
There are interesting links with other finalists:
- OpenDaylight Hydrogen The Brocade is a Platinum member of the OpenDaylight project, and the Brocade/InMon DDoS mitigation solution employs OpenDaylight Hydrogen as an OpenFlow controller. Like Brocade, many of the OpenDaylight project members also support sFlow in their networking equipment, including: Brocade, Cisco, IBM, Juniper, NEC, A10 Networks, Arista, Dell, HP, Huawei, Intel, and ZTE. One might expect to see other vendors start to build traffic aware solutions on OpenDaylight in the coming months.
- HP SDN App Store and Open SDN Continue reading
New design guide: VMware NSX with Cisco UCS and Nexus 7000
Back in September 2013 I wrote a piece on why you would deploy VMware NSX with your Cisco UCS and Nexus gear. The gist being that NSX adds business agility, a rich set of virtual network services, and orders of magnitude better performance and scale to these existing platforms. The response to this piece was phenomenal […]New design guide: VMware NSX with Cisco UCS and Nexus 7000
Back in September 2013 I wrote a piece on why you would deploy VMware NSX with your Cisco UCS and Nexus gear. The gist being that NSX adds business agility, a rich set of virtual network services, and orders of magnitude better performance and scale to these existing platforms. The response to this piece was phenomenal with many people asking for more details on the how.
The choice is clear. To obtain a more agile IT infrastructure you can either:
- Rip out every Cisco UCS fabric interconnect and Nexus switch hardware you’ve purchased and installed, then proceed to repurchase and re-install it all over again (ASIC Tax).
- Add virtualization software that works on your existing Cisco UCS fabric interconnects and Nexus switches, or any other infrastructure.
To help you execute on choice #2, we decided to write a design guide that provides more technical details on how you would deploy VMware NSX for vSphere with Cisco UCS and Nexus 7000. In this guide we provide some basic hardware and software requirements and a design starting point. Then we walk you through how to prepare your infrastructure for NSX, how to design your host networking and bandwidth, how traffic flows, and Continue reading
New design guide: VMware NSX with Cisco UCS and Nexus 7000
Back in September 2013 I wrote a piece on why you would deploy VMware NSX with your Cisco UCS and Nexus gear. The gist being that NSX adds business agility, a rich set of virtual network services, and orders of magnitude better performance and scale to these existing platforms. The response to this piece was phenomenal with many people asking for more details on the how.
The choice is clear. To obtain a more agile IT infrastructure you can either:
- Rip out every Cisco UCS fabric interconnect and Nexus switch hardware you’ve purchased and installed, then proceed to repurchase and re-install it all over again (ASIC Tax).
- Add virtualization software that works on your existing Cisco UCS fabric interconnects and Nexus switches, or any other infrastructure.
To help you execute on choice #2, we decided to write a design guide that provides more technical details on how you would deploy VMware NSX for vSphere with Cisco UCS and Nexus 7000. In this guide we provide some basic hardware and software requirements and a design starting point. Then we walk you through how to prepare your infrastructure for NSX, how to design your host networking and bandwidth, how traffic flows, and Continue reading
New design guide: VMware NSX with Cisco UCS and Nexus 7000
Back in September 2013 I wrote a piece on why you would deploy VMware NSX with your Cisco UCS and Nexus gear. The gist being that NSX adds business agility, a rich set of virtual network services, and orders of magnitude better performance and scale to these existing platforms. The response to this piece was phenomenal with many people asking for more details on the how.
The choice is clear. To obtain a more agile IT infrastructure you can either:
- Rip out every Cisco UCS fabric interconnect and Nexus switch hardware you’ve purchased and installed, then proceed to repurchase and re-install it all over again (ASIC Tax).
- Add virtualization software that works on your existing Cisco UCS fabric interconnects and Nexus switches, or any other infrastructure.
To help you execute on choice #2, we decided to write a design guide that provides more technical details on how you would deploy VMware NSX for vSphere with Cisco UCS and Nexus 7000. In this guide we provide some basic hardware and software requirements and a design starting point. Then we walk you through how to prepare your infrastructure for NSX, how to design your host networking and bandwidth, how traffic flows, and Continue reading
JunOS ‘L3 incompletes’, what and why?
There is quite often chatter about L3 incompletes, and it seems there are lot of opinions what they are. Maybe some of these opinions are based on some particular counter bug in some release. Juniper has introduced also toggle to allow stopping the counter from working. It seems very silly to use this toggle, as it is really one of the few ways you can gather information about broken packets via SNMP.
What they (at least) are not
- Unknown unicast
- CDP
- BPDU
- Packet from connected host which does not ARP
- Packet from unconfigured VLAN
What they (at least) are
- IP header checksum error
- IP header error (impossibly small IHL, IP version 3, etc)
- IP header size does not match packet size
Troubleshooting
So if you are seeing them, what can you do? As it is aggregate counter for many different issues, how do you actually know which one is it and is there way to figure out who is sending them? Luckily for Trio based platforms answers and highly encouraging, we have very good tools to troubleshoot the issue.
To figure out what they exactly are, first you need to figure out your internal IFD index (not snmp ifindex)
im@ruuter> Continue reading
Coffee Break – Show 3
Mike Fratto joins us this week to talk about the news of the week on IPv4, Broadband Performance, Net Neutrality, IBM, SDN and more.Coffee Break – Show 3
Mike Fratto joins us this week to talk about the news of the week on IPv4, Broadband Performance, Net Neutrality, IBM, SDN and more.
Author information
The post Coffee Break – Show 3 appeared first on Packet Pushers Podcast and was written by Greg Ferro.
Coffee Break – Show 3
Mike Fratto joins us this week to talk about the news of the week on IPv4, Broadband Performance, Net Neutrality, IBM, SDN and more.
The post Coffee Break – Show 3 appeared first on Packet Pushers.
Configuration Backups for F5
As an administrator of network devices, keeping full backups is important for being able to recover from hardware failure. With F5 devices, backups come in the form of UCS files which is an archive that contains all configurations and SSL certificates. With a UCS file, you can take a replacement device, upload a UCS file […]
Author information
The post Configuration Backups for F5 appeared first on Packet Pushers Podcast and was written by Eric Flores.
Dell, Cumulus, Open Source, Open Standards, and Unified Management
On Thursday, at Network Field Day 7, Arpit Joshipura described Dell's networking strategy. He started by polling the delegates to see which topics were most on their mind.
Arpit suggests that customers will choose Cumulus Linux as the operating system for the layer 3 features and because they can use the same expertise and tools (Puppet, Chef etc.) to manage Linux servers and the switches connecting them. He also suggested that customers would choose FTOS for legacy networks and layer 2 features. Support for the Open Networking Install Environment Continue reading
Comware: Clearing an Interface Configuration
HP released the “default” command on interface-view in the latest version of Comware in order to restore to default configuration of an interface.
This command is useful when you want to clear an interface configuration and reuse the interface for some other task. Normally you would need to issue the “undo” command for each line.
Following below the configuration (the command was tested on HP 7500 Switches Release 6626P02)
[HP-GigabitEthernet1/0/1] display this
! checking interface configuration before clean up
#
interface GigabitEthernet1/0/1
port link-mode bridge
port link-type trunk
port trunk permit vlan all
#
return
[HP-GigabitEthernet1/0/1]default
This command will restore the default settings. Continue? [Y/N]:y
! Setup default command on interface
!
[HP-GigabitEthernet1/0/1]display this
#
interface GigabitEthernet1/0/1
port link-mode bridge
#
See you soon 
Changing Data Center Workloads
Networking-wise, I’ve spent my career in the data center. I’m pursuing the CCIE Data Center. I study virtualization, storage, and DC networking. Right now, the landscape in the network is constantly changing, as it has been for the past 15 years. However, with SDN, merchant silicon, overlay networks, and more, the rate of change in a data center network seems to be accelerating.
Things are changing fast in data center networking. You get the picture
Whenever you have a high rate of change, you’ll end up with a lot of questions such as:
- Where does this leave the current equipment I’ve got now?
- Would SDN solve any of the issues I’m having?
- What the hell is SDN, anyway?
- I’m buying vendor X, should I look into vendor Y?
- What features should I be looking for in a data center networking device?
I’m not actually going to answer any of these questions in this article. I am, however, going to profile some of the common workloads that you find in data centers currently. Your data center may have one, a few, or all of these workloads. It may not have any of them. Your data center may have one of the Continue reading
Out with the old, in with the new
A few weeks ago I was asked to help a client turn up and move everything over to a new network. I have done this many times and this is not an uncommon type of project. In doing network assessments for clients I have found some old equipment still in service, still part of the […]
Author information
The post Out with the old, in with the new appeared first on Packet Pushers Podcast and was written by Charles Galler.
Big Switch, Cumulus, and OpenFlow
Two of the three companies promoting white box, now more commonly known as bare metal, switching are Cumulus and Big Switch Networks. There has been coverage on each of these companies, but the question always arises, “does Cumulus support OpenFlow?” I had the chance to talk to JR Rivers, Cumulus CEO, at the last Open Networking User Group (ONUG) during a Tech Field Day video and heard the answer from him then, but hadn’t seen anything documented publicly.
There was a SDN Meetup at Stanford last week where JR gave his take on SDN and a great overview on Cumulus, which happens to be on Vimeo. More importantly, he touches upon the question regarding OpenFlow support in the Cumulus Linux software stack during the video.
Coming directly from JR, his response (around the 58 minute mark):
Coming directly from JR, his response (around the 58 minute mark):
“The only way you can truly be successful in meeting the customer needs around OpenFlow is to be truly focused on a great OpenFlow agent that lives on the switch platform. Trying to come up with a hybrid approach or half approach inevitably end up in unhappy customers… In general, when customers want to use OpenFlow, Cumulus will say, Continue reading
Can Wi-Fi be made easier to use than cellular?
"Making Wi-Fi as easy as cellular” is a popular maxim when engineers, marketeers, and journalists talk about Hotspot 2.0. And it’s not hard to understand why. The cellular connectivity experience is well understood in virtually every culture, while, except to...Comware: STP disable
As default, STP and other features are disable on some HP device based on Comware. In this case it is important to always check the Spanning-Tree Protocol status before include a device in a network in production. And if necessary enable it. 
[Switch] display stp
Protocol Status :disabled
Protocol Std. :IEEE 802.1s
Version :3
Bridge-Prio. :32768
MAC address :000f-e203-0200
Max age(s) :20
Forward delay(s) :15
Hello time(s) :2
Max hops :20
! Identify that STP is enabled on Switch
[Switch]stp enable
%Jun 18 16:21:10:253 2012 Switch MSTP/6/MSTP_ENABLE: STP is now
enabled on the device.
! enabling Spanning-Tree
See you soon.
Redundant Default Gateway solutions in IPv4 networks
How does the internet work - We know what is networking
This article is an introduction to different default gateway solutions. Those technologies are enabling devices on IPv4 local subnets to have more than one Default gateway configured or at least some configuration that make them work half the way of ideal redundant solution. Idea behind this article is to be an introduction to a set […]