PhonesAllDay
Technical User
I have two G450's Firmware upgraded and booted on both banks as follows: 36.18.0 -> 37.41.0 ->38.21.2 -> 39.20.0
Loading AVP 7.0, once EULA is accepted, G450 faults with Insertion Failure.
The other G450 is in production with S8300E with AVP version 7.1.3, (upgraded first to 7.0, then 7.1.2...) was restarted several times during power outages and showing Insertion Failure.
Re-seating, downgrading/upgrading G450 firmware, restarting, changing boot banks, re-loading AVP, nothing works and this can be repeated every time. Show MM, the board is "Initializing"
Connecting directly to AVP via services port works just fine.
Avaya sent a document that this is a known issue with fix scheduled in AVP release 7.1.4
Their document states: "same issue in the lab on S8300 D and E on AVP 7.1.0, 7.1.2, 7.1.3 and 7.1.3.2 and on gateway firmware G450 39.12.0, G430 38.20.1, G450 on 38.21.1. I have tired on on other combinations".
Avaya said this is a workaround which I haven't got to work successfully yet: kill -9 `pidof watchd` && /etc/init.d/watchd start
I'm wondering if anyone else is experiencing this, or found a fix?
Thanks,
PhonesAllDay
(and AllNight)
Loading AVP 7.0, once EULA is accepted, G450 faults with Insertion Failure.
The other G450 is in production with S8300E with AVP version 7.1.3, (upgraded first to 7.0, then 7.1.2...) was restarted several times during power outages and showing Insertion Failure.
Re-seating, downgrading/upgrading G450 firmware, restarting, changing boot banks, re-loading AVP, nothing works and this can be repeated every time. Show MM, the board is "Initializing"
Connecting directly to AVP via services port works just fine.
Avaya sent a document that this is a known issue with fix scheduled in AVP release 7.1.4
Their document states: "same issue in the lab on S8300 D and E on AVP 7.1.0, 7.1.2, 7.1.3 and 7.1.3.2 and on gateway firmware G450 39.12.0, G430 38.20.1, G450 on 38.21.1. I have tired on on other combinations".
Avaya said this is a workaround which I haven't got to work successfully yet: kill -9 `pidof watchd` && /etc/init.d/watchd start
I'm wondering if anyone else is experiencing this, or found a fix?
Thanks,
PhonesAllDay
(and AllNight)