Hey everybody, this is my first post... hopefully I'm doing this properly. I have a dual-homed ISP architecture that I would like to take from active/standby to load-balanced. I'm BGP peering with both ISPs and redistributing all the routes into my OSPF core. Is there a simple way to load-balance the two ISP links in this architecture? Maybe there's a way to carry the AS path into OSPF and calculate that into the metric? Please help!
Hello, I followed this documentation from cisco site. But me did not work. follows the topology and configuration attached below.
RouterA ! interface FastEthernet0/0 ip address 10.10.10.1 255.0.0.0 duplex auto speed auto ! interface FastEthernet1/0 ip address 188.8.131.52 255.0.0.0 duplex auto speed auto ! interface FastEthernet2/0 ip address 184.108.40.206 255.0.0.0 duplex auto speed auto ! interface FastEthernet2/1 ip address 220.127.116.11 255.0.0.0 duplex auto speed auto ! router bgp 300 no synchronization no bgp log-neighbor-changes network 18.104.22.168 network 22.214.171.124 neighbor 10.10.10.10 remote-as 100 neighbor 10.10.10.10 route-map UPDATES-1 in neighbor 126.96.36.199 remote-as 200 neighbor 188.8.131.52 route-map UPDATES-2 in no auto-summary ! access-list 1 permit 0.0.0.0 access-list 2 deny 0.0.0.0 access-list 2 permit any ! route-map UPDATES-2 permit 10 match ip address 1 ! route-map UPDATES-2 permit 20 match ip address 2 set weight 100 ! route-map UPDATES-1 permit 10 match ip address 1 set weight 100 ! route-map UPDATES-1 permit 20 match ip address 2
Router SP-A ! interface FastEthernet0/0 ip address 10.10.10.10 255.0.0.0 duplex auto speed auto ! router bgp 100 no synchronization no bgp log-neighbor-changes neighbor 10.10.10.1 remote-as 300 neighbor 10.10.10.1 default-originate neighbor 10.10.10.1 soft-reconfiguration inbound no auto-summary ! Router SP-B ! interface FastEthernet0/0 ip address 184.108.40.206 255.0.0.0 duplex auto speed auto ! ! router bgp 200 no synchronization no bgp log-neighbor-changes neighbor 220.127.116.11 remote-as 300 neighbor 18.104.22.168 default-originate neighbor 22.214.171.124 soft-reconfiguration inbound no auto-summary !
In the example of the site said to use an access-list to match traffic from 126.96.36.199 188.8.131.52 until I changed the access-list to get the default (0.0.0.0) and enter the command "neighbor ip default-originate" even so not working. Does anyone have any idea where I'm wrong?
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...