|
|
1 |
(% class="row" %) |
|
|
2 |
((( |
|
|
3 |
(% class="col-xs-12 col-sm-7 test-report-content" %) |
|
|
4 |
((( |
|
|
5 |
---- |
|
|
6 |
|
|
|
7 |
Deploying a DC POD from scratch is typically a complex procedure that involves many steps and parameters to consider. It starts with the design phase, where the physical structure, the number of devices to deploy, and the underlay network parameters like IP address spaces, VRFs, and VLAN ranges are determined. After the design phase, a review is conducted to ensure the design is free of issues, such as IP overlapping or missed configurations. The implementation phase follows, during which the design is applied to the devices. This phase is often demanding and requires careful work. After implementation, a verification phase is necessary to confirm the correct implementation and functionality of the design. |
|
|
8 |
|
|
|
9 |
Automating the DC POD deployment is a valuable feature that saves time and reduces design errors. The Document ETSI GR ENI 049 specifies the system’s requirements and establishes an evaluation scale for the automation grade. |
|
|
10 |
|
|
|
11 |
In the following tests, we designed and deployed a DC POD using Huawei iMaster NCE-Fabric and aimed for an automation level 4, which provides a user-friendly, intent-based interface and design verification. |
|
|
12 |
|
|
|
13 |
|
|
|
14 |
(% id="prev-next-links" %) |
|
|
15 |
|[[< Previous>>doc:Main.Huawei Data Center Autonomous Network L4 Verification Test Report.WebHome]]|[[Next ~>>>doc:Main.Huawei Data Center Autonomous Network L4 Verification Test Report.Network Planning and Construction Service - DC POD Planning, Construction, and Deployment.1\.1\.1- POD Requirement Analysis L4 Capability Test.WebHome]] |
|
|
16 |
))) |
|
|
17 |
|
|
|
18 |
(% class="col-xs-12 col-sm-5 test-report-sidebar" %) |
|
|
19 |
((( |
|
|
20 |
{{box}} |
|
|
21 |
{{include reference="Main.Huawei Data Center Autonomous Network L4 Verification Test Report.Sidebar Nav"/}} |
|
|
22 |
{{/box}} |
|
|
23 |
))) |
|
|
24 |
))) |
