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’t have to worry about that. The cpu will recover itself.Please send me the updates as soon as possible.

Thank you,

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.

http://blog.michaelfmcnamara.com/2009/02/ethernet-routing-switch-8600-software-release-v4182/

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’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!

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’t worry. It is some sort of “I’m too busy right now to handle your specific need, but I’ll log this message for you” type of error. I don’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

While I can’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!

I’ve personally experienced the bug you are referring to. The latest stable version of code that I ran was v4.1.1. I didn’t have any IST/SMLT or ARP/FDB issues with v4.1.1 software. A fully meshed four way switch cluster can be very complicated. When you made the FDB aging change did you change every VLAN on all four core switches? If you are still having the problem I would suggest you continue to lean on Nortel and have the case escalated. I did hear through the grape vine that v4.1.8 is supposed to be release by Friday of this week.

Good Luck!

you have very good webpage!
We had the same problem with the 4.1.6 Firmware, but the timer change didn’t solve the problem. Nortel told us to perform a downgrade to 4.1.5.

Ok, now we running the firmware 4.1.5, but the problem is still existent!

The problem is,´the switch lost the traffic and doesn’t have a entry in the arp table. A ping from the switch is the solution.

We have 4 ERS8600, two pairs(IST)connected a full meshed SMLT.

On the ERS8600 linecards we have HP bladecenter with cisco switche in a SMLT configuration.

The strange thing on the bug is, sometimes we have the bug, sometimes we don’t have the bug.

I’m at the end and I think my consulatns, too.

Normally I had work we Cisco 6500 switches, so that’s my first contact with Nortel and it’s not the best start :-(

I hope you have any ideas

By

René