Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Failed Upgrade to Rls 6.0 2

Status
Not open for further replies.

klamb

IS-IT--Management
Mar 30, 2001
55
0
0
GB
Hello,
Over the weekend we attempted to upgrade from Rls4.5 to Rls 6.0
The system was built in a test chassis, verified, then the components were moved to the Live chassis where the replacement cards and new sig servers were installed, etc...

Once everything was up and running it was noticed that the call processors were not joining the security domain - all MGCs joined but the call processors did not.
Trying reg ucm sys - the call processors didn't recognise the fingerprint, etc, we acknowledged and continued to add anyway only to be met with an error advising that:
BUG761 could not securely store data (RADIUS 1)

which effectively means that the call processors cannot join the security domain.

We tried reinstalling UCM, Call processors, everything - still the same problem, had to back out of the upgrade.

Any pointers would be appreciated.


 
I had this happen once, and Nortel worked some PDT magic to fix the problem, but the command syntax didn't get posted to the below solution.

This is one of the famous no answer answers from Nortel solution search:


Solution Detail


CS 1000 6.00R: Unable to register Call Server (CS) to the security domain

--------------------------------------------------------------------------------

Problem Description
Unable to register vxWorks CS to security domain.
When the "reg ucm sys"command is issued in LD 117 the following error is displayed:
BUG761 Problem storing secured data. (Type: RADIUS Error code: 1)

Cause of problem
The secret manager file is damaged.
Problem Resolution
1. Reset the secret manager file back to system defaults.
2. Regenerate the Secure Shell (SSH) keys on the CS.
3. Unregister and register the security domain.

 
thanks for the prompt and precise response - that is exactly the issue.

We tried flattening the cards and servers and rebuilding from scratch but got the same issue - possibly the rebuild kept some inherent config from the previous install.

Will see if we can find any way to reset the secret manager file back to defaults....

Thanks.
 
I dug out some old notes. No warranty expressed or implied. :)

From PDT:
smDataStructureDump
smCreateDefaultFilesAndData

Afterwards go into LD 117:
ssh key gen act
reg ucm sys
 
Muchas gracias....

will pass this along to the engineers.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top