[c-nsp] Ethernet Question - Problem with link

[Michael Malitsky]

Did you use a cross-over cable?

Michael

> Message: 1
> Date: Wed, 24 Oct 2007 06:50:05 -0400
> From: "Paul Stewart" <paul at paulstewart.org>
> Subject: Re: [c-nsp] Ethernet Question - Problem with link
> To: "'Mike Louis'" <MLouis at nwnit.com>, "'Pete Templin'"
> 	<petelists at templin.org>
> Cc: cisco-nsp at puck.nether.net
> Message-ID: <000501c8162b$a419faf0$ec4df0d0$@org>
> Content-Type: text/plain;	charset="us-ascii"
> 
> Thanks - yes VLAN exists and no changes to VLAN database 
> recently other than
> adding this new VLAN.... it's on an access port which is 
> trunked out on
> another port...
> 
> Paul
> 
> 
> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net
> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Mike Louis
> Sent: Wednesday, October 24, 2007 12:42 AM
> To: Pete Templin
> Cc: cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] Ethernet Question - Problem with link
> 
> Is there vlan configured on the up down switch port? Does 
> that vlan exist in
> the database.
> 
> 
> If you recently removed a vlan database from a switch and a 
> vlan configured
> on the switchport doesn't exist in the DB you will see this issue.
> 
> 
> 
> ________________________________________
> From: cisco-nsp-bounces at puck.nether.net 
> [cisco-nsp-bounces at puck.nether.net]
> On Behalf Of Steve Bertrand [cisco at ibctech.ca]
> Sent: Tuesday, October 23, 2007 10:50 PM
> To: Pete Templin
> Cc: cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] Ethernet Question - Problem with link
> 
> Pete Templin wrote:
> > Paul Stewart wrote:
> >
> >> Just looking for a thought - ethernet cable from switch to 
> switch.  One
> side
> >> is up/up but other side is up/down....
> >>
> >> Cabling problem?  It's a new connection...
> >
> > The problem(s) could be:
> >
> > 1:  Transmitter on up/up side.
> > 2:  Cabling problem.
> > 3:  Receiver on up/down side.
> > 4:  Perhaps other settings issues.
> >
> > The easy one is #2.
> 
> (My last message bounced, wrong address I used):
> 
> I'd go with #4. I find settings easier to check rather than physical,
> especially if accessible remotely when possible.
> 
> Could be misconfig, or the port was forgotten about and was 
> earlier used
> as a span monitor port and would show up/down. This is 
> happening on the
> 6500, right?
> 
> Steve