Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

2.0(18) faulty ?

2.0(18) faulty ?

2.0(18) faulty ?

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
 ip route gateway dest Lan1
 Ip route gateway 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

RE: 2.0(18) faulty ?

Sounds like we should all rush out and upgrade

RE: 2.0(18) faulty ?

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. :(

RE: 2.0(18) faulty ?

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 !!!

RE: 2.0(18) faulty ?

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.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close