Avaya IP Office 500V2 on 9.1.5 issue with DS16B System not seeing the module

[MightyRed]

Hi All

We have recently upgraded an Avaya IP Office 500 V1 to an Avaya IP Office 50 V2.

We used the original internal cards from the V1, so I had to create the config offline on 9.1.1.0 in our office before going to site. Then once the cards had been moved across to the V2 system, the config was uploaded on to the Avaya IP Office 500 V2 on site. All the internal cards work fine, the embedded VM works ok and the phones are working ok. But when we connect the DS16B, the IP Office does not see the module. We have upgraded the IPO to 9.1.5.145 but still the system will not see the module. We have tried 2 different DS16B modules and the same issue. The engineer on site has even tried to DTE into the module and try to force it to upgrade but still no luck. The DS16B light just keeps flashing green and our engineer has been to site 3 times now.

The licence on the system is an Essential Normal edition.

We have spoken to our Tech Support company and all they can suggest now is to setup a complete system in our office with a DS16B, then program it from scratch and take it all to site.

Has any one got any ideas?

thanks

Phil

 

[derfloh]

It is not disabled due to a small site upgrade license?

 

[intrigrant]

The IP Office has eight expansion slots shown in manager as device 6 to 14.
Is there another card type in the config of IP Office programmed?
In Manager select "systemunit" to see the programmed devices.
Try to connect the module to a unprogrammed slot, reboot IP Office and see what happens using monitor.

 

[joe2938]

It that ds16 module was a v1 would it work on a v2 ip office? does he need a v2 ds16 module now?

 

[MightyRed]

derfloh - The system was already on 9.1.1 when we got it and we just bought the Essential Edition licence so we could change from Basic to Standard. The licence says it is a normal licence, surely you only need the large site upgrade licence if you were upgrading from a lower software version.

Joe2938 - I haven't been on site myself, so I will have to check with the other engineer to see if he has tried more than one expansion port. The DS16B will work with IPO 500V2 on 9.1 so should be ok, but we have tried 2 units and no luck.

intrigant - In the Control unit section of Manager you don't see the DS16B and if you try to upgrade the IPO, you don't get the chance to upgrade the DS16B either. I did set the first expansion slot for a DS16 V2 on the offline config by accident, but have since deleted that and rebooted the system.

Cheers

 

[intrigrant]

Initially when you start up a IP Office 500v2 with a new DSxB unit then the system does not show that module anywere, wait approx fifteen minutes and re-open the config, by then the unit shoud have loaded the software and must be up and running and only then it is visible in Manager or System Status.
The old type modules would show up directly, changing the behaviour of things is a bad idea, especially if it is not documented. Typical Avaya....

 

[MightyRed]

Hi intrigant

The DS16B is still connected to the system and our engineer left site on Monday. We still can't see the module, so not sure what is going on.

When he first connected the DS16B he left it for over an hour and nothing happened. He has spoken to Scansource but even with their help he can't get it working.

Cheers

 

[amriddle01]

Just to be clear, you have removed the reference to the incorrect module.
And powered down the system, connected the DS module to the system and powered that up first
Then after 20-30 secs powered up the IP Office and left it without doing anything for at least 30 mins

 

[MightyRed]

Thank you for joining the thread amriddle01

Yes I removed the reference for the DS16 V2 remotely after our engineers first visit and rebooted the system, this was whilst the first DS16B was connected. Since then our engineer has been to site and disconnected the first DS16B, powered up a second DS16B, connected it to the expansion module ports and then rebooted the IPO 500V2 and the second DS16B is still connected to the system now.

He has confirmed he has tried several expansion ports on the system.

Cheers

 

[amriddle01]

Getting expansion modules to synch has been getting worse and worse with every release since R7.
And with new hardware thrown in I'm not surprised Avaya has made it as difficult to achieve as what Richard Pryor had to do with the 2 computer keys in Superman 3

I would be tempted to try a different chassis with a fresh config just to see if it comes up, that will reveal it's a corrupt config, expansion module or faulty chassis causing issues

 

[MightyRed]

Yes that is what Scansource have said now.

We need to set up a IPO 500V2 system in the office and connect the DS16B to it. Once the system can see the DS16B, we need to reprogram and then take all the hardware to site.

 

[MightyRed]

We connected the DS16B to an IPO500V2 in our office and we experienced exactly the same issue.

When we connect an IP400 DS30V2 to the same system using the same network cable, the system sees the unit and the unit upgrades to the software on the IPO500V2.

So there is definitely an issue with the DS16B units.