Dell Fabric Manager Dell Fabric Manager Deployment Guide 1.0.0 - Page 21

–

underscore (

_

)

–

@

–

+

When you specify the name of the distributed core,Dell Fabric Manager automatically names the nodes (spines and

leaves) in the distributed core with the core name as the prefix. For example,

if the name of the core is

EastCore

,

the node names assigned are

EastCore-Spine-1

and

EastCore-Leaf1

.

2.

(Optional) Enter the description of the distributed core.

There is no character restriction. The length of the description can be between 1 and 128 characters.

3.

Select the core type from the

Core Type

pull-down menu.

For guidelines about selecting the core type, see

Designing a Distributed Core

.

4.

Select the interlink over-subscription rate that is appropriate for your deployment from the

interlink over-

subscription ratio

pull-down menu.

The interlink over-subscription rate varies the maximum number of available interconnect links. The ratio you

specify depends on the bandwidth, throughput, and available edge port requirements. The interlink over-

subscription does

not

come off the edge port downlinks.

As you increase the interlink over-subscription ratio:

–

The total number of ports for the uplinks and downlinks increase.

–

The total number interconnect links from the leaves to the spines decrease.

–

The maximum number of available ports increases.

Use the 1:1 interlink over-subscription rate for the non-blocking, line rate between the leaves and spines. Use this

option when you require a lot of bandwidth and not a lot of ports.

After entering the basic core design information, the Core Design Wizard displays a list of requirements to build the

core in the

Requirements based on core type and oversubscription

section at the bottom right of the screen.

5.

Click

Next

to go to the

Port Count

screen.

Core Design – Step 3: Port Count

Use the

Port Count

screen to enter the number of edge port uplinks and downlinks required for the initial deployment

and future expansion.

This screen displays the following information:

•

Available Ports—Displays the maximum available ports based on the selected core type and interlink over-

subscription rate in the

Core Name and Type

screen. This a read only field.

•

Total Planned Ports—Displays the total number of ports for all the current and future uplinks and downlinks on

the leaves.

•

Remaining Available Ports—Displays the difference of available ports and total planned ports. This is a read-

only field.

•

Uplinks—Each uplink connects to a WAN, which typically connects to a ISP. The minimum number of current

and future uplinks is 2 (one uplink is for redundancy) and the maximum is 32.

•

Downlinks—The sum of downlink ports (current + future) should be minimum of 2 but not exceed the maximum

available ports (available ports – (current + future uplink ports)).

When designing the distributed core, it is important to determine the future needs of the distributed core so that you can

later expand it as the data center grows. After you finalized the core design, you

cannot

change it. As a result, make

sure you enter the future requirements for the edge (leaf switch) ports in the

Number of additional edge ports for future

expansion

area during the core design phase.

21

Section	Page
Contents	3
Introduction	7
Conventional Core Versus Distributed Core	7
Conventional Core	7
Distributed Core	8
Key Advantages	9
Designing a Distributed Core	9
Terminology	10
Gathering Useful Information	11
Key Considerations for Designing a Distributed Core	11
Selecting a Distributed Core Design Template	13
Type 1: Large Core Design	13
Type 2: Medium Core Design	14
Type 3: Small Core Design	16
Getting Started	17
Designing and Deploying a Distributed Core	17
Flowchart for Designing and Deploying a Distributed Core	18
How to Design and Deploy a Distributed Core	18
Using the Core Design Wizard	19
Core Design – Step 1: Welcome Page	19
Core Design – Step 2: Core Name and Type	20
Core Design – Step 3: Port Count	21
Core Design – Step 4: Interlink Configuration	22
Core Design – Step 5: Uplink Configuration	23
Core Design – Step 6: Downlink Configuration	23
Core Design – Step 7: Output	23
Core Design – Step 8: Summary	25
Using the Pre-deployment Wizard	27
Pre-Deployment – Step 1: Introduction	27
Prerequisites	27
Flowchart for preparing the distributed core for deployment	28
Pre-Deployment Screens	28
Pre-deployment – Step 2: Assign Switch Identities	29
Pre-Deployment – Step 3: Management IP	29
Pre-Deployment – Step 4: Software Images	30
Pre-Deployment – Step 5: DHCP Integration	30
Pre-Deployment – Step 6: Output	31
Pre-Deployment – Step 7: Summary	31
Deploying and Validating the Core	33
Viewing Deployment and Validation Status	35
Understanding Core Phases	37
Operations Allowed During Each Core State	39
Troubleshooting	41
Switch Deployment Status Errors	41
Validating Connectivity to the ToR	44
Validation Errors	44
Expanding the Core	47
Modifying and Viewing the Distributed Core	49
Dashboard	49
Cores	50
Editing the Core	50
Deleting the Core	51
Viewing and Exporting Wiring Diagram	51
Viewing the DHCP Configuration File	51
Alerts	53
Active Alerts	53
Alerts and Event History	54
Monitor	55
Reports	55
Creating a New Report	55
Running a Report	56
Editing a Report	56
Duplicating Reports	56
Deleting a Report	57
Global Statistics	57
Data Collection	57
Administration	59
Settings	59
TFTP Settings	59
Syslog IP Addresses	59
SNMP Configuration	60
CLI Credentials	60
Data Retention	61
Client Settings	61
Managing User Accounts	61
Adding a User	62
Deleting a User	63
Editing a User	63
Changing Your Password	64
Unlocking a User	64

Dell Fabric Manager Dell Fabric Manager Deployment Guide 1.0.0 - Page 21

Core Design – Step 3: Port Count, Core Name and Type

Page 21 highlights