On Thursday 04 February 2010 05:11:49 am Peter Kranz wrote:
So in terms of enabling MPLS on a fully meshed set of
routers running BGP and OSPF..
Here are the general steps I believe;
#conf t
Tag-switching advertise-tags
!
Int g0/0
Mtu 9216
Tag-switching ip
!
Be very
On 02/02/2010 18:13, Peter Kranz wrote:
The network is composed of 6509-e chassis with SUP 720 3BXL cards at all
sites..
So far respondents have recommended the following options; (so many ways to
skin this cat..!)
EoMPLS
Cisco Resilient Ethernet Protocol (REP)
802.17 (RPR)
Spatial
AFAIK, SRP was implemented/available in 12K's and 7200's, I used it in a
cmts environment. This was 5 years ago, not sure about the offering
nowdays.
On Wed, Feb 3, 2010 at 4:16 AM, Nick Hilliard n...@inex.ie wrote:
On 02/02/2010 18:13, Peter Kranz wrote:
The network is composed of 6509-e
So in terms of enabling MPLS on a fully meshed set of routers running BGP
and OSPF..
Here are the general steps I believe;
#conf t
Tag-switching advertise-tags
!
Int g0/0
Mtu 9216
Tag-switching ip
!
However, what can I expect to happen when this is done, i.e. will
On 02/01/2010 08:59 PM, Peter Kranz wrote:
Currently in our network we use dot1Q trunks to forward end-user/customer
VLANs from Site A to Site B to provide them virtual point-to-point circuits
between data centers without the overhead of some type of VPN tunnel.
However if one of our backhauls
@puck.nether.net
Subject: Re: [c-nsp] Layer 2 VLAN advice..
On 02/01/2010 08:59 PM, Peter Kranz wrote:
Currently in our network we use dot1Q trunks to forward
end-user/customer VLANs from Site A to Site B to provide them virtual
point-to-point circuits between data centers without the overhead of some
On Wednesday 03 February 2010 02:13:03 am Peter Kranz wrote:
The network is composed of 6509-e chassis with SUP 720
3BXL cards at all sites..
Oh that will do MPLS quite nicely :-).
Of course, as someone else already mentioned, it means
enabling MPLS in the network if you don't already have
Currently in our network we use dot1Q trunks to forward end-user/customer
VLANs from Site A to Site B to provide them virtual point-to-point circuits
between data centers without the overhead of some type of VPN tunnel.
However if one of our backhauls between data centers fails, we would desire
On Tuesday 02 February 2010 04:59:55 am Peter Kranz wrote:
It seems like there are a lot of different approaches to
provide some level of self-healing/redundancy to these
layer2 services we offer, I am interested in advice on
which would be most straightforward to implement on top
of our
Mark Tinka wrote:
If you can support MPLS, I'd recommend that for a self-
healing control plane to transport Ethernet frames.
Else, STP (or some flavor of it) or your vendor's incarnate
of the same are your other options.
Or EAPS if your kit does it.
On 2/1/10 12:59 PM, Peter Kranz pkr...@unwiredltd.com wrote:
Currently in our network we use dot1Q trunks to forward end-user/customer
VLANs from Site A to Site B to provide them virtual point-to-point circuits
between data centers without the overhead of some type of VPN tunnel.
However
11 matches
Mail list logo
