My branch campus network will have 2nd ISP by next month. So we decided to do the multihoming for link redundancy & traffic sharing. Since i'm a beginner in BGP area, need feedback from you guys regarding preparation before doing the multihoming configuration. The questions as below :
as in branch campus you'll have 2 ISPs connected to 1 device.
If your current setup supposes BGP connectivity with your current ISP, you should have AS number already. You can use it for peering with your second ISP - or request AS number from him, but in that case you'll need to use local-as feature (http://www.cisco.com/en/US/partner/docs/ios/12_3t/ip_route/command/reference/ip2_n1gt.html#wp1098123) Also you need your local IP address for peering, ip address of neighboring device and ip address block (if they support this service) for NATing your internal address space.Also your ISP can provide you some communities for tagging your network prefixes you need to advertise outside.
2) As it was said previously, it depends on your current configuration. If both your sires (Main Campus and Branch Campus) are connected to your current ISP via BGP - you should have AS number(s) already.
3) You need develop local policies describing how your traffic will be forwarded inside and outside. What is your primary link between sites - Metro or via ISP? Will you use both links (to ISP1 and ISP2) in the same time? How to avoid asimmetrical routing in this case?
4) For multihoming it doesn't matter if you will use IPv6 in future or not. But some day you'll need to check if your ISPs supports IPv6 infrastructure. In this case your transition will be very simple; otherwise you'll need to use some tunneling mechanisms.
5) It depends again on what is the primary link between your sites. If it is Metro - you can use static routes from branch campus to MYREN address space and vice versa, or if you have iBGP session between Main and Branch - use BGP policies to advertise prefixes. To answer this question we need more information about current configuration of your devices.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...