We would like to do load sharing between the 2 ISP's.
For Incoming traffic, can we advertise our IP range through both the ISP's without any preference attribute. The Internet Community based on peering of ISP1 and ISP2 with other service providers shall decide the incoming traffic based on the geographical orientation of the ISPs across the Internet.
this is possible for sure. Do you have your own official AS number? If not, then the config gets somewhat more tricky.
In case you have an official AS number the config could look like this:
description to ISP1
ip address 1.4.x.x.x.255.252
description to ISP2
ip address 2.2.x.x.x.255.252
router bgp 65000
network 184.108.40.206 mask 255.255.0.0
neighbor 220.127.116.11 remote-as 1 ! ISP1
neighbor 18.104.22.168 prefix-list NoTrash in
neighbor 22.214.171.124 filter-list 1 out
neighbor 126.96.36.199 weight 150
neighbor 188.8.131.52 remote-as 2 ! ISP2
neighbor 184.108.40.206 prefix-list NoTrash in
neighbor 220.127.116.11 filter-list 1 out
neighbor 18.104.22.168 weight 100
ip as-path access-list 1 permit ^$
ip prefix-list NoTrash deny 192.168.0.0/16 le 32
ip prefix-list NoTrash deny 172.16.0.0/12 le 32
ip prefix-list NoTrash deny 10.0.0.0/8 le 32
ip prefix-list NoTrash deny 22.214.171.124/16 le 32
ip prefix-list NoTrash permit 0.0.0.0/0 le 32
ip route 1.1.x.x.255.0.0 Null 0 250
This would not announce only the assigned IP addresses (assumed 126.96.36.199/16) to ISP1 and ISP2, i.e. it prevents that you become transit AS between them. Also all RFC1918 routes are blocked. You could extend this and use the BOGON list for filtering, but this would require more maintainance, because you have to adjust the filters from time to time. For a customer it should be sufficient to block all routes you potentially have internally.
You need to adjust IP addresses, AS numbers and prefix to your environment.
In this example ISP1 is primary and ISP2 is backup (selected through weight). In case you want to have a more flexible selection you should use an incoming route-map to set f.e. Local Preference.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...