Re: [c-nsp] MSTP between Cisco / Brocade
On Apr 25, 2012, at 5:08 PM, Randy wrote: Who is: 0015.62b7.0dc0 with a bridge-priority of 16384? That is the who the cisco is blocking. From Brocade-output above: Bridge: 8024389c3d00 [Priority 32768, SysId 0, Mac 0024389c3d00] ./Randy The mac in question is the Cisco's: ar01.prov#sh spanning-tree active MST0 Spanning tree enabled protocol mstp Root IDPriority16384 Address 0015.62b7.0dc0 This bridge is the root But nevermind I suppose, the issue is resolved with help from Brocade TAC. The MLX defaults to route-only which apparently means every port acts like Cisco's equivalent to no switchport or layer-3 only mode. So it would receive the MLX's BPDUs and silently discard them. Here's the strange part, despite being set for route-only, the MLX still transmits BPDUs. Which the Cisco received, detected that the MLX said port role is designated, and put it into blocking dispute since Cisco is the real root. Is it common expected for swouters to tx BPDUs when the port is in layer-3-only mode? Or am I just not getting the idea behind route-only in Brocade? Thanks for the help! ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] MSTP between Cisco / Brocade
On Apr 26, 2012, at 1:09 PM, Steven Raymond wrote: The MLX defaults to route-only which apparently means every port acts like Cisco's equivalent to no switchport or layer-3 only mode. So it would receive the MLX's BPDUs and silently discard them. s/receive the MLX's/receive the Cisco's/ Meh my crappy proofreading. ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] MSTP between Cisco / Brocade
Is it common expected for swouters to tx BPDUs when the port is in layer-3-only mode? Or am I just not getting the idea behind route-only in Brocade? I would definitely not expect a routed interface to transmit BPDUs by default. Steinar Haug, Nethelp consulting, sth...@nethelp.no ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
[c-nsp] MSTP between Cisco / Brocade
Have a single layer 2 connection between 7609, version 12.2(33)SRD4, 6708, with a 10G connection to Brocade. Using simplest form of MSTP, it works fine to a Brocade TI24X switch, running version 4 something. Move the same cable to a 10G port on a MLXe, version 5.2.0T165, the Cisco blocks the port as the following: ar01.prov#show spanning-tree active detail Port 4 (TenGigabitEthernet1/4) of MST0 is designated blocking (dispute) Port path cost 2000, Port priority 128, Port Identifier 128.4. Designated root has priority 16384, address 0015.62b7.0dc0 Designated bridge has priority 16384, address 0015.62b7.0dc0 Designated port id is 128.4, designated path cost 0 Timers: message age 0, forward delay 14, hold 0 Number of transitions to forwarding state: 0 Link type is point-to-point by default, Internal BPDU: sent 20540, received 10287 Google suggests that this may be caused by both switches' ports declaring they are designated role for the segment, and the Cisco proceeds to block as a defense against uni-directional link. But these same optics and cables work fine on the other device. Even so, they have been swapped with same circumstance. Am certain there is no uni-directional link here. Other searching says that Cisco is bad and sends the BPDUs tagged and that native vlan tagging must be removed, which is not enabled to begin with. Brocade said to add pvst-mode to the interface config on the MLXe side, but it did not help at all. And I don't understand what PVST has to do with MSTP as currently configured. Any suggestions? Thanks!! ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] MSTP between Cisco / Brocade
--- On Wed, 4/25/12, Steven Raymond sraym...@acedatacenter.com wrote: From: Steven Raymond sraym...@acedatacenter.com Subject: [c-nsp] MSTP between Cisco / Brocade To: cisco-nsp Service Providers cisco-nsp@puck.nether.net Date: Wednesday, April 25, 2012, 1:52 PM Have a single layer 2 connection between 7609, version 12.2(33)SRD4, 6708, with a 10G connection to Brocade. Using simplest form of MSTP, it works fine to a Brocade TI24X switch, running version 4 something. Move the same cable to a 10G port on a MLXe, version 5.2.0T165, the Cisco blocks the port as the following: ar01.prov#show spanning-tree active detail Port 4 (TenGigabitEthernet1/4) of MST0 is designated blocking (dispute) Port path cost 2000, Port priority 128, Port Identifier 128.4. Designated root has priority 16384, address 0015.62b7.0dc0 Designated bridge has priority 16384, address 0015.62b7.0dc0 Designated port id is 128.4, designated path cost 0 Timers: message age 0, forward delay 14, hold 0 Number of transitions to forwarding state: 0 Link type is point-to-point by default, Internal BPDU: sent 20540, received 10287 Google suggests that this may be caused by both switches' ports declaring they are designated role for the segment, and the Cisco proceeds to block as a defense against uni-directional link. But these same optics and cables work fine on the other device. Even so, they have been swapped with same circumstance. Am certain there is no uni-directional link here. Other searching says that Cisco is bad and sends the BPDUs tagged and that native vlan tagging must be removed, which is not enabled to begin with. Brocade said to add pvst-mode to the interface config on the MLXe side, but it did not help at all. And I don't understand what PVST has to do with MSTP as currently configured. Any suggestions? Thanks!! ...I haven't played with Foundry/Brocade for a while. It is clear that on the Cisco you have enabled 802.1s(MISTP) I am not clear if you have 802.1s OR 802-1w enabled on the Brocade(care to post the stp output from Brocade?) I ask because in the past Brocade/Foundry referred to 802.1W(R-PVST in Cisco-speak) as MULTIPLE-SPANNING-TREE! ./Randy ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] MSTP between Cisco / Brocade
On Apr 25, 2012, at 3:55 PM, Randy wrote: I am not clear if you have 802.1s OR 802-1w enabled on the Brocade(care to post the stp output from Brocade?) sh run | i mstp mstp name acedc mstp revision 1 mstp instance 0 vlan 1 to 4090 mstp start tel...@ar04.prov#show mstp detail MSTP Instance 0 (CIST) - VLAN Scope: 1 to 4090 Bridge: 8024389c3d00 [Priority 32768, SysId 0, Mac 0024389c3d00] FwdDelay 15, HelloTime 2, MaxHops 20, TxHoldCount 6 Port 2/1 - Role: DESIGNATED - State: FORWARDING PathCost 2000, Priority 128, OperEdge T, OperPt2PtMac F, Boundary N/A Designated - Root 8024389c3d00, RegionalRoot 8024389c3d00, Bridge 8024389c3d00, ExtCost 0, IntCost 0 ActiveTimers - helloWhen 2 MachineState - PRX-DISCARD, PTX-IDLE, PPM-SENDING_RSTP, PIM-CURRENT PRT-ACTIVE_PORT, PST-FORWARDING, TCM-INACTIVE BPDUs- Rcvd MST 0, RST 0, Config 0, TCN 0 Sent MST 11, RST 0, Config 0, TCN 0 tel...@ar04.prov#sh spanning-tree tel...@ar04.prov#show rstp tel...@ar04.prov# That helpful? Thanks! ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] MSTP between Cisco / Brocade
--- On Wed, 4/25/12, Steven Raymond sraym...@acedatacenter.com wrote: From: Steven Raymond sraym...@acedatacenter.com Subject: Re: [c-nsp] MSTP between Cisco / Brocade To: Randy randy_94...@yahoo.com Cc: cisco-nsp Service Providers cisco-nsp@puck.nether.net Date: Wednesday, April 25, 2012, 3:03 PM On Apr 25, 2012, at 3:55 PM, Randy wrote: I am not clear if you have 802.1s OR 802-1w enabled on the Brocade(care to post the stp output from Brocade?) sh run | i mstp mstp name acedc mstp revision 1 mstp instance 0 vlan 1 to 4090 mstp start tel...@ar04.prov#show mstp detail MSTP Instance 0 (CIST) - VLAN Scope: 1 to 4090 Bridge: 8024389c3d00 [Priority 32768, SysId 0, Mac 0024389c3d00] FwdDelay 15, HelloTime 2, MaxHops 20, TxHoldCount 6 Port 2/1 - Role: DESIGNATED - State: FORWARDING PathCost 2000, Priority 128, OperEdge T, OperPt2PtMac F, Boundary N/A Designated - Root 8024389c3d00, RegionalRoot 8024389c3d00, Bridge 8024389c3d00, ExtCost 0, IntCost 0 ActiveTimers - helloWhen 2 MachineState - PRX-DISCARD, PTX-IDLE, PPM-SENDING_RSTP, PIM-CURRENT PRT-ACTIVE_PORT, PST-FORWARDING, TCM-INACTIVE BPDUs - Rcvd MST 0, RST 0, Config 0, TCN 0 Sent MST 11, RST 0, Config 0, TCN 0 tel...@ar04.prov#sh spanning-tree tel...@ar04.prov#show rstp tel...@ar04.prov# That helpful? Thanks! Yes No. Yes: both devices are running 802.1s No: Because of outputs posted: Output from Brocade-above: Bridge: 8024389c3d00 [Priority 32768, SysId 0, Mac 0024389c3d00] Output from Cisco: Port 4 (TenGigabitEthernet1/4) of MST0 is designated blocking (dispute) Port path cost 2000, Port priority 128, Port Identifier 128.4. Designated root has priority 16384, address 0015.62b7.0dc0 Designated bridge has priority 16384, address 0015.62b7.0dc0 Who is: 0015.62b7.0dc0 with a bridge-priority of 16384? That is the who the cisco is blocking. From Brocade-output above: Bridge: 8024389c3d00 [Priority 32768, SysId 0, Mac 0024389c3d00] ./Randy ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
