DX NetOps

Spec KB:  Trap Director considerations for CA Spectrum 9.2 and 9.3

  • 1.  Spec KB:  Trap Director considerations for CA Spectrum 9.2 and 9.3

    Broadcom Employee
    Posted Feb 24, 2014 04:21 PM

    Document ID:    TEC602288


    Spec KB:  Trap Director considerations for CA Spectrum 9.2 and 9.3



    Trap Director was enhanced in 9.2.3 H11 to allow for more capacity:

    Symptom: Historically, there have been two main problem areas with Trap Director functionality:1) Trap Director may not be able to forward traps to remote servers as fast as they are received. This can result in the Trap Director SpectroSERVER (SS) terminating due memory exhaustion.2) The Trap Director does not immediately recognize when models are moved from one SpectroSERVER to another. These changes aren't accounted for until either the Trap Director cache ages out or the Trap Director SpectroSERVER is restarted.

    Resolution: The following enhancements have been made to Trap Director functionality.1) Trap forwarding to remote landscapes is now done in an asynchronous manner. This can greatly increase forwarding throughput in a geographically distributed environment.2) Trap Director cache accuracy has been improved. Remote SpectroSERVERs now notify the Trap Director SpectroSERVER of events that require the cache to be updated.3) A new Trap Management sub-view has been added to the VNM model Information tab, which contains control options and informational fields related to trap processing.

    (H11, 168540)
    (H11, 110598, 21048835-1)
    (H11, 170858, 21258291-1)

    As part of this work, there are two areas of concern:

    1.      The SpectroSERVER may crash when forwarding traps

    2.      When the Trap Director SpectroSERVER is started in a distributed environment with mixed Spectrum patch versions (for example: some servers running H10 and some running H12), the SpectroSERVERs may crash.

    A stack dump similar to the following may be observed (please contact CA Spectrum Support for analysis of crash files to obtain the stack info):

    #0 0xf70d4ef0 in CsAlertFwdMgr::rem_pim_from_cache () from
    #1 0xf70da8b0 in CsAlertFwdMgr::clear_central_cache_contents () from
    #2 0xf70da96c in CsAlertFwdMgr::connect_callback () from
    #3 0xf6d6e4c1 in LandscapeConnectionMonitor::doNotificationLoop () from
    #4 0xf6d6e517 in LandscapeConnectionMonitor::notificationWrapper () from
    #5 0xf7cdadfb in Thread::call_thread_function () from
    #6 0xf7cdc5a7 in thread_start () from /opt/SPECTRUM/lib/libmoot.so.1
    #7 0x005bba1b in makecontext () from /lib/libc.so.6
    #8 0x0cfbf148 in ?? ()
    #9 0x00000000 in ?? ()


    Please select the following link for more information on this subject:

    Knowledge Document Link: