Why do the download bin files only include 12 files?

[pkellow]

Having downloaded the binary files for 6_1_12 from support.avaya.com I've extracted them and have the following files only:
avpots16.bin
bin.cfg
dvppots.bin
ip406u.bin
ip412.bin
ip500.bin
ip500v2.bin
naatm16.bin
naDCP-16.bin
naDCPv2.bin
nas0-16.bin

However having previously installed Manager version 8.1.12 for IPO 6.1.12, under c:\program files\Avaya\IP Office\Manager\ I have many more bin files, such as:
ha96xxua3_11.bin
hb96xxua3_11.bin
These appear to be other binary/firmware files for the phones etc.

Let's say you've installed IPO 7.0 (Manager 9.0), and you have a IPO 6.0 to IPO 6.1.12 upgrade to perform. I was informed you could use the 7.0 (9.0) version of manager, download the binary files for 6_1_12, create a directory (e.g. "6_1_12_bin_files") under c:\program files\Avaya\IP Office\Manager and change Manager->preferences->directories->bin directory, so this points to the 6_1_12 folder, and use the downloaded binary files, I.E. to upgrade to IPO 6.1.12.

However I don't understand, would the 12 files be necessary only (just the binary files downloaded from support.avaya.com) or would I need to locate all the bin files from a previous and complete installation of 6_1_12 (Manager 8_1_12)?

Thanks in anticipation.

 

[kholladay]

Because the .bin file download is for upgrading the IP Office/Modules not upgrading the phones.

Kyle Holladay
ACSS & APSS SME Communications
MCP/MCTS Exchange 2007
Adtran ATSA, Aruba ACMA

"I have one speed, I have one gear...GO!!!" - Charlie Sheen

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford

 

[pkellow]

Thanks, that makes sense.

To clarify:
to do a complete upgrade of 6.0 to 6.1 using Manager 9.0 (IPO 7.0) you'd need all the bin files from 6.1. You shouldn't copy the Manager bin files from 9.0 (IPO 7.0) to a directory, then copy in the 6.1 downloaded bin files. i.e. use all the bin files from a previous install of Manager 8.1 (IPO 6.1) only. Don't mix the phone bin files from latest version of IPO (7.0) with the 'core' bin files downloaded from 6.1.

Is that right?

 

[tlpeter]

Pkellow, i always copy the folder "manager" and rename it to "manager_version_number"
Then i install a newer version.
This way you always have the versions you need and you can change working directories very easy.

BAZINGA!

I'm not insane, my mother had me tested!

 

[pkellow]

Just I'm hot off a training course & was taught there was no need to copy the entire manager directory to retain old versions, just as long as you copy out the bin files necessary for the version/upgrade. I'll copy all the bin files from c:\program files\avaya\ip office\manager out to a V6_0_18_bins directory (for example) under c:\program files\avaya\ip office\manager and use just these (by setting preferences for Manager and change just the bin directory). This will minimise disk space usage.

If this does not work, I can always install the appropriate manager version, and copy the entire manager directory off somewhere (i.e. copy the folder "manager" and rename it to "manager_version_number").


Thanks all.

PS I'm being clear/verbose, only so I can save this for future reference.

 

[tlpeter]

That is an option too but sometimes it is cery handy to have a complete copy of a version.


BAZINGA!

I'm not insane, my mother had me tested!

 

[kholladay]

Why do you need a complete set of .bin files? Are you planning on downgrading later?

You can use 9.0 Manager to perform maintenance on any version of IP Office back down to 3.2 or somewhere around there (3.0 maybe?). The only reason for the .bin files would be if you planned on using your copy of Manager to upgrade a clients system from some older version to some other older version as you said 6.0 to 6.1 using Manager 9.0. In that case yes you just need the full .bin set.

The only reason to keep older copies of Manger is if you want to create an offline config for an older version as Manager will create an offline config appropriate for its own version number.



Kyle Holladay
ACSS & APSS SME Communications
MCP/MCTS Exchange 2007
Adtran ATSA, Aruba ACMA

"I have one speed, I have one gear...GO!!!" - Charlie Sheen

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford

 

[kwing112000]

I am with Peter on this. i keep a copy of the manager folder for most versions and use it for upgrades all the time.

Kevin Wing
ACSS Small and Medium Enterprise (SME) Communications
ACS- Implement IP Office
ACA- Implement IP Office
Carousel Industries

 

[kholladay]

To each his own and that is a perfectly valid solution. I hate having extra and unneeded software on my system so I keep the .bins and NNxxupgrade.scr and the like an dump the rest.

Kyle Holladay
ACSS & APSS SME Communications
MCP/MCTS Exchange 2007
Adtran ATSA, Aruba ACMA

"I have one speed, I have one gear...GO!!!" - Charlie Sheen

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford

 

[tlpeter]

Dect uses different versions sometimes.
Also when strange issues appear then i rather use the right manager.
But you could do it all with the lateat manager.

Though i saw scn stuff appear in a sip trunk on 7.0
So strange stuff can happen.

BAZINGA!

I'm not insane, my mother had me tested!

 

[kholladay]

I'll have to defer to Peter on this one. I use Manager primarily to export/import the configuration.csv so I can do my editing in Excel so I likely miss many of these things.

Kyle Holladay
ACSS & APSS SME Communications
MCP/MCTS Exchange 2007
Adtran ATSA, Aruba ACMA

"I have one speed, I have one gear...GO!!!" - Charlie Sheen

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford

 

[pkellow]

I did not realise the manager version will create an offline version appropriate to it's version.

I'll stick to the bins only for upgrades and use just the latest manager version. If I see any strange things I'll use the correct manager.

thanks for all your contributions, definately saving this one.

regards
paul