Article #: KA-04134
Published: 9th Jan 2026
Last reviewed: 9th Jan 2026
How to collect an SNMP walkfile from a PDU
Introduction
From time to time, it may be required to collect a walkfile from any Panduit PDUs. Walkfiles are beneficial for efficiently discovering, mapping, and troubleshooting network devices by automatically collecting vast amounts of of data (OIDs) from an entire MIB subtree in one simple step.Purpose
The purpose of this article is to provide the end-user with the required steps to effectively collect a walkfileRequirements
- Applies to any G5 & G6 Panduit PDU (Any firmware version)
- Enabled SNMP Access on the PDU
- Windows or Linux OS(most distributions will work)
- Net-SNMP installed on the workstation collecting the walk
Procedure
To collect the snmpwalk file, you need to have the IP address of the PDU and the read SNMP community strings.Once you have these two pieces of information, execute the following command:
snmpwalk –v2c –ObenU –c [SNMP READ COMMUNITY][IP ADDRESS] 1.3 > [TEXT FILE]
Where
[SNMP READ COMMUNITY] is the SNMP read community string
[IP ADDRESS] is the IP address of the target PDU
Example:
snmpwalk -v2c -Obenu -c public 192.168.1.1 1.3 >WalkOutput.txt
Afte the command has been successfully executed, you should see a message similar to “No more variables left in this MIB View” at the end of the output file (Which in the example is called WalkOutput.txt) – The following page shows an excerpt from a typical snmpwalk output file.
Some Pages deleted for brevity