The MPLS-OPS Archive

[Jerome Law <Jerome.Law@vanco.co.uk>]

Title: RE: [MPLS-OPS]: Customer VPN Convergence

It has to do with a number of factors such as whether you are doing QoS/CoS which has an impact on the router's performance in terms of routing, and also depending on who the provider is and whether you have global coverage as opposed to a local incumbent who can provide local connectivity.

-----Original Message-----
From: Yakov Rekhter [mailto:yakov@juniper.net]
Sent: 23 March 2003 02:54
To: Russell, David
Cc: 'mpls-ops@mplsrc.com'
Subject: Re: [MPLS-OPS]: Customer VPN Convergence

Russell,

> Hi,
>
>   Has anyone got any convergence time data for MPLS VPN (2547) networks from
> the customer's point of view?  Assume that a company has 100 sites world
> wide connected to a provider's MPLS network and that there is a routing
> table of about 500 entries and the failure is the CE-PE link.  What is the
> time for another site to detect the failure and the time to detect that it
> has been restored?
>
> Is it safe to assume that most providers have sub-second times to resolve
> internal failures?

I think that the answer to you question is going to be implementation
specific.

Yakov.

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

**********************************************************************
Any opinions expressed in the email are those of the individual and 
not necessarily the company. This email and any files transmitted with
it are confidential and solely for the use of the intended recipient.  
If you are not the intended recipient or the person responsible for 
delivering it to the intended recipient, be advised that you have 
received this email in error and that any dissemination, distribution, 
copying or use is strictly prohibited.

If you have received this email in error, or if you are concerned with
the content of this email please e-mail to: 
e-security.support@vanco.co.uk

The contents of an attachment to this e-mail may contain software 
viruses which could damage your own computer system. While the sender
has taken every reasonable precaution to minimise this risk, we cannot
accept liability for any damage which you sustain as a result of 
software viruses. You should carry out your own virus checks before 
opening any attachments to this e-mail.
**********************************************************************