MPLS Link Monitoring

[tndrc.try]

Hi,

CA SpectrumMPLS Transport Manger discovery Not happening configuration Item creation to MPLS link

 

   We using two MPLS link. Both are connected as a following method.

   

      Access SW -> Cisco SW -> Multiplexer -> Fiber Link -> Multiplexer-> Cisco SW -> Access SW

 

Cisco switch have no IP, it act as only pass through device.

 

Two Links are connected to Access switch with LACP Method. If one link down means network flow through another link

automatically. We able to monitor only the access switch through IP. If Cisco switch down means only access switch port will down.Otherwise access switch port will not down, if one MPLS link goes down means also.

We are got alarm when both link goes down means communication between two end stoped.

 

But we need, if anyone link goes down means to get alarm. If any options are available to monitor the link as  per bandwidth speed or other options.

 

 

Regards,

Bala.

[AMISH03]

Hello Bala,

 

I will suggest you to enable the port level monitoring. Their are few attributes, which you need to enable. Please refer the below tech doc:

 

Port/Interface alarming in CA Spectrum when a port/interface model goes down 

 

HTH

Amit

[tndrc.try]

Hi Amit,

   The document says, If port or interface goes down means only generate alarm. In my setup port never goes to down,  service only down.

 

We have LACP with two link. So one link down means traffic flow on other link.

 

The ok_to_poll, PollPortStatus and GeneratePortStatusAlarms are raise alarm on when port or interface fail to respond.

 

So when both links are goes down means only we getting alarm on above mentioned concepts.

 

 

 

Regards,

Bala

[Glenn Shoemake]

Hi Bala,

 

Are you using Spectrum MPLS Manager to monitor the MPLS connections?  Are the MPLS connections being modeled after doing an MPLS Manager discovery?  If not please follow these steps:

 

Steps to check for MPLS devices not being discovered through MPLS Manager

 

1. Check to make sure Layer 2 discovery connections are present  
2. Check for rfc3812app models to make sure they have been created for the devices on the Application Models from Locater
3. Check these attributes via the MIB MPLS-TE-STD-MIB to make sure they have values and are not 0 from MibTools on the MPLS devices.

 

mplsTunnelConfigured

mplsTunnelIsIf

mplsTunnelRole

mplsTunnelAdminStatus

mplsTunnelOperStatus

mplsTunnelRowStatus

 

Best Regards,

Glenn