<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: ADAC and VLAN Configurations</title>
	<atom:link href="http://blog.michaelfmcnamara.com/2008/08/adac-and-vlan-configurations/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.michaelfmcnamara.com/2008/08/adac-and-vlan-configurations/</link>
	<description>technical blog around technology, networking solutions and IP telephony</description>
	<lastBuildDate>Thu, 11 Mar 2010 15:33:38 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Deepak</title>
		<link>http://blog.michaelfmcnamara.com/2008/08/adac-and-vlan-configurations/#comment-1361</link>
		<dc:creator>Deepak</dc:creator>
		<pubDate>Fri, 16 Oct 2009 16:59:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfmcnamara.com/?p=394#comment-1361</guid>
		<description>Thanks Michael . I have tried with B option already with bt set to y but it stops at DHCP option . I will play around with option B.</description>
		<content:encoded><![CDATA[<p>Thanks Michael . I have tried with B option already with bt set to y but it stops at DHCP option . I will play around with option B.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael McNamara</title>
		<link>http://blog.michaelfmcnamara.com/2008/08/adac-and-vlan-configurations/#comment-1359</link>
		<dc:creator>Michael McNamara</dc:creator>
		<pubDate>Thu, 15 Oct 2009 23:40:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfmcnamara.com/?p=394#comment-1359</guid>
		<description>Hi Deepak,

You can&#039;t set that option with the legacy Nortel-i2004-A option. You need to use the Nortel-i2004-B option which requires UNIStim v2.3 or later firmware on the IP phones. You can find additional information on the Nortel-i2004-B option in this &lt;a href=&quot;http://blog.michaelfmcnamara.com/2008/05/nortel-ip-phones-unistim-release-v23/&quot; rel=&quot;nofollow&quot;&gt;post&lt;/a&gt;. If you only have a few phones you can probably just enable bluetooth from the phone itself.

Cheers!</description>
		<content:encoded><![CDATA[<p>Hi Deepak,</p>
<p>You can&#8217;t set that option with the legacy Nortel-i2004-A option. You need to use the Nortel-i2004-B option which requires UNIStim v2.3 or later firmware on the IP phones. You can find additional information on the Nortel-i2004-B option in this <a href="http://blog.michaelfmcnamara.com/2008/05/nortel-ip-phones-unistim-release-v23/" rel="nofollow">post</a>. If you only have a few phones you can probably just enable bluetooth from the phone itself.</p>
<p>Cheers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deepak</title>
		<link>http://blog.michaelfmcnamara.com/2008/08/adac-and-vlan-configurations/#comment-1358</link>
		<dc:creator>Deepak</dc:creator>
		<pubDate>Thu, 15 Oct 2009 23:16:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfmcnamara.com/?p=394#comment-1358</guid>
		<description>Hi Michael,

How do I enable bluetooth in option 128 ? Tried with bt=1

option 128 ascii “Nortel-i2004-A,10.2.224.15:4100,1,2;10.2.224.15:4100,1,2;bt,1.”</description>
		<content:encoded><![CDATA[<p>Hi Michael,</p>
<p>How do I enable bluetooth in option 128 ? Tried with bt=1</p>
<p>option 128 ascii “Nortel-i2004-A,10.2.224.15:4100,1,2;10.2.224.15:4100,1,2;bt,1.”</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael McNamara</title>
		<link>http://blog.michaelfmcnamara.com/2008/08/adac-and-vlan-configurations/#comment-1300</link>
		<dc:creator>Michael McNamara</dc:creator>
		<pubDate>Fri, 25 Sep 2009 16:58:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfmcnamara.com/?p=394#comment-1300</guid>
		<description>I&#039;m happy I was able to help. 

Cheers!</description>
		<content:encoded><![CDATA[<p>I&#8217;m happy I was able to help. </p>
<p>Cheers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deepak</title>
		<link>http://blog.michaelfmcnamara.com/2008/08/adac-and-vlan-configurations/#comment-1299</link>
		<dc:creator>Deepak</dc:creator>
		<pubDate>Fri, 25 Sep 2009 16:14:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfmcnamara.com/?p=394#comment-1299</guid>
		<description>Hi Michael,

You are the Champ .. It works now !! 

I was using option 191 is voice VLAN instead of data VLAN .

Thank you so much . You made my day .. Have a wonderful weekend !</description>
		<content:encoded><![CDATA[<p>Hi Michael,</p>
<p>You are the Champ .. It works now !! </p>
<p>I was using option 191 is voice VLAN instead of data VLAN .</p>
<p>Thank you so much . You made my day .. Have a wonderful weekend !</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael McNamara</title>
		<link>http://blog.michaelfmcnamara.com/2008/08/adac-and-vlan-configurations/#comment-1298</link>
		<dc:creator>Michael McNamara</dc:creator>
		<pubDate>Fri, 25 Sep 2009 12:22:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfmcnamara.com/?p=394#comment-1298</guid>
		<description>Hi Deepak,

You need DHCP addresses in the data (default) VLAN with option 191 defined. You need DHCP addresses with option 128 defined in the voice VLAN.

The IP phone will issue a DHCP request in the default VLAN. If it receives a response with option 191 it will issue a DHCP release and issue a DHCP request in the voice VLAN (VLAN tag equal to the value returned in option 191). The switch port needs to be configured as untag default VLAN (allowing trunking but only tagging the non PVID ports).

Good Luck!</description>
		<content:encoded><![CDATA[<p>Hi Deepak,</p>
<p>You need DHCP addresses in the data (default) VLAN with option 191 defined. You need DHCP addresses with option 128 defined in the voice VLAN.</p>
<p>The IP phone will issue a DHCP request in the default VLAN. If it receives a response with option 191 it will issue a DHCP release and issue a DHCP request in the voice VLAN (VLAN tag equal to the value returned in option 191). The switch port needs to be configured as untag default VLAN (allowing trunking but only tagging the non PVID ports).</p>
<p>Good Luck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deepak</title>
		<link>http://blog.michaelfmcnamara.com/2008/08/adac-and-vlan-configurations/#comment-1297</link>
		<dc:creator>Deepak</dc:creator>
		<pubDate>Fri, 25 Sep 2009 07:13:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfmcnamara.com/?p=394#comment-1297</guid>
		<description>Hi Michael,

I am trying to connect Nortel IP Phone 1120E for full DHCP with cisco 6509 switch ( which is a DHCP server ) . But I am not able to get this Full DHCP working without configuring the Voice VLAN ID in the IP Phone settings. 

option 128 ascii &quot;Nortel-i2004-A,10.2.224.15:4100,1,2;10.2.224.15:4100,1,2.&quot;
option 191 VLAN-A:501.

where 501 is Voice DHCP VLAN.

Any clues ?</description>
		<content:encoded><![CDATA[<p>Hi Michael,</p>
<p>I am trying to connect Nortel IP Phone 1120E for full DHCP with cisco 6509 switch ( which is a DHCP server ) . But I am not able to get this Full DHCP working without configuring the Voice VLAN ID in the IP Phone settings. </p>
<p>option 128 ascii &#8220;Nortel-i2004-A,10.2.224.15:4100,1,2;10.2.224.15:4100,1,2.&#8221;<br />
option 191 VLAN-A:501.</p>
<p>where 501 is Voice DHCP VLAN.</p>
<p>Any clues ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael McNamara</title>
		<link>http://blog.michaelfmcnamara.com/2008/08/adac-and-vlan-configurations/#comment-912</link>
		<dc:creator>Michael McNamara</dc:creator>
		<pubDate>Wed, 27 May 2009 01:06:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfmcnamara.com/?p=394#comment-912</guid>
		<description>Thanks for the comment Peter!</description>
		<content:encoded><![CDATA[<p>Thanks for the comment Peter!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Donnelly</title>
		<link>http://blog.michaelfmcnamara.com/2008/08/adac-and-vlan-configurations/#comment-908</link>
		<dc:creator>Peter Donnelly</dc:creator>
		<pubDate>Thu, 21 May 2009 19:06:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfmcnamara.com/?p=394#comment-908</guid>
		<description>I had a similar error where we changed the PVID of ADAC enabled ports on a 4550T-PWR stack whilst phones were plugged in.  The switches went into a reboot cycle and only a hard power cycle would bring them back up properly.  The resolve as you so rightly pointed out was

1.  Disable ADAC on all telephony ports.
2.  Change PVID on all required ports.
3.  Re-Enable ADAC on ports.

Downtime was unavoidable but only lasted 3-5 minutes in total. 

Best advice is to plan,plan,plan and get the settled config before putting into production.</description>
		<content:encoded><![CDATA[<p>I had a similar error where we changed the PVID of ADAC enabled ports on a 4550T-PWR stack whilst phones were plugged in.  The switches went into a reboot cycle and only a hard power cycle would bring them back up properly.  The resolve as you so rightly pointed out was</p>
<p>1.  Disable ADAC on all telephony ports.<br />
2.  Change PVID on all required ports.<br />
3.  Re-Enable ADAC on ports.</p>
<p>Downtime was unavoidable but only lasted 3-5 minutes in total. </p>
<p>Best advice is to plan,plan,plan and get the settled config before putting into production.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RD</title>
		<link>http://blog.michaelfmcnamara.com/2008/08/adac-and-vlan-configurations/#comment-892</link>
		<dc:creator>RD</dc:creator>
		<pubDate>Wed, 13 May 2009 11:52:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfmcnamara.com/?p=394#comment-892</guid>
		<description>Thanks Michael. Worked like a charm (with a little editing). For anyone else reading, it was only successful when the referrenced uoplink port in the MLT was the last numerically. Not sure if tht is teh case for everyone else.</description>
		<content:encoded><![CDATA[<p>Thanks Michael. Worked like a charm (with a little editing). For anyone else reading, it was only successful when the referrenced uoplink port in the MLT was the last numerically. Not sure if tht is teh case for everyone else.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
