Subject: Enterprise network as an ISP with a single huge customer Date: Fri,
Jun 12, 2015 at 08:08:29PM +0300 Quoting Stepan Kucherenko (t...@megagroup.ru):
Hello,
I'm sure lots of you work for big enterprises, and some of you work
for biggest of them.
How many of you architect your
On 12/Jun/15 19:08, Stepan Kucherenko wrote:
How many of you architect your network as an ISP, with that enterprise
as the biggest customer ? Office networks in l3vpn, VPLS/EVPN on top
of your own network for DCI, etc ? Or is it usually just a single IGP
domain with no unnecessary bells
On 13 Jun 2015, at 17:49, Randy Bush wrote:
i have seen many universities and large enterprises with as much clue
as your serious isp.
I've seen a few, but not many. All of the ones I've seen who fall into
that category operate significant public-facing infrastructure, so they
have
In my subjective experience, relatively few enterprises have the
technical and operational savvy to design, deploy, operate, and
troubleshoot a network designed in such a manner, or even understand
the appropriate usage of these technologies, much less reap the
benefits thereof.
i have seen
On 13 Jun 2015, at 10:00, Tim Raphael wrote:
There are plenty of people out there that will use MPLS / multiple
tables for the wrong reasons just so they can say that's what they're
doing.
Concur 100%.
I also agree with both Chris and with Randy with regards to pros and
cons of this
it's nice to have the tools to segregate traffic/users/things...
mpls/etc is one method to do that... I don't know that many
enterprises pursue this path though :( which is sad (I think).
i have seen a lot of this done with firewall devices and vlans. with
vlans or mpls, you can make
It will also depend greatly on the knowledge of the design team / person and
the operations team. If the designer is ex-SP or has a strong knowledge of both
SP and Enterprise then yes, a good design may result.
There are plenty of people out there that will use MPLS / multiple tables for
the
On Fri, Jun 12, 2015 at 10:04 PM, Randy Bush ra...@psg.com wrote:
it's nice to have the tools to segregate traffic/users/things...
mpls/etc is one method to do that... I don't know that many
enterprises pursue this path though :( which is sad (I think).
i have seen a lot of this done with
i have seen a lot of this done with firewall devices and vlans. with
vlans or mpls, you can make spaghetti without wires, one wheat and one
semolina.
oh absolutely. you can use many tools to lop off your fingers, my
point was that things like mpls (or vlans) provide a nice other tool
to
On Fri, Jun 12, 2015 at 1:08 PM, Stepan Kucherenko t...@megagroup.ru wrote:
Hello,
I'm sure lots of you work for big enterprises, and some of you work for
biggest of them.
How many of you architect your network as an ISP, with that enterprise as
the biggest customer ? Office networks in
13.06.2015 05:35, Randy Bush wrote:
i have seen a lot of this done with firewall devices and vlans. with
vlans or mpls, you can make spaghetti without wires, one wheat and one
semolina.
oh absolutely. you can use many tools to lop off your fingers, my
point was that things like mpls (or
What I have done is leverage the production data center redundancy to
provide connectivity services to any nearby offices in the same region,
basically using our colo as the office ISP for internet connectivity but as
far as doing vpls services and the like, it has been so far cheaper to
contract
12 matches
Mail list logo