In this section:
The DSP25 module shown in the figure below is the second generation Signal Processing Server (SPS) for SBC 5400 providing increased signal processing capabilities by incorporating the latest DSP technology.
DSP25 modules are considered hot-swappable. They may be removed and replaced without powering down the node. For example, inserting a DSP25 module which is administratively enabled results in the module booting up as normal without user further intervention. Appropriate alarms are raised and automatically cleared by the system. The current node continues to deliver service (if Active SBC) or provide protection (if Standby SBC).
The DSP25 module is accessible from the rear of the chassis, and connects to the DSP2x tray. The DSP25 module contains five DSP devices. The product codes for DSP25 modules are SBC-5400-DSP25 and SBC-5400-DSP25-S.
A DSP25 module is inserted/removed to either increase/decrease DSP capacity, or to replace a faulty module. DSP25 modules are added to or removed from the SBC 5400 platforms using one of the following methods:
Only one DSP20 is allowed in SBC 5400 chassis, and it must reside in slot 1. Mixing DSP20 and DSP25 modules (both within a chassis and between Active/Standby servers) is not supported. For example, if SBC-A contains DSP25 in slot 1-3, SBC-B should also have a DSP25 in slots 1-3. As another example, if SBC-A has a DSP20 in slot 1, SBC-B should not have anything other than a DSP20 in slot 1.
In case of a DSP failure, the SBC supports reloading the faulted DSP in one second without a system switchover while restoring channels, if any, and collecting coredumps. If the DSP reload fails or if the number of DSP failures exceeds two within 24 hours, the SBC performs a system switchover.
For more information on the DSP Channel Densities, see SBC 5400 DSP Densities.
To prevent damage from electrostatic discharge, an ESD strap is provided in the accessory kit. See Connecting ESD Wrist Strap to install it.
The following procedure describes the basic steps to replace the DSP25 module. If your system is in a production environment, more detailed steps are provided further down on this page.
Loosen the screws securing the DSP25 module (or slot cover) at the rear of the SBC 5400 chassis.
Insert the new/replacement DSP25 module into the empty DSP slots.
On HA server pairs, the modules should be installed in matching physical slot locations to maintain redundancy protection. Install the DSP25 modules in order of slot 1, 2, 3, 4. For example, if you install two DSP modules in slot 1 and 2 on Active SBC, and 2 DSP modules in slot 2 and 3 on Standby SBC, a mismatch will result and calls will get dropped.
Run SBC HW Diags and observe results after the installation is completed.
The SBC operator interface allows the operator to gracefully or forcefully dry up calls on a module and disable a DSP25 slot.
Removing a DSP25 module that has not been administratively disabled in a non-HA configuration triggers a service-impacting reboot. This is to prevent an indeterminate FPGA/bus state on the common hardware (that is, motherboard). In other words, predictable behavior cannot be guaranteed if the system is allowed to run without reboot.
A detectable DSP25 module failure triggers the SBC node to reboot and return to service in a degraded state (that is, less DSP capacity). The SBC node reboots, detects the DSP25 module failure during initialization and returns to service with the DSP25 module disabled.
For CLI command details to enable/disable DSP slot, see Daughter Board Admin (CLI). For EMA, see System - Daughter Board Admin.
Use the following CLI syntax to administratively enable the DSP2x module:
% set system daughterBoardAdmin <system name> <slot #> state enabled
The DSP software can also be enabled from the All > System > Daughter Board Admin path in SBC main screen.
From the Daughter Board Admin screen, select "enabled" in the State field.
Use the following CLI command syntax to administratively disable the DSP2x module. By default, the disable cleanup type is set to "graceful".
% set system daughterBoardAdmin <system name> <slot #> state disabled
On SBC main screen, navigate to the Daughter Board Admin screen and select "disabled" from the State field.
The steps below describe module replacement procedure in an HA pair configuration for a DSP25 module that experiences a hardware failure. This procedure assumes that the failure is detected at run-time and during subsequent start-up diagnostics.
The following HA configurations are available to dictate SBC behavior in case a DSP25 module fails or mismatched DSP hardware is detected between active/standby nodes using the set system admin dspMismatchAction
command. For CLI details, see Admin (CLI), For EMA, see System - Admin.
If a switchover occurs while operating in this mode, calls using DSPs on the primary SBC that correspond to the disabled slot on the secondary are not protected during switchover (that is, partial redundancy).
The procedures below describe two methods of adding DSP25 modules to an in-service SBC 5400 HA pair to increase DSP capacity. In these procedures, "SBC-A" represents the currently active SBC and "SBC-B" the current standby.
Steps 2 and 3 in the procedures above are not required, but are included to trigger the switchover in a more standard way with predictable behavior. Additionally, these steps cause the preserve-redundancy/preserve-capacity logic to take effect.
The procedures below describe removing DSP25 modules from an in-service SBC 5400 HA pair to decrease DSP capacity. In these procedures, "SBC-A" represents the currently active SBC and "SBC-B" the current standby.
If the SBC is configured to 'preserve capacity', this procedure is service impacting, and calls may be dropped.
Calls using DSPs on the primary SBC corresponding to the disabled slot on the secondary are not protected during a switchover (that is, partial redundancy). Loss of active calls can be avoided by performing a dry-up prior to module removal.
The DSP25 module includes a Field-Programmable Gate Array (FPGA) that may occasionally require reprogramming. The reprogramming is fully autonomous and occurs during system reboot process. The only noticeable effect to the system is a slight increase to the duration of the system reboot. For each DSP25 installed, expect an additional 1-2 minutes added to the length of a normal reboot process.
Log messages pertaining to FPGA reprogramming are stored in the following files:
/var/log/sonus/sbx/openclovis
directory. This file contains all logs related to system startup as well as a log of other scripts that call this FPGA reprogramming utility./var/log/messages
file.Example Log Messages:
No upgrade is needed for a slot
updateAll:: key: 1, value: DSP25. NO ACTION REQUIRED FOR SLOT 1. version 2013/03/20 18:03:52, minVersionRequired 2013/03/20 18:03:52
Upgrade is needed for a slot
updateAll:: Require update for slot 1 version :: 2013/03/20 18:03:52 and minVersionRequired 2013/03/20 18:03:53 upgradeFpgaForSlot Upgrading FPGA for Slot 1 Loading DSP25 FPGA File to memory [rr_dsp_mux3_routed.rom]...Complete Design Name: rr_dsp_mux3_routed.ncd;HW_TIMEOUT=FALSE;UserID=0xFFFFFFFF Device Name: 6vlx75tff484 Version: 2013/03/20 18:03:52 Image Length: 0x00320c2c Erasing DSP25 SPI Flash [SLOT 1]... Complete Programming DSP25 SPI Flash [SLOT 1]... Complete
All SBC SBC 5400 CRUs are shipped in ESD bags and must be handled using appropriate ESD precautions.
The storage environment for these CRUs are:
The ESD Susceptibility symbol warns of the presence of Ribbon devices susceptible to electrostatic discharge. Do not handle equipment without wearing a properly grounded ESD wrist strap.