+ Post New Thread
Results 1 to 2 of 2
Wired Networks Thread, Tagging VLAN 1 - Powerconnect in Technical; Morning all, As the title suggests, does anyone have any idea if it is possible to tag VLAN 1, i.e. ...
  1. #1

    Join Date
    Sep 2011
    Thank Post
    Thanked 17 Times in 15 Posts
    Rep Power

    Tagging VLAN 1 - Powerconnect

    Morning all,

    As the title suggests, does anyone have any idea if it is possible to tag VLAN 1, i.e. the native VLAN in Powerconnect switches, across all ports, much like the vlan dot1q tag native command on cisco switches? We have a 2848.

    I know they don't allow it for best practice and security reasons, but like a lot of systems that start on the native vlan, it isn't easy to go round and reprogram each and every switch, just because Dell made a decision!

    I know the answer will be a systematic reprogram of all switches but thought I'd ask after googling failed!



  2. #2

    Join Date
    Apr 2012
    Thank Post
    Thanked 0 Times in 0 Posts
    Rep Power
    In case those PowerConnects have a similar CLI as IOS (some of their switches are OEM-Broadcom Hard- and Software) and share similar Broadcom underlying FastPath software as a couple of Netgears. Anyway, I've even gone this far to ban VLAN 1 from every port (On Netgear in global config mode it's: vlan partitipcation exclude 1 all) since it's otherwise auto-included as untagged on every port.

    If you want to accept it only tagged without banning, there is no such thing as native VLANs as on Cisco. On those boxes you include a VLAN on a port (if it's not already), then tell it to be tagged (otherwise it's not).
    Then you don't want to miss the Port VLAN ID (PVID) setting which tells the switch what to do with untagged ingress traffic - that's most likely on default 1. By changing it to another (even blackhole VLAN) you stop accepting traffic on VLAN 1 on those (access?) ports.

    If you switches are as similar to Netgears according to the snippets I saw in the manual, then you might be able to enable VLAN ingress filtering which will make sure that even if the port is not part of that VLAN - memberships is only applying to egress traffic on a Port - ingress traffic to VLAN 1 will still be accepted on ports that are not members of VLAN (i.e. exclude it).

    Although not a replacement for a complete CLI manual it's already something, and if you are familiar with Cisco a couple of commands are very similar and I found the CLI to be quicker than clunky webinterfaces ;-)

    Good luck!

+ Post New Thread

Similar Threads

  1. Hyper-V VLAN Tagging - 2 or more VM's (Server 2008)
    By mo_vigilante in forum Windows Server 2008
    Replies: 2
    Last Post: 30th October 2013, 10:16 AM
  2. Workstation VLAN Tagging
    By darrenmcginnis in forum Hardware
    Replies: 16
    Last Post: 2nd September 2013, 12:14 PM
  3. BYOD VLAN - Some help with VLAN tagging please
    By robknowles in forum Wired Networks
    Replies: 1
    Last Post: 8th September 2012, 10:03 AM
  4. Changing port vLANs on an HP ProCurve switch
    By MrDylan in forum Hardware
    Replies: 6
    Last Post: 9th March 2006, 04:13 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts