Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi I am getting this error%MDT-4-INCOMPATIBLE_TUNNEL_TYPE: Incompatible tunnel type in BGP update router_id:2.0.200.8 RD:200:2 type:1 tunnel_type:4; local tunnel_type:3 the MVPN is between IOS-XE and IOS XR please correct me if I am wrong - the above...
Hi, My trace is not working in one direction. Ping for Site A to Site B and vice versa works (PING's are from CE TO CE and CPE) SITEA#ping vrf DDDDD-DDDD x.x.228.57 source x.x.228.65Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to x.x....
Hi,
Could someone please explain that why am I seeing this output ? I think I should see just one route, but I see two paths coming from same BGP neighbor and RR, the only difference I see is that best path has Extended community and the other path...
I have AS 100 with 3 routers (R1, R2 and R3) running OSPF and IBGP. R2 Being route reflector R1 is connected to R4 (EBGP) === R4 is advertising 11.0.0.1/8R2 is connected to R5 (EBGP) === R5 is advertising 11.0.0.1/16R3 is connected to R6 (EBGP) ===...
While redistributing BGP routes to OSPF, I see some routes as TYPE 3 LSA and majority of routes as Type 5 LSA in OSPF database. Why I am seeing Type 3 LSA?? They should all be Type 5 right? Can some one suggest anything? Thanks
Even if its cisco router and I get same prefixes from all three ISP's, weight is not a good option, bcz weight is local to router, it does not get advertised within the AS. R2 and R3 will never know that R1 is the preferred exit path as weight is app...
Weight or any other BGP path attribute will not work in this case. Before hitting the BGP attributes its hitting the normal Route selection process which is matching the longest prefix.
