Wired Intelligent Edge

 View Only
last person joined: 2 days ago 

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

can't get 2nd vlan to work on 2530

This thread has been viewed 23 times

  • 1.  can't get 2nd vlan to work on 2530

    Posted Dec 19, 2022 12:57 AM
    Hi,

    We already had 1 working vlan, but getting the second 1 to works remains an issue.
    Setup is rather easy, 1 router, 1 switch. On the switch i've noticed the default gateway was set to 172.16.44.254 and have already removed this since i noticed in the webinterface this was automatically set as default gateway to all vlans when changing.

    Port 1 of the switch is the uplink to the router, with has both vlans tagged and both have dhcp pool setup in their range. No default vlan1 and no untagged vlans are used.

    Router (cisco):
    interface GigabitEthernet0/1/0
     switchport trunk allowed vlan 44,61
     switchport mode trunk

    Config switch:
    vlan 44
    untagged 2-40
    tagged 1
    ip address 172.16.44.1 255.255.255.0

    vlan 61
    untagged 40-48
    tagged 1
    ip address 172.16.61.1 255.255.255.0




  • 2.  RE: can't get 2nd vlan to work on 2530

    Posted Dec 19, 2022 05:09 AM
    What was the older configuration on CISCO Router with a single VLAN?
    Do you have a L3 interface configured for both VLANs on CISCO Router, if it is L3 CISCO Router you should have sub-interfaces configured on the port.

    Are you able to ping from 2530 switch to CISCO L3 Interfaces?

    ------------------------------
    Harendra
    ACDX|ACEP|CWSP|
    ------------------------------

    Original Message


  • 3.  RE: can't get 2nd vlan to work on 2530

    Posted Dec 20, 2022 12:54 PM
    unfortunately the cisco is not in my management
    can ping 172.16.44.254  from the switch and in the mpls
    can not ping 172.16.44.254 from the switch, but can ping it from else where in the mpls
    Original Message


  • 4.  RE: can't get 2nd vlan to work on 2530

    MVP GURU
    Posted Dec 20, 2022 07:10 AM
    Hi,

    "On the switch i've noticed the default gateway was set to 172.16.44.254 and have already removed this since i noticed in the webinterface this was automatically set as default gateway to all vlans when changing"

    That is pretty normal.

    The Switch's Default Gateway is needed to let the Switch itself (and any of its VLAN with an IP interface assigned) to reach other reachable networks...via that Gateway. Without that gateway the switch can't reach any network and the only way to reach it is to have a host connected to each involved VLAN (say an host belonging to your VLAN 44 and an host belonging to your VLAN 61, both hosts connected on interfaces of your Aruba 2530, each one untagged on its respective VLAN).

    From what you posted the interface 1 is a Tagged member of VLAN 44 and 61 and it is used as the uplink interface (L2) to your Cisco Router with acts (or should act) as the IP Router for those VLANs. The fact you assigned two IP Addresses (respectively 172.16.44.1 and 172.16.61.1 on those VLANs) means you want to reach the Aruba 2530 on both those VLANs by means of the IP Router.
    Original Message


  • 5.  RE: can't get 2nd vlan to work on 2530

    MVP GURU
    Posted Dec 20, 2022 07:40 AM
    Is the interface 1 also "no untagged vlan 1" (no more an Untagged member of Default VLAN 1)?

    Check its VLAN membership status with the help of this CLI command: show vlans ports ethernet 1 detail.



    Original Message


  • 6.  RE: can't get 2nd vlan to work on 2530

    Posted Dec 20, 2022 01:08 PM
    172.16.44.254 showing up as default gateway in vlan 61 with  172.16.61.0/24 seems strange (that default gateway should be 172.16.61.254)  or am i looking at it the wrong way?
    I failed to mention vlan 44 doesn't do dhcp, everything was setup static.

    I'm able to recreate the problem:
    There's another network and router of which i can access the config. So i've did some testing there.
    I created a vlan 20 on that router, and tagged port 2 of the switch with vlan 20 (instead of port 1) just to test the config of the switch.
    Setting the vlan 20 with DHCP/bootp on the switch i received an ip adress defined on that other router.

    However the port 2 uplink to that other router has vlan 20 tagged but also a native default vlan 1.
    When i remove the native default vlan 1 on that router interface, so that only vlan 20 exists on that port (just like on the cisco router only vlan 44 and 61 exist and nothing else) i no longer receive and IP address.

    I think this is somewhat the issue, but i'm at a loss, usually i use a default native vlan 1 + tagged vlans (and some untagged ports if device doesn't support vlan tagging).
    Original Message


  • 7.  RE: can't get 2nd vlan to work on 2530

    Posted Dec 20, 2022 01:11 PM
    if i can only reach it via 172.16.44.1 that is fine, 172.16.61.1 was setup up to be able to ping something to test in that vlan 61
    Original Message


  • 8.  RE: can't get 2nd vlan to work on 2530
    Best Answer

    Posted Dec 26, 2022 10:47 AM
    The issue was on the router
    Original Message