[c-nsp] Monitoring failed state of DSL / Cable (Ethernet)interfaces

Josh Duffek consultantjd16 at ridemetro.org
Tue Mar 1 15:10:47 EST 2005


Interesting.

josh duffek    network engineer
consultantjd16 at ridemetro.org

> -----Original Message-----
> From: Rodney Dunn [mailto:rodunn at cisco.com]
> Sent: Tuesday, March 01, 2005 2:05 PM
> To: Josh Duffek
> Cc: Luan Nguyen; Brian Feeny; cisco-nsp
> Subject: Re: [c-nsp] Monitoring failed state of DSL / Cable
> (Ethernet)interfaces
> 
> Nothing ever got put in under that
> bug.
> 
> All the feature documenation went in under
> SAA and Object tracking for PBR.
> 
> Search on CCO for that information to
> get details.
> 
> A ddts # for a feature only would give you where
> it's put in the code in the first place but that
> doesn't mean that's where it was officially supported.
> 
> Rodney
> 
> On Tue, Mar 01, 2005 at 01:58:38PM -0600, Josh Duffek wrote:
> > It's the feature request bug that I submitted for this a few years
ago.
> > I used to have notes on when it got added into IOS but I lost those.
I
> > have some info on the feature but its internal only stuff that at
this
> > point I shouldn't even have :)
> >
> > Thanks,
> >
> > josh duffek    network engineer
> > consultantjd16 at ridemetro.org
> >
> > > -----Original Message-----
> > > From: Luan Nguyen [mailto:luan.nguyen at mci.com]
> > > Sent: Tuesday, March 01, 2005 1:55 PM
> > > To: Josh Duffek; 'Brian Feeny'; 'cisco-nsp'
> > > Subject: RE: [c-nsp] Monitoring failed state of DSL / Cable
> > > (Ethernet)interfaces
> > >
> > > What is that CSCds88143?  I can't bring this up using the bug
toolkit.
> > >
> > > Thanks.
> > >
> > > luan
> > >
> > > -----Original Message-----
> > > From: cisco-nsp-bounces at puck.nether.net
> > > [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Josh
Duffek
> > > Sent: Tuesday, March 01, 2005 1:21 PM
> > > To: Brian Feeny; cisco-nsp
> > > Subject: RE: [c-nsp] Monitoring failed state of DSL / Cable
> > > (Ethernet)interfaces
> > >
> > > Need to get an image that has CSCds88143.  Something like 12.3T or
> > > better I think.
> > >
> > > Thanks,
> > >
> > > josh duffek    network engineer
> > > consultantjd16 at ridemetro.org
> > >
> > > > -----Original Message-----
> > > > From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-
> > > > bounces at puck.nether.net] On Behalf Of Brian Feeny
> > > > Sent: Tuesday, March 01, 2005 12:10 PM
> > > > To: 'cisco-nsp'
> > > > Subject: [c-nsp] Monitoring failed state of DSL / Cable
(Ethernet)
> > > > interfaces
> > > >
> > > >
> > > > I have a configuration where I am load balancing default routes
over
> > 2
> > > > WAN interfaces.
> > > >
> > > > One interface is a T1 and the other is an ethernet interface
plugged
> > > > into a DSL / Cable bridge.
> > > >
> > > > My concern is that if the connectivity goes down on the Cable /
DSL
> > > > then the interface
> > > > may stay up, since the ethernet connection may still look good.
> > > >
> > > > I think some of you are using SAA stuff to deal with his, does
> > anyone
> > > > have any links on this?
> > > >
> > > > Basically I just want to check the next hop and if its down,
then
> > pull
> > > > the route.
> > > >
> > > > Brian
> > > >
> > > > ---------------------------------------------
> > > > Brian Feeny, CCIE #8036, CISSP
> > > > Network Engineer
> > > > ShreveNet Inc.
> > > >
> > > > _______________________________________________
> > > > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > > > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > > > archive at http://puck.nether.net/pipermail/cisco-nsp/
> > >
> > > _______________________________________________
> > > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > > archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
> >
> > _______________________________________________
> > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/



More information about the cisco-nsp mailing list