The MPLS-OPS Archive

[Roger Clark Williams <rogerw@nordlink.com>]

Paolo, as I understand it, the way Cisco's VPNSCv2 or the newly released 
ISCv3 monitors is to look at the VRF tables. If there is routing 
information in the tables that fits with the VPN setup, the software 
assumes a functioning VPN and the audit is successful. If there is no 
routing information, it assumes a non-functioning VPN and the audit fails, 
giving an error message to the operator. This is not real-time monitoring, 
but it is monitoring of the functionality of the VPN. I am sure there are 
SNMP methods as well, I just don't know what they are specifically.

I hope this helps

Roger Williams


>X-MindSpring-Loop: rogerw@nordlink.com
>Resent-Date: Wed, 21 May 2003 18:05:00 -0400
>X-Authentication-Warning: host.secure4-hosting.net: mplsrc12 set sender to 
>mpls-ops-request@mplsrc.com using -f
>Sender: pecchi@smtp3-cm.mail.eni.net
>Date: Wed, 21 May 2003 14:42:29 -0700
>From: Paolo Pecchi <ppecchi@epoch.net>
>Organization: Epoch Internet
>X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.8 sun4u)
>X-Accept-Language: en
>To: mpls-ops@mplsrc.com
>Subject: [MPLS-OPS]: MPLS/VPN monitoring
>Resent-From: mpls-ops@mplsrc.com
>X-Mailing-List: <mpls-ops@mplsrc.com> archive/latest/5825
>X-Loop: mpls-ops@mplsrc.com
>Resent-Sender: mpls-ops-request@mplsrc.com
>Resent-Bcc:
>
>Hi everybody,
>
>does somebody out there know of a tool
>to integrate eventually with Openview-NNM, or independent from it,
>to monitor MPLS/VPNs ?
>
>Many tools or suggestions I read about it, are related to inject the 
>Monitoring
>Network
>ip address inside the VPNs, and 'bla bla', to be able to 'ping' the CPE
>sites.
>
>I don't think this can be considered as 'VPN monitoring'.
>
>In fact that technique lets the Monitoring Station monitor
>the reachability of the sites from the Monitoring Station, but there is no
>  garantie that those sites are able to reach the other ones
>(if the MPLS/VPN is a full mesh VPN).
>  To accomplish that, I think the monitoring station
>  needs to monitor the Label Switch Paths (LSPs) for each VPNs.
>
>The entity to monitor is 'reachabilty among sites', that is defined in
>the routers with LSPs, so the Monitoring Tool needs to be MPLS/VPN aware,and
>be able 'to trace' the LSPs for the single VPNs.
>
>Does somebody have knowledge of such tool? some ideas how to accomplish it?
>
>Thank you in advance for your answers
>
>Paolo
>
>--
>Paolo Pecchi
>Backbone Engineering
>Sr. Network Engineer
>HP-Openview NNM Certified Consultant
>Epoch Internet
>
>-------
>The MPLS-OPS Mailing List
>Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
>Archive: http://www.mplsrc.com/mpls-ops_archive.shtml

-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml