Network Availability Management
Availability Management gives a measure of the managed element’s reacheability statistics creating an overview of how well each element responds to queries and for which periods of time. Consequently Availability management provides a eye on service continuity across the network as a whole or across a certain managed zone as well as on the specific element itself.
This is the traditional view of Availability management and it is largely dependent on the statistics gathered through ICMP based data and in some rare cases; SNMP polling based as well. This short sighted vision of Availability management implementation that we are seeing today has been the main reason why Availability Management never really took its rightful place as a viable and critical field of study that enables network administrators to understand, anticipate, then counter-act any changes, errors, or incidents compromising the network devices and the network environment.
The prime focus of Availability management the way we see this through our IMMS model is however different. The prime focus SHOULD be more geared towards assessing and then handling the routine risks to availability that can be reasonably expected to occur on a day-to-day basis. Assessing and Handling comes only from experience with the network environment. Due to the dynamic nature of today’s network environments; this is only known and evaluated by the administrators managing or running their own network’s day-to-day operations and not by the NMS software solutions providers or vendors!
Risks to availability could be evaluated and/or anticipated by listening to the network environment’s events, faults, and alarms and correlating them together and to any other detected -- anticipated or unanticipated – Changes as well as to any particular calculated Trends that could be detected on the the network?
The measure of each of the managed element’s reacheability statistics is provided through a special imbedded SOSL variable called sysAvailability.