Article #: KA-03901
Published: 09/22/2025
Last reviewed: 09/22/2025
G6 PDU Not Accessible After Network Change
Contents
Introduction
This article addresses connectivity issues with Panduit G6 PDUs following network infrastructure changes such as VLAN reconfiguration, subnet modifications, DHCP server changes, or network equipment replacement. The G6 PDU's network behavior follows specific patterns that, when understood, allow for systematic recovery of network access without requiring physical PDU replacement or extended downtime.Purpose
This article provides field technicians and network administrators with step-by-step procedures to restore network access to Panduit G6 PDUs after network changes. It covers multiple recovery methods ranging from simple IP discovery to direct connection and serial console access, ensuring PDU accessibility can be restored regardless of the network situation.
Procedure
Method 1: Identify Current PDU IP Address
Check PDU Local Display
Press any button on the PDU's OLED display to wake it
Navigate using control buttons: Menu → Setup → Network → IPv4
Document the displayed IP address
If display shows 0.0.0.0, the PDU has no IP assignment
Verify Physical Network Connection
Locate Ethernet port on PDU controller (Figure 1, page 9)
Check LED indicators:
Solid green (right): Link established
Flashing yellow (left): Network activity
If no LEDs are lit, verify cable and switch port
Understand Default IP Behavior
According to manual page 9-10:
PDU searches for DHCP on power-up or cable connection
If DHCP found: Automatically obtains IP
If no DHCP after several minutes: Defaults to 192.168.0.1
Unplugging/replugging network cable restarts this process
Method 2: Direct Connection Recovery
When PDU is unreachable on production network, establish direct connection (Appendix G, pages 131-136):
Configure PC Network Adapter
IP Address: 192.168.0.10
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.0.1
DNS Server: 192.168.0.1
Physical Connection
Disconnect PDU from production network
Connect PC directly to PDU Ethernet port with patch cable
Wait 30 seconds for link establishment
Access Web Interface
Open browser to: https://192.168.0.1
Accept certificate warning (self-signed certificate)
Login: admin / 12345678 (default)
Reconfigure Network Settings
Navigate: Settings → Network Settings → IP Configuration
Select appropriate configuration:
DHCP: For automatic IP assignment
Static: For fixed IP address
Enter new network parameters
Save configuration
Return to Production
Reconnect PDU to production network
Allow 60 seconds for network initialization
Verify connectivity at new IP address
Method 3: Serial Console Configuration
If network access is completely unavailable (Appendix H, pages 137-147):
Physical Connection
Obtain MA017 cable or create custom cable (pinout page 139)
Connect to "Serial In" port on PDU (Figure 2, page 10)
Terminal Configuration
Baud Rate: 115200
Data Bits: 8
Parity: None
Stop Bits: 1
Flow Control: None
Login and Configure
Login with admin credentials
View current network configuration:
net tcpip
Set DHCP mode:
net tcpip dhcp
Or configure static IP:
net tcpip static 192.168.1.100 255.255.255.0 192.168.1.1
Confirm reboot when prompted
Method 4: Recovery for Daisy-Chained PDUs
For daisy-chain configurations (Section 5, page 87):
Identify Primary PDU
Only PDU1 (primary) has network configuration
All others connect through PDU Out/In ports
Restore Primary PDU Access
Use Methods 1-3 above on primary PDU only
Once primary is accessible, all chained PDUs become available
Restart Chain if Needed
Press and hold reset button on primary PDU for 8-10 seconds
This re-synchronizes the daisy chain without affecting outlet states
Troubleshooting
1. Cannot access at default IP 192.168.0.1
Resolution:
Verify PC is configured for 192.168.0.x subnet
Disable all other network adapters on PC
Clear browser cache and cookies
Try different browser or incognito mode
Ensure using HTTPS not HTTP
2. PDU not obtaining DHCP address
Resolution:
Verify DHCP server is operational
Check VLAN configuration on switch port
Ensure DHCP scope has available addresses
Review DHCP server logs for requests
Try static IP assignment instead
3. Serial connection not working
Resolution:
Verify correct COM port selected
Check cable continuity with multimeter
Ensure using correct pinout (page 139)
Try different terminal software (PuTTY, HyperTerminal)
Confirm baud rate 115200
4. Web interface shows "refused to connect"
Resolution:
Verify using HTTPS:// prefix (page 15)
Check if HTTP/HTTPS is enabled (page 23)
Clear browser SSL/TLS cache
Try IP address instead of hostname
Verify no firewall blocking port 443
5. Changes not persisting after reboot
Resolution:
Ensure clicking "Save" after changes
Wait for save confirmation before rebooting
Check if PDU in USB configuration mode
Verify admin privileges for user account
6. Multiple PDUs showing same IP
Resolution:
Check for RNA (Redundant Network Access) mode
Verify daisy chain configuration
Look for IP conflicts on network
Ensure each standalone PDU has unique IP