Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Be careful after 4.1(9) upgrade!

Status
Not open for further replies.

t1techcole

Technical User
Aug 9, 2006
28
US
Be careful out there after you upgrade to 4.1(9) that you upgrade all manager versions which have access to your system. Had a customer connect to a 4.1(9) 406V2 with manager 3.2(54) and it will allow the connection and also accept the merge, but it puts the unit into a software reboot loop. You will have to dispatch to restore the unit.
(3.2(53) also tested and will connect, 3.2(57) and greater would not even see the units - as designed).
 
That is fun :)


ACA - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 


Just on a side note, has anybody tried opening an alchemy cfg with 4.1 manager, it works.

ACE - Avaya Certified Expert
ACI - Avaya Certified Instructor
 
He is right too, you can see 4.1 system in a 3.2.53 maanager too.



ACE - Avaya Certified Expert
ACI - Avaya Certified Instructor
 
How does the lcr/ars look then ?
That is why the system stops working


ACA - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
You can also use the old Network Alchemy Manager tool to login the 4.1 you don't need and Administrator password but just the old "password" works.

greetzzz....Bas

y1pzZTEUdok1vrI5cLb3FdPX4PgTPlSONkb5WPjz0x50etSujaMSmhdRCbOx9vASnrRNzzXv0IxNQA

___________________________________________
It works! Now if only I could remember what I did...
___________________________________________
 
tlpeter you can make changes fine, I did it, all that happened was it lost any reference to ARS...obviously, other than that the system worked fine

ACS - IP Office Implement
 
I had a customer open a 4.0 system with 3.2 and save it and it removed all the ars entrys. Of course some how it was my fault but they get billed to fix it.
 
pretty simple really, don't try and change a config on a system with a later version of s/w than the version of manager you have. Shame on the upgrader for not checking the customer's versions before leaving.
 
The one i had was a subcontractor who installed 4.0 when all the other sites were 3.2 and then gave the customer the IP address and said you can manager all your systems from your PC. I have them remote into the local server and use the software onsite. we try not to give it to them to put on their own pcs. only on the server.
 
Changing the IPO IP address should make the manager not be able to find the IPO.

 
4.x manager was specifically designed to be reverse-compatible with 3.x (I believe only 3.1 and 3.2).

You had to be at a minimum release of those though (like 3.2.59 or something) because they prepped the database so Manager could read what options you had and what to hide (based on version).

Kris.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top