> I can't understand why you are using EEM (on Spectrum installation). I can do > the LDAP/AD integration using native OneClick configuration (I believe you're > using for single sign-on purpose, right ?).
If you use more than one CA product you can install EEM and connect all other applications to this authentication source. If you switch from one product to another (like open eHealth reports out of Spectrum OneClick) you don't need to authenticate again with the same credentials. Regards amasol Kundentag 8.-9.Juni 2011 - Infos und Anmeldung http://www.amasol.de/ -- Christoph Keßler amasol AG [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 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 > -----Ursprüngliche Nachricht----- > Von: Marcio Augusto Alvarez [mailto:[email protected]] > Gesendet: Freitag, 27. Mai 2011 14:28 > An: spectrum > Cc: Wagner Franciosi > Betreff: RES: [spectrum] H04 experiences (WAS: Problems with Spectrum 9.2 H03) > > I'll be honest with you guys... > > I'm working with two different environment (customers). Both with distributed > environment and fault tolerance (3 primary SpectroServers and 3 secondary SS > each). > I wish to install H04 as soon as possible because nothing can be worst than > H03. I got a lot of SS crashes and bugs on both environment after H03 > installation. The Spectrum application is running under RHEL5, Solaris 9 and > Solaris 10. > > In some servers I can see a high both CPU and Memory usage. > > I'll not talk about SRM, because this module just can't work fine for me (I > open few thickets about that). > > I can't understand why you are using EEM (on Spectrum installation). I can do > the LDAP/AD integration using native OneClick configuration (I believe you're > using for single sign-on purpose, right ?). > > We are using EEM for LDAP/AD integration on eHealth only. > > Regards. > > Marcio Augusto Alvarez > Gerenciamento de Rede > Fone.: 55.11.4166.6962 > Fax.: 55.11. 4195-3366 > Celular: 55.11.6365.0197 > E-mail.: [email protected] > TM Solutions - Soluções sob medida em tecnologia da informação > Rua Gêmeos, 64 - Cond. Conde Empresarial - Alphaville - CEP.06473-020 > > > -----Mensagem original----- > De: Naiman, Eugen [mailto:[email protected]] > Enviada em: quinta-feira, 26 de maio de 2011 20:02 > Para: spectrum > Assunto: RE: [spectrum] H04 experiences (WAS: Problems with Spectrum 9.2 H03) > > No major problems here after installing H04, well: no EEM, no fault tolerant > and no distributed SS and so far is working well without any crashes. > The only problem I am experiencing is related to alarm filters. > For some reason, on workstations having OneClick open overnight and using an > alarm filter, the display will show alarms with missing fields (IP, Name and > some others...). All of these alarms would have been hidden by the filter in > place. If OneClick is restarted everything is back to normal. > > Other than that - it's fine. No reason for me to consider a rollback. > > Regards, > > ============================================ > > Eugen NAIMAN > IT Officer > ICT Infrastructure > Department Health and Human Services > 5/99 Bathurst Street, Hobart, 7000 > (: (03) 6233 8565 > Ê: (03) 6233 6297 > [email protected] > ============================================ > > > -----Original Message----- > From: Pfleger, Jim [mailto:[email protected]] > Sent: Friday, 27 May 2011 5:50 AM > To: spectrum > Cc: David Game; Cantwell, Rene D > Subject: Re: [spectrum] H04 experiences (WAS: Problems with Spectrum 9.2 H03) > > Rene' Cantwell (manager, CA Support) was having trouble replying back to the > list, and asked me to post this on her behalf. > > ========== > > If I may, I'd like to give some detail on the H04 issues seen, the reason it > is temporarily unavailable and our plan going forward. > > To date we have several customers like Jim who have installed H04 and are > successfully up and running, in development/test environments as well as in > production. > > After identify the customers who installed H04 and experienced the EEM > integration issue, the decision was made to make H04 unavailable for download > until we have a full understanding of the technical issues and impact to our > customers. Determining root cause and solutions is an ongoing effort we are > in the middle of with 4 customers. As of today we have 3 of the 4 customers > with the EEM integration up and running. We are also working on a knowledge > doc that will detail the various scenarios and solutions. So far these are > all configuration issues and not H04 code problems. > > In addition to the EEM integration issues, we have been working with 4 > customers who have experienced a post H04 SpectroSERVER crash. For 3 > of these customers the crash is due to SNMP throttling functionality attached > to Foundry devices. We have identified the root cause, a workaround and we > are developing a patch to resolve. The 4th customer SpectroSERVER crash is > still being investigated, we do not yet know how or if this will affect any > other customers. > > David Game, I will have additional support and sustaining engineers review > your SpectroSERVER crash issue to determine if it is the issue above or > different and what action plan we can put in place to identify the root cause > and get you back up and running. > > Both the EEM integration scenarios and the SpectroSERVER crash scenarios need > to be fully understood and documented before we can release H04 again. We do > not expect to make any code changes to H04, at this time it will only be a > release of what we originally posted along with knowledge documents on the > known issues above. > > I'd like to make one finial comment on the uninstall process for H04. > Due to complexity reasons it is nearly impossible to develop an uninstall > process for hotfix patches, service packs or full releases. > For this reason we developed this best practice knowledge document; > > Title: What is the best practice to make a complete back up copy of > SPECTRUM? > > https://support.ca.com/irj/portal/kbtech?docid=3D512407&searchID=3DTEC51 > 2=407&fromKBResultsScreen=3DT=20 > > Without a complete save of your environment before installing a hotfix, > service pack or full release upgrade, the only method to get back to it is > through reinstalls. > > If anyone would like to talk further about H04, or plan to re-release or > upgrade concerns, please feel free to contact me directly. > > > Regards, > Rene' > > > > Rene' Cantwell > CA Technologies > Support Delivery Manager > Tel: +1-603-334-2497 or +1 877-428-6324 > Fax: +1-603-334-2540 > [email protected] > > > > On 5/26/11 10:58 AM, "Pfleger, Jim" <[email protected]> wrote: > > > Our systems that are running H04 are all RHEL 5 VMs. There are five > > total landscapes (one MLS/TD/SBGW landscape, and four with actual > > models), each with two VMs. All 10 SS servers have the equivalent of 2 > > Xeon CPUs at 2.9GHz, 6GB of RAM, and 27GB disk. We also have three > > plain OC servers, one SRM OC server, and one BOXI server. > > > > Landscapes vary between 1400 and 2100 models each. We total around 30 > > traps/sec and very few syslogs across the environment. > > > > The only clean install we've done is 9.0; we've been upgrading ever since. > > > > HTH, > > Jim > > > > > > On 5/26/11 10:46 AM, "[email protected]" <[email protected]> wrote: > > > >> > >> > >> It would be nice to get some environmental detail on these issues > >> > >> Operating System > >> Hardware or VM > >> Number of Models > >> Upgraded SSDB vs a clean install > >> Trap/Syslog load > >> > >> > >> We are getting ready to build out our dev environment with H04 under > >> RH5 > >> > >> Dan Ellsweig > >> > >> Enterprise Management Systems > >> Avon Products > >> 1 Avon Plaza > >> Rye, NY 10830 > >> > >> 914-935-2723 > >> > >> > >> > >> > >> James Garthek > >> <james.garthek@gm > >> ail.com> To > >> "spectrum" > >> 05/26/2011 01:39 <[email protected]> > >> PM cc > >> spectrum > >> <[email protected]> > >> Please respond to Subject > >> James Garthek Re: [spectrum] H04 experiences > >> <james.garthek@gm (WAS: Problems with Spectrum 9.2 > >> ail.com> H03) > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> Linux > >> I'm planning to do some troubleshooting, but I hadn't time yet. > >> > >> > >> On Thu, May 26, 2011 at 7:25 PM, Diego Pereyra > >> <[email protected]> wrote: > >>> under wich operating system ?? > >>> > >>> -----Original Message----- > >>> From: James Garthek [mailto:[email protected]] > >>> Sent: Thu 26/05/2011 14:24 > >>> To: spectrum > >>> Subject: Re: [spectrum] H04 experiences (WAS: Problems with Spectrum > >>> 9.2 > >> H03) > >>> > >>> Hi, > >>> > >>> After installing H04, our SpectroServer was working 5 minutes. After > >>> that, it crashed!!! (no EEM integration, no fault tolerant) > >>> > >>> Now, working with H03 again. > >>> > >>> James. > >>> > >>> > >>> On Thu, May 26, 2011 at 6:58 PM, David Game > >>> <[email protected]> > >> wrote: > >>>> I should have added that not everyone will be affected by the > >>>> issues > >> found > >>>> but we had stability problems with it. > >>>> > >>>> > >>>> > >>>> We're not using EEM either but had 3 crashes on our dev server in > >>>> the > >> space > >>>> of 4-5 days. My colleague testing it found other issues too (which > >>>> I > >> can't > >>>> recall many of right now) but for CA to pull it from release means > >>>> there must have been some major issues with it for various other > >>>> people as > >> well. > >>>> I'm holding off H04 on our main production systems until we get a > >>>> stable release. > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> From: Pfleger, Jim [mailto:[email protected]] > >>>> Sent: 26 May 2011 17:55 > >>>> To: David Game > >>>> Cc: Spectrum users > >>>> Subject: Re: [spectrum] H04 experiences (WAS: Problems with > >>>> Spectrum 9.2 > >>>> H03) > >>>> > >>>> > >>>> > >>>> My understanding from CA is that it was pulled because it caused a > >> problem > >>>> in the Spectrum<->EEM integration, which we're not using. > >>>> Regardless, > >> we're > >>>> stuck on H04 since hotfixes do not contain a rollback mechanism > >>>> like > >> patches > >>>> do. We're putting in an ER for this. > >>>> > >>>> > >>>> On 5/26/11 9:49 AM, "David Game" <[email protected]> wrote: > >>>> > >>>> Jim - HF04 has been pulled due to an inordinate number of bugs! If > >>>> you > >> can > >>>> roll back to H03 until HF04 is "fixed" I'd strongly advise it. > >>>> > >>>> > >>>> > >>>> From: Pfleger, Jim [mailto:[email protected]] > >>>> Sent: 26 May 2011 16:09 > >>>> To: spectrum > >>>> Subject: [spectrum] H04 experiences (WAS: Problems with Spectrum > >>>> 9.2 > >> H03) > >>>> > >>>> As promised, here's an update on the issues from my previous email > >>>> - all four were addressed in H04. I'm awaiting final confirmation > >>>> from our reporting guru on the SRM issue, but I believe it's been > >>>> resolved. Also, we're occasionally getting duplicate notifications > >>>> again, but the debug looks different from the last time this > >>>> happened, so we're treating it > >> as a > >>>> separate issue. > >>>> > >>>> Because of these fixes (and others) we installed H04 as soon as it > >>>> was available, so I can provide some early feedback. > >>>> > >>>> We've found two events (so far) that are no longer logged to the > >>>> events database (0x1010a and 0x1010d, for model attr changes). > >>>> We're going to > >> now > >>>> conduct a full audit of what other undocumented event changes came > >>>> with > >> H04. > >>>> It seems that our failover servers are sometimes being started as > >>>> root instead of ssadmin, which is mangling file permissions. The > >>>> problem > >> started > >>>> after H04, but it's not clear why yet, partly because it's only > >> happening on > >>>> some of our failover servers. > >>>> The negative alarm counts issue citied in the release notes is not > >>>> (completely) fixed, and we already have a new ticket open on it. > >>>> > >>>> That's all I have so far on H04. When I have anything else of note, > >>>> I'll definitely share it with the group. > >>>> > >>>> HTH, > >>>> Jim > >>>> > >>>> ___________________________________________________________________ > >>>> ___ This email has been scanned by the MessageLabs Email Security > >>>> System. > >>>> For more information please visit http://www.messagelabs.com/email > >>>> ___________________________________________________________________ > >>>> ___ > >>> > >>> --- > >>> To unsubscribe from spectrum, send email to [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] > >> > >> > >> > >> --- > >> To unsubscribe from spectrum, send email to [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] > > > --- > To unsubscribe from spectrum, send email to [email protected] with the body: > unsubscribe spectrum [email protected] > > > CONFIDENTIALITY NOTICE AND DISCLAIMER > > The information in this transmission may be confidential and/or protected by > legal professional privilege, and is intended only for the person or persons > to whom it is addressed. If you are not such a person, you are warned that any > disclosure, copying or dissemination of the information is unauthorised. If > you have received the transmission in error, please immediately contact this > office by telephone, fax or email, to inform us of the error and to enable > arrangements to be made for the destruction of the transmission, or its return > at our cost. No liability is accepted for any unauthorised use of the > information contained in this transmission. If the transmission contains > advice, the advice is based on instructions in relation to, and is provided to > the addressee in connection with, the matter mentioned above. Responsibility > is not accepted for reliance upon it by any other person or for any other > purpose. > > --- > To unsubscribe from spectrum, send email to [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] --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
