Downgrade to R9 from 9.1,

[dthszn]

I have a system that was shipped at R9.1. I am adding it to a SCN with centralized VM where all of the systems are at 9.0.6.0.979. The company just paid for all the upgrades and do not want to upgrade all of the systems again. I know that the SCN works fine as long as the systems are within one release, but have been told and experienced multiple issues with centralized VM on different releases. I have set up the new system at 9.1 and made the first call and get the confirmation in System Status. My question is after I downgrade the system. Will I still be able to tell that I made the call at R9.1 or will I need to buy an Upgrade license when going to R9.1 later this year. Thanks in advance.

 

[hibroth]

After you gone back to R9.0 start sysmon traces with default filters, you should see at the beginning of printing the "system software history" including the R9.1 one.
All those records cannot be deleted even if defaulted via DTE, so the answer shoud be: YES

 

[dthszn]

Thanks for the reply. I tried this, but I don't see it sysmon. I have defaulted all of the filters. I don't see anything containing "system software history". Any thoughts?

 

[holdmusic34]

a) Cannot replicate this.
b) Didn't know about it.
c) I would know of it if you could.

Respectfully disagree. Prove me wrong Hibroth...please.

'Look- one of ours out of the main hold!'

 

[tlpeter]

After the first made call this system does not need a license for anything on 9.1 or lower.
When you upgrade to a 9.2 or higher (whatever version is released) then you will need an upgrade license.


BAZINGA!

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

 

[hibroth]

Don't worry Holdmusic, you can disagree because I am not the truth repository and may be I'm wrong but this is what I see on all our machines which I DTE defaulted I dont't know how many times:


********** Warning: TEXT Logging to C:\Program Files (x86)\Avaya\IP Office\Monitor\\TMP1.$$$ File: STARTED on 30/6/2015 11:22:06 **********
513494798mS PRN: Monitor Started IP=192.168.0.24 IP 500 V2 9.0.7.0 build 983 OurCompany
(IP Office: Supports Unicode, System Locale is default)
513494798mS PRN: LAW=A PRI=2, BRI=4, ALOG=0, VCOMP=64, MDM=0, WAN=0, MODU=1 LANM=0 CkSRC=13 VMAIL=1(VER=3 TYP=1) 1-X=1 CALLS=4(TOT=3381)
513497798mS PRN: +++ START OF ALARM LOG DUMP +++
513497798mS PRN: ALARM: 28/06/2011 07:12:42 IP 500 V2 7.0(12) <TLB Data > CRIT RAISED addr=00000024 d=5 pc=f09a8f34 f09a9fd8 f09a90a0 f09c8ee8 f097f65c f0984f9c
513497798mS PRN: ALARM: 19/12/2012 09:18:49 IP 500 V2 8.1(63) <ISI Excep > CRIT RAISED addr=00000000 d=5 pc=41820004 f130132c f1350a48 f1324ad0 f13278c8 f1327a70
513497799mS PRN: ALARM: 05/02/2013 10:07:03 IP 500 V2 8.1(63) <ISI Excep > CRIT RAISED addr=00000000 d=5 pc=41820004 f1306130 f1350a48 f1324ad0 f13276a0 f1325874
513497799mS PRN: ALARM: 19/02/2013 15:27:42 IP 500 V2 8.1(63) <ISI Excep > CRIT RAISED addr=00000000 d=5 pc=41820004 f130132c f1350a48 f1324ad0 f13278c8 f1327a70
513497799mS PRN: ALARM: 07/08/2013 14:43:49 IP 500 V2 9.0.0.0 build 816 <TLB Data > CRIT RAISED addr=7f7f806b d=5 pc=f04470c4 f04470bc f041ff68 f042af44 f04311cc f043032c
513497800mS PRN: ALARM: 28/11/2013 03:24:37 IP 500 V2 9.0.0.0 build 829 <TLB Data > CRIT RAISED addr=00000000 d=5 pc=f0b16348 f0b15b38 f1133cb8 f0aeedf8 f11328cc f1560b7c
513497800mS PRN: ALARM: 19/06/2014 12:23:12 IP 500 V2 9.0.3.0 build 941 <TLB Data > CRIT RAISED addr=00000014 d=5 pc=f0341760 f040deb8 f0341a70 f05776ec f043dc1c f043ca84
513497801mS PRN: ALARM: 20/06/2014 10:19:51 IP 500 V2 9.0.3.0 build 941 <TLB Data > CRIT RAISED addr=00000014 d=5 pc=f0341760 f040deb8 f0341a70 f05776ec f043dc1c f043ca84
513497801mS PRN: +++ END OF ALARM LOG DUMP +++

 

[tlpeter]

These are alarms and in a normal situation those should not show up at all


BAZINGA!

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

 

[holdmusic34]

The truth will set you free. As Tlpeter says, these are alarms from the 'print' feature in monitor.
Would be a good feature hey?
But as far as getting a grip request through- two chances. Buckleys and none.
(Australian saying)

'Look- one of ours out of the main hold!'

 

[sizbut]

We need to be careful what we wish for else Avaya will interpret this as a request to have a deliberate default critical alarm built into each release* rather than have the unlicensed release entitlement of a system appear somewhere in SSA or monitor.

(*rather than the current random set of bugs we have now)

Stuck in a never ending cycle of file copying.

 

[dthszn]

Thanks for all of the information. I've been away for a couple of days. So my questions still remains. Is there anyway to tell that I had the system at 9.1. I will document this, but with a team of technicians, I'm afraid it could fall through the cracks (I'm sure nobody else has this problem ) or if we work on systems that we didn't install, we could see what options we have. Thanks again for any information.