Data Center Gas Fire Suppression System Comparison

So, you have to choose a gas fire suppression system to protect against fire destroying valuable assets such as Computer Equipment, Document Vaults or Telecommunications / Switch Gear. You have a choice between Chemical Fire Suppression Systems such as Novec 1230 or FM200 and Inert Fire Suppression Systems such as Inergen.

FM200 Fire Suppression

Firstly, FM200 is a HFC Gas that is now monitored under the Kyoto Protocol. Why? Well, it has a high Global Warming Potential and therefore has to be treated and monitored accordingly.

Any engineer working on an FM200 fire suppression system, even for maintenance purposes, has to be trained and certified in F-Gases.

The disposal of FM200 can only be carried out by licensed companies. All this additional licensing puts additional responsibilities and expense on the end user, who are often not aware of their responsibilities around this gas.

So why is FM200 still chosen as a fire suppression agent? FM200 is more cost effective when its maintenance and disposal costs are left out of the equation. However, if the cost of the system is considered over its lifetime and subsequent disposal, then the obvious decision is to consider a different agent.

Novec 1230 Fire Suppression

Novec 1230 fire suppression agent is a relatively recent addition to the fire suppression industry. Manufactured by 3M, Novec 1230 comes with a 20 year “Blue Sky Warranty”, guaranteeing its “Green” credentials.

Choosing Novec 1230 over FM200 is the smarter choice and from here in this article, we shall consider only Novec 1230 and Inergen for that reason.

Inergen Fire Suppression

Inergen fire suppression agent is a mixture of three naturally occurring gases: nitrogen, argon and carbon dioxide. As Inergen agent is derived from gases present in the earth’s atmosphere, it exhibits no ozone depleting potential, does not contribute to global warming, nor does it contribute unique chemical species with extended atmospheric lifetimes. Because Inergen agent is composed of atmospheric gases, it does not pose the problems of toxicity associated with some of the chemically derived agents.

HP MSA 2040 SAN Storage – Connecting to the Network


You can set network port IP addresses manually using the command-line interface port and cable. If you have not done so already, you need to enable your system for using the command-line interface port.

Network ports on controller module A and controller module B are configured with the following factory-default IP settings:

  • Management Port IP Address: (controller A), (controller B)
  • IP Subnet Mask:
  • Gateway IP Address:

Continue reading “HP MSA 2040 SAN Storage – Connecting to the Network” »

  1. From your network administrator, obtain an IP address, subnet mask, and gateway address for controller A, and another for controller B.
  2. Use the provided USB cable to connect controller A to a USB port on a host computer.
  3. Windows customers should locate the downloaded device driver described in Downloading a device driver for Windows computers.
  4. Start and configure a terminal emulator, such as Hyper Terminal or VT-100, using the display settings / connection settings in Table.
Terminal emulation mode VT-100 or ANSI (for color support)
Font Terminal
Translations None
Columns 80
Baud Rate 115,200
Data Bits 8
Parity None
Stop Bits 1
Flow Control None
Parameter Value
  • In the terminal emulator, connect to controller A. Press Enter to display the CLI prompt (#).

    At the login prompt, enter the default user manage.

    Enter the default password !manage.

  • At the prompt, type the following command to set the values you obtained in step 1 for each network port, first for controller A and then for controller B:

    set network-parameters ip address netmask netmask gateway gateway controller a|b

    For example:

    # set network-parameters ip netmask gateway controller a

    # set network-parameters ip netmask gateway controller b

  • Type the following command to verify the new IP addresses:

    show network-parameters

  • Use the ping command to verify network connectivity.

    For example:

    # ping (gateway)

    In the host computer’s command window, type the following command to verify connectivity, first for controller A and then for controller B:

    ping controller-IP-address

  • If you cannot access your system for at least three minutes after changing the IP address, your network might require you to restart the Management Controller(s) using the CLI. When you restart a Management Controller, communication with it is temporarily lost until it successfully restarts.

    Type the following command to restart the management controller on both controllers:

    restart mc both

  • When you are done using the CLI, exit the emulator.

 [source: HP Documentation]