In your peering sessions you will announce the same block out to both providers. Make sure your providers do not prepend your announcement and that they will just forward to their upstream your network.
Your traffic inbound will be determined by metrics, not everyone will come in on the same path. Your outbound traffic will work much the same way. When peering with your ISP's you might want to get full routes from them, BUT make sure you have enough memory. The routing tables are rather large and having both ISP's send them will eat up a lot of memory. Make sure you have no less then 256k
I prefferd u ple go with OER or if this is not possible then you can buy link proof branch which is the load balancer because with 2 different isp's ,it will depends on isp's how they are supporting you ,and also one big issue is public and private AS number.
And through load balancing protocols like (GLBP and HSRP..)redundency is possible but load shearing is possible in place of load balancing .
[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...