DX NetOps

 View Only
  • 1.  Spectrum Policy Manager

    Posted Mar 08, 2017 04:24 PM

    Suppose there existed a custom created Spectrum global policy/rule which has the two settings:

       1) 'GeneratePortStatusAlarms' (0x12a54) attributes to NO.  

       2) 'AlarmOnLinkDownTrap(0x11fc2) 0

     

    for all ports (i.e. All network gear and systemEdge agent monitored hosts). The policy is said to have affected approx. 690K models.

    For Spectrum SMEs, what would be your recommended ways to 'turn' port monitoring back on wisely without getting flooded with false positive alarms?

     

    Thanks,

    Charles



  • 2.  Re: Spectrum Policy Manager

    Posted Mar 21, 2017 04:19 PM

    Hi Charles,

     

    create a Global Collection "Connected_Ports" with Model Class = Port and NetworkLinkType != No Link to get all ports which have a modeled pipe in Spectrum. Then, assign this GC to a policy which enables the "alarming" attributes. Also refer to https://www.ca.com/us/services-support/ca-support/ca-support-online/knowledge-base-articles.TEC1074036.html.

     

    Change your existing global policy to include only Ports with NetworkLinkType = No Link.

     

    Alternatively, what we have also done for customers is to create an Event Procedure which resets the port alarming attributes when a port leaves the "Connected_Ports"  GC. That way, you don't have a huge GC with unconnected ports.

     

    Regards

    Maik



  • 3.  Re: Spectrum Policy Manager

    Posted May 30, 2017 07:15 AM

    Would you mind sharing the Event Procedure you wrote to the community?



  • 4.  Re: Spectrum Policy Manager

    Posted Jun 02, 2017 11:42 AM

    Hi Christophe,

     

    here you go - I just tested it to verify that it works. the Event Procedure resets the Port Alarming, Port Trap Processing and some Port Thresholds:

     

    0x110a04 E 50 R CA.EventCondition, "({v 2} == {S \"Connected_Ports\"})" , "0xffff0002  -:-"

    0xffff0002 E 50 P \
    " And( WriteAttribute( {C CURRENT_MODEL}, {H 0x11fc2}, { I 0}), \
      And( WriteAttribute( {C CURRENT_MODEL}, {H 0x12da6}, { I 0}), \
      And( WriteAttribute( {C CURRENT_MODEL}, {H 0x12952}, { I 0}), \
      And( WriteAttribute( {C CURRENT_MODEL}, {H 0x1294e}, { I 0}), \
      And( WriteAttribute( {C CURRENT_MODEL}, {H 0x12951}, { I 0}), \
      And( WriteAttribute( {C CURRENT_MODEL}, {H 0x1294d}, { I 0}), \
      And( WriteAttribute( {C CURRENT_MODEL}, {H 0x12be5}, { I 0}), \
      And( WriteAttribute( {C CURRENT_MODEL}, {H 0x12da4}, { I 0}), \
      And( WriteAttribute( {C CURRENT_MODEL}, {H 0x12da3}, { I 0}), \
      And( WriteAttribute( {C CURRENT_MODEL}, {H 0x12957}, { B FALSE}), \
      And( WriteAttribute( {C CURRENT_MODEL}, {H 0x12a54}, { B FALSE}), \
      And( WriteAttribute( {C CURRENT_MODEL}, {H 0x11ace}, { B FALSE}), \
      And( WriteAttribute( {C CURRENT_MODEL}, {H 0x129f8}, { B FALSE}), \
      And( WriteAttribute( {C CURRENT_MODEL}, {H 0x1280a}, { B FALSE}), \
           WriteAttribute( {C CURRENT_MODEL}, {H 0x11dd8}, { B FALSE})))))))))))))))"

     

    Regards

    Maik



  • 5.  Re: Spectrum Policy Manager

    Posted Jun 09, 2017 05:05 AM

    Hi,

    Thank you very much for sharing this!

    Best regards