| |||||||||
![]() | | ||||||||
| |||||||||||||||
| |||||||||||||||
| Meridian Systems Welcome to the Nortel Meridian Forums Including Meridian Options 11-81C CS1000M Meridian Mail Call Pilot Companion and Sucession Hospitality OTM MAT MICB RAN NetGateway ..., and all other Applications |
| Tags: parallel, reload, sysload |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #1 (permalink) | ||||||||
| Junior Member
Location: NC Rep Power: 0 ![]() | What is best to clean up some corrupt TN's?? Parallel Reload or Sysload? Support group suggest a Sysload. And would a parallel reload invoke a Sysload? Again, I'm not U/G'ing in any fashion(sftware or hardware), just have to clean up some corrupt TN's. | ||||||||
| | |
| | #2 (permalink) | ||||||||
| Senior Member
Location: NORTEL - NJ Rep Power: 6 ![]() | Compatibility CP100 A parallel reload involves splitingthe processors giving you the opportunity to work on the offline side of the PBX. This offline side actually SYSLOAD's when it comes online, so you can see the effect of a sysload on your problem. While in split, the active core handles all processing, and no user outtage is experienced. You can determine if the problem you were experiencing is still there or not, and if it has cleared, you can swing this inactive side into active mode. When you switchover, you will experience a brief interuption of new calls, but existing calls will stay up for the most part. This is the preffered method for troubleshooting, as you can back out if you don;t like what you see on the offline side. A full system SYSLOAD distrupts the entire system all at once, and in my opinion, is not recomended for trouble isolation. | ||||||||
| | |
| | #3 (permalink) | |||||||||
| Moderator
Location: 1069.7 miles from Tiverton, Ontario (CANADA) Rep Power: 12 ![]() | Quote:
You da man Fletch. | |||||||||
| | |
| | #4 (permalink) | |||||||||
| Senior Member
Location: 3498.51 miles from Tiverton, Ontario (CANADA) Rep Power: 16 ![]() | Quote:
Haven't dealt with the PIIs but I know on the CPs it tends to be a 50/50 shot. So far I've found that timing the steps for the forceover seems to be the trick to avoid pooching the process. | |||||||||
| | |
| | #5 (permalink) | ||||||||
| Junior Member
Location: NC Rep Power: 0 ![]() | Startalk Flash : Help Wanted Fletch, Thanks for the input and detailed insight! The reason for my question and as you had mentioned, I too, was a little suspect of a Sysload in comparison to the Parallel reload for troubleshooting. Thanks again!! -Mike | ||||||||
| | |
| | #7 (permalink) | |||||||||
| Senior Member
Location: NORTEL - NJ Rep Power: 6 ![]() | Quote:
Bottom line if the Father /Son call registers can be rebuilt on the INI, the call path will be maintained. If that Call Register connection is lost, or cannot be established, then the call drops. Depending on where the problem is, your actual milage may vary, but I have certainly seen better than 50/50 on call drop on a regular basis. | |||||||||
| | |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
| |