VMware vSphere

 View Only
  • 1.  IBM HS23 Management Network

    Posted Feb 06, 2014 03:44 PM

    Hello,

    We recently received our first HS23 blades to use in our IBM H Chassis, we have configured the management network and verified the blade switch is showing connectivity to the slot however the blade does not communicate past the default gateway nor can I ping another host within the Chassis. The blade has an Emulex NIC using the be2net driver as well as the IBM specific build of ESXi for 5.5. All the troubleshooting guides on VMware's website hasn't produced any good head way on what the problem might be, all other blades in our environment are working fine and haven't had an issue like this until we got these new HS23's. Any insight is much appreciated.

    Thank You.

    Mike M.



  • 2.  RE: IBM HS23 Management Network

    Posted Jan 19, 2015 05:33 PM

    Hi Mousseuau,

    i know this post is quite old, but the same thing is happening to me, did you found a solution to this problem?

    the primary NICs on the HS23 connect and get IP, the secondary NICs negotiate the port speed correclty and get link, but cannot communicate with static IP, cannot talk to the other blades on the mgmt network, and cannot get ip in dhcp.

    i dont know if its related to the other reported problem with the brocade oneconnect drivers, but i tryied to shift the be2net drivers, with no avail.

    Thanks!



  • 3.  RE: IBM HS23 Management Network

    Posted Feb 04, 2015 03:16 AM

    Anyone happened to have a similar issue? VMware support doesnt respond, VMWare Sales doesnt care to send us a quote if renewal is needed, and we already changed the complete blades with new ones.



  • 4.  RE: IBM HS23 Management Network

    Broadcom Employee
    Posted Feb 04, 2015 01:37 PM

    Hi,

    Could you provide more infos ?

    How are configured vswitches ? and internal switch of blade ?

    Thanks



  • 5.  RE: IBM HS23 Management Network

    Posted Feb 05, 2015 07:46 PM

    Hi Mauro,

    thanks for answering me, i didnt get back quickly because of frustration and trying to fix this,

    Both switch modules on the blade chasis are with default configuration, nothing was modified (all ports on vlan 1 and 4095)

    the switches are L2/L3 BNT copper 1Gbps switches, and i also tried putting the ports on trunk mode, with no luck (disabling dot1q, disabling most options, etc).

    we have in the chassis 2 HS22 and 2 HS23.

    the HS22, which have broadcom net adapters have no problems whatsoever with both switches,

    the HS23, the first 1Gbps Emulex network adapter works fine, the secondary adapter gets link, negotiates speed, but is unable to connect to any network whatsoever.

    we discarded a hardware problem, since we replaced the HS23's entirely with new spares with IBM support,

    Emulex doesnt want to jump into the problem with the argument that the part number is from IBM,

    the following graphic is a simple explanation of whats happening (green wires are working, red wires are not).

    both blades we tried with firmware stock versions (4.x) running the old be2net driver, and with newer firmware version 10.2.377.29 and with driver 10.2.261.4 (elxnet on vmware page).

    we cant find a solution to this, and we're going in circles.

    Anything you ask ill be happy to answer,

    Cheers,

    Cristian