[c-nsp] MST & Reserved VLANs on Nexus 5010
Gary T. Giesen
giesen at snickers.org
Mon Aug 30 22:35:34 EDT 2010
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 LACBPDUs
(until this release), if the other side was configured for Fast, the
port would occasionally bounce on its own. Doesn't seem to be the case
anymore (and now fully supports Fast Mode).
GG
On Fri, Jul 9, 2010 at 12:36 AM, Lincoln Dale <ltd at cisco.com> wrote:
> 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 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 frame does appear to Q4 2010. I'm pursuing it with
>> my account team to see if I can get it pushed up but I'm not sure if
>> that will go anywhere.
>>
>> GG
>>
>> On Mon, Jun 28, 2010 at 7:22 PM, Lincoln Dale <ltd at cisco.com> wrote:
>>> 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 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 make all externally-facing bugs available in
>>>> Bug Toolkit to best assist our customers. As a result, the system
>>>> administrators have been automatically alerted to the problem.
>>>
>>> indeed, the person that filed the bug marked it as internal only.
>>> i'll ask them to fix that. clearly it should be visible.
>>>
>>>
>>> cheers,
>>>
>>> lincoln.
>>>
>>>>
>>>> GG
>>>>
>>>> On Mon, Jun 28, 2010 at 3:33 AM, Lincoln Dale <ltd at cisco.com> wrote:
>>>>> 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,
>>>>>
>>>>> lincoln.
>>>>>
>>>>>
>>>
>>>
>>
>> _______________________________________________
>> 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