Cabinets

Managing Cabinets
Cabinets represent one of the most commonly replicated containers within the data center - it is the mechanism by which you move from a 2D world of the floor plan to a 3D world to describe the vertical element. The industry standard unit of measurement is the Rack Unit (RU), and is approximately 1.75".

The Edit Cabinets button will take you to the Cabinet Manager screen (seen below), which should not be confused with the Cabinet Navigator screen. The Cabinet Manager is strictly for defining the container, while the Cabinet Navigator is for working with devices within that container.

Database Information
The data for describing cabinets is stored within the fac_Cabinet table of the MySQL database. It references foreign keys of DataCenterID->fac_DataCenter.DataCenterID and AssignedTo->fac_Department.DepartmentID (though if left blank, it is assigned as General Use). The CabinetID is referenced as a foreign key from fac_PowerDistribution and fac_Device.



Field Information
'''Note: Not all database fields are managed within the Cabinet Manager screen. Some are updated through the Coordinate Mapper.'''


 * CabinetID - Displayed to the user in the picklist as the value of the Location field, this is a unique key assigned automatically by MySQL. It is referenced as a foreign key by fac_PowerDistribution and fac_Device.
 * DataCenterID - The user picklist will show the name of the data center, but the database field stores the foreign key DataCenterID.
 * Location - The name for this cabinet. It is highly suggested that a grid system be used to denote cabinets (typically the front left edge designates the naming).  Naming your cabinets Infra-1, Infra-2, Infra-3 isn't intuitive and can become very difficult to scale.
 * AssignedTo - If this cabinet is reserved for the use of a single customer, you can assign it to them. This is useful if you are billing for your services and need to attach entire cabinets to a single department.  If it is a general population cabinet, the value stored in the database can either be null or 0.  If assigned, it must match up as a foreign key to fac_Department.DepartmentID.
 * ZoneID - Not currently implemented. Reserved for future use.
 * CabinetHeight - The height of the cabinet, in RU. The most common in use today seems to be 42U and fits through most doors.
 * Model - A freeform field for entering the model number of the cabinet.
 * MaxKW - The maximum KW supported in this cabinet. Currently you need to account for any redundancy requirements, but in future versions this should be handled via a cabinet level configuration item.
 * RedundantPower - Not currently implemented. Reserved for future use.
 * MaxWeight - The maximum weight supported in this cabinet. Be sure to check the maximum weight that your floor can support in this footprint, not just what the cabinet can support!
 * InstallationDate - The date that you commissioned this cabinet for use.
 * MapX1 - Picked from the Coordinate Mapper screen
 * MapX2 - Picked from the Coordinate Mapper screen
 * MapY1 - Picked from the Coordinate Mapper screen
 * MapY2 - Picked from the Coordinate Mapper screen
 * TempSensorIP (Added in v2.0) - The IP address of an SNMP temperature sensor for this cabinet
 * TempSensorOID (Added in v2.0) - The SNMP OID for the temperature reading (in 1/10 degree increments) on the sensor defined above
 * TempSensorCommunity (Added in v2.0) - The SNMP Community for the SNMP sensor defined above

Next Topic - Navigating Cabinets

or

Return to the Main Page