Wired Intelligent Edge

last person joined: 2 days ago 

Bring performance and reliability to your network with the HPE Aruba Networking Core, Aggregation, and Access layer switches. Discuss the latest features and functionality of your switching devices, and find ways to improve security across your network to bring together a mobile-first solution
Back to discussions
Expand all | Collapse all

2930F how to make it as TAGGED PORT to enable talked to Fortigate applicance and wireless controller

This thread has been viewed 10 times

  • 1.  2930F how to make it as TAGGED PORT to enable talked to Fortigate applicance and wireless controller

    Posted Jul 30, 2017 09:25 PM

    ARUBA.JPG

    how to configure these ports 46,47and 48 as trunk port i already tagged them to all VLANs..thank you!



  • 2.  RE: 2930F how to make it as TAGGED PORT to enable talked to Fortigate applicance and wireless controller
    Best Answer

    EMPLOYEE
    Posted Jul 31, 2017 04:35 AM

    There is no trunk (port with tagged vlans) or access mode on the ArubaOS switches. Just putting VLANs as tagged on the interface will do the job. A maximum of one VLAN can be untagged on a port. Example for an uplink port (10) that has a few VLANs as tagged:

    hp2530# show running-config interface 10

Running configuration:

interface 10
   dhcp-snooping trust
   tagged vlan 2,5-6,9,31-37
   exit

     



  • 3.  RE: 2930F how to make it as TAGGED PORT to enable talked to Fortigate applicance and wireless controller

    Posted Aug 07, 2017 11:06 PM

    thanks, u mean by just tagging that port it can talked already to WLC and FW(configured with VLAN also) ?



  • 4.  RE: 2930F how to make it as TAGGED PORT to enable talked to Fortigate applicance and wireless controller

    EMPLOYEE
    Posted Aug 08, 2017 05:13 AM

    When you add the VLAN tagged to a port, and the device on the other side of the link has the same VLAN tagged (and may be port in trunk-mode), yes they can communicate over that VLAN.

     

    Small side-step, on ArubaOS Switches, a trunk is what is called an etherchannel on other platforms. So if you define trunk ports, you can add multiple physical ports that form a higher capacity and redundant link most times to other switches like your core. If you are reading the documentation, that may be confusing. If you are familiar with Cisco or Comware commands, this ArubaOS-Switch, Comware and Cisco IOS CLI Reference Guide may be useful.

     

    So, yes you will be fine if you add the VLANs tagged on both sides. No need to switch port mode.