LAN problems after 3.2(17) upgrade

[jamie77]

We have upgraded an ip406v2 PCS 07 to 3.2 and now seem to be having problems with the 8 LAN ports.

This unit is only 3 months old and has only been used as a spare for rebuilding corrupt databases without any problems. It was defaulted through Manager and using AT-X2/AT-X3 after initial problems.

Manager reboots or not leaving the power off for at least 2 mins means that LAN ports lock up (anywhere between 1 and all 8 of them).

I have done lots of testing and passed the findings onto our distributor for Avaya's attention. It seems it may be a known issue.

I have had LAN ports lock up before but a reboot normally sorts it out.

Has anyone had similar issues??

Jamie Green

Fooball is not a matter of life and death-It is far more important!!!!

 

[JeSTeROCK]

I have seen LAN ports lock up when if loops occur in the network

 

[jamie77]

This was just the IPO and my laptop

Jamie Green

Fooball is not a matter of life and death-It is far more important!!!!

 

[Orlando21]

I just had the same trouble on an install I worked on. I was not sure of the exact trouble but here is the scenario. Same trouble as you with ports locking up. On that switch I went from 2.29 to 3.099 and then to 3.1.65. Everything seemed fine. Got to site and trouble started happening that was much more noticiable. If you wait approx 30 to 40 mins. after a reboot things seems fine and you can connect with manager.

I was under the gun so we got a new switch (other one was new also) this time I followed the upgrade instructions to a tee. Went from 2.1.27 to 2.1.73 to 3.0.55 to 3.0.99 to 3.1.65. I also had a V290 modem card in the mix that I left out this time as I did not need it (plans changed). I haven't tested the modem yet but I think I would believe that it is the upgrade. I had trouble doing a correct AT-X2, 3 and then Bootp. It would not erase my upgrade just default the switch. This is why I swapped the unit.

Hope this helps, I know it is a bit vague but the more info you get the more you can piece it together.

 

[jamie77]

My distibutor believes this is part of wider problem with 406v2's so this is why I did extnesive tests and DTE traces with this unit. It has now been send back.

Our unit was 406v2 PCS 07. DO you know what PCS the unit you had trouble with was??

New ones are now PCS 08.

Jamie Green

Fooball is not a matter of life and death-It is far more important!!!!

 

[superikey]

What Does PCS Mean?

Isaac Braca
CTO / ICCS & Co., LLC.
Email: braca@iccsllc.com

ICCS, Your Premier IT Partner, is a NYC Based Avaya Business Partner and IT Consulting Firm.

 

[jamie77]

hardware revision

Jamie Green

Fooball is not a matter of life and death-It is far more important!!!!

 

[superikey]

And where is this PCS indicated ont he System?

 

[jamie77]

on the sticker on the rear of the unit

Jamie Green

Fooball is not a matter of life and death-It is far more important!!!!

 

[sizbut]

PCS" = "Product Change Status" which is the hardware engineers equivalent of version number.

 

[Orlando21]

I had a PCS 09 and got a replacement 09. The trouble with my 406V2 PCS 09 was the same. I got a 09 replacement and things seem to be fine.

 

[TheDoz]

I have the Same problem. Reboot system and can'it get back in unless I wait awhile. IP Office 406v2 Ver.3.2. I had same problem with 3.1, but got worse with 3.2.
I'm replacing the 406 unit.

"A politician is a fellow who will lay down your life for his country.

 

[Orlando21]

Hey TheDoz this one is for you.

I am not sure if it was my 406v2 or if it was the upgrade. My tip is for you on this one if you get a unit pre loaded 2.1.29 use the upgrade points that I listed earlier in this session. Some might be redundant but my unit works fine. Extra cautious I suppose. I still followed the procedures with the loader version before you go to 3.1.???? And if you get something before 2.0 smack your distributor but there is a loader version upgrade there too.

Good luck

 

[NewNic]

This getting new equip with old loads in them...I just cant seem to buy into it....Ya ya....I understand it would cost them money...but it costs us as well

 

[TheDoz]

Hey Orlando21,
I think it was probally my upgrade proceedures is what messed my IP Office . Tech support said that I don't need to validate when upgrading 3.1 to 3.2. but 3.0 and under needs to validate upgrade. He said when you do not validate, upgrade will erase core software then replace core software. If you validate, upgrade will not erase core software but will use more memory of your system which may cause a problem upgrading(Both old and new core software will be loaded on IP Office system).
Thanks for your reply.


"A politician is a fellow who will lay down your life for his country.

 

[Orlando21]

TheDoz,

You're welcome, I hate being stuck in the dark too.

Info that you posted there good to know. Just to get things right. For users let's say at 3.1.xx when upgrading to 3.2; in the Upgrade Wizard, have the validate box unchecked while going through the upgrade? If I understand you, this statement stands correct. According to your Avaya source. So far I have stayed away from 3.2 until the next release to see if things are okay there too. I don't need it so I won't put it.

Now did you get a new system and go through the upgrades or did you AT-???? the old and then reload. When I had trouble with mine I could use those commands but with no down grade, just the config erase. I have done it loads of times before and all was well.

 

[TheDoz]

Orlando21,
I got a replacement 406v2 (Via return authorization) and it was at 3.1(29). I did not use any AT commands like I did on my other 406. I beleive that was my problem. A person should not use AT commands unless they really need to. Any way on this replacement, using Manager (5.2 (17)) I upgraded the system to 3.1 (999)and I did not validate this time like I did before. It upgraded successfully. The I upgraded from 3.1 (999) to 3.2 (17) and did not validate and it upgraded successfully. Now, I had not sent the other one back yet. This weekend I'm going to try to upgrade the other 406 and see if I can get it to work because it is a New System. The replacement avaya sent me was a used 406. So now I have more exspirence in upgrading I want to get my new system back working and ship their used system back to them. If I can not get it working properly I'll be happy with an older working system. I'll let you know what the result is later on. Monday I'm shipping one of these back to avaya. Hopefully I'll keep my new one enstead of the older one. By the way,(The 3.2 documents say to validate when upgrading to 3.2., but tech support says not to.)
Thanks again.

"A politician is a fellow who will lay down your life for his country.

 

[dflsam]

omg how do i recover my corrupt system from this mess!



Teleset Voice & Data Integration
Teleset.com 1-888-teleset

 

[Spanning]

just remove the ip routes and then add them back after reboot

 

[Orlando21]

TheDoz,

Tech support said not to validate if you are already in a 3.1.xx to 3.1.99 and again to 3.2.17. Yet on the site it said to. Reason same as what you had mention earlier to wipe out the core software and replace it with this one. When you get in touch with tech. support ask them or I will next time I give them a call. IF it would be more beneficial to upgrade and not validate every time if it is going to conserve space and only have one version of the core software running. Let me know what becomes of of it.