Wired Intelligent Edge

last person joined: yesterday 

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

HP 5400ZL Issues added vlan

This thread has been viewed 0 times

  • 1.  HP 5400ZL Issues added vlan

    Posted May 15, 2018 06:14 AM

    Hi,

     

    We have an 5400zl switch. We added a new VLAN with an IP address (10.217.150.254/24). Unfortuantely we can't ping the default static route (0.0.0.0 0.0.0.0 10.217.255.1). Between the VLAN's we can normally ping. All other VLAN's can reach the default static route. The new VLAN is in the ip route. Any idea's?

     

    Thanks!



  • 2.  RE: HP 5400ZL Issues added vlan

    MVP EXPERT
    Posted May 15, 2018 08:47 AM

    I guess its the same as at comwware that minimum one interface in the new vlan must be up, to bring the vlan up



  • 3.  RE: HP 5400ZL Issues added vlan

    Posted May 16, 2018 02:24 AM

    Hi,

     

    Please check if there is routing for 10.217.150.254/24 on the GW(10.217.255.1)



  • 4.  RE: HP 5400ZL Issues added vlan

    Posted May 28, 2018 01:22 AM

    Unless a VLAN has at least one interface that is UP, the assigned IP address will not respond. Tag the VLAN to the uplink port/trunk if you always want it up irrespective of active ports in that VLAN on the switch.

     

    Think about loopback addresses for management too.



  • 5.  RE: HP 5400ZL Issues added vlan

    EMPLOYEE
    Posted May 30, 2018 09:50 PM

    Hi Schuurmans,

     

    The vlan is Up and hence you are able to see it in the ip route table.

    Tag the new vlan to the port that connects to the DG - 10.217.255.1.

    If that is already done, then make sure that there is a reverse route configured for the new vlan on the DG 10.217.255.1.

     

    Aditional steps:

    In case it does not work even after adding the reverse route in the DG 10.217.255.1. Take a packet capture from the uplink port to check if it even hits the uplink port or not when you ping it. With the packet capture we ll get to know where is the traffic actually getting dropped.