We help IT Professionals succeed at work.

Unable to ping VLAN IP on HP E5406zl

Hi,

We just purchased an HP E5406zl Core Switch, and a number of HP 2920 Switches.  I've assigned an IP to each VLAN on the E5406zl, but find I am unable to ping any of them from inside the switch, including the IP that I'm telnetted into the switch with.  When I do a Show IP Route, sometimes all the configured VLAN's show up as connected, sometimes they don't show up at all.  On the occasional times that I can ping a VLAN IP, when I try to ping an IP in the same VLAN on another switch, there's no joy.  Any help with this would be greatly appreciated.  I've attached the running config and show ip route
HP-E5406zl-Running-Config.txt
Comment
Watch Question

Don JohnstonInstructor
Top Expert 2015

Commented:
Could be there are no active ports associated with the VLANs. Hard to say without more information.
Salah Eddine ELMRABETTechnical Lead Manager (Owner)

Commented:
Hi,

Why did you configure the default Vlan IP using DHCP and configure a default gateway?

Best Regards.

Salah

Author

Commented:
Don,

I would think that with no active ports, that the VLAN IP would still respond to ping.  But I'll put a PC on one of the ports, and untag the port for that VLAN to see what happens

Chuck

Author

Commented:
Salah,

Right now the default VLAN 1 is setup for DHCP so I can access it remotely from my desk, as the Test Network is setup in my DC.  Should I have not put in a Default Gateway for the VLANs?  Could you elaborate more as to what you mean?  

Chuck
Zephyr ICTCloud Architect

Commented:
Do you need "ip default-gateway 192.168.1.1"  when ip routing is enabled? Should'nt ip routing take care of that by routing?

Can you remove it?
Don JohnstonInstructor
Top Expert 2015

Commented:
I've never checked on HP equipment, but on Cisco switches, if there are no ports carrying a particular VLAN, the VLAN will show as "inactive" and there will not be an entry in the routing table for that network.
Don JohnstonInstructor
Top Expert 2015

Commented:
"ip routing" deals with moving packets between networks.  Not routing protocols.

Author

Commented:
After connecting a pc to both the core switch, and to switch 1, i can ping the VLAN IP from the PC connected to it, but I can't ping the other switch VLAN IP, or either pc that are connected to them.  I'm staying with working with a single VLAN right now
Don JohnstonInstructor
Top Expert 2015

Commented:
It would help to see the topology (or at least know what ports the PC and switch are connected to).

Can you ping the "other" switch is you connect the PC directly to it?

Can you post the config of this other switch?

Author

Commented:
Don,

I've attached a Simple Network Drawing and The Running Config for the other switch.  On the core switch, the PC is connected to port A1.  On TC1, the PC is connected to port 1/1.  Both ports are untagged on VLAN 600

Chuck
TC1-Running-Config.txt
Simple-Network-Drawing.pdf
Don JohnstonInstructor
Top Expert 2015

Commented:
Which port of the 5406 is connected to which port on TC1?

Author

Commented:
Don,

Core Switch - Port A21 Trunk Group 1
TC1 - Port 1/A1 Trunk Group 1
Don JohnstonInstructor
Top Expert 2015

Commented:
I think that's your problem.

On the 5406 trunk 1 is made up of 5 interfaces: A21-A22,B21-B22,C22

On TC1, trunk 1 is just a single interface: 1/A1.  

So how many links exist between the 5406 and TC1?

Author

Commented:
Don,

1 link exists between the 5406 and TC1.  So should I setup a separate Trunk Group for the connection to each Switch, TC1, TC2, TC3, TC4, and TC6?  As far as pinging the PC from the switch it's connected to, I feel like an idiot...the firewall was the issue.  So, I can now ping the switch from the PC connected to it, and vice-versa, but still can't ping the other switch or its connected PC, which I'm assuming has something to do with the Trunk Groups?
Instructor
Top Expert 2015
Commented:
Remove all the trunk commands. If you don't have multiple links between two switches, you don't have a trunk.  

Try that.

Author

Commented:
Don,

Then do I still have to Tag the Uplink Ports with all the VLANs going across them?
Don JohnstonInstructor
Top Expert 2015

Commented:
If you're going to be sending more than one VLAN over a link, yes.  If it's just a single VLAN, you can go untagged.

Author

Commented:
Don,

Thank You very much, I really appreciate your help on this.  It's always some small setting that messes me up

Chuck
Don JohnstonInstructor
Top Expert 2015

Commented:
It's always something small.

But if it was easy, anybody could do it and us tech types wouldn't be worshiped, right?  ;-)