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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Restoring Core 1 on CS1K Rls 5.0 2

Status
Not open for further replies.

lgjc

Technical User
Sep 1, 2010
88
CA
The FMD on my Core 1 was corrupt. I have replaced it and have loaded software and customer data. I am in split mode and the High speed link and Elan on Core 1 are currently disconnected. When I check the core I just loaded the MGC loadware is not the same as the active core 0 and none of the peps are loaded. When I am loading core 1 should the HSP and Elan be connected ? Will the MGC loadware and peps load on core 1 when I attempt to do the Join? I have CPIV processers.
 
You'll want to load the MGC loadware and patches before joining the cores.
 
If you think about this being similar to a software upgrade, then you should not need to load the loadware or PEPs on core 1.

When you join the processors, part of the process is a sync of the FMDs with the active call server (core 0 in your case) acting as the source.

When you load PEPs and Loadware normally, you don't load them on both cores, you load them on the active core, and they are automatically propogated to the inactive core due to the system being in a redundant state.
 
Thanks for your responses. My thought process was the same as Allenmac but I wasn't sure. The other thing is that we did not actually issue the split command. The stat health just shows active core 0 and side 1 as unknown. I don't know if I should actually issue the split command first then connect the High speed and then Join or just go ahead and connect the High speed pipe and see if it will sync on its own??
 
I personally never leave the sync of loadware and patches to an automated process. The extra few minutes it takes to know that the proper loadware and patches are installed on the CPU that was just reloaded is worth it to me. I've had enough PSDL file and PSDL sync errors in the past that I don't trust anything automated anymore when doing upgrades or replacing failed processors. I had a 1000E that switched CPUs and downgraded all the MGC loadware due to this exact type of maintenance that was performed in the past.

It's just a matter of personal preference for me.
 
As long as the system is redundant, I have never had a problem with the PEPs, PSDL, or loadware.

I can imagine that if the system redundancy was lost, and the system restarts on the 'older' core where you would have problems.

I've been working on these systems since release 20 was just coming out.
 
I've never had an issue when the system was redundant either, just when reloading/replacing a failed CPU, only a couple of times, and only on 4.5 and higher software. Those couple of times were all it took to make me gun shy.

You have me beat. I got introduced to this world in the release 25 days.
 
Thanks for the input guys. We decided to load the loadware and will be putting it into service tonite. We have not yet done the peps since it is not just a plain deplist , it has other single patches so if we load deplist the patch handles probably won't match what is in core 0. I'm told I can use filezilla and FTP the whole list from core 0 and FTP it on to core 1. Anyone used this method as I am not familiar with using FTP ?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top