MM314 POE issue

[rlance610]

Everyone, I am working on a G350 with a MM314 (24 POE switch) and the gateway/mm are having some troubles. I am getting a "workQPanic: Kernel work queue overflow" whenever I have the module inserted. When I take it out the g350 boots normally. Has anyone run into this before, and if so how was it resolved. Thanks in advance!

Randy

 

[Mitch672]

Yes, AVAYA is having issues with the G350 Suffix: D HW Vintage: 1, and the new HD MM314 Suffix: C HW Vintage: 1 or 2

They have a "test" release of G350 firmware (g350_sw_27_27_10.bin), but, I have found that replacing the G350 (returning it to your AVAYA ditributor and getting another one) is the fastest way to solve the problem.

In my case, I had 3 different G350's for 3 different clients I replaced all 3 of the G350's, and after upgrading them to g350_sw_27_27_0.bin, they all worked... of course the G350 version now claims to be: Suffix: B HW Vintage: 3, even though before the 27_27_0 firmware it showed up as Suffix: D HW Vintage: 1

AVAYA thinks some G350's where made with 50Mhz oscillattors instead of 33Mhz oscillators.

In any case, your going to have to open a case, and get the G350 replaced, most likely.

mitch


AVAYA Certified Specialist

 

[josephr123]

hey Mitch, if you reset the gateway does it still work? I found 1 that the card worked until a reset. I have downgraded my 3 gateways to 25.30 and they work and Avaya told me they were aware of the problem and are working on it.

 

[Mitch672]

yes, older firmare didn't have an issue, and worked fine.

mitch


AVAYA Certified Specialist

 

[backe]

Hi
I have a prolem
I have G350 with MM314 but I cannot manage to put MM314 to work
In ASA I cannot see the module wich is allready inserted

Do I have to set up something in ASA or via console on G350 to make it work?

 

[Mitch672]

nothing you do in ASA will fix this issue. We are STILL having issues getting MM314's recognized by the G350's. This has been going on for MONTHS now, and AVAYA does not seem to be addressing this issue. We end up sending back the G350 and the MM314, and get replacements, eventually we get a pair that works. This is totally unacceptable, I now have 3 sets of these we are having issues with. AVAYA came out with some new expirmental G350 firmware, but that makes no difference. They have a hardware issue, something to do with a 50mhz oscillator in the new G350, and they need to address this issue.

All you can really do is open a case with AVAYA, hopefully once they see just how widespread this issue is, someone will address it directly.

mitch


AVAYA Certified Specialist

 

[IPOthermia]

Would and NVRAM INIT help?

Just a thought.

Thanks.
Matt...

 

[backe]

NVRAM init is not helpful

 

[Daudet]

Well i am into a 100 sites project and i have 6 MM314 so far that will not boot in G350.
So far this is the MM314 blade that is defective.
When i provision G350 i do it in batch of 3 or 4 in my LAB and when i hit a defective MM314 i try it in all 4 GW with same result.
i Even have 2 that were OK in the LAB and then 2 weeks later i ship to remote site for installation and they dont work. Another on blew up 4 weeks after installation.

How do you get replacement, are you sending the defective unit to Avaya direct? Here in Canada 30 days after we receive the material the DOA replacement does not apply anymore. So we have to send it to repair which takes months to get it back.

Daniel

 

[Mitch672]

Daniel you need to test them within the 30 days, and send tem back to your vendor, which is what we do. After that you have to deal with AVAYA National Parts, and they only send out refurbed units... Just don't buy any more than you can test within the 30 days, would be my recomendation.

Also, AVAYA is well aware of this issue, and has supposedly gone through our distributors inventory and removed any defective G350's (yes, the problem is an oscilattor in the G350 that causes the problem)

mitch

P.S. Nice to see you here, you worked on one of our Candian (Montreal) clients with me a ways back, we had a little discussion about ProVision


AVAYA Certified Specialist

 

[Daudet]

