32 Appendix A Troubleshooting
NN40020-401
If your BCM50 3.0 (or SRG50 3.0) system does not function properly
If your BCM50 (or SRG50) system does not function after the upgrade and the problem cannot be
corrected by other troubleshooting methods, then complete the following steps to revert your
system back to its pre upgrade status and attempt the upgrade again.
1 Use the reset switch to perform a level 2 reset on your BCM50 (or SRG50) system to factory
defaults. For details about performing a level 2 reset, see the Installation and Maintenance
Guide.
If you did not upgrade the manufacturing image of your system, your system reverts back to
the factory defaults of the software version before the upgrade (BCM50 1.0 or BCM50 2.0).
If you did upgrade the manufacturing image of your system, then your system reverts to the
BCM50 3.0 factory defaults.
2 For SRG only, convert your BCM50 system to an SRG50 system. For more information about
creating an SRG50 system, see the Survivable Remote Gateway 50 Configuration Guide and
Communication Server CS 2100 Configuration-Survivable Remote Gateway 50
(NN42200-500).
3 Restore the BCM50 (or SRG50) data to your system from the backup you created during the
pre upgrade tasks.
The BCM50 (or SRG50) system is now back at the pre upgrade configuration. You can attempt the
upgrade again.
If your BCM50 3.0 system generates a 31250 alarm after the upgrade
This warning alarm indicates that you upgraded your system to BCM50 3.0, but you have not
upgraded the manufacturing image to BCM50 3.0. The system generates this alarm every time the
BCM50 3.0 reboots.
This alarm does not affect the services running on the BCM50 3.0 system, therefore it is not
mandatory that you upgrade the manufacturing image.
To upgrade the manufacturing image to BCM50 3.0, see Upgrading the manufacturing image to
BCM50 3.0 on page 27.
