Wired

 View Only
last person joined: 20 hours ago 

Expand all | Collapse all

Help on 6200M

This thread has been viewed 33 times
  • 1.  Help on 6200M

    Posted Feb 02, 2024 10:03 AM

    Hi everyone.

    We are replacing our ancient HP2620 routers and moving to 6200M / 6100. We are very well versed with the HP 2620 but are struggling with the new 6200M. Our network is very basic and we only have 2 VLANS. The first is a general VLAN and the second is a VLAN for our warehouse WiFi network. Both VLANS can currently talk to each other.

    On our HP2620 we have VLAN 1 set as untagged across all ports and Trk1. On VLAN 2 we have all ports set as Tagged.

    How do I replicate this on the 6200M as the tagged / untagged CLI commands do not seem to work anymore. The commands seem to have changed quite a lot and we have gotten as far as being able to ping the gateway from each VLAN but cannot ping PC's in each VLAN.

    Any help / advice is much appreciated!



  • 2.  RE: Help on 6200M

    Posted Feb 02, 2024 03:25 PM

    I'm guessing the 2620 is the old Procurve/ArubaOS operating system?

    Your old CLI config probably looks like this, correct?

    vlan 1

    untagged 1-48,Trk1

    exit

    vlan 2

    tagged 1-48,Trk1

    exit

    the 6200's are Aruba CX so these switches are structurally different. You have to do the following:

    1. define the VLAN
    2. create the VLAN interface (if it's just a Layer 2 vlan interface, you only create the interface, if it's the L3 SVI, give it an IP)
    3. set your native (untagged) and allowed (tagged) vlans at the interface level

    Here is how you do it

    vlan 1

    name VLAN1

    exit

    vlan 2

    name VLAN2

    exit

    interface vlan 1

    description VLAN1

    exit

    interface vlan 2

    description VLAN2

    exit

    interface 1/1/1

    vlan trunk native 1

    vlan trunk allowed 1,2

    exit

    The "allowed" vlan lists what VLAN's can be on the interface. anything that isn't "native" automatically is assumed as a tagged vlan, but you do have to include the native vlan ID in the allowed list. Here, VLAN 1 is untagged, while VLAN 2 ends up being tagged. if you had vlan's 3-10 listed , they'd also all be "tagged"

    this guide does an ok job of helping you understand the differences between the procurve/ArubaOS syntax and the new Aruba CX platform 

    https://www.hpe.com/psnow/doc/c04793912




  • 3.  RE: Help on 6200M

    Posted Feb 02, 2024 03:35 PM

    One other thing, if your uplink ports are redundant using LACP, then on the Aruba CX ports, you are creating a LAG interface, much like you create the Trk1 trunk port. 

    Instead of Trk1, now you might have "interface lag 1". under that interface would also be where you tag your vlans

    Example: On one of my aruba switches that I'm currently testing, I have the following:

    interface lag 1
        description Core Switch uplink
        no shutdown
        no routing
        vlan trunk native 1 tag
        vlan trunk allowed all
        lacp mode active
        rate-limit broadcast 1000000 kbps
        rate-limit icmp ip-all 1000000 kbps
        arp inspection trust
        dhcpv4-snooping trust

    I realize I'm being lazy with the "allowed all". but the "tag" after "native 1" tells the LAG interface to only accept tagged packets on that interface. while VLAN 1 is the default built in VLAN, my actual VLANs on this test switch are three different vlans and those are all tagged. We just did it that way for whatever reason. We left VLAN 1, unused, and tagged all the other VLAN's on the LAG interface.

    (hopefully I'm using the correct terminology ... Cisco and HP/Aruba use trunk and access ports different ways. CX is a lot more like Cisco IOS than Aruba O/S was.)




  • 4.  RE: Help on 6200M

    Posted Feb 08, 2024 03:50 AM

    Thanks for the reply's so far. I think I am missing something here so I'll post what the ruuning-config has:

    vlan 2

    name Office

    vlan 3

    name WiFi

    spanning-tree

    interface 1/1/1

    no shutdown

    no routing

    vlan trunk native 2

    vlan trunk allowed 2-3

    interface 1/1/3

    no shutdown

    no routing

    vlan trunk native 2

    vlan trunk allowed 2-3

    interface vlan 2

    ip address 172.15.1.254/16

    interface vlan 3

    ip address 192.168.3.1/24


    PC 1 with IP 172.15.1.11 can ping 172.15.1.254 and 192.168.3.1 it cannot ping PC2

    PC2 with IP 192.168.3.2 can not ping 192.168.3.1 or 172.15.1.254 or PC1

    I hope thats enough information to see where I am going wrong on this?




  • 5.  RE: Help on 6200M

    Posted Feb 08, 2024 08:53 AM

    You assigned both interface 1/1/1 and 1/1/3 to be native vlan 2. that means 172.15.0.0/16 traffic is the default VLAN for both of those ports. PC2 needs to be on a port that is assigned to be native vlan 3, so it can receive untagged traffic on VLAN 3, but tagged traffic from other vlans

    Plug PC1 into port 1/1/1

    Change 1/1/3 to be as follows, and plug PC2 into that port

    interface 1/1/3
        no shutdown
        no routing
        vlan trunk native 3
        vlan trunk allowed 2-3

    Then try again.




  • 6.  RE: Help on 6200M

    Posted Feb 08, 2024 09:38 AM

    Many thanks for being so patient. I have made the changes ahd sh run shows:

    interface 1/1/1

    no shutdown

    no routing

    vlan trunk native 2

    vlan trunk allowes 2,3

    interface 1/1/3

    no shutdown

    no routing

    vlan trunk native 3

    vlan trunk allowed 2,3

    interface vlan 2

    ip address 172.15.1.254/16

    interface vlan 3

    ip address 192.168.3.1/24

    PC1 on 1/1/1 can ping both VLANS but not PC2 which is 192.168.3.2

    PC2 on 1/1/3 can ping both VLANS but not PC1 which is 172.15.1.11




  • 7.  RE: Help on 6200M

    Posted Feb 08, 2024 01:20 PM

    are your PC's set to use those Layer 3 SVI IP's as their default gateway?

    PC1 should be using a gateway address of 172.15.1.254, with a subnet address of 255.255.0.0

    PC2 should be using the gateway of 192.168.3.1, with a subnet address of 255.255.255.0

    At this point, all of your intervlan routing should be working, so I'm wondering if it's an issue of the PC's knowing what gateway address to use.

    if you can post the ipconfigs and a "route print" of the two stations, it would be helpful.




  • 8.  RE: Help on 6200M

    Posted Feb 09, 2024 02:50 AM

    PC1 on 1/1/1 is configured as follows:

    IP 172.15.1.11 Subnet 255.255.0.0 Gateway 172.15.1.254

    PC2 on 1/1/3 is configured as follows:

    IP 192.168.3.2 Subnet 255.255.255.0 Gateway 192.168.3.1

    PC1 route print

    C:\Users\TBC>route print
    ===========================================================================
    Interface List
      6...a0 29 19 43 cc f5 ......Intel(R) Ethernet Connection (13) I219-LM
     41...a0 ce c8 66 4a 4e ......ASIX AX88179 USB 3.0 to Gigabit Ethernet Adapter
      7...d4 54 8b 5e bd da ......Microsoft Wi-Fi Direct Virtual Adapter
      3...d6 54 8b 5e bd d9 ......Microsoft Wi-Fi Direct Virtual Adapter #2
      5...d4 54 8b 5e bd d9 ......Intel(R) Wi-Fi 6 AX201 160MHz
     10...d4 54 8b 5e bd dd ......Bluetooth Device (Personal Area Network)
      1...........................Software Loopback Interface 1
    ===========================================================================

    IPv4 Route Table
    ===========================================================================
    Active Routes:
    Network Destination        Netmask          Gateway       Interface  Metric
              0.0.0.0          0.0.0.0     172.15.1.254      172.15.1.11    281
            127.0.0.0        255.0.0.0         On-link         127.0.0.1    331
            127.0.0.1  255.255.255.255         On-link         127.0.0.1    331
      127.255.255.255  255.255.255.255         On-link         127.0.0.1    331
           172.15.0.0      255.255.0.0         On-link       172.15.1.11    281
          172.15.1.11  255.255.255.255         On-link       172.15.1.11    281
       172.15.255.255  255.255.255.255         On-link       172.15.1.11    281
            224.0.0.0        240.0.0.0         On-link         127.0.0.1    331
            224.0.0.0        240.0.0.0         On-link       172.15.1.11    281
      255.255.255.255  255.255.255.255         On-link         127.0.0.1    331
      255.255.255.255  255.255.255.255         On-link       172.15.1.11    281
    ===========================================================================
    Persistent Routes:
      Network Address          Netmask  Gateway Address  Metric
              0.0.0.0          0.0.0.0     172.15.1.254  Default
    ===========================================================================

    IPv6 Route Table
    ===========================================================================
    Active Routes:
     If Metric Network Destination      Gateway
      1    331 ::1/128                  On-link
      1    331 ff00::/8                 On-link
    ===========================================================================
    Persistent Routes:
      None

    PC2 route print

    C:\Users\TBC>route print
    ===========================================================================
    Interface List
      8...a4 4c c8 07 5c cd ......Intel(R) Ethernet Connection (4) I219-LM
     15...f8 59 71 bd 69 4c ......Intel(R) Dual Band Wireless-AC 8265
     16...f8 59 71 bd 69 4d ......Microsoft Wi-Fi Direct Virtual Adapter
      6...f8 59 71 bd 69 50 ......Bluetooth Device (Personal Area Network)
      1...........................Software Loopback Interface 1
    ===========================================================================

    IPv4 Route Table
    ===========================================================================
    Active Routes:
    Network Destination        Netmask          Gateway       Interface  Metric
              0.0.0.0          0.0.0.0      192.168.3.1      192.168.3.2    281
            127.0.0.0        255.0.0.0         On-link         127.0.0.1    331
            127.0.0.1  255.255.255.255         On-link         127.0.0.1    331
      127.255.255.255  255.255.255.255         On-link         127.0.0.1    331
          192.168.3.0    255.255.255.0         On-link       192.168.3.2    281
          192.168.3.2  255.255.255.255         On-link       192.168.3.2    281
        192.168.3.255  255.255.255.255         On-link       192.168.3.2    281
            224.0.0.0        240.0.0.0         On-link         127.0.0.1    331
            224.0.0.0        240.0.0.0         On-link       192.168.3.2    281
      255.255.255.255  255.255.255.255         On-link         127.0.0.1    331
      255.255.255.255  255.255.255.255         On-link       192.168.3.2    281
    ===========================================================================
    Persistent Routes:
      Network Address          Netmask  Gateway Address  Metric
              0.0.0.0          0.0.0.0      192.168.3.1  Default
    ===========================================================================

    IPv6 Route Table
    ===========================================================================
    Active Routes:
     If Metric Network Destination      Gateway
      1    331 ::1/128                  On-link
      8    281 fe80::/64                On-link
      8    281 fe80::da3a:579b:7d11:e024/128
                                        On-link
      1    331 ff00::/8                 On-link
      8    281 ff00::/8                 On-link
    ===========================================================================
    Persistent Routes:
      None




  • 9.  RE: Help on 6200M

    Posted Feb 12, 2024 08:59 AM

    you also declare the vlans near the top of the config, right?

    with your config, interVLAN routing should work. I haven't done intervlan routing myself on the CX switches except at the core level. The CX's have done weird things if there isn't an interface on a trunk interface that actually is in the up state

    can you post two outputs on the switch?

    • show ip route
    • show vlan

    also, for funs and giggles, disable windows firewall on the machines and see what happens