<?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: ERS 8600 Software 4.1.6.0 buggy</title>
	<atom:link href="http://blog.michaelfmcnamara.com/2008/07/ers-8600-software-4160-buggy/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.michaelfmcnamara.com/2008/07/ers-8600-software-4160-buggy/</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: Michael McNamara</title>
		<link>http://blog.michaelfmcnamara.com/2008/07/ers-8600-software-4160-buggy/#comment-4874</link>
		<dc:creator>Michael McNamara</dc:creator>
		<pubDate>Fri, 23 Sep 2011 02:50:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfmcnamara.com/?p=222#comment-4874</guid>
		<description>Hi Legacy,

How many VLANs are involved in the problem? Are you running VRRP or RSMLT in those VLANs? Where there any changes to any of the VLANs recently?

When I had that problem in 4.1.6.x and 4.1.8.x the only long term solution was to reboot each of the ERS 8600 switches (one at a time of course). You can utilize the MAC/FDB aging fix to help the mitigate the issue, not sure if it will resolve the issue completely but it&#039;s a good practice and helps save the CPU from wasting needless cycles.

&lt;i&gt;config vlan 1 fdb-entry aging-time 21601&lt;/i&gt;

I will say that I have not personally seen this issue on 5.1.x software.

Good Luck!</description>
		<content:encoded><![CDATA[<p>Hi Legacy,</p>
<p>How many VLANs are involved in the problem? Are you running VRRP or RSMLT in those VLANs? Where there any changes to any of the VLANs recently?</p>
<p>When I had that problem in 4.1.6.x and 4.1.8.x the only long term solution was to reboot each of the ERS 8600 switches (one at a time of course). You can utilize the MAC/FDB aging fix to help the mitigate the issue, not sure if it will resolve the issue completely but it&#8217;s a good practice and helps save the CPU from wasting needless cycles.</p>
<p><i>config vlan 1 fdb-entry aging-time 21601</i></p>
<p>I will say that I have not personally seen this issue on 5.1.x software.</p>
<p>Good Luck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Legacy</title>
		<link>http://blog.michaelfmcnamara.com/2008/07/ers-8600-software-4160-buggy/#comment-4869</link>
		<dc:creator>Legacy</dc:creator>
		<pubDate>Thu, 22 Sep 2011 20:16:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfmcnamara.com/?p=222#comment-4869</guid>
		<description>Hi Gene,
Am not really sure if it&#039;s exactly  the same issue posted on this blog However  we been noticing a similar situation where the is not ARP entries on both 8600&#039;s (Cluster) for some of the layer 2  Edge devices. it&#039;s usually One or 2 edge switch at a time out off 600+ 

 On the other hand there is NO service interruptions to the Business. EU&#039;s are able to make phone, access business applications etc..  (CLI and JDM works fine when you  are physically connect to the edge switch).    

The temporary  workaround is to ping the edge switch from  one of the 8600&#039;s and suddenly  all is back to normal; sometimes it resolves itself without any action taken by us

Code Levels on 8600&#039;s (Cluster): 5.1.3.1
Code Level Edge Switches: 5.1.1.017

Can you please advise if this is the same issue? 

Thank You!</description>
		<content:encoded><![CDATA[<p>Hi Gene,<br />
Am not really sure if it&#8217;s exactly  the same issue posted on this blog However  we been noticing a similar situation where the is not ARP entries on both 8600&#8242;s (Cluster) for some of the layer 2  Edge devices. it&#8217;s usually One or 2 edge switch at a time out off 600+ </p>
<p> On the other hand there is NO service interruptions to the Business. EU&#8217;s are able to make phone, access business applications etc..  (CLI and JDM works fine when you  are physically connect to the edge switch).    </p>
<p>The temporary  workaround is to ping the edge switch from  one of the 8600&#8242;s and suddenly  all is back to normal; sometimes it resolves itself without any action taken by us</p>
<p>Code Levels on 8600&#8242;s (Cluster): 5.1.3.1<br />
Code Level Edge Switches: 5.1.1.017</p>
<p>Can you please advise if this is the same issue? </p>
<p>Thank You!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gene</title>
		<link>http://blog.michaelfmcnamara.com/2008/07/ers-8600-software-4160-buggy/#comment-669</link>
		<dc:creator>Gene</dc:creator>
		<pubDate>Tue, 10 Mar 2009 15:36:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfmcnamara.com/?p=222#comment-669</guid>
		<description>Mary

From Nortel:

Thankyou for choosing Nortel.

     I will explain it again for better clarification.
    [*Mar  1 07:18:04 [172.20.133.3.12.24] CPU5 [03/01/07 20:28:12] SW WARNING dpmGetActivityBit:ltrSyncSend FAILED for MAC_ADDR/MAC_VLAN. MAC addr: 0x00130abbb800,pimport: 15, destslot: 1, status=9*]

This is occurring because dpmGetActivityBit is sending a LTR message to COP, if COP will receive the message then it will return the activity of particular MAC.

But the message sending from CP to COP failed. Reason for failing is because ltrSyncSend is returning LTR_INTERNAL_ERR(9),   /* internal platform-dependent error */

ltrSyncSend tries to send the packet through transport layer mechanism (SyncTransportLayer) which in turn return the above error when it is not able to take the semaphore/resources.

This problem is likely not impacting the work of the device.

The reason for above message is: The main CPU is not able to send the message to COP (I/O blade CPU). The message sending mechanism failed to transfer the message due to lack of resources. Probably message sending mechanism is busy sending other higher priority messages in queue or there is already a big queue of message to be transferred.

(It will potentially happen if large tables exist on the device and there are timing issues aging these tables between CPU and R-Module.)

I have few questions for you:

1. How often you see this message
2. Where do you see this? I meant to ask weather it reflects on both passport at the same time?
3. Does it create any connectivity issues?
4. Is it throwing out this message continuesly?
5. What is the states of the ports at the time of message disply?
6. Even though the port states shows green, using a sniffer and check weather traffic flow is happening fine.

If the message is displayed once in a long while and if we are not having any connectivity issues, we don&#039;t have to worry about that. The cpu will recover itself.Please send me the updates as soon as possible.

Thank you,</description>
		<content:encoded><![CDATA[<p>Mary</p>
<p>From Nortel:</p>
<p>Thankyou for choosing Nortel.</p>
<p>     I will explain it again for better clarification.<br />
    [*Mar  1 07:18:04 [172.20.133.3.12.24] CPU5 [03/01/07 20:28:12] SW WARNING dpmGetActivityBit:ltrSyncSend FAILED for MAC_ADDR/MAC_VLAN. MAC addr: 0x00130abbb800,pimport: 15, destslot: 1, status=9*]</p>
<p>This is occurring because dpmGetActivityBit is sending a LTR message to COP, if COP will receive the message then it will return the activity of particular MAC.</p>
<p>But the message sending from CP to COP failed. Reason for failing is because ltrSyncSend is returning LTR_INTERNAL_ERR(9),   /* internal platform-dependent error */</p>
<p>ltrSyncSend tries to send the packet through transport layer mechanism (SyncTransportLayer) which in turn return the above error when it is not able to take the semaphore/resources.</p>
<p>This problem is likely not impacting the work of the device.</p>
<p>The reason for above message is: The main CPU is not able to send the message to COP (I/O blade CPU). The message sending mechanism failed to transfer the message due to lack of resources. Probably message sending mechanism is busy sending other higher priority messages in queue or there is already a big queue of message to be transferred.</p>
<p>(It will potentially happen if large tables exist on the device and there are timing issues aging these tables between CPU and R-Module.)</p>
<p>I have few questions for you:</p>
<p>1. How often you see this message<br />
2. Where do you see this? I meant to ask weather it reflects on both passport at the same time?<br />
3. Does it create any connectivity issues?<br />
4. Is it throwing out this message continuesly?<br />
5. What is the states of the ports at the time of message disply?<br />
6. Even though the port states shows green, using a sniffer and check weather traffic flow is happening fine.</p>
<p>If the message is displayed once in a long while and if we are not having any connectivity issues, we don&#8217;t have to worry about that. The cpu will recover itself.Please send me the updates as soon as possible.</p>
<p>Thank you,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mary</title>
		<link>http://blog.michaelfmcnamara.com/2008/07/ers-8600-software-4160-buggy/#comment-668</link>
		<dc:creator>Mary</dc:creator>
		<pubDate>Tue, 10 Mar 2009 12:56:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfmcnamara.com/?p=222#comment-668</guid>
		<description>Hi Gene, 

I have the same message on a 8600 running 4.1.4.0 version : 

CPU6 [03/04/09 21:53:37] COP-SW ERROR Slot 1: dpmRxSyncReceive: CommandType 155
UnKnown
CPU6 [03/04/09 21:53:37] SW WARNING dpmGetActivityBit:ltrSyncSend FAILED for MAC
_ADDR/MAC_VLAN. MAC addr: 0x00188b1f784a,pimport: 1, destslot: 1, status=9

You said that you have opened a Nortel case, what was their explanation for the error message ? 

Thanks.</description>
		<content:encoded><![CDATA[<p>Hi Gene, </p>
<p>I have the same message on a 8600 running 4.1.4.0 version : </p>
<p>CPU6 [03/04/09 21:53:37] COP-SW ERROR Slot 1: dpmRxSyncReceive: CommandType 155<br />
UnKnown<br />
CPU6 [03/04/09 21:53:37] SW WARNING dpmGetActivityBit:ltrSyncSend FAILED for MAC<br />
_ADDR/MAC_VLAN. MAC addr: 0x00188b1f784a,pimport: 1, destslot: 1, status=9</p>
<p>You said that you have opened a Nortel case, what was their explanation for the error message ? </p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael McNamara</title>
		<link>http://blog.michaelfmcnamara.com/2008/07/ers-8600-software-4160-buggy/#comment-578</link>
		<dc:creator>Michael McNamara</dc:creator>
		<pubDate>Tue, 10 Feb 2009 12:41:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfmcnamara.com/?p=222#comment-578</guid>
		<description>For those that may have an email subscription to this thread. Nortel has finally released v4.1.8.2 software for the Ethernet Routing Switch 8600.

http://blog.michaelfmcnamara.com/2009/02/ethernet-routing-switch-8600-software-release-v4182/</description>
		<content:encoded><![CDATA[<p>For those that may have an email subscription to this thread. Nortel has finally released v4.1.8.2 software for the Ethernet Routing Switch 8600.</p>
<p><a href="http://blog.michaelfmcnamara.com/2009/02/ethernet-routing-switch-8600-software-release-v4182/" rel="nofollow">http://blog.michaelfmcnamara.com/2009/02/ethernet-routing-switch-8600-software-release-v4182/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael McNamara</title>
		<link>http://blog.michaelfmcnamara.com/2008/07/ers-8600-software-4160-buggy/#comment-547</link>
		<dc:creator>Michael McNamara</dc:creator>
		<pubDate>Thu, 29 Jan 2009 04:56:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfmcnamara.com/?p=222#comment-547</guid>
		<description>Welcome back Rene!

I use Equal Cost Multi-Pathing (ECMP) in my WAN routing to provide redundancy and high availability between my sites. I bridge the majority of my LAN traffic between the edge and the core across a SMLT connection. 

Here&#039;s a test for you... re-enable ECMP but disable one of the SMLT links, re-test your problem. Then enable the original SMLT link and disable the other SMLT link, re-test your problem. Does the problem persist if you are only running a single link? 

Good Luck!</description>
		<content:encoded><![CDATA[<p>Welcome back Rene!</p>
<p>I use Equal Cost Multi-Pathing (ECMP) in my WAN routing to provide redundancy and high availability between my sites. I bridge the majority of my LAN traffic between the edge and the core across a SMLT connection. </p>
<p>Here&#8217;s a test for you&#8230; re-enable ECMP but disable one of the SMLT links, re-test your problem. Then enable the original SMLT link and disable the other SMLT link, re-test your problem. Does the problem persist if you are only running a single link? </p>
<p>Good Luck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rene</title>
		<link>http://blog.michaelfmcnamara.com/2008/07/ers-8600-software-4160-buggy/#comment-543</link>
		<dc:creator>Rene</dc:creator>
		<pubDate>Wed, 28 Jan 2009 08:36:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfmcnamara.com/?p=222#comment-543</guid>
		<description>Do you use ecmp routing, we have a issue with ecmp and smlt.
after disabled ecmp the issue gone. do you have more info about your network?</description>
		<content:encoded><![CDATA[<p>Do you use ecmp routing, we have a issue with ecmp and smlt.<br />
after disabled ecmp the issue gone. do you have more info about your network?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gene</title>
		<link>http://blog.michaelfmcnamara.com/2008/07/ers-8600-software-4160-buggy/#comment-541</link>
		<dc:creator>Gene</dc:creator>
		<pubDate>Wed, 28 Jan 2009 02:57:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfmcnamara.com/?p=222#comment-541</guid>
		<description>We are now at 4.1.7.2 as of two weeks ago. The only error of note in the logs are:

CPU5 [01/05/09 04:18:09] SW WARNING dpmGetActivityBit:ltrSyncSend FAILED for MAC_ADDR/MAC_VLAN. MAC addr: 0x000e7f36ecc8,pimport: 4, destslot: 3, status=9

I got two instances of this on two user devices. Nortel ticket opened and they stated if it does not happen a great deal, don&#039;t worry. It is some sort of  &quot;I&#039;m too busy right now to handle your specific need, but I&#039;ll log this message for you&quot; type of error. I don&#039;t know. I have not noticed any problems since going to 4.1.7.2. 
 
These entries appear in both ERS cores IST connected. Things have been stable, thus far. Glad to dump the 4.0.3.0/4.0.6.0 crap.

Gene</description>
		<content:encoded><![CDATA[<p>We are now at 4.1.7.2 as of two weeks ago. The only error of note in the logs are:</p>
<p>CPU5 [01/05/09 04:18:09] SW WARNING dpmGetActivityBit:ltrSyncSend FAILED for MAC_ADDR/MAC_VLAN. MAC addr: 0x000e7f36ecc8,pimport: 4, destslot: 3, status=9</p>
<p>I got two instances of this on two user devices. Nortel ticket opened and they stated if it does not happen a great deal, don&#8217;t worry. It is some sort of  &#8220;I&#8217;m too busy right now to handle your specific need, but I&#8217;ll log this message for you&#8221; type of error. I don&#8217;t know. I have not noticed any problems since going to 4.1.7.2. </p>
<p>These entries appear in both ERS cores IST connected. Things have been stable, thus far. Glad to dump the 4.0.3.0/4.0.6.0 crap.</p>
<p>Gene</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael McNamara</title>
		<link>http://blog.michaelfmcnamara.com/2008/07/ers-8600-software-4160-buggy/#comment-536</link>
		<dc:creator>Michael McNamara</dc:creator>
		<pubDate>Wed, 28 Jan 2009 01:22:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfmcnamara.com/?p=222#comment-536</guid>
		<description>I believe we should see 4.1.8.2 within the next week or two. 

While I can&#039;t say much right now (Non-disclosure agreement), I will be happy to comment on 4.1.8.2 when it is released.

Thanks again for the feedback!</description>
		<content:encoded><![CDATA[<p>I believe we should see 4.1.8.2 within the next week or two. </p>
<p>While I can&#8217;t say much right now (Non-disclosure agreement), I will be happy to comment on 4.1.8.2 when it is released.</p>
<p>Thanks again for the feedback!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: michael gagnon</title>
		<link>http://blog.michaelfmcnamara.com/2008/07/ers-8600-software-4160-buggy/#comment-531</link>
		<dc:creator>michael gagnon</dc:creator>
		<pubDate>Tue, 27 Jan 2009 19:40:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfmcnamara.com/?p=222#comment-531</guid>
		<description>i ran into the same issues upgrading from 4.1.1.1 --&gt; 4.1.7.2 over holiday shutdown a month ago.  i&#039;m surprised it took nortel (and escalation) so long before someone got a fix for us (approx 3-4 days going back and forth with escalation).  the FDB-ageout entry fix worked immediately.  still waiting for 4.1.8.0 to arrive; anyone else hear of an ETA?</description>
		<content:encoded><![CDATA[<p>i ran into the same issues upgrading from 4.1.1.1 &#8211;&gt; 4.1.7.2 over holiday shutdown a month ago.  i&#8217;m surprised it took nortel (and escalation) so long before someone got a fix for us (approx 3-4 days going back and forth with escalation).  the FDB-ageout entry fix worked immediately.  still waiting for 4.1.8.0 to arrive; anyone else hear of an ETA?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Served from: blog.michaelfmcnamara.com @ 2012-02-08 17:11:17 by W3 Total Cache -->
