Wired Intelligent Edge

 View Only
Expand all | Collapse all

Help needed - adding ArubaOS-CX devices to Procurve network

This thread has been viewed 51 times
  • 1.  Help needed - adding ArubaOS-CX devices to Procurve network

    Posted Feb 13, 2024 11:02 AM
    Edited by urosg Feb 13, 2024 12:14 PM

    Hi all!

    I am facing a problem with basic configuration on new Aruba switches (6200F series).

    Until now we used exclusively Procurve switches but with the new shipment we received Aruba switches where we have basic problems with VLAN configurations.

    I tried different variants for configuration but can not seem to succeed in wanted configuration.

    Main link (router) has present VLANs 2,20 and 22 which is connected to a Procurve switch where the interface is tagged for these VLANs, this same switch then tags these same VLANs to an outgoing interfaces where the new switches (two at this moment) are connected.

    On this switches I made simple configuration:

    Procurve switch has IP 10.1.2.2 on VLAN 2

    Switch 1 (uplink from this switch is 1/1/49):

    vlan 2

    vlan 20

    vlan 22

    interface 1/1/49

      vlan trunk allowed 2,20,22

      vlan trunk native 2 tag

    interface vlan 2

      ip address 10.1.2.13/24

    Switch 2 (uplink for this switch is 1/1/27):

    vlan 2

    vlan 20

    vlan 22

    interface 1/1/27

      vlan trunk allowed 2,20,22

      vlan trunk native 2 tag

    interface vlan 2

      ip address 10.1.2.14/24

    After this configuration I can ping between switches but I can not ping switch from router on VLAN2 nor from Procurve switch.

    I tried also doing "vlan trunk native 2" and untagging vlan 2 on procurve, same effect.

    Simply new switches see each other but I can not communicate with the rest of the network, nor does it forward traffic if I then set an interface to "vlan access 2" and a client device on that interface does not get an IP from DHCP server on VLAN 2.

    I know this must be a basic setting that I am missing, but until now I could not find the reason.

    Help would be really appreciated.

    Uros

    EDIT: corrected IP of VLAN2 on switch 2



  • 2.  RE: Help needed - adding ArubaOS-CX devices to Procurve network

    Posted Feb 13, 2024 11:11 AM

    This output seems a bit confusing. but it does appear that you are putting the same IP address on the VLAN 2 Interface of both switch 1 and switch 2. 

    Was this a typo? You cannot have the same IP Address on an interface in the same VLAN. On switch 2, interface VLAN 2, set the IP to 10.1.2.14/24 or any other IP that is available in that IP range, just can't use 10.1.2.13/24 since it was assigned to VLAN 2 interface of switch 1. At least this is the first thing I see as an issue with the config you have provided.

    Interfaces 1/1/49 & 1/1/27 seem to be correct.




  • 3.  RE: Help needed - adding ArubaOS-CX devices to Procurve network

    Posted Feb 13, 2024 12:13 PM

    Yes, sorry that was a typo - I copy pasted and missed to correct the IP for the second switch.




  • 4.  RE: Help needed - adding ArubaOS-CX devices to Procurve network

    Posted Feb 13, 2024 01:32 PM

    What is the Untagged VLAN on the ProCurve and the router?

    Can you provide the configs of the ports for the upstream ProCurve and the router?




  • 5.  RE: Help needed - adding ArubaOS-CX devices to Procurve network

    Posted Feb 14, 2024 03:12 AM

    The untagged VLAN on the procurve is VLAN1; uplink port has:

     Status and Counters - VLAN Information - for ports 25

      Port name: 10GB Uplink
      VLAN ID Name                 | Status     Voice Jumbo Mode
      ------- -------------------- + ---------- ----- ----- --------
      1       DEFAULT_VLAN         | Port-based No    No    Untagged
      2       VLAN2                | Port-based No    No    Tagged
      3       VLAN3                | Port-based No    No    Tagged
      4       VLAN4                | Port-based No    No    Tagged
      20      VLAN20               | Port-based No    No    Tagged
      21      VLAN21               | Port-based No    No    Tagged
      22      VLAN22               | Port-based No    No    Tagged
      23      VLAN23               | Port-based No    No    Tagged
      24      VLAN24               | Port-based No    No    Tagged

    To this interface an 10Gbit Mikrotik switch is connected which is VLAN agnostic (does NOT have VLAN filtering enabled); to this switch there are currently 6 switches connected now (two of them are the new Aruba 6200F); all VLAN traffic works without problems on the Procurve switches (2500 and 2900 series) that are connected through this link. I have tried connecting the new Arubas directly to Procurve switch also, but no luck.

    Whole network on this location consists of Mikrotik Routers and 26 Procurve switches, we are now trying to add these new Aruba switches and are having some problems...




  • 6.  RE: Help needed - adding ArubaOS-CX devices to Procurve network

    Posted Feb 14, 2024 05:57 AM

    You wrote earlier:

    interface 1/1/49
      vlan trunk allowed 2,20,22
      vlan trunk native 2 tag
    

    which does not match the output that you shared from the procurve. Not sure why you have the vlan trunk native 2 tag, never seen that.

    To match the procurve output, please try on CX:

    interface 1/1/49
      switchport mode trunk
      vlan trunk allowed 1-4,20-24


    ------------------------------
    Herman Robers
    ------------------------
    If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
    ------------------------------



  • 7.  RE: Help needed - adding ArubaOS-CX devices to Procurve network

    Posted Feb 14, 2024 06:22 AM

    Command "switchport" is not recognized on ArubaOS-CX. 

    I know that the configuration differs as I was trying different approaches so I had tried also just with one VLAN, etc.

    Current interface configuration:

    interface 1/1/49
        no shutdown
        no routing
        vlan trunk native 1
        vlan trunk allowed 1-2,20,22
        exit
    



  • 8.  RE: Help needed - adding ArubaOS-CX devices to Procurve network

    Posted Feb 14, 2024 07:03 AM

    Provided the config from memory, but what you have now looks correct to have VLAN 1 (probably not used) untagged on the interface, and VLAN 2,20,22 tagged.

    Example from a live switch:

    interface xxxx
        no shutdown
        no routing
        vlan trunk native 1
        vlan trunk allowed 10,200
     


    ------------------------------
    Herman Robers
    ------------------------
    If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
    ------------------------------



  • 9.  RE: Help needed - adding ArubaOS-CX devices to Procurve network

    Posted Feb 14, 2024 07:06 AM

    I agree, from my understanding the basic configuration should work.

    Along with the port configuration I have:

    interface vlan 2
        ip address 10.1.2.<x>/24
        exit
    

    where <x> is the IP of the configured switch and I can not ping any other devices on the VLAN 2 as I would expect to be able to do so nor do I see an ARP entry in any upstream devices for this switch.




  • 10.  RE: Help needed - adding ArubaOS-CX devices to Procurve network

    Posted Feb 14, 2024 07:57 AM

    I would check the mac table on both ends to see what MAC addresses are seen. ARP only works if there is already connectivity.

    Example:

    CX6300F# show mac-address-table
    MAC age-time            : 300 seconds
    Number of MAC addresses : 4
    
    MAC Address          VLAN     Type                      Port
    --------------------------------------------------------------
    b0:5a:da:98:a8:b0    10       dynamic                   1/1/1


    ------------------------------
    Herman Robers
    ------------------------
    If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
    ------------------------------



  • 11.  RE: Help needed - adding ArubaOS-CX devices to Procurve network

    Posted Feb 14, 2024 09:20 AM

    What is the port to port connection configuration between the 6300f switches and the ProCurve?

    What port of the 6300f Switch #1 connects to what port of the Procurve? Please provide config of interfaces from both the 6300f and Procurve.

    What port of the 6300f Switch #2 connects to what port of the Procurve? Please provide config of interfaces from both the 6300f and Procurve.




  • 12.  RE: Help needed - adding ArubaOS-CX devices to Procurve network

    Posted Feb 14, 2024 12:39 PM
    Already posted interface configurations are for the connecting interfaces.




  • 13.  RE: Help needed - adding ArubaOS-CX devices to Procurve network

    Posted Feb 15, 2024 12:33 PM
    To close this issue; we have identified the problem; configuration was correct all along but my colleague that was onsite has misidentified uplink (mid-link) switch and after spending almost whole day scouring the network I could not find the active link as it should have been…

    Thank you all for all the input.