Thank you for answer, This bug details is very similar to our problem. We will try to apply this workaround If this helps us we will write about it
2010/3/22 Paolo Lucente <[email protected] <pl%[email protected]>> > Perhaps it's CSCtd26215. If BGP dampening is enabled, give a try disabling > it. > > Cheers, > Paolo > > On Mon, Mar 22, 2010 at 01:02:59PM +0200, [email protected] wrote: > > > > Hello all, > > > > We have faced the same problem when we have tried to update to version > > SRD4. > > Our hardware is Cisco 7600 with RSP720-3CXL-GE with 2GB RAM and > > WS-X6704-10GE. > > We have observed the bgp notification in logging such as "neighbor > > 1xx.x.x.x 3/1 (update malformed)". > > The all sessions get down after that with message "Down No memory" > > > > Who was faced with such problem also? How to solve it? > > > > We had the following errors log occur: > > > > %BGP-5-ADJCHANGE: neighbor 1xx.x.x.x Down BGP Notification sent > > %BGP-3-NOTIFICATION: sent to neighbor 1xx.x.x.x 3/1 (update malformed) 0 > > bytes > > %BGP-4-MSGDUMP: unsupported or mal-formatted message received from > > 1xx.x.x.x: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 004F 0200 0000 3440 > > 0101 0040 0208 0203 00AE 04D7 8F11 4003 0495 068D A980 0404 0001 4C26 > > 4006 00C0 0706 8F11 D018 1489 C008 0800 AE52 0800 AE55 FD18 C029 A2 > > %BGP-5-ADJCHANGE: neighbor 10.x.x.x vpn vrf XX Down No memory > > %BGP_SESSION-5-ADJCHANGE: neighbor 10.x.x.x IPv4 Unicast vpn vrf IT > > topology base removed from session No memory > > %BGP-5-ADJCHANGE: neighbor 6x.x.x.x Down No memory > > %BGP_SESSION-5-ADJCHANGE: neighbor 6x.x.x.x IPv4 Unicast topology base > > removed from session No memory ... > > > > > > > > Mack McBride ??????????: > > > I am looking at 2 - 7600s with RSP720-3CXLs w/ 4GB of RAM and 6708-3CXL > cards running SRD3. > > > These are not currently production equipment but are connected to > upstreams > > > as well as route-reflectors but are not advertising routes as we have > advertisements blocked > > > with a deny-all prefix list. We THINK the dumped BGP packet is > correctly formatted and > > > the packet dumped is actually the packet before the bad packet. Has > anyone else > > > seen similar issues? Does anyone else know if this is a known bug that > exists in this code or > > > early versions of the SRD train? I know there are entirely too many > caveats in SRC5. > > > > > > Mack McBride > > > Network Architect > > > ViaWest, Inc. > > > > > > We had the following errors occur: > > > > > > Log from 7600-01: > > > Nov 24 02:41:59.696 MST: %BGP-5-ADJCHANGE: neighbor 207.xx.xx.xx Down > BGP Notification sent > > > Nov 24 02:41:59.696 MST: %BGP-3-NOTIFICATION: sent to neighbor > 207.xx.xx.xx 3/1 (update malformed) 0 bytes > > > Nov 24 02:41:59.696 MST: %BGP-4-MSGDUMP: unsupported or mal-formatted > message received from 207.xx.xx.xx: > > > FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0064 0200 0000 4940 0101 0040 > 0208 0203 > > > 10E3 00AE 0865 4003 04CF FA73 1540 0600 C007 0608 659A 3604 36C0 0824 > 10E3 0033 > > > 10E3 01F5 10E3 03F7 10E3 09C7 10E3 C350 FE4D 03F7 FE4E 0004 FE4F 0001 > FE50 012D > > > 18C0 2104 > > > Nov 24 02:41:59.748 MST: %BGP-5-ADJCHANGE: neighbor 74.xx.xx.xx1 Down > No memory > > > Nov 24 02:41:59.748 MST: %BGP_SESSION-5-ADJCHANGE: neighbor > 74.xx.xx.xx1 IPv4 Unicast topology base removed from session No memory > > > Nov 24 02:41:59.748 MST: %BGP-5-ADJCHANGE: neighbor 74.xx.xx.xx2 Down > No memory > > > Nov 24 02:41:59.748 MST: %BGP_SESSION-5-ADJCHANGE: neighbor > 74.xx.xx.xx2 IPv4 Unicast topology base removed from session No memory > > > Nov 24 02:41:59.748 MST: %BGP_SESSION-5-ADJCHANGE: neighbor > 207.xx.xx.xx IPv4 Unicast topology base removed from session BGP > Notification sent > > > Nov 24 02:42:06.384 MST: %BGP-5-ADJCHANGE: neighbor 207.xx.xx.xx Up > > > Nov 24 02:42:12.640 MST: %BGP-5-ADJCHANGE: neighbor 74.xx.xx.xx2 Up > > > Nov 24 02:42:12.672 MST: %BGP-5-ADJCHANGE: neighbor 74.xx.xx.xx1 Up > > > Nov 24 02:42:31.436 MST: %BGP-5-ADJCHANGE: neighbor 207.xx.xx.xx Down > BGP Notification sent > > > Nov 24 02:42:31.436 MST: %BGP-3-NOTIFICATION: sent to neighbor > 207.xx.xx.xx 3/1 (update malformed) 0 bytes > > > Nov 24 02:42:31.440 MST: %BGP-4-MSGDUMP: unsupported or mal-formatted > message received from 207.xx.xx.xx: > > > FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0064 0200 0000 4940 0101 0040 > 0208 0203 > > > 10E3 00AE 0865 4003 04CF FA73 1540 0600 C007 0608 659A 3604 42C0 0824 > 10E3 0033 > > > 10E3 01F5 10E3 03F7 10E3 09C7 10E3 C350 FE4D 03F7 FE4E 0004 FE4F 0001 > FE50 012D > > > 18C0 2104 > > > Nov 24 02:42:31.504 MST: %BGP-5-ADJCHANGE: neighbor 74.xx.xx.xx1 Down > No memory > > > Nov 24 02:42:31.504 MST: %BGP_SESSION-5-ADJCHANGE: neighbor > 74.xx.xx.xx1 IPv4 Unicast topology base removed from session No memory > > > Nov 24 02:42:31.504 MST: %BGP-5-ADJCHANGE: neighbor 74.xx.xx.xx2 Down > No memory > > > Nov 24 02:42:31.504 MST: %BGP_SESSION-5-ADJCHANGE: neighbor > 74.xx.xx.xx2 IPv4 Unicast topology base removed from session No memory > > > Nov 24 02:42:31.504 MST: %BGP_SESSION-5-ADJCHANGE: neighbor > 207.xx.xx.xx IPv4 Unicast topology base removed from session BGP > Notification sent > > > Nov 24 02:42:38.620 MST: %BGP-5-ADJCHANGE: neighbor 74.xx.xx.xx2 Up > > > Nov 24 02:42:38.620 MST: %BGP-5-ADJCHANGE: neighbor 207.xx.xx.xx Up > > > Nov 24 02:42:42.928 MST: %BGP-5-ADJCHANGE: neighbor 74.xx.xx.xx1 Up > > > > > > 7600-02: > > > Nov 24 02:42:16.343 MST: %BGP-5-ADJCHANGE: neighbor 4.xx.xx.xx Down BGP > Notification sent > > > Nov 24 02:42:16.343 MST: %BGP-3-NOTIFICATION: sent to neighbor > 4.xx.xx.xx 3/1 (update malformed) 0 bytes > > > Nov 24 02:42:16.343 MST: %BGP-4-MSGDUMP: unsupported or mal-formatted > message received from 4.xx.xx.xx: > > > FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 005F 0200 0000 4440 0101 0040 > 0208 0203 > > > 0D1C 00AE 0865 4003 0404 350B 8580 0404 0000 0000 4006 00C0 0706 0865 > 9A36 0436 > > > C008 180D 1C00 030D 1C00 160D 1C00 560D 1C02 3F0D 1C02 9A0D 1C07 D818 > C021 04 > > > Nov 24 02:42:16.403 MST: %BGP_SESSION-5-ADJCHANGE: neighbor 4.xx.xx.xx > IPv4 Unicast topology base removed from session BGP Notification sent > > > Nov 24 02:42:16.403 MST: %BGP-5-ADJCHANGE: neighbor 74.xx.xx.xx1 Down > No memory > > > Nov 24 02:42:16.403 MST: %BGP_SESSION-5-ADJCHANGE: neighbor > 74.xx.xx.xx1 IPv4 Unicast topology base removed from session No memory > > > Nov 24 02:42:16.403 MST: %BGP-5-ADJCHANGE: neighbor 74.xx.xx.xx2 Down > No memory > > > Nov 24 02:42:16.403 MST: %BGP_SESSION-5-ADJCHANGE: neighbor > 74.xx.xx.xx2 IPv4 Unicast topology base removed from session No memory > > > Nov 24 02:42:22.907 MST: %BGP-5-ADJCHANGE: neighbor 4.xx.xx.xx Up > > > Nov 24 02:42:25.551 MST: %BGP-5-ADJCHANGE: neighbor 74.xx.xx.xx2 Up > > > Nov 24 02:42:29.107 MST: %BGP-5-ADJCHANGE: neighbor 74.xx.xx.xx1 Up > > > > > > _______________________________________________ > > > cisco-nsp mailing list [email protected] > > > https://puck.nether.net/mailman/listinfo/cisco-nsp > > > archive at http://puck.nether.net/pipermail/cisco-nsp/ > > > > > > > _______________________________________________ > > cisco-nsp mailing list [email protected] > > https://puck.nether.net/mailman/listinfo/cisco-nsp > > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
