DX NetOps

  • 1.  Device with contact lost but condition still Normal

    Posted Dec 04, 2018 08:03 AM

    Hello people,

     

    I have one device in my environment that is presenting Contact Status: Lost and it's condition is still Normal and there's no alarm for this device.

     



  • 2.  Re: Device with contact lost but condition still Normal

    Broadcom Employee
    Posted Dec 04, 2018 09:37 AM

    Hi Alex,

     Are there any events?

    Cheers

    Jay



  • 3.  Re: Device with contact lost but condition still Normal

    Broadcom Employee
    Posted Dec 05, 2018 04:22 AM

    Hi Alex,

     

    We have seen this from time to time and the quick solution is to put the device into Maintenance mode, wait a poll cycle and then take the device out of maintenance.

    If you are able to troubleshoot this further please open a support issue and provide the following (before putting device into/out of maintenance mode).

    1. .moot.trace from the SpectroSERVER for at least 15 mins.

    "How to run a moot trace for CA Spectrum". - CA Knowledge 

    2. SNMP Stack debug from the VNM Model, Dynamic Debugging, Set to Enabled for 15 minutes.

    3. Wireshark sniffer trace (windows) or tcpdump (Linux) from the SpectroSERVER to the device.

     

    With this information we should be able to determine what the problem is.

     

    Best regards,

    Glenn



  • 4.  Re: Device with contact lost but condition still Normal

    Broadcom Employee
    Posted Dec 05, 2018 01:15 PM

    It seems the 0x10302 event code was customized to generate a Critical alarm and then the alarm was manually cleared.

     

    "Severity","Created On","Name","Cleared On","Event","Event Type","Created By","Cleared By","Model Type Name","Event Precedence"

     

    "Critical","Dec 4, 2018 9:17:00 AM BRST","2960-24Almoxarifado03","Dec 4, 2018 11:50:47 AM BRST","Contact has been lost with model 2960-24Almoxarifado03 of type SwCiscoIOS.","0x10302","System","spectrum@bhz-app-spect03","SwCiscoIOS","10"

     

    "","Dec 4, 2018 9:17:00 AM BRST","2960-24Almoxarifado03","","Alarm number 298495 with probable cause id 0x10302 generated for device 2960-24Almoxarifado03 of type SwCiscoIOS. The severity of this alarm is CRITICAL.","0x10701","System","","SwCiscoIOS","10"

     

    "","Dec 4, 2018 11:50:47 AM BRST","2960-24Almoxarifado03","","User spectrum@bhz-app-spect03 cleared alarm number 298495 with probable cause id 0x10302 for device 2960-24Almoxarifado03 of type SwCiscoIOS.","0x10706","spectrum@bhz-app-spect03","","SwCiscoIOS","10"