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

Converting SFPs from stacking to uplink in 2500

This thread has been viewed 0 times
  • 1.  Converting SFPs from stacking to uplink in 2500

    Posted Jan 07, 2015 10:13 AM

    How to convert SFP3 & SFP4 from stacking to uplink in S2500



  • 2.  RE: Converting SFPs from stacking to uplink in 2500
    Best Answer

    EMPLOYEE
    Posted Jan 07, 2015 10:15 AM
    3+4 are not stacking ports out of the box. Did you change them? 

    The command is 
    Delete stacking interface 
     


  • 3.  RE: Converting SFPs from stacking to uplink in 2500

    Posted Jan 07, 2015 10:18 AM
    No I didn't change them These ports can be used as uplink ports or a combination of two uplink ports and two stacking ports. By default, Ports 0 and 1 are configured as uplink ports and Ports 2 and 3 are configured as ArubaStack ports. The ArubaStack ports are indicated by a box around the port number. These port assignments can be changed to meet your configuration needs from the CLI.


  • 4.  RE: Converting SFPs from stacking to uplink in 2500

    EMPLOYEE
    Posted Jan 07, 2015 10:22 AM
    You're right. Fingers moving faster than the brain this morning :)

    Use the commands above. 


  • 5.  RE: Converting SFPs from stacking to uplink in 2500

    Posted Jan 07, 2015 10:22 AM

    You are correct, the 2500 has 3 and 4 as stackign and 1 and 2 as normal uplink ports.  Try the commands above andyou should be able to convert 3 and/or 4 to normal uplink ports.

     

     



  • 6.  RE: Converting SFPs from stacking to uplink in 2500

    EMPLOYEE
    Posted Jan 07, 2015 10:23 AM

    I think Cappalli hasn't had his coffee yet this morning so he didn't correlate SFP3 and SFP4 to mean the latter two ports of the uplink (0/1/2 and 0/1/3).

     

    Clembo has provided the proper instructions on converting the ports to normal uplink ports.

     

    Best regards,

     

    Madani



  • 7.  RE: Converting SFPs from stacking to uplink in 2500

    Posted Jan 07, 2015 11:09 AM

    Thanks All,

     

    it worked

     

    I have another question

     

    I have 2 Corinex powerline adapters that I use to connect 2 points as there no is way to install any cable

    When I connect them to any 2 switches or laptops they work fine, but when I use them between 2 Aruba switches S1500 they don't work.

     

    So I think that there is something which block their traffic

    Anybody can help??

     

    Thanks in advance



  • 8.  RE: Converting SFPs from stacking to uplink in 2500

    Posted Jan 07, 2015 12:10 PM

     

    When you connect these on S1500, even port LEDs won't glow ?

     

    or, just that traffic is not passing ? In that case can you check one of these port has moved to STP blocking state (show spanning-tree)

     

     

    Thanks,

    -Vinay

     

     



  • 9.  RE: Converting SFPs from stacking to uplink in 2500

    Posted Jan 09, 2015 10:53 AM
    Yes, the led is on and the traffic is blocked And when I disabled the spanning the port turned down How can I permit traffic in this case?


  • 10.  RE: Converting SFPs from stacking to uplink in 2500

    Posted Jan 11, 2015 12:00 AM

     It is strange that disabling STP brings down the link. STP doesn't control physical link/port properties.

     

    Now, With ports connected on S1500 with Corinex, and STP enabled (spanning-tree mode mstp),

    Can you dump the o/p of  "show interface gigabitethernet <x/y/z>" for ports on both S1500s ?

     

    And, when you say  "When I connect them to any 2 switches they work fine"

     - which switches are you refering to ?

     

    Also, to confirm the connectivity, is this how they are connected ?

     

    S1500-ONE {GE-0/0/1} --------- [Corinex adapter]------------ {GE-0/0/1} S1500-TWO

     

    Thanks,

    -Vinay

     



  • 11.  RE: Converting SFPs from stacking to uplink in 2500

    Posted Jan 11, 2015 09:35 AM

    The link was done due to another issue
    But when I convert it to PVST, everthing worked

    But do we have a way to keep the MSTP and unblock the traffic

     

    Thanks



  • 12.  RE: Converting SFPs from stacking to uplink in 2500

    Posted Jan 11, 2015 02:20 PM

     

    As we know PVST runs seperate STP instances per VLAN, whch makes some ports in "Forward" state in some VLANs & blocking in others, hence we can achieve kind of load-balancing of traffic

     

     Similar thing can be achieved in MSTP as-well.

     By default when you enable MSTP, only one 'instance' is running which spans on VLANS on the system.

      For better load-balancing of traffic, you can create multiple MST "instances": via something called as "instance VLAN mapping"

      This needs bit planning & deciding a root-bridge for each of those instances for "optimal" topology.

    Sample config like below needs to  be configured on all the switches in your topology

     

    (IDF-1) (config) #mstp

    (IDF-1) (Global MSTP) #region-name REG-1

    (IDF-1) (Global MSTP) #instance 0 bridge-priority 16384

    (IDF-1) (Global MSTP) #instance 1 bridge-priority 32768

    (IDF-1) (Global MSTP) #instance 2 bridge-priority 16384

    (IDF-1) (Global MSTP) #instance 1 vlan 100,200     

    (IDF-1) (Global MSTP) #instance 2 vlan 300,400

     

      Above config makes VLAN 100,200 as part of MSTP "instance 1", and so on....

     

      And bridge-priority needs to be varied on other switches. In short, Bridge-priority (lower) decides which switch will be root-bridge for specific instance, (Refer MAS documentation for more details...)

     

     



  • 13.  RE: Converting SFPs from stacking to uplink in 2500

    Posted Jan 07, 2015 10:17 AM

    To convert a stcking port to uplink, run the following:

     

    delete stacking interface stack <module/port>