Showing all posts tagged sdn:

Aruba EdgeConnect Simplifying the Last Mile for the Hybrid Workplace

Aruba recently presented their vision of the SilverPeak integration into the Aruba family, now branded as EdgeConnect Enterprise and augmented a number existing solutions to round out the offering with EdgeConnect SD-Branch, Microbranch, and Mobile. The mix of solutions here enables use-case based right sizing of the hardware. Aruba's pivot to support this space and expand the existing footprint from mostly on-premises solutions to enabling robust solutions for the entire spectrum of work environments from large enterprise to remote worker and SOHO spaces is necessary in today's environment as the traditional practice of "protecting four walls" is antiquated as users connect from everywhere, with a much larger percentage now remote.


Adjusting from the traditional thinking of each device role to its role in this environment makes sense when following the use case:

  • EdgeConnect Mobile - VIA for remote VPN users
  • EdgeConnect Microbranch - RAP/IAP for SOHO users
  • EdgeConnect SD-Branch - "Office in a Box" style use cases
  • EdgeConnect Enterprise - large office, enterprise use cases

Tying together known device types leveraging AOS10 and Aruba's policy engines and creating intent-based profiles that seamlessly work across the LAN, SD-WAN, endpoints, and now extend out to SASE platforms creates a great opportunity to meet customers where they are at in their journey and a point of differentiation for Aruba, who has always leaned in to the best of breed space. This step is an important shift in the paradigm of providing NAC-like solutions in the corporate environment, while many home connections go unsecured. A holistic approach that weaves these use cases together in a simplified way might take a little adjusting to, however is absolutely necessary in today's hybrid work environment.


The Aruba EdgeConnect SD-WAN Fabric Orchestrator enables the extension of role-based policy controls and infusion into the SD-WAN environment through Aruba ClearPass or through options like radius snooping or proxies, or VXLAN to enforce roles out at the enterprise edge. Leveraging existing technologies to then intelligently apply policies to create this net new functionality offers network security engineers with numerous new ways to segment and secure traffic. Additionally, being able to dynamically recognize devices and drive them to a user profile based off of known characteristics simplifies tasks of dealing with IoT type devices in all cases.

Building upon this strategy, there is room for adding numerous capabilities to the environment, support workflows, and provide nuanced control of the network. Enabling an organization to spend more time to focus on the policy and the intent of its enforcement can enable more reliable delivery of applications, create better and more customized user experience. Aruba's solution also address some of the concerns left by some manufacturers as legacy WAN Optimization is no longer enough, the need to distribute internet access and provide control at the edge can facilitate a migration to the cloud.

The Edge to Cloud story highlights that these solutions provide the last mile of connectivity from application to user, and if it can be done such that it enables the users to consume that data on their own terms from location to device to media type, it is a big win for everyone. Looking forward to watching this solution continue to be refined and mature to be even further integrated into the Aruba product portfolio. The approach used for EdgeConnect should be able to pair with the existing mobility overlay methods that Aruba is using and allow for automated, yet complex, network topologies that are created by policy rather than extensive engineering.





One Company's Journey Out of Darkness, Part VI: Looking Forward

I've had the opportunity over the past couple of years to work with a large customer of mine on a refresh of their entire infrastructure. Network management tools were one of the last pieces to be addressed as emphasis had been on legacy hardware first and the direction for management tools had not been established. This mini-series will highlight this company's journey and the problems solved, insights gained, as well as unresolved issues that still need addressing in the future. Hopefully this help other companies or individuals going through the process. Topics will include discovery around types of tools, how they are being used, who uses them and for what purpose, their fit within the organization, and lastly what more they leave to be desired.


If you'e followed the series this far, you've seen a progression through a series of tools being rolled out. My hope is that this last post in the series spawns some discussion around tools that are needed in the market and features or functionality that is needed. these are the top three things that we are looking at next.

Event Correlation
The organization acquired Splunk to correlate events happening at machine level throughout the organization, but this is far from fully implemented and will likely be the next big focus. The goal is to integrate everything from clients to manufacturing equipment to networking to find information that will help the business run better and experience fewer outages and/or issues as well as increase security. Machine data is being collected to learn about errors in the manufacturing process as early as possible. This error detection allows for on the fly identification of faulty machinery and enables quicker response time. This decreases the amount of bad product and waste as a result, improving overall profitability. I still believe there is much more to be gained here in terms of user experience, proactive notifications, etc.

Software Defined X
Looking to continue move into the software defined world for networking, compute, storage, etc. These offerings vary greatly and the decision to go down a specific path shouldn't be taken lightly by an organization. In our case here we are looking to simplify network management across a very large organization and do so in such a way that we are enabling not only IT work flows, but for other business units as well. This will likely be OpenFlow based and start with the R&D use cases. Organizationally IT has now set standards in place that all future equipment must support OpenFlow as part of the SDN readiness initiative.

Software defined storage is another area of interest as it reduces the dependency on any one particular hardware type and allows for ease of provisioning anywhere. The ideal use case again is for R&D teams as they develop new product. Products that will likely lead here are those that are pure software and open, evaluation has not really begun in this area yet.

DevOps on Demand
IT getting a handle on the infrastructure needed to support R&D teams was only the beginning of the desired end state. One of the loftiest goals is to create an on-demand lab environment that provides compute, store and network on demand in a secure fashion as well as provide intelligent request monitoring and departmental bill back. We've been looking into Puppet Labs, Chef, and others but do not have a firm answer here yet. This is a relatively new space for me personally and I would be very interested in further discussion around how people have been successful in this space.


Lastly, I'd just like to thank the Thwack Community for participation throughout this blog series. Your input is what makes this valuable to me and increases learning opportunities for anyone reading.