Pipe collision detected when sending x.x.x.x to table Collector

[Javor Kliachev]

Hello, We're trying to implement in our RS configuration additional "Collector" table. After making the changes began to generate the following message to our log file like this and our log file become too large for a very short time : 17-12-2012 13:57:16 <ERR> Pipe collision detected when sending 120.28.62.0/24 to table Collector 17-12-2012 13:57:16 <ERR> Pipe collision detected when sending 120.28.62.0/24 to table Collector 17-12-2012 13:57:16 <ERR> Pipe collision detected when sending 120.28.62.0/24 to table Collector 17-12-2012 13:57:16 <ERR> Pipe collision detected when sending 120.28.62.0/24 to table Collector 17-12-2012 13:57:16 <ERR> Pipe collision detected when sending 120.28.62.0/24 to table Collector 17-12-2012 13:57:16 <ERR> Pipe collision detected when sending 120.28.62.0/24 to table Collector 17-12-2012 13:57:16 <ERR> Pipe collision detected when sending 120.28.62.0/24 to table Collector 17-12-2012 13:57:16 <ERR> Pipe collision detected when sending 120.28.62.0/24 to table Collector 17-12-2012 13:57:16 <ERR> Pipe collision detected when sending 120.28.62.0/24 to table Collector 17-12-2012 13:57:16 <ERR> Pipe collision detected when sending 120.28.62.0/24 to table Collector Also we observe that this generating message caused our processor to load significantly. Such message is generated of each received prefixes. In this particular lab we have only one established BGP session and other 10-11 neighbors not active. Everything other works fine. We would like to understand if there is something wrong in our configuration? Here is the configuration which we generated for each new BGP session: table T65050 protocol pipe P65050 from PIPES {   description "PINGER_PIT";   peer table T65050;   export where bgp_out(65050); } protocol pipe C65050 from PIPES {  description "PINGER_PIT";  table Collector;  peer table T65050;  export none; }  protocol bgp R0_149 from PEERS {   description "0.149_PINGER_PIT";   neighbor 193.218.0.149 as 65050;   import where bgp_in(65050);   route limit 320000;   table T65050; } Global configuration: table Collector; # Protocol templates template bgp PEERS {   local as myas;   import all;   export all;   route limit 10000;   rs client;   passive on;   prefer older on; } template pipe PIPES {   table master;   mode transparent; } Thanks in advance! Best~ -- --- Javor Kliachev IP engineer Neterra Ltd. Telephone: +359 2 975 16 16 Fax: +359 2 975 34 36 Mobile: +359 885 988 495 www.neterra.net