Mitch672,
can you ring my Bell for this Canadian Customer in Montreal? I am doing so many..
Back to this G350 Issue.
I just log into most of my GW and here is a list of it.
with FWVersion,HWV-HWS for G350 and HWV-HWS MM314.
So far most of my problem i had was MM314 that prevent GW to boot. I even got one, Site 25 Kingston (3-C) was working fine in my lab (I am provision then in LAB) and i ship it to site and my tech could not get the dam GW to work, so over the phone i told him to stick out the MM314 and the GW boot up properly and register right away. So it ship another MM314 for replacement from my spare stock. Once i got the blade back i had 3 G350 in LAB being Provisionned and the Kingston blade never worked in any of 3 GW which were also (3-C). SO could it be the MM314 Blade that are the problem and not the G350?

Site Site Name FWV HWV-HWS HWV-HWS
21 Montreal Center 26.31.0 3-B 2-C
22 St-John NB 26.31.0 3-B 2-C
23 Oshawa 26.31.0 3-B 2-C
24 Acadie ahuntsic 26.31.0 3-B 2-C
25 Kingston 27.27.0 3-C 3-C
26 GTA Leaside 26.31.0 3-B 2-C
27 Burlington 26.31.0 3-B 2-C
28 Windsor 4 26.31.0 3-B 2-C
29 Niagara Falls 26.31.0 3-B 2-C
30 Sudbury 26.36.0 3-B 1-C
31 ThunderBay 26.31.0 3-B 2-C
32 Sault-Ste-Marie 26.31.0 3-B 2-C
33 Halifax 27.27.0 3-B 2-C
34 Fredericton 26.31.0 3-B 2-C
35 Brampton 27.27.0 3-B 2-C
36 Edmonton NW 27.27.0 3-C 3-C
37 Laval West 27.27.0 3-B 2-C
38 Kitchener 27.27.0 3-C 3-C
39 Peterborough 27.27.0 3-C 2-C
40 Hamilton 27.27.0 3-C 2-C
41 Calgary J-Hunt 26.44.0 3-C 2-C
42 St-Hubert 26.44.0 3-C 2-C
43 Thornhill 26.31.0 3-C 2-C
44 Cambridge 27.27.0 3-C 2-C
45 Waterloo 27.31.0 3-C 2-C
46 Oakville 27.27.0 3-C 3-C
47 Gatineau 2 26.44.0 3-C 2-C
48 Quebec 26.44.0 3-C 3-C
49 Stoney Creek 26.31.0 3-C 2-C
50 Pickering 27.27.0 3-C 2-C
51 Ajax 27.27.0 3-C 2-C
52 GTA GS MDeBlas 27.27.0 3-C 2-C
53 GTA JQ 27.27.0 3-C 2-C
54 Sudbury 2 27.27.0 3-C 2-C
55 Windsor 2 26.31.0 3-C 2-C
56 Richmond Hill 27.27.0 3-C 2-C
57 London 2 27.27.0 3-C 2-C
58 Medicine Hat 26.44.0 2-B n/a
59 Sherbrooke 26.44.0 2-B n/a
60 Belleville 26.44.0 2-B n/a
61 Guelph 27.27.0 3-B 2-C
63 Calgary NE 27.27.0 3-C 3-C
65 Windsor 3 27.27.0 3-B 2-C
66 Red Deer 27.27.0 3-B 2-C
67 Edmonton SE 27.27.0 3-B 2-C
68 Dartmouth 27.27.0 3-C 3-C
71 Gloucester 27.27.0 3-C 3-C
72 Windsor 27.27.0 3-B 3-C
74 GTA CP 27.27.0 3-C 2-C
75 Cornwall 26.44.0 2-B n/a
77 Vaughan 27.27.0 3-C 3-C
79 North Bay 26.44.0 4-B n/a
81 London 3 27.27.0 3-C 3-C

Also the only GW i have send so far were DCHP problem.

i have another problem that just started a couple week ago
GW is registered to main site and IP Phone can make call but not talkpath. Also autoattendant via local PRI get dead air not annoucement played. I telnet in the GW while in trouble and found (sh voip) that Voip engine was falty and showed no resources. I reset the GW and it went back to normal. VOIP firm was at 74 i brought it up to 76. But it failed again today. G350 at 27.31.0 3-C and MM314 at 2-C. Did you ever had this problem before.
Also we got another site that the VOIP engine disappeared today. This site is #26 G350 at 26.31.0 3-B and MM314 at 2-C
I really dont know where to hit this time. Should i replace the G350, could it be the dam MM314 that is causing this. I will upgrade the Firmware to 27.31.0 and Voip to latest tonite....

Daniel