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
Before deploying the Nexus Cluster, it’s best for the operator to set the iDRAC IPs while organizing the hardware racks. Here’s how to map servers to IPs:
404
+
405
+
- Assign IPs based on each server’s position within the rack.
406
+
- Use the fourth /24 block from the /19 subnet allocated for Fabric.
407
+
- Start assigning IPs from the bottom server upwards in each rack, beginning with 0.11.
408
+
- Continue to assign IPs in sequence to the first server at the bottom of the next rack.
409
+
410
+
### Example
411
+
412
+
Fabric range: 10.1.0.0-10.1.31.255 – iDRAC subnet at fourth /24 is 10.1.3.0/24.
413
+
414
+
| Rack | Server | iDRAC IP |
415
+
|--------|---------------|---------------|
416
+
| Rack 1 | Worker 1 | 10.1.3.11/24 |
417
+
| Rack 1 | Worker 2 | 10.1.3.12/24 |
418
+
| Rack 1 | Worker 3 | 10.1.3.13/24 |
419
+
| Rack 1 | Worker 4 | 10.1.3.14/24 |
420
+
| Rack 1 | Worker 5 | 10.1.3.15/24 |
421
+
| Rack 1 | Worker 6 | 10.1.3.16/24 |
422
+
| Rack 1 | Worker 7 | 10.1.3.17/24 |
423
+
| Rack 1 | Worker 8 | 10.1.3.18/24 |
424
+
| Rack 1 | Controller 1 | 10.1.3.19/24 |
425
+
| Rack 1 | Controller 2 | 10.1.3.20/24 |
426
+
| Rack 2 | Worker 1 | 10.1.3.21/24 |
427
+
| Rack 2 | Worker 2 | 10.1.3.22/24 |
428
+
| Rack 2 | Worker 3 | 10.1.3.23/24 |
429
+
| Rack 2 | Worker 4 | 10.1.3.24/24 |
430
+
| Rack 2 | Worker 5 | 10.1.3.25/24 |
431
+
| Rack 2 | Worker 6 | 10.1.3.26/24 |
432
+
| Rack 2 | Worker 7 | 10.1.3.27/24 |
433
+
| Rack 2 | Worker 8 | 10.1.3.28/24 |
434
+
| Rack 2 | Controller 1 | 10.1.3.29/24 |
435
+
| Rack 2 | Controller 2 | 10.1.3.30/24 |
436
+
| Rack 3 | Worker 1 | 10.1.3.31/24 |
437
+
| Rack 3 | Worker 2 | 10.1.3.32/24 |
438
+
| Rack 3 | Worker 3 | 10.1.3.33/24 |
439
+
| Rack 3 | Worker 4 | 10.1.3.34/24 |
440
+
| Rack 3 | Worker 5 | 10.1.3.35/24 |
441
+
| Rack 3 | Worker 6 | 10.1.3.36/24 |
442
+
| Rack 3 | Worker 7 | 10.1.3.37/24 |
443
+
| Rack 3 | Worker 8 | 10.1.3.38/24 |
444
+
| Rack 3 | Controller 1 | 10.1.3.39/24 |
445
+
| Rack 3 | Controller 2 | 10.1.3.40/24 |
446
+
| Rack 4 | Worker 1 | 10.1.3.41/24 |
447
+
| Rack 4 | Worker 2 | 10.1.3.42/24 |
448
+
| Rack 4 | Worker 3 | 10.1.3.43/24 |
449
+
| Rack 4 | Worker 4 | 10.1.3.44/24 |
450
+
| Rack 4 | Worker 5 | 10.1.3.45/24 |
451
+
| Rack 4 | Worker 6 | 10.1.3.46/24 |
452
+
| Rack 4 | Worker 7 | 10.1.3.47/24 |
453
+
| Rack 4 | Worker 8 | 10.1.3.48/24 |
454
+
| Rack 4 | Controller 1 | 10.1.3.49/24 |
455
+
| Rack 4 | Controller 2 | 10.1.3.50/24 |
456
+
457
+
An example design of three on-premises instances from the same NFC/CM pair, using sequential /19 networks in a /16:
- All network fabric devices (except for the Terminal Server) are set to `ZTP` mode
404
468
- Servers have default factory settings
405
469
470
+
## Firewall rules between Azure to Nexus Cluster.
471
+
472
+
To establish firewall rules between Azure and the Nexus Cluster, the operator must open the specified ports. This ensures proper communication and connectivity for required services using TCP (Transmission Control Protocol) and UDP (User Datagram Protocol).
0 commit comments