Skip to content

Commit 8de8f17

Browse files
SatyanarayanatalluriSatyanarayanatalluri
committed
[operator-nexus] Add iDRAC configuration and firewall rules
1 parent 72bcd57 commit 8de8f17

File tree

1 file changed

+83
-0
lines changed

1 file changed

+83
-0
lines changed

‎articles/operator-nexus/howto-platform-prerequisites.md

Lines changed: 83 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -397,11 +397,94 @@ Terminal Server has been deployed and configured as follows:
397397
- puretune -set PS_RDMA_STALE_OP_THRESH_MS 5000 "PURE-209441";
398398
- puretune -set PS_BDRV_REQ_MAXBUFS 128 "PURE-209441";
399399
400+
## iDRAC IP Assignment
401+
402+
Before deploying AODS software, it’s best for the Operator to set the iDRAC IPs while organizing the hardware racks. Here’s how to map servers to IPs:
403+
404+
- Assign IPs based on each server’s position within the rack.
405+
- Use the fourth /24 block from the /19 subnet allocated for fabric.
406+
- Start assigning IPs from the bottom server upwards in each rack, beginning with .11.
407+
- Continue to assign IPs in sequence to the first server at the bottom of the subsequent rack.
408+
409+
### Example
410+
411+
Fabric range: 10.1.0.0-10.1.31.255 – iDRAC subnet at fourth /24 is 10.1.3.0/24
412+
413+
| Rack | Server | iDRAC IP |
414+
|--------|---------------|---------------|
415+
| Rack 1 | Worker 1 | 10.1.3.11/24 |
416+
| Rack 1 | Worker 2 | 10.1.3.12/24 |
417+
| Rack 1 | Worker 3 | 10.1.3.13/24 |
418+
| Rack 1 | Worker 4 | 10.1.3.14/24 |
419+
| Rack 1 | Worker 5 | 10.1.3.15/24 |
420+
| Rack 1 | Worker 6 | 10.1.3.16/24 |
421+
| Rack 1 | Worker 7 | 10.1.3.17/24 |
422+
| Rack 1 | Worker 8 | 10.1.3.18/24 |
423+
| Rack 1 | Controller 1 | 10.1.3.19/24 |
424+
| Rack 1 | Controller 2 | 10.1.3.20/24 |
425+
| Rack 2 | Worker 1 | 10.1.3.21/24 |
426+
| Rack 2 | Worker 2 | 10.1.3.22/24 |
427+
| Rack 2 | Worker 3 | 10.1.3.23/24 |
428+
| Rack 2 | Worker 4 | 10.1.3.24/24 |
429+
| Rack 2 | Worker 5 | 10.1.3.25/24 |
430+
| Rack 2 | Worker 6 | 10.1.3.26/24 |
431+
| Rack 2 | Worker 7 | 10.1.3.27/24 |
432+
| Rack 2 | Worker 8 | 10.1.3.28/24 |
433+
| Rack 2 | Controller 1 | 10.1.3.29/24 |
434+
| Rack 2 | Controller 2 | 10.1.3.30/24 |
435+
| Rack 3 | Worker 1 | 10.1.3.31/24 |
436+
| Rack 3 | Worker 2 | 10.1.3.32/24 |
437+
| Rack 3 | Worker 3 | 10.1.3.33/24 |
438+
| Rack 3 | Worker 4 | 10.1.3.34/24 |
439+
| Rack 3 | Worker 5 | 10.1.3.35/24 |
440+
| Rack 3 | Worker 6 | 10.1.3.36/24 |
441+
| Rack 3 | Worker 7 | 10.1.3.37/24 |
442+
| Rack 3 | Worker 8 | 10.1.3.38/24 |
443+
| Rack 3 | Controller 1 | 10.1.3.39/24 |
444+
| Rack 3 | Controller 2 | 10.1.3.40/24 |
445+
| Rack 4 | Worker 1 | 10.1.3.41/24 |
446+
| Rack 4 | Worker 2 | 10.1.3.42/24 |
447+
| Rack 4 | Worker 3 | 10.1.3.43/24 |
448+
| Rack 4 | Worker 4 | 10.1.3.44/24 |
449+
| Rack 4 | Worker 5 | 10.1.3.45/24 |
450+
| Rack 4 | Worker 6 | 10.1.3.46/24 |
451+
| Rack 4 | Worker 7 | 10.1.3.47/24 |
452+
| Rack 4 | Worker 8 | 10.1.3.48/24 |
453+
| Rack 4 | Controller 1 | 10.1.3.49/24 |
454+
| Rack 4 | Controller 2 | 10.1.3.50/24 |
455+
456+
An example design of three instances using sequential /19 networks in a /16:
457+
458+
| Instance | Fabric Range | iDRAC subnet |
459+
|------------|-------------------------|--------------|
460+
| Instance 1 | 10.1.0.0-10.1.31.255 | 10.1.3.0/24 |
461+
| Instance 2 | 10.1.32.0-10.1.63.255 | 10.1.35.0/24 |
462+
| Instance 3 | 10.1.64.0-10.1.95.255 | 10.1.67.0/24 |
463+
400464
### Default setup for other devices installed
401465
402466
- All network fabric devices (except for the Terminal Server) are set to `ZTP` mode
403467
- Servers have default factory settings
404468
469+
## Firewall rules between Azure to undercloud.
470+
471+
To establish firewall rules between Azure and the undercloud, the Operator must open the specified ports. This ensures proper communication and connectivity for required services.
472+
473+
474+
| S.No | Source | Destination | Port (TCP/UDP) | Bidirectional | Rule Purpose |
475+
|------|------------------------|-----------------------|-----------------|----------------|----------------------------------------------------------|
476+
| 1 | Azure virtual Network | Undercloud | 22 TCP | No | For SSH to undercloud servers from CM subnet |
477+
| 2 | Azure virtual Network | Undercloud | 443 TCP | No | For accessing undercloud nodes iDRAC |
478+
| 3 | Azure virtual Network | Undercloud | 5900 TCP | No | Gnmi |
479+
| 4 | Azure virtual Network | Undercloud | 6030 TCP | No | Gnmi Certs |
480+
| 5 | Azure virtual Network | Undercloud | 6443 TCP | No | For accessing undercloud K8S cluster |
481+
| 6 | Undercloud | Azure virtual Network | 8080 TCP | Yes | For mounting ISO image into iDRAC and NNF runtime upgrade|
482+
| 7 | Undercloud | Azure virtual Network | 3128 TCP | No | Proxy to connect to public Azure endpoints |
483+
| 8 | Undercloud | Azure virtual Network | 53 TCP and UDP | No | DNS |
484+
| 9 | Undercloud | Azure virtual Network | 123 UDP | No | NTP |
485+
| 10 | Undercloud | Azure virtual Network | 8888 TCP | No | For connecting to Cluster Manager webservice |
486+
| 11 | Undercloud | Azure virtual Network | 514 TCP and UDP | No | For accessing undercloud logs from Cluster Manager |
487+
405488
## Install CLI extensions and sign-in to your Azure subscription
406489
407490
Install latest version of the

0 commit comments

Comments
 (0)