SR-7102 multihoming- full BGP routing table supported?

[Igoris_1]

I am trying to configure multihoming with two ISPs on secure router 7102. When ISP is sending full BGP routing table to the 7102 router it stops responding from LAN, only console session works, CPU 99% and after 5 minutes or so router gets back to life, but no BGP routes seen in the routing table, it seems router can't accept such large BGP routing table. Any ideas how to configure BGP multihoming?

[Mohieddin Kharnoub]

Hi

The BGP Multihoming on the ProCurve Secure Router concept and examples can be found here:

ftp://ftp.hp.com/pub/networking/software/SR7000dl-Adv-C15-Adv_Routing-Nov2006.pdf

Have a look then check your configuration, and see if you can do something.

If you need more help, try to explain little about the topology you have and attach the configuration on the router.

Good Luck !!!

[Igoris_1]

I configured to filter incoming BGP routes with a prefix length greater than 16, but it seems filtering does not work, router receives up to 160000 routing entries, says "out of memory" and reboots. This is the part of config:
ip prefix-list baltneta seq 10 deny 0.0.0.0/0 ge 16 le 32
router bgp 30775
no auto-summary
no synchronization
network 89.249.80.0 mask 255.255.240.0
neighbor 195.14.169.218
no default-originate
description Baltnet
ebgp-multihop 10
prefix-list baltneta in
prefix-list fdl_out_deny out
soft-reconfiguration inbound
remote-as 8486

How come I receive route 12.18.239.0/24 when prefix-list configured to deny length greater than 16?

[Igoris_1]

some more info:
Latest Firmware revision: J06.06
ISP router is connected to the 7102 through an ethernet interface.
Can anybody try prefix-list filtering, to see if the problem replays? I used configuration from ProCurve-SR-BGP-Config-Guide-08-05.pdf and SR7000dl-AdvncdMgmtConfig-Nov2006.pdf, none works, it looks like software bug.

[sebusel]

I get stuck with similar problem, debuging by serial port shows that router reloads while device receiving BGP informiation from ISP. After restart there is alog information:

Cause of reset: JTAG Reset
Core: source\PacketCore\AdUtil\AdAlloc.cpp#430: AdFatal(OUT OF MEMORY ...

I have sent email to ProCurve tech support and there is opened a case.

I tried to workaround this problem but I am not sure if I had used prefix-list filter in right way.