Upgrading a new 406V2

[Avayatech713]

Just downloaded the latest IPO Admin SW 4.2.4 CD (IPO Manager 6.2 (4) and am trying to connect to a new 406V2 to upgrade it to 4.2 SW load - should be at 2.1 from the factory..

Have upgraded many over the years but this new one w/ 6.2 Mgr seems to be a problem.

Since it is a new install on my lab notebook - I don't have any configs - clean install. Opening config and trying to connect to the 406 at 255.255.255.255 doesn't work. The 406 is connect to our LAN and DHCP should have assigned it an IP address as it always has in the past - but it isn't finding it?

Any ideas?

Once MGR finds the 406 - what are the upgrade steps - I'm trying to remember - latest Bin 2.X - then 3.2.99 - then 4.0?? - have it written down but can't find it.

I think I have to use an earlier version of Manager for the upgrade steps as 4.2 is too high for the early loads? Can I laod multiple verson of MGR - older ones along with the newest 6.2?

Also - couldn't find the latest BIN file for 4.2 in the 4.2 Admin CD downlaod from Avaya site? I thought it always was in the BIN folder? Have all the older BINS from 4.1 on down in my working directory.

 

[TomMills]

the will have an ip of 192 .168.42.1 if it is fresh out of the box and by default it will act as a dhcp server not client.

from docs
IP406v2** 3.1(62) and lower 3.1.999 Loader ** Load 4.1
IP406v2 3.1(63) and higher Load 4.1
IP406v2 3.2 Load 4.1
IP406v2 4.0 Load 4.1

** Note: The 3.1.999 loader can be found in the bin\IP406v2\V3_1_999 directory of
the admin CD
or in the Manager\V3_1_999

as to whether you can use the 4.2 manager or not, i have never tried

 

[Avayatech713]

What SW load does the new 406V2 come with - 2.1 as the 403s did?

So the connections in Manager - 406V2 - new config - I set the mac address then the IP address of 192.168.42.1 and saved the config then tried to open the config but MGR could find it?

Am connected direct via straight thru patch cable - 406 to PC LAn port. Have IP of the PC set to 192.168.42.0 and SNM of 255.255.255.255 with no gateway and Windows won't accept the IP data for that connection.

Any ideas?

 

[Bas1234]

don't use 192.168.42.0 but use 192.168.42.2

___________________________________________
It works! Now if only I could remember what I did...
___________________________________________

 

[Bas1234]

and the SNM 255.255.255.0

___________________________________________
It works! Now if only I could remember what I did...
___________________________________________