I'm trying to diagnose what is potentially a DHCP relay issue on an SG300. I have a client with one deployed with 3 VLAN's. Windows 2008 R2 DHCP server is providing addresses for all 3 VLAN's. Everything is working as expected except for Linux machines. On 2 of the VLAN's, any Linux machines (includes embedded linux e.g. in printers) are heavily delayed in receiving an IP address from the DHCP server. They do arrive eventually but can be over an hour later. The other VLAN contains the DHCP server and it has no problem handing out IP's to Linux clients (isn't operating DHCP relay for that VLAN).
I've been running wireshark at a client and on the DHCP server, but its hard to see what is actually happening. Since the DHCP relay requests come from the switch rather than the client, its hard to identify discovers as they are made.
I'm wondering if there is an easy way of doing packet captures at the SG300 to try and identify the DHCP traffic and see whether the issue is with the switch or at the DHCP server.
I'm planning on upgrading both firmware and boot code on it (hopefully this weekend). I don't suppose you have heard of anything like this happening in DHCP relay on the SG300? It's odd that everything is fine for Windows clients, just not Linux clients.
I don't think I can open a ticket - don't have a support contract with Cisco.
I'm wondering if my problem is related to this thread: https://supportforums.cisco.com/discussion/12306761/firmware-14088-sg300-52-appears-break-dhcp-relay
The TCAM on the SG300 is set at default of 128, but I have over 200 hosts on the network. Would this explain why I see dropped packets to places intermittently that have no problems with their actual physical connectivity? This also probably explains why I'm not seeing it in my test environment either.
Any rules on what to set the TCAM to? Just aim for a figure higher than the number of hosts, ACL's, routes etc?
Well, changing TCAM has sorted it. Raised the setting on the production SG300 and our network traffic has flattened out again and we have normal timings on DHCP relay allocation for non-windows machines as well.
Introduction:Topology Diagram:Configuration Overview:Related
Information: Introduction: This document describes how to connect SG300
with Catalyst switch via STP. Spanning Tree Protocol (STP) is a Layer 2
protocol that runs on mainly on switches. The spec...
On a technical level, Cisco 300 Series is far superior to the HP 1910
and 2530 products. This document provides evidence that Cisco has >100
features not supported by the HP platforms. Check this out and decide
for yourselves. Notes (2/5/2014):- Informati...
The Sx500 Series Stackable Switches offers different port features. You
can add security to a port, make the port more energy efficient, map a
VLAN to a port, make a port available or not to a specific network
portion, and so forth. The next set of articl...