From: Richard Dumoulin (Richard.Dumoulin@vanco.fr)
Date: Sat Sep 10 2005 - 22:15:02 GMT-3
For OSPF I am referring to the fact that MPBGP is able to carry LSA type,
cost etc... So the migration to MPLS is almost transparent. I am not aware
of this for ISIS
-- Richard
-----Message d'origine-----
De : Scott Morris [mailto:swm@emanon.com]
Envoyi : dimanche 11 septembre 2005 01:29
@ : Richard Dumoulin; ccielab@groupstudy.com
Objet : RE: Cisco MPLS
Very true, and the world works on the concept of next-hop visibility. From
PE to PE you're fine. You can have label in label as well, which is really
the path for making your P routers agnostic.
OSPF supports the necessary digs for MPLS as does IS-IS.
Scott
_____
From: Richard Dumoulin [mailto:Richard.Dumoulin@vanco.fr]
Sent: Saturday, September 10, 2005 5:06 PM
To: 'Scott Morris'; ccielab@groupstudy.com
Subject: RE : Cisco MPLS
Scott, yes I know but a label is only created once a route is present in the
routing table although in the end only label switching is done. What I find
wonderful is their behaviour for BGP routes. I have not read the RFC and I
do not know if they mention this as a requirement. It might just be a Cisco
trick and the way Cisco routers function.
So in a Juniper P router the BGP routes do not appear? This was my original
question.
The fact is that there are a lot of MPLS improvement done by Cisco and this
might prove very important when choosing a provider or another. For example
in MPLS VPN, the superbackbone OSPF stuff is really nice. I have heard of a
big enterprise that chose Cisco because they could migrate to MPLS almost
transparently without having to redesign their routing.
Regards
-- Richard
-----Message d'origine-----
De : Scott Morris [mailto:swm@emanon.com <mailto:swm@emanon.com> ]
Envoyi : samedi 10 septembre 2005 21:56
@ : Richard Dumoulin; ccielab@groupstudy.com
Objet : RE: Cisco MPLS
I'm not sure if I'm missing the point of the question here (didn't get much
sleep last nite), but it's not a requirement that your P routers have a full
routing table. In a true MPLS network, the core will really just be moving
LSP information back and forth and just need to know internal information
only. Your PE devices are those that are interconnected and will/may be
doing an L3 lookup.
This is a design concept, and not really indicative of any one vendor's
capabilities. I've done it/seen it on Juniper networks as well as on Cisco
ones. So it's just whatever you desire to do in the end. :)
Scott
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com
<mailto:nobody@groupstudy.com> ] On Behalf Of
Richard Dumoulin
Sent: Friday, September 09, 2005 5:03 PM
To: 'ccielab@groupstudy.com'
Subject: Cisco MPLS
There is a feature in MPLS that I find powerful and it is the possibility of
building an Internet backbone with 160000 routes present only in the PEs
routing table. I was wondering if this was only a Cisco feature or do the Ps
of other vendors also support this like Juniper for example?
Thx
-- Richard
**********************************************************************
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.info
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.
**********************************************************************
This archive was generated by hypermail 2.1.4 : Sun Oct 02 2005 - 14:40:14 GMT-3