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

Avaya G450 freezing

Status
Not open for further replies.
FXLL

FXLL

Technical User
Joined
May 10, 2016
Messages
24
Location
US
Hi All,

I have two Avaya G450 that are freezing randomly.

They have the below firmware versions:
34 .5 .1 /1
34 .5 .0 /1

When the Local IT goes to the server room, he see the G450 powered on but not responding neither using the console/service port.
They needs to be power cycled to have them back.

They have been having this behavior for the last week.

This is the only that we get once it's rebooted:

<190>Dec 31 09:58:57 AZSTZ04L1-CMI09 -NoTag: -NoUTC 2016 055 1 mediagateway.g450 | 0 coldStart[BOOT-Informational: System boot up from cold reset, ID=7001004001


Do you have any idea of what could be causing this?

Here the boards installed on each one:

MG #2

002V1 DS1 MM MM710BP HW16 FW052
002V2 DS1 MM MM710BP HW16 FW053
002V3 DS1 MM MM710BP HW16 FW052
002V4 DS1 MM MM710BP HW16 FW052
002V5 ANA MM MM716AP HW12 FW098
002V6 ANA MM MM716AP HW12 FW095
002V7 DS1 MM MM710BP HW16 FW052
002V8 DS1 MM MM710BP HW11 FW053
002V9 MG-ANNOUNCEMENT VMM-ANN

MG #3 (THIS ONE IS CURRENTLY FREEZE)

003V6 DS1 MM no board
003V8 ANA MM no board
003V9 MG-ANNOUNCEMENT no board
 
Sort by date Sort by votes
I would suggest upgrading your gateway firmware. The 34.5.1 software is from 2013 and was from the CM6.3.2 timeframe. You should be on at least CM6.3.11.1 which would also include gateway firmware 36.18.0.
 
Upvote 0 Downvote
Thank you jimbojimbo.

There is a document with the release dates and Firmware relationship with the CM version?

Thanks in Advance.
 
Upvote 0 Downvote
I would also look at your network region. Make sure that the 2 remote locations are not part of the same NR as the main site, and that there is an intervening region. Otherwise the system might be using all of the DSP resources out of the remote site. I have seen that lock up a remote gateway before.
 
Upvote 0 Downvote
Thank you DAVIDPAYNE,

Both MG are in a different NR than the Main Location.

Thanks in Advance-
 
Upvote 0 Downvote
Do both freeze at the same time? I'd look at power.
 
Upvote 0 Downvote
Thank you PhonesAllDay, I'll check this link right away,

kyle555 the gateways freeze at different times,

ie.

MG #2 was freeze 12/26 12/30 and 01/03
MG #3 was freeze 12/22 12/24 12/30 and 01/01

Kind Regards-
 
Upvote 0 Downvote
Maybe check /var/logs/ecs in CM at that time to see if anything CM related caused it beyond CM just seeing a link dropped.
 
Upvote 0 Downvote
Here what I have from the CM logs


sysadm@MainCM> egrep -R "MG=#" 2016-122*
2016-1221-192638.log:20161222:043921181:20511591:capro(10532):MED:[ConnClosed: MG=#3 disconnected: socket closure, moved to link-bounce state¦: near_ipaddr = 10.5.5.22, far_ipaddr = 10.6.5.36 actIntf 2]
2016-1222-135558.log:20161222:150802879:20531114:capro(10532):MED:[mgRegister MG=#3 First attempt to return to main from LSP]
2016-1222-135558.log:20161222:233806118:20537586:capro(10532):MED:[ConnClosed: MG=#2 disconnected: socket closure, moved to link-bounce state¦: near_ipaddr = 10.5.5.22, far_ipaddr = 10.6.5.29 actIntf 2]
2016-1223-101633.log:20161223:113058524:20548153:capro(10532):MED:[mgRegister MG=#2 First attempt to return to main from LSP]
2016-1223-101633.log:20161223:113302802:20548191:capro(10532):MED:[mgRegister MG=#2 First attempt to return to main from LSP]
2016-1223-101633.log:20161223:113609282:20548294:capro(10532):MED:[mgRegister:re-registration by existing MG. Connection will be deleted and registration re-issued, MG=#2]
2016-1224-041315.log:20161224:110857160:20595608:capro(10532):MED:[ConnClosed: MG=#3 disconnected: socket closure, moved to link-bounce state¦: near_ipaddr = 10.5.5.22, far_ipaddr = 10.6.5.36 actIntf 2]
2016-1224-183716.log:20161224:210933161:20607694:capro(10532):MED:[ConnClosed: MG=#2 disconnected: socket closure, moved to link-bounce state¦: near_ipaddr = 10.5.5.22, far_ipaddr = 10.6.5.29 actIntf 0]
2016-1224-183716.log:20161224:211219168:20607914:capro(10532):MED:[ConnClosed: MG=#2 disconnected: socket closure, moved to link-bounce state¦: near_ipaddr = 10.5.5.22, far_ipaddr = 10.6.5.29 actIntf 0]
2016-1225-080059.log:20161225:105900020:20629627:capro(10532):MED:[ConnClosed: MG=#2 disconnected: socket closure, moved to link-bounce state¦: near_ipaddr = 10.5.5.22, far_ipaddr = 10.6.5.29 actIntf 0]
2016-1225-114354.log:20161225:114421898:20630561:capro(10532):MED:[ConnClosed: MG=#2 disconnected: socket closure, moved to link-bounce state¦: near_ipaddr = 10.5.5.22, far_ipaddr = 10.6.5.29 actIntf 0]
2016-1225-114354.log:20161225:121407383:20631359:capro(10532):MED:[ConnClosed: MG=#2 disconnected: socket closure, moved to link-bounce state¦: near_ipaddr = 10.5.5.22, far_ipaddr = 10.6.5.29 actIntf 0]
2016-1225-114354.log:20161225:163843243:20636680:capro(10532):MED:[ConnClosed: MG=#2 disconnected: socket closure, moved to link-bounce state¦: near_ipaddr = 10.5.5.22, far_ipaddr = 10.6.5.29 actIntf 0]
2016-1225-232109.log:20161226:034903423:20651959:capro(10532):MED:[ConnClosed: MG=#2 disconnected: socket closure, moved to link-bounce state¦: near_ipaddr = 10.5.5.22, far_ipaddr = 10.6.5.29 actIntf 0]
2016-1225-232109.log:20161226:072056121:20655754:capro(10532):MED:[ConnClosed: MG=#2 disconnected: socket closure, moved to link-bounce state¦: near_ipaddr = 10.5.5.22, far_ipaddr = 10.6.5.29 actIntf 0]
2016-1226-202422.log:20161226:212838094:20673925:capro(10532):MED:[ConnClosed: MG=#2 disconnected: socket closure, moved to link-bounce state¦: near_ipaddr = 10.5.5.22, far_ipaddr = 10.6.5.29 actIntf 0]


sysadm@MainCM> egrep -R "MG=#" 2017-010*
2017-0101-020619.log:20170101:035240125:20887407:capro(10532):MED:[ConnClosed: MG=#3 disconnected: socket closure, moved to link-bounce state¦: near_ipaddr = 10.5.5.22, far_ipaddr = 10.6.5.36 actIntf 2]
2017-0102-145716.log:20170102:155357463:20944694:capro(10532):MED:[mgRegister MG=#3 First attempt to return to main from LSP]
2017-0103-101438.log:20170103:104309931:21035535:capro(10532):MED:[ConnClosed: MG=#2 disconnected: socket closure, moved to link-bounce state¦: near_ipaddr = 10.5.5.22, far_ipaddr = 10.6.5.29 actIntf 0]



sysadm@MainCM> egrep -i mgreg 2016-122*
2016-1222-135558.log:20161222:150802879:20531114:capro(10532):MED:[mgRegister MG=#3 First attempt to return to main from LSP]
2016-1222-135558.log:20161222:151047896:20531164:capro(10532):MED:[mgRegister:success MG#=3, MG_G450, Ipif=0x1, SerialNum=13TG25180305, HW Vintage=1, FW ver=34.5.0]
2016-1222-135558.log:20161222:151047896:20531165:capro(10532):MED:[mgRegister:IPV4addr 10.6.5.36]
2016-1222-135558.log:20161222:151047896:20531166:capro(10532):MED:[mgRegister:IPV6addr 0.0.0.0]
2016-1222-135558.log:20161222:151047896:20531167:capro(10532):MED:[mgRegister:success MG Restart type=MG_RETURNS_FRM_LSP, action=LINK_UP_CNPR]
2016-1223-101633.log:20161223:113058524:20548153:capro(10532):MED:[mgRegister MG=#2 First attempt to return to main from LSP]
2016-1223-101633.log:20161223:113302802:20548191:capro(10532):MED:[mgRegister MG=#2 First attempt to return to main from LSP]
2016-1223-101633.log:20161223:113609282:20548294:capro(10532):MED:[mgRegister:re-registration by existing MG. Connection will be deleted and registration re-issued, MG=#2]
2016-1223-101633.log:20161223:113609818:20548295:capro(10532):MED:[mgRegister:success MG#=2, MG_G450, Ipif=0x1, SerialNum=14TG20647119, HW Vintage=1, FW ver=34.5.1]
2016-1223-101633.log:20161223:113609818:20548296:capro(10532):MED:[mgRegister:IPV4addr 10.6.5.29]
2016-1223-101633.log:20161223:113609818:20548297:capro(10532):MED:[mgRegister:IPV6addr 0.0.0.0]
2016-1223-101633.log:20161223:113609818:20548298:capro(10532):MED:[mgRegister:success MG Restart type=MG_DISC_WARM_BOOT, action=LINK_UP_CNPR]
2016-1224-183716.log:20161224:210951636:20607854:capro(10532):MED:[mgRegister:success MG#=2, MG_G450, Ipif=0x1, SerialNum=14TG20647119, HW Vintage=1, FW ver=34.5.1]
2016-1224-183716.log:20161224:210951637:20607855:capro(10532):MED:[mgRegister:IPV4addr 10.6.5.29]
2016-1224-183716.log:20161224:210951637:20607856:capro(10532):MED:[mgRegister:IPV6addr 0.0.0.0]
2016-1224-183716.log:20161224:210951637:20607857:capro(10532):MED:[mgRegister:success MG Restart type=MG_DISC_WARM_BOOT, action=LINK_CNPR_LB]
2016-1224-183716.log:20161224:211332196:20607926:capro(10532):MED:[mgRegister:success MG#=2, MG_G450, Ipif=0x1, SerialNum=14TG20647119, HW Vintage=1, FW ver=34.5.1]
2016-1224-183716.log:20161224:211332196:20607927:capro(10532):MED:[mgRegister:IPV4addr 10.6.5.29]
2016-1224-183716.log:20161224:211332196:20607928:capro(10532):MED:[mgRegister:IPV6addr 0.0.0.0]
2016-1224-183716.log:20161224:211332196:20607929:capro(10532):MED:[mgRegister:success MG Restart type=MG_DISC_WARM_BOOT, action=LINK_CNPR_LB]
2016-1225-080059.log:20161225:110003848:20629646:capro(10532):MED:[mgRegister:success MG#=2, MG_G450, Ipif=0x1, SerialNum=14TG20647119, HW Vintage=1, FW ver=34.5.1]
2016-1225-080059.log:20161225:110003848:20629647:capro(10532):MED:[mgRegister:IPV4addr 10.6.5.29]
2016-1225-080059.log:20161225:110003849:20629648:capro(10532):MED:[mgRegister:IPV6addr 0.0.0.0]
2016-1225-080059.log:20161225:110003849:20629649:capro(10532):MED:[mgRegister:success MG Restart type=MG_DISC_WARM_BOOT, action=LINK_CNPR_LB]
2016-1225-114354.log:20161225:114543924:20630592:capro(10532):MED:[mgRegister:success MG#=2, MG_G450, Ipif=0x1, SerialNum=14TG20647119, HW Vintage=1, FW ver=34.5.1]
2016-1225-114354.log:20161225:114543924:20630593:capro(10532):MED:[mgRegister:IPV4addr 10.6.5.29]
2016-1225-114354.log:20161225:114543924:20630594:capro(10532):MED:[mgRegister:IPV6addr 0.0.0.0]
2016-1225-114354.log:20161225:114543924:20630595:capro(10532):MED:[mgRegister:success MG Restart type=MG_DISC_WARM_BOOT, action=LINK_CNPR_LB]
2016-1225-114354.log:20161225:121447964:20631381:capro(10532):MED:[mgRegister:success MG#=2, MG_G450, Ipif=0x1, SerialNum=14TG20647119, HW Vintage=1, FW ver=34.5.1]
2016-1225-114354.log:20161225:121447964:20631382:capro(10532):MED:[mgRegister:IPV4addr 10.6.5.29]
2016-1225-114354.log:20161225:121447964:20631383:capro(10532):MED:[mgRegister:IPV6addr 0.0.0.0]
2016-1225-114354.log:20161225:121447964:20631384:capro(10532):MED:[mgRegister:success MG Restart type=MG_DISC_WARM_BOOT, action=LINK_CNPR_LB]
2016-1225-114354.log:20161225:163928950:20636800:capro(10532):MED:[mgRegister:success MG#=2, MG_G450, Ipif=0x1, SerialNum=14TG20647119, HW Vintage=1, FW ver=34.5.1]
2016-1225-114354.log:20161225:163928950:20636801:capro(10532):MED:[mgRegister:IPV4addr 10.6.5.29]
2016-1225-114354.log:20161225:163928950:20636802:capro(10532):MED:[mgRegister:IPV6addr 0.0.0.0]
2016-1225-114354.log:20161225:163928950:20636803:capro(10532):MED:[mgRegister:success MG Restart type=MG_DISC_WARM_BOOT, action=LINK_CNPR_LB]
2016-1225-183921.log:20161225:185829115:20639984:capro(10532):MED:[mgRegister MG=#4 First attempt to return to main from LSP]
2016-1225-232109.log:20161226:034944463:20651970:capro(10532):MED:[mgRegister:success MG#=2, MG_G450, Ipif=0x1, SerialNum=14TG20647119, HW Vintage=1, FW ver=34.5.1]
2016-1225-232109.log:20161226:034944463:20651971:capro(10532):MED:[mgRegister:IPV4addr 10.6.5.29]
2016-1225-232109.log:20161226:034944463:20651972:capro(10532):MED:[mgRegister:IPV6addr 0.0.0.0]
2016-1225-232109.log:20161226:034944463:20651973:capro(10532):MED:[mgRegister:success MG Restart type=MG_DISC_WARM_BOOT, action=LINK_CNPR_LB]
2016-1225-232109.log:20161226:072149897:20655766:capro(10532):MED:[mgRegister:success MG#=2, MG_G450, Ipif=0x1, SerialNum=14TG20647119, HW Vintage=1, FW ver=34.5.1]
2016-1225-232109.log:20161226:072149897:20655767:capro(10532):MED:[mgRegister:IPV4addr 10.6.5.29]
2016-1225-232109.log:20161226:072149897:20655768:capro(10532):MED:[mgRegister:IPV6addr 0.0.0.0]
2016-1225-232109.log:20161226:072149897:20655769:capro(10532):MED:[mgRegister:success MG Restart type=MG_DISC_WARM_BOOT, action=LINK_CNPR_LB]
2016-1226-202422.log:20161226:212939556:20673935:capro(10532):MED:[mgRegister:success MG#=2, MG_G450, Ipif=0x1, SerialNum=14TG20647119, HW Vintage=1, FW ver=34.5.1]
2016-1226-202422.log:20161226:212939556:20673936:capro(10532):MED:[mgRegister:IPV4addr 10.6.5.29]
2016-1226-202422.log:20161226:212939556:20673937:capro(10532):MED:[mgRegister:IPV6addr 0.0.0.0]
2016-1226-202422.log:20161226:212939556:20673938:capro(10532):MED:[mgRegister:success MG Restart type=MG_DISC_WARM_BOOT, action=LINK_CNPR_LB]


sysadm@MainCM> egrep -i mgreg 2017-010*
2017-0102-145716.log:20170102:155357463:20944694:capro(10532):MED:[mgRegister MG=#3 First attempt to return to main from LSP]
2017-0102-145716.log:20170102:155657460:20944933:capro(10532):MED:[mgRegister:success MG#=3, MG_G450, Ipif=0x1, SerialNum=13TG25180305, HW Vintage=1, FW ver=34.5.0]
2017-0102-145716.log:20170102:155657460:20944934:capro(10532):MED:[mgRegister:IPV4addr 10.6.5.36]
2017-0102-145716.log:20170102:155657460:20944935:capro(10532):MED:[mgRegister:IPV6addr 0.0.0.0]
2017-0102-145716.log:20170102:155657460:20944936:capro(10532):MED:[mgRegister:success MG Restart type=MG_RETURNS_FRM_LSP, action=LINK_UP_CNPR]
2017-0103-101438.log:20170103:104510864:21036181:capro(10532):MED:[mgRegister:success MG#=2, MG_G450, Ipif=0x1, SerialNum=14TG20647119, HW Vintage=1, FW ver=34.5.1]
2017-0103-101438.log:20170103:104510864:21036182:capro(10532):MED:[mgRegister:IPV4addr 10.6.5.29]
2017-0103-101438.log:20170103:104510864:21036183:capro(10532):MED:[mgRegister:IPV6addr 0.0.0.0]
2017-0103-101438.log:20170103:104510864:21036184:capro(10532):MED:[mgRegister:success MG Restart type=MG_DISC_WARM_BOOT, action=LINK_UP_CNPR]
 
Upvote 0 Downvote
Judging by those logs, and not knowing exactly what time they froze, I'd say you have some sort of network or software mismatch problem. What patch load of CM are you running?

How are they both in the same subnet but doing LSP recovery at different times?
2016-1222-135558.log:20161222:150802879:20531114:capro(10532):MED:[mgRegister MG=#3 First attempt to return to main from LSP]

Wouldn't you expect MG2 and 3 to have stuff like that at the same time? Are their MGC lists, transition points, primary/total search and recovery rules all lined up?

Generally after one of these:
2016-1223-101633.log:20161223:113609818:20548298:capro(10532):MED:[mgRegister:success MG Restart type=MG_DISC_WARM_BOOT, action=LINK_UP_CNPR]
You'd immediately see the reregistration

2016-1224-183716.log:20161224:211332196:20607929:capro(10532):MED:[mgRegister:success MG Restart type=MG_DISC_WARM_BOOT, action=LINK_CNPR_LB]
2016-1225-080059.log:20161225:110003848:20629646:capro(10532):MED:[mgRegister:success MG#=2, MG_G450, Ipif=0x1, SerialNum=14TG20647119, HW Vintage=1, FW ver=34.5.1]

Why those two lines above have such a gap - presumably during the freeze and need to reboot them, that's odd.

Is layer 2 half duplex anywhere or is signaling h248 qos dropped over a WAN or something? That, or CM patch load not lining up with gateway firmware? Best I can guess.


 
Upvote 0 Downvote
You might also want to go into the gateway and run 'show logging file content'.
 
Upvote 0 Downvote
From the last issues I found this Denial Error in the CM logs


20170103:104309930:21035533:capro(10532):MED:[ DENYEVT ERR event=2055 d1=0002 d2=71323024]
20170103:104309930:21035534:hmm(10527):MED:[ MTCEVT ERR type=0321 lname=5400 pn1=00000807 pn2=00000002 aux=71323024 rc=0]
20170103:104309931:21035535:capro(10532):MED:[ConnClosed: MG=#2 disconnected: socket closure, moved to link-bounce state›: near_ipaddr = 10.5.5.22, far_ipaddr = 10.6.5.29 actIntf 0]
20170103:104309931:21035536:hmm(10527):MED:[ MTCEVT ERR type=0301 lname=1424 pn1=00000000 pn2=00000002 aux=00000000 rc=0]

20170104:193817240:21089045:capro(10532):MED:[ DENYEVT ERR event=2055 d1=0002 d2=71322c6c]
20170104:193817240:21089046:hmm(10527):MED:[ MTCEVT ERR type=0321 lname=5400 pn1=00000807 pn2=00000002 aux=71322c6c rc=0]
20170104:193817240:21089047:hmm(10527):MED:[ MTCEVT ERR type=0301 lname=1424 pn1=00000000 pn2=00000002 aux=00000000 rc=0]
20170104:193817240:21089048:capro(10532):MED:[ConnClosed: MG=#2 disconnected: socket closure, moved to link-bounce state›: near_ipaddr = 10.5.5.22, far_ipaddr = 10.6.5.29 actIntf 0]
20170104:193817244:21089049:mdm(10563):MED:[ MTCEVT ALM type=0003 lname=1424 pname=00000002 cbusy=0000 filt=w]
 
Upvote 0 Downvote
Our vendor recommended to upgrade the firmware to the version 36.8.0.

I updated the firmware yesterday night and I'm monitoring the MGs.

As per the Network Team no issues were found in their side.
 
Upvote 0 Downvote
Thank you All,

After upgrade the firmware to 36.8.0 no more issues has been reported.
Both MGs remains stable and with no Errors/Alarms on them.

Seems like this issue was resolved by the upgrade.

Thanks.
 
Upvote 0 Downvote
There has been 8 days without issues reported,

Seems like the firmware upgrade was the solution.
Thank you All,

Kind Regards-
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

T
  • Locked
  • Question Question
Avaya G450 with ACCM
Replies
2
Views
566
nutrinoman
nutrinoman
R
  • Locked
  • Question Question
G450 Analog-test command
Replies
0
Views
519
Red19
R
hunterrob
  • Locked
  • Question Question
Avaya EM200 removal
Replies
3
Views
490
dialtonebone
dialtonebone
BIS
  • Locked
  • Question Question
Avaya Infinity
Replies
1
Views
537
gnesvik
gnesvik
Saltylad
  • Locked
  • Question Question
Avaya Workplace
Replies
2
Views
546
SouthernKnight
SouthernKnight

Part and Inventory Search

Sponsor

Back
Top