ers5000 v6.0.0.13 diag pulled off support.avaya.com (BUG)

[Paul L]

I guess this news slipped under the radar.  but today I noticed that v6.0.0.13 got pulled off the avaya support site today.

quote "A problem has been found in the diag changes made for NEBS compliance. As a result, the Diagnostic Image (5xxx_60013_diags.bin) is being taken offline until the issue is resolved and a replacement diag image is available. This affects the 6.2.3 and 6.2.2 releases. Please use the Diagnostic Image (5xxx_60010_diags.bin) from the 6.2.1 release."

now with my limited knowledge of NEBS compliance. Its my understanding that NEBS only pertains to Carriers and CO based Networks. And its only a voluntary compliance.  So I am unsure how this would affect enterprise or "normal" networks.  but the fact remains, the problem was big enough that avaya pulled it off the site. 

any thoughts? 

[mohan]

hi all,

Just to update all you guys we have done the following testing

diags:--5xxx_60013_diags.bin  ;   image:--  5xxx_622025s.img.

the switch used for testing is 5698 TFD-PWR

Autonegotiation is enabled at both switch side and laptop everything works fine.
Auto neg disabled on switch side and hard coded 1000 full on switch side and laptop, link never came up.
Auto neg enabled on switch side and hard coded 1000 full on laptop, everything works fine.
Auto neg disabed on switch side and hard coded 100 full on switch side and laptop,everything works fine.

We have repeated the same testing by changing the image to 5xxx_623011s.img.
results are same as above.

Case 2:--

diags:---  5xxx_60009_diags.bin   img:--- 5xxx_612029s.img.
Same switch
Every combination in the above test works fine.

[Paul L]

the switch will work fine.  don't worry.

NEBS compliance has to do mostly with Environmental controls and noise.

http://en.wikipedia.org/wiki/Network_Equipment-Building_System

 

[mohan]

All the other features are working fine.As we have upgraded a switch in server farm,we have faced this auto neg problem,later we replaced the server farm stack with previous versions switches to support auto neg problems.

[Paul L]

good to know   .   thanks 

[Michael McNamara]

Thanks for sharing @Paul and thanks for the additional information @mohan

[Dominik]

After some research I finally could figure out why the DIAG 6.0.0.13 was pulled from the Avaya Support side.
There is an issue with the ERS5632FD, that you can transform into a very expensive brick with the DIAG 6.0.0.13 and some reboots.
For more details check the Product Correction Notice #1817P.

I was lucky, 4 ERS5632FD with that DIAG in production doenīt have done any reboots on these machines so far.
Update to DIAG 6.0.0.14 is recommanded immediatly.

Cheers

[int21h]

@mohan, we have replicated that bug (auto-negotiation) and logged it with Avaya some time ago, but we were told that this was 'by design' and not a bug.
Have you had any sucess in logging it as a bug and is it related to the PCN v6.0.0.13 diag ?
I will run the same tests on ERS5500 running v6.0.0.14 diag and see if it has been fixed.

A minor gripe, we bricked 2x 5632's and sent them back as DOA at the start of October. However, we weren't aware of this problem until a couple of days ago when we read about it here. Even though the PCN is dated 23/9/2011, we never heard anything back from Avaya/Support until we raised the PCN with them yesterday.
I feel that there is some internal communication problems with Avaya, if their support/warranty personell are not being notified of such PCN's in adequate time.

To end my rant, we still have not received replacements for our 5632's that were logged as DOA 3+ weeks ago.

[mohan]

hi ,
Very sorry for the late reply.I was in a holiday due to festive season in india.

In order to disable autoneg and to enable 1000 full we have configured like this:-
1.Go to interface configuration.
2.speed 1000,Duplex full
However the actual config as per avaya is
1.Go to interface configuration
2.auto-negotiation-advertisements 1000-full.
This config actually served our requirement as at server side it's hardcoded as 1000-full.
Previously we are using a switch with
diags:---  5xxx_60009_diags.bin   img:--- 5xxx_612029s.img. In this switch we used to configure speed 1000 and duplex full and we did not get any problems.The same switch is upgraded to diags:--5xxx_60013_diags.bin  ;   image:--  5xxx_622025s.img. then with the same above config ,we have faced problems that server port will not come up.

We were told to use auto-negotiation-advertisements 1000-full to get the link up.