Views:


Article #: KA-04131
Published: 9th Jan 2026
Last reviewed: 9th Jan 2026

Resetting a PDU using SNMP

 

Resetting a PDU

Depending on the circumstances, sometimes it might be necessary to reset a PDU when it becomes unreachable and when no services are available (SSH, WebUI, HTTP(s)) other than SNMP– If the PDU becomes inaccessible via its web UI interface or SSH but SNMP has been previously enabled on the PDU, an end-user could reset its NMC card using SNMP.
 
  1. Introduction
  2. Purpose
  3. Requirements
  4. Procedure
  5. Scripted
 

Introduction

If the PDU becomes inaccessible via its http(s) web interface or SSH but SNMP has been previously enabled on the PDU, an end-user could reset its NMC card using SNMP.
 

Purpose

The objective of this article is to guide an end-user to reset the PDU’s NMC using SNMP, via command line and/or any SNMP browser tool.

Requirements

  • Applies to any G5 & G6 Panduit PDU (Any firmware version)
  • Net-SNMP command line tool (Windows/Linux) Or SNMP MIB Browser (e.g. iReasoning MIB Browser)
  • SNMP Read-Write (RW) community strings (The RW community strings that had been previously configured in the PDU)
 

Procedure

The focus of this procedure is mainly to depict the OID for resetting the PDU, since this process makes a change on the PDU’s NMC; the WR community strings are required.
The process is pretty straightforward, and it could take under a minute to complete for a single PDU and well over two minutes for a POD of daisy-chained PDUs (more than 4 PDUs)
The OID for resetting the NMC card is 1.3.6.1.4.1.19536.10.1.1.3.1.10.1 or module pdug5ConfigNetworkManagementCardReset and can be implemented in the following manner using the net-snmp command line.
The execution of the reset process for the purposes of this article is implemented using SNMP v2c and the Linux OS but can be also used in Windows.
Open a terminal window and execute the following command:
snmpset -c private -v2c 192.168.1.1 1.3.6.1.4.1.19536.10.1.1.3.1.10.1 i 1
After its execution, the PDU will reset and will come back online after its reboot
Structure of the snmpset command used above
snmpset -c private -v2c 192.168.1.1 1.3.6.1.4.1.19536.10.1.1.3.1.10.1 i 1

 
snmpsetNet-snmp command (used to modify existing configuration settings, -c switch specifies the community string)
privateCommunity string
v2cSNMP version
192.168.1.1PDU’s IP address
1.3.6.1.4.1.19536.10.1.1.3.1.10.1PDU NMC’s reset OID
iData type being written to PDU (i=integer)
1Value being written to PDU (1 = reset)
 

Scripted

For automation purposes, resetting a PDU can also be scripted, the following example is written in Korn shell for Linux, which can also be interpreted by any Bourne (sh) compatible shell.


#!/usr/bin/ksh
PDU_IP=$1
COMM='private'

nmc_reset(){
echo "Resetting PDU: " $PDU_IP
snmpset -c $COMM -v2c $PDU_IP 1.3.6.1.4.1.19536.10.1.1.3.1.10.1 i 1
}

if [[ -z $1 ]];
then
        echo " No parameters passed. - Usage: reset_pdu PDUIPADDRESS"
        exit 1
else
        nmc_reset $PDU_IP
ping -D -O $1
fi


The above script can be executed by passing the PDU’s IP address as its single parameter e.g. reset_pdu 192.168.1.1 – if no IP address is provided the script provides its proper usage (example below)




When an IP address is provided, the script will run and depict a series of PING requests immediately after its execution, with the purpose of depicting when the PDU comes back online from its reboot process (example below)



Once the PDU comes back online, it will respond to the PING requests from the script (as depicted above), at this point the script can be manually stopped using Ctrl-z.





Global World Headquarters  |  18900 Panduit Drive  |  Tinley Park, IL 60487                                                    www.panduit.com/contact-us