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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Why isn't 3.1 available for download on the public avaya site? 3
- Thread starter icmpman
- Start date
ProviderReborn
Technical User
The builder levels you need will come on the 3.2 Admin suite.
ACA - IP Office Implement
ACA - IP Telephony
CCENT - Cisco ICND1
CCNA - Working towards.
ACA - IP Office Implement
ACA - IP Telephony
CCENT - Cisco ICND1
CCNA - Working towards.
-
1
- #3
Software upgrade debate time people.
The Tech Bulletins for 3.2 say to upgrade to 3.2 ALL systems must be at 3.1(65) first.
So 3.0>3.2 needs to go via 3.1(65) but 3.0>4.1 doens't (note: other loaders are needed in both!!). Is the 3.1(65) step needed. You don't get the 3.1(65) .bin files with 3.2> Admin CD's but if we are to go by the book (ie the TB's) we need to do it.
Thoughts?????
Jamie Green
ACA:Implement - IP Office
ACS:Implement - IP Office
Fooball is not a matter of life and death-It is far more important!!!!
The Tech Bulletins for 3.2 say to upgrade to 3.2 ALL systems must be at 3.1(65) first.
So 3.0>3.2 needs to go via 3.1(65) but 3.0>4.1 doens't (note: other loaders are needed in both!!). Is the 3.1(65) step needed. You don't get the 3.1(65) .bin files with 3.2> Admin CD's but if we are to go by the book (ie the TB's) we need to do it.
Thoughts?????
Jamie Green
ACA:Implement - IP Office
ACS:Implement - IP Office
Fooball is not a matter of life and death-It is far more important!!!!
- Thread starter
- #4
Ok guys - Well the 3.2 admin download included 3.0.99 bin but no 3.1(65) for the 406v1. I was sure hoping Provider was right, but 3.1.99 was the only bin included and it was for 406v2.
So... What am I to do? Need to go from 3.1(29) to latest 3.2 and 3.1.65 is not available from Avaya.
Anyone have any insight on this?
Thanks in advance.
So... What am I to do? Need to go from 3.1(29) to latest 3.2 and 3.1.65 is not available from Avaya.
Anyone have any insight on this?
Thanks in advance.
-
1
- #5
When you do not have the 3.1.65 then you need to use the 3.1.999 bin file
When you have 3.1.62 or lower you need the 3.1.999 and when you are on 3.1.63 and higer then you can upgrade without the 3.1.999
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!
When you have 3.1.62 or lower you need the 3.1.999 and when you are on 3.1.63 and higer then you can upgrade without the 3.1.999
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!
So where is that documented??
Jamie Green
ACA:Implement - IP Office
ACS:Implement - IP Office
Fooball is not a matter of life and death-It is far more important!!!!
Jamie Green
ACA:Implement - IP Office
ACS:Implement - IP Office
Fooball is not a matter of life and death-It is far more important!!!!
It is not completly true but it is only needed for a 406v2 !!!
It is in techbulletin 80
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!
It is in techbulletin 80
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!
Here a little more from a doc
Early IP Office 406V2 releases at PCS 4, 5 and 6 had flash size of 3MBytes allocated
for the code and 16Mbytes of RAM. These systems need to have their loader
upgraded to V2.4. This can be achieved by upgrading to IP Office version 3.0(999) –
a specific loader upgrade binary. The procedure need only ever be completed once
for a given IP Office 406V2. Once the upgrade to 3.0(999) has completed, the
system will require an additional upgrade to 3.1(999). The IP Office can then be upgraded to 3.2. The flash is extended from 3Mbytes to 6Mbytes by uploading to
loader V2.4.
A similar issue exists for IP Office 406v1 running old versions of the loader (Branch 2
Loader 0.1) found with PCS level 03 and earlier, very few of these exist. To upgrade
to 3.2 these variants should also have their loader upgraded to IP Office version
3.0(999). The procedure need only ever by completed once for a given IP406v1.
Once the upgrade to 3.0(999) has completed the IP Office can be upgraded to 3.1.65
prior to upgrading to 3.2 as normal.
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!
Early IP Office 406V2 releases at PCS 4, 5 and 6 had flash size of 3MBytes allocated
for the code and 16Mbytes of RAM. These systems need to have their loader
upgraded to V2.4. This can be achieved by upgrading to IP Office version 3.0(999) –
a specific loader upgrade binary. The procedure need only ever be completed once
for a given IP Office 406V2. Once the upgrade to 3.0(999) has completed, the
system will require an additional upgrade to 3.1(999). The IP Office can then be upgraded to 3.2. The flash is extended from 3Mbytes to 6Mbytes by uploading to
loader V2.4.
A similar issue exists for IP Office 406v1 running old versions of the loader (Branch 2
Loader 0.1) found with PCS level 03 and earlier, very few of these exist. To upgrade
to 3.2 these variants should also have their loader upgraded to IP Office version
3.0(999). The procedure need only ever by completed once for a given IP406v1.
Once the upgrade to 3.0(999) has completed the IP Office can be upgraded to 3.1.65
prior to upgrading to 3.2 as normal.
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!
It does say at the bottom for 406v1 to go via 3.1(65)
Jamie Green
ACA:Implement - IP Office
ACS:Implement - IP Office
Fooball is not a matter of life and death-It is far more important!!!!
Jamie Green
ACA:Implement - IP Office
ACS:Implement - IP Office
Fooball is not a matter of life and death-It is far more important!!!!
- Thread starter
- #10
And so following up on tlpeter and jamie comments - 406v1 does require 3.1(65) before going to 3.2(x), but it is not available for download. In fact, 3.1(anything) isn't available for download on avaya site. Why is that? Am I still missing something here?
-
1
- #11
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Now give it a rest being a pedantic *** and use some common sense. When 3.2 was being trialled 3.1(65) was the build number given to the intermediate upgrade. They do that because a) that was its true build number and b) just in case they need to do a 3.1(66) or such later. Then they renumber those things to 99 or 999 just before GA. So the guys who wrote the bulletin left a few mentions of (65) rather than (999) in the Techh Bull - jez, take then all out and shot them at dawn without any last meal or reprive from the govenor. Its over a year back and everyone else has managed to work this one out. By the way, did I say...
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
ps. that mean the first answer was the right answer, and it usually is.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Now give it a rest being a pedantic *** and use some common sense. When 3.2 was being trialled 3.1(65) was the build number given to the intermediate upgrade. They do that because a) that was its true build number and b) just in case they need to do a 3.1(66) or such later. Then they renumber those things to 99 or 999 just before GA. So the guys who wrote the bulletin left a few mentions of (65) rather than (999) in the Techh Bull - jez, take then all out and shot them at dawn without any last meal or reprive from the govenor. Its over a year back and everyone else has managed to work this one out. By the way, did I say...
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
Use 3.1(999) as the intermediate upgrade for an IP406V2 before going to 3.2. Its installed as part of the IP Office 3.2 and later Manager.
ps. that mean the first answer was the right answer, and it usually is.
Someone needs a holiday ;-)
Fancy answering the 406v1 question???? And you can answer it once if you want. No need to answer 30 times!
Jamie Green
ACA:Implement - IP Office
ACS:Implement - IP Office
Fooball is not a matter of life and death-It is far more important!!!!
Fancy answering the 406v1 question???? And you can answer it once if you want. No need to answer 30 times!
Jamie Green
ACA:Implement - IP Office
ACS:Implement - IP Office
Fooball is not a matter of life and death-It is far more important!!!!
- Thread starter
- #13
Yeah, I guess I should have specified the fact I'm asking about 406v1 in the original question, but I didn't until a little later on. I'm not trying to beat this in the ground.
I'm just asking the experienced experts what I should do to upgrade a 406v1 from 3.1(29) to 3.2.x. What brought this up is the fact that 3.1.anything is not available on the download site from Avaya and the Tech bulitens state I should upgrade to 3.1.65 before going to 3.2.x.
3.1.anything isn't available for download and the 3.1.999 bin files included with 3.2 admin cd download are only for the 406v2. 3.0.999 is all that exists on the 3.2 admin cd download for 406v1. I don't think I've missed a TB, but that's why I'm here, not to annoy sizbut. I was hoping someone had to go from 3.1 to 3.2 at some point and had some good advice!
Thanks all for your time and input.
I'm just asking the experienced experts what I should do to upgrade a 406v1 from 3.1(29) to 3.2.x. What brought this up is the fact that 3.1.anything is not available on the download site from Avaya and the Tech bulitens state I should upgrade to 3.1.65 before going to 3.2.x.
3.1.anything isn't available for download and the 3.1.999 bin files included with 3.2 admin cd download are only for the 406v2. 3.0.999 is all that exists on the 3.2 admin cd download for 406v1. I don't think I've missed a TB, but that's why I'm here, not to annoy sizbut. I was hoping someone had to go from 3.1 to 3.2 at some point and had some good advice!
Thanks all for your time and input.
But to help you out on your way here is the 406v1 bin file
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!
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!
I actually kind of enjoyed the sizbut annoyance. No offense dude, but it was kind of cool to see someone else gets annoyed besides myself sometimes, and responds the way I feel like doing sometimes.
Not that I am saying icmpman is one of these guys(I do not think he is), but it gets frustrating sometimes to hand hold some guys who think that their MCSE, or other certification in IT means much in their own field let alone qualifies them to administer a PBX, or to belittle the products they do not know their arse from a hole in the ground in concern to, or even in the communications field as a whole. The more of these types of guys I see talking crud about the products they support/muck up with no knowledge or experience, except with whining, and crying about issues they cause by their own ignorance, and unwillingness to have at least one communications competent, or at least professional in the system room by hiring one, the less I think that helping them in here does anyhting more than screwing professionals in our industry out of some hard earned work by their diligent preparation for that work, and make some arrogant "IT" un"professionals" look like they can actually do our jobs the way they seem to think they can, and say we are not needed.
O.K. rant over, breathe in nose, out mouth. image deer running through the forest, and bunnies hopping along the path while butterflies flutter silently by.
Not that I am saying icmpman is one of these guys(I do not think he is), but it gets frustrating sometimes to hand hold some guys who think that their MCSE, or other certification in IT means much in their own field let alone qualifies them to administer a PBX, or to belittle the products they do not know their arse from a hole in the ground in concern to, or even in the communications field as a whole. The more of these types of guys I see talking crud about the products they support/muck up with no knowledge or experience, except with whining, and crying about issues they cause by their own ignorance, and unwillingness to have at least one communications competent, or at least professional in the system room by hiring one, the less I think that helping them in here does anyhting more than screwing professionals in our industry out of some hard earned work by their diligent preparation for that work, and make some arrogant "IT" un"professionals" look like they can actually do our jobs the way they seem to think they can, and say we are not needed.
O.K. rant over, breathe in nose, out mouth. image deer running through the forest, and bunnies hopping along the path while butterflies flutter silently by.
- Thread starter
- #17
Wow. OK. Thanks for the input guys. Really, really didn't mean to offend anyone here. Really didn't feel like I was whining about anything, just trying to understand the inaccuracies and what people did in their best practice.
Have a good weekend.
BTW, Thanks again tlpeter.
Have a good weekend.
BTW, Thanks again tlpeter.
I upgraded a 403 with a DS16V1 from 3.0 to 3.2.
Upgrade Wizard would not let me upgrade the damn expansion module until it was on 3.1.65.
My distributor had to provide the 3.1 bins, as they are not available as stated.
So what was the loader version needed for that?
------------------------------------------
Wash, rinse, repeat.
Upgrade Wizard would not let me upgrade the damn expansion module until it was on 3.1.65.
My distributor had to provide the 3.1 bins, as they are not available as stated.
So what was the loader version needed for that?
------------------------------------------
Wash, rinse, repeat.
- Status
Similar threads