The MPLS-OPS Archive
[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index]
Re: Cisco or Juniper BGP/MPLS VPN for CSC using IPv4BGP label distribution]
-
From: online <johnliu@online.sh.cn>
-
Date: Fri, 19 Jul 2002 10:01:10 +0800
-
CC: mpls-ops@mplsrc.com
-
Resent-Date: Thu, 18 Jul 2002 23:07:48 -0400
-
To: elkou141061@hotmail.com
Hi,
I have some practical reports in http://johnliu.chinaquest.com, as
a minor demo for Mr.Rajiv Asati's excellent explaination.
Best Regards,
Liu Jun
Hi For the case that customer carrier
sites is pure IP .Customer carrier say CSC-CE1 is advertising internal
route (/32) in site 1 tobackbone carrier CSC-PE1 using IPV4BGP label
distribution . Case 1 : Those internal routes are part of the
IGP and using BGP "network" statements on CSC-CE1 to be included
in the BGP table . Is CSC-CE1 advertise :1) a different label value
to each internal routesOr2)"Implicit_Null" as label for all internal routes
. If "1" : At CSC-CE1 what wil be the label action assigned .
is it A- "Untag"
Or
B- "Aggregate" . Case2 : Each node in Site1 will have L0 amd
L1 address . L0 is known via the IGP but not L1 . Each node propagate
L1 through iBGP full mesh (all nodes in site1 run iBGP) CSC-CE1
will propagate L1's for all internal nodes to CSC-PE1 . Same
enq as case1 ,ie: CSC-CE1 behaviour as "1A" ,"1B" or "2" . Case2
is included to see if the internal routes are leraned through
different way (IGP or iBGP) will influenece CSC-CE1 behaviour .
I guess that all ( "1A","1B" or "2") are workable ,but "1B" is less
efficient than "2" and "1A" is better than "2" . Iintersted to know
what the method selected by the major manufacturer . Brgds
Join the world’s largest e-mail service with MSN Hotmail. Click
Here
------- 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
| |
|