NEC Director of Business Development Don Clark shares the latest SDN deployment lessons and guidelines in a special SDxCentral webinar based on the SDxCentral SDN Controller Report.
Fortinet-Cisco ACI integration uses SDN to reduce costs and improve service delivery in the cloud and in multitenant data centers.

Friday afternoon, late, and the new system is finally up. Users are logged in, getting their work done, and you’ve just received an email from the CTO (your boss’ boss’ boss’ boss, probably), saying what a good job the team did in getting things up and running so quickly. For once, in fact, the system went in perfectly. There was no close to team breakups over which technology or vendor to use; there were very few unexpected items that crept into the budget, the delays were minimal, and you even learned a couple of new skills to top it all off.
Wonderful, right? The perfect unicorn project.
But before you break open that bottle of bubbly (or whatever cold beverage is your choice), or maybe pop up a bowl of popcorn and sit down to a long deserved break binge watching the shows you missed pulling this thing together, you need to ask one more question:
Did you strip and sand first? Or did you just paint right on top?
Or don’t you remember the time you tried to paint that old trailer that had been sitting in your back yard for ages? Sure, it was covered in rust, dirt, Continue reading

The post Worth Reading: A map of the Internet in the US appeared first on 'net work.
For a while now we’ve been hearing a lot of buzz about hyperconverged systems and we’ve been following it closely. We think what’s missing from these conversations is how critical the network is to the sustained success of these systems.
In our quest to build a simply better network, our key focus is on how to truly hyperconverge the network. And we do it by combining the latest in Ethernet switching with optical multiplexing to create a high performance, resilient, low latency and scalable data center network fabric. Unlike traditional leaf/spine approaches, Plexxi Switches are deployed as a single tier, eliminating cost and complexity while vastly reducing operational overhead so the enterprise can build true fabric agility to support the dynamic workload needs of hyperconverged nodes.
At VMWorld, Mat Matthews pointed out in his 5 Key Takeaways blog that hyperconverged solution providers are zoning in on the simplification of the consumption process around infrastructure. The silos are gone. Providers are recognizing that customers want to get new workloads up and running quickly without having to deal with getting storage, compute and networking to work together.
This is good news all around. We are seeing the realization that the network has Continue reading
Another week, another story from the SDN land, this time The Register reporting on AT&T plans. Even though there are almost no details in the story, the headline boasts that “SDN is eating vendors’ lunch”, prompting SDN hopefuls on LinkedIn groups to claim that “the promise of SDN is fast coming to fruition.”
Not so fast.
Read more ...I recently received a letter from the company that monitors my home alarm. It basically stated that to avoid a $3US surcharge that I must opt out of receiving bill in the mail (which is fine) and that I must set up automatic transactions. I also found this form attached.
This is not the first time that I have seen a payment option that includes a requirement for the CVV2 or CID value from my credit card. However with a little knowledge of PCI, I have to ask myself the following question, “What exactly are they going to do with this information?” According to PCI-DSS, this information must not be stored (even in an encrypted format) after authorization.
That raises the following questions for the merchant requiring this information–
In this Continue reading
When testing SDN functions in the Mininet network emulator and viewing captured OpenFlow messages in a packet analyzer such as Wireshark, it is difficult to identify which SDN switch is the source or destination of each captured message.
The only reliable way to identify which SDN switch sent or received an OpenFlow message is to look at the source or destination TCP port of the OpenFlow packets. This is because most OpenFlow messages exchanged between switches and the controller do not contain any other information that helps identify the sending or receiving switch. Neither Mininet nor the Open vSwitch database provides information that might be used to identify the TCP ports used by each switches to communicate with the OpenFlow controller in the network.
This post describes a procedure to map which TCP ports are used on each switch to communicate with the SDN controller in the Mininet network simulation. This procedure will enable researchers or students to study the interactions between SDN controller and switches in a more detailed and accurate way.
To map which TCP ports are used on each switch to communicate with the SDN controller in the Mininet network simulation, execute the steps Continue reading