Various master data have to be recorded in ERAMON. Due to the integrated way the data are being held, it is essential that you first of all assign a location before assigning a circuit in the carrier management.
A user always has to be assigned to a permission group. It is not possible to leave a user as stand-alone.
The transfer of permissions to the user occurs through the permission group. If values within the permission group are changed, these changes will affect the user(s) for that particular permission group.
You can have an individual map from the topology view shown for each user on login.
A user can be sorted into a queue. Queues are there to split device errors into groups, for example, all errors of LAN devices are sorted into the LAN queue; all those of WAN devices into the WAN queue group. So, if a company has two different departments dealing with the network’s LAN and/or WAN, then – depending on the permissions – while each can access both queues, they would normally only see the errors of the devices for which they are responsible.
Geographical permissions are also possible. You can ensure through appropriate assignments to location groups, which can be managed either automatically or manually, that users only see the devices of a particular region. Central user groups, such as in the NOC, however, have access to all regions.
Some sections/pages in ERAMON allow the users to set up custom fields themselves. The field can be freely defined, for example: a list of five options where the third option is the standard. Once the fields are set up and in compliance with the assignment, this field will then be made available in the following sections:
Various options are available for the setup of devices:
- Device Importer: import via CSV files
- Auto-Scan: automatic scan of one or more IP networks
- Manual device import: GUI for setting up a device
- Interface: variable formats are available (XML, database, etc.)
Groups can be saved for many sections/functions to carry out specific operations effectively and in a standardized manner.
- Setting up a device group called: “All Cisco Devices”
- Specifying a ruleset for automatically entering, for example: device manufacturer or device name
- To run particular measurements, such as QoS loads, in the EPM module will only occur for this device group
It is often useful if not all ports in a network were monitored or statistics gathered. Rulesets can help to influence which ports are relevant, for example:
It is also possible to set certain parameters automatically based on various filters, such as device manufacturer or device name.
An example for a targeted activation of the config backup:
- Activate the config back up for all “Cisco” devices.
- Also activate the firmware backup for all LAN-“Cisco” devices.
- Deactivate the firmware backup for all WAN-“Cisco” devices.
Both rulesets are run automatically for new devices, the system therefore manages itself.
By default users are authenticated on the GUI via a local password. Depending on the application, this can be edited via the following protocols:
The client ability allows you to record a separate authentication for each client.
Within the master data menu you are presented with a wide range of possible settings for device parameters, for example: an adjustable timeout for SNMP pollings or alternative Sys-OIDs, and more. For other sections/operations you are given a range of options via the configuration parameters, to customize ERAMON specifically for the user area. You could, for example, customize the display of the graphs. This is just a selection of possible settings for the ERAMON application modules:
- Carrier Management
Technical parameters: These enable you to manage the technical parameters for the order of circuits, such as: interface, terminating unit, transfer unit.
Default setting of ports, default values of ports during the scanning process (managed, EPM), can be specified: all managed, all unmanaged, all ports with Oper status up, or all ports with admin status up.
Saving a logo in png-format as a background image in graphs.
Acknowledgement obligation: when acknowledging an event through the central event console, the user has to enter a text, such as a ticket number.
TACACS: When creating a job, the user has to enter a TACACS password. Alternatively, the system will use a super-user already existant in the background.