Ask Me About Webinar: Data Center Assets - Modeling, Cooling, and CFD Simulation Join our 30-minute expert session on July 10, 2025 (9:00 AM & 5:00 PM CET), to explore Digital Twins, cooling simulations, and IT infrastructure modeling. Learn how to boost resiliency and plan power capacity effectively.Register now to secure your spot!
Release Notes for NetShelter™ Rack Power Distribution Units and In-Line Current Meters with NMC3 Firmware v3.1.1.4
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Network Management Card 3 (NMC3) Operating System and NetShelter RPDU Application
3.1.1.4
Not available for download
Secure NMC System (SNS) Tool for RPDU
3.1.1.4
snst_2.0.0.2_nmc3_rpdu2g_3-1-1-4.exe
PowerNet® SNMP Management Information Base (MIB)
4.5.2
powernet452.mib
Network Management Device IP Configuration Utility
4.0.5
DevIPSetup.exe
IMPORTANT: You must have a valid Secure NMC System (SNS) subscription (SWNMC3PDU-•Y-DIGI) for PDU devices to update the firmware to version 3.0 or later. You must use the SNS tool for Rack Power Distribution Units (RPDUs) to upgrade to firmware version 3.0 or later. This is the only supported upgrade method.
New Features
New Feature
APC Operating System
Support added for user authentication via Lightweight Directory Access Protocol (LDAP).
Support added for TLS 1.3.
Support added for SNMPv3 encryption via the SHA 256 and AES 256 protocols.
APDU9•••, AP8•••, AP7•••B, and AP71••B Applications
Modbus TCP Support. The Rack PDU properties, configuration and status can be queried via Modbus TCP. Modbus TCP can be enabled through CLI modbus command or Rack PDU web page Configuration ⇒ Network ⇒ Modbus ⇒TCP
Link-RX/TX LED is now working for all embedded NMC3s.
Dates in SNMP, such as upsAdvIdentDateOfManufacture, are now available in the correct format, mm/dd/yyyy.
The audit log of the Web UI is displayed in all supported languages.
APDU9•••, AP8•••, AP7•••B, and AP71••B Applications
None
Security Updates
The following security vulnerabilities have been addressed in this release:
CWE-327: Use of a Broken or Risky Cryptographic Algorithm. This software uses a broken or risky cryptographic algorithm or protocol.
Removed support in SSH for diffie-hellman-group14-sha1.
CWE-598: Use of GET Request Method with Sensitive Query Strings. This software uses the HTTP GET method to process a request and includes sensitive information in the query string of that request.
Configuration of HSTS is now independent from HTTP or HTTPS configuration. When HSTS is enabled, an STS header is added to all responses over HTTPS.
CWE-307: Improper Restriction of Excessive Authentication Attempts. This software does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame, making it more susceptible to brute force attacks.
The account now gets locked after bad login attempts.
CWE-523: Unprotected Transport of Credentials. Login pages do not use adequate measures to protect the user name and password while they are in transit from the client to the server. CWE-319: Cleartext Transmission of Sensitive Information. The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
The user is now referred as an index rather than the user name NMC/KrtUvuh39YtQmHbyua297g/usercfg.htm?user=2.
CWE-200: Exposure of Sensitive Information to An Unauthorized Actor
SSH Cipher Block Chaining (CBC) cipher has been removed.
CWE-74: Improper neutralization of special elements in output used bya downstream component (Injection)
CWE-79: Improper neutralization of input during web page generation (Cross-site Scripting).
APDU9•••, AP8•••, AP7•••B, and AP71••B Applications
Synchronized outlet groups do not function when enabled over the network. They do function when enabled locally or when enabled through the In/Out ports.
The Reset RPDU to Defaults action also resets the system settings.
APDU9••• and AP8••• Applications
The Network Port Sharing (NPS) system does not update connected units if one of the following occurred:
The upgrade file was uploaded via SCP without the original filename.
The host device was reset to factory defaults.
APDU9••• Application
It is possible to configure a PDU without a network connection as an NPS host if that PDU has been configured with a static IP address. If one or more members of your NPS group have static IP addresses and you want to manually change the NPS host, ensure the new host has a network connection before changing the host.
When using certain tools (including the MIB Browser) as an SNMP interface to set string configurations on the device, be aware that strings starting with the “#” character may be reserved for special syntax by your interface tool. These strings will be interpreted as colon-separated decimal representations of ASCII character codes and will be stored as such by the Network Management Card. For example, setting #80:68:85 will result in the string “PDU being configured on the NMC.” If values configured in this way are not valid strings (e.g. “#1”), the OID for that value may stop responding to get and set requests. To fix this OID behavior, overwrite the invalid configuration with a valid string via any non-SNMP interface.
The Rack PDU will not warn the user when they have connected too many guest devices to the NPS group. Up to 31 guest devices can be connected to an NPS group.
It may take 30 minutes or more to apply a comprehensive config.ini file to an NPS group.
If the clearing method for an outlet alarm action is set to Auto, outlets are automatically set to the non-action state when an alarm clears, regardless of what state they were in before the alarm. For example, if the alarm action is Off, the outlets are turned on when the alarm clears. This happens even if the outlets were off before the alarm started.