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

Understanding Core Phases

Get Dell Fabric Manager PDF manuals and user guides View all Dell Fabric Manager manuals
Add to My Manuals
Save this manual to your list of manuals

Page 37 highlights

6 Understanding Core Phases DFM allows you to create a distributed core design, make changes to the pre-deployment configuration, deploy the core, and validate the core designed with the discovered core. DFM provides up-to-date status during each phase of the core from design to validate. The DFM displays any pending steps required that you need to complete to ensure the distributed core is fully functional for each core design. The following table describes the four core phases displayed on the Cores > Core Deployment screen. Use this information to correct the distributed core design and pre-deployment configuration before and after you deploy the distributed core. Phase Design State • Incomplete-Indicates that only partial information was provided to the core design. This state is applicable only during initial design. After a design is completed, it will never revert back to this state. • Complete-Indicates that all required information was entered to complete the core design. Pre-deployment Configuration • Not Started-Indicates that pre-deployment configuration was never initiated. • Incomplete-Indicates that only part of the pre-deployment configuration was entered and the information provided is not sufficient to proceed with the deployment. • Partial Complete-Indicates that only part of the pre-deployment configuration was entered and the information provided is sufficient to proceed with deployment. • Complete-Indicates that all pre-deployment configurations were entered and the information provided is sufficient to proceed with the deployment. Deployment • Not Started-Indicates that deployment was never initiated. • In-progress-Indicates that deployment is in-progress. • Incomplete-Indicates that deployment did not succeed on any switches. Validation is not performed automatically. • Partial Complete-Indicates that the deployment succeeded for one or more nodes. Validation is not performed automatically. • Complete-Indicates that all the switches the distributed core were deployed. Validation • Not Started-Indicates that core validation was never initiated. NOTE: Validation can be initiated if the deployment configuration is in the partial complete or complete state. • In-progress-Indicates that core validation is in-progress. The deployment configuration is in a partial complete or complete state. • Error-Indicates that one or more validation errors exist. • Complete-Indicates that no validation error exists. 37

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
6
Understanding Core Phases
DFM allows you to create a distributed core design, make changes to the pre-deployment configuration, deploy the
core, and validate the core designed with the discovered core. DFM provides up-to-date status during each phase of the
core from design to validate. The DFM displays any pending steps required that you need to complete to ensure the
distributed core is fully functional for each core design.
The following table describes the four core phases displayed on the
Cores > Core Deployment
screen. Use this
information to correct the distributed core design and pre-deployment configuration before and after you deploy the
distributed core.
Phase
State
Design
•
Incomplete–Indicates that only partial information was provided to the core design. This
state is applicable only during initial design. After a design is completed, it will never revert
back to this state.
•
Complete–Indicates that all required information was entered to complete the core design.
Pre-deployment
Configuration
•
Not Started–Indicates that pre-deployment configuration was never initiated.
•
Incomplete–Indicates that only part of the pre-deployment configuration was entered and
the information provided is
not
sufficient to proceed with the deployment.
•
Partial Complete–Indicates that only part of the pre-deployment configuration was entered
and the information provided is sufficient to proceed with deployment.
•
Complete–Indicates that all pre-deployment configurations were entered and the
information provided is sufficient to proceed with the deployment.
Deployment
•
Not Started–Indicates that deployment was never initiated.
•
In-progress–Indicates that deployment is in-progress.
•
Incomplete–Indicates that deployment did not succeed on any switches. Validation is not
performed automatically.
•
Partial Complete–Indicates that the deployment succeeded for one or more nodes.
Validation is not performed automatically.
•
Complete–Indicates that all the switches the distributed core were deployed.
Validation
•
Not Started–Indicates that core validation was never initiated.
NOTE:
Validation can be initiated if the deployment configuration is in the partial complete or
complete state.
•
In-progress–Indicates that core validation is in-progress. The deployment configuration is in
a partial complete or complete state.
•
Error–Indicates that one or more validation errors exist.
•
Complete–Indicates that no validation error exists.
37