3 Management Functional Areas
Last update PvD

3.7 GM
General Management

System Management or Self Management

Not obvious at all from the M.3400 is the fact that all management areas should not only manage Network Elements, but also the TMN itself, i.e. the TMN should take care of itself including the management network (DCN).

This is sometimes called System Management (in this document we call it General Management) and includes all five management areas:

Report faults in the TMN, test it.
TMN installation support, Provisioning of the TMN (keep track of TMN configuration (hw & sw), TMN component status & control (control TMN processes, set parameters, etc.).
Only applicable when customers or other operators have to pay for TMN services (e.g. Customer Network Management).
Measure and check TMN performance (e.g. line-, CPU-, memory- & disk utilisation);  performance control to counteract overload (e.g. after event avalanches caused by major network faults).
In particular Security Management should probably manage more the TMN than the NEs.

Obviously, the DCN will be implemented in an (X.25 or IP) data network, and the OSFs on will be implemented on servers.  These servers will need extensive IT management facilities, like doing an orderly start or shut-down of applications, do backup & restore, etc.

The platform for TMN applications is the subject of SPIRIT (Service Providers' Integrated Requirements for Information Technology, a group within the NMForum;  see section Standards.Organisations).

Next section: MFA versus LLA
Up to Contents
Up to Index