Just to give an update to everyone...
4.2(1)N2(1), released on 30-Jul-2010, has the fix for this, and
supports all VLANs (for the purposes of MST, the VLANs are still
reserved). Also seems to have solved a nasty little LACP bug I ran
into. Since the Nexus didn't explicitly support LACP Fast
Gary,
DeeWhy Plus will contain the fix.
timeframe for that is approximately late August.
cheers,
lincoln.
On 06/07/2010, at 6:09 AM, Gary T. Giesen wrote:
Just a quick update for everyone. It appears the fix is two releases
away. The first (Deewhy Plus) is going to be based on 4.2 and
Just a quick update for everyone. It appears the fix is two releases
away. The first (Deewhy Plus) is going to be based on 4.2 and should
be out in Q3 2010. It will not contain the fix. The second (Eaglehawk)
will be based on NX-OS 5.0 regardless. It will supposedly contain the
fix. And the time
Gary,
On 28/06/2010, at 1:04 AM, Gary T. Giesen wrote:
NX-OS definitely prevents you from mapping them to *any* instance.
I'll open a TAC case with Cisco tomorrow and see if I get anywhere.
CSCtc54335 covers this.
its due to be sync'd to the next 4.2(x) maintenance release on N5K.
cheers,
Any idea on when that might be? I can't even view the bug report.
Dear valued Cisco Bug Toolkit customer, the bug ID CSCtc54335 you
searched contains proprietary information that cannot be disclosed at
this time; therefore, we are unable to display the bug details. Please
note it is our policy to
On 29/06/2010, at 12:26 AM, Gary T. Giesen wrote:
Any idea on when that might be? I can't even view the bug report.
the next NX-OS 4.2 maintenance release for the N5K is due to be posted on
cisco.com in Q4 CY2010.
Dear valued Cisco Bug Toolkit customer, the bug ID CSCtc54335 you
searched
On Fri, Jun 25, 2010 at 02:35:28PM -0400, Gary T. Giesen wrote:
I've run into a bit of a problem with a couple of new Nexus 5010
switches we've recently acquired. I've tried to apply our standard MST
configuration, and have run into the problem that the Nexus has 81
VLANs that are reserved for
On Sun, Jun 27, 2010 at 12:56:29PM +0200, Joerg Mayer wrote:
On Fri, Jun 25, 2010 at 02:35:28PM -0400, Gary T. Giesen wrote:
I've run into a bit of a problem with a couple of new Nexus 5010
switches we've recently acquired. I've tried to apply our standard MST
configuration, and have run
NX-OS definitely prevents you from mapping them to *any* instance.
I'll open a TAC case with Cisco tomorrow and see if I get anywhere.
GG
On 6/27/10, Ross Vandegrift r...@kallisti.us wrote:
On Sun, Jun 27, 2010 at 12:56:29PM +0200, Joerg Mayer wrote:
On Fri, Jun 25, 2010 at 02:35:28PM -0400,
On Sun, Jun 27, 2010 at 12:55:19PM -0400, Ross Vandegrift wrote:
The good news is that they should be convinced fairly easily - tell
them to look at IOS, it correctly permits any dot1Q ID to be mapped.
I had to argue with HP for three years before they removed the
requirement that the VLAN
I've run into a bit of a problem with a couple of new Nexus 5010
switches we've recently acquired. I've tried to apply our standard MST
configuration, and have run into the problem that the Nexus has 81
VLANs that are reserved for system use (3968 to 4047 4094), which
are not reserved on any of
11 matches
Mail list logo
