MSTP does work, well at least when i tried it on 10.3

On Wed, Nov 3, 2010 at 3:38 AM, Nilesh Khambal <nkham...@juniper.net> wrote:
> David,
>
> I don't think you can run RSTP in logical routers. As you can see from your
> outputs below, RSTP instances in all the LRs are using same system MAC. You
> can probably try MSTP but don't think RSTP will work in LRs.
>
> BTW, what JUNOS version is this?
>
> Thanks,
> Nilesh.
>
>> n...@mx960-lab-re0> ...ge logical-system SW1 routing-instance 11
>> STP bridge parameters
>> Routing instance name               : SW1/11
>> Context ID                          : 1
>> Enabled protocol                    : STP
>>   Root ID                           : 0.80:71:1f:8c:7f:d0
>>   Hello time                        : 2 seconds
>>   Maximum age                       : 20 seconds
>>   Forward delay                     : 15 seconds
>>   Message age                       : 0
>>   Number of topology changes        : 2
>>   Time since last topology change   : 388 seconds
>>   Local parameters
>>     Bridge ID                       : 0.80:71:1f:8c:7f:d0 <<<<<<<
>>     Extended system ID              : 0
>>
>> {master}
>> n...@mx960-lab-re0> ...tree bridge logical-system SW2 routing-instance 12
>> STP bridge parameters
>> Routing instance name               : SW2/12
>> Context ID                          : 2
>> Enabled protocol                    : STP
>>   Root ID                           : 8192.80:71:1f:8c:7f:d0
>>   Hello time                        : 2 seconds
>>   Maximum age                       : 20 seconds
>>   Forward delay                     : 15 seconds
>>   Message age                       : 0
>>   Number of topology changes        : 1
>>   Time since last topology change   : 396 seconds
>>   Local parameters
>>     Bridge ID                       : 8192.80:71:1f:8c:7f:d0  <<<<<<<
>>     Extended system ID              : 0
>
>
>
> On 11/2/10 7:08 PM, "David Lockuan" <dlock...@gmail.com> wrote:
>
>> Hi guys,
>>
>> I'm testing the protocols rstp over logical-systems, but when I set the
>> priority over one interface for it work as root, it is not change the status
>> in the protocols rstp  and the other interface don't change to Blocking.
>> theirs always keep on Forwarding state.
>>
>> The topology that I am using it is the next:
>>
>> SW1 (logical)-----------ge-3/0/2------------loop
>> fisico------------ge-3/0/3----------SW2(logical)
>> SW1 (logical)-----------ge-3/0/4------------loop
>> fisico------------ge-3/0/5----------SW2(logical)
>>
>> I want to put the interface ge-3/0/2 as root interface.
>>
>> These are configuration of both logical-systems:
>>
> ******************************************************************************>
> *
>> {master}
>> n...@mx960-lab-re0> show configuration interfaces
>> ge-3/0/2 {
>>     encapsulation ethernet-bridge;
>> }
>> ge-3/0/3 {
>>     encapsulation ethernet-bridge;
>> }
>> ge-3/0/4 {
>>     encapsulation ethernet-bridge;
>> }
>> ge-3/0/5 {
>>     encapsulation ethernet-bridge;
>> }
>>
>> {master}
>> n...@mx960-lab-re0> show configuration logical-systems SW1
>> interfaces {
>>     ge-3/0/2 {
>>         unit 0 {
>>             family bridge;
>>         }
>>     }
>>     ge-3/0/4 {
>>         unit 0 {
>>             family bridge;
>>         }
>>     }
>> }
>> routing-instances {
>>     11 {
>>         instance-type virtual-switch;
>>         protocols {
>>             rstp {
>>                 bridge-priority 0;
>>                 interface ge-3/0/2 {
>>                     priority 0;
>>                     mode point-to-point;
>>                 }
>>                 interface ge-3/0/4 {
>>                     mode point-to-point;
>>                 }
>>                 force-version stp;
>>             }
>>         }
>>         bridge-domains {
>>             br1 {
>>                 interface ge-3/0/2.0;
>>                 interface ge-3/0/4.0;
>>             }
>>         }
>>     }
>> }
>>
>> {master}
>> n...@mx960-lab-re0> show configuration logical-systems SW2
>> interfaces {
>>     ge-3/0/3 {
>>         unit 0 {
>>             family bridge;
>>         }
>>     }
>>     ge-3/0/5 {
>>         unit 0 {
>>             family bridge;
>>         }
>>     }
>> }
>> routing-instances {
>>     12 {
>>         instance-type virtual-switch;
>>         protocols {
>>             rstp {
>>                 bridge-priority 8k;
>>                 interface ge-3/0/3 {
>>                     mode point-to-point;
>>                 }
>>                 interface ge-3/0/5 {
>>                     mode point-to-point;
>>                 }
>>                 force-version stp;
>>             }
>>         }
>>         bridge-domains {
>>             br1 {
>>                 interface ge-3/0/3.0;
>>                 interface ge-3/0/5.0;
>>             }
>>         }
>>     }
>> }
>>
>> {master}
>> n...@mx960-lab-re0>
>>
> ******************************************************************************>
> *
>>
>> The output of the show spanning-tree commands:
>>
>>
> ******************************************************************************>
> *
>> {master}
>> n...@mx960-lab-re0> ...e interface logical-system SW1 routing-instance 11
>>
>> Spanning tree interface parameters for instance 0
>>
>> Interface    Port ID    Designated      Designated         Port    State
>> Role
>>                          port ID        bridge ID          Cost
>> ge-3/0/2         0:123        0:123      0.80711f8c7fd0     20000  FWD
>> DESG
>> ge-3/0/4       128:125      128:125      0.80711f8c7fd0     20000  FWD
>> DESG
>>
>> {master}
>> n...@mx960-lab-re0> ...e interface logical-system SW2 routing-instance 12
>>
>> Spanning tree interface parameters for instance 0
>>
>> Interface    Port ID    Designated      Designated         Port    State
>> Role
>>                          port ID        bridge ID          Cost
>> ge-3/0/3       128:124      128:124   8192.80711f8c7fd0     20000  FWD
>> DESG
>> ge-3/0/5       128:126      128:126   8192.80711f8c7fd0     20000  FWD
>> DESG
>>
>> {master}
>> n...@mx960-lab-re0> show spanning-tree bridge logical-system SW1
>> Spanning-tree is not enabled in layer2-control instance SW1/default.
>>
>> {master}
>> n...@mx960-lab-re0> ...ge logical-system SW1 routing-instance 11
>> STP bridge parameters
>> Routing instance name               : SW1/11
>> Context ID                          : 1
>> Enabled protocol                    : STP
>>   Root ID                           : 0.80:71:1f:8c:7f:d0
>>   Hello time                        : 2 seconds
>>   Maximum age                       : 20 seconds
>>   Forward delay                     : 15 seconds
>>   Message age                       : 0
>>   Number of topology changes        : 2
>>   Time since last topology change   : 388 seconds
>>   Local parameters
>>     Bridge ID                       : 0.80:71:1f:8c:7f:d0
>>     Extended system ID              : 0
>>
>> {master}
>> n...@mx960-lab-re0> ...tree bridge logical-system SW2 routing-instance 12
>> STP bridge parameters
>> Routing instance name               : SW2/12
>> Context ID                          : 2
>> Enabled protocol                    : STP
>>   Root ID                           : 8192.80:71:1f:8c:7f:d0
>>   Hello time                        : 2 seconds
>>   Maximum age                       : 20 seconds
>>   Forward delay                     : 15 seconds
>>   Message age                       : 0
>>   Number of topology changes        : 1
>>   Time since last topology change   : 396 seconds
>>   Local parameters
>>     Bridge ID                       : 8192.80:71:1f:8c:7f:d0
>>     Extended system ID              : 0
>>
>>
> ******************************************************************************>
> *
>>
>> I don't know, if my configuration is right? or maybe i have a mistake.
>>
>> Somebody has tried to implement this feature on single chassis MX with
>> logical-systems??
>>
>> Thanks in advance for your help.
>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>



-- 
Phill Jolliffe

_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Reply via email to