How to troubleshoot an EL2P network module lockup

Contents

1. Introduction
2. Purpose
3. Procedure
4. Troubleshooting

Introduction

EL2P PDU's network module can occasionally enter an unresponsive state where it cannot be reached via its web UI, SSH, SNMP, or Redfish API. In these cases, a standard reset or power cycle of the outlet section does not restore management connectivity, even though the outlets themselves continue to deliver power normally to connected loads.

Purpose

This article provides the recovery procedure for the network module that has become fully locked up and does not respond to a standard reset or reboot. Following this procedure restores management access without requiring an RMA or on-site hardware swap.

Procedure

• Locate the recessed Reset button on the EL2P network module.

• Using a paperclip or similar tool, press and hold the Reset button for more than 20 seconds, then release. This forces a hard recovery of the network module's processor beyond a normal warm reset.

• Allow the network module 2–3 minutes to fully reinitialize and obtain network connectivity.

• Confirm management access has been restored by logging in to the web UI or pinging the assigned management IP.

• Once management access is restored, upgrade the network module firmware to version 1.6.8 to prevent recurrence. The upgrade can be performed via the web UI under Settings--> System management --> Actions --> Upload firmware, or by uploading the firmware image through the supported management interface via USB.

• After the upgrade completes and the module reboots, verify the firmware version is reporting as 1.6.8 and confirm normal operation.

Troubleshooting

If the network module remains unresponsive after the >20 second reset:

• Verify the PDU is receiving input power and that outlets are still energized (rules out a full PDU failure vs. a network module issue).

• Confirm the Ethernet link light on the network module is active and that the switchport is up; try a known-good cable and switchport to rule out an L1 issue.

• If a DHCP-assigned address is expected, check DHCP lease activity on the network side. If using a static address, connect via the local serial/console interface to verify configuration.

• If the module still does not come up after a second >20 second reset attempt, unscrew the 2 hex screws holding the module together, unplug the ribbon cable from the back, wait 1 minute and re-plug back in. This procedure should re-energize the PDU.