Article #: KA-03900
Published: 09/22/2025
Last reviewed: 09/22/2025
Integrating G6 PDUs with DCIM Software
Contents
Introduction
The Panduit G6 Intelligent PDU integrates with Data Center Infrastructure Management (DCIM) software primarily through SNMP using the Panduit-specific PDU MIB file. The PDU also supports REST API (Redfish) for modern integrations. DCIM platforms use the MIB file to understand the PDU's data structure and available metrics for monitoring and alerting.Purpose
This article provides guidance for integrating Panduit G6 PDUs with DCIM software, focusing on:
- Loading and using the Panduit MIB file in DCIM platforms
- Configuring SNMP polling and traps
- Understanding OID structure for custom monitoring
- Setting up REST API integration where supported
- Troubleshooting common integration issues
Procedure
1. MIB File Integration
Obtaining the Panduit MIB File:
Download from Panduit.com → Support → Download Center → PDUs
File typically named: PANDUIT-G6-MIB.mib or similar
Ensure you have the latest version matching your firmware
Loading MIB into DCIM Software:
For common DCIM platforms:
Import MIB via Device Discovery → Custom Devices
Nlyte: Administration → Device Types → Import MIB
Sunbird: Configuration → Import → SNMP MIB
Device42: Tools → Import → SNMP MIB Import
Key MIB Structure (Based on Manual References):
Enterprise OID: 1.3.6.1.4.1.19536
The MIB defines trap codes, sensor types, and measurement points
Supports up to 6 daisy-chained PDUs
Maximum 8 environmental sensors per controller
2. SNMP Configuration
Enable SNMP on G6 PDU:
Navigate to Settings → SNMP Manager → SNMP General
Enable SNMP Access
Select Version (v1/v2c or v3)
Configure SNMP Port (default: 161)
SNMP v1/v2c Setup:
- Read Community: [your_read_string]
- Write Community: [your_write_string]
- Manager IP: [DCIM_server_IP] or 0.0.0.0 for any
SNMP v3 Setup (Recommended):
Security Levels:
- NoAuthNoPriv: No authentication
- AuthNoPriv: MD5/SHA authentication
- AuthPriv: Authentication + AES encryption (128/192/256)
Configure SNMP Traps:
Go to Settings → SNMP Manager → Trap Receivers
Configure up to 5 trap receivers
Set trap server IP and community/credentials
Select trap types based on manual's trap codes (Appendix E)
Trap Categories from Manual:
Critical: Codes 1-197 (power thresholds, breaker states)
Warning: Codes 200-362 (threshold warnings)
Informational: Codes 380-766 (status changes, user activity)
Clear: Codes 770-859 (alarm cleared)
Enhanced Security: Codes 1100-1110 (rack access)
Phase Power: Codes 1121-1153 (phase measurements)
3. REST API (Redfish) Integration
Supported Endpoints (Per Manual Appendix L):
GET Methods:
/redfish/v1/SessionService
/redfish/v1/AccountService
/redfish/v1/Managers
/redfish/v1/PowerEquipment/RackPDUs
/redfish/v1/PowerEquipment/RackPDUs/{pdu_id}
/redfish/v1/PowerEquipment/RackPDUs/{pdu_id}/Sensors
/redfish/v1/EventService
POST Methods:
/redfish/v1/SessionService/Sessions
/redfish/v1/AccountService/Accounts
DELETE Methods:
/redfish/v1/SessionService/Sessions/{session_id}
/redfish/v1/AccountService/Accounts/{username}
4. Data Collection Best Practices
Recommended Polling Intervals:
Based on Data Log configuration (1-1440 minutes)
Default: 10 minutes (Section 2, page 52)
Maximum 2000 records before overwrite
Daisy Chain Considerations:
Up to 6 PDUs per chain (same SKU, same firmware)
Maximum cable length: 15m (49 ft)
Access via single IP address
Primary PDU aggregates all data
5. DCIM Integration Workflow
Initial Setup:
Load Panduit MIB file into DCIM
Add PDU using SNMP discovery
Verify all OIDs are recognized
Configure Monitoring:
Set polling intervals
Map PDU metrics to DCIM dashboards
Configure threshold alerts
Validate Integration:
Test SNMP walk
Verify trap reception
Check data accuracy
Troubleshooting
Common Issues:
1. MIB Not Loading
Ensure MIB file matches firmware version
Check for MIB syntax errors
Verify DCIM supports Panduit Enterprise OID
2. SNMP No Response
Verify SNMP is enabled (Web GUI)
Check community strings match
Ensure firewall allows port 161/162
Test with: snmpwalk -v2c -c [community] [IP] 1.3.6.1.4.1.19536
3. Missing Sensor Data
Maximum 8 sensors per controller
Check sensor connection at RJ45 ports
Verify sensor compatibility (Appendix J)
4. Trap Not Received
Verify trap receiver configuration
Check SNMP trap port (162)
Review trap codes in manual Appendix E
Enable specific trap types in Event Notifications
5. Authentication Issues
Account locks after 3 failed attempts
Default lockout duration: 1440 minutes (24 hours)
Use CLI to unlock: usr unlock [username]