Working with DERMS FEP Management
DERMS FEP Management displays the Front End Processors (FEPs) configured for Edge DERMS and provides actions to configure and control their connections. An FEP is a Live Energy Connect (LEC) instance that communicates with one or more aggregators. Multiple connections can be configured for an FEP to provide alternate communication endpoints.
Open DERMS FEP Management from the Tool Selector. You need the Access DERMS FEP Management permission. Before adding an FEP, arrange for the corresponding LEC instance and obtain its LEC FEP ID, connection addresses, ports, and any required certificate information from your administrator.
Understanding the FEP List
The list displays the following information:
Additional columns available through Organize Columns include Id, Secure, Description, Debug, and Connection Description. Id is the internal FEP identifier; LEC FEP ID identifies the external LEC FEP.
Control and Status describe different aspects of an FEP or connection. Enabled makes it available for use; check Status to determine whether it is Connected. A saved configuration or an Enabled control value alone does not confirm communication with LEC.
Adding or Editing an FEP
1. Select Actions, and then select Add FEP. To edit an existing FEP, select its row and select Actions, and then select Edit FEP.
2. Enter or update the following fields.
3. Select OK to save, or Cancel to discard the dialog changes.
A new FEP is created disabled. Configure and enable at least one connection before enabling the FEP. Creating an entry here does not create the external LEC instance.
Viewing FEP Details
Select an FEP and select Actions, and then select View FEP Details. DERMS FEP Details shows read-only FEP settings, a Connections table, and an Aggregators table. Use Edit FEP in DERMS FEP Management to change the FEP settings.
The Connections table shows Control, Status, Name, Description, Order, TCP/IP Address, and Port. Connection Id is also available as an optional column. The Aggregators table lists the FEP's assigned aggregators and information such as their descriptions, device availability, reductions, and latest update time.
Adding or Editing a Connection
1. In DERMS FEP Details, select Actions, and then select Add Connection. To edit a connection, select it in the Connections table and select Actions, and then select Edit Connection.
2. Enter or update the following fields.
3. Select OK to save, or Cancel to discard the dialog changes.
The same address and port combination cannot be configured twice on one FEP. A new connection is created disabled. Select its row and select Actions, and then select Enable Connection to make it available. When changing only the Order of the sole enabled connection on an enabled FEP, disable the FEP first.
Controlling FEPs and Connections
Use the following Actions menu options in DERMS FEP Management:
• Enable FEP: Enables the selected FEP. At least one of its connections must already be enabled. Monitor Status to confirm that communication connects.
• Disable FEP: Disables the selected FEP and closes its communication. Its connections are shown as Disconnected.
• Swap Connection: Requests the next enabled connection in increasing Order, wrapping to the lowest enabled Order after the last. This action is available when the FEP is enabled and has more than one enabled connection.
• Delete FEP: Deletes the selected FEP after confirmation. Move its assigned aggregators to another FEP first; an FEP with assigned aggregators cannot be deleted.
In the Connections table in DERMS FEP Details, select a connection and use:
• Enable Connection: Makes the selected connection available for use.
• Disable Connection: Makes the selected connection unavailable. Disabling the active connection causes communication to transition to an alternate enabled connection when one is available.
• Delete Connection: Deletes the selected connection after confirmation.
You cannot disable or delete the last enabled connection while its FEP is enabled. Disable the FEP first if you need to remove its final enabled connection. Swap Connection is also available in DERMS FEP Details and acts on the FEP rather than selecting an arbitrary connection row.
Moving an Aggregator
1. In DERMS FEP Details, select an aggregator in the Aggregators table.
2. Select Actions, and then select Move Aggregator.
3. Select the Target FEP and select OK. Select Cancel to leave the assignment unchanged.
The target list excludes the current FEP. Another FEP must exist before you can move the aggregator. Verify the target FEP's configuration and communication status before relying on the new assignment.
Testing SSL Configuration
In DERMS FEP Details, select Test SSL Configuration to inspect server-side security configuration. The dialog shows a Valid or Invalid result for Keystore Location, Keystore Type, Keystore, Truststore Location, Truststore Type, Truststore, Private Key, Public Key, and CA Certificate Chain.
The certificate-chain check uses the selected FEP's CA certificate alias. Ask your administrator to investigate Invalid results. These checks inspect the configured server stores and keys; they do not perform an end-to-end connection test to the remote LEC endpoint. Select Close to exit the dialog.
Monitoring Communication
FEP and connection displays update as server changes are received. Use the Control and Status columns together when monitoring communication. When working in a standalone tool window, select Actions, and then select Refresh to reload its information.
The global FEP_DISCONNECT_PERIOD parameter determines how many seconds Edge DERMS waits for reconnection following a disconnection. The default is 10 seconds. Configure it on the Parameters tab of DERMS Configuration. Individual FEP Keep Alive and Retry Interval values use milliseconds.
Connection failure can trigger failover to another enabled connection. Check the connection status after manual control changes or a failure, and use the DERMS Alerts and DERMS Alerts History tools to investigate communication problems and recorded control changes. Alert visibility depends on the configured alert rules.