Not that i recognize the error but with with the early sup8s i learned to
always upgrade the rommon first. Also upgrade using REAL power cycle not
a reload.
I know - sounds like nonsense, unfortunatelly backed by number of TAC
cases...
-pavel
On Tuesday, 11 October 2016, Sebastian Beutel <
sebas
James,
So all your customers are on 6708?
Why thing you can try is check the internal architecture of the 6708 cards
especially the egress replication asic.Probably also depends on which ports
you have the customers connected...
-pavel
Dňa 13.10.2016 18:44 používateľ "Matthew Huff" napísal:
>
Hi Guys,
I have issues in VPLS network where we get loop sometimes because of mac
flood from customer side and sometimes because of media loop in last mile.
Being a service provider what are the best practices which I could
implement on my PE Router or PE switch or in transmission equipment to
avo
On Mon, Oct 17, 2016 at 9:20 AM, Zahid Khan wrote:
> I have issues in VPLS network where we get loop sometimes because of mac
> flood from customer side and sometimes because of media loop in last mile.
> Being a service provider what are the best practices which I could
> implement on my PE Rout
> I have issues in VPLS network where we get loop sometimes because of mac
> flood from customer side and sometimes because of media loop in last mile.
> Being a service provider what are the best practices which I could
> implement on my PE Router or PE switch or in transmission equipment to
> avo
Lukas Tribus wrote:
> Don't use VPLS, but L3VPN's. Like Ivan says: "VPLS is not aspirin" [1].
yeah, seriously. L2 loops in VPLS networks are an endemic problem
because you normally end up bridging multiple separate layer 2 domains
together which run different bridging protocols. This is a recipe
On 17/Oct/16 16:22, Lukas Tribus wrote:
>
> You probably don't want to hear this, but:
>
> Don't use VPLS, but L3VPN's. Like Ivan says: "VPLS is not aspirin" [1].
I tend to agree.
I've been telling customers (including product managers and sales folk)
since 2009 that you're better off taking a
On 17/Oct/16 16:40, Nick Hilliard wrote:
>
> yeah, seriously. L2 loops in VPLS networks are an endemic problem
> because you normally end up bridging multiple separate layer 2 domains
> together which run different bridging protocols. This is a recipe for
> disaster and it is totally unsurpris
Hi Pavel
obviously not, as you see from previous email market is connected to an
ASR. then there is a C6807 and the only customer currently requesting this
huge mcast feed is connected to C6500 with a WAN link...
I've attached my hw configuration, facing my cisco knowledge it shouldn't
be an issue
Good Afternoon Masters of the BGP,
I am not good at BGP regex.
I need to come up with an ip as-path access-list that will only accept customer
routes that belong to a certain provider, the ISP in question does not have a
way of differentiating, so I was hoping to use a regex.
So for example if
Most SP’s support community tags of their directly connected customer prefixes.
That may be your path of lease resistance.
--
inoc.net!rblayzor
XMPP: rblayzor.AT.inoc.net
PGP Key: 78BEDCE1 @ pgp.mit.edu
> On Oct 17, 2016, at 4:14 PM, Nick Cutting wrote:
>
> Good Afternoon Masters of t
On Mon, Oct 17, 2016 at 08:14:07PM +, Nick Cutting wrote:
> If 55 and 56 are Customer AS's connected to AS 100 (our ISP)
> need to allow:
>
> 100 55 i
> 100 56 i
>
> Or 100 55 55 55 I (to allow for prepending)
>
> But NOT
>
> 100 55 something else
>
> Is this possible?
> Any help greatly a
Thank you for your answer.
The problem is I do not know the ASN's of the ISP's customers.
Robert - I am afraid that this particular ISP does not have a community for
this, nor can they send me just their customer routes.
From: Brandon Ewing [mailto:nicot...@warningg.com]
Sent: Monday, October 17
--- Begin Message ---
- Original Message -
From: Nick Cutting
To: Brandon Ewing ; "cisco-nsp
(cisco-nsp@puck.nether.net)"
Sent: Monday, October 17, 2016 4:32 PM
Subject: Re: [c-nsp] BGP Regex to allow ISP customers
Thank you for your answer.
The problem is I do not know the ASN's of t
It's been a while but, the following might do it
^(100_)+([0-9_]+)(_\2)*$
It matches any customer of 100 also accounting for case where both 100 and
customer are prepending.
On Tue, Oct 18, 2016 at 2:28 AM, Randy via cisco-nsp <
cisco-nsp@puck.nether.net> wrote:
> _
That should be
^(100_)+([0-9]+)(_\2)*$
But the above should* work as well...
On Tue, Oct 18, 2016 at 3:31 AM, Dragan Jovicic wrote:
> It's been a while but, the following might do it
>
> ^(100_)+([0-9_]+)(_\2)*$
>
> It matches any customer of 100 also accounting for case where both 100 and
> c
On Mon, 17 Oct 2016, Nick Cutting wrote:
Thank you for your answer.
The problem is I do not know the ASN's of the ISP's customers.
Robert - I am afraid that this particular ISP does not have a community for
this, nor can they send me just their customer routes.
Since you don't know the ISP's
Hi,
Have an interesting(unexpected) situation on an ASR920 that is running ospf /
frr(rLFA) to a number of other ASR920's (All running sopf / frr(rLFA)but it
also has a non-frr(rLFA) link to a 7200, which also has a non-frr(rLFA) link
back to the other ASR920's (So bascially a triangle topo
Thanks Aaron, Lukas, Mark and Nick for your valuable feedback.
Unfortunately my client is not agreeing to share any routing with ISP(us).
We are looking into option to explore creation of p2p pseudo-wire but this
will involve major design changes in customer end design and latency will
also increa
19 matches
Mail list logo
