Re: OT: 3560 Code issues MST

No, I made sure all the names were hardset, domain names hardset for vtp and revision numbers were set . I went as far as completely removing the most configuration rebooting and then re applying the config. I hope I don't get something like this in the test, because I might just grab my 1,500 $ drink and walk out. ;)

Regards,
 Joe Sanchez

( please excuse the brevity of this email as it was sent via a mobile device. Please excuse misspelled words or sentence structure.)

On Sep 5, 2012, at 7:01 AM, Carlos G Mendioroz <tron_at_huapi.ba.ar> wrote:

> Joe,
> Did you check region name/version/mapping ?
> The switches were sticking as CIST root or just regional root ?
> A show span vlan was showing the "should be root" as internal ?
>
> I've run into issues with switches with different default configuration names, that partition the spanning tree domain w/o my being aware, that's why I ask. It may be a code bug too, of course.
>
> -Carlos
>
>
> Joe Sanchez @ 05/09/2012 01:38 -0300 dixit:
>> Just had a major issue with my 3560 code, the problem was the code I had was
>> the same across all my switches, although each of the switches are different
>> by model i.e.
>> 48ps versus 24TS but none-the-less had major issues with
>> MST.
>>
>> Problem code was: c3560-ipservicesk9-mz.122-50.SE1.bin
>> Hardware was: WS-C3560-24PS
>> Problem:
>>
>> Although all ports were FastEthernet and the fact that MST instance 0-3
>> priority was set to 61440 and two of the upstream switches were configured
>> for root primary and root secondary the problem switch refused to become
>> anything but ROOT for all instances "VLANs"
>> I did everything from
>> configuring all the upstream facing port cost to extremely low, to setting
>> the priorities of the upstream switches facing the problem switch to 64,
>> nothing worked.. So I upgraded the code to a
>> c3560-ipservicesk9-mz.122-53.SE1.bin now all is working fine and I can move
>> on with my lab
>> For what ever reason, I haven't ran into this problem in
>> the past although I know that I've been through a few major MST topologies,
>> but test is coming up so I thought I'd tackle a bigger MST lab
>> good
>> troubleshooting though!!!!
>>
>> Good luck all, hope you can avoid the hours I spent on this one
>> MAC does't
>> have a working tFTP server, and had to put my work laptop into safe-mode to
>> avoid the NIDS breaking my tftpd-32 software transfers
>> I need a break
>> :)
>>
>> Joe Sanchez
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>>
>>
>>
>>
>>
>>
>>
>
> --
> Carlos G Mendioroz <tron_at_huapi.ba.ar> LW7 EQI Argentina

Blogs and organic groups at http://www.ccie.net
Received on Wed Sep 05 2012 - 08:44:22 ART