Maintenance Management is a frame work type service employed by many industries today such as the automotive, oil refineries, and factories. It is hence interpreted differently by different industries and according to the particular industry’s individual requirements.
The Maintenance Management System delivers a service where its fundamental model is the primary means for understanding the major functions of network Maintenance Management Systems. This model consists of two major schools and four conceptual areas: Preventive Maintenance and Corrective Maintenance schools.
The Models then consists of the following five conceptual areas of Information Management:
The goal of Traffic-Flow maintenance management is focused on maintaining the Flow of management information traffic on the Network; with an emphasis on avoiding Management information traffic storms across LAN and WAN links between NMS requests and the Network Element’s responses to those requests.
Flow Maintenance involves three main steps.
Management Requests should be mainly an SQL SELECT type of operation; where the targeted element’s relevant information is targeted without having to continuously use GetNext or GetBulk operations which require a dedicated and high cost search criteria, one that is present in INDEX components.
Historically; NMS generated management queries have been launched uncontrollably (using BULK operations for example) to all elements detected in the network, prompting each and every element to reply back to every request. This has been known to overwhelm NMS Servers as well as managed network element’s resources significantly enough to cause link congestions. This indeed has been known to cause the loss of the very management information itself that the NMS is originally trying to collect.
Allowing Network Administrators to logically Bundle sets of large and extensive network management data requests into a number of autonomously controlled management processes, may it targets information directly related to the physical elements themselves, or a certain service implemented on those elements, or a subset of elements, or indeed a subset of one or more of the services running on those elements; is essential to allow for a full scalability of management traffic-flow.
The goal of the Authority maintenance management is the maintenance of authoritative rights and ownerships over managed information.
Authority over managed information is exercised by means of an application User(s) with the appropriate rights to initiate pre-determined, planned, and structured set of management information requests to be sent to a pre-determined, planned, and structured set of the network element(s) to be managed.
Another implicit and equally important goal for exercising this Authority over the managed information is the grouping of managed network elements into logical entities to allow the NMS to forward its intended data request sets to each managed group independently from other groups, where the particular set of requests could be considered unnecessary overhead.
Allowing network administrators to logically break large networks into a number of autonomously managed bodies, may it represents the physical elements themselves, or a certain service implemented on those elements, or even a subset of the total elements, or indeed a subset of one or more of the services running on those elements; is essential to allow for a full scalability of management solutions implementations.
Page 1/3 Next Page
[About
ANMS], [About SmartMIB], [About
IMMS], [About SOSL], [FAQ]
[Home], [About], [Solutions Center], [NMS Market],
[Products & Services],
[Management Technology], [Technical Support],
[Contact us], [Site
Map]