I85PREP
⌘ K
Dell PowerEdge Operate 2023 study materials
Dell PowerEdge Operate 2023 study resources

Dell PowerEdge Operate 2023: Installation, Cabling, and Initial Configuration

Dell PowerEdge Operate 2023 · Work through your exam, one topic at a time.

All guide sections

Installation, Cabling, and Initial Configuration

What this domain tests

Installation, Cabling, and Initial Configuration covers physical commissioning: rail and cable management, power feeds, management and data cabling, first-boot settings, and the handoff to OS deployment. Questions are practical and often ask what you configure before the server leaves the staging bench.

Rack and power

  • Use the correct rail kit for the chassis depth and square or round-hole rack; a cable management arm needs extra rear clearance.
  • Connect PSUs to different PDUs on separate circuits for true redundancy; check PSU rating and connector type.
  • Leave airflow blanks in empty drive and riser bays. Label both ends of every cable and record the iDRAC service tag.

Management and data cabling

  • The iDRAC dedicated port is the preferred management path; the shared LOM option carries iDRAC traffic on a host adapter and needs VLAN separation.
  • Use CAT6A or better for 10GbE BASE-T, DAC for short in-rack 25GbE, and the correct optics for fiber.
  • For iDRAC Direct, connect a laptop to the micro-USB port and browse to the iDRAC IP; no network is required.
  • Redundant network links should terminate on different switches, not two ports on one switch.

First-boot configuration

  • Set a static iDRAC IP, gateway, DNS, and NTP before adding the host to management. Correct time is required for certificates and logs.
  • Choose UEFI boot mode for modern OSes, enable Secure Boot if required, and confirm TPM presence.
  • Create the boot virtual disk first, usually RAID 1 on BOSS or a pair of drives.
  • Set the boot order, disable unused PXE options, and record the configuration in the build sheet.

Worked example

A new R760 arrives with two 10GbE SFP+ ports and a dedicated iDRAC port. The engineer racks it, connects PSUs to A and B feeds, patches iDRAC to the management VLAN, sets a static address, DNS, and NTP, then configures the two host ports as a LACP bond to separate switches. Only then is the OS deployed. The reasoning is that management reachability and time sync must exist before automation and certificates are applied.

Traps

  • Using the shared LOM for iDRAC without a management VLAN.
  • Forgetting NTP; expired or invalid certificates then break iDRAC logins.
  • Installing rails without checking rear clearance for the CMA.
  • Leaving iDRAC on DHCP in a production rack.