Hi,

I have another possible problem with H09:
- If your SSdb was not closed clearly, the upgrade to H09 will fail.

With H09 CA impliments that several Tools, which need access to the SSdb (like 
SpectroServer, SSdbsave..) will not work, if the SSdb was not closed clearly. 
The can happen when e.g. the SpectroServer crashed. You have to load an old 
clean backup of the SSdb until you can start again the SS.

If this happens before an upgrade, the installer will start the installation, 
but stops when migrating the SSdb. Until this step, the installer copied new 
files as root and move some files. The upgrade will stop at the point 
"migriatin database" and exit, because the SSdb could be corrupt.
After this, the SpectroServer installation is not useable any more, because 
some files are missing and other files have wrong owner.

Be sure, that the SpectroServer stopped clearly before installing H09!

Regards
--
Christoph Keßler
amasol AG                    [email protected]<mailto:[email protected]>
Campus Neue Balan            Phone:+49 (89) 1894743-24
Claudius-Keller-Straße 3 B   Fax:  +49 (89) 1894743-99
81669 München, Germany       Web:  www.amasol.de<http://www.amasol.de/>

amasol Aktiengesellschaft für Informations- und Kommunikationstechnologie
Aufsichtsrat: Prof. Dr. Stephan Kaiser (Vorsitzender)
Vorstand: Wolfgang Bachmann, Stefan Deml, Thomas Dirsch, Frank Jahn, Johann 
Maurer
Amtsgericht München HRB 128327, Sitz der Gesellschaft München

________________________________
Von: Bohra, Saurabh [[email protected]]
Gesendet: Dienstag, 18. Dezember 2012 22:21
An: spectrum
Betreff: [spectrum] Spectrum upgrade to 9.2.2.H09

Some of you have asked me how did my upgrades go to 9.2.2.H09. below is my 
experience.

Our production environment is RHEL 5 .

Distributed 7 DSS (5 have FT SS), 2 OC + SRM  and 1 CABI

Installation was smooth on all the servers.

Issues:

1.       Looks like there is an issue with connecting to SSdb using CLI. The 
connections are getting refused – DEFECT being worked on.

2.       ./CsVendor/Ctron_Gen_HOST/SeverityMaps/aggCurrState_1 file throws 
error message in EventDisp file – Resolution run dos2unix on the file name and 
reload event configuration from VNM.

3.       One of my remote SS for 5 days had non-clearable “CONNECTION TO 
LANDSCAPE CANNOT BE ESTABLISHED" of cause code 0x10c21 alarm. There is no 
connectivity issue between MLS and remote SS.

4.       eHealth integration – was not recognized on the OC server, only 
configuration entries were present. I looked into the custom area and saw 
details in the xml file from my previous version. Clicked test button and 
received - “ehealth configuration error while testing element service”. 
Rebooting eHealth console resulted in OC to pickup the integration and details 
from my previous version. I have also noticed since upgrade every few days the 
ehealth console web services is now going into hang state, no changes (os or 
app patch) have been applied to ehealth server in last few weeks. I am keeping 
an eye on this right now before opening ticket with support.

5.       In my 9.2 SP1 install I had several thousand ncmbucket files and per 
support issue was resolved in H06 and h07 and they would not provide any patch 
for GA SP1 release, the issue is not fixed even in H09 and now I have more 
bucket files previous to upgrade.

6.       On some of my VNM the alarm counts is incorrect.

7.       Several different error messages have been observed in catalina.out, 
support is currently looking into this.

8.       When Windows 2008 R2 or Windows 2007 server are discovered in 
Spectrum, the random port (physical or virtual) on the server gets connected to 
the switch.

Saurabh Bohra
Sr. Network Mgmt Systems Analyst
ESPN Inc.
O: 860-766-0842  |  M: 860-385-3597  |  e-mail: 
[email protected]<mailto:[email protected]>


 *   --To unsubscribe from spectrum, send email to 
[email protected]<mailto:[email protected]> with the body: unsubscribe spectrum 
[email protected]

---
To unsubscribe from spectrum, send email to [email protected] with the body: 
unsubscribe spectrum [email protected]

Reply via email to