You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -5,59 +5,140 @@ author: surajmb #Required; your GitHub user alias, with correct capitalization.
5
5
ms.author: surmb #Required; microsoft alias of author; optional team alias.
6
6
ms.service: azure #Required; service per approved list. slug assigned by ACOM.
7
7
ms.topic: how-to #Required; leave this attribute/value as-is.
8
-
ms.date: 03/03/2023 #Required; mm/dd/yyyy format.
8
+
ms.date: 03/13/2023 #Required; mm/dd/yyyy format.
9
9
ms.custom: template-how-to #Required; leave this attribute/value as-is.
10
10
---
11
11
12
12
# Operator Nexus platform prerequisites
13
13
14
-
You'll need to complete the prerequisites before you can deploy the
15
-
Operator Nexus platform. Some of these steps may take
14
+
Operators will need to complete the prerequisites before the deploy of the
15
+
Operator Nexus platform software. Some of these steps may take
16
16
extended amounts of time, thus, a review of these prerequisites may prove beneficial.
17
17
18
18
In subsequent deployments of Operator Nexus instances, you can skip to creating the on-premises
19
19
[Network Fabric](./howto-configure-network-fabric.md) and the [Cluster](./howto-configure-cluster.md).
20
20
21
-
###Azure prerequisites
21
+
## Azure prerequisites
22
22
23
-
-When deploying Operator Nexus for the first time or in a new region,
24
-
you'll first need to create a Network Fabric Controller and then a Cluster Manager as specified [here](./howto-azure-operator-nexus-prerequisites.md).
23
+
When deploying Operator Nexus for the first time or in a new region,
24
+
you'll first need to create a Network Fabric Controller and then a Cluster Manager as specified [here](./howto-azure-operator-nexus-prerequisites.md). Additionally, the following tasks will need to be accomplished:
25
25
- Set up users, policies, permissions, and RBAC
26
26
- Set up Resource Groups to place and group resources in a logical manner
27
27
that will be created for Operator Nexus platform.
28
+
- Establish ExpressRoute connectivity from your WAN to an Azure Region
28
29
29
-
###On your premises prerequisites
30
+
## On your premises prerequisites
30
31
31
-
- Purchase and install hardware:
32
-
- Purchase the hardware as specified in the BOM provided to you
33
-
- Perform the physical installation (EF&I)
34
-
- Cable as per the BOM including the cabling to your WAN via a pair of PE devices.
35
-
- All network fabric devices (except for the Terminal Server (TS)) are set to ZTP mode
36
-
- Servers and Storage devices have default factory settings
37
-
- Establish ExpressRoute connectivity from your WAN to an Azure Region
38
-
- Terminal Server has been [deployed and configured](#set-up-terminal-server)
32
+
When deploying Operator Nexus on-premises instance in your datacenter, various teams are likely involved to perform a variety of roles. The following tasks must be performed accurately in order to ensure a successful platform software installation.
33
+
34
+
### Physical hardware setup
35
+
36
+
An operator that wishes to take advantage of the Operator Nexus service will need to
37
+
purchase, install, configure, and operate hardware resources. This section of
38
+
the document will describe the necessary components and efforts to purchase and implement the appropriate hardware systems. This section will discuss the bill of materials, the rack elevations diagram and the cabling diagram, as well as the steps required to assemble the hardware.
39
+
40
+
#### Using the Bill of Materials (BOM)
41
+
42
+
To ensure a seamless operator experience, Operator Nexus has developed a BOM for the hardware acquisition necessary for the service. This BOM is a comprehensive list of the necessary components and quantities needed to implement the environment for a successful implementation and maintenance of the on-premises instance. The BOM is structured to provide the operator with a series of stock keeping units (SKU) that can be ordered from hardware vendors. SKUs will be discussed later in the document.
43
+
44
+
#### Using the elevation diagram
45
+
46
+
The rack elevation diagram is a graphical reference that demonstrates how the
47
+
servers and other components fit into the assembled and configured racks. The
48
+
rack elevation diagram is provided as part of the overall build instructions and will help the operators staff to correctly configure and install all of the hardware components necessary for service operation.
49
+
50
+
#### Cabling diagram
51
+
52
+
Cabling diagrams are graphical representations of the cable connections that are required to provide network services to components installed within the racks. Following the cabling diagram ensures proper implementation of the various components in the build.
53
+
54
+
### How to order based on SKU
55
+
56
+
#### SKU definition
57
+
58
+
A SKU is an inventory management and tracking method
59
+
that allows grouping of multiple components into a single designator. A SKU
60
+
allows an operator to order all needed components with through specify one SKU
61
+
number. This expedites the operator and vendor interaction while reducing
62
+
ordering errors due to complex parts lists.
63
+
64
+
#### Placing a SKU based order
65
+
66
+
Operator Nexus has created a series of SKUs with vendors such as Dell, Pure
67
+
Storage and Arista that the operator will be able to reference when they place
68
+
an order. Thus, an operator simply needs to place an order based on the SKU
69
+
information provided by Operator Nexus to the vendor to receive the correct
70
+
parts list for the build.
71
+
72
+
### How to build the physical hardware footprint
73
+
74
+
The physical hardware build is executed through a series of steps which will be detailed in this section.
75
+
There are three prerequisite steps prior to the build execution. This section will also discuss assumptions
76
+
concerning the skills of the operator's employees to execute the build.
77
+
78
+
#### Ordering and receipt of the specific hardware infrastructure SKU
79
+
80
+
The ordering of the appropriate SKU and delivery of hardware to the site must occur before the
81
+
start of building. Adequate time should be allowed for this step. We recommend the operator
82
+
communicate with the supplier of the hardware early in the process to ensure and understand
83
+
delivery timeframes.
84
+
85
+
#### Site preparation
86
+
87
+
The installation site must be capable of supporting the hardware infrastructure from a space, power,
88
+
and network perspective. The specific site requirements will be defined by the SKU purchased for the
89
+
site. This step can be accomplished after the order is placed and before the receipt of the
90
+
SKU.
91
+
92
+
#### Scheduling resources
93
+
94
+
The build process will require several different staff members to perform the
95
+
build, such as engineers to provide power, network access and cabling, systems
96
+
staff to assemble the racks, switches, and servers, to name a few. To ensure that the
97
+
build is accomplished in a timely manner, we recommend scheduling these team members
98
+
in advance based on the delivery schedule.
99
+
100
+
#### Assumptions regarding build staff skills
101
+
102
+
The staff performing the build should be experienced at assembling systems
103
+
hardware such as racks, switches, PDUs and servers. The instructions provided will discuss
104
+
the steps of the process, while referencing rack elevations and cabling diagrams.
105
+
106
+
#### Build process overview
107
+
108
+
If the site preparation is complete and validated to support the ordered SKU,
109
+
the build process occurs in the following steps:
110
+
111
+
1. Assemble the racks based on the rack elevations of the SKU. Specific rack assembly
112
+
instructions will be provided by the rack manufacturer.
113
+
1. After the racks are assembled, install the fabric devices in the racks per the elevation diagram.
114
+
1. Cable the fabric devices by connecting the network interfaces per the cabling diagram.
115
+
1. Assemble and install the servers per rack elevation diagram.
116
+
1. Assemble and install the storage device per rack elevation diagram.
117
+
1. Cable the server and storage devices by connecting the network interfaces per the cabling diagram.
118
+
1. Cable power from each device.
119
+
1. Review/validate the build through the checklists provided by Operator Nexus and other vendors.
120
+
121
+
#### How to visually inspect the physical hardware installation
122
+
123
+
It is recommended to label on all cables following ANSI/TIA 606 Standards,
124
+
or the operator's standards, during the build process. The build process
125
+
should also create reverse mapping for cabling from a switch port to far end
126
+
connection. The reverse mapping can be compared to the cabling diagram to
127
+
validate the installation.
128
+
129
+
## Terminal Server and storage array setup
130
+
131
+
Now that the physical installation and validation has completed, the next steps involved configuring up the default settings required before platform software installation.
132
+
133
+
### Set up Terminal Server
134
+
135
+
Terminal Server has been deployed and configured as follows:
39
136
- Terminal Server is configured for Out-of-Band management
40
137
- Authentication credentials have been set up
41
-
- DHCP client is enabled on the out-of-band management port, and
138
+
- DHCP client is enabled on the out-of-band management port
42
139
- HTTP access is enabled
43
-
- Terminal Server interface is connected to your on-premises Provider Edge routers (PEs) and configured with the IP addresses and credentials
140
+
- Terminal Server interface is connected to the operators on-premises Provider Edge routers (PEs) and configured with the IP addresses and credentials
44
141
- Terminal Server is accessible from the management VPN
45
-
- For the [Network Fabric configuration](./quickstarts-platform-deployment.md#step-1-create-network fabric) (to be performed later)
46
-
you'll need to provide:
47
-
- ExpressRoute credentials and information
48
-
- Terminal Server IPs and credentials
49
-
-[optional] IP prefix for the network
50
-
Network Fabric Controller (NFC) subnet during its creation; the default IPv4 and IPv6
51
-
prefix are `10.0.0.0/19` and `FC00:/59`, respectively
52
-
-[optional] IP prefix for the Operator Nexus
53
-
Management plane during NFC creation.
54
-
By default, `10.1.0.0/19` and, `FC00:0000:0000:100::/59`
55
-
IPv4 and IPv6 prefix, respectively, are used for subnets in the management plane for the first
56
-
Operator Nexus instance. Prefix range `10.1.0.0/19` to `10.4.224.0/19` and
57
-
`FC00:0000:0000:100::/59` to `FC00:0000:0000:4e0::/59` are used for
58
-
the 32 instances of Operator Nexus supported for each NFC instance.
0 commit comments