When primary hub is restarted, alarms come through from systems which are in a maintenance window

Document ID:  TEC1123557
Last Modified Date:  06/16/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA Unified Infrastructure Management

Releases

  • CA Unified Infrastructure Management:Release:8.51
  • CA Unified Infrastructure Management:Release:8.5
  • CA Unified Infrastructure Management:Release:8.47
  • CA Unified Infrastructure Management:Release:8.42
  • CA Unified Infrastructure Management:Release:8.41
  • CA Unified Infrastructure Management:Release:8.4
  • CA Unified Infrastructure Management:Release:8.31
  • CA Unified Infrastructure Management:Release:8.2

Components

  • UIM NAS:UIMNAS
  • UIM MAINTENANCE MODE:UIMMTM
Issue:

When a server is placed in maintenance mode, and the primary hub is restarted, alarms that are generated by remote robots during the restart will bypass maintenance mode and the alerts will be seen unexpectedly.

 

 

Cause:

Sometimes the maintenance_mode probe takes longer to start than expected.  If NAS cannot contact the maintenance_mode probe, it will allow all alarms to come through until contact is restored.

Workaround:

1. On the primary hub, locate the file:  /Nimsoft/robot/controller.cfg

2. Open this file with a text editor such as vi, notepad, or Notepad++

3. Locate the alarm_enrichment section which looks similar to the following:

<alarm_enrichment>

   description = Alarm Enrichment Server

   group = Infrastructure

   active = yes

   type = daemon

   command = <startup java>

   arguments = -Dfile.encoding=UTF-8 -jar ../lib/alarm_enrichment.jar

   config = alarm_enrichment.cfg

   logfile = alarm_enrichment.log

   workdir = probes/service/nas/alarm_enrichment

   magic_key = LL0P0tM9FJtztfSmSrctGBni3O19oO6+slDYaxmwDbsU3sJGS4s571bjpvc2Wd58r5o7rRLSD+ZGe4QPJgELFA==

</alarm_enrichment>

Anywhere in this section, add the following line:

start_after = maintenance_mode

 

This will force the alarm_enrichment probe to wait until the maintenance_mode probe is fully started before it attempts to start.  The NAS probe in turn is already configured not to start until alarm_enrichment starts.  Therefore, this configuration will prevent the NAS from starting up before maintenance_mode, which will resolve this issue.

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >

Chat with CA

Just give us some brief information and we'll connect you to the right CA ExpertCA sales representative.

Our hours of availability are 8AM - 5PM CST.

All Fields Required

connecting

We're matching your request.

Unfortunately, we can't connect you to an agent. If you are not automatically redirected please click here.

  • {{message.agentProfile.name}} will be helping you today.

    View Profile


  • Transfered to {{message.agentProfile.name}}

    {{message.agentProfile.name}} joined the conversation

    {{message.agentProfile.name}} left the conversation

  • Your chat with {{$storage.chatSession.messages[$index - 1].agentProfile.name}} has ended.
    Thank you for your interest in CA.


    Rate Your Chat Experience.

    {{chat.statusMsg}}

agent is typing