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]
