How to generate an alarm in OneClick when the Multiplexer goes down at the ISP end.


Article ID: 50178


Updated On:


CA Spectrum



Clients may have redundant multiplexer's (Mux) at their ISP end and expect an alarm in OneClick when any of the Mux at ISP end goes down.

Something like the below connection:

Router1 -> L2 Switch -> Mux -> WAN Link -> Mux -> L2 Switch -> Router2.

If there is only one Mux at the ISP end and if it goes down, the other end router will not be reachable indicating that something has gone wrong at ISP end. In the topology if there is a redundant Mux the other end router will be reachable even if the primary Mux goes down. In this case we may not have a proper root cause as the Mux from the ISP cannot be discovered in Spectrum as a model to alarm on it. This problem can be solved by representing the Mux as a WAN Segment model and using Condition Correlation Editor.


BGP is a requirement and must be enabled on the end routers connected to the WAN Link so that in the event of an outage we get a BGP peer session lost alarm on the end router interface connected to ISP when the primary Mux goes down.

Create a WAN Segment for the Mux model using the below process in OC and connect this WAN Segment to both ends of the router interfaces which are connected to the WAN Link.

To manually create a WAN Link between two end devices:

  1. Go to the container where you have the end devices.(Router1-L2 switch and Router2- L2 switch). Use Model By Type and select WAN Link model type to create WAN Link model.

  2. Navigate into the WAN Link model you just created.

  3. In the WAN Link model use Model By Type and select WAN Segment model type to create WAN Segment model.

  4. On the new WAN Segment, right click and select Start Connection.

  5. Now, navigate out to one of the end devices you want to connect.

  6. In Component Details, Interface tab, right click on the interface you want the connection on.

  7. Select Connect with <WAN Segment name>.

  8. Go to the other end device and do the same; find the interface on the other side of the connection and Select Connect with <WAN Segment name>.

    Now you should see the WAN Link with connections to both end devices(Router1 and Router2).

    Please remember you should never have more than one WAN Segment model created per WAN Link.

    Now when the Primary Mux goes down we get BGP peer session lost alarm on the router interfaces connected to the WAN Link. And when the Mux is up again we get the BGP session established alarm on the interface connected to the WAN Link.

    1. Now we created one new event in the Event Configuration Editor for alarming on the WAN Segment.

    2. We created a clear event for the alarm generated using step 1.

    3. Note the event codes for the BGP session established/lost events.

    4. Created 2 conditions using condition correlation editor, one for BGP alarm and other for Mux down (set/clear events will be the events created in step1/2) using condition correlation editor.

    5. We created one WAN Link container in OneClick and added a model of type WAN Segment.

    6. We created the Rule in CCE like the below

      Symptoms Condition:
      Model Active, BGP Condition.

      Root Cause Condition:
      Mux Condition


      Root Cause Target:
      Condition:Model Active
      Parameter : Model

      Rule Criteria:

      Left Operand:

      Parameter: ModeltypeHandler

      Equals to

      Right Operand:
      By value
      Give the Modeltypehandler of the WAN segment
      Select the parameter as String.

    7. Now we generated the BGP peer session lost event on the Port model which in turn triggered the Mux down events on the WAN Segment.

    8. When the BGP peer session lost alarm is received on the port model, the BGP condition is triggered in CCE which in turn triggers the Mux condition which in turn calls the set event in this condition and triggers an alarm on the respective WAN Segment.


Component: SPCAEM