Everything Instant On

 View Only

  • 1.  Is there a way to downgrade from 2.8.0(17) to 2.6.0(74)?

    Posted 08-19-2024 09:56 AM
    Good day,
    Short version:
    I've upgraded a pair of Aruba 1930 (JL686A) to 2.8.0(17).  During that process the (3rd party) SFPs that I have been using stopped working, after being quite happy for ~18 months.  These SFPs are the single mode connection between two building on our campus.  I am desperate to get this single mode link working again. Even if I have to loose my switch configs in a some kind of drastic "downgrade" process.
    Long version:
    I have happily been using a pair of FS.com SFP1G-LX-31 (Aruba SFP-LX 1000BASE-LX SFP Transceiver Module - FS.com) for over 18 months now.  The SFP units I have, until last night, had been working flawlessly in my Aruba 1930 (JL686A).
    However, last night, I updated the Aruba FW in...
    • my root switch "A": from v2.6.0(74) to  v2.8.0(17)
    • my leaf switch "B": from v1.0.5.0(139) to v2.8.0(17)
    Unfortunately, now the single mode optical connection between these two switches is out of service. And both switches are reporting that these SFP interfaces are...
    • "Suspended due to link-flapping"
    Given that...
    • that both "old" Aruba FW images were completely happy with the SFP1G-LX-31
    • the "new" Aruba FW was completely unhappy with the SFP1G-LX-31
    ...it is my suspicion is that there is a FW compatibility issue with the new v2.8.0 FW and the FS.com SFP1G-LX-31 module. :-( 
    However, since these two SFPs are an inter-building connection on our campus, I am willing to try almost anything to get the link back up.  (After ordering Aruba's expensive SFP modules, but with a multi-day delivery date) I'm still looking for a quick way to get this link back up and running.  That is up to and including any sort of drastic downgrade procedure (to 2.6.0(74) for instance) that erases the two switch's configs.
    Thank you in advance for any help or suggestions.
    Cheers....


    ------------------------------
    Mark
    ------------------------------


  • 2.  RE: Is there a way to downgrade from 2.8.0(17) to 2.6.0(74)?

    Posted 08-19-2024 01:06 PM

    I have been in a similar situation with HP Procurve OS switches in the past.  In order to prevent malicious code from being introduced from 3rd party providers (and conveniently keep higher prices) HPE started enforcing signature signing to verify authentic HP SPFs.  It might be something similar?

     

    I have not downgraded the Aruba Instant On 1930 but you can try downloading the previous firmware from this link and "update" the switch with the older firmware.  Obviously backup first.

     

    https://community.arubainstanton.com/blogs/jamie-easly1/2020/06/03/instant-on-1930-switching-software-portal

     

     

    Jim

     

     






  • 3.  RE: Is there a way to downgrade from 2.8.0(17) to 2.6.0(74)?

    Posted 08-20-2024 09:25 AM

    As Jim already wrote, you can try manually flash with older FW version.

    As Aruba Instant On SFPs, you'll find S0G20A (HP NW Instant On 1G SFP LC LX 10km) priced very reasonably. Just don't order/buy Aruba enterprise SFPs for InstantOn deployment. Instant On SFPs are priced in the range of ION gear.

    Best, Gorazd



    ------------------------------
    Gorazd Kikelj
    ------------------------------



  • 4.  RE: Is there a way to downgrade from 2.8.0(17) to 2.6.0(74)?

    Posted 08-21-2024 10:10 AM

    Do the switches say anything about the SFP modules being incompatible or non-Aruba?

     

    Did you verify that the upgrade didn't change either switches config?  I have seen that behavior when both switches thought there were in charge of spanning tree. 

     

    Aaron




    Original Message


  • 5.  RE: Is there a way to downgrade from 2.8.0(17) to 2.6.0(74)?

    Posted 08-30-2024 11:29 AM

    Did you manage to fix it? I am having a similar issue with an FS.com transceiver :(



    ------------------------------
    Catalin Bercu
    ------------------------------



  • 6.  RE: Is there a way to downgrade from 2.8.0(17) to 2.6.0(74)?

    Posted 10-14-2024 08:31 PM
    rocasper,

    Sorry for the delay.  Once I fixed my issue, I sort of stopped checking my ArubaCommunity email folder. My bad.

    Short version:
    I never found anything wrong with the transceivers nor the Aruba FW image.  I finally just turned off the "link flapping detection" on the problematic port.��

    Long version:
    I was pulling my hair out, trying to get the inter building optical link back in service before the start of classes at my school.  I ever put in a trouble ticket with AT&T (my local interconnect provider) to have them reset the two optical interfaces on their side.  No joy. ��

               Building "A"                                             Building "B"
    <from    +--------------+        +--------------------------+     +--------------+
    srvc  ---| 1930 "A"  p52|--------|pXX  <some AT&T eqpt>  pYY|-----|p49  1930 "B" |
    prov>    +--------------+        +--------------------------+     +--------------+

    In the end, I simply turned off the link flap detection on p52 of my "A" switch.  Not a very satisfying solution to the issue, but Building B was now operational.

    My speculation is that somewhere in my image upgrades:
    • my root switch "A": from v2.6.0(74) to  v2.8.0(17)
    • my leaf switch "B": from v1.0.5.0(139) to v2.8.0(17)
    That one of two things happened...
    1. that the default setting for "link-flapping detection" got changed from "off" to "on"
      1. I don't ever remember turning on link flap detection. ��
    2. that the link flap detection algorithms had been improved
      1. and my inter-building network connection has characteristics "just on the wrong side" of the improved algorithm.
    But, with "link flap detection" OFF for my inter building link, I am now happily running v2.8.0 and Aruba optical SFPs on both switches.  (When there is a school break, I plan to roll back to the FS.com optical SFP as a final recheck to verify that it is really NOT a SFP issue.)


    Cheers...   mschnell42



    Original Message


Related Content