Furukawa's Conscius EMS Management System is designed to support the FW-3D radio line for a variety of sizes requiring functionality such as obtaining status and inventory information, alarms, radio and VLAN provisioning, as well as providing different levels of management.
Furukawa's Conscius EMS Management System is designed to support the FW-3D radio line for a variety of sizes requiring functionality such as obtaining status and inventory information, alarms, radio and VLAN provisioning, as well as providing different levels of management.
Furukawa's Conscius EMS Management System aims to serve the FW-3D radio line for a variety of sizes and that require features such as obtaining status and inventory information, alarms, radio and VLAN provisioning, in addition to providing different levels of management.
Functions such as access controls, administration, inventory and fault management are made available by the system, which is responsible for providing security for communication with equipment and managing these items through the SNMP protocol (Simple Network Management Protocol). The main components of the system are:
Management provides support to the FCAPS (Failure, Configuration, Account, Performance and Security) model of the ISO Telecommunications Management Network (TMN). The architecture used in the system is of the Web Server type, with the servers responsible for processing requests made by client interfaces (browsers).
Basically, the operation of the platform provides resources for the insertion (through IP addressing) and monitoring of the managed equipment.
Among the available features, we have:
In addition, as main features, the system brings:
The system allows the use of SNMP v1 and v2c protocol versions to communicate with managed equipment. Information is made available in real time to users using this protocol.
The solution offers a data redundancy solution, with a multi-user platform and Web Server structure with access to the system (client) via browser. The operating system of the servers is Linux (Ubuntu Server) and the database used is PostgreSQL.
FIRST LEVEL:
SECOND LEVEL:
OTHER LEVELS:
The user has at their disposal specific configuration interfaces by type / model / product line. This configuration, by default, is performed using the SNMP protocol.
For cases that have a more advanced management level, interfaces are also offered that allow configuration and provisioning through the management system itself.
The access to the configurations of a managed equipment, as well as the act of modifying them, is controlled according to the type of operation associated with each user, each user having a login and password of access.
A user with an administrator profile can add, remove, and edit the users and profiles (operations) created by him. The administrator is also allowed to provide permissions to other users and block (per user) access to the system.
The system records all actions of each user (log), thus allowing each activity within the management system to be audited (Audit).
Through the fault module, the platform notifies the customer of changes in the operating characteristics of the managed equipment. All alarm notifications generated are listed in the system GUI according to their category and severity.
Events received by the platform are recorded in the system, without any association of related severity (Event Log). An event can generate an alarm in the system.
Each alarm is associated with a severity and a generating source (equipment or a component of that equipment). Filters are also offered for viewing alarms / events.
The system also provides Clear, pickup and Inhibited functions. Functions used respectively to remove an alarm from the alarm list, associate a user with a specific alarm (making it easier to view alarms that are or will be handled) and inhibit an alarm that you do not want to see in the system. An alarm when “configured” as inhibited is temporarily removed from the list of active alarms and is only registered in the system event list.
This alarm is then blocked, without viewing the alarm list, until the user manually removes it from the inhibited state.
The graphical representation of alarms follows a standard color code, considering different levels: Critical, Severe, Major, Minor, Warning, Unreachable and Clear. Unreacheable status is the indication of loss of management communication with the equipment. And the severity of CLEAR indicates the deactivation of an alarm.
Each piece of equipment is managed individually by the system. In the case of radios, the system considers the IDU and the ODUs as a single piece of equipment, the “radio”.
The equipment network is represented by a list of contextualized items. For each item in this list, identification information and possible actions to be performed are presented. Among these actions, we have access to:
Filters are also offered that allow localization, data ordering, up / down status information and mastes / slave radios in the same topology, in addition to custom views that can be used for management.
Each equipment registered in the management system has a set of logical and physical inventory information, the physical inventory being dependent on a user manual registration.
As an example of logical inventory we have:
The logical inventory of the managed equipment can also be viewed through the equipment's bayfaces or status related to the interfaces made available by the equipment.
The maintenance tasks provided by the system are divided into two groups: one group directed to the management system itself and the other directed to the managed equipment. The functionalities related to the system are:
For the equipment group, the following are available:
The operation of the management system is completely independent of the operation, that is, an eventual fall in the system will not have any impact on the standard operation and performance of the managed equipment.
All information and configurations of the system and equipment are stored in the database. An interface is also available to perform the backup on the system itself. To restore system data, a tool is provided, outside the system, without the need for direct access to the database.
Compare features, sizes, models to find the perfect option for you
