<?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>technology, networking and IP telephony</description>
	<lastBuildDate>Tue, 07 Feb 2012 12:06:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Avaya Ethernet Routing Switches and non-ADAC VLANs &#124; Michael McNamara</title>
		<link>http://blog.michaelfmcnamara.com/2008/08/adac-and-vlan-configurations/#comment-4862</link>
		<dc:creator>Avaya Ethernet Routing Switches and non-ADAC VLANs &#124; Michael McNamara</dc:creator>
		<pubDate>Thu, 22 Sep 2011 04:19:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfmcnamara.com/?p=394#comment-4862</guid>
		<description>[...] the end device in the wrong VLAN and unable to communicate.I blogged about the problem back in 2008 here and here and there were many of you that found out the hard way that neither Java Device Manager [...]</description>
		<content:encoded><![CDATA[<p>[...] the end device in the wrong VLAN and unable to communicate.I blogged about the problem back in 2008 here and here and there were many of you that found out the hard way that neither Java Device Manager [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael McNamara</title>
		<link>http://blog.michaelfmcnamara.com/2008/08/adac-and-vlan-configurations/#comment-4365</link>
		<dc:creator>Michael McNamara</dc:creator>
		<pubDate>Thu, 09 Jun 2011 02:15:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfmcnamara.com/?p=394#comment-4365</guid>
		<description>Thanks for the comment Eric.

If you haven&#039;t already drop by the &lt;a href&quot;http://forums.networkinfrastructure.info/index.php&quot; rel=&quot;nofollow&quot;&gt;discussion forums&lt;/a&gt;, it&#039;s a great place to share your questions or help answer a few.

Cheers!</description>
		<content:encoded><![CDATA[<p>Thanks for the comment Eric.</p>
<p>If you haven&#8217;t already drop by the <a href"http://forums.networkinfrastructure.info/index.php" rel="nofollow">discussion forums</a>, it&#8217;s a great place to share your questions or help answer a few.</p>
<p>Cheers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EricO.</title>
		<link>http://blog.michaelfmcnamara.com/2008/08/adac-and-vlan-configurations/#comment-4364</link>
		<dc:creator>EricO.</dc:creator>
		<pubDate>Wed, 08 Jun 2011 22:02:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfmcnamara.com/?p=394#comment-4364</guid>
		<description>Thanks Mike,

I just confirmed with the Client that the IP Phone wasn&#039;t programmed with the Voice VLAN manually. So that most likely explains why it didn&#039;t work as expected.

I just want to use this opportunity to say that I have been reviewing your Blog for months now and it has been been very informative in every way one can imagine.

I really appreciate the effort you have put into it and thanks again for the great work overall.

I guess, I speak for most of us when I say that your work as regards to your Blog is inspiring.

Thanks again!</description>
		<content:encoded><![CDATA[<p>Thanks Mike,</p>
<p>I just confirmed with the Client that the IP Phone wasn&#8217;t programmed with the Voice VLAN manually. So that most likely explains why it didn&#8217;t work as expected.</p>
<p>I just want to use this opportunity to say that I have been reviewing your Blog for months now and it has been been very informative in every way one can imagine.</p>
<p>I really appreciate the effort you have put into it and thanks again for the great work overall.</p>
<p>I guess, I speak for most of us when I say that your work as regards to your Blog is inspiring.</p>
<p>Thanks again!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael McNamara</title>
		<link>http://blog.michaelfmcnamara.com/2008/08/adac-and-vlan-configurations/#comment-4363</link>
		<dc:creator>Michael McNamara</dc:creator>
		<pubDate>Wed, 08 Jun 2011 03:52:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfmcnamara.com/?p=394#comment-4363</guid>
		<description>Hi Eric,

The unTagPvidOnly setting will only impact devices that you have connected to the PC port of the IP phone. Because those devices generally won&#039;t understand the 802.1q header so the the PVID needs to be set to the data VLAN and the switch will strip the 802.1q headers off the Ethernet frames before it sends them down the IP phone and ultimately out the PC port. 

How do you make it work? You need to set the Voice VLAN ID within the IP phone and you need to make sure that the port (1/3) is a member of that VLAN. With that done the IP phone will boot either with a static IP address of with a DHCP address if you have a DHCP pool available in that VLAN.

Good Luck!</description>
		<content:encoded><![CDATA[<p>Hi Eric,</p>
<p>The unTagPvidOnly setting will only impact devices that you have connected to the PC port of the IP phone. Because those devices generally won&#8217;t understand the 802.1q header so the the PVID needs to be set to the data VLAN and the switch will strip the 802.1q headers off the Ethernet frames before it sends them down the IP phone and ultimately out the PC port. </p>
<p>How do you make it work? You need to set the Voice VLAN ID within the IP phone and you need to make sure that the port (1/3) is a member of that VLAN. With that done the IP phone will boot either with a static IP address of with a DHCP address if you have a DHCP pool available in that VLAN.</p>
<p>Good Luck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EricO.</title>
		<link>http://blog.michaelfmcnamara.com/2008/08/adac-and-vlan-configurations/#comment-4362</link>
		<dc:creator>EricO.</dc:creator>
		<pubDate>Tue, 07 Jun 2011 22:49:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfmcnamara.com/?p=394#comment-4362</guid>
		<description>Hi Michael,

If I hard code a Nortel IP Phone with an IP Address on the Voice VLAN and the IP Phone is connected to Port 1/3 which is associated with the command &quot;vlan ports 1/1-47 tagging unTagPvidOnly&quot;, shouldn&#039;t the Phone work just fine without manual intervention of changing the Port&#039;s PVID to be that of the Voice VLAN ID instead of the Data/Native VLAN?

This unfortunately didn&#039;t work. The PVID for Port 1/3 had to be changed to the Voice VLAN ID. 

Any ideas?</description>
		<content:encoded><![CDATA[<p>Hi Michael,</p>
<p>If I hard code a Nortel IP Phone with an IP Address on the Voice VLAN and the IP Phone is connected to Port 1/3 which is associated with the command &#8220;vlan ports 1/1-47 tagging unTagPvidOnly&#8221;, shouldn&#8217;t the Phone work just fine without manual intervention of changing the Port&#8217;s PVID to be that of the Voice VLAN ID instead of the Data/Native VLAN?</p>
<p>This unfortunately didn&#8217;t work. The PVID for Port 1/3 had to be changed to the Voice VLAN ID. </p>
<p>Any ideas?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hemant Shingane</title>
		<link>http://blog.michaelfmcnamara.com/2008/08/adac-and-vlan-configurations/#comment-2904</link>
		<dc:creator>Hemant Shingane</dc:creator>
		<pubDate>Fri, 26 Nov 2010 10:40:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfmcnamara.com/?p=394#comment-2904</guid>
		<description>Michael,

I am very happy about your blog because i got lot of information on Nortel Switches.

I am facing one problem in ERS 5520 that whenever i remove the cable form port,  i am not getting any cli messages (alter) on cli prompt . But in cisco  switch wherever i disconnected port form cisco switch, i am getting alter messages on cli prompt. So i need a solution on ERS 5520 as well as ers8600.

Thanks
Hemant Shingane</description>
		<content:encoded><![CDATA[<p>Michael,</p>
<p>I am very happy about your blog because i got lot of information on Nortel Switches.</p>
<p>I am facing one problem in ERS 5520 that whenever i remove the cable form port,  i am not getting any cli messages (alter) on cli prompt . But in cisco  switch wherever i disconnected port form cisco switch, i am getting alter messages on cli prompt. So i need a solution on ERS 5520 as well as ers8600.</p>
<p>Thanks<br />
Hemant Shingane</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JamesAttanasio</title>
		<link>http://blog.michaelfmcnamara.com/2008/08/adac-and-vlan-configurations/#comment-1983</link>
		<dc:creator>JamesAttanasio</dc:creator>
		<pubDate>Thu, 29 Apr 2010 17:43:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfmcnamara.com/?p=394#comment-1983</guid>
		<description>Hello Michael and everybody reading this. 

Our infrastrucure : 
Network : Nortel stacks with 5520 switches (firmware 6.0.1.002)
IP Phones : Cisco 7911

Data vlan configured on every port. Adac is configured to dynamicaly assigned voice vlan to a port. Unfortunately  this not working well : We often see phones that go in the data vlan and stay. 

Our switch configuration looks equal as yours but...something must be wrong.

It is interesting to note that :
a. disabling/enabling adac on the port can put the phone in the voicevlan.
b. disabling/enabling poe can also put he ipphone in the voice vlan.
c: this can happened on every port.</description>
		<content:encoded><![CDATA[<p>Hello Michael and everybody reading this. </p>
<p>Our infrastrucure :<br />
Network : Nortel stacks with 5520 switches (firmware 6.0.1.002)<br />
IP Phones : Cisco 7911</p>
<p>Data vlan configured on every port. Adac is configured to dynamicaly assigned voice vlan to a port. Unfortunately  this not working well : We often see phones that go in the data vlan and stay. </p>
<p>Our switch configuration looks equal as yours but&#8230;something must be wrong.</p>
<p>It is interesting to note that :<br />
a. disabling/enabling adac on the port can put the phone in the voicevlan.<br />
b. disabling/enabling poe can also put he ipphone in the voice vlan.<br />
c: this can happened on every port.</p>
]]></content:encoded>
	</item>
	<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>
</channel>
</rss>

<!-- Served from: blog.michaelfmcnamara.com @ 2012-02-08 17:13:05 by W3 Total Cache -->
