NEM Configurator
For more details see section NEM Configurator.
Network configuration
The following steps have to be performed to create a database representing the network to be managed.
Management network
After the physical management network has been set up, the necessary Agents for the control of the management communication should be created.
Managed objects
The Network Elements (NEs) to be supervised have to be assigned to each agent.
SNMP compatible third party equipment can be assigned to a specific SNMP agent.
Third party equipment can also be added by creating Foreign Objects (FOs). ALCAR alarm monitoring units can be used to supervise external alarms of FOs.
Security configuration
The FOXMAN‑UN security system has to be configured to allow structured access to the various system functions. With the system release R17A, role-based access control (RBAC) has been introduced, replacing domain access control (DAC). For details, see section NEM Configurator.
Role-Based Access Control (RBAC)
Security in FOXMAN‑UN is organized around domains, users, and roles. Role-based access control is described in NEM Configurator - Main Window.
Domains
Domains (see Domain – Create) contain managed objects of the FOXMAN‑UN structure, such as network elements, agents, domains, users, services.
Users
Users can be created, managed, or deleted by a user with appropriate administrator permissions. The are assigned to one or several domains. This allows them to perform the actions defined by their roles on the objects contained in the domains. Assignments can be on a permanent basis, or they can be made to terminate at a specific date and time.
Roles
Roles are assigned to a user by an administrator having the role RBACMNT.
Supervision aspects
The NEM Configurator allows stopping and starting supervision of single NEs. Forced polling can be executed on any NE. Access to the alarm situation of single NEs is possible via alarm list, local craft terminal (FOXCST), or hardware view (legacy).