Users Guide

Understanding the Sonus VSBC VNF Package | Configuring Virtualization
864 OMNM 6.5.3 User Guide
License Requirements
Sonus Networks does require and provide licenses to operate a SBC SWe (VSBC) as a fully
functional Virtual Machine in the OpenStack environment.
Contact the Sonus Networks support team regarding license requirements and logistics.
Known Issues
The Sonus VSBC instances require that the CLI user account’s password change during the initial
login session. A task was implemented in the Sonus Device Driver so that it applies a password
change via CLI communication with the VSBC during the initial SSH session established to a
newly deployed VSBC Virtualized Network Function’s (VNF’s) Virtualization Deployment Unit
(VDU).
Contact the Sonus Networks support team for further details regarding known issues or caveats
utilizing the SBC SWe VNF.
References
This section provides references to:
•
Vendor Documentation (URLs)
• VNF Configuration Methods
Vendor Documentation (URLs)
Refer to the Sonus Networks website (http://www.sonus.net) for all vendor-specific documentation.
For the Sonus VSBC documentation and release notes, refer to the following Sonus Networks
websites page:
http://www.sonus.net/products/session-border-controllers/sbc-swe
VNF Configuration Methods
A combination of image (snapshot) preparation, along with Virtualization Deployment Unit
(VDU) Post Instantiate Configuration Lifecycle Events (LCEs), is implemented in this Virtualized
Network Function (VNF) package to ensure that the Sonus VSBC VDUs are automatically brought
under OpenManage Network Manager (OMNM) management.
Customized Image Preparation
For the VSBC VDUs:
• The original qcow2 image was used to create this VNF package, without a need to customize
or take a snapshot for the Sonus VSBC VNF VDUs.
• Configuration changes are applied automatically through discovery actions to the VSBC
running in the OpenStack system post boot-up in order to have OpenManage Network
Manager (OMNM) monitor, configure and manage the VSBC.
For the SIP Client and Server VDUs:
• Cloud-init was added by first using the original image, VMSipp-RR-Master, and then
installing cloud-init on a running instance booted from the original image. A snapshot image
was created with cloud-init included.