DX NetOps

  • 1.  Email alert if landscape down or switched to secondary

    Posted Jan 11, 2013 09:39 AM
    Hi

    Kindly help how to configure email alert if a particular landscape connected to main location server is down or switched to secondard


  • 2.  RE: Email alert if landscape down or switched to secondary

    Posted Jan 14, 2013 09:48 AM
    I havent do it for switched to secondary, but at least for one server you can do something like this in the setscript (alarmnotifier):

    IF [ "$EVENTCODE" = "0x00010c0b" -o "$EVENTCODE" = "information: Server shutdown" ]


    that would send an email if the Report Manager stops or if the server is shutdown,

    Hope that helps,
    cheers,
    Daniel


  • 3.  RE: Email alert if landscape down or switched to secondary

    Posted Jan 14, 2013 12:02 PM
    HI Mate,

    When a switch over happens and if any landscape goes down i believe there will be an alarm on the vnm model. So use SANM filters with model name of vnm and the alrm code as filtered parameters to send email notification.

    kalyan


  • 4.  RE: Email alert if landscape down or switched to secondary

    Broadcom Employee
    Posted Feb 14, 2013 11:45 AM
    Here is some information I found in the distributed SS admin guide ....

    Monitor the Changeover Between the Primary and Secondary SpectroSERVERs
    You can use watches to monitor the status of your fault tolerant environment. You can create a watch that alerts you when either the primary or the secondary SpectroSERVER is ready to take over.
    To monitor the changeover between the primary and secondary SpectroSERVERs, do the following:
    1. Create a watch on the VNM model to monitor the PercentInitialized (0x11da6) attribute.
    When the value of this attribute is equal to 100 percent, the SpectroSERVER has been initialized and is ready to take over.
    2. Set up the watch to generate an event or an alarm or run a script when the following expression evaluates to TRUE:
    PercentInitialized == 100
    The watch must be set up as an active polled watch. Once it has been created on the primary SpectroSERVER, the primary SpectroSERVER must be synched with the secondary SpectroSERVER so that the watch exists on the secondary server.
    3. Specify a value for the Model_Name (0x1006e) attribute in the watch expression, if you want to be notified only when the secondary SpectroSERVER is ready to take over.
    For example, if the following watch expression evaluates to TRUE, the secondary SpectroSERVER <sec_server> is ready to take over.
    (PercentInitalized == 100) & (Model_Name= <sec_server>)
    Note: For more information about creating a watch, see the Watches User Guide.
    4. To limit the potential for false events or alarms, add the following line to the secondary SpectroSERVER’s .vnmrc file:
    is_secondary = TRUE
    This setting allows the secondary SpectroSERVER to drop events unless CA Spectrum’s internal mechanisms have determined that the secondary SpectroSERVER has taken over as the primary SpectroSERVER.

    The watches can be configured to alarm and can be filtered accordingly with SANM

    HTH,
    Joe