In this section:
This guide lists the minimum number of tasks recommended to maintain an in-service SBC 5xx0/5400/7000 system. This guide is not intended to explain diagnostics, repair specific faults, nor is it intended to optimize performance. File locations and system settings may vary, mainly due to customer-specific configurations and requirements.
This guide does not cover the following topics. Refer to the specified documents for more information on them.
As a routine maintenance best practice, Ribbon recommends the following:
Build a template and create a daily/weekly record log, spreadsheet, or database that you can use to record the observed results and notes.
Identify what tasks in the Routine Maintenance Guide you intend to run and set a schedule. Include fields against each task such as run date, run time, results, and comments.
Plan your day to run the checks. If a day or task is omitted, make sure you annotate that the task was not run.
Look for trends.
If there is an anomaly in a result, pass the event or incident on for triage. Contact Customer Support.
See How to Access the SBC for guidance with accessing the SBC EMA, EMA (Platform Mode), CLI, and BMC interfaces.
Routine SBC daily maintenance tasks include the following activities:
This section includes the following methods for backing up the SBC configuration:
Perform the following procedure to back up the current configuration using EMA:
Perform the following procedure to back up the current configuration with the CLI:
From the top-level CLI mode, enter the command:
request system admin <SBC_system_name> saveConfig fileNameSuffix <filename.suffix>
yes
'. A message displays indicating the configuration was saved to a tar.gz file.<filename>.tar.gz
file from the /var/log/sonus/sbx/config
directory to a remote location using FileZilla or some other software utility.
The SBC stores up to 10 manual and 7 automatic backup files.
This section includes the following methods for monitoring SBC various status indications:
To monitor outstanding alarms across all managed objects from the EMA, see Dashboard - Alarms page.
To monitor the status of the following entities from the EMA, see Dashboard - System Status page.
To monitor system status from CLI top-level mode, the following commands are available. For additional commands and command details, see Show Status System and Show Table System pages.
show status global callCountStatus all show status system daughterBoardStatus show status system ethernetPort mgmtPortStatus / packetPortStatus show status system fanStatus show status system hardDiskStatus show status system hardDiskUsage show status system powerSupplyStatus show status system serverStatus show status system syncStatus show status system systemCongestionStatus
Use one or more of the following methods below to monitor SBC performance.
To monitor the following critical system statistics from the EMA, see Dashboard - System Statistics page.
To perform policy analysis from the EMA using SSReq tool, see Troubleshooting Tools - Policy Analysis - SSREQ page.
To monitor the following statistics from the EMA (Platform Mode), see Monitoring - Dashboard page.
To monitor SBC performance data from CLI top-level mode, the following commands are available. For additional commands and command details, see Show Status Command Details - CLI and Show Table System pages.
show status alarms historyStatus show status system dspRes dspCallCurrentStatistics show status system dspRes dspUsageCurrentStatistics show status global tcpGeneralGroupStatistics show status system dspStatus dspUsage show status system ethernetPort mgmtStatistics show status system ethernetPort packetStatistics show status system systemCongestionCurrentStatistics show status global udpGeneralGroupStatistics
Perform the following SBC routine maintenance tasks on a weekly basis:
The Logs Management window (EMA - Platform Mode) allows you to manage the following logs. For details, refer to Log Management.
For security protection, the Netconf interface does not support "/aaa" records.
The TShark Logs and System Diagnostic Logs are available only when you select and execute these objects, for more information on usage of these objects, refer to the respective links Troubleshooting Tools - TShark and System Administration - System Diagnostics.
Delete unneeded files, such as old core dump files, on a regular basis. To manage and remove log files from the EMA (Platform Mode), see Log Management page.
To view the configured parameters for all SBC event types from the CLI, use the command:
show configuration oam eventLog typeAdmin
To view the event log status for all event types, use the command:
show status oam eventLog typeStatus
Perform the following activities prior to upgrading the SBC:
Perform pre-upgrade checks and system baselining, plus gather any requisite upgrade information.
Download the software in advance.
Back-up the system in the unlikely event that a rollback.is required.
Follow the prescribed SBC 5xx0/5400/7000 upgrade procedures. Refer to Upgrading SBC Application page and the latest release notes from Production Releases page for upgrade details.
Execute your tests to verify the system is fully operational.
If problems are detected that cannot be resolved, consider backing out of the software update.
Verify following:
1. No new fault/alarm conditions
2. No errors in system logs
3. No call failure ratio increases (for example, decreased ASR)
Once you are satisfied with the update, commit to the upgrade when applicable (for example, Live Software Upgrade using CLI).
The following procedures are included in this section:
To power off the SBC, perform the following steps:
Click the Remote Control tab to open the Remote Control screen.
Click Power Control (or click Server Power Control from the left tree menu) to open the "Power Control and Status" screen.
Select Power Off Server - Orderly Shutdown option and click Perform Action.
To power on the SBC, perform the following steps:
Select Power On Server option and click Perform Action.
To stop the SBC Application, perform the following steps:
Login to the EMA (Platform Mode) and navigate to Administration > System Administration > Platform Management.
The Platform and SBC Application Controls window appears.
Click Stop SBC Application.
To start the SBC Application, perform the following steps:
Login to the EMA (Platform Mode) and navigate to Administration > System Administration > Platform Management.
The Platform and SBC Application Controls window appears.
Click Start SBC Application.
To restart the SBC Application, perform the following steps:
Login to the EMA (Platform Mode) and navigate to Administration > System Administration > Platform Management.
The Platform and SBC Application Controls window appears.
Click Restart SBC Application.
To reboot the SBC Application, perform the following steps:
Login to the EMA (Platform Mode) and navigate to Administration > System Administration > Platform Management.
The Platform and SBC Application Controls window appears.
Click Reboot Platform.
For detailed information on different SBC application, refer to System Administration - Platform Management.
Monitor the Platform and SBC Application Controls window to observe the various processes.