Datacenter Troubleshooting Guide

Blog

Jan 27, 2015 12:34 PM
Oct 29th, 2010

/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin-top:0cm; mso-para-margin-right:0cm; mso-para-margin-bottom:10.0pt; mso-para-margin-left:0cm; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;}

“Datacenter troubleshooting guide” – a blog by Gilles Dufour.

Day 1 – Start with the basic

Very often I see questions regarding troubleshooting steps to follow when working with a loadbalancer like ACE (Application Control Engine).

Some people believe that because this is a new platform, it works differently than all previous equipments they ever worked with.

Suddenly, because this is a loadbalancer, we see CCIE not knowing what to do when the device does not respond to ping requests.

It is true that a new platform will have new features, new functions, new GUI and maybe a new CLI.  But at the end, a loadbalancer remains a TCP/IP device. 

If your loadbalancer does not loadbalance, I would suggest to perform standard routing/switching troubleshooting first.  This includes checking the path from the source to the destination, making sure routing tables and arp tables are correct.  You will also check the reverse path making sure the server will respond to the client THROUGH the ACE (asymetric routing is often not accepted by loadbalancers).

And I strongly recommend to have a sniffer tool ready to capture traces to verify that traffic gets to your loadbalancer and leaves it in the right direction.

Next time, I will focus on loadbalancing at layer 3 and 4.

Gilles Dufour.

Overall Rating: 0 (0 ratings)
expertadvisor20151 Wed, 01/21/2015 - 17:48

Cisco has a new solution called ITD:

http://blogs.cisco.com/datacenter/itd-load-balancing-traffic-steering-clustering-using-nexus-5k6k7k

 

ITD (Intelligent Traffic Director) is a hardware based multi-Tbps Layer 4 load-balancing, traffic steering and clustering solution on Nexus 5K/6K/7K series of switches. It supports IP-stickiness, resiliency, NAT (EFT), VIP, health monitoring, sophisticated failure handling policies, N+M redundancy, IPv4, IPv6, VRF, weighted load-balancing, bi-directional flow-coherency, and IPSLA probes including DNS. There is no service module or external appliance needed.

 

Actions

Login or Register to take actions

This Blog

Posted October 29, 2010 at 5:17 AM
Updated January 27, 2015 at 12:34 PM
Stats:
Comments:1 Overall Rating:0
Views:2991   
Shares:0