Sun Microsystems, Inc.  Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1400752.1
Update Date:2012-02-07
Keywords:

Solution Type  Technical Instruction Sure

Solution  1400752.1 :   SunMD PDU/CDU locations  


Related Items
  • Sun Modular Datacenter S20
  •  
  • Sun Modular Datacenter D20
  •  
Related Categories
  • PLA-Support>Sun Systems>SPARC>SPARC-MISC>SN-SPARC: MD-x20
  •  
  • .Old GCS Categories>Sun Microsystems>Servers>Modular Datacenter
  •  


This article describes how to locate individual rack power distribution units (PDUs) within a SunMD, and also describes the nomenclature used to distinguish individual PDUs.

In this Document
  Goal
  Solution


Applies to:

Sun Modular Datacenter D20 - Version: Not Applicable and later   [Release: N/A and later ]
Sun Modular Datacenter S20 - Version: Not Applicable and later    [Release: N/A and later]
Information in this document applies to any platform.

Goal

Understanding the nomenclature used in identifying PDUs within a rack, and physically locating a PDU based on its IP adderss or fault message.


Solution

The SunMD racks employ a modular power distribution system with smart Power Distribution Units or PDUs, which plug into the IEC 60309 outlets which hang above carrel where each rack is normally parked, and CDUs or Cabinet Distribution Units which plug into rack's PDUs and provide IEC 60320 power outlets for equipment installed within each rack.

Each CDU has six IEC 60320-C13 outlets and two IEC 60320-C19 outlets.

Every SunMD rack has 1 PDU from panel A with 3 CDUs, 1 PDU from panel B with 3 CDUs.

A high-power X-Option or upgrade adds 1 slave PDU from panel A with 2 CDUs, 1 slave PDU from panel B with 2 CDUs.

High-power describes the number of PDUs and CDUs, and should not be confused with  high-voltage which describes the external power feeds to the SunMD.

Slave PDUs have their own power cord which plugs into an IEC 60309 outlet above the rack carrel, but have no IP address.  The master  PDUs have the IP address and serial console port.  The slave PDUs communicate with their master PDU with a proprietary communications link.

Master PDU IP scheme:
10.10.10.XY (Default is: 192.168.1.254)
X=1 PDU is fed from breaker panel A
X=2 PDU is fed from breaker panel B
Y=rack number (1-8)

IMS /etc/hosts entries:
#
# Primary PDU's
#
10.10.10.11    rack1p
10.10.10.12    rack2p
10.10.10.13    rack3p
10.10.10.14    rack4p
10.10.10.15    rack5p
10.10.10.16    rack6p
10.10.10.17    rack7p
10.10.10.18    rack8p
#
# Secondary PDU's
#
10.10.10.21    rack1s
10.10.10.22    rack2s
10.10.10.23    rack3s
10.10.10.24    rack4s
10.10.10.25    rack5s
10.10.10.26    rack6s
10.10.10.27    rack7s
10.10.10.28    rack8s

#

Primary and Secondary refer to the AC breaker panels at the rear of the SunMD, and should not be confused with master and slave PDUs.

Every rack has one Primary and one Secondary PDU.  With the high-power option, every rack with the exception of rack1 also has a Primary slave PDU and a Secondary slave PDU.

The Primary PDUs plug into IEC 60309 outlets fed from AC breaker panel A at the rear of the SunMD, Secondary PDUs plug into outlets fed from AC breaker panel B.  Each IEC 60309 outlet has its own circuit breaker in either AC breaker panel A or B.

The master PDUs are the ones toward the top of the rack, and are designated TowerA.
The slave PDUs are optional, and if installed are the ones towards the bottom of the rack, designated TowerB.

Rack 1 only has the two master PDUs, one from breaker panel A and one from breaker panel B.

Example:

All PDUs in Rack 1 fail (only 2 PDUs in Rack 1, one from panel A, one from panel B)

rack1p  EVENT: Tower "TowerA" [A] detected a status error -- reason = Fan Fail
rack1s  EVENT: Tower "TowerA" [A] detected a status error -- reason = Fan Fail

Master and slave PDUs from panel A in Rack 2 fail (4 PDUs total in this rack)

rack2p  EVENT: Tower "TowerA" [A] detected a status error -- reason = Fan Fail
rack2p  EVENT: Tower "TowerB" [B] detected a status error -- reason = Fan Fail


All 4 PDUs in Rack 3 fail (master and slave from panel A, master and slave from panel B)

rack3p  EVENT: Tower "TowerA" [A] detected a status error -- reason = Fan Fail
rack3p  EVENT: Tower "TowerB" [B] detected a status error -- reason = Fan Fail
rack3s  EVENT: Tower "TowerA" [A] detected a status error -- reason = Fan Fail
rack3s  EVENT: Tower "TowerB" [B] detected a status error -- reason = Fan Fail



The p PDUs are the ones fed from breaker panel A, s PDUs are fed from breaker panel B.

The p = Primary = panel A PDUs are on the container wall side of the rack.  The s = Secondary = anel B PDUs are on the aisle side of the rack.

The TowerA  PDUs are the Master PDUs  which have the Ethernet and serial port connections.  The TowerA PDUs are located in the top half of each rack.  The TowerB PDUs are the Slave PDUs (available with the high-power option) and are located in the bottom half of the payload racks 2-8.  Rack 1 has only the two Master aka TowerA PDUs.

Examples:

rack2p  EVENT: Tower "TowerB" [B] detected a status error -- reason = Fan Fail
Indicates a problem with the slave (TowerB) PDU in rack2 which is fed from AC breaker panel A (p = primary = panel A).  It is physically located on the container wall side of rack2, in the bottom half of the rack.

rack3s  EVENT: Tower "TowerA" [A] detected a status error -- reason = Fan Fail
Indicates a problem with the master (TowerA) PDU in rack3 which is fed from AC breaker panel B (s = secondary = panel B).  It is physically located on the aisle side of rack3, in the top half of the rack.




Attachments
This solution has no attachment
  Copyright © 2012 Sun Microsystems, Inc.  All rights reserved.
 Feedback