Networking and Fabric Integration
What this domain tests
Networking and Fabric Integration covers adapter selection, cabling, link aggregation, VLANs, and fabric integration for PowerEdge and modular systems. Questions mix physical-layer choices with configuration that affects redundancy and management separation.
Adapter and cabling rules
- LOM or OCP 3.0 slots provide onboard or modular network ports; PCIe adapters add ports but consume slots and airflow.
- Match the transceiver to the port: SFP28 for 25GbE, QSFP28 for 100GbE, DAC for short runs, and the correct fiber type for distance.
- The iDRAC dedicated port keeps management traffic separate. Shared LOM mode carries iDRAC traffic on a host port and requires a dedicated management VLAN.
- Redundant links should use separate physical switches. A single switch with two ports protects against cable failure, not switch failure.
Configuration rules
- LACP or static teaming must match the switch configuration. A mismatch causes a loop, a blocked link, or no traffic.
- Tag management, storage, and VM traffic on separate VLANs where the design requires isolation.
- For iSCSI, use dedicated adapters or VLANs, enable jumbo frames consistently end to end, and confirm the initiator and target see the same MTU.
- SR-IOV and NPAR change how a physical port is presented to the OS; confirm driver and firmware support before enabling.
- In MX chassis, fabric switches and M-Mode networking change the uplink and management model. Verify the chassis fabric type before cabling.
Worked example
A two-node cluster needs redundant 25GbE storage traffic. Each node gets an OCP adapter with two SFP28 ports, cabled to two different switches. The ports are configured as an LACP bond with a storage VLAN, jumbo frames are enabled on both switches and hosts, and iDRAC remains on its dedicated port. The reasoning is that redundancy must survive a switch failure and management traffic must not share the storage path.
Traps
- Using the shared LOM without a management VLAN.
- Mismatched LACP settings between host and switch.
- Mixing jumbo frame settings on one hop.
- Assuming any SFP fits any port.
- Forgetting that a modular chassis has its own fabric and management design.