DX NetOps

Expand all | Collapse all

Principle of colored status for pipes

  • 1.  Principle of colored status for pipes

    Posted 09-04-2015 04:58 AM

    When one link is down - pipe change it color to red ("Critical" condition), and doesn't matter that another one is up (examle: 10 links in one pipe, one link down - all pipe is red). Is any way to change this action to another. Example, like for Network container: when all models is red, then Network container is orange?



  • 2.  Re: Principle of colored status for pipes

    Broadcom Employee
    Posted 09-07-2015 07:33 PM

    If you want a container then you can put the interface models which are involved in the connections (10 connections will be 20 interface models) into the container. When a connection is down by default one port will get BAD LINK DETECTED red alarm, and another end of the interface model is suppressed. Another alternative is to create Service model that represent the heal of the entire connections between the 2 devices.



  • 3.  Re: Principle of colored status for pipes

    Posted 09-08-2015 08:01 AM

    Hello Roman,

     

    I suggest to use Service manager so that the service (live pipe) is affected based on the condition of various interface models added in the domain. Add the interfaces connected to both ends of the link into a single domain and map this domain to a policy and service.



  • 4.  Re: Principle of colored status for pipes

    Posted 09-17-2015 12:55 PM

    Roman, in case you're using multilink bundles, Spectrum has intelligence for these.  You might be interested in the

    Monitoring Physical and Logical Connections section of this part of the docs:

     

     

    https://wiki.ca.com/display/CASP941/Live+Pipes+and+Fault+Management

     

    Beyond that, this would be a good candidate to post as an idea for new functionality.

     

    Scott