In this section:
The primary interfaces used to access the
EMA
The EMA provides a comprehensive method to provision, maintain and administer the
For login details, refer to Logging Into EMA.
EMA in Platform Mode
The EMA in Platform Mode provides current status of the platform, application software version information and system information. The EMA in Platform Mode is also used to start, stop and restart the application as well as reboot the host. The EMA in Platform Mode supports upgrading the operating system and application. Additional features include a web interface for generic troubleshooting activities, security and remote access management.
For more information, refer to Logging into EMA in Platform Mode.
Command Line Interface
Command Line Interface (CLI) is the traditional method to configure systems from any machine with network access using a secure shell (SSH) client terminal emulator).
For login details, refer to Logging Into CLI.
Baseboard Management Controller
Not applicable to the SBC Software Edition (SWe).
The Baseboard Management Controller (BMC) supports the following functions:
- View basic system information
- Change mouse mode
- Configure BMC and EMA in Platform Mode network settings
- Add, edit or remove users
- Configure NTP settings
- View or change SSL certificate
- Perform remote control settings
- Update BMC firmware and reboot BMC
- Switch to EMA in Platform Mode
- Integrated Lights Out Management (LOM)
For login details, refer to Logging Into the BMC
RESTCONF API
RESTCONF has the following properties:
- Stateless: No client context is stored on the server. A request from the client will contain all the necessary information required to process the request.
Client-Server model: In a client-server model, clients are associated with the user interface, and the servers manage data storage behind the interface. This allows a separation between the client and server.
- Cacheable: Improvement in scalability and performance when the client caches responses.
- Language–independent: Unable to show "metadata-from": No such page "_space_variables"uses open standards. Any language may be used to access the API ( C++, Java, etc. ) resources via URI paths.
To use a
For access details, refer to Accessing RESTCONF API.
SOAP API
SOAP APIs provide access to Simple Object Access (SOAP) API which is protocol specification used to exchange structured information in the implementation of web services. It uses XML information set for its message format, and usually relies on other application layer protocols, such as Hypertext Transfer Protocol (HTTP) or Simple Mail Transfer Protocol (SMTP), for message negotiation and transmission. The advantage of using SOAP is that it is very versatile and uses different transport protocols. The standard stacks use HTTP as a transport protocol.
The SBC SOAP API supports the following requests for each managed object:
- CREATE – creates a managed object in the SBC.
- UPDATE – updates a managed object in the SBC.
- DELETE – deletes a managed object in the SBC.
- SHOW– retrieves managed object details from SBC.
- User defined operations – For example, manual switchover of the SBC.
The
For access details, refer to Accessing SOAP API.
RAMP SBC Configuration Manager
If your network includes the
The SBC Core includes the utility /opt/sonus/bin/SbcSftp
with permissions -rwsr-xr-x
, which allows you to securely transfer files to a remote server using the Linux shell.
When executed, the program SbcSftp
:
- Creates the necessary Access Control List (ACL) to allow the sftp connection from the SBC Linux shell to a remote server
Uploads/Downloads specified files to/from the remote server over a SFTP session, if the user has permissions to access the file
- Deletes the ACL
The advantage of using SbcSftp
over standard sftp
is that SbcSftp
automatically creates and deletes ACLs for accessing the remote server. For details, refer to SbcSftp - Secure File Transfers with Automated ACL Creation and Deletion.