<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Nov 1, 2011, at 8:24 AM, Eduardo Barreto wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">I'm setting a Centralized DHCP, defining many vlan's to work within multiple virtual interfaces, does anyone knows, what kind of problem may I deal with it.<span class="Apple-converted-space"> </span><br><br>Cheers,<br><br>I appreciate your help, I'm taking you in advance.</span></blockquote></div><br><div>I have a central dhcp server that hosts services for about 7 different vlans. I assigned Tagged vlans to the primary interface of my server. DHCP requests are very quick when broadcasting on the same vlan. I do have a few locations that must use DHCP/UDP helpers</div><div><br></div><div>the biggest job is managing your clients and who gets IP's and who doesn't. Also you should consider a secondary as a failover backup.</div><div>-j</div></body></html>