That routes detail command doesn't really give me that much extra info over
the other one.
Could it be that my import at RIPE for my customer AS is set to action
pref=100 instead of 120 is causing this?
Regards,
Rens
-Original Message-
From: Richard A Steenbergen
Hi,
Any design consideration on PPPoE agg routing? Any good example of
covering multiple customers or subnets ?
Thanks,
Devang Patel
And is that the one that traverses the 3550 with the 1500 byte MTU?
Both connection traver through the 3550. I will disable the command on 7206
vxr. thanks
-Original Message-
From: Richard A Steenbergen r...@e-gerbil.net
To: Michael Ruiz mr...@telwestservices.com
Cc: Brian Dickson
Oh you guys are going to love this...Before I could send out the maintenance
notification for tonight to make changes, The session has been up for 21
hours. This is before I could put a packet capture server on the segment.
Sigh
SNIP
BGP state = Established, up for 21:29:25
Last read
On Thu, Sep 17, 2009 at 09:17:00AM -0500, Michael Ruiz wrote:
Oh you guys are going to love this...Before I could send out the maintenance
notification for tonight to make changes, The session has been up for 21
hours. This is before I could put a packet capture server on the segment.
http://cisco.cluepon.net/index.php/Using_capture_buffer_with_ELAM
http://cisco.cluepon.net/index.php/6500_SPAN_the_RP
Well even the IBGP session came up on its own now and has been up for 1
day and 1 hour, I can honestly say this is bizarre situation. I will
use the above links if something like
Recently something seems to have changed with the @txt.att.net email to
SMS gateway. Messages sent through the gateway suffer from the following:
1) Long delay in reaching the phone (intermittent)
(yes I know there is no latency guarantee)
and, even more crippling,
2) Message comes through
Dave Pascoe wrote:
Recently something seems to have changed with the @txt.att.net email to
SMS gateway. Messages sent through the gateway suffer from the following:
1) Long delay in reaching the phone (intermittent)
(yes I know there is no latency guarantee)
and, even more crippling,
On 9/17/2009 at 12:03 PM, Dave Pascoe davek...@gmail.com wrote:
Recently something seems to have changed with the @txt.att.net email to
SMS gateway. Messages sent through the gateway suffer from the following:
1) Long delay in reaching the phone (intermittent)
(yes I know there is no
All,
Today I had yet another cross-connect fail at our colo provider. From
memory, this is the 6th cross-connect to fail while in service, in 4yrs
and recently there was a bad SFP on their end as well. This seemes like
a high failure rate to me. When I asked about the high failure rate,
Michael J McCafferty wrote:
All,
Today I had yet another cross-connect fail at our colo provider. From
memory, this is the 6th cross-connect to fail while in service, in 4yrs
and recently there was a bad SFP on their end as well. This seemes like
a high failure rate to me. When I asked
We have never had a xconnect fail, ever. And we have several. This is over a
6 year period.
William
--Original Message--
From: Michael J McCafferty
To: nanog
Subject: cross connect reliability
Sent: Sep 17, 2009 4:45 PM
All,
Today I had yet another cross-connect fail at our
From: Michael J McCafferty [mailto:m...@m5computersecurity.com]
All,
Today I had yet another cross-connect fail at our colo
provider. From memory, this is the 6th cross-connect to
fail while in service, in 4yrs and recently there was a
bad SFP on their end as well. This seemes like
Hello Michael:
-Original Message-
From: Michael J McCafferty [mailto:m...@m5computersecurity.com]
Sent: Thursday, September 17, 2009 2:46 PM
To: nanog
Subject: cross connect reliability
All,
Today I had yet another cross-connect fail at our colo provider.
From
memory,
Seth Mattinen wrote:
Michael J McCafferty wrote:
All,
Today I had yet another cross-connect fail at our colo provider. From
memory, this is the 6th cross-connect to fail while in service, in 4yrs
and recently there was a bad SFP on their end as well. This seemes like
a high failure rate
On Sep 17, 2009, at 5:52 PM, Seth Mattinen wrote:
Michael J McCafferty wrote:
All,
Today I had yet another cross-connect fail at our colo provider.
From
memory, this is the 6th cross-connect to fail while in service, in
4yrs
and recently there was a bad SFP on their end as well. This
From: Michael J McCafferty m...@m5computersecurity.com
Organization: M5Hosting
Date: Thu, 17 Sep 2009 14:45:36 -0700
To: nanog nanog@nanog.org
Subject: cross connect reliability
All,
Today I had yet another cross-connect fail at our colo provider. From
memory, this is the 6th cross-connect to
Alex Balashov wrote:
Seth Mattinen wrote:
Michael J McCafferty wrote:
All,
Today I had yet another cross-connect fail at our colo provider.
From
memory, this is the 6th cross-connect to fail while in service, in 4yrs
and recently there was a bad SFP on their end as well. This seemes
Marshall Eubanks wrote:
On Sep 17, 2009, at 5:52 PM, Seth Mattinen wrote:
Michael J McCafferty wrote:
All,
Today I had yet another cross-connect fail at our colo provider.
From
memory, this is the 6th cross-connect to fail while in service, in 4yrs
and recently there was a bad SFP on
[lots of stuff deleted].
We've seen cross-connects fail at sites like E and others. Generally
speaking, it is a human-error issue and not a component failure one. Either
people are being sloppy and aren't reading labels, or the labels aren't there.
In a cabinet situation, every cabinet does
We have a winner!
On Thu, Sep 17, 2009 at 5:59 PM, Marshall Eubanks t...@americafree.tvwrote:
Or until someone pulls out the wrong cable (which has happened to me).
Regards
Marshall
~Seth
Hello All,
Any scenario where we are using MPLS between PE-CE when CE is multi-vrf
router, any deployment in real word? Carrier supporting carrier CSC is one
where you have MPLS between PE-CE link.
If PE-CE running MPLS between them then what will be impact on MULTICAST
between two site?
If PE-CE
On 09/17/2009 06:37 PM, Deepak Jain wrote:
[lots of stuff deleted].
A famous one that can happen with some techs is that they make jumpers
from solid wire with generic rj45 plugs (yes, I've seen this recently
from several folks who should know better). These will last somewhere
around a
Not really. That's all too easy to diagnose and fix. Poorly terminated
and or mistreated cabling is far more likely. I wrote a long post about
all the crap termination and poor treatment I've seen...but canceled the
message.
On Thu, 17 Sep 2009, Mike Lieman wrote:
We have a winner!
On
Because no-one is stealing pairs anymore?
On Thu, Sep 17, 2009 at 7:23 PM, Jon Lewis jle...@lewis.org wrote:
Not really. That's all too easy to diagnose and fix. Poorly terminated
and or mistreated cabling is far more likely. I wrote a long post about all
the crap termination and poor
In message 20090917234547.gt51...@gerbil.cluepon.net, Richard A Steenbergen w
rites:
On Thu, Sep 17, 2009 at 03:35:37PM -0700, Charles Wyble wrote:
Random failures of a single ports connectivity bizzare and annoying.
Whole switches? Seen it.
Whole panels? Seen it.
Whole blades?
26 matches
Mail list logo