Network Management

 View Only

  • 1.  Problem adding VLAN to lagg in 1950 stack

    Posted Aug 06, 2025 11:51 AM

    Hello team!

    We have 2 switches HPE 1950 in a stack.

    This stack is working and have many servers in many different VLANs connected to this.

    The uplink is the static lagg called "BAGG 1", which contains the ports XGE1/0/1 and XGE2/0/1 (The only lagg on the stack)

    We need to add a new VLAN to this stack, which is already created on another stack connected to this stack through BAGG 1 interfaces

    Actually, BAGG 1 is not redundant because we have just one cable connected

    This lagg and members, are as "trunk" and have many VLANs, we just need to add another VLAN as tagged

    We found few docummentation about this switches, and the only info that we found about how to add a VLAN to lagg was in the "User guide", in page 98 (Which is an example of how to create a lagg) .  In this example, the lagg members are added to the tagged member list of the new VLAN

    We have created the VLAN successful, with no problems, but when we added XGE1/0/1 and XGE2/0/1 on the tagged member list of the new VLAN, we lost access to the stack and everything connected to it.

    All servers connected to this stoped working, so we needed to restart both switches to get the "startup configuration" running in the stack, which allow us to access again to everything.

    Is this the correct procedure to add a VLAN to a lagg?

    Do you have another better docummentation about these switches?

    Do you know why the stack became unaccesible when I added the lagg port members to the tagged list of the VLAN?

    Thanks in advance.

    Regards,

    Damián



    -------------------------------------------


  • 2.  RE: Problem adding VLAN to lagg in 1950 stack
    Best Answer

    Posted Aug 06, 2025 01:43 PM
    Hi, AFAIK - in case of a LAG (Links Aggregation Group) - the VLAN membership (tagging or untagging) must be configured and managed at LAG interface level and not at LAG member interfaces level (member interfaces vanish under the logical LAG interface). Try to assign the new VLAN tagging to the LAG logical interface instead of doing that at LAG's physical member interfaces.



    Original Message


  • 3.  RE: Problem adding VLAN to lagg in 1950 stack

    Posted Aug 07, 2025 08:31 AM

    Hello Parnassus, thanks for your answer!

    It is hard to test, because if the stack and all server become unaccessible again, they will kill me! lol

    I will try with the support.

    Regards

    Damián

    -------------------------------------------

    Original Message


  • 4.  RE: Problem adding VLAN to lagg in 1950 stack

    Posted Aug 07, 2025 01:36 PM
    Hi, yes...I understand you very well.

    Our job always translates into the challenge of performing network management as transparently as we can (read: causing minimal or no disruption at all to our business workflows). Given that what I suggested to you is not performing "a test".

    You really just need to create the new VLAN Id on the HPE 1950 stack (if you already didn't that before...and I believe you did since your attempt was an unlucky test), once the VLAN Id is available on the HPE 1950 stack you simply need to add that VLAN Id as tagged to the BAGG logical interface (the LAG formed by the aggregation of physical interfaces XGE1/0/1 and XGE2/0/1)...in other words you should "tag" that LAG interface with that particular VLAN Id (this is not going to change the existing VLAN Id tagging of that interface). It's a quite simple approach. To avoid issues you should grant yourself a proper maintenance window so you can manage the change accordingly in case of issues (you only know your network). Cheers!



    Original Message


  • 5.  RE: Problem adding VLAN to lagg in 1950 stack

    Posted Aug 07, 2025 03:58 AM
    Edited by parnassus Aug 07, 2025 04:22 AM

    Hi, forgot to add that the HPE 1950 (old name of the HPE OfficeConnect 1950) is a Comware OS based Switch (so - basically - we can think about it as a "feature stripped-down" version of the Comware OS we can find on other current HPE 51xx series production, as example; where here with "stripped-down" or, better, with its features not totally exposed on the GUI but available at CLI level...I mean a simpler Switch with simpler features but with a good - often undisclosed - potential)...that's to say that the "stack" on the HPE 1950 is - de-facto - an IRF (!). Just to say. The point is that the user is forced to manage the Switch through the Web GUI and its weirdness instead of going down the CLI path. This behaviour was adopted also on old HP/HPE 1920 (Comware OS based too) and, lately, also with HPE 1920S (Custom Linux OS based). This means that if you have a doubt about how to do things on the 1950 you could eventually look for and compare for the same feature on other low-end/medium-end Comware OS based switches, that could be illuminating.

    -------------------------------------------

    Original Message


  • 6.  RE: Problem adding VLAN to lagg in 1950 stack

    Posted Aug 07, 2025 04:41 AM

    You may have a better audience for this question in the HPE Instant ON forums.



    ------------------------------
    Herman Robers
    ------------------------
    If you have urgent issues, always contact your HPE Aruba Networking partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact HPE Aruba Networking TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or HPE Aruba Networking.

    In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
    ------------------------------

    Original Message


  • 7.  RE: Problem adding VLAN to lagg in 1950 stack

    Posted Aug 07, 2025 05:43 AM

    Hi Herman, despite your suggestion I suspect that the Aruba InstantON community forum is not the right place to forward similar (sporadic) requests: I believe that who knows about the Aruba InstantON switch series doesn't necessarily know about the older HPE 19x0 switch series (e.g. the 1920, 1920S and the 1950)...and the fact that Aruba InstantON used the 18x0 and 19x0 nomenclatures (as example see the 1930 and 1960) doesn't help at all because that is still confusing uneducated users and, in the end, we are speaking of comparing apples versus oranges, yes...both are fruits but different ones (InstantON are basically Cloud managed, the others are still locally Web Based GUI managed with some capability on the CLI side).

    To further sustain my opinions, if I counted them correctly, there are only two threads involving the HPE 1950 in 5 Years on the Aruba InstantON community portal:

    A really sad outcome. Cheers, Davide.

    -------------------------------------------

    Original Message


Related Content