Corrupt File Brought Down FAA's Antiquated IT System

The system itself is called NADIN (National Aerospace Data Interchange Network). It was designed by North American Philips for the FAA in the early 1980s. The two Philips DS714/81 mainframes became operational in January 1988. The company went out of business later that year, and the FAA bought out the entire parts inventory.

To its credit, the system has been running 24/7 for a long, long time—since the tail end of the Reagan administration, in fact. But the time has come for it to be replaced, as underscored by the shutdown this week.

Resource Library:

By the end of 2008, Takemoto said, the entire system will be replaced by a new, state-of-the-art system: new hardware, software, everything. "It'll have a memory that will be exponentially larger than this one," Takemoto said. "It'll be able to handle spikes like the one we had yesterday."

Kenny Van Zant, chief product strategist at SolarWinds, a network management software maker, told me that most network outages are not caused by corrupted files.

"If you look at the root causes of most network outages, north of 70 percent of them are caused by configuration errors by humans," Van Zant told me. "Computers fail a whole lot less often than the humans punching things into computers fail. Network engineers, as smart as they are, are not immune from that."

Details about the FAA's proprietary network configuration software setup were not made available.

Detection and Monitoring on the Way

SolarWinds has a new configuration called Orion NCM (Network Configuration Manager) v5, which integrates new features into the previous Cirrus Configuration Manager product. Orion alerts network managers—via a Web-based user interface for handheld devices, cell phones and laptops—when any change in the network structure occurs, so that outages can be handled quickly.

Jim Battenberg, director of product marketing for Neverfail, a disaster recovery software vendor, told me that his software asynchronously replicates all the data between the two environments and monitors the network 24/7.

"So we would detect if the network goes down, if the server goes down, if there's problems with the hardware, if the processor is being hit too hard, or what have you," Battenberg said. "We detect everything within the ecosystem. And if there's a problem, we can a) fix some things ourselves, or b) fail over to the secondary system. And we do that automatically."