H20-923_V1.0 HCSP-Field-Data Center Facility V1.0 Questions and Answers

In Huawei alarm management,masking rulesare used to control how alarms are handled and displayed during specific conditions, such as planned maintenance, commissioning, device replacement, or known temporary abnormalities. When a masking rule is applied, the system can change how an alarm is classified so that O&M staff can distinguish between alarms that require immediate action and alarms that are expected or should be excluded from operational statistics. Two key statuses that masking rules can assign areMaintenanceandInvalid.Maintenanceindicates the alarm is generated during an approved maintenance activity (for example, power-off tests, sensor rewiring, cooling maintenance), so it is treated as expected and does not trigger normal escalation logic.Invalidindicates the alarm is not considered effective for operational follow-up—commonly used when a point is confirmed to be non-applicable, temporarily disabled, or its triggering condition is not meaningful to current operations. By contrast,ValidandStandardrepresent normal alarm handling states rather than outcomes specifically “identified by masking rules.”

NetEco is an enterprise management application with specific runtime dependencies, including supported operating system versions, database/middleware compatibility, CPU/memory/storage requirements, and network/security prerequisites. Because of these dependencies, Huawei does not treat NetEco as “hypervisor-agnostic for any virtualization platform.” In practice, NetEco deployment in virtualized environments is supported only when the virtualization stack meets Huawei’s compatibility requirements, such as validated hypervisors/virtualization solutions, proper virtual hardware settings, and resource reservation rules to ensure stable performance (especially for alarm processing, historical data storage, and northbound integration tasks). If deployed on an unverified virtualization platform, issues may occur such as clock drift, I/O latency, database performance bottlenecks, unstable NIC behavior, or unsupported VM device models, which can impact data collection, event correlation, and overall system stability. Therefore, the correct interpretation is that NetEco can be deployed onsupported/verifiedvirtualization platforms, not onanyvirtualization platform.

Huawei’s ECC800-Pro supports PUE (Power Usage Effectiveness) management as part of its energy efficiency and green data center features. In practical O&M, different sites calculate PUE differently depending on metering topology, what loads are included (IT load only vs. auxiliary loads), and whether the site uses integrated modules (UPS, cooling, lighting, etc.) or external systems. To handle these real-world differences, the ECC800-Pro provides two PUE configuration approaches on the WebUI.“Standard”mode is used when the site’s metering points and calculation logic align with a predefined Huawei template, enabling rapid commissioning and consistent reporting.“User-defined”mode is used when the customer’s metering structure or management requirements differ—allowing engineers to select specific measurement points, define inclusion/exclusion rules, and tailor the calculation path so that displayed PUE matches the site’s accepted KPI definition. This dual-mode design ensures PUE is both standardized where possible and flexible where necessary, improving energy analysis accuracy and supporting optimization actions.

This statement is incorrect because it combines two different frame configurations into one description. In the UPS5000-H family,cabinet composition depends on capacity. For theUPS5000-H-1200 kVA, the user manual’s exterior description shows asingle power cabinet plus a bypass cabinet, together with theMDU. In other words, 1200 kVA is not described as “two power cabinets + one bypass cabinet” in its standard cabinet topology. By contrast, theUPS5000-H-1600 kVAis a wider frame and its maintenance/structure description explicitly showsPower cabinet 1, Power cabinet 2, and a bypass cabinet, and the product documentation also includes component sections for items like thesurge protection boxandMDU. Because the 1200 kVA model does not match the “two power cabinets” description, the combined statement (covering both 1200 kVA and 1600 kVA) isfalse, even though the “two power cabinets + one bypass cabinet” part is valid for 1600 kVA.

Huawei data center facility design typically follows a layered fire protection concept: early detection, controlled alarm linkage, and suppression methods that protect equipment and ensure personnel safety. A smoke detection system (often combined with staged alarms) provides early warning so operators can verify events and initiate emergency procedures. For the IT white space, a clean-agent gas extinguishing system is preferred because it suppresses fire without leaving residue and significantly reduces the risk of corrosion or contamination compared with powder-based agents. The extinguishing system is normally integrated with linkage/interlock controls: audible/visual pre-discharge alarms, time delay, emergency abort, door access control logic, and HVAC shutdown or damper control to help maintain agent concentration. This coordinated mechanism reduces false discharge risk while preserving a reliable automatic response if a real fire develops. In contrast, relying only on manual extinguishers is too slow for rapid fire growth, and water sprinklers alone can cause substantial collateral damage to servers and power equipment.

For FusionCol8000-A230, the “two systems” part is correct: Huawei’s quick guide explicitly states that theindoor and outdoor units consist of two independent cooling systems, which is the basis for redundancy and staged capacity control.

However, the rest of the statement (“each system uses three compressors connected in parallel and two EEVs”) is not supported as a fixed, universal configuration in the installation/commissioning guide text that is available here. In Huawei smart cooling designs, compressor quantity and the number of electronic expansion valves (EEVs) aremodel- and configuration-dependentand are tied to how the refrigerant circuit is partitioned (for example, multiple compressor stages for capacity modulation, and one or more EEVs for different evaporator branches). Because the documentation we can directly verify confirmstwo independent systemsbut doesnotconfirm “three compressors per system” as an explicit requirement, the combined statement (two systems + specific compressor/EEV counts) is judgedfalse: one part is verified true, while the detailed component count cannot be confirmed as stated.

Huawei’s scenario-based data center facility portfolio is organized around clearly defined solution families that map to typical deployment scenarios and site sizes. FusionModule500 and FusionModule2000 are smart modular data center solutions designed for standardized, fast deployment in equipment rooms and enterprise edge/branch scenarios.They integrate key subsystems such as power supply and distribution, cooling, monitoring, and optional fire protection into a modular architecture that reduces footprint and accelerates on-site delivery. Likewise, FusionDC1000 is Huawei’s prefabricated modular data center series, delivered as complete, factory-integrated modules that combine civil engineering elements with electromechanical infrastructure for rapid construction, predictable quality, and scalable expansion across different capacity tiers. In contrast, FusionDC800 is not used as a defined scenario-based solution name within Huawei’s mainstream data center facility solution lineup (where “FusionDC” offerings are represented by the FusionDC1000 series and “FusionModule” offerings by numbered FusionModule solutions). Therefore, FusionDC800 is the option that does not match Huawei’s scenario-based solution naming.

Huawei room-level air conditioning products are commonly identified by the series name plus a model suffix that indicates the cooling medium and airflow form factor. Anin-room chilled waterunit uses a chilled-water coil as the primary heat-exchange component and relies on the building’s chilled-water system (chiller/plant) rather than an onboard refrigeration compressor for cooling generation. “Horizontal air supply” describes the discharge direction: the unit supplies conditioned air laterally into the room or into a specific airflow organization (such as cold-aisle delivery), supporting predictable airflow paths and stable return air conditions. Within the provided options,FusionCol5000-A050His the model that matches both identifiers: it belongs to Huawei’s room cooling product line and the model code indicates an in-room configuration withchilled-watercapability andhorizontalair supply orientation. The other options belong to different series or represent configurations typically associated with other deployment forms (such as different placement, airflow direction, or system architecture). Therefore, the correct selection isFusionCol5000-A050H.

In Huawei precision cooling commissioning, the wizard groups functional commissioning items so technicians can validate key subsystems efficiently. Thecooling system commissioningis mandatory because it verifies the primary control and protection loop that directly determines whether the unit can safely provide cooling capacity. This includes confirming the refrigeration or chilled-water cooling path can start and stop correctly, sensors and control logic are valid, and protection conditions (such as abnormal pressures/temperatures, flow conditions, or interlocks) behave as expected. Without completing cooling-system commissioning, the unit’s core purpose—stable temperature control for IT loads—cannot be assured, and the controller cannot reliably judge normal versus fault states during operation.

Other items (indoor fans, condensate pump, humidifier) are important butscenario-dependent: some sites do not use humidification, some drainage designs do not require an internal condensate pump, and fan checks can be handled as part of broader functional tests or may vary by redundancy configuration. Therefore, the wizard allows non-mandatory items to be deselected, but the cooling system commissioning must remain selected to complete a valid baseline commissioning workflow.

Wizard startup commissioning is designed to verify that the unit’skey controllable subsystemscan be started, regulated, and protected correctly. Conditions that prevent a subsystem from operating normally will directly cause commissioning failure. If thecondensate pump is stuck, the drainage function cannot be validated and water may accumulate in the drain pan, which is treated as a functional fault during commissioning. Ifindoor fan 2 drive is faulty, the fan system cannot meet airflow requirements or redundancy expectations, so the fan commissioning item fails. If theelectronic expansion valve (EEV) is not opened, refrigerant flow and cooling control cannot be established, so the cooling system commissioning fails because the unit cannot build a stable refrigeration cycle or reach expected operating parameters.

In contrast, thewater leakage ropeis aprotective detection accessoryused for leak sensing and alarming. While it is important for site safety and recommended for operation, its absence typically does not block the unit from completing the functional commissioning steps for fans, cooling, and drainage; it mainly affects leak detection coverage and related alarms rather than the basic startup commissioning pass/fail.

Huawei UPS5000-H is a modular UPS platform built by paralleling standardized power modules inside the power cabinet to form different system capacities. In this architecture, the “single power module” is the basic building block that contributes a fixed rated apparent power to the total UPS capacity. For the UPS5000-H series, each power module is rated at100 kVA, and the system capacity is achieved by installing multiple 100 kVA modules and configuring redundancy (such as N+1). This modular approach improves availability and O&M efficiency because a failed module can be isolated and replaced without shutting down the entire UPS, while the remaining modules continue carrying the load within their capacity limits. Using 100 kVA as the module rating also simplifies planning: technicians can quickly estimate remaining headroom by counting active modules and comparing total available kVA/kW against the real-time load, ensuring the UPS stays within recommended loading and redundancy margins during maintenance or fault conditions.

In the FusionDC1000A IT scenario, the external input power cables are designed to enter the power distribution system throughdedicated cable inlets at the bottomof the Power PDB. During installation, the procedure requires opening the Power PDB, removing the plugs from thebottom cable holes, and routing the external input power cables into the cabinet through these bottom entries before arranging them along the nearby cable support/bridge inside the Power PDB area. After the cables are terminated (for example, L1/L2/L3/N and PE), the bottom cable entries are resealed using waterproof sealing materials to maintain enclosure protection performance. This bottom-entry method supports reliable mechanical routing for thick/armored power cables, reduces bending stress, helps maintain orderly segregation from signal cabling, and improves on-site safety by guiding high-current cables through a controlled inlet path. Therefore, the correct cabling mode for external power cables in FusionDC1000A IT scenarios isbottom cabling.

In UPS5000-H operation,normal modemeans the load is supplied by theinverter, and the rectifier/charger maintains the DC link and batteries. Themaintenance bypass switch(maintenance bypass breaker) is a mechanical isolation path intended to keep the load powered while the UPS is taken out of service for inspection or repair. Because it changes the power path and can create unsafe or unintended parallel paths if operated incorrectly, it isnot permitted to simply close the maintenance bypass switch while the UPS is in normal mode. The correct O&M logic is to perform acontrolled transferfirst (typically transferring the load tostatic bypasswith proper synchronization and confirmation that bypass power is healthy), and only then close the maintenance bypass switch so the UPS can be safely isolated. This prevents disturbance to the load, avoids synchronization/transfer hazards, and protects personnel from incorrect switching operations. Therefore, the statement is true in the sense of standard UPS5000-H operating procedure and safety interlock intent.

For the Huawei UPS5000-H (380/400/415 V class), “upstream input voltage range” refers to the acceptableAC mains (rectifier) line-to-line input voltage windowthat the UPS can tolerate while maintaining operation. Huawei specifies a wide mains input voltage range of138–485 Vac (line voltage)to improve adaptability to weak or fluctuating power grids and to reduce unnecessary battery usage when the utility voltage sags or rises within allowable limits. Within this overall window, the UPS may applyderating rulesat lower voltages (for example, full-load operation is typically guaranteed only above a higher threshold), but the upstream input can still remain connected and the UPS continues supplying the load according to its control strategy and available capacity. The other options do not match the upstream AC input range:360–600 Vis commonly associated withbattery DC voltage ranges,220–240 Vis single-phase class, and380–415 Vrepresentsrated voltage, not the full acceptable upstream range.

In Huawei delivery scenarios, apreinstalled servermeans the target software (for example, the NetEco platform and its required runtime components) has already been deployed and integrated on the server image before it is handed over for on-site commissioning. Because the installation media has already been applied, the on-site engineer’s work typically shifts from “software installation” to “environment verification and initialization,” such as confirming OS/service status, checking resource allocation, validating database and middleware health, verifying network planning (IP, gateway, DNS/NTP as required), and completing application-level initialization (site creation, user/role configuration, northbound interface settings, and device/model import if needed). In this case,downloading the full installation package is not a mandatory stepfor commissioning, because the package is mainly required when performing a fresh installation or reinstall/upgrade. However, standard practice is still to prepare supporting materials (patches, licenses, and compatibility documents) and ensure the preinstalled version matches the project baseline before acceptance.