• May 21, 2012, 08:08:56 AM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: ERS 5500 v6.2+ EDM Bugs  (Read 1753 times)

0 Members and 2 Guests are viewing this topic.

Offline int21h

  • Rookie
  • **
  • Posts: 15
Re: ERS 5500 v6.2+ EDM Bugs
« Reply #15 on: August 16, 2011, 09:01:11 PM »
You can use JDM to connect to switches running 6.2. You receive a popup message saying that you are using old version of JDM with new switch code. However you can still view the switch and click through settings, BUT some configuration items have changed and JDM displays them as red and unpopulated. Therefore I have not been game enough to make changes using JDM.


Offline int21h

  • Rookie
  • **
  • Posts: 15
Re: ERS 5500 v6.2+ EDM Bugs
« Reply #16 on: August 18, 2011, 01:40:36 AM »
I thought I would provide you an update on where I am with Avaya support and share some of my frustration.

Firstly, the problem where the VLAN popup port selection doesn't appear, relates to the port members column width. If you have XX (i haven't identified exact number)  number ports selected on a VLAN, the cloumn width automatically expands to show you all of the port details, which breaks the popup window. The good news, you can fix this by resizing this column to a shorter width, however these changes will be lost once you logout.

Now to the frustration part. Avaya Support said that they only support IE7 and Firefox 3.0, and so if you experience any problems when using any other version of IE or FireFox, they can not help because you are using unsupported software. This seems like a major cop-out considering we are talking about switch code released in August 2011 and IE8 was released in March 2009, and it's still not supported.

Long story short, I was able to replicate the same problem on IE7 in both production and alab environment. Thankfully the Avaya support person was able to witness this first hand and they will now raise it up to the next support level.

With regards to the delay with CLI, I can confirm the same hardware and config on version 6.1.x doesn't have this issue. Nor do our stacks of 5650-TD running 6.2.x. This problem only appears on 5510/5520 hardware running 6.2.x To me this points to the hardware on 5510/5520 is not adequate to run v6.2.

Ok so why am I complaining here ?
We are in the process of deploying  Cisco infrastructure to support approxmiately 5000 Cisco handsets. We want to deploy v6.2 to take advantage of the improvements to ADAC & LLDP. Our infrastructure consists of over 300 5510/5520s, so it is important that this code works on 5510/5520.
At the moment we're not getting much assistance from Avaya and I'm hoping that the more I make other customers aware of the bugs, the more chance we have at getting these bugs fixed.