2.0(18) faulty ?

[IPGuru]

Has anyone experienced problems with 2.0(18) yet, we have found a number of problems whilst testing in the lab:-

1) bootp entrys can get corrupt when performing an upgrade

2) IP routs will no longer merge

3) IP routing does not seem to work when routing over the lan ie

IPO 1 192.168.42.1
ip route 192.168.43.0/24 gateway 192.168.43.1 dest Lan1

IPO2 192.168.43.1
Ip route 192.168.42.0/24 gateway 192.168.42.1 dest Lan1

When runnig 2.0(16) it is posible to ping ither IPO & route data, after upgrade to 2.0(18) it is no longer posible to rout between the subnets

 

[GrandmasterOPI]

Sounds like we should all rush out and upgrade

 

[MrIPO]

Yet another #$%^%$#$ Upgrade !!!!

I am telling you 2.0(16) is a dog, and CCC 4.0(16) forget it. Even Delta server 4.0(24)with 2.0(18) firmware has issues with reflecting group status correctly in CCV this was sopposed to be fixed in 4.0(22)Delta.

We have upgraded a couple of sites to 2.0(18) and it seems generally to be more stable. I really wish they would LOAD test there software better and not just test and release to the market for us to find there ISSUES. I suppose we cannot ask for too much joy with 2.0(16) as it was the first release of 2.0. I feel like taking all the 2.0 sites back to 1.4(27) which seems to be a very stable version.

Anybody else feeling my onging pain with AVAYA.

P.S Today has not been a nice day.

 

[MrIPO]

You are correct with the IP Routes not being mergable in 4.0(19) manager with 2.0(18) firmware. They are simply not there after you get the configuration after a merge.

Good spotting IPGuru !!!

 

[IPGuru]

We have now recieved confirmation not to trust the copy of 2.0(18) on the avaya web site, apparently the incorrect version was posted & should have been removed.