Page History

How to Use This Guide

This guide lists the minimum number of tasks recommended to maintain an in-service 

This guide does not cover the following topics. Refer to the specified documents for more information on them.

• Troubleshooting—When the system generates alarms or traps indicating trouble, see the Alarms Guide to determine the cause and course of action. Other pages you may find useful when troubleshooting are FAQs and Tips and Using SSReq.
  
  

• Spacevars
  0 product

  hardware replacement—When replacing 

  Spacevars
  0 product

  customer replaceable units (CRUs), refer to the relevant CRU page:
  
  • SBC 5000 Series CRUs
  • SBC 7000 Series CRUs

SBC Access Methods

See How to Access the SBC for guidance with accessing the SBC EMA, EMA (Platform Mode), CLI, and BMC interfaces.

Anchor
RoutineDailyMaintenance RoutineDailyMaintenance

Routine Daily Maintenance

Routine

Backing Up SBC Configuration

This section includes the following methods for backing up the 

• Back Up SBC Configuration Using EMA
• Back Up SBC Configuration Using CLI

Anchor
BackUpSBCConfigurationUsingEMA BackUpSBCConfigurationUsingEMA

Back Up SBC Configuration Using EMA

Perform the following procedure to back up the current configuration using EMA:

1. Backup your configuration using the procedure on the page System Administration - Backup/Restore.
2. Copy your configuration to a remote location using the procedure on the page System Administration - Backup/Restore.

Anchor
BackUpSBCConfigurationUsingCLI BackUpSBCConfigurationUsingCLI

Back Up SBC Configuration Using CLI

Perform the following procedure to back up the current configuration with the CLI:

1. From the top-level CLI mode, enter the command:

   Code Block
   language none
   request system admin <SBC_system_name> saveConfig fileNameSuffix <filename.suffix>

2. When prompted to continue, enter 'yes'.  A message displays indicating the configuration was saved to a tar.gz file.
3. Copy the latest <filename>.tar.gz file from the /var/log/sonus/sbx/config directory to a remote location using FileZilla or some other software utility.
   

Monitoring SBC Status

This section includes the following methods for monitoring

• Monitoring EMA Alarms
• Monitoring System Status From EMA
• Monitoring Status From CLI

Anchor
MonitorEMAAlarms MonitorEMAAlarms

Monitoring EMA Alarms

To monitor outstanding alarms across all managed objects from the EMA, see Dashboard - Alarms page.

Anchor
MonitorSystemStatusFromEMA MonitorSystemStatusFromEMA

Monitoring System Status From EMA

To monitor the status of the following entities from the EMA, see Dashboard - System Status page.

• Server Status—status of the system including the name, hardware and software versions system up-time.
• Fan Status—current fan speeds.
• Hard Disk Status—hardware information about the on-board disks along with total capacity and status.
• Hard Disk Usage—disk status and usage.
• Power Supply Status—status of the power supply including any failures.
• Daughter Board Status—list of daughter boards present on the system.
• Policy Server Status—statistics of the routing database and application (local or external).

Anchor
MonitorStatusFromCLI MonitorStatusFromCLI

Monitoring Status From CLI

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

Monitoring SBC Performance

Use one or more of the following methods below to monitor

• Monitoring Performance From EMA
• Monitoring Performance From CLI

Anchor
MonitorPerformanceFromEMA MonitorPerformanceFromEMA

Monitoring Performance From EMA

To monitor the following critical system statistics from the EMA, see Dashboard - System Statistics page.

• Call Count Statistics
• TCP General Group Statistics
• UDP General Group Statistics
• System Congestion Statistics
• DSP Call Statistics
• DSP Usage Statistics
• DSP Utilization

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.

• Alarms
• CAC Offenders Status
• CPU
• Disk Usage
• Hardware Inventory
• IP Interface Status
• Live Monitor
• Memory Usage
• Ports
• System Statistics
• System Status
• System and Software Info
• Task Usage

Anchor
MonitorPerformanceFromCLI MonitorPerformanceFromCLI

Monitoring Performance From CLI

To monitor

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

Anchor
RoutineWeeklyMaintenance RoutineWeeklyMaintenance

Routine Weekly Maintenance

Perform the following

General Maintenance

• Wipe the outer case clean with a slightly moist (not wet), lint-free cloth.
• Inspect air filters, and clean or replace if needed. To replace an air filter, see the applicable page:
  • SBC 5000 Series Air Filter
  • SBC 7000 Series Air Filter.
• Check external fan covers or grills for excessive dust buildup or obstructions; clean, if necessary, by gently wiping with a clean, lint-free cloth, making sure not to penetrate the protective cover or grill.
• Check fans to ensure they are operating and not generating any unusual noises. Make certain the fan is operating by holding your hand next to the intake vent to be sure air is flowing into the unit. If a fan is not running or unusual noises are present, contact Customer Support.

Backing Up SBC Logs

The Logs Management window (EMA - Platform Mode) allows you to manage the following logs. For details, refer to Log Management.

• Core Dumps
• Event Logs
• Message Logs
• System Dump
• Back Trace
• Apache
• Netconf
• User Activity
• Install Logs
• Upgrade Logs

Deleting Old SBC Logs

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.

Viewing SBC Log Files and Status From CLI

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 

Anchor
SBCUpgradeGuidelines SBCUpgradeGuidelines

SBC Upgrade Guidelines

Perform the following activities prior to upgrading the

Preparation

Perform pre-upgrade checks and system baselining, plus gather any requisite upgrade information.

1. Read all release notes for any pertinent upgrade instructions and applicable patches. See Production Releases page for available release notes.

2. Read all applicable WBAs (Check the associated release notes for applicable WBAs).

   Tip
   To view WBA details, login to Customer Portal and from left panel, enter WBA into the Find Solutions search field, then click Go.

3. Download the software in advance.
4. Verify network is healthy and in a condition to accept an upgrade.
5. Familiarize yourself with the upgrade and roll-back procedures.
6. Select a period of low traffic to perform the upgrade. Inform end users.
7. Contact Customer Support to schedule on-call support.

Backup

Back-up the system in the unlikely event that a rollback.is required.

Upgrade

Follow the prescribed

Decision Point

Execute your tests to verify the system is fully operational.

1. Ensure the upgraded software release and data migration has no detrimental impact on existing functionality.
2. Test interoperability with existing third-party applications, OSS, OA&M, BSS, and so on.
3. Focus on customer-sensitive aspects.

Failure Recovery

If problems are detected that cannot be resolved, consider backing out of the software update.

Post-Upgrade Monitoring

Verify following:
1. No new fault/alarm conditions
2. No errors in system logs
3. No call failure ratio increases (for example, decreased ASR)

Commit Software

Once you are satisfied with the update, commit to the upgrade when applicable (for example, Live Software Upgrade using CLI).

Anchor
ShutdownandStartupProcedures ShutdownandStartupProcedures

Shutdown and Startup Procedures

The following procedures are included in this section:

• Powering Off the SBC
• Powering On the SBC
• Stopping/Starting the SBC

Anchor
PowerOff PowerOff

Powering Off the SBC

To power off the