I am hardly a BGP expert, so please don't quote this as gospel, but...I am reasonably familiar with RFC 1812, requirements for IP version 4 routers by Fred Baker of Cisco Systems. I would also call it, "what a good router should be when it grows up..." Having said that, I would call your attention to paragraph 5.3.7 "Martian Address Filtering" The specific paragraph in question reads as follows: A router SHOULD NOT forward any packet that has an invalid IP destination address or a destination address on network 0. A router SHOULD NOT forward, except over a loopback interface, any packet that has a destination address on network 127. A router MAY have a switch that allows the network manager to disable these checks. If such a switch is provided, it MUST default to performing the checks. Since it appears that your router is attempting to show a next hop address of 157.130.255.255, that might be a slight problem, due to the fact that 157.130.255.255 is probably a broadcast address, assuming a netmask of /16. If your neighbor is propagating a route like this, my guess is that your router is barfing on it. Generally, it is pretty tough to induce such a fault on a router due to built in safety locks. For example, if I attempted to add an ip address that is listed below, it would come out as follows (watch wrap): cisco804(config-if)#ip add 157.130.255.255 255.255.0.0 Bad mask /16 for address 157.130.255.255 Notice what happens when I change the mask: cisco804(config-if)#ip add 157.130.255.255 255.255.255.255 cisco804(config-if)# Notice that now it took without any problem when placed on a loopback interface. If you check the routing table and neighbor notifications however, it is a different story: IP-EIGRP: Processing incoming UPDATE packet IP-EIGRP: Int 157.130.255.255/32 M 409600 - 256000 153600 SM 128256 - 256 128000 IP-EIGRP: 157.130.255.255/32 routing table not updated IP-EIGRP: 192.168.1.0/24, - do advertise out Ethernet2/0 BFR#sh ip rou Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default U - per-user static route, o - ODR Gateway of last resort is not set 3.0.0.0/24 is subnetted, 1 subnets C 3.3.3.0 is directly connected, Ethernet2/1 C 192.168.1.0/24 is directly connected, Ethernet2/0 BFR# I cannot say if this is the exact culprit, but you may want to check with the peer out your 157.130.6.101 interface to see if the neighbor/BGP speaker is advertising a bad/Martian route. HTH, Paul Werner > Hi Group, > > I've been experience problems BGP sessions running on our core > route, > Does anyone know what %BADCOPY-3-BADCOPYCOUNT error message is ??? It > would appear that every time this error occur we lose our connectivity > with > our peers .... > > I've enclosed part of the router log, the IOS version is Version > 11.1(27)CC, and the router is a 7500 > > If anyone can help I we'll be most grateful. > > Thanks in Advance > Anthony > > > > > Log Buffer (16384 bytes): > 09:34:13: %BADCOPY-3-BADCOPYCOUNT: bad copy count from 0x6150E67A to > 0x6150E8A8 count 0xFFFFFFFE > - -Traceback= 601E0484 60145EB8 603BDB24 603C28F4 603C4D0C 603CBA10 > 603D096C > 60167D08 60167CF4 > Jan 3 09:34:29: %BGP-6-NEXTHOP: Invalid next hop (157.130.255.255) > received > from 157.130.6.101: martian next hop > Jan 3 09:35:12: %BADCOPY-3-BADCOPYCOUNT: bad copy count from 0x6150E67A > to > 0x6150E8A8 count 0xFFFFFFFE > - -Traceback= 601E0484 60145EB8 603BDB24 603C28F4 603C4D0C 603CBA10 > 603D096C > 60167D08 60167CF4 ________________________________________________ Get your own "800" number Voicemail, fax, email, and a lot more http://www.ureach.com/reg/tag _________________________________ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]