The MPLS-OPS Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] RE: How do you monitor client VPN devices
Not clear how Netflow could be used to "monitor" a CPE ,could U pls elaborate . Brgds >From: "Thomas D. Nadeau" <tnadeau@cisco.com> >Reply-To: <tnadeau@cisco.com> >To: "'Yuly Milner'" <ymilner@unistars.lv>, <mpls-ops@mplsrc.com> >Subject: RE: [MPLS-OPS]: How do you monitor client VPN devices >Date: Fri, 16 May 2003 09:15:47 -0400 > > > > In general, there are several options for you: > > 1) SAA probes to monitor jitter/delay/CV. > 2) LSP ping/trace > 3) MIBs (PPVPN-MPLS-VPN MIB, IF-MIB, > other MPLS MIBs). > 4) Netflow > > It might help if you can provide more >specifics about what you mean by "monitor the >customer's devices" in terms of how the customer >devices are connected to the PE and other such >things. > > --Tom > > > Hello, > > > > We have a L2/L3 MPLS VPN-capable network, cisco-based. > > I wonder what possibilities to monitor availability of CPEs are. > > > > We have a NOC, which resides in system routing segment. From > > there we can test availability of our devices (like WLL > > terminals, since our network is based on wireless equipment). > > We need to monitor the customer's devices, which reside in > > respective VRFs. What are the options of doing it? Can > > someone share his/her experience? > > > > Thanks > > > > Yuly > > > > ------- > > 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 _________________________________________________________________ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail ------- The MPLS-OPS Mailing List Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml Archive: http://www.mplsrc.com/mpls-ops_archive.shtml |
|