Data center fabric orchestration
HPE Aruba Networking Fabric Composer
Per managed switch, subscription dependent
Compatibility, scale and topology validation
Direct answer for buyers
HPE Aruba Network Fabric Orchestration is a buyer-facing way to describe the software-led orchestration of compatible HPE Aruba Networking AOS-CX data center fabrics. Fabric Composer is the HPE product that performs this role for supported switch families. It is mainly used to automate fabric provisioning, coordinate underlay and overlay configuration, improve topology and workload visibility, manage multiple fabrics and integrate network actions with surrounding data center systems. Organisations considering it should confirm the exact switch models and AOS-CX releases, subscription tier and term, number of managed switches, intended topology, virtualisation host, high-availability design and required third-party integrations before requesting a bill of materials.
What it does in a data center
Fabric orchestration sits above individual switch configuration. Instead of treating every switch as a separate device, the orchestration layer understands the collection of switches as a fabric and uses guided workflows, APIs and topology awareness to apply coordinated changes. HPE describes Fabric Composer as an API-driven, software-defined orchestration solution for network provisioning, security management and day-to-day operations across rack-scale compute and storage infrastructure. This is particularly relevant where network teams need repeatable leaf-spine construction, underlay routing, EVPN-VXLAN overlays, multi-fabric interconnection or coordinated changes across many AOS-CX devices.
The platform does not remove the need to decide addressing, routing design, segmentation, redundancy, cabling, switch roles or operational ownership. Those decisions become inputs to the orchestration process. Buyers therefore gain the most value when the intended architecture is clear and the switch estate is aligned to supported models and software versions.
Who should consider it
The strongest fit is generally an organisation operating or building an HPE Aruba Networking AOS-CX data center where manual, switch-by-switch work is becoming difficult to scale. That can include enterprise data centers, private cloud teams, hosting environments, service providers, education and government infrastructure, large virtualisation estates, and organisations modernising from simpler Layer 2 designs toward resilient leaf-spine fabrics.
It may also be relevant where the network must coordinate with VMware, Nutanix, HPE infrastructure or AMD Pensando services, subject to the exact Fabric Composer release and the versions of those platforms. A small network with only a few switches and limited change may not need a full orchestration platform. Likewise, buyers running a mixed-vendor fabric should not assume that Fabric Composer will orchestrate every device. The supported-switch matrix and integration matrix should be treated as design constraints, not as optional reading.
Business problems the orchestration layer helps address
Configuration drift across switches
As data center fabrics grow, separate CLI sessions increase the chance that one switch differs from the intended design. Fabric-level workflows apply coordinated configuration from a common model. This can reduce repetitive work, but change governance and validation remain necessary because an incorrect design can also be propagated consistently.
Complex EVPN-VXLAN build tasks
A leaf-spine fabric can involve BGP or OSPF underlay choices, VTEPs, EVPN control-plane relationships, VRFs, VLANs and VXLAN segments. Fabric Composer provides guided workflows that can automate much of this configuration. Buyers still need a validated addressing plan, segmentation model and operational standard before automation begins.
Limited fabric-wide visibility
Troubleshooting a service path is harder when the operator must correlate many switch views manually. Fabric Composer can present fabric topology, connected hosts and other contextual information through a common interface, helping teams relate network state to the attached environment rather than viewing every port in isolation.
Multi-site growth
When data center pods or sites need controlled connectivity, the design must address route exchange, segmentation and failure domains. HPE documents multi-fabric workflows that can help automate interconnection of EVPN-VXLAN fabrics. The topology, latency, transport and disaster-recovery objectives still need engineering review.
Network and workload coordination
Data center changes often begin outside the network team. Fabric Composer includes integration capabilities intended to react to events in workload and infrastructure platforms. Compatibility is release specific, so the exact VMware, Nutanix, HPE or Pensando versions should be checked before assuming a workflow is available.
Security policy coordination
In environments using the HPE Aruba Networking CX 10000 and AMD Pensando services, Fabric Composer can take a central role in orchestrating segmentation and firewall policy. This is architecture and license dependent and should be designed with the security team rather than treated as a default capability of every AOS-CX switch.
Capability band: what changes operationally
Operators work with coordinated fabric constructs rather than viewing every switch configuration as an unrelated task.
Common fabric workflows can be built with structured inputs and applied consistently across the selected topology.
Topology and attached infrastructure context can improve how teams inspect fabric state and trace operational issues.
Automation can connect network workflows with supported data center systems where release compatibility is confirmed.
Fit matrix for HPE Aruba fabric orchestration
| Requirement | Suitable when | Confirm before ordering |
|---|---|---|
| Leaf-spine automation | The target design uses supported AOS-CX switches and a validated spine-leaf architecture. | Switch roles, AOS-CX versions, underlay protocol, EVPN-VXLAN requirements and addressing plan. |
| Two-tier data center | The selected topology is supported by the current Fabric Composer release. | Core/access design, Layer 2 versus Layer 3 boundaries, redundancy and migration sequence. |
| Multi-fabric operations | More than one fabric or data center location needs coordinated visibility or interconnection. | Scale, transport, DCI design, route control, failure domains and host resources for the orchestration platform. |
| CX 10000 security services | The architecture uses CX 10000 and supported AMD Pensando services. | Services licensing, PSM compatibility, security policy ownership and software version sequence. |
| Virtualisation integration | The fabric must coordinate with a supported VMware, Nutanix or other documented platform. | Exact platform release, credentials, network reachability, workflow objective and change controls. |
| Small, stable switch estate | Useful when repeatability or topology visibility still justifies orchestration. | Whether a simpler management workflow could meet the requirement at lower operational complexity. |
Sizing values describe software host requirements in HPE documentation, not switch capacity or network throughput. They should be reviewed again against the release selected for deployment. A quotation should never be based on VM size alone; the number of managed switches, integrations, fabrics, HA requirement, software lifecycle and operational model all affect the final design.
Configuration, licensing and compatibility dependencies
Fabric orchestration is highly dependent on the exact environment. The same product name can lead to very different bills of materials depending on which switch families are managed, how many switches are in scope, whether the fabric is single-site or multi-site, whether high availability is required and how long the subscription should run. A buyer should therefore treat the orchestration license as part of a design rather than as a generic software item that can be ordered independently of the network.
Switch and AOS-CX compatibility
The supported switch family is only the first check. The exact model, software train and Fabric Composer release must be compatible. New AOS-CX releases can introduce features that require a corresponding Fabric Composer release, while older combinations may be supported, deprecated or no longer qualified. Capture the current switch inventory before requesting the license.
Subscription tier and term
HPE documentation separates subscription tiers by supported switch family and provides multi-year options. A 6300-based requirement and a CX 10000-based requirement should not be assumed to use the same subscription. Determine quantity per managed switch, preferred term and whether any existing entitlements can be reused or renewed under current vendor policy.
Integration version alignment
An integration name alone does not prove compatibility. VMware, Nutanix, PSM and other connected systems have their own release cycles. The Fabric Composer compatibility matrix should be compared with the versions actually running in the data center, and upgrade sequencing should be planned where the selected combination is not supported.
FourTeck can help structure these checks before the quotation stage. Share the switch models, AOS-CX versions, expected number of fabrics, virtualisation platform, third-party integrations, management network details and the preferred subscription term. This reduces the risk of receiving a license set that does not match the deployment.
A practical purchase and deployment journey
Inventory the existing network
Record switch models, serial or asset references where useful, current AOS-CX releases, device roles, existing VSX or VSF relationships, uplinks, management addressing and any current automation tools. If the project is greenfield, replace the inventory with the proposed bill of materials and topology.
Define the target fabric
Decide whether the design is two-tier or spine-leaf, whether EVPN-VXLAN is required, which switches will act as spine, leaf or border, how routing and addressing will work and whether multiple fabrics must be connected. Capture segmentation and resilience requirements at this stage.
Check compatibility
Match the selected Fabric Composer release to the switch families and AOS-CX software. Repeat the check for VMware, Nutanix, PSM or other planned integrations. If upgrades are required, sequence them as part of the project rather than discovering the dependency after licensing is ordered.
Size the orchestration host
Use the number of switches, integrations and fabrics to select the documented host profile for the chosen release. Decide whether the platform will run on VMware, KVM, Hyper-V, Nutanix or another supported environment and whether a three-node HA design is required.
Build the subscription bill of materials
Map each managed switch to the correct subscription tier and term. Confirm whether the quote requires one, three or five years, plus any separate services licenses for platforms such as CX 10000. Do not infer that an accessory license or third-party entitlement is included unless the ordering guide explicitly says so.
Plan implementation and acceptance
Agree who will install the software, discover switches, create the fabric, integrate external systems, migrate existing configuration, validate redundancy and document the final state. Define rollback points and an acceptance checklist before production changes begin.
Fabric-wide automation without losing design control
The practical attraction of orchestration is not that it makes network engineering disappear. It gives engineering decisions a consistent execution path. A team can define a leaf-spine topology, choose an underlay design, establish overlay constructs and then use guided workflows to deploy those decisions across the participating switches. HPE documentation highlights workflow automation for switch discovery, initial setup, VSX configuration, leaf-spine deployment, BGP or OSPF underlay creation and EVPN-related workflows.
For an operations team, that consistency matters during both the first build and later change. New racks or fabrics can follow an established pattern instead of depending on an operator to recreate every command from memory. An API-driven platform also makes it easier to connect change activity to an external automation process when there is a clear reason to do so.
The limit is important: orchestration can reproduce a poor design as efficiently as it reproduces a good one. Before deployment, define route policy, address pools, VLAN and VRF naming, redundancy, failure behavior, change approvals and validation tests. FourTeck can include design review and configuration scope in the quotation where the customer wants assistance translating those decisions into a deployable fabric.
Visibility that connects fabric state to workloads
Switch-by-switch monitoring is often sufficient for a small network, but it becomes less efficient when application traffic crosses multiple leaf switches, virtual hosts and overlays. Fabric Composer is designed to provide topology and attached infrastructure context so an operator can view the network as a fabric. HPE describes visibility across hosts, virtual machines, VLANs, services and workloads, with integrations providing additional context where supported.
This does not mean every application dependency is automatically discovered or that the platform replaces an observability stack. The value is more specific: network state can be presented in a way that relates switches, ports, fabric constructs and connected infrastructure. During troubleshooting, this can reduce the amount of manual correlation needed to understand where a path or configuration issue may sit.
Buyers should decide what they expect to observe before the project begins. If the requirement includes detailed application performance, packet analysis, SIEM integration or long-term analytics, those may involve other tools and data sources. Define the operational questions the team wants Fabric Composer to answer, then verify that the planned release and integrations expose the needed information.
Multi-fabric growth and data center interconnection
Many fabric projects begin with one data center pod and later expand into another hall, another building or a disaster-recovery site. HPE documents multi-fabric orchestration and EVPN-VXLAN interconnection workflows that can help coordinate multiple fabrics. This can be useful when the organisation wants a consistent operational model across several data center locations rather than creating an isolated management process for each site.
The orchestration capability should not be confused with the transport itself. A multi-site design still depends on the available DCI transport, route and segmentation policies, failure-domain decisions, latency, MTU, addressing, security and the applications that may extend between sites. Stretching Layer 2 or Layer 3 reachability can have operational consequences, so the design should be driven by workload requirements and recovery objectives rather than by the fact that a workflow can configure it.
For a Dubai organisation planning a second UAE or regional site, it is useful to document which networks genuinely require cross-site reachability, which should remain local, how default routes and external connectivity should behave, and what happens if the DCI is lost. Those answers inform both the Fabric Composer design and the wider switching and routing bill of materials.
Security orchestration with CX 10000 environments
The security dimension becomes particularly important in a data center using HPE Aruba Networking CX 10000 switches and AMD Pensando distributed services. HPE positions Fabric Composer as a unified network and security management engine for this architecture, with workflows for segmentation, security and firewall policy. Centralised policy definition can help network and security teams coordinate intent while enforcement occurs close to workloads.
This is not a universal property of every Fabric Composer deployment. The CX 10000, its services license, Pensando PSM release, Fabric Composer release and related integration requirements have to align. Security policy also needs an owner. Decide whether the network team, security team or a joint operations process will approve changes; determine how policies will be named, reviewed and rolled back; and identify what logging must be retained elsewhere for audit or investigation.
When requesting a quote, state whether CX 10000 distributed services are already deployed, planned for a new fabric or outside the project. That simple distinction changes the licensing and implementation discussion. FourTeck can help separate the base fabric-orchestration requirement from additional security-service components so the customer can see which items are mandatory for the chosen architecture and which are optional or environment dependent.
Ideal business environments and use cases
Private cloud expansion
A private-cloud team adding compute clusters may need repeatable rack connectivity and predictable network segmentation. Fabric orchestration can turn an agreed fabric design into reusable provisioning workflows, while integrations may provide additional context for supported virtualisation environments.
Data center modernisation
An organisation moving from a traditional aggregation design toward AOS-CX spine-leaf architecture can use orchestration as part of the new operational model. Migration sequencing, coexistence with the existing network and rollback planning should be included in the project scope.
Multi-site resiliency
Businesses operating primary and recovery data centers may use multi-fabric capabilities to standardise configuration and simplify inter-fabric workflows. The recovery design still needs application, storage, routing and security input beyond the network orchestration platform.
CX 10000 distributed security
Where east-west policy is being enforced with CX 10000 distributed services, Fabric Composer can be part of the unified operational workflow. Licensing and PSM integration should be verified as separate design items.
Operations standardisation
A central network team supporting multiple data center pods can use a common orchestration approach to reduce differences in how fabrics are built and maintained. Governance is still required to ensure that standardisation does not remove necessary site-specific controls.
High-change virtualised environments
Where workloads move and network changes are frequent, supported integrations and event-driven workflows can reduce manual coordination. The value depends on the exact virtualisation stack and the specific workflow the business wants to automate.
Integration and operational considerations
Before integrating Fabric Composer with another platform, identify the operational outcome rather than beginning with the connector. A VMware integration may be valuable because the network team wants visibility of virtual workloads, because a workflow should react to workload changes, or because CX 10000 policy needs to align with VM context. Those are different objectives and may require different permissions, components and validation.
Management reachability
The Fabric Composer host needs stable addressing, DNS and time services, plus network reachability to the switches and any integrated platforms. HPE installation guidance calls out static or reserved addressing and NTP requirements. Treat the management path as infrastructure that deserves redundancy and monitoring.
Credentials and role design
Integrations need credentials or API access. Define least-privilege roles where supported, document who owns service accounts and include credential rotation in operations. Avoid using a personal administrator account as the permanent integration identity.
Change ownership
When both an orchestration platform and external automation can change the network, teams need a clear source of truth. Decide which system creates a configuration, which validates it and which records approvals. This helps prevent two automation paths from working against each other.
If the existing environment already uses HPE Aruba Networking Central, NetEdit, Ansible or another management platform, include those tools in the discovery process. The goal is not to deploy a new interface without deciding what it replaces or complements. FourTeck can help map the intended operational responsibilities before implementation so administrators know where to perform routine configuration, orchestration, monitoring and troubleshooting.
Buyer questions to resolve before requesting a quotation
Procurement checklist
How FourTeck can support the planning process
FourTeck can help convert a general request for HPE Aruba network fabric orchestration into a quote-ready requirement. The process can start with the switch inventory and target architecture, then move through compatibility review, subscription mapping, host sizing and implementation scope. Where the customer is building a new fabric, the discussion can include switch roles, management design, EVPN-VXLAN objectives, multi-site requirements and the expected integrations.
For an existing environment, the focus may be different: determine whether the installed AOS-CX versions can be managed by the selected Fabric Composer release, identify any required upgrade sequence and decide how current switch configuration will be discovered or incorporated. If other tools already manage the switches, their role should be documented so the new orchestration platform does not create overlapping ownership.
Visit the FourTeck technology services page for related planning and implementation assistance, or use the FourTeck contact page to share your switch list and project requirement.
Quotation inputs that make the answer more accurate
A product name by itself is not enough for an accurate Fabric Composer quotation because the license is tied to managed switches and subscription terms. Provide the exact switch family and quantity, whether the switches are already deployed, the intended license duration and any planned expansion. If the fabric uses multiple sites, include the location of each site and whether Fabric Composer will manage them as separate or interconnected fabrics.
For project services, describe whether FourTeck is expected to provide design validation, software installation, switch discovery, fabric creation, integration, migration, testing or handover. The customer should also state any change-window limitations and whether production traffic can be interrupted. These details allow implementation scope to be separated from the software subscription rather than bundled into an undefined service line.
Buyers comparing other infrastructure options can also review the FourTeck product portfolio and the wider FourTeck UAE technology site.
UAE availability and support guidance
For Dubai and the wider UAE, contact FourTeck to confirm the current HPE Aruba Networking Fabric Composer subscription options, orderable SKUs, license region and vendor lead time. Availability can vary by subscription tier, term, quantity and current HPE ordering policy. The software entitlement and any implementation service should be quoted as separate, clearly understood elements when possible. If installation or configuration is required, include the scope in the request so the quotation reflects software deployment, switch onboarding, integration, validation and documentation rather than assuming those activities are included with the license.
A UAE buyer should also confirm the support path expected after go-live. Operational support may involve HPE software support, the customer’s internal network team, FourTeck coordination or a combination of these. Define who will own upgrades, license renewals, backup, HA health, integration credentials and change requests. This makes lifecycle planning more predictable than treating the orchestration platform as a one-time purchase.
Dubai, Abu Dhabi, Sharjah and Ajman project coordination
FourTeck can discuss HPE Aruba fabric-orchestration requirements for organisations operating data centers, server rooms, private-cloud infrastructure or recovery environments across Dubai, Abu Dhabi, Sharjah and Ajman. The useful starting point is the same across all four locations: identify the managed AOS-CX switches, software versions, required Fabric Composer subscription term, intended topology and implementation responsibilities. Where more than one UAE site is involved, clarify whether the orchestration requirement is simply common management or whether the fabrics must also be interconnected. Delivery and project coordination can be discussed after the exact software, quantity, destination and deployment scope are confirmed.
GCC Availability
FourTeck can assist organisations planning HPE Aruba network fabric orchestration across GCC projects by reviewing the technical requirement before software and services are quoted. This can include switch-family validation, Fabric Composer subscription selection, license-term planning, host sizing, integration review, deployment scope and renewal guidance. Requirements may originate in the United Arab Emirates and extend to Saudi Arabia, Kuwait, Qatar, Bahrain or Oman, but availability and commercial conditions can differ by destination. Product availability, licensing, vendor lead time, delivery planning, service visits and project scope can vary by country, model, quantity and customer requirement. For a regional quotation, provide the destination country, exact AOS-CX switch models, managed-switch quantity, preferred subscription term, deployment location, planned integrations and expected project timeline. FourTeck can then coordinate the appropriate commercial and technical discussion without assuming that a license or service arrangement from one GCC market automatically applies in another.
Africa Availability
Organisations planning data center fabric automation in Africa can engage FourTeck for requirement review, licensing guidance, subscription planning, compatibility checks and deployment-scope coordination. Projects may involve a single data center, a multi-site environment or a wider technology refresh in East, West, Central or Southern Africa. Availability and fulfilment depend on the destination, exact switch models, quantity, license region, software version, shipping arrangements, vendor lead time and local project conditions. Installation or support coverage should be confirmed for the specific site rather than assumed from a general regional statement. Buyers in markets such as Kenya or Uganda can share the target architecture, managed-switch count, preferred schedule, integration platforms and support expectations so FourTeck can advise on the next steps. Relevant regional information is also available through FourTeck Africa and the FourTeck Kenya site.
Related FourTeck options to consider
HPE Aruba AOS-CX data center switching
Fabric Composer depends on compatible AOS-CX switches. A new deployment may therefore require switch selection, transceiver planning, port-speed review and redundancy design before orchestration licenses are finalised.
HPE Aruba Networking Central
Central provides broader cloud-based management capabilities across wired, wireless and other network domains. It should not be treated as identical to Fabric Composer; the right management platform depends on the data center architecture and operational model.
Network design and migration services
A brownfield fabric project may need topology assessment, addressing design, migration sequencing, rollback planning and production validation in addition to the software entitlement.
CX 10000 distributed services
Where the project includes distributed stateful services, confirm the CX 10000 design, Pensando PSM requirements and services licensing separately from Fabric Composer subscription licensing.
Why businesses contact FourTeck for this type of project
The most useful role for a technology supplier on an orchestration project is to reduce ambiguity before an order is placed. The requirement may arrive as a request for Fabric Composer, fabric automation, EVPN orchestration or simply a desire to stop configuring data center switches one at a time. Each phrase can lead to a different architecture and bill of materials.
FourTeck can help clarify which AOS-CX switches are in scope, identify the correct subscription tier and term, review the compatibility of the proposed Fabric Composer release, separate mandatory licenses from optional components and define installation or configuration responsibilities. Where the project includes an existing environment, the discussion can also cover upgrade dependencies and migration planning. For a greenfield fabric, the buyer can ask for support with topology, sizing and the boundary between switch configuration, orchestration and surrounding virtualisation or security platforms.
This approach avoids unsupported claims about stock, fixed delivery dates or universal compatibility. The quote is prepared around the actual requirement and current vendor information. More background on the company is available on the FourTeck company page.
What buyers usually need to understand before choosing fabric orchestration
Fabric Composer versus ordinary switch management
A common buyer question is whether Fabric Composer is simply another graphical interface for switches. The distinction is orchestration. Device management focuses on the settings and status of individual devices; fabric orchestration applies an architecture across a group of devices and understands those devices as a coordinated fabric. This matters most when the network includes repeatable relationships such as spine and leaf roles, underlay routing, overlay segments, VSX pairs and multi-fabric connections. A graphical interface is part of the user experience, but the business value comes from the workflow and fabric model behind it.
When EVPN-VXLAN changes the buying decision
Buyers researching data center fabrics frequently encounter EVPN and VXLAN without knowing whether both are mandatory. VXLAN provides an overlay encapsulation mechanism, while EVPN is commonly used as the control plane that distributes endpoint and reachability information. HPE validates Fabric Composer for EVPN-VXLAN spine-leaf designs, but a customer should not add an overlay just because the orchestration platform can build one. The decision should follow from requirements such as scalable segmentation, workload mobility, Layer 2 or Layer 3 reachability and multi-tenant design. Simpler environments may use a supported two-tier architecture instead.
Why the switch list matters more than the software name
Fabric Composer licensing is based on managed switches, and HPE separates subscription tiers by switch family. This means procurement should begin with the switch inventory. Two organisations asking for the same product can need different licenses because one uses CX 6300 and another uses CX 8360 or CX 10000. The current HPE 7.3 installation guide lists CX 6300 under Tier 3 and several data center families under Tier 4. Exact model support and AOS-CX compatibility should still be validated in the current matrix because family membership alone does not establish a supported software combination.
How to think about platform sizing
Another practical question is whether Fabric Composer needs dedicated hardware. HPE documents virtual deployment options and host-size profiles based on the number of switches, integrations and fabrics. The current 7.3 guide defines small, large and extra-large profiles, with the extra-large profile intended for multi-fabric or environments up to 200 switches. These figures help plan CPU, memory and disk for the orchestration application; they are not measures of packet throughput. Network traffic continues to be switched by the AOS-CX hardware. Sizing should therefore focus on management scale, integrations and availability rather than link bandwidth.
Single instance or high availability
A buyer also needs to decide how important continuous access to the orchestration platform is. HPE documents a three-node high-availability installation procedure. The right choice depends on how the organisation uses the platform. If Fabric Composer is central to frequent production changes and operational troubleshooting, HA may be justified. If it is used mainly for periodic orchestration and the underlying switches continue forwarding traffic independently, the business may accept a different availability model. The answer should come from operational risk and recovery objectives, not from a blanket assumption that every deployment needs three nodes.
What a useful quote request looks like
A useful request contains the managed-switch count and models, current AOS-CX versions, desired subscription duration, target topology, number of sites or fabrics, host platform, integrations and implementation expectations. If the buyer only provides the phrase ‘network fabric orchestration’, the supplier still has to discover these facts before the license and services can be sized correctly. Sharing them upfront produces a more meaningful comparison between options and reduces the chance that a low initial price excludes required subscriptions or deployment work.
The most important comparison is usually not ‘Fabric Composer versus manual configuration’ in isolation. It is the operating model the business wants for the next several years. Consider how often the fabric changes, how many sites will exist, who owns automation, how virtualisation and security teams interact with the network, and whether the organisation has the process maturity to treat fabric templates and workflows as controlled production assets.
Decision questions that can change the architecture or quotation
Do we need Fabric Composer if we already use HPE Aruba Networking Central?
Possibly, but the answer depends on the data center design and management objective. Central is a broad network-management platform with capabilities spanning wired, wireless, SD-WAN and other domains. Fabric Composer is purpose-built around orchestration of supported AOS-CX data center fabrics. An organisation may use one, the other or both in different roles. Before purchasing, define which platform will own fabric configuration, day-to-day changes and visibility so operational responsibilities do not overlap unnecessarily.
Can we use existing AOS-CX switches without replacing them?
Often yes if the exact models and software versions are supported, but family names alone are not enough. Compare each installed model and AOS-CX release to the compatibility matrix for the Fabric Composer version you plan to deploy. A brownfield project may require software upgrades, configuration cleanup or topology changes before the switches are ready to participate in the intended fabric. Those activities should be included in migration scope.
Is licensing based on users, sites or switches?
HPE documents Fabric Composer as a per-managed-switch subscription, with tiering tied to supported switch families and terms available for multiple years. This makes the switch count a core commercial input. Multi-site operation may increase the number of managed switches and can also affect host sizing, but it does not turn the license into a simple site subscription. Always confirm current orderable SKUs at quote time.
What must be prepared before an EVPN-VXLAN deployment?
The automation needs architectural inputs: switch roles, loopback and point-to-point addressing, routing design, VLAN and VRF structure, VNI allocation, redundancy, border connectivity and operational naming. Fabric Composer can automate deployment of these constructs, but it should not be asked to invent the business segmentation model. If these inputs are not ready, include a design workshop before configuration work begins.
What information is needed for CX 10000 security orchestration?
State the exact CX 10000 models, AOS-CX version, Fabric Composer release, PSM release and services licensing. Explain which workloads require policy, how security groups will be defined and who owns rule approval. The network orchestration and distributed services components are related but should be validated independently so a missing services entitlement or version mismatch does not delay the fabric project.
Should installation services be part of the same quote?
Include them when the customer wants a defined outcome rather than software entitlement only. A clear service scope can cover host deployment, initial hardening, switch discovery, fabric creation, integration, migration, testing, documentation and handover. If some tasks remain with the customer’s internal team, identify those responsibilities explicitly. This makes commercial comparison fairer and reduces assumptions during implementation.
Frequently asked questions
What is HPE Aruba Network Fabric Orchestration?
It describes the software-led orchestration of supported HPE Aruba Networking AOS-CX data center fabrics. HPE Aruba Networking Fabric Composer is the product used for this role, providing fabric provisioning, visibility, workflow automation and supported integration capabilities.
Which switches can Fabric Composer manage?
The current HPE Fabric Composer 7.3 installation guide lists CX 6300 for Tier 3 subscriptions and CX 10000, 6400, 8100, 8400, 8325, 8360 and 9300 for Tier 4 subscriptions. Exact model and AOS-CX release compatibility must be checked before ordering.
Is a subscription required for every managed switch?
HPE documents Fabric Composer as a per-switch software subscription. The applicable tier and term depend on the managed switch family and current ordering catalog. Confirm quantity and subscription term for the actual switch inventory before requesting a quote.
Can Fabric Composer build EVPN-VXLAN fabrics?
Yes. HPE documents Fabric Composer workflows for spine-leaf designs with EVPN-VXLAN and for automated underlay and overlay configuration. The network architecture, addressing, segmentation and supported software versions still need to be defined and validated.
Does Fabric Composer support high availability?
HPE documents a three-node high-availability deployment procedure for Fabric Composer. Whether HA is necessary depends on the customer’s operational risk, change model and recovery objectives, and the host resources should be sized for the selected release.
Can it integrate with VMware or Nutanix?
HPE documents integrations with VMware and Nutanix platforms, among other systems. Compatibility is version specific. Check the Fabric Composer compatibility matrix against the exact VMware, Nutanix and Fabric Composer releases planned for the project.
Is Fabric Composer the same as HPE Aruba Networking Central?
No. Central is a broader network-management platform, while Fabric Composer is focused on orchestration of supported AOS-CX data center fabrics. The products can have different roles, and the preferred operating model should be established before deployment.
What should I send FourTeck for a Dubai quotation?
Send the switch models and quantities, AOS-CX versions, target topology, number of fabrics, preferred subscription term, host platform, integration requirements and whether installation, migration or configuration services are required. This allows the quotation to reflect the actual architecture.
How is UAE availability confirmed?
FourTeck can check current license options, subscription terms and vendor lead time after the exact requirement is known. Availability can depend on license, quantity, region and current HPE policy, so it should be confirmed at quotation time rather than assumed.
Plan the orchestration layer around your actual fabric
Share your HPE Aruba Networking switch inventory, target topology, software versions, preferred subscription term and integration requirements with FourTeck. We can help confirm the Fabric Composer licensing approach, compatibility, host sizing and implementation scope before a UAE quotation is prepared. Current product availability and project scheduling will be confirmed against the final requirement.