1. IS-IS in a single area can handle thousand(s) of routers in a "stable"
manner. OSPF can handle hundreds, which is great, but perhaps not the best
choice for a service provider architecture. The "single area" idea can be
thought of as a typical representation of a service provider network. Flat
access for customers.
2. Yes and no. :) There is a NEW card for the IGX, it has been announced,
but you'd have to talk to your local SE about availability. It's a card
that allows an LSR as part of the IGX. Do you ONLY have IGXs in your
network? The BPX can already pair with a 7200/7500 to act as an LSC/LSR.
3. Haven't got a clue. Hopefully someone else will chime in.
4. For dialup users, I would strongly suggest taking a look at integrating
an L2TP solution into your network. That will tunnel the Layer 2 PPP stuff
back to a customers' "home" network, and in tunneling the data, you'd hop
right in to the MPLS fabric.
Scott
-----Original Message-----
From: Vinod Anthony Joseph Cherunni [mailto:vac@dsqworld.com]
Sent: Tuesday, November 07, 2000 7:04 AM
To: cisco-nsp@puck.nether.net
Subject: [nsp] REG: MPLS Traffic engineering
Hi All,
Thanks once again for your valuble help. I am sorry for taking up so much
of your time, Kindly pls clarify a few points mentioned.
1.I understand flooding the entire network topology with IGP updates is'nt
scalable. What would be the right approach for a service provider with OSPF
as the IGP, designed with multiple areas to offer end-end MPLS VPN
services. Is it migrating to IS-IS?
("IS-IS networks tend to be a single much larger level, rather than several
small areas like OSPF has"). Kindly explain a little on this.
2. Are the Cisco IGX series switches MPLS ready? Since they are only layer
2 devices (FR/ATM), what will be the usefulness of being MPLS ready.
Because I feel it makes better sense for providers to use the BPX series,
which provide Layer 2 & Layer 3 functions built in. This will provide a
transparent view of the network to routing protocols, which are generally
hidden in ATM networks, Correct me if I am wrong? Just trying to see what
will fit in for our SP network.
3. This question is just out of the way, While offering MPLS VPN
services,what is the mathematical formulae for understanding how bandwidth
and distance relate to ping response times. How will it be possible to
offer an MPLS VPNs & commit on roundtrip times.
4. Another long standing confusion on how do we provide MPLS services for
mobile users, providing a dialup user seamless access to his corporate site
without using any encryption like IPSEC etc. Is it possible to do so
similar to doing it on leased circuits.
5. And lastly, While providing Internet access for a VPN customer, As
mentioned if I provide a default route in the global table, How does the
route statement apply, I mean how will I ensure that destination prefixes
that are not allowed to be routed for a particular customer do not choose
the global static route. For eg If VPN customer A is only authorized to
access destination prefix "192.168.100.0" which is part of his Intranet, &
if he tries to access another another prefix say "172.27.135.0", Will the
global table having the default route be referenced?
Kindly advice,
With warm regards,
Vinod.
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:20 EDT