Network Management

 View Only

  • 1.  HPE 2530-48G POE+ Tagged VLAN

    Posted Mar 15, 2023 10:42 AM

    I am working on testing VLAN setups as we are working towards implementing them across our network. We have mostly HPE J9772A switches and I am running across a bit of what I think is a weird issue. I have tested this with the default VLAN1 and also with a new VLAN10.

    Below is the current config of the switch. Port 47 goes to a test Sonicwall switch and port 49 goes to a layer 3 HPE 1920 switch. I have a laptop plugged into port 11 and if that port is Untagged, then I can ping everywhere including the VLAN ip of 172.16.0.2. If I simply change that port to Tagged, then I cannot ping anything at all and cannot get to the web interface of the switch. I've tried it with each VLAN and it is the same scenario, but the Tagged 47 and 49 ports work as they should between the switches.

    Is this normal behavior and I am way off in my limited knowledge of VLAN's? Or is there something funky going on with this switch? I don't see how you could have a Tagged voice vlan and Untagged data vlan on the same port in this scenario. 



  • 2.  RE: HPE 2530-48G POE+ Tagged VLAN

    Posted Mar 15, 2023 01:21 PM
    Hi, your host is VLAN unaware, tagging the port it is connected to on the switch side requires you to configure the host network port with a corresponding VLAN Id (if its network adapter supports such configuration <- generally that is supported but it requires you to apply a configuration since the default condition is often associated with VLAN Id 1 and untagged egress traffic).





  • 3.  RE: HPE 2530-48G POE+ Tagged VLAN

    Posted Mar 15, 2023 04:29 PM

    Ok that is what I was wondering about, but did not know that there was VLAN ID setting in the network connections. So how would this work with a VOIP system? Do you have to set the VLAN ID on each phone or do most VOIP Systems propagate that ID out from the cabinet?


    Original Message


  • 4.  RE: HPE 2530-48G POE+ Tagged VLAN

    Posted Mar 16, 2023 12:04 PM

    Also, is this only an HPE switch setting? That you have to set the VLAN ID for it to work on the tagged port? I can take the same laptop (without VLAN ID set) and plug it into a tagged port on our Sonicwall switch, and it will work as intended.


    Original Message


  • 5.  RE: HPE 2530-48G POE+ Tagged VLAN

    Posted Mar 16, 2023 04:59 PM
    I doubt you can (you believe it's working for a reason but it's working for another).

    It's not just a "HPE Switch" affair...it's how tagging works.

    Let me to suppose I tag a Switch port used for access with a particular VLAN Id (the Tagged VLAN Id is then the port unique VLAN Id or PVID, in this case a counter intuitive "Native" tagged VLAN Id), that port will drop any ingressing traffic not carrying the particular VLAN Id used...in other terms it will accept only ingress traffic with that particular VLAN Id. The egressing traffic will leave the port with that particular VLAN Id tag...and so it is friendly called tagged (on that VLAN Id).

    How an host totally "VLAN Tag unaware" (with the NIC Ethernet port's traffic leaving the port not tagged) is able to communicate with a Switch port - like the one in my above example - that is configured to receive/send only tagged traffic on a particular VLAN Id?

    It can only if the NIC Ethernet port provides the feature of tagging traffic with that particular VLAN Id, if it can't...there will not be communication between Switch and NIC port.

    So a question: how Sonicwall port is configured to make you believe it's working?




    Original Message


Related Content