Wired Intelligent Edge

last person joined: yesterday 

Bring performance and reliability to your network with the HPE Aruba Networking Core, Aggregation, and Access layer switches. Discuss the latest features and functionality of your switching devices, and find ways to improve security across your network to bring together a mobile-first solution
Expand all | Collapse all

MSTP Questions

This thread has been viewed 7 times
  • 1.  MSTP Questions

    Posted Apr 30, 2018 04:18 AM
      |   view attached

    Hi all,

     

    We are running 3 sites with HP Aruba switches. MSTP is enabled (no config nor setup just out of the box).

     

    We are running 12 VLANs across the network. All VLANs are tagged across the links between switches.

     

    ======================================================

    Currently:

     

    Site A  connects to Site B with fibre

    Site B connects to Site C with a Wireless Link 

     

    Proposed Change:

     

    Site A  connects to Site B with fibre

    Site B connects to Site C with a Wireless Link 

    Site B connects to Site C with a second wireless link

    Site C to connect to Site A with a wireless link

     

    =====================================================

     

    Currently at Site B a HP Stack is in the main control room and has a single fibre connection to each of the 6 switches in the factory.

     

    We would like to change this so that the switches are in a ring e.g:

     

    Switch 1 has a connection to switch 6 & switch 2

    Switch 2 has a connection to switch 1 & switch 3

    Switch 3 has a connection to switch 2 & switch 4

    Switch 4 has a connection to switch 3 & switch 5

    Switch 5 has a connection to switch 4 & switch 6

    Switch 6 has a connection to switch 5 & switch 1

     

    ====================================================

     

    When we connected the redundant wireless links, spanning tree did not shut down one of the links. This caused me concern that it needs configuration out of the box.

     

    I have provided a visio of our current setup in the attachments.

     

    Could anyone let me know what I am doing wrong please? What do I need to do to make sure that when we change the switches into a "loop" MSTP shuts down one of the links?

     

    Many thanks. Please let me know if this wording does not make sense.

     

     

     



  • 2.  RE: MSTP Questions

    EMPLOYEE
    Posted Apr 30, 2018 01:01 PM

    Greetings!

     

    We need a bit more information to get to the bottom of what's going on here.  Could you provide the output of 'show spanning-tree' from each of the switches in the 'looped' state so we can figure out why ports aren't being shut down?  Configurations of the switches in question would also be helpful (you can send these by PM if you'd rather not do so publicly).



  • 3.  RE: MSTP Questions

    Posted May 01, 2018 07:46 AM

    Hi Matthew,

     

    As soon as I noticed the ports had not shut-down automatically I manually disabled the loop (circa 10mins after it was plugged in). We had not noticed a spike in traffic but not much was on the network at the time.

     

    I need to double check that all VLANs are added on all switches, would this make a difference?

     

    Thanks,

     

    Phil

     

     

    Attachment(s)



  • 4.  RE: MSTP Questions

    EMPLOYEE
    Posted May 01, 2018 12:38 PM

    If this is an out of the box configuration, has Spanning Tree been enabled? The default configuration has MSTP basically operating in RSTP mode, but if I recall correctly Spanning Tree still needs to be globally enabled first.



  • 5.  RE: MSTP Questions

    Posted May 01, 2018 12:40 PM

    Hi Charlie,

     

    This is out of the box. MSTP shows as being enabled, but they all seem to have different Root bridge? This would suggest each site has formed it's own perhaps?



  • 6.  RE: MSTP Questions

    EMPLOYEE
    Posted May 02, 2018 01:52 PM

    It is entirely possible that this is the case.  You mentioned that the inter-site connections (with the exception of the fiber link between A and B) are wireless; have you checked to see if BPDUs are being passed across those links between all three sites?  If they're being blocked, it's likely that each site is simply creating its own local spanning tree with an independent root bridge, which might explain what you're seeing.



  • 7.  RE: MSTP Questions

    Posted May 03, 2018 03:44 AM

    Hi All,

     

    I watched some cisco videos last night to try and understand more. It was my impression that the instances all needed the same name. The names on mine all seem to be different, I'm a little confused. Please see details below:

     

    SiteMake/Model 
    Site 1HP SingleMST Configuration Identifier Information

      MST Configuration Name : d0bf9c7fbe00
      MST Configuration Revision : 0
      MST Configuration Digest : 0xAC36177F50283CD4B83821D8AB26DE62

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs
    Site 1HP Single MST Configuration Identifier Information

      MST Configuration Name : 5820b134ac80
      MST Configuration Revision : 0
      MST Configuration Digest : 0xAC36177F50283CD4B83821D8AB26DE62

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs
      ----------- ---------------------------------------------------------
    Site 1HP StackMST Configuration Identifier Information

      MST Configuration Name : 00fd45b98220
      MST Configuration Revision : 0
      MST Configuration Digest :

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs
      ----------- ---------------------------------------------------------
    Site 1HP Single
     MST Configuration Identifier Information

      MST Configuration Name : 00fd45b863a0
      MST Configuration Revision : 0
      MST Configuration Digest :

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs
      ----------- ---------------------------------------------------------
    Site 1HP Single MST Configuration Identifier Information

      MST Configuration Name : d06726452080
      MST Configuration Revision : 0
      MST Configuration Digest : 0xAC36177F50283CD4B83821D8AB26DE62

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs
      ----------- ---------------------------------------------------------
    Site 1HP Single
     MST Configuration Identifier Information

      MST Configuration Name : d0bf9c7f1d80
      MST Configuration Revision : 0
      MST Configuration Digest : 0xAC36177F50283CD4B83821D8AB26DE62

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs
      ----------- ---------------------------------------------------------
    Site 1HP Stack MST Configuration Identifier Information

      MST Configuration Name : 308d9954a000
      MST Configuration Revision : 0
      MST Configuration Digest : 0xAC36177F50283CD4B83821D8AB26DE62

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs
      ----------- ---------------------------------------------------------
    Site 1HP Single
     MST Configuration Identifier Information

      MST Configuration Name : 5065f3ab7380
      MST Configuration Revision : 0
      MST Configuration Digest : 0xAC36177F50283CD4B83821D8AB26DE62

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs
      ----------- ---------------------------------------------------------
    Site 3HP Stack MST Configuration Identifier Information

      MST Configuration Name : 308d99434b00
      MST Configuration Revision : 0
      MST Configuration Digest : 0xAC36177F50283CD4B83821D8AB26DE62

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs
      ----------- ---------------------------------------------------------
    Site 3HP StackMST Configuration Identifier Information

      MST Configuration Name : 3ca82a6156c0
      MST Configuration Revision : 0
      MST Configuration Digest : 0xAC36177F50283CD4B83821D8AB26DE62

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs
      ----------- ---------------------------------------------------------
    Site 3HP Stack 
    MST Configuration Name : 3ca82a615420
      MST Configuration Revision : 0
      MST Configuration Digest : 0xAC36177F50283CD4B83821D8AB26DE62

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs
      ----------- ---------------------------------------------------------
    Site 3HP Stack MST Configuration Identifier Information

      MST Configuration Name : 3ca82a615360
      MST Configuration Revision : 0
      MST Configuration Digest : 0xAC36177F50283CD4B83821D8AB26DE62

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs
      ----------- ---------------------------------------------------------
    Site 3HP Stack MST Configuration Identifier Information

      MST Configuration Name : 3ca82a614560
      MST Configuration Revision : 0
      MST Configuration Digest : 0xAC36177F50283CD4B83821D8AB26DE62

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs
      ----------- ---------------------------------------------------------
    Site 2HP Single  MST Configuration Name : 5065f3ab46c0
      MST Configuration Revision : 0
      MST Configuration Digest : 0xAC36177F50283CD4B83821D8AB26DE62

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs
    Site 2  HP Single MST Configuration Identifier Information

      MST Configuration Name : a01d481f7d90
      MST Configuration Revision : 0
      MST Configuration Digest : 0xAC36177F50283CD4B83821D8AB26DE62

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs


  • 8.  RE: MSTP Questions

    Posted May 04, 2018 07:18 AM

    Hi guys, 

     

    Sorry for slow response, I thought I'd posted but it's not been uploaded. I did some research on the cisco variant of MSTP and wondered if my MSTP Config names matched, they do not. I ran "show spanning-tree mst-config" on each switch.
    Please see below:

     

    SiteMake/Model 
    Site 2HP SingleMST Configuration Identifier Information

      MST Configuration Name : d0bf9c7fbe00
      MST Configuration Revision : 0
      MST Configuration Digest : 0xAC36177F50283CD4B83821D8AB26DE62

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs
    Site 2HP Single MST Configuration Identifier Information

      MST Configuration Name : 5820b134ac80
      MST Configuration Revision : 0
      MST Configuration Digest : 0xAC36177F50283CD4B83821D8AB26DE62

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs
      ----------- ---------------------------------------------------------
    Site 2HP StackMST Configuration Identifier Information

      MST Configuration Name : 00fd45b98220
      MST Configuration Revision : 0
      MST Configuration Digest :

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs
      ----------- ---------------------------------------------------------
    Site 2HP Single
     MST Configuration Identifier Information

      MST Configuration Name : 00fd45b863a0
      MST Configuration Revision : 0
      MST Configuration Digest :

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs
      ----------- ---------------------------------------------------------
    Site 2HP Single MST Configuration Identifier Information

      MST Configuration Name : d06726452080
      MST Configuration Revision : 0
      MST Configuration Digest : 0xAC36177F50283CD4B83821D8AB26DE62

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs
      ----------- ---------------------------------------------------------
    Site 2HP Single
     MST Configuration Identifier Information

      MST Configuration Name : d0bf9c7f1d80
      MST Configuration Revision : 0
      MST Configuration Digest : 0xAC36177F50283CD4B83821D8AB26DE62

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs
      ----------- ---------------------------------------------------------
    Site 2HP Stack MST Configuration Identifier Information

      MST Configuration Name : 308d9954a000
      MST Configuration Revision : 0
      MST Configuration Digest : 0xAC36177F50283CD4B83821D8AB26DE62

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs
      ----------- ---------------------------------------------------------
    Site 2HP Single
     MST Configuration Identifier Information

      MST Configuration Name : 5065f3ab7380
      MST Configuration Revision : 0
      MST Configuration Digest : 0xAC36177F50283CD4B83821D8AB26DE62

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs
      ----------- ---------------------------------------------------------
    Site 1HP Stack MST Configuration Identifier Information

      MST Configuration Name : 308d99434b00
      MST Configuration Revision : 0
      MST Configuration Digest : 0xAC36177F50283CD4B83821D8AB26DE62

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs
      ----------- ---------------------------------------------------------
    Site 1HP StackMST Configuration Identifier Information

      MST Configuration Name : 3ca82a6156c0
      MST Configuration Revision : 0
      MST Configuration Digest : 0xAC36177F50283CD4B83821D8AB26DE62

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs
      ----------- ---------------------------------------------------------
    Site 1HP Stack
    MST Configuration Name : 3ca82a615420
      MST Configuration Revision : 0
      MST Configuration Digest : 0xAC36177F50283CD4B83821D8AB26DE62

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs
      ----------- ---------------------------------------------------------
    Site 1HP Stack MST Configuration Identifier Information

      MST Configuration Name : 3ca82a615360
      MST Configuration Revision : 0
      MST Configuration Digest : 0xAC36177F50283CD4B83821D8AB26DE62

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs
      ----------- ---------------------------------------------------------
    Site 1HP Stack MST Configuration Identifier Information

      MST Configuration Name : 3ca82a614560
      MST Configuration Revision : 0
      MST Configuration Digest : 0xAC36177F50283CD4B83821D8AB26DE62

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs
      ----------- ---------------------------------------------------------
    Site 3HP Single  MST Configuration Name : 5065f3ab46c0
      MST Configuration Revision : 0
      MST Configuration Digest : 0xAC36177F50283CD4B83821D8AB26DE62

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs
    Site 3  HP Single MST Configuration Identifier Information

      MST Configuration Name : a01d481f7d90
      MST Configuration Revision : 0
      MST Configuration Digest : 0xAC36177F50283CD4B83821D8AB26DE62

      IST Mapped VLANs : 1-4094

      Instance ID Mapped VLANs

     

     



  • 9.  RE: MSTP Questions

    Posted May 08, 2018 03:39 AM

    Hi all,

     

    I'm going to triple check all VLANs are enabled on all switches and then re-name the MSTP instances using:

     

    (ArubaS3500) (config) #mstp
    (ArubaS3500) (Global MSTP) #region-name MSTP_REGION_A

     

    Is this correct or do I need to do anymore?

     

    Source of info:

    http://community.arubanetworks.com/t5/Wired-Networks/Global-MSTP-Configuration-on-MAS/ta-p/234046



  • 10.  RE: MSTP Questions

    Posted May 10, 2018 07:12 AM

    Has anyone got any thoughts or advice?

     

    Thanks,

     

    Phil