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

Trying to swap two 008 MLX cards for 016 MLX cards 2

Status
Not open for further replies.

troidus

Technical User
Feb 21, 2015
8
US
Good afternoon, everyone.

Have a Legend chassis running Magix Release 4.0 v7.0 on a CKE4 processor. All 17 slots are full, but it's not yet at 200 station ports. I was hoping to change that by replacing two 008 MLX cards in slots 9 and 10 with 016 MLX cards. Got the cards in and did a board renumber, but then could not call in or out on either local, long distance, or Tie T1 cards, receiving a fast busy, instead, and immediately after dialing 9 for outside calls. Calls to other extensions within the switch were fine, though. Current layout is:

0
CKE4​
1
408 GLM-U​
2
408 GS/LS-MLX​
3
008 MLX​
4
016 MLX-U​
5
016 MLX-U​
6
016 MLX-U​
7
016 TRR​
8
016 TRR​
9
008 MLX-U​
10
008 MLX​
11
100D​
12
100D-U​
13
016 MLX-U​
14
016 MLX-U​
15
016 MLX-U​
16
100D​
17
016 MLX-U​

11 is a tie line to another switch running Legend Release 7. 12 is a T1 for local phone service. 16 is a T1 for long distance.

What'd I miss? I thought the T1 cards would keep their numbering, and I'm pretty sure they did, but I had only an hour of downtime to work in and had to quickly roll back to the original config, so didn't get a printout. Thanks.
 
You have to look at load too. That middle cabinet may need a new power supply to support all those 016MLX's. I'll see if I can find the load requirement and let you know.
 
To calculate the actual unit loads per carrier:
1. Add up the unit loads for each type of module by using Table 2-4. If the total
doesn’t exceed 96, no further calculations are necessary. Table 2-4
assumes a mix of telephone types with no more than 50% of telephones
being large, multi-button telephones (4424LD+, 4424D+, 4412D+, MLX-
20L, MLX-28D, ETR-34D, and ETR-18D telephones).

An 016MLX has a load of 27, an 016TR has a load of approx 13 so your 2nd cabinet is now over 100. That will take it and everything else after it (your PRI's) down. You will need to re-arrange the modules if you want to get to 200 stations.
 
Below are the unit loads for each card. Each cabinet needs to be below 96:

Circuit Module App Code Type UNIT LOAD
617A52 412 LS-TDL 13
617A58 024 TDL 24
617A59 100R INA 0
617C21 008 MLX 13.5Unit Loads
2-21
Installing the Control Unit
2. If unit loads calculated fromTable 2-4 exceed 96 or if >50% of the
telephones are large multi-button telephones, calculate the actual total
using the Unit Load values in Table 2-5 on page 2-22 for each type of
station device and trunk shown in Table 2-5 (include DSS and adjuncts
powered from the Processor)
617A54 016 MLX 27
617E34 016 T/R 12.8
617A56 016 ETR 24
617B35 800 NI-BRI 0
617G20 800 DID 8.0
617 E28 008 OPT 8.0
617D14 400 E&M 8.0
617B31 800 GS/LS-ID 0
617N15 100 DS1 0
617S15 100 DCD 0
617E29 408GS/LS-ID-MLX 13.5
617A49 MERLIN Messaging 0
 
You would probably be better off getting TDL cards and adding some 44xx series phones as they have less load.
 
Thanks for the quick response. Where can I find these load tables? I generally have only MLX-10Ds installed, so I definitely don't have a large per-station load, but if the ports themselves are a problem, then I'll have to figure out how to rearrange them.

My first attempt at installing boards had me replacing the 008 in slot 9 with an 016, pulling the 008 in slot 10, then shifting the remaining boards forward one slot and putting the second 016 MLX in slot 17, but that completely hosed my extension numbering, taking what had been in slot 10 and shifting it to 13, instead of bringing it forward to the new ports in slot 9. I didn't check to see if I could call out with that config, but if power issues require it, then I guess that's what I'll have to do. I'm trying to depopulate the Legend as much as I can as cheaply as possible to ease a later transition to a new VoIP system (and because I can't keep SMDR running on the Legend because something keeps blowing out the port), so doing a massive module and station upgrade on the Magix isn't in the cards.
 
OK, so I did some math. Using the default load numbers, the second and third expansion chassis are out of spec as is, at 108 each, and the first is close at 94.5. Calculated loads based on what's plugged in are much better, at 56.6, 70.2, and 61.5. Loads from my first attempt (which really messed with the extension numbering) came in at 94.5, 108, and 108 with default loads and 56.6, 70.2, and 61.5 with calculated loads. The second attempt, when I couldn't call out, came in at 94.5, 81, and 135 with default loads and 56.6, 55.8, and 75.9 with calculated loads. The power supplies are all 391C1s, so I think I should have been OK. I wish I had tried to place calls on the first attempt, before looking at the extension numbers.

Thoughts?
 
I'm not sure why you drained the swamp in the first place, but you realized just how big and mean the Alligator population really is, once you got rid of the water. So, now how can you go forward.

I'd do this, A PRINT ALL, then, switch the Modules around like you were trying to do, and then do another PRINT ALL. (Put it back to the Original Config, one more time) and then look at the two print outs and see what changes would be required to fix the New Config.

Once you get that figured out, you should be able to proceed with nothing more than a few dozen hours work.

I avoid moving Modules around like the Plague. It's like trying to teach a Dog how to bathe a Cat. It can get very messy, and the Dog nor Cat like it at all.



-merlinmansblog.blogspot.com
 
LOL. Thanks for that visual. The modules haven't been touched since 2007, and never by me except to replace failed ones. I'm trying to get everyone in the main building on the same switch, but I can't quite get there with what I have, which is why I want to swap out the two modules. Some of these folks have managers who want to see the SMDR records, and I can't keep SMDR running on the other switch (two log servers and three SMDR ports have blown up in recent years, and even zorched a 355AF adapter in one of the failures), so I'm trying to depopulate it as much as I can. I wouldn't mind doing a Print All if it didn't take six hours to run. Any suggestions for speeding it up?
 
You can manually do it yourself. Under maintenance, System, Port, enter *0101 (port 1, slot 1). It will tell you the extension associated with it. You could then press the next button and it will tell you the adjunct associated with that port, next again will show you port 2, slot 1. Keep pressing next and writing it down. Takes a while, but can be quicker than doing a print all.

The benefit of the print all is you will have all the programming in case something doesn't come back working properly. The above is just telling you what extension is in what port of the system.
 
Thanks for that, and I've used that method before on the other switch that has no SMDR, but I usually just Print the Ext Direct. (Finally got WinSPM installed on the log server over there and have used that to dump info via the Admin port, so no more manual reports.) I actually have really good mapping for the station ports, but knowing the button programming and if anyone is currently forwarding will be essential.

Maybe it'll be enough to get a Print All initially, and then print the Ext Direct after switching modules. That'll tell me which ports have which addresses, and hopefully the button programming moves in tandem. That print won't take nearly as long, and I can examine the All dump beforehand to see if someone on an affected module has a bunch of buttons and compare that to a print of that same extension number after the module swap. If the programming, the extension number, and the label move together, then I could just move patch cords for a bunch of them.
 
Here's a thought, If 11 is for the Other switch, where those extra MLX Sets are moving from, why not move your SLOT 16 Translations for the LD T1 to 11, get rid of 16, and then (if this will yeild enough MLX Ports) put an 016-MLX in slot 16. I think that would be the least amount of re-programming, if it'll fit.

It's just a thought!



-merlinmansblog.blogspot.com
 
That'd be nice, but that'll have to wait until the company decides to replace the phone system. Once I've moved the MLX sets (and two BIS-22 sets that are being upgraded, down from 23 that had been in service) that are scheduled to move, I'll still have 18 MLX sets and 29 active T/R ports on the other switch.
 
I succeeded, but neglected to come back in here to update the thread.

I was able to replace the 008s in slots 9 and 10 with 016s. This caused all of the station port and adjunct numbers past slot 09 port 08 to change, but left all of the programming and labeling in place on the ports. It was a simple matter to go into SysRenumber/Single/Extensions for 09/08 and Next my way through the rest of the ports, putting the station port numbers back the way they were. I had made sure I was not using any Adjuncts in the affected range ahead of time, so I could skip over those. It also did not affect my 100D card addressing at all.

Yes, load calcs were important. Taking the default numbers I was over, but since I don't have anything fancier than an MLX-16D in service for regular stations, I was well under the load limit.

Thanks again, everyone, for your help.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top