Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    2.7.0ce release VLAN tagging not working at all on LAN port DELL R410 server.

    Scheduled Pinned Locked Moved L2/Switching/VLANs
    2 Posts 1 Posters 181 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N8LBVN
      N8LBV
      last edited by N8LBV

      This is my first bout with 2.7.0ce and I'm not exactly sure what I'm up against yet.
      More details to follow as I work through it.
      I am working on a Dell R410 server (Broadcomm NICS) and VLAN tagging to OPT1 on the LAN port is absolutely not working.
      It appears that the packets are not getting tagged at all.
      Sorry do not have more details but will soon.
      Ended up having to install on a different older Dell Poweredge 2950 server which is working and Tagging the packets as expected.
      Do add to the confusion the "broken" server was restored from a 2.7.0dev backup file to upgrade to 2.7.0 release (which is supposed to work and be supported).
      I have yet to try a factory default and configure VLAN on it from scratch and see if have the same problem or not.
      Anyhow just starting this conversation without a lot of detail just to get it started.
      I will likely be pulling the R410 server to investigate further and continue this.
      First time I have run into this problem..
      It's weird and rather inconvenient so far.
      I am trying to add the tagged VLAN just now.
      It did not exist in the restored configuration.
      I have also tried completely blowing away the interfaces and re-creating them.
      This did not fix it.
      :)

      I feel more like I do now.

      N8LBVN 1 Reply Last reply Reply Quote 0
      • N8LBVN
        N8LBV @N8LBV
        last edited by

        It works just fine.
        I spent 4 hours scratching my head and troubleshooting almost everything technical about this and not seeing the VLAN tagging packets coming from What I thought was the otehr end of a cable on the LAN interface.
        This because I was trusting which very obvious and only cable of its color was feeding the uplink port on the main switch.
        I even drove a couple hours and back to go grab another server (different hardware) that I knew was working.
        Just as I went to rack and connect the different server, I could see that we had been on the wrong cable all along SMH.
        Heat and dehydration were factors and just trying stuff trying to figure it out totally trusting the information I was given about the cable feeding the switch.
        Which is usually a solid accurate and trusted source on a normal day :)
        Sorry for the false alarm.
        I really need to kick myself harder this time.
        No excuse for this crap. I'm usually better than that.

        I feel more like I do now.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.