Wired

 View Only
last person joined: yesterday 

Back to discussions
Expand all | Collapse all

2930F Untagged Vlan

This thread has been viewed 70 times

  • 1.  2930F Untagged Vlan

    Posted Mar 25, 2021 11:47 AM
      |   view attached
    Hello, i have a situation with switch model  Aruba 2930F. I want to assign a port(ex 20) to an untagged vlan, let's say on vlan4. 

    Initial status for port 20:

    1. ArubaVSF_1# sho runn int 1/20

                Ru1nning configuration:

                interface 1/20

               untagged vlan 1

               exit

    2. Triyng to put untagged vlan4 on port20:

    ArubaVSF_1# conf t

                ArubaVSF_1(config)# int 1/20

                ArubaVSF_1(eth-1/20)# untagged vlan 4

                4: Inconsistent value.

                ArubaVSF_1(eth-1/20)# untag vlan 99

                99: Inconsistent value

    3. If am triyng to put port20 tagged on vlan4 it let me:

    ArubaVSF_1(eth-1/20)# tagg vlan 4

     

                ArubaVSF_1(eth-1/20)# sho runn int 1/20

                Running configuration:

                interface 1/20

               tagged vlan 4

               untagged vlan 1

               exit



    4. I'm removing tagging from vlan4:

    ArubaVSF_1(eth-1/20)# no tagg vlan 4

     

            ArubaVSF_1(eth-1/20)# sho runn int 1/20

            Running configuration:

            interface 1/20

           untagged vlan 1

       exit

    5. Triyng to put untagged on vlan10 for ex.:

    ArubaVSF_1(eth-1/20)# untagged vlan 10

            10: Inconsistent value.

            ArubaVSF_1(eth-1/20)#

    I need some help, i have 2 switches(2930F) in vsf stack. I just want to assign any port(20 for ex.) untagged on any vlan(let's say 4), what is with 'Inconsistent value'? On another switch(2930F) which dosen't belong to vsf, it is in another configuration scheme , i can do this.  Is it true that i have another firmware version on the switch that i can do untagged. Those in vsf stack have #WC.16.10.0010 version.
    I also attached configuration.
    Thank you in advance!

      



    ------------------------------
    Dragos Ilie
    ------------------------------

    Attachment(s)

    docx
    config.docx   21 KB 1 version


  • 2.  RE: 2930F Untagged Vlan

    Posted Mar 26, 2021 06:29 AM
    you should assign port to vlan 4

    vlan 4
    untagged 1/20

    ------------------------------
    jongyong park
    ------------------------------

    Original Message


  • 3.  RE: 2930F Untagged Vlan

    MVP GURU
    Posted Mar 26, 2021 01:06 PM
    Technically speaking the procedure to assign the Untagged/Tagged membership(s) for a particular VLAN ID to a particular (Physical/Logical) interface (aka port) should work either way:

    • Context -> Interface id (or range) -> tag or untag assignment to VLAN ID (or range of IDs)
    • Context -> VLAN id -> tag or untag assignment to interface ID (or range of IDs)
    generally the latter is the preferred way working on HPE Aruba ArubaOS-Switch OS (or legacy HP ProVision OS) because it matches the "VLAN centric" fashion of the OS (but, again, it should work using both modes).

    The former is typically adopted when working on other Network OSes like the Comware 5/7 or the HPE Aruba ArubaOS-CX, OSes that are more "interface-centric" than ArubaOS-Switch.

    ------------------------------
    Davide Poletto
    ------------------------------

    Original Message


  • 4.  RE: 2930F Untagged Vlan

    Posted Mar 26, 2021 01:09 PM
      |   view attached
    Hi,

    Try to change the configuration from the vlan not from the port
     Check if there is an ip assigned to the vlan
    In the manual I send you are all the aruba switch event messages

    Good Luck !
    Ciro Gustavo Mele

    ------------------------------
    Ciro Gustavo Mele
    ------------------------------

    Attachment(s)

    pdf
    ArubaOS-Switch_Logs.pdf   1.66 MB 1 version
    Original Message


  • 5.  RE: 2930F Untagged Vlan

    Posted Mar 30, 2021 10:39 AM
    Hi, thank you for the info. Still i cannot do untagged port to vlan:

    ==========this is vlan 4=================

    ArubaVSF_1# sho runn vlan 4
    Running configuration:
    vlan 4
       name "VOIP"
       tagged 1/6,1/25-1/33,2/6,2/13-2/17,2/46,Trk1-Trk2,Trk4-Trk9
       untagged 1/22
       ip address 192.168.4.254 255.255.254.0
       ipv6 enable
       ipv6 address autoconfig
       exit

    ==============this is port 1/20===================
    ArubaVSF_1# sho runn int 1/20
    Running configuration:
    interface 1/20
       untagged vlan 1
       exit

    ==========triyng from port to vlan============
    ArubaVSF_1# conf t
    ArubaVSF_1(config)# int 1/20
    ArubaVSF_1(eth-1/20)# untagged vlan 4
    4: Inconsistent value.
    ArubaVSF_1(eth-1/20)# end
    ArubaVSF_1# sho runn int 1/20
    Running configuration:
    interface 1/20
       untagged vlan 1
       exit

    =========trying from vlan 4 to port============
    ArubaVSF_1# conf t
    ArubaVSF_1(config)# vlan 4
    ArubaVSF_1(vlan-4)# untagged 1/20
    1/20: Inconsistent value.
    ArubaVSF_1(vlan-4)# end
    ArubaVSF_1# sho runn vlan 4
    Running configuration:
    vlan 4
       name "VOIP"
       tagged 1/6,1/25-1/33,2/6,2/13-2/17,2/46,Trk1-Trk2,Trk4-Trk9
       untagged 1/22
       ip address 192.168.4.254 255.255.254.0
       ipv6 enable
       ipv6 address autoconfig
       exit



    ------------------------------
    Dragos Ilie
    ------------------------------

    Original Message


  • 6.  RE: 2930F Untagged Vlan

    Posted Mar 30, 2021 11:16 AM
    Maybe it can be something phisical? I don't know..i am afraid to upgrade firmware from #WC.16.10.0010 to WC_16_10_0012. Maybe the upgrade will help me?

    Thank you.

    ------------------------------
    Dragos Ilie
    ------------------------------

    Original Message


  • 7.  RE: 2930F Untagged Vlan

    MVP GURU
    Posted Mar 30, 2021 11:43 AM
    Hi Dragos, does it let you to tag the port 1/20 with VLAN id 4? I mean...instead of changing the untagged VLAN id (PVID)...that's to see if the issue if with "untagging" the port only or it happens too with "tagging" the port with that particular VLAN id...what client are you using to perform CLI commands? PuTTY SSH? PuTTY direct Serial? other? maybe a bug in WC.16.10.0010? pretty strange.

    Have you tried to reboot the switch or to perform the same operation through the CLI Menu mode? in any case save the running configuration. It the running configuration file "clean"?

    ------------------------------
    Davide Poletto
    ------------------------------

    Original Message


  • 8.  RE: 2930F Untagged Vlan

    Posted Mar 31, 2021 10:23 AM
    Hi,  if i am tagging the port in vlan 4 i can do this, with no problem. The problem is when i try to untagg from vlan1. It dosen't come out from  untagged vlan1 so that i can put untagged in vlan4.

    Sim:

    ArubaVSF_1# sho runn int 1/20

    Running configuration:

    interface 1/20
    untagged vlan 1
    exit

    ArubaVSF_1# conf t
    ArubaVSF_1(config)# int 1/20
    ArubaVSF_1(eth-1/20)# tagg vlan 4
    ArubaVSF_1(eth-1/20)# sho runn int 1/20

    Running configuration:

    interface 1/20
    tagged vlan 4
    untagged vlan 1
    exit

    ArubaVSF_1(eth-1/20)# no tagged vlan 4
    ArubaVSF_1(eth-1/20)# sho runn int 1/20

    Running configuration:

    interface 1/20
    untagged vlan 1
    exit

    ArubaVSF_1(eth-1/20)# untagg vlan 4
    4: Inconsistent value.
    ArubaVSF_1(eth-1/20)#
    ArubaVSF_1(eth-1/20)# sho runn int 1/20
    Running configuration:
    interface 1/20
    untagged vlan 1
    exit
    ArubaVSF_1(eth-1/20)#

    ------------------------------
    Dragos Ilie
    ------------------------------

    Original Message


  • 9.  RE: 2930F Untagged Vlan

    EMPLOYEE
    Posted Jun 22, 2022 02:28 PM
    Hi 

    This is a known issue that is fixed in the latest codes.

    For some reason, the port config would have been removed and the index also removed from the egress-map saved in config.
    Since ports are not present in the egress map (which means these ports are not part of any VLAN present in the system), when we try to configure any port on any VLAN we will see this error. ( Inconsistent Value)


    For a quick resolution boot system should fix this issue.

    To resolve this issue, we may need to erase the config and bring it up again.
    Overall recommendation

    1) Upgrade to the latest release like 16.10.0021.

    2) If the "inconsistent Value" error persists, erase the configuration and reconfigure the entire stack.



    Aruba TAC


    Original Message


  • 10.  RE: 2930F Untagged Vlan

    Posted Apr 05, 2021 03:54 AM
    Do you have stack member?

    If not, you just type port number.

    Check port index.

    show interface brief

    and 

    vlan 4
      untagged 20

    ------------------------------
    jongyong park
    ------------------------------

    Original Message