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!

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

Restoring DB to different 3300 chassis version.

Status
Not open for further replies.
12345kevin

12345kevin

Vendor
Feb 15, 2006
125
GB
We have a customer with an MXe chassis and raid hardrives that developed a fault. The engineer attending had an MXe3 chassis and single hard drive with him so he loaded the correct software and swapped, modules, sys ID etc and got the customer back on line.

Subsequently we have returned to site with an MXe chassis with the customers raid hardrives installed. The engineer has proceeded to swap the parts and restore the latest backup as there has been many changes during the 2 week period since the system failed. All appears to be good as the system goes alarm free and all seems to work. However IP devices are unable to make calls over either of the E1 circuits (1 is PRI & 1 is Dass2) Analogue extensions and supersets on the Per Cabs are able to dial out fine. So it would appear to be an issue between IP & TDM

We have also tried a 2nd MXe Chassis which had the same issues.

Software is MCD6.0 SP1

At present we have left the MXe3 on site

Could there be an issue when using a Database that has been on an MXe3 and converting it back ? I cant see why it would be different.


 
Sort by date Sort by votes
Changing between variants of MXe is not an issue so it is unlikely to be this.
Is the MXe an expanded system with a 2nd processor card (E2T)? When fitted it does all the IP to TDM conversions.
If so then this needs to be configured with an IP address.


Share what you know - Learn what you don't
 
Upvote 0 Downvote
Neither of the systems has second processor to worry about.
 
Upvote 0 Downvote
The symptoms definitly suggest an E2T issue

what alarms are present?

**********************************************
What's most important is that you realise ... There is no spoon.
 
Upvote 0 Downvote
I would agree that it appears to be E2T related. There are no alarms on the system and both MXe chassis show the same symptoms, so ruling out any hardware issues with E2T resources. The only cards transferred between chassis are Dual T1/E1 and 2 x Fim.
 
Upvote 0 Downvote
The only other thing that it could be is the default gateway on the RTC.
If this is not correct then this will cause the same symptoms.


Share what you know - Learn what you don't
 
Upvote 0 Downvote
What Supernova suggests will be true if IP phones are on different subnets.

That happened to me long ago with one of the very first versions of MXe contrellers, and the problem was caused by a missing 128 echo canceller mmc. Does the new controller has the same MMC configurations than the other one?

cheers,

daniel


 
Upvote 0 Downvote
Dan might be on to something here...
Did your engineer swap out 'all' the MMC cards?
You don't say what the original fault was that prompted you to change the chassis. If there was a DSP or EC card fitted and this has been swapped over then it maybe faulty.

If EC and DSP cards have been swapped over try removing them and see if the issue resolves itself.
DSP and EC resources are embedded on the controller, however fitting MMC modules adds to the resources and if these are faulty then this might be causing the problem.

Share what you know - Learn what you don't
 
Upvote 0 Downvote
There are only 3 cards installed in the system, T1/E1 & 2 x Fim. All IP addressing, subnets, gateway etc is exactly as original and the same as the MXe3.


The original fault was very strange. After approx 20 minutes of loading, all IP devices would start to loose contact with the 3300 and then no access to the 3300 from a PC. If it was rebooted and left disconnected from the customers switch with just 2 ip phones plugged in the front all was OK ? We were convinced it was a network issue and tried lots of changes including the customer changing the 3com switch. Eventually we switched to the MXe3 and "normal" service was resumed immediatley. This is a network that has been unchanged for the last 4 years with no issues.


 
Upvote 0 Downvote
Very extrange but not the first time they happens. I have experience that same fault twice in the last year. Rebooted controller and 20 minutes after controller not responding.

Unfortunately i opened a ticket with the support guys and after a few tries the suggested to replace controller.

So you did good replacing the unit.

What I dont like is that after replacing controller you are loosing audio when changing media from IP to TDM.

Would it be easy for you to reinstall software, sync lincenses and then CreAte only a analoge extension and an IP and test if you have audio?

Please do that? And if it works then restore the DB. I wan to make sure tht that controller and its mmcs are healthy. Also, make sure the harddrives get their operating system while they are in the controller.

Regars,

Daniel

 
Upvote 0 Downvote
We always reformat / reload the software when changing a chassis as you can get some very peculiar results.

Our next stage is as you suggest get a base load onto the system and set up one analogue and one IP device. We wont be able to use the customers licensing so will just use our lab licensing, at least should prove the hardware.

This will be in the new year now as the office is closed, thanks for your input and i'll update soon.

 
Upvote 0 Downvote
Also MCD 6.0SP2 is released , we are having some issues with SP1 - different symptoms to yours but you never know

If I never did anything I'd never done before , I'd never do anything.....
 
Upvote 0 Downvote
You mention moving the sys ID in the first post? Are you phyically moving something between systems?

The beatings will continue until morale improves.
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

sadic
  • Question
Mitel 3300 MXE III
Replies
11
Views
205
sadic
sadic
VoIPP
  • Locked
  • Question
Upgrade Mitel 3300 MXe III 1
Replies
2
Views
658
TheMitelGuy
TheMitelGuy
Daniel_RO
  • Locked
  • Question
3300 cx ii new disk
Replies
6
Views
1K
voipneerd
voipneerd
W
  • Locked
  • Question
Mitel 3300 MXe III-L LAN Ports Dead
Replies
3
Views
684
jpruder
jpruder
bojo3871
  • Locked
  • Question
MiVB: Different sched/timing for day/night1 & 2 mode service for different groups?
Replies
2
Views
536
bojo3871
bojo3871

Part and Inventory Search

Sponsor

Back
Top