This is not a Wikipedia article: It is an individual user's work-in-progress page, and may be incomplete and/or unreliable. For guidance on developing this draft, see Wikipedia:So you made a userspace draft. Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
This article's use of external links may not follow Wikipedia's policies or guidelines. (June 2016) |
Developer(s) | OS Group |
---|---|
Stable release | 3.0.0
|
Type | Network management system |
License | Commercial |
Website | www |
‘’’Equipment Manager (EqM)’’’ Orange System Equipment Manager (EqM) – OSS/BSS platform to manage and operate Telecom and Enterprise networks, which provide opportunities for operations to increase SLA’s and KPI’s in networks (NGN, IP-based, TDM, etc.). Equipment Manager provides features of OSS/BSS within TMN TM Forum Frameworx:
- Compatibilities;
- Monitoring;
- Performance Management;
- Task Management;
- Inventory Management;
- Network Resource Management.
Orange System Equipment Manager (EqM) is a network equipment inventory system with management and monitoring functions consisting of the following basic components.
Modules
editThe following Equipment Manager modules support the main system-specific functions of OSS/BSS class systems:
Automated workstations (AWS)
editThe following types of AWS are available to work with the system modules:
- AWS "EqM";
- AWS "Device Configuration";
- AWS "Admin Workplace".
Automated workstation (AWS) "Device Configuration" enables users to configure the functionality of the system modules. Automated workstation (AWS) "Admin Workplace" enables the system administration.
Access permissions
editA flexible configuration of permissions to work with the system is supported by the access permission subsystem. Restrictions may be set for a single object or specific operations.
System Architecture
editEquipment Manager is a system based on client-server technology that includes the following main components:
- EqM server(s);
- User workstations.
The following options for server architecture are available depending on the scale of the served network and the set of modules used:
- Standard — all system components are installed on one hardware server. One database and one server ("Primary server") are used.
- Multi SRV — the system core ("Inventory", "Monitoring", "Monitoring archive" database) is installed on one server ("Primary server"); the preprocessing module and polling module are hosted on one or more separate servers ("Server for collecting and preprocessing monitoring information messages"). One database, one server for the system core, and one (or more) "Server(s) for collecting and preprocessing monitoring information messages" are used.
- Multi DB — databases are distributed across separate servers:
- "Inventory" — "Primary server" database.
- "Monitoring" — "Server for processing monitoring information messages" database.
- "Monitoring archive" — "Archive server for monitoring event log" database.
The monitoring module and polling module are installed on one or more separate servers ("Server for collecting and preprocessing monitoring information messages"). In this case three databases, three servers (individual for each database), and one (or more) "Server for collection and preprocessing of monitoring information messages" are used.
System Requirements
editThe following minimum system requirements must be met for Equipment Manager to function according to the selected architecture:
- Standard
Primary server: 2 x CPU (quad-core) with frequency 2.2 GHz; 64 GB RAM; 300 GB drive array; 2 x NIC with bandwidth 10/100 MB/s; UPS.
- Multi SRV
Primary server, server for collecting and preprocessing monitoring information messages: 2 x CPU (quad-core) with frequency 2.2 GHz; 64 GB RAM; 300 GB drive array; 2 x NIC with bandwidth 10/100 MB/s; UPS.
- Multi DB
Primary server, server for processing monitoring information messages: 2 x CPU (quad-core) with frequency 2.2 GHz; 64 GB RAM; 300 GB drive array; 2 x NIC with bandwidth 10/100 MB/s; UPS. Archive server for monitoring event log: 2 x CPU (quad-core) with frequency 2.2 GHz; 16 GB RAM; 300 GB drive array; 2 x NIC with bandwidth 10/100 MB/s; UPS. Server for collecting and preprocessing monitoring information messages: 2 x CPU (quad-core) with frequency 2.7 GHz; 8 GB RAM; 200 GB drive array; 2 x NIC with bandwidth 10/100 MB/s; UPS. An automated workstation must meet the following minimum system requirements for any type of system architecture: CPU with frequency 1.5 GHz; 256 MB RAM (recommended 512 MB); 100 MB HDD (available space); NIC with bandwidth 10 MB/s.
Developer & Owner
editOS Group (TMForum member) specialized in the software development and flexible integration of its own OSS/BSS solutions. Equipment Manager operates and monitors over the 30% of broadband internet customers in Russia. Last 10 years OS Group are leading in developing and integrating OSS/BSS products for the best players of Russian Telecommunication Market (more than 50 successful projects).
Links
editExternal links
edit