| Add_docset_workflow |
|---|
| AUTH1 | vnarayan |
|---|
| DEV1 | pckumar |
|---|
| LDEV1 | rmorse |
|---|
| SVT1 | jgarach |
|---|
| LSVT1 | radaikalam |
|---|
|
| Panel |
|---|
| borderColor | green |
|---|
| bgColor | transparent |
|---|
| borderWidth | 2 |
|---|
|
Additional sections: |
...
...
...
...
The Embedded Management Application (EMA)
...
is a web-based management system for
...
Session Border Controllers (s ...
). EMA offers efficient operation, administration, management and provisioning (OAMP)
...
of
s through its browser-based user interface. EMA supports all operations that are available from the ...
Command Line Interface (CLI) and, in addition, provides specialized functionality that
...
facilitates common device management operations.
...
...
If the web browser crashes, hangs or is manually closed while logged into the EMA GUI, the EMA session will still remain open. Manual intervention by the administrator is required to terminate the session from the EMA GUI. To terminate the hanging session, refer to Users and Application Management - User and Session Management page.
EMA provides the following types of functionality:
- Fault management
- Configuration management
- Security management
- Certificate management
- Support to upgrade/downgrade software
- Service provisioning workflows
- Alarm monitoring
The Embedded Management Application (EMA) User Guide provides operational instructions covering all aspects of the EMA interface.
EMA User Guide
| Warning |
|---|
This User Guide does not reflect the latest GUI images. The images will be replaced gradually. |
Audience
This guide is intended for operators and system administrators responsible for provisioning, maintaining, and administering the
. It is assumed that the end user of this document will have basic understanding and working knowledge of the following technical aspects:- VoIP
- SIP protocol
- H323 protocol
- IP-to-IP networking
- Linux operating system
- Packet networking.
This guide also requires specific knowledge of the
and its configuration.Characteristics of EMA
The following are the EMA key characteristics:
- EMA supports the following functionality:
- Fault management
- Configuration management
- Security management
- A web-based interface for better usability
- Certificate management
- Support to upgrade/downgrade software
- Service Provisioning workflows
- Monitoring alarms
...
| Warning |
|---|
The GUI images included in this User Guide are intended as examples and do not always reflect the latest interface design. The images will be replaced gradually. |
Supported Browsers and Client Computer Requirements
| Info |
|---|
|
If the web browser crashes, hangs or is manually closed while logged into the EMA GUI, the EMA session will still remain open. Manual intervention by the administrator is required to terminate the session from the EMA GUI. To terminate the hanging session, refer to Users and Application Management - User and Session Management page. |
The minimum recommended requirements for each user's computer are outlined below. Configurations that do not meet these recommendations may experience excessively poor performance. Also note that slow network connections can also result in poor performance.
Client Computers
The minimum recommended memory/processor requirements of a client computer/workstation when accessing EMA is following:
...
- dual core processor
- 2 GB RAM
The platform/browser combinations supported are listed in the table below.
The minimum browser resolution that is supported is 1024 x 768 pixels.
| Caption |
|---|
| 0 | Table |
|---|
| 1 | Supported Platforms and Browsers |
|---|
|
Browser | Version | Platform and OS |
|---|
Internet Explorer | 9, 10, and 11 | - Microsoft Windows (XP, Vista, 7, 10)
| Firefox | 31 and later | - Microsoft Windows (XP, Vista, 7, 10)
- Intel-based Mac (10.5 and later)
| | Chrome | 32 and later | - Microsoft Windows (XP, Vista, 7, 10)
|
|
| Div |
|---|
|
| Excerpt |
|---|
EMA Cross-context QueriesThe EMA provides the ability to view status and statistics across contexts. For example, it is possible to view trunk group status across all zones and address contexts. For large configurations, however, performance may be impacted when viewing status and statistics across contexts. This is especially true for configurations with more than 20 zones. To address this problem, |
|
...
| provides a script to disable cross-context queries. If you experience performance issues when viewing status and statistics, run this script to alleviate this issue. |
|
...
| Running this script disables all cross-context functionality forcing you to specify the object context before viewing status, statistics or configuration information for an object. For example, after running this script you will need to first select a specific address context and zone in order to view trunk group status or a list of trunk groups. |
Disabling Cross-Context QueriesTo disable cross-context queries, perform the following steps: - Open the BMC for the SBC.
- In the BMC, select the Remote Control tab, then click the Console Redirection button.
- Launch the redirection console.
- In the redirection console, login using an Administrator username and password for the SBC.
Enter the following command and press Enter
|
|
...
: | Code Block |
|---|
| /opt/sonus/ema/updateCrossContextDisabledValue.sh true |
Log out of the redirection console and close it Log out of the BMC.
|
|
...
| If the is part of an HA pair, perform these steps on both the primary and secondary . |
Re-enabling Cross-Context QueriesTo re-enable cross context queries, follow the steps above substituting the following command with the one in step 5: | Code Block |
|---|
| /opt/sonus/ema/updateCrossContextDisabledValue.sh false |
|
|