Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Trunking issue after power off/on HP1910 switch

Trunking issue after power off/on HP1910 switch

Trunking issue after power off/on HP1910 switch


I have a strange issue. HP 1910 switch connected to an ESXi server with 2 Nics. Ports are  Link aggregated (trunked) with no lacp. When I created the trunk, if I create them for the 2 ports that already have active NICs in the them communication will never work over the trunk. If I setup 2 ports that have nothing in them, plug one NIC in, wait a minute and then plug the other one in it works. I can live with that, but what I am finding is, if I power off the switch and back on again, the trunk will stop sending traffic over it. If I unplug one NIC, it comes back. As soon as I put both in, it fails again. By fails U mean I cannot ping (or anything else) the ESXi server anymore. The idea is to use VLANs once we get the Link Aggregation/trunking setup correctly.

ESXi is setup up correctly with routing set to IP hash. Any ideas what I am doing wring on the HP? I am new to HP switches but this works with Cisco switches no problem.



RE: Trunking issue after power off/on HP1910 switch

double check that not only your vSwitch has Load Balancing set to IP Hash, but also your Port Group(s); ettings don't always inherit properly. Also, post your trunk configuration.

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)

RE: Trunking issue after power off/on HP1910 switch


Thanks that solved it. All port groups in ESX were set to inherit, but they weren't. Forced them all to IP hash and then back to inheritted and it works.

Thanks Matt

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close