Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: bluewhite4 on February 17, 2012, 11:26:47 PM
-
Bringing a new system online today, and had an issue never seen before.
Brand new 5330 would get DHCP from data vlan, use options and switch to voice vlan 2. They would get DHCP, and downloaded/upgraded their firmware without a problem. After the upgrade, each phone would sit say "DHCP Discovery Using Option 125" for roughly 5 minutes, then would finally load and have dial-tone. Went so far as to unplug the controller from the network, and plug a phone directly in with a PoE injector; same issue.
Anyone else seen any issues like this with 5.0SP1? Was suppose to start rolling this out for upgrade customers, but now I'm not so sure.
-
It happened to me as well with that version of software. I downgraded to 5.0 and I'll wait for SP2 to be released.
I will open a ticket to see what tech support has to say about it, I will post back...
-
Yep we have a similar issue with a 5.0 SP1 system. Even built up a spare system and it did the same thing.
Have had a ticket lodged with Mitel for over a week but have got nothing so far. ::)
Strangely enough 52xx series phones worked fine!
-
Ok, glad we're not the only ones. I opened a ticket with Mitel as well, unfortunately I was told I was imagining it. Or if it truly was happening, they wanted a wire shark trace of the phone getting DHCP. They're only suggestion was to completely reload the system, and run a fix partition in the in the vxworks boot options. In the mean time we just static'd the twenty phones on site.
-
Martyn or Danremirez, in either of your cases, were they brand new systems or upgrades?
-
Martyn or Danremirez, in either of your cases, were they brand new systems or upgrades?
One of each!
-
I have one that I recently upgraded that does the same thing.
I chalked it up to not enough resources to download all the phones about 100 at the same time.
-
Bluewhite,
My system was upgraded, not brand new.
-
For an answer on this check out KB 12-5191-00261 on MOL. It explains the cause, and it isn't actually a fault, more of design by the looks of it.
-
Saw that today. Except that it doesn't apply to us. We continued to have the pause even with a phone directly connected to the controller via PoE Injector-brick. So no vlans, no switch ports, no nothing. And also when we static'd the phones to the voice vlan we had the issue. In general anytime the phones encountered 3300 DHCP, we had the ~5minute wait.
-
I just upgraded today and have experienced exactly the same problem as the people above where 53xx series of phones took 5 minutes to get an IP. has anyone found a solution to this or had a responce from Mitel about it, other than the KB article.
-
I'd like to see a wireshark trace of this problem.
Maybe we can see what it's doing.
Ralph
-
Im currently setting a CXi up in our lab on MCD 5 SP1. Not got any handsets working on it yet though, will give it a try tomorrow and see what happens. Will also try to get a wireshark trace
-
Looks like an updated sw release available to address this. 5.0 SP1 PR1
Sent from my iPad using Tapatalk
-
From the work that I've done and closely reading the MOL KB it is just that in your option 125 that MCD dishes out to a 53xx hand set you need to ensure that there is no vlan ID in there.
As a flow on from that you also have to remove the QoS values.
-
Has anyone tried this new update to see if it solves the problem?
-
It isn't a problem as such, it's more that they have come in to line with the standards, so they wont be changing it back.
The "issue" makes a mention in the release notes for 5.0 SP1 PR1, but only as much to tell you to read the KB article on MOL.
-
the problem isn't that it doesn't connect at all which would be the case if the tagging was incorrect though, it is just that the 53xx series of phones take 5 minutes to get an IP address
-
Just read that someone found that by removing DHCP option 6 from the Mitel DHCP scope resolved issue.
Option 6 is DNS servers. Issue may be related to having multiple servers in DHCP Option 6 scope.
Ralph
Forward to international numbers (http://www.mitelforums.com/articles/international-call-forwarding.php)
-
Hmm, ok, will have to give that a go on Monday and see what happens. Pity I didn't see this yesterday as I had the perfect lab situation to try this in!
-
We have experienced the same on an CX that was upgraded from MCD 4.0 to 5 SP1. But only on two new phones that were placed after the upgrade. A 5340 and a 5312. They upgraded perfectly and worked for a while. A couple of minutes to be exact. The only way we got them working back again, was by setting the IP settings by hand. The strange on this is that on this site there are other 5312 and 5340 (running before the upgrade) and they still work fine with dynamic settings.
It concerns a site different Vlans (1 data, 2 voice).