i hve the following network design which we r planning to upgrade after sometime.meanwhile we need to consider redundancy,reliability and resilence.
we have 2 routers one 1751/one 803 both r in remote location. 1751 connected to our 7206 via 2Mbps pipe.1751 and 803 connected thru ethernet(via switch).in 1751 we hve got 3 other locations connected dont hve isdn port in tht.so we r planning to use th isdn line with 803.
can i run HSRP or VRRP in this situation ?will it work?i prefer to get all u r inputs and testing b4 going on road to implement the same.
how can i configure hsrp ??which port do i need to preempt ?how the routing part will be done ?
how my remote locations will sense and make use of redundancy(using hsrp)??pls advice/help/explain.
I would say you cannot use HSRP to provide redundancy for remote connections. You will have to use either a dynamic routing protocol or work with (floating) static routes and e.g. manipulate admin distances on these static routes.
this is a extended kinda of setup.we hv already got our own core routers placed in diff location(locationA).we r connecting this 1751 with one of our routers ther in location A.
since we dont want to run any dynamic protocols in these routers(1751,803)tried with static which is not wkg when the 2Mbps pipe goes down.isdn is geting fired but traffic is not moving out of the bri port.
this issue is hitting my head like anything ..
any help pls ..
ip address x.x.x.33 255.255.255.252
ip address y.y.y.186 255.255.255.252
ip route 0.0.0.0 0.0.0.0 Serial1/1(cnnected to our core router)
ip route 0.0.0.0 0.0.0.0 a.a.a.15 10
ip route a.a.a.15(eth of 803) 255.255.255.255 FastEthernet0/0
no ip http server
config of 803
ip route 0.0.0.0 0.0.0.0 bri 0
ip route a.a.a.9(eth 1751) 255.255.255.255 Ethernet0/0
ip route x.x.x.36 255.255.255.252 eth0/0
core config :
ip route x.x.x.36 255.255.255.252 ser 12/0/7
ip route x.x.x.36 255.255.255.252 briip 240
incidently the BRI is getting connected to our RAS which is again hving our corerouter as g/w.
so if i route via briip with metric it shuld take ,ideally which is working for other customers not with the same setup.
we hve tested the same with some routing changes in our RAS after tht the routing issue is solved now.
our main concern right now is though we hve mentioned the 803 shuld be used only during backup we have added static according to tht in our 1751 which i hv clearly mentioned in my previous post.
but now my problem is though my wan link is up in 1751 my isdn is getting fired at times which i dont require and want to restrict.i tried even putting 255 as dialer load threshold ,still the prob presists.
In my 803 i hve given a default route thru bri interface.becoz of tht its getting connected all the times.since my 1751 and 803 are connected via eth i cant put default route via eth since tht wont go down untill unless we do something manual.
anyway out ther to comeout of this troublesome problem ??
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 custome...