Eye on Blades Blog: Trends in Infrastructure
Get HP BladeSystem news, upcoming event information, technology trends, and product information to stay up to date with what is happening in the world of blades.

Question: What does “receive path validation” do and what could be the reason for the failure?

This one of the methods used to provide fail over for network traffic. 


 


From our BladeSystem support staff


 

"This is just a “redundancy mechanism” that is part of the HP Teaming driver.Not trying to over simply things but here it goes. NIC A and NIC B are teamed together. NIC A is receiving frames okay, NIC B has not received any frames.Teaming driver sends “Test Frame” out NIC A, sets timers and waits for NIC B to receive it. This is repeated a few times.If NIC B still has not received a frame after a few intervals, it is determined the RX (Receive) Path to this NIC is broken, thus NIC is marked as “Receive Path Validation” and is removed as an Active member of the team. This is a good thing because we don’t want a NIC in the team that can’t hear… So…either there is a problem with that NIC receiving frames (fix it) or there is a problem in the Teaming driver detecting “false” RX Path failures.Either way the recommendation is never to disable it as a solution to the problem.

 

Blade Hacks: NIC teaming recommendations with Virtual Connect

A simple question came across the virtual watercooler yesterday and the experts weighed in with some great advice.


Question:


What are the recommended NIC teaming options when using VC? Any conditions where one setting would be preferable over another?


Answer:


There are no “recommended” NIC teaming option for Virtual Connect but ther is extra flexibility in defining your uplink sets, which give you HA you can’t get in the rackmount world.  To summarize:


 


You can make an NFT team from NICs that are serviced by the same or different VC Ethernet modules.  One NIC or the other is active at any given moment, and stays active until a link loss is detected.  Note – Smartuplink should be set on VC networks servicing NFT teams, so that an uplink failure translates to a downlink failure to the NIC, triggering NFT to fail over to the other NIC.  If all NICs in an NFT team are serviced by the same module, that module can be a single point of failure.  If serviced by separate modules, then you have better HA.


You can make a TLB team from NICs that are serviced by the same or different VC Ethernet modules.  If all NICs in an TLB team are serviced by the same VC module, that module can be a single point of failure.  If serviced by separate modules, then you have better HA.


SLB is NOT supported with any VC module. SLB=port channeling and VC doesn’t support it. Only NFT and TLB are supported.

See the Virtual Connect Ethernet cookbook and Usage Scenario videos found here for more details.

 

Search
Showing results for 
Search instead for 
Do you mean 
Follow Us


About the Author(s)
  • More than 25 years in the IT industry developing and managing marketing programs. Focused in emerging technologies like Virtualization, cloud and big data.
  • I work within EMEA HP Servers Central Team as a launch manager for new products and general communications manager for EMEA HP Server specific information. I also tweet @ServerSavvyElla
  • Hello! I am a social media manager for servers, so my posts will be geared towards HP server-related news & info.
  • HP Servers, Converged Infrastructure, Converged Systems and ExpertOne
  • WW responsibility for development of ROI and TCO tools for the entire ISS portfolio. Technical expertise with a financial spin to help IT show the business value of their projects.
  • I am a member of the HP BladeSystem Portfolio Marketing team, so my posts will focus on all things blades and blade infrastructure. Enjoy!
  • Luke Oda is a member of the HP's BCS Marketing team. With a primary focus on marketing programs that support HP's BCS portfolio. His interests include all things mission-critical and the continuing innovation that HP demonstrates across the globe.
  • Global Marketing Manager with 15 years experience in the high-tech industry.
  • Network industry experience for more than 20 years - Data Center, Voice over IP, security, remote access, routing, switching and wireless, with companies such as HP, Cisco, Juniper Networks and Novell.
  • 20 years of marketing experience in semiconductors, networking and servers. Focused on HP BladeSystem networking supporting Virtual Connect, interconnects and network adapters.
  • Greetings! I am on the HP Enterprise Group marketing team. Topics I am interested in include Converged Infrastructure, Converged Systems and Management, and HP BladeSystem.
Labels
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation