Wired

 View Only
last person joined: 17 hours ago 

Back to discussions
Expand all | Collapse all

Aruba 6300M One Way Routing

This thread has been viewed 8 times

  • 1.  Aruba 6300M One Way Routing

    Posted Jul 15, 2024 10:01 AM

    I have a new Aruba 6300M and have configured VLANs 1 and 2.   

    Each has a vlan interface acting as SVI for it's subnet set as such...
    Interface VLAN1 with IP 10.10.10.1/24  and a secondary IP 10.10.30.1/24
    Interface VLAN2 with IP 10.10.20.1/24

    I have my PC-1 plugged into a port set for VLAN 1, and give it a static IP of 10.10.10.10/24 with it's default-gateway 10.10.10.1/24

    And PC-2 has an IP of 10.10.20.20/24 and goes to a port set for vlan 2 with the default-gateway IP set as 10.20.20.1/24

    Interface VLAN 1 CAN ping Interface VLAN 2 

    Interface VLAN 2 CAN ping Interface VLAN 1 

    PC-1 CANNOT ping it's primary VLAN 1Gateway IP 10.10.10.1/24

    PC-1 CANNOT ping it's secondary VLAN 1 Gateway IP 10.10.30.1/24

    PC-1 CANNOT ping PC-2 IP 10.10.20.20/24

    PC-2 CAN ping VLAN1 Gateway IP 10.10.10.1/24

    PC-2 CAN ping PC-1 IP 10.10.10.10/24

     

    I cleared ARP and see all my device IPs.  I confirmed the IP settings on both PC's

    If PC-2 can ping Interface VLAN1 and PC-1 then that means the return traffic is making it back to PC-2, so why can't PC-1 ping it's gateway 



  • 2.  RE: Aruba 6300M One Way Routing

    Posted Jul 16, 2024 03:25 AM

    That doesn't make sense to me, and if PC2 can ping PC1, that means there is bidirectional routing, otherwise the echo-reply could not reach PC2. As you mention...

    You may have a subnet error on one of the switch VLANs or PCs (like a /16 or /8), but I would not expect the PC2->PC1 ping to work then either. Or are there any ACLs on the switch? Or firewall enabled on the PCs?

    Personally I would check the routing tables on all involved devices, and if that doesn't clarify, run a Wireshark on PC1 (and PC2) and validate the ARP, and L2/L3 information for the working and non-working pings.



    ------------------------------
    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.
    ------------------------------

    Original Message