Users Guide

Design State Pre-Deploy Configuration
State
Deployment
State
Validation
State
Operation Allowed
Incomplete
indicates that
AFM is
deploying the
switches.
Complete
indicates all the
switches in the
distributed fabric
are deployed.
Error /
Complete
Speed (Advanced
fabric)
• Number of
switches per stack
(stack mode)
• Pre-deployment
Configuration
• View DHCP
Configuration
• Deploy and
Validate Fabric —
Validation is only
allowed when
deployment is
partial or fully
complete
• View Deployment
and Validation
Status
• Delete Fabric
Deployment Topology Use Cases
To select a deployment topology, refer to the following use cases as a guide.
Use Case 1: One-Tier Layer 2 Fabric
If you select a one-tier Layer 2 fabric:
• The uplinks between the two aggregation switches and external switch support the Layer 3 protocol
(OSPF, iBGP or eBGP).
• The downlinks from the two aggregation switches support the Layer 2 protocol (VLAN or VLAN/
VRRP). The default setting on the pre-deployment screen is VLAN configuration, which allows you to
configure downlink connections to servers. To support redundancy between the aggregation
switches and ToR switches, select VLAN and VRRP Configuration.
Use Case 2: One-Tier Layer 3 with Resiliency (Routed VLT)
If you select a one-tier Layer 3 with Resiliency (Routed VLT) fabric:
• The uplinks between the two aggregation switches and external switch (WAN) support the Layer 3
protocol (OSPF, iBGP or eBGP).
• The downlinks from the two aggregation switches support the Layer 2 protocol (VLAN/VRRP or VLAN
IP). During the design phase on the Deployment Topology screen, select the fabric type and
deployment type (topology). Based on the selected deployment type options, different downlink
options are configured in the access tier.
Use Case 3: Two-Tier Layer 2
If you select a two-tier Layer 2 VLT fabric:
• The fabric links between aggregation and access switches support the Layer 2 protocol.
Designing the Fabric
55