Link Search Menu Expand Document
calendar_month 07-Mar-24

Customer Profile

This section provides an The requirements WAN and Branch requirements of Orange Widge Logistics.

In the two following sections, reference architectures are provided to illustrate:

  • A solution design to meet the hypothetical customer’s requirements using EdgeConnect SD-WAN.

  • A solution design to meet the hypothetical customer’s requirements using EdgeConnect SD-Branch.

Customer Overview

The customer is a US-based business operating hubs in Seattle and New York.

The business has 100 branch locations of varying size and importance spread throughout the US.

The customer expects an average of 10% year-over-year growth of branch locations.

The solution is scaled out for at least five years of growth.


The customer seeks to:

  • Decrease reliance on MPLS to reduce operational expense, with the goal to phase it out completely over time.
  • Improve the experience for users using IaaS (Infrastructure-as-a-Service) and SaaS (Software-as-a-Service) applications as the business migrates to the cloud.
  • Protect certain sensitive corporate data going to a SaaS service by traversing IPS/DLP.
  • Provide critical guest Wi-Fi service at branch locations.
  • Gather guest Wi-Fi usage data to assess customer behavior and apply a “digital-first” approach to improve the customer experience and attract customers to stores.
  • Use a cloud-first approach for all IT infrastructure, minimizing the on-premise footprint as much as possible.
  • Begin using IaaS providers such as AWS and Azure and employ SD-WAN optimization for the IaaS locations.

Site Profiles

As the customer gains comfort with the SD-WAN solution, the MPLS connections will be phased out in favor of additional Internet circuits.

Traffic between the traditional hubs and spokes will continue to decrease over time as more workloads are moved to IaaS environments and SaaS solutions.

  • Seattle and New York both have existing 200 mpbs MPLS connections. They will use two 1000/1000 mbps business class internet circuits.
  • Although the virtual hubs in Seattle and New York are not currently in place, the customer plans for deployments in the cloud provider for the US West region and the US East region.
  • 20 large sites, defined as:
    • The business has no tolerance for unscheduled downtime
    • Uptime is provided by the gateway HA and cellular backup.
    • Up to 200 users
    • Use existing 40 Mbps connection and add 200/50 mbps commodity Internet circuits and a 5G LTE backup
  • 75 medium sites, defined as:
    • The business has less tolerance for downtime
    • More uptime is provided by the gateway HA, but with no cellular backup.
    • Up to 100 users
    • Use existing 30 Mbps MPLS connection and add 100/10 commodity internet circuit
  • 5 small sites, defined as:
    • The business can tolerate downtime
    • Up to 10 Users
    • Require only a single gateway, with no device-level HA or cellular backup
    • Use existing 5mbps MPLS connections and the customer plans to add 50/10 mbps commodity Internet circuits.

Traffic Profile

The company’s traffic predominantly includes:

  • Use of Zoom and Microsoft Teams for real-time communications
  • Real-time inventory data queries on in-house SQL systems, hosted at data centers
  • Bulk FTP file transfers used throughout the environment to process transactions hosted at data centers
  • SaaS applications, such as Sales Force, are used to provide optimal Internet egress.

Table of contents

Back to top

© Copyright 2024 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Aruba Networks and the Aruba logo are registered trademarks of Aruba Networks, Inc. Third-party trademarks mentioned are the property of their respective owners. To view the end-user software agreement, go to Aruba EULA.