Strange R11 Issue with DS30B Mods 2

[DTGMI]

Have a project that is running C2 Control unit successfully w/ R11.0.4.5.0 Build 3

Current config has (2) DS30B2 and (3) Phone 30 mods - runningproperly.

We are trying to add (3) more DS30B mods. they are currently at R9.1.12 and the CU recognizes them ... but won't auto upgrade them boot up?

We also tried to upgrade them manually to current R11 SW of the CU - but it fails ... Yes - we have the directories set properly as we have upgraded the Phone 30s in the past.

In the Manager screen they show up as having 9.1.12 SW but in the upgrade screen - they all (3) show R11.0.5 ... with R11.0.4.5.0 Build 3 as "Available" for upgrade?

Can't get them to upgrade properly.

DTE default process doesn't fix them. They aren't bricked ...

Any ideas?

See the attachment.

 

[budbyrd]

Did you buy them new? Older dig 30 v2 aren't supported at R11. They need to be the B version.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[DTGMI]

Bud

See above

We are trying to add (3) more DS30B mods.

 

[DTGMI]

Additionally

Per Avaya R11 Docs - IP500 DS30 Mods (original version) and IP400 DS30 V2 Mods are supported ... just read it to be sure.

We are using "b" though on this project.

 

[budbyrd]

Yeah... With 17 years of working with Avaya and over 30 years in the field... The guys who write the docs have never touched the equipment. The tier what ever guys at tech support usually have less than one years experience and are working off a script written by a guy they fired a year ago. What I do know is we have had to buy referbs for older systems. So I could be wrong. The B versions will work. It could be a matter of the boot order. Make sure to have all expansions flashing green before rebooting the chassis.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[TomMills]

That seems to be more true every year bud.

If it's not boot order as Bud suggests (they should be flashing before booting the V2 up), then what error do you get when you try to manually upgrade?

Based on the screenshot I'd be tempted to connect them to a system running a higher firmware version and seeing if they connect up properly or upgrade. I would trust the upgrade wiz over manager for getting their firmware version. Looks like they may not have connected to the system properly as they are running a higher version.

APSS/ACIS/ACSS-SME
not arrogant, just succinct.

 

[DTGMI]

Thanks Bud and Tom

We ended up just doing the emergency SW recovery process thru direct DTE port on the mod.

Took 5 min once we remembered the steps.

 

[TomMills]

So you DTE'd them onto the firmware you wanted and they came up?

APSS/ACIS/ACSS-SME
not arrogant, just succinct.

 

[DTGMI]

Correct

 

[infonaut]

Emergency SW recovery process thru direct DTE port on the mod.
Care to elaborate?

 

[Westi]

My guess is that this was the procedure for it

https://www.tek-tips.com/faqs.cfm?fid=7860

Joe
FHandw, ACSS (SME)

"Dew knot truss yore Spell Cheque