11 messages in net.nether.puck.cisco-nsp[c-nsp] Re: 6500 Port Monitor
FromSent OnAttachments
Ziv MoseryJan 18, 2005 3:37 am 
PiltrafillaJan 18, 2005 4:58 am 
Ziv MoseryJan 18, 2005 5:05 am 
Voll, ScottJan 18, 2005 7:14 am 
Todd, Douglas M.Jan 18, 2005 9:35 am 
Tim StevensonJan 18, 2005 12:22 pm 
Tim StevensonJan 18, 2005 12:30 pm 
Ziv MoseryJan 18, 2005 4:22 pm 
Greg SchwimerJan 18, 2005 7:13 pm 
Tim StevensonJan 19, 2005 5:29 pm 
Justin M. StreinerJan 19, 2005 7:21 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[c-nsp] Re: 6500 Port MonitorActions...
From:Justin M. Streiner (stre@cluebyfour.org)
Date:Jan 19, 2005 7:21:27 pm
List:net.nether.puck.cisco-nsp

On Wed, 19 Jan 2005, Tim Stevenson wrote:

This problem has to do with the particular line card you are using for the span destination ports, ie, one of the 8:1 oversubscribed GETX blades.

There are two solutions to your problem: either move the gig and 100M SPAN dest ports to 2 different muxing ASICs on this module (eg, port 1 & port 9, they are in contiguous groups of 8 ports); or, upgrade to 12.1(26)E, where this problem is resolved.

By chance would this same fix apply to the same problems with 48-port FE/TX blades in the 6500s? I've run into problems in the past where I couldn't span to or from a port if there was a pvlan port configured in the same ASIC bundle...

jms