The EdgeView contains the EdgeView Service Control Center (SCC). The EdgeView SCC can launch an SBC Edge instance's UI in your internet browser, which allows you to configure, operate, and monitor the instance if the remote UI connection is currently active. For example, you can configure the EdgeView Agent (EVAgent) logging and view the current connection and remote UI status of the EdgeView connection. To enable this feature for the SBC Edge, you require the EdgeView 16.0.1 Release or later. With the EdgeView SCC enabled, the SBC Edge sends a SIP signaling group (SG) and port status report and the most recent, highest severity alarm to the EdgeView. The SIP SG and port status report includes information about the SIP SG and port's unique ID, administrative status, and real-time status. If a timeout results in the runtime status not being retrieved, then the SBC Edge reports the real-time status as Unknown. To enable the EdgeView SCC, you must configure the EdgeView panel (see the following procedure) according to your SBC Edge: SBC SWe Lite - Configure the EdgeView IP address or FQDN and the EdgeView Management ID. When you enter the EdgeView Management ID, you must insert a colon every two characters (00:00:00). Otherwise, the SBC SWe Lite cannot connect to the EdgeView.Requirements
For intermittent connectivity failure from the SWe Lite during initial setup
Configure the SBC Edge for EdgeView during Initial Setup
To configure the SBC Edge for EdgeView SCC during your initial setup, refer to one of the following procedures:
- SBC 1000/2000 - Running Initial Setup
- SBC SWe Lite - Running Initial Setup on SBC SWe Lite
When you configure the Initial Ribbon Setup screen, use the following table to configure the EdgeView panel.
When you enter the EdgeView Management ID, you must insert a colon every two characters (00:00:00). Otherwise, the SBC SWe Lite cannot connect to the EdgeView.
Troubleshooting Tips - Intermittent Connectivity from SWe Lite to EdgeView
- Wait at lease 2 -3 minutes minutes before determining connection is down; it may not be instantaneous.
- Examine the EV Agent (EVAgent) logs and the response to the registration request the SBC transmits to EdgeView. Ribbon testing experienced that when the SBC does not connect to Edgeview, there is usually an error response from Edgeview, and the problem is on the EdgeView side.
- For a failed response from the EdgeView the retry to connect to EdgeView is not instantaneous. There is an increasing delay with each retry, and eventually only trying with a very long time out. This increase in delay is by design; when an EdgeView goes down or has connectivity problems, all the devices trying to connect to it will not flood it at the same time with too many requests.
Options to Reconnect
Two options to recover/re-establish connection:
- Reboot SWe Lite (not required)
- Toggle EdgeView connection (execute the steps listed in Configure the SBC Edge for EdgeView during Initial Setup