Wired Intelligent Edge

 View Only
Expand all | Collapse all

Multiple VLANS on Aruba 2930F connected to trunk port of Cisco 3560 not getting access to 2nd vlan

This thread has been viewed 18 times
  • 1.  Multiple VLANS on Aruba 2930F connected to trunk port of Cisco 3560 not getting access to 2nd vlan

    Posted Feb 03, 2020 06:38 PM

    Please help...

    I can only get vlan 1 traffic and if I connec pc to ports 37 or 38 I get status on aruba that vlan 200 is enabled but pc gets unidentified network and no internet

     

    Cisco 3560 port config

      interface FastEthernet0/4
      switchport trunk encapsulation dot1q
      switchport trunk allowed vlan 1,2,200,1002-1005
      switchport mode trunk

     

    Aruba 2930F config

    Running configuration:

    ; JL558A Configuration Editor; Created on release #WC.16.07.0003
    ; Ver #14:01.4f.f8.1d.9b.3f.bf.bb.ef.7c.59.fc.6b.fb.9f.fc.ff.ff.37.ef:02
    hostname "Aruba-2930F-48G-740W-PoEP-4SFPP"
    module 1 type jl558a
    trunk 1 trk1 trunk
    ip default-gateway 192.168.1.1
    ip routing
    snmp-server community "public" unrestricted
    vlan 1
    name "DEFAULT_VLAN"
    no untagged 37-38
    untagged 2-36,39-52,Trk1
    ip address dhcp-bootp
    ipv6 enable
    ipv6 address dhcp full
    exit
    vlan 200
    name "North"
    untagged 37-38
    ip address 192.168.48.5 255.255.252.0
    ip helper-address 192.168.48.100
    exit
    spanning-tree Trk1 priority 4



  • 2.  RE: Multiple VLANS on Aruba 2930F connected to trunk port of Cisco 3560 not getting access to 2nd vlan

    Posted Feb 04, 2020 05:31 AM
      |   view attached

    The attached document should let you figure out the right configuration.

    Attachment(s)



  • 3.  RE: Multiple VLANS on Aruba 2930F connected to trunk port of Cisco 3560 not getting access to 2nd vlan

    Posted Feb 04, 2020 06:33 AM

    if you want to connect the aruba to cisco port Fa 0/4, make sure to tag the vlans on the port, because you are tagging the vlans on the cisco side (802.1q):

     

    interface <port>

    tagged vlan 1,2,200,1002-1005

     

    now you can connect a pc in 1 of the vlans using this config:

     

    interfac <port>

    untagged vlan <id>



  • 4.  RE: Multiple VLANS on Aruba 2930F connected to trunk port of Cisco 3560 not getting access to 2nd vlan

    Posted Feb 04, 2020 06:18 PM

    Hi @AERon, basically what you need is to uplink the Aruba 2930F to your Cisco 3560 (or, vice-versa, downlink your Cisco to your Aruba 2930F)...in other words you just need to create a single link connection between them sharing the same VLAN tagging pattern.

     

    If the Cisco 3560 has VLAN id 1, 2, 200 and the range 1002-1005 you should replicate the very same VLAN ids alson on Aruba 2930F (clearly VLAN id 1 is already present since it is the default Port VLAN id assigned to all ports in a Switch with the default factory configuration = this means all ports are untagged member of VLAN id 1).

     

    Once your Aruba 2930F has VLAN id 1, 2, 200 and the range 1002-1005 you simply need to configure the port used to link to Cisco 3560 as tagged member of those VLAN id list, suppose you are going to use port 37:

     

    interface ethernet 37 vlan tagged 1,2,200,1002-1005

     

    which means that port 37 is not untagged member of VLAN id 1 but it is tagged member of VLAN id 1 (it accepts ingressing packets with VLAN id 1 tag and tag egressing packets with that same VLAN id, it became orphaned of PVID which initially was VLAN id 1 - note that port 37 will appear as no untagged under the VLAN 1 context in running configuration - when it was simply an untagged member of that VLAN id) AND it is also tagged member of all other listed VLAN ids (it accepts ingressing packets with VLAN id = 2, 200, 1002, 1003, 1004 and 1005 and tag egressing packets with that same VLAN ids).

     

    Given that you will have port 37 linked to port 0/4 and both share the same VLAN id tagging configuration so packets with those VLAN ids can traverse the link flowing between both peer switches.