Wired Intelligent Edge

last person joined: 6 hours ago 

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

two Vlans

This thread has been viewed 30 times
  • 1.  two Vlans

    Posted Aug 25, 2021 11:49 AM
    hello Guys 

    now i have Core Switch 8320 and have 2 Management vlans (vlan ID 3 and Vlan ID 110 with subnet 192.168.x.0/24 192.168.xx.0/24
    now i need 2 Vlans can Access each others  ,
    2nd i need to allow telnet to reach my core from any switch at my network

    at end thank you

    ------------------------------
    Ahmed Fares
    ------------------------------


  • 2.  RE: two Vlans

    Posted Aug 25, 2021 07:02 PM
    Hi Ahmed Fares, if your Aruba 8320 was configured to act as the IP Router for its defined VLANs (and I don't doubt it really was) then once you configured the SVI for VLAN 3 and VLAN 110 (example):

    VLAN 3 192.168.x.254/24
    VLAN 110 192.168.y.254/24

    then automatically hosts on both VLANs can ping each others (if no ACL denies that).​

    ------------------------------
    Davide Poletto
    ------------------------------



  • 3.  RE: two Vlans

    Posted 30 days ago
    this is a topology if any one have best solution  




    ------------------------------
    Ahmed Fares
    ------------------------------



  • 4.  RE: two Vlans

    Posted 30 days ago
    You have to check that downlinks to Switch with VLAN 3 configured (those three on the left side on your diagram) and downlinks to Switches with VLAN 110 configured (those three on the right side on your diagram) are correctly VLAN mapped (VLAN membership: tagged or untagged, as required by your scenario/topology) on both ends (Aruba 8320 side and edge switches side)...respectively VLAN 3 and VLAN 110 must be "transported" where necessary (tagged or untagged, it doesn't matter <- it depends on how you structured your network).

    Once verified, you only need that each edge switch is configured with a proper IP on its VLAN 3 or VLAN 110 and that a Default Gateway (pointing to each Aruba 8320 VLAN SVIs) is set.

    Example for left switches:

    Edge Switch 1 on VLAN 3 192.168.x.101 (Default Gateway 192.168.x.254 <- this is configured on the Core Aruba 8320 as the VLAN 3 SVI)
    Edge Switch 2 on VLAN 3 192.168.x.102 (Default Gateway 192.168.x.254 <- this is configured on the Core Aruba 8320 as the VLAN 3 SVI)
    Edge Switch 3 on VLAN 3 192.168.x.103 (Default Gateway 192.168.x.254 <- this is configured on the Core Aruba 8320 as the VLAN 3 SVI)

    Example for right switches:

    Edge Switch 4 on VLAN 110 192.168.y.101 (Default Gateway 192.168.y.254 <- this is configured on the Core Aruba 8320 as the VLAN 110 SVI)
    Edge Switch 5 on VLAN 110 192.168.y.102 (Default Gateway 192.168.y.254 <- this is configured on the Core Aruba 8320 as the VLAN 110 SVI)
    Edge Switch 6 on VLAN 110 192.168.y.103 (Default Gateway 192.168.y.254 <- this is configured on the Core Aruba 8320 as the VLAN 110 SVI)

    Clearly the Switch 4 (the one you described with NO VLAN set) to which the Aruba 8320 is connected and that bridges the Switch 5 and 6 on your right...it needs to at least transport VLAN 110.

    All VLAN on edge switches SHOULD NOT be set as "Management VLAN", they just need to be set as normal VLAN (the purpose of those VLANs is to manage switches)....that's because if you're using ProCurve/ArubaOS-Switch on the edge switches those use the Management VLAN type as a non-routable VLAN...so it's better to say (and configure) a VLAN with the purpose of using it for Management and not configuring a Management VLAN.

    Hope to have clarified.

    ------------------------------
    Davide Poletto
    ------------------------------