Learn something new every day
More Info... by email
Fault management is a term commonly used in telecommunications that refers to the process of detecting, identifying, and ultimately resolving any issues that are decreasing the efficiency of communications within a network. The idea is to correct the malfunctions as quickly as possible and restore the network to full functionality. This same basic concept can be applied to the management of an internal business network as well as a communications system that processes voice and data across a nation or group of nations.
There are a number of processes that aid in conducting effective fault management. Tools such as diagnostic software programs and sequence testing processes are two examples of proactive measures taken to isolate and correct malfunctions before users of the network are adversely affected. With a teleconference service, diagnostics on conference bridges can often identify a channel or port connected to the bridge that is compromised in some manner. This makes it possible to disable that port so the system does not select it as a point of termination for an inbound call. The port remains disabled and unavailable for use until the malfunction is corrected, preventing any customers of the conference call bureau from being inconvenienced.
Along with identifying and correcting telecommunications malfunctions, the process of fault management can also be effective in managing networks that are in operation as part of a company’s internal network. Here, the purpose of the fault management is to correct any issues that threaten to disrupt the ongoing tasks that allow the business to function. This includes managing and correcting faults associated with servers, workstations, or any other component that is a part of that network. Backups and regular diagnostics aid in resolving issues before they have the chance to interfere with the business operation, while tools such as log files make it possible to review events that do take place and temporarily disrupt the system. Error logs are especially helpful in isolating the origins of various types of exceptions or faults, and correcting them as quickly as possible.
Many fault management programs provide what are known as error detection notifications. This is simply a message delivered to an administrator that something is not working properly. Some management programs also include tools that make it possible to correct the fault immediately, after permission is granted by an administrator, a feature that also helps to limit the amount of downtime experienced due to some sort of malfunction.
@Mammmood - We live and die by our mobile communications devices. From my standpoint, mobile communications should be at the top tier of priorities for network fault management.
They are subject to a lot more potential hacks in my opinion, like unauthorized people jumping onto a WiFi signal and potentially bringing down a network connection.
Also, it seems that everyone is going wireless. This means that there are more things that can go wrong too.
I think that network fault management should be at the very top of the list of priorities for any phone company offering DSL or other broadband services. Of course, I realize that for the phone company, fault management would be important for other reasons too, like making sure people can make phone calls.
However, speaking as a consumer, it’s losing my Internet connection that really spooks me. I can always make calls on my cell phone. But I have DSL and when a recent rainstorm caused an outage that brought down my Internet connection for seven hours, I was not a happy camper.
I had to call the company on the cell and they gave me an approximate time for repair. In my opinion these things should not happen to begin with, much less for a rainstorm. A hurricane I can understand; but a strong rainstorm should not bring down any network connection.
One of our editors will review your suggestion and make changes if warranted. Note that depending on the number of suggestions we receive, this can take anywhere from a few hours to a few days. Thank you for helping to improve wiseGEEK